From owner-freebsd-net@FreeBSD.ORG Sun Nov 30 03:20:24 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9BA416A4CE; Sun, 30 Nov 2003 03:20:24 -0800 (PST) Received: from sphinx.mythic-beasts.com (sphinx.mythic-beasts.com [195.82.107.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87BBA43FDF; Sun, 30 Nov 2003 03:20:23 -0800 (PST) (envelope-from xelah@sphinx.mythic-beasts.com) Received: from xelah (helo=localhost) by sphinx.mythic-beasts.com with local-esmtp (Exim 3.33 #3) id 1AQPci-0003F4-00; Sun, 30 Nov 2003 11:20:20 +0000 Date: Sun, 30 Nov 2003 11:20:19 +0000 (GMT) From: Alex Hayward X-X-Sender: xelah@sphinx.mythic-beasts.com To: cjc@freebsd.org In-Reply-To: <20031130073243.GA4474@blossom.cjclark.org> Message-ID: References: <20031130073243.GA4474@blossom.cjclark.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Alex Hayward cc: freebsd-net@freebsd.org Subject: Re: Racoon(8) Deleting SPD Entries X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2003 11:20:24 -0000 On Sat, 29 Nov 2003, Crist J. Clark wrote: > Versions: Racoon(8) from ports racoon-20030826a. FreeBSD kernel > 4.8-RELEASE-p13. Running with net.key.prefered_oldsa=1, but flipping > to 0 does not seem to make a difference. I've never quite seen the point of this option; surely using the old SA just can't possibly work properly? > I am having some problems with racoon(8). Everything works fine for > the lifetime of the initial SA, but then things die. When the initial > SA is removed, racoon(8) seems to be clearing out the corresponding > entry in the SPD. However, when we had reached the soft timeout > earlier, racoon(8) had established new SAs. Since we have good SAs, > racoon(8) doesn't try to do new negotiations. Both ends have a good > SAD, but the responder no longer has SPD entries for the pair. I've come across this, too. It appears to be a bug in Racoon; I've submitted a bug report to KAME - bug fbsd4/530. When Racoon creates the security policy it gives it a timeout equal to the timeout on the SA. It doesn't renew this timeout when a new SA is negotiated and will only create a new SP if the existing SP has already timed out. My solution was to statically configure the security policies. This works OK for us because the clients have static IP addresses - but it means that their dial-up fallback won't work because their IP addresses will change. It looks like the SP timeout could be left unset as a quick fix. Ideally, though, I'd prefer to have some sort of 'security policy template' database which would allow clients with particular IDs to establish SPs tunnelling to/from only particular networks but with the remote tunnel endpoints being whatever IP addresses they have at the time. There is a possibility I'll get the chance to work on doing this. On the other hand we might just use Linux and FreeSWAN instead. From owner-freebsd-net@FreeBSD.ORG Sun Nov 30 04:26:38 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53C1616A4CF for ; Sun, 30 Nov 2003 04:26:38 -0800 (PST) Received: from spf13.us4.outblaze.com (205-158-62-67.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DCF543FCB for ; Sun, 30 Nov 2003 04:26:33 -0800 (PST) (envelope-from ivo@bsdmail.org) Received: from 205-158-62-68.outblaze.com (205-158-62-68.outblaze.com [205.158.62.68]) by spf13.us4.outblaze.com (Postfix) with QMQP id A91F81801C74 for ; Sun, 30 Nov 2003 12:26:31 +0000 (GMT) Received: (qmail 99825 invoked from network); 30 Nov 2003 12:26:31 -0000 Received: from unknown (HELO ws5-2.us4.outblaze.com) (205.158.62.133) by 205-158-62-153.outblaze.com with SMTP; 30 Nov 2003 12:26:31 -0000 Received: (qmail 7869 invoked by uid 1001); 30 Nov 2003 12:26:31 -0000 Message-ID: <20031130122631.7868.qmail@bsdmail.com> Content-Type: multipart/mixed; boundary="----------=_1070195191-6845-0" Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [62.73.96.164] by ws5-3.us4.outblaze.com with http for ivo@bsdmail.org; Sun, 30 Nov 2003 14:26:31 +0200 From: "Ivo Vachkov" To: freebsd-ipfw@freebsd.org Date: Sun, 30 Nov 2003 14:26:31 +0200 X-Originating-Ip: 62.73.96.164 X-Originating-Server: ws5-3.us4.outblaze.com cc: freebsd-net@freebsd.org Subject: X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2003 12:26:38 -0000 This is a multi-part message in MIME format... ------------=_1070195191-6845-0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Hi all, I've been trying to write some code using divert(4) sockets, but i meet the following difficulties: - when i get diverted packet it has both source and destination IP addresses the same. The attached code shows: 192.168.0.2 -> 192.168.0.2 getting 84 bytes, real: 84 and the way I run it is (on 192.168.0.2): ipfw add 100 divert 8670 ip from any to 192.168.0.1 burstd then on 192.168.0.2 I issue "ping 192.168.0.1" - the manual says this happens with recvfrom()/sendto(), but recv() is mentioned to be same as recvfrom() and read()/write() sometimes fail. After digging some kernel code I've found that around line 167 in ip_divert.c we have: /* * Record receive interface address, if any. * But only for incoming packets. */ divsrc.sin_addr.s_addr = 0; if (incoming) { struct ifaddr *ifa; /* Sanity check */ KASSERT((m->m_flags & M_PKTHDR), ("%s: !PKTHDR", __FUNCTION__)); /* Find IP address for receive interface */ TAILQ_FOREACH(ifa, &m->m_pkthdr.rcvif->if_addrhead, ifa_link) { if (ifa->ifa_addr == NULL) continue; if (ifa->ifa_addr->sa_family != AF_INET) continue; divsrc.sin_addr = ((struct sockaddr_in *) ifa->ifa_addr)->sin_addr; break; } } which (as I think) changes the address of diverted packet. What is the reason for that and are there any workarounds to get real source and destination IP addresses from a diverted packet. I need both because I try to make connection tracking based on src<->dst . Any help with that is appretiated. Any divert code welcome. I've looked through natd.c and it was helpfull. Ivo Vachkov P.S. Excuse my: - English - long pastes - (sometimes) lack of kernel code understanding -- _______________________________________________ Get your free email from http://mymail.bsdmail.com Powered by Outblaze ------------=_1070195191-6845-0 Content-Type: application/octet-stream; name="Makefile" Content-Disposition: attachment; filename="Makefile" Content-Transfer-Encoding: base64 Q0MJPQljYwpDRkxBR1MJPQktZyAtV2FsbCAtV3BvaW50ZXItYXJpdGgKTElC Uwk9CgpTUkMJPQlidXJzdGQuYwpPQkoJPQkKUFJPRwk9CWJ1cnN0ZAoKYWxs OiQoU1JDKQoJJChDQykgJChDRkxBR1MpIC1jICouYwoJJChDQykgJChDRkxB R1MpIC1vICQoUFJPRykgJChTUkMpICQoT0JKKSAkKExJQlMpCgpjbGVhbjoK CXJtIC1mICQoUFJPRykgKi5jb3JlICoubyBldGMvKgo= ------------=_1070195191-6845-0 Content-Type: application/octet-stream; name="burstd.h" Content-Disposition: attachment; filename="burstd.h" Content-Transfer-Encoding: base64 I2luY2x1ZGUgPHN5cy90eXBlcy5oPgojaW5jbHVkZSA8c3lzL3NvY2tldC5o PgojaW5jbHVkZSA8c3lzL3N5c2N0bC5oPgojaW5jbHVkZSA8c3lzL3RpbWUu aD4KI2luY2x1ZGUgPG5ldGluZXQvaW4uaD4KI2luY2x1ZGUgPG5ldGluZXQv aW5fc3lzdG0uaD4KI2luY2x1ZGUgPG5ldGluZXQvaXAuaD4KI2luY2x1ZGUg PG1hY2hpbmUvaW5fY2tzdW0uaD4KI2luY2x1ZGUgPG5ldGluZXQvdGNwLmg+ CiNpbmNsdWRlIDxuZXRpbmV0L3VkcC5oPgojaW5jbHVkZSA8bmV0aW5ldC9p cF9pY21wLmg+CiNpbmNsdWRlIDxuZXQvaWYuaD4KI2luY2x1ZGUgPG5ldC9p Zl9kbC5oPgojaW5jbHVkZSA8bmV0L3JvdXRlLmg+CiNpbmNsdWRlIDxhcnBh L2luZXQuaD4KI2luY2x1ZGUgPGFsaWFzLmg+CiNpbmNsdWRlIDxjdHlwZS5o PgojaW5jbHVkZSA8ZXJyLmg+CiNpbmNsdWRlIDxlcnJuby5oPgojaW5jbHVk ZSA8bmV0ZGIuaD4KI2luY2x1ZGUgPHNpZ25hbC5oPgojaW5jbHVkZSA8c3Rk aW8uaD4KI2luY2x1ZGUgPHN0ZGxpYi5oPgojaW5jbHVkZSA8c3RyaW5nLmg+ CiNpbmNsdWRlIDxzeXNsb2cuaD4KI2luY2x1ZGUgPHVuaXN0ZC5oPgoKLy8g I2luY2x1ZGUgInF1ZXVlLmgiCgojZGVmaW5lIENPTkYJCSJidXJzdGQuY29u ZiIKCi8qIENvbm5lY3Rpb24gdHlwZTsgYnVyc3RpbmcgKi8KdHlwZWRlZiBz dHJ1Y3QgX2Zsb3cKewoJc3RydWN0IGluX2FkZHIgCXNyY19hZGRyOwoJc3Ry dWN0IGluX2FkZHIJZHN0X2FkZHI7Cglsb25nIGxvbmcJYnl0ZXM7Cglsb25n IGxvbmcJbGFzdDsKCWludAkJYWxpdmU7CglpbnQgCQl1c2VkOwp9Q09OTkVD VElPTjsKCnR5cGVkZWYgc3RydWN0IF9ub2RlCnsKCXN0cnVjdCBfbm9kZSAJ Km5leHQ7CglzdHJ1Y3QgX2Zsb3cJKmRhdGE7Cn1DT05OX0xJU1Q7Cgpsb25n IGxvbmcgCWxpbWl0LCByYXRlOwoKLyogU29tZSBmdW5jdGlvbnMgKi8KCi8q IHNpZ25hbC5jICovCnZvaWQgc2lnX2Fscm1faG5kKGludCBzaWcpOwovKiBp bml0LmMgKi8Kdm9pZCBzZXRfcmF0ZV9saW1pdCgpOwovKiBwYXJlbnQuYyAq LwppbnQgc2VhcmNoX2Nvbm4oQ09OTkVDVElPTiBjb25zW10sIHN0cnVjdCBp bl9hZGRyIHNhZGRyLCBzdHJ1Y3QgaW5fYWRkciBkYWRkcik7CmludCBhZGRf Y29ubihDT05ORUNUSU9OIGNvbnNbXSwgQ09OTkVDVElPTiBzX2Nvbm4pOwo= ------------=_1070195191-6845-0 Content-Type: application/octet-stream; name="burstd.c" Content-Disposition: attachment; filename="burstd.c" Content-Transfer-Encoding: base64 I2luY2x1ZGUgImJ1cnN0ZC5oIgoKaW50IG1haW4oaW50IGFyZ2MsIGNoYXIg Kiphcmd2KQp7CglpbnQgCQkJZGl2SU87CglmZF9zZXQJCQlyZWFkbWFzazsK CXN0cnVjdCBzb2NrYWRkcl9pbiAJc2E7CglpbnQgCQkJYnl0ZXMsIG9sZGJ5 dGVzLCBhZGRyU2l6ZTsKCXN0cnVjdCBpcCoJCWlwOwoJdm9pZCoJCQlidWZm OwoJCgoJYnVmZiA9ICh2b2lkICopbWFsbG9jKElQX01BWFBBQ0tFVCk7Cglt ZW1zZXQoKHZvaWQgKilidWZmLCAwLCBJUF9NQVhQQUNLRVQpOwoJCglpZigo ZGl2SU8gPSBzb2NrZXQoUEZfSU5FVCwgU09DS19SQVcsIElQUFJPVE9fRElW RVJUKSkgPT0gLTEpCgl7CgkJcGVycm9yKCJzb2NrZXQiKTsKCQlleGl0KC0x KTsKCX0KCglzYS5zaW5fZmFtaWx5ID0gQUZfSU5FVDsKCXNhLnNpbl9hZGRy LnNfYWRkciA9IElOQUREUl9BTlk7CglzYS5zaW5fcG9ydCA9IGh0b25zKDg2 NzApOwoJaWYoYmluZChkaXZJTywgKHN0cnVjdCBzb2NrYWRkciopJnNhLCBz aXplb2Yoc3RydWN0IHNvY2thZGRyKSkgPT0gLTEpCgl7CgkJcGVycm9yKCJi aW5kIik7CgkJZXhpdCgtMSk7Cgl9CgoJRkRfWkVSTygmcmVhZG1hc2spOwoJ RkRfU0VUKGRpdklPLCAmcmVhZG1hc2spOwoJCgl3aGlsZSgxKQoJewoJCWlm KHNlbGVjdChnZXRkdGFibGVzaXplKCkgKyAxLCAmcmVhZG1hc2ssIE5VTEws IE5VTEwsIE5VTEwpID09IC0xKQoJCXsKCQkJcGVycm9yKCJzZWxlY3QiKTsK CQkJZXhpdCgtMSk7CgkJfQoJCWlmKEZEX0lTU0VUKGRpdklPLCAmcmVhZG1h c2spKQoJCXsKCQkJYWRkclNpemUgPSBzaXplb2Yoc2EpOwoJCQlpZigob2xk Ynl0ZXMgPSByZWN2ZnJvbShkaXZJTywgYnVmZiwgSVBfTUFYUEFDS0VULCAw LCAoc3RydWN0IHNvY2thZGRyKikgJnNhLCAmYWRkclNpemUpKSA9PSAtMSkK CQkJewoJCQkJcGVycm9yKCJyZWN2ZnJvbSIpOwoJCQkJZXhpdCgtMSk7CgkJ CX0KCQkKCQkJaXAgPSAoc3RydWN0IGlwKikgYnVmZjsKCQkJcHJpbnRmKCIl cyAtPiAlc1xuIiwgaW5ldF9udG9hKGlwLT5pcF9zcmMpLCBpbmV0X250b2Eo aXAtPmlwX2RzdCkpOwoJCQlwcmludGYoImdldHRpbmcgJWQgYnl0ZXMsIHJl YWw6ICVkXG4iLCBvbGRieXRlcywgbnRvaHMoaXAtPmlwX2xlbikpOwoJCQlw cmludGYoInNhLnNpbl9hZGRyLnNfYWRkciA9ICVzXG4iLCBpbmV0X250b2Eo c2Euc2luX2FkZHIpKTsKCQkJCgkJCWlmKChieXRlcyA9IHNlbmR0byhkaXZJ TywgYnVmZiwgb2xkYnl0ZXMsIDAsIChzdHJ1Y3Qgc29ja2FkZHIqKSAmc2Es IGFkZHJTaXplKSkgIT0gb2xkYnl0ZXMpCgkJCXsKCQkJCXByaW50ZigiRGlm ZmVyZW50IHJlY2lldmVkL3NlbnQgdmFsdWVzOiAlZCA8LT4gJWRcbiIsIG9s ZGJ5dGVzLCBieXRlcyk7CgkJCQlwZXJyb3IoInNlbmR0byIpOwoJCQkJZXhp dCgtMSk7CgkJCX0KCQl9Cgl9CglyZXR1cm4gMDsKfQo= ------------=_1070195191-6845-0-- From owner-freebsd-net@FreeBSD.ORG Sun Nov 30 08:31:04 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A731716A4DE; Sun, 30 Nov 2003 08:31:04 -0800 (PST) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92A5743FB1; Sun, 30 Nov 2003 08:31:03 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (#6@localhost [127.0.0.1]) by whizzo.transsys.com (8.12.9p2/8.12.9) with ESMTP id hAUGUoIg060968; Sun, 30 Nov 2003 11:30:50 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200311301630.hAUGUoIg060968@whizzo.transsys.com> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: "Ivo Vachkov" X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" References: <20031130122631.7868.qmail@bsdmail.com> In-reply-to: Your message of "Sun, 30 Nov 2003 14:26:31 +0200." <20031130122631.7868.qmail@bsdmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 30 Nov 2003 11:30:50 -0500 Sender: louie@TransSys.COM cc: freebsd-ipfw@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2003 16:31:04 -0000 The problem is in your test program; you're calling inet_ntoa() twice in your printf() invocation, and the second call to inet_ntoa() overwrites the static buffer that's returned. louie From owner-freebsd-net@FreeBSD.ORG Mon Dec 1 05:54:48 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7AD816A4CE for ; Mon, 1 Dec 2003 05:54:48 -0800 (PST) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id C807944011 for ; Mon, 1 Dec 2003 05:54:47 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.9p1/8.12.3) with ESMTP id hB1Dsl2e087869; Mon, 1 Dec 2003 05:54:47 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.9p1/8.12.3/Submit) id hB1Dsljg087868; Mon, 1 Dec 2003 05:54:47 -0800 (PST) (envelope-from rizzo) Date: Mon, 1 Dec 2003 05:54:47 -0800 From: Luigi Rizzo To: net@freebsd.org Message-ID: <20031201055447.A87811@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Subject: proposed bootpd change X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2003 13:54:48 -0000 Hi, i would like to suggest the following bootpd change (after 5.2) that fixes the following problem with our bootpd. There are cases where one wants to run bootp over a non standard port, e.g. ton install new machines etc. Newer versions of etherboot support that, and there is even a couple of port numbers reserved to this purpose in /etc/services (1067 and 1068). It is easy to reconfigure bootp (if launched from inetd) to listen on port 1067 -- t just suffices to change one line in inetd.conf; however, the client service name ("bootpc") is hardwired in the bootpd code, and there is no way to override it short of changing /etc/services, which is undesirable. I can think of two ways to enable the user to configure the client port, one is to add a command-line flag to bootpd, the other one is to infer the client port number from the server port number, which is what the attached patch does. Would people be comfortable with modifying bootpd in one of these two ways ? cheers luigi Index: bootpd.c =================================================================== RCS file: /home/ncvs/src/libexec/bootpd/bootpd.c,v retrieving revision 1.13.2.3 diff -u -r1.13.2.3 bootpd.c --- bootpd.c 15 Feb 2003 05:36:01 -0000 1.13.2.3 +++ bootpd.c 28 Nov 2003 20:00:58 -0000 @@ -245,6 +245,7 @@ if (bind_addr.sin_family == AF_INET) { standalone = FALSE; bootps_port = ntohs(bind_addr.sin_port); + bootpc_port = bootps_port + 1; } else { /* Some other type of socket? */ report(LOG_ERR, "getsockname: not an INET socket"); @@ -473,7 +474,9 @@ * Get destination port number so we can reply to client */ servp = getservbyname("bootpc", "udp"); - if (servp) { + if (bootpc_port != 0) { + /* nothing to do; already set */ + } else if (servp) { bootpc_port = ntohs(servp->s_port); } else { report(LOG_ERR, From owner-freebsd-net@FreeBSD.ORG Mon Dec 1 07:30:29 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73D6816A4CE for ; Mon, 1 Dec 2003 07:30:29 -0800 (PST) Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AAAC43FEA for ; Mon, 1 Dec 2003 07:29:28 -0800 (PST) (envelope-from cgaylord@vt.edu) Received: from steiner.cc.vt.edu (IDENT:mirapoint@evil-steiner [10.1.1.14]) by lennier.cc.vt.edu (8.12.8/8.12.8) with ESMTP id hB1FTRHL433276; Mon, 1 Dec 2003 10:29:27 -0500 (EST) Received: from vt.edu (e028121.vtacs.vt.edu [63.164.28.121]) by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.7-GR) with ESMTP id CCA43516; Mon, 1 Dec 2003 10:29:25 -0500 (EST) Message-ID: <3FCB5E55.1090402@vt.edu> Date: Mon, 01 Dec 2003 10:29:25 -0500 From: Clark Gaylord User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Luigi Rizzo References: <20031201055447.A87811@xorpc.icir.org> In-Reply-To: <20031201055447.A87811@xorpc.icir.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: net@freebsd.org Subject: Re: proposed bootpd change X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2003 15:30:29 -0000 Luigi Rizzo wrote: > I can think of two ways to enable the user to configure the > client port, one is to add a command-line flag to bootpd, the > other one is to infer the client port number from the server > port number, which is what the attached patch does. > > Would people be comfortable with modifying bootpd in one > of these two ways ? I agree that this would be a desirable feature. Whether to allow a client port other than bootps_port+1 is an interesting question. I don't recall the spec prohibiting it, but one could imagine someone somewhere wanting to use 1067 and 10068. I don't know that we want to accomodate that ... seems a bit feeping to me ... but it is an interesting question. Maybe for that we say "if you are that insane, you have to edit /etc/services". Perhaps a case 'p' in "Read switches" block? Or maybe it is time to reuse 's'? How long has it been deprecated? --ckg From owner-freebsd-net@FreeBSD.ORG Mon Dec 1 11:02:30 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF86416A4CE for ; Mon, 1 Dec 2003 11:02:30 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D545A44005 for ; Mon, 1 Dec 2003 11:01:32 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id hB1J1WFY015785 for ; Mon, 1 Dec 2003 11:01:32 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id hB1J1VYK015779 for freebsd-net@freebsd.org; Mon, 1 Dec 2003 11:01:31 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 1 Dec 2003 11:01:31 -0800 (PST) Message-Id: <200312011901.hB1J1VYK015779@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2003 19:02:30 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2002/03/09] conf/35726 net Won't let me use ifconfig on the interfac 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/11/14] bin/22846 net Routed does not reflect preference of Int 1 problem total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2002/05/04] kern/37761 net process exits but socket is still ESTABLI o [2003/07/11] kern/54383 net NFS root configurations without dynamic p 2 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Dec 1 13:19:39 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8844F16A4CE for ; Mon, 1 Dec 2003 13:19:39 -0800 (PST) Received: from web80213.mail.yahoo.com (web80213.mail.yahoo.com [66.218.79.48]) by mx1.FreeBSD.org (Postfix) with SMTP id 7979D43FD7 for ; Mon, 1 Dec 2003 13:19:22 -0800 (PST) (envelope-from secureplay@sbcglobal.net) Message-ID: <20031201211922.53625.qmail@web80213.mail.yahoo.com> Received: from [161.114.1.182] by web80213.mail.yahoo.com via HTTP; Mon, 01 Dec 2003 13:19:22 PST Date: Mon, 1 Dec 2003 13:19:22 -0800 (PST) From: Val P To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: bridging... stops? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2003 21:19:39 -0000 Hi, Every now and then (maybe once a month), our freebsd firewall/bridge stops bridging. There are no errors anywhere, and no obvious triggers (for example, it was working sunday night, Monday morning it was dead). Turning off IPF or setting its rules to pass all did not fix the problem, so I am somewhat ruling out IPF as the problem. Rebooting the machine did fix the problem -- everything was working once again... but I'd rather not be fixing problems the microsoft way. :) How can I go about debugging this issue when it happens again? FYI: Proliant DL380/G2 (or G3, I forget?) with 1GB RAM. Three active NICs: copper broadcomm gigabit on bge0 (management port), and fiber broadcom gigabit on bge 2/3 (bridge endpoints). Single processor at around 2 GHz or so. Load on the server is light, no packet loss. Running FreeBSD 4.8. There were absolutely no changes (physical or software) between the time the machine was working and the time it stopped working. Whether or not there were any transient network conditions I do not know. I did find a machine on the network which was broadcasting with an IP of 127.0.0.1, and killed it.. but that was after rebooting the server and restoring bridging functionality. From owner-freebsd-net@FreeBSD.ORG Mon Dec 1 13:26:35 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A0BF16A4DC for ; Mon, 1 Dec 2003 13:26:35 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F10A43FEA for ; Mon, 1 Dec 2003 13:26:02 -0800 (PST) (envelope-from max@love2party.net) Received: from [212.227.126.207] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AQvYP-0003Nb-00 for net@freebsd.org; Mon, 01 Dec 2003 22:26:01 +0100 Received: from [217.227.155.56] (helo=fbsd52.laiers.local) (TLSv1:EDH-RSA-DES-CBC3-SHA:168) (Exim 3.35 #1) id 1AQvYP-0000Tr-00 for net@freebsd.org; Mon, 01 Dec 2003 22:26:01 +0100 References: <200312011901.hB1J1VYK015779@freefall.freebsd.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Max Laier To: net@freebsd.org Date: Mon, 01 Dec 2003 22:25:59 +0100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:e28873fbe4dbe612ce62ab869898ff08 Subject: Re: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2003 21:26:35 -0000 > o [2002/03/09] conf/35726 net Won't let me use ifconfig on the interfac Ping!? ... anyone looked at my patch? http://pf4freebsd.love2party.net/in.c.diff I can't reach the PR-creator as my provider seems black-listed :( Thanks ---- Best regards, Max mailto:max@love2party.net From owner-freebsd-net@FreeBSD.ORG Mon Dec 1 13:40:47 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BB5B16A4DD for ; Mon, 1 Dec 2003 13:40:47 -0800 (PST) Received: from web80209.mail.yahoo.com (web80209.mail.yahoo.com [66.218.79.44]) by mx1.FreeBSD.org (Postfix) with SMTP id 3202443FEA for ; Mon, 1 Dec 2003 13:40:40 -0800 (PST) (envelope-from secureplay@sbcglobal.net) Message-ID: <20031201214039.17122.qmail@web80209.mail.yahoo.com> Received: from [161.114.1.182] by web80209.mail.yahoo.com via HTTP; Mon, 01 Dec 2003 13:40:39 PST Date: Mon, 1 Dec 2003 13:40:39 -0800 (PST) From: Val P To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: freebsd bridging and failover X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2003 21:40:47 -0000 Is there a way to implement a failover in a bridge? Basically I'd like to keep two filtering bridges on the network at the same time, one primary and one backup. However, since freebsd bridging doesn't support STP, I can't do that without creating a loop. Is there something (like the vrrp implementation but for bridges) that I can use? Theoretically I can interconnect the two bridges over a serial port and write some sort of heartbeat application, but I'd rather have a solution that has already been tested. Also, my simplistic solution would cause existing connections to be disconnected during the failover. From owner-freebsd-net@FreeBSD.ORG Tue Dec 2 03:19:54 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 769C416A4CE for ; Tue, 2 Dec 2003 03:19:54 -0800 (PST) Received: from srv1.lonline.com.br (srv1.lonline.com.br [200.211.46.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1D7D43FE5 for ; Tue, 2 Dec 2003 03:19:52 -0800 (PST) (envelope-from tpeixoto@widesoft.com.br) Received: from widesoft.com.br (200-148-158-68.netconsultoria.com.br [200.148.158.68] (may be forged)) by srv1.lonline.com.br (8.12.9/8.12.2) with ESMTP id hB2BJnDU032459 for ; Tue, 2 Dec 2003 09:19:50 -0200 (BRST) Message-ID: <3FCC7555.EEBB49FA@widesoft.com.br> Date: Tue, 02 Dec 2003 09:19:49 -0200 From: "Tobias P. Santos" X-Mailer: Mozilla 4.79 [en] (Win95; U) X-Accept-Language: pt-BR,en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: IPFW issue: skip past end of rules X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2003 11:19:54 -0000 Hello, I have a gateway limiting the bandwidth of my customers. Everything is working fine, but I got some messages in the log file, see: [...] Dec 1 15:04:55 proxy /kernel: +++ ipfw: ouch!, skip past end of rules, denying packet Dec 1 15:06:17 proxy last message repeated 90 times Dec 1 15:19:24 proxy last message repeated 41 times Dec 1 15:33:58 proxy last message repeated 142 times Dec 1 15:38:57 proxy last message repeated 121 times [...] Here are my rules: 00100 344 101154 allow ip from any to any via lo0 00200 0 0 deny ip from any to 127.0.0.0/8 00300 450 18000 deny ip from 127.0.0.0/8 to any 00400 9971 1390018 pipe 1 ip from any to any MAC any 00:00:00:00:00:00 in 00500 12282 11562920 pipe 2 ip from any to any MAC 00:00:00:00:00:00 any out 00600 0 0 pipe 3 ip from any to any MAC any 11:11:11:11:11:11 in 00700 0 0 pipe 4 ip from any to any MAC 11:11:11:11:11:11 any out 00800 0 0 pipe 5 ip from any to any MAC any 22:22:22:22:22:22 in 00900 0 0 pipe 6 ip from any to any MAC 22:22:22:22:22:22 any out 01000 0 0 pipe 7 ip from any to any MAC any 33:33:33:33:33:33 in 01100 0 0 pipe 8 ip from any to any MAC 33:33:33:33:33:33 any out 01200 2336717 1482414132 divert 8668 ip from any to any via vr0 65000 9272277 5914106630 allow ip from any to any 65535 318 177373 deny ip from any to any Am I missing something? I can't find information about this issue anywhere. Thank you in advance! Best regards, Tobias. From owner-freebsd-net@FreeBSD.ORG Tue Dec 2 12:29:09 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBE3416A4CE for ; Tue, 2 Dec 2003 12:29:09 -0800 (PST) Received: from tenebras.com (laptop.tenebras.com [66.92.188.18]) by mx1.FreeBSD.org (Postfix) with SMTP id B9FDA43F93 for ; Tue, 2 Dec 2003 12:29:06 -0800 (PST) (envelope-from kudzu@tenebras.com) Received: (qmail 87455 invoked from network); 2 Dec 2003 20:29:06 -0000 Received: from sapphire.tenebras.com (HELO tenebras.com) (192.168.188.241) by laptop.tenebras.com with SMTP; 2 Dec 2003 20:29:06 -0000 Message-ID: <3FCCF60D.4020703@tenebras.com> Date: Tue, 02 Dec 2003 12:29:01 -0800 From: Michael Sierchio User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, zh-tw, zh-cn, fr, en, de-de MIME-Version: 1.0 To: Tyler Andersen References: <3FCC1FC8.3040407@tenebras.com> <1070350602.4578.223.camel@tyler.andersens.org> <3FCCE0B3.7050008@tenebras.com> In-Reply-To: <3FCCE0B3.7050008@tenebras.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Mailing List FreeBSD Network cc: imp@freebsd.org cc: soekris-tech@lists.soekris.com Subject: Re: Problems with Demarc Prism Card X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2003 20:29:10 -0000 Michael Sierchio wrote: > > [copied to soekris-tech because I know some of you are > using these cards] > > Which firmware rev are you running on the Demarc card? > mine reports > > wi0: Intersil Firmware: Primary 1.01.01, Station 1.07.04 > > which I guess is sorely out of date, SOP for shipped > product? > > The choices seem to range: 1.36, 1.49, 1.56, 1.74 The FreeBSD Handbook wireless section sez that Prism 2.5 cards should use firmware rev. 1.4.9. Is this still correct? Is 1.4.9 "better" than 1.5.6 or 1.7.4? From owner-freebsd-net@FreeBSD.ORG Tue Dec 2 15:06:55 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1324D16A4CE for ; Tue, 2 Dec 2003 15:06:55 -0800 (PST) Received: from mail.anderseninternet.com (mail.anderseninternet.com [63.78.210.8]) by mx1.FreeBSD.org (Postfix) with SMTP id 1AABC43FBD for ; Tue, 2 Dec 2003 15:06:53 -0800 (PST) (envelope-from soekrislist@anderseninternet.com) Received: (qmail 32502 invoked by uid 502); 2 Dec 2003 23:46:50 -0000 Received: from unknown (HELO tyler.andersens.org) (soekrislist@anderseninternet.com@unknown) by unknown with SMTP; 2 Dec 2003 23:46:50 -0000 From: Tyler Andersen To: Michael Sierchio In-Reply-To: <3FCCF60D.4020703@tenebras.com> References: <3FCC1FC8.3040407@tenebras.com> <1070350602.4578.223.camel@tyler.andersens.org> <3FCCE0B3.7050008@tenebras.com> <3FCCF60D.4020703@tenebras.com> Content-Type: text/plain Message-Id: <1070406316.4588.271.camel@tyler.andersens.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4-8mdk Date: Tue, 02 Dec 2003 16:05:16 -0700 Content-Transfer-Encoding: 7bit cc: Mailing List FreeBSD Network cc: imp@freebsd.org cc: soekris-tech@lists.soekris.com Subject: Re: Problems with Demarc Prism Card X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2003 23:06:55 -0000 On Tue, 2003-12-02 at 13:29, Michael Sierchio wrote: > Michael Sierchio wrote: > > > > The choices seem to range: 1.36, 1.49, 1.56, 1.74 > > The FreeBSD Handbook wireless section sez that Prism 2.5 > cards should use firmware rev. 1.4.9. Is this still > correct? Is 1.4.9 "better" than 1.5.6 or 1.7.4? I didn't use 1.7.4 because it was still beta at the time. As for 1.4.9 vs. 1.5.6, I don't know... - Tyler From owner-freebsd-net@FreeBSD.ORG Tue Dec 2 19:02:24 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E94D16A4CE for ; Tue, 2 Dec 2003 19:02:24 -0800 (PST) Received: from tenebras.com (laptop.tenebras.com [66.92.188.18]) by mx1.FreeBSD.org (Postfix) with SMTP id 2829D43FDD for ; Tue, 2 Dec 2003 19:02:23 -0800 (PST) (envelope-from kudzu@tenebras.com) Received: (qmail 91399 invoked from network); 3 Dec 2003 03:02:22 -0000 Received: from sapphire.tenebras.com (HELO tenebras.com) (192.168.188.241) by laptop.tenebras.com with SMTP; 3 Dec 2003 03:02:22 -0000 Message-ID: <3FCD523D.4070004@tenebras.com> Date: Tue, 02 Dec 2003 19:02:21 -0800 From: Michael Sierchio User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, zh-tw, zh-cn, fr, en, de-de MIME-Version: 1.0 To: Jim Thompson References: <3FCC1FC8.3040407@tenebras.com> <1070350602.4578.223.camel@tyler.andersens.org> <3FCCE0B3.7050008@tenebras.com> <3FCCF60D.4020703@tenebras.com> <1070406316.4588.271.camel@tyler.andersens.org> <16333.13031.939853.881683@zaphod.netgate.com> In-Reply-To: <16333.13031.939853.881683@zaphod.netgate.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Mailing List FreeBSD Network cc: Tyler Andersen cc: soekris-tech@lists.soekris.com Subject: Re: [Soekris] Re: Problems with Demarc Prism Card X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2003 03:02:24 -0000 Jim Thompson wrote: > use 1.4.9 unless you've got code that implments WDS (the real > 4-address mode needs at last 1.5.6) or you've got code that implements > WPA (requires 1.7.4). Thank you for that authoritative statement, super. For WPA we're waiting on addenda to the Atheros driver by Sam Leffler. I wonder if he knows he's supposed to be working on this? ;-) 1.4.9 it is... > p.s. what happened to Tony? MIA From owner-freebsd-net@FreeBSD.ORG Tue Dec 2 20:42:49 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B35FE16A4CE for ; Tue, 2 Dec 2003 20:42:49 -0800 (PST) Received: from c009.snv.cp.net (h017.c009.snv.cp.net [209.228.34.130]) by mx1.FreeBSD.org (Postfix) with SMTP id B2DAD43F85 for ; Tue, 2 Dec 2003 20:42:48 -0800 (PST) (envelope-from jdroflet@canada.com) Received: (cpmta 6959 invoked from network); 2 Dec 2003 20:42:47 -0800 Received: from 209.228.34.115 (HELO mail.canada.com.criticalpath.net) by smtp.canada.com (209.228.34.130) with SMTP; 2 Dec 2003 20:42:47 -0800 X-Sent: 3 Dec 2003 04:42:47 GMT Received: from [65.92.125.2] by mail.canada.com with HTTP; Tue, 02 Dec 2003 20:42:46 -0800 (PST) Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 To: freebsd-net@freebsd.org From: jdroflet@canada.com X-Sent-From: jdroflet@canada.com Date: Tue, 02 Dec 2003 20:42:46 -0800 (PST) X-Mailer: Web Mail 5.5.0-3_sol28 Message-Id: <20031202204247.22396.h002.c009.wm@mail.canada.com.criticalpath.net> cc: secureplay@sbcglobal.net Subject: Re: freebsd bridging and failover X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2003 04:42:49 -0000 Perhaps http://www.bsdshell.net/hut_fvrrpd.html Not tried it myself but been meaning too, probably when my main box locks up on Christmas Eve an dno failover, I will get to it.... Val P. Wrote: Is there a way to implement a failover in a bridge? Basically I'd like to keep two filtering bridges on the network at the same time, one primary and one backup. However, since freebsd bridging doesn't support STP, I can't do that without creating a loop. Is there something (like the vrrp implementation but for bridges) that I can use? Theoretically I can interconnect the two bridges over a serial port and write some sort of heartbeat application, but I'd rather have a solution that has already been tested. Also, my simplistic solution would cause existing connections to be disconnected during the failover. From owner-freebsd-net@FreeBSD.ORG Wed Dec 3 10:25:05 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C022816A4CE for ; Wed, 3 Dec 2003 10:25:05 -0800 (PST) Received: from cs78135006.pp.htv.fi (cs78135006.pp.htv.fi [62.78.135.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D6E343FAF for ; Wed, 3 Dec 2003 10:25:03 -0800 (PST) (envelope-from jau@cs78135006.pp.htv.fi) Received: from cs78135006.pp.htv.fi (localhost [127.0.0.1]) hB3IOvQ9013511 for ; Wed, 3 Dec 2003 20:24:57 +0200 (EET) Received: (from jau@localhost) by cs78135006.pp.htv.fi (8.12.10/8.12.3/Submit) id hB3INa5j013485 for freebsd-net@freebsd.org; Wed, 3 Dec 2003 20:23:36 +0200 (EET) Posted-Date: Wed, 3 Dec 2003 20:23:36 +0200 (EET) Message-Id: <200312031823.hB3INa5j013485@cs78135006.pp.htv.fi> To: freebsd-net@freebsd.org Date: Wed, 3 Dec 2003 20:23:36 +0200 (EET) From: jau@iki.fi (Jukka A. Ukkonen) Sender: jau@iki.fi Latin-Date: dies Mercurii III Decembrie a.d. MMIII Organization: Private person OS-Platform: FreeBSD Phone: +358-9-6215280 (home) Content-Conversion: prohibited X-Mailer: ELM [version 2.4 PL25+pgp] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Driver for D-Link DWL-G520+ ?? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jau@iki.fi List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2003 18:25:05 -0000 Hi! Is there anyone writing a driver for a D-Link DWL-G520+ card (apparently prism54)? The already existing driver for DWL-520+ (prism) does not work with the new 54/108 Mbps card. Probably it cannot be modified to work at all, because the Ethernet device chips might have to be different in these two cards. AFAIK someone said the older card had a very slow Ethernet part which just barely made it in the 802.11b speeds. When checking what the card reports of itself to the pci bus "pciconf -lv" gave me originally this... none0@pci0:14:0: class=0x028000 card=0x3b041186 chip=0x9066104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' class = network I made the following additions to /usr/share/misc/pci_vendors. (A couple of ATI Radeon 9200 entries were missing too.) --- /usr/share/misc/pci_vendors.orig Wed Dec 3 19:15:39 2003 +++ /usr/share/misc/pci_vendors Wed Dec 3 19:17:19 2003 @@ -290,6 +290,8 @@ 5654 215VT222 Mach 64 VT VIDEO XPRESSION 5655 Mach 64 VT3 5656 Mach64 VT4 PCI (PQFP Package) + 5941 Radeon 9200 (128MB) - Secondary + 5961 Radeon 9200 (128MB) 5964 Radeon 9200 Series 5D44 Radeon 9200 Series - Secondary 700F A3/U1 PCI to AGP Bridge @@ -976,6 +978,7 @@ 8026 TSB43AB21 1394a-2000 OHCI PHY/link-layer Controller 8027 PCI4451 OHCI-Lynx IEEE-1394 FireWire Adapter 8400 802.11b+ 22Mbps Wireless Adapter + 9066 802.11g+ 54/108 Mbps Wireless Adapter A001 TDC1570 64-Bit PCI ATM Interface A100 TDC1561 32-Bit PCI ATM Interface A102 TNETA1575 HyperSAR Plus w/PCI Host interface & UTOPIA Interface Properly recognising the device id code naturally did not hint me to any direction where to start looking for a suitable basis or starting point for a new driver or modifying an old existing one. Linux people seem to have their own Prism54 team working on this hw. They even have a team web site "Linux Driver for the 802.11g Prism GT / Prism Duette / Prism Indigo Chipsets". How close is that to a good starting point? So, if someone is already working with this, it would be nice to know. If nobody else has put any effort in this yet, any hints helping me grab and modify pieces of existing code would be great. Cheers, // jau .--- ..- -.- -.- .- .- .-.-.- ..- -.- -.- --- -. . -. / Jukka A. Ukkonen, Mawit Ltd, Finland /__ M.Sc. (sw-eng & cs) (Phone) +358-500-606-671 / Internet: Jukka.Ukkonen(a)Mawit.Com (Home) +358-9-6215-280 / Internet: ukkonen(a)nic.funet.fi v Internet: jau(a)iki.fi + + + + My opinions are mine and mine alone, not my employers. + + + + From owner-freebsd-net@FreeBSD.ORG Wed Dec 3 10:41:56 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8E8916A4CE for ; Wed, 3 Dec 2003 10:41:56 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C31843FB1 for ; Wed, 3 Dec 2003 10:41:55 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id D259365491; Wed, 3 Dec 2003 18:41:54 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 82755-02-3; Wed, 3 Dec 2003 18:41:54 +0000 (GMT) Received: from saboteur.dek.spc.org (unknown [82.147.19.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 04D496542C; Wed, 3 Dec 2003 18:41:54 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 3E8A33F; Wed, 3 Dec 2003 18:41:53 +0000 (GMT) Date: Wed, 3 Dec 2003 18:41:53 +0000 From: Bruce M Simpson To: "Jukka A. Ukkonen" Message-ID: <20031203184153.GC56046@saboteur.dek.spc.org> Mail-Followup-To: "Jukka A. Ukkonen" , freebsd-net@freebsd.org References: <200312031823.hB3INa5j013485@cs78135006.pp.htv.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200312031823.hB3INa5j013485@cs78135006.pp.htv.fi> cc: freebsd-net@freebsd.org Subject: Re: Driver for D-Link DWL-G520+ ?? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2003 18:41:56 -0000 On Wed, Dec 03, 2003 at 08:23:36PM +0200, Jukka A. Ukkonen wrote: > Is there anyone writing a driver for a D-Link DWL-G520+ card > (apparently prism54)? I know a chap (local to me) working on such a thing:- http://wlan.kewl.org/ BMS From owner-freebsd-net@FreeBSD.ORG Thu Dec 4 08:27:22 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07DAB16A4CF for ; Thu, 4 Dec 2003 08:27:22 -0800 (PST) Received: from web40302.mail.yahoo.com (web40302.mail.yahoo.com [66.218.78.81]) by mx1.FreeBSD.org (Postfix) with SMTP id 4194E43FE0 for ; Thu, 4 Dec 2003 08:27:20 -0800 (PST) (envelope-from m_evmenkin@yahoo.com) Message-ID: <20031204162719.62941.qmail@web40302.mail.yahoo.com> Received: from [24.52.242.150] by web40302.mail.yahoo.com via HTTP; Thu, 04 Dec 2003 08:27:19 PST Date: Thu, 4 Dec 2003 08:27:19 -0800 (PST) From: Maksim Yevmenkin To: questions@freebsd.org, net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: how to force packets to go out on a specific interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2003 16:27:22 -0000 Dear Hackers, is there a way to force packets to go out on a specific interface based on a source IP address? here is what we want: for testing purposes we have a FreeBSD box with two 100Mbit NICs (em0 and em1). both NICs are on the the same subnet 172.1.1.x/23. both NICs are connected to the ServerIron. the purpose of the setup is to get 200Mbit link between FreeBSD and ServerIron. ethernet trunking is NOT an option. it seems ServerIron uses algorithm that selects physical port in the trunk based on source and destination IP. IPs do not change during the test, so one NIC gets more traffic then another (we only have few clients that talk to the FreeBSD box). so what is really required is: if a process was bound to 172.1.1.1 (em0) then the packets should go out on em0 and if process was bound to 172.1.1.2 (em1) then packets should go out on em1. we tried ipfw(8) "forward" and it did not do what we want. Linux can handle this via "ip route foo bar" thing where we can specify which local source address should go out on which interface. one more thing: the solution must be compatible with dummynet(4). thanks, max __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ From owner-freebsd-net@FreeBSD.ORG Thu Dec 4 11:40:21 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25B2816A4CE for ; Thu, 4 Dec 2003 11:40:21 -0800 (PST) Received: from web40309.mail.yahoo.com (web40309.mail.yahoo.com [66.218.78.88]) by mx1.FreeBSD.org (Postfix) with SMTP id 824F643FB1 for ; Thu, 4 Dec 2003 11:40:19 -0800 (PST) (envelope-from m_evmenkin@yahoo.com) Message-ID: <20031204194019.30975.qmail@web40309.mail.yahoo.com> Received: from [66.35.239.94] by web40309.mail.yahoo.com via HTTP; Thu, 04 Dec 2003 11:40:19 PST Date: Thu, 4 Dec 2003 11:40:19 -0800 (PST) From: Maksim Yevmenkin To: current@freebsd.org, net@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-1581803876-1070566819=:29876" cc: re@freebsd.org Subject: PATCH: dummynet(4) panic X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2003 19:40:21 -0000 --0-1581803876-1070566819=:29876 Content-Type: text/plain; charset=us-ascii Content-Id: Content-Disposition: inline Dear Hackers, could we please commit the attached patch. it fixes the dummynet(4) panic when you do ipfw(8) flush with configured dummynet(4) rules. thanks, max p.s. if re@ will give a green ligth can someone please commit it? i will not be able to do it until evening. __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ --0-1581803876-1070566819=:29876 Content-Type: application/octet-stream; name="ip_dummynet.c.diff" Content-Transfer-Encoding: base64 Content-Description: ip_dummynet.c.diff Content-Disposition: attachment; filename="ip_dummynet.c.diff" LS0tIGlwX2R1bW15bmV0LmMub3JpZwlUaHUgRGVjICA0IDE5OjAxOjMwIDIw MDMKKysrIGlwX2R1bW15bmV0LmMJVGh1IERlYyAgNCAxOTowMjozMCAyMDAz CkBAIC0xMzg2LDcgKzEzODYsNiBAQAogICAgIGhlYXBfZnJlZSgmcmVhZHlf aGVhcCk7CiAgICAgaGVhcF9mcmVlKCZ3ZnFfcmVhZHlfaGVhcCk7CiAgICAg aGVhcF9mcmVlKCZleHRyYWN0X2hlYXApOwotICAgIERVTU1ZTkVUX1VOTE9D SygpOwogCiAgICAgLyoKICAgICAgKiBOb3cgcHVyZ2UgYWxsIHF1ZXVlZCBw a3RzIGFuZCBkZWxldGUgYWxsIHBpcGVzCkBAIC0xNDAzLDYgKzE0MDIsNyBA QAogCXAgPSBwLT5uZXh0IDsKIAlmcmVlKGN1cnJfcCwgTV9EVU1NWU5FVCk7 CiAgICAgfQorICAgIERVTU1ZTkVUX1VOTE9DSygpOwogfQogCiAK --0-1581803876-1070566819=:29876-- From owner-freebsd-net@FreeBSD.ORG Thu Dec 4 12:00:35 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80A1016A4D5 for ; Thu, 4 Dec 2003 12:00:35 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD0F243FBD for ; Thu, 4 Dec 2003 12:00:32 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 29444 invoked from network); 4 Dec 2003 18:58:31 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 4 Dec 2003 18:58:31 -0000 Message-ID: <3FCF925E.1EAB8E91@freebsd.org> Date: Thu, 04 Dec 2003 21:00:30 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Maksim Yevmenkin References: <20031204194019.30975.qmail@web40309.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: re@freebsd.org cc: current@freebsd.org cc: net@freebsd.org Subject: Re: PATCH: dummynet(4) panic X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2003 20:00:35 -0000 Maksim Yevmenkin wrote: > > Dear Hackers, > > could we please commit the attached patch. it fixes the dummynet(4) panic > when you do ipfw(8) flush with configured dummynet(4) rules. Your patch looks good. > p.s. if re@ will give a green ligth can someone please commit it? > i will not be able to do it until evening. I could do it. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Dec 4 13:41:53 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2480416A4CE; Thu, 4 Dec 2003 13:41:53 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 226B243FD7; Thu, 4 Dec 2003 13:41:50 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc12) with ESMTP id <2003120421414901400c6l5oe>; Thu, 4 Dec 2003 21:41:49 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA44790; Thu, 4 Dec 2003 13:41:47 -0800 (PST) Date: Thu, 4 Dec 2003 13:41:45 -0800 (PST) From: Julian Elischer To: Maksim Yevmenkin In-Reply-To: <20031204162719.62941.qmail@web40302.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: questions@freebsd.org cc: net@freebsd.org Subject: Re: how to force packets to go out on a specific interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2003 21:41:53 -0000 if you use ipfw then the 'fwd' command CAN be used to force this if you set up the routes correctly.. you send the packets to addresses that can only reached through the different interfaces according to the routes that you have installed.. On Thu, 4 Dec 2003, Maksim Yevmenkin wrote: > Dear Hackers, > > is there a way to force packets to go out on a specific interface > based on a source IP address? > > here is what we want: for testing purposes we have a FreeBSD box with > two 100Mbit NICs (em0 and em1). both NICs are on the the same subnet > 172.1.1.x/23. both NICs are connected to the ServerIron. the purpose > of the setup is to get 200Mbit link between FreeBSD and ServerIron. > > ethernet trunking is NOT an option. it seems ServerIron uses algorithm > that selects physical port in the trunk based on source and destination > IP. IPs do not change during the test, so one NIC gets more traffic then > another (we only have few clients that talk to the FreeBSD box). > > so what is really required is: if a process was bound to 172.1.1.1 (em0) > then the packets should go out on em0 and if process was bound to > 172.1.1.2 (em1) then packets should go out on em1. we tried ipfw(8) > "forward" and it did not do what we want. Linux can handle this via > "ip route foo bar" thing where we can specify which local source address > should go out on which interface. > > one more thing: the solution must be compatible with dummynet(4). > > thanks, > max > > __________________________________ > Do you Yahoo!? > Free Pop-Up Blocker - Get it now > http://companion.yahoo.com/ > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Thu Dec 4 19:07:22 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCF4F16A4CE for ; Thu, 4 Dec 2003 19:07:22 -0800 (PST) Received: from smtp800.mail.ukl.yahoo.com (smtp800.mail.ukl.yahoo.com [217.12.12.142]) by mx1.FreeBSD.org (Postfix) with SMTP id E76CF43FCB for ; Thu, 4 Dec 2003 19:07:20 -0800 (PST) (envelope-from secureplay@sbcglobal.net) Received: from adsl-67-65-160-144.dsl.hstntx.swbell.net (HELO darkcitylt) (secureplay@sbcglobal.net@67.65.160.144 with login) by smtp1.bt.mail.vip.ukl.yahoo.com with SMTP; 5 Dec 2003 03:07:17 -0000 From: "Val P" To: Date: Thu, 4 Dec 2003 21:06:53 -0600 Organization: Secureplay Consulting Message-ID: <003d01c3badc$d83ca390$d20a0a0a@jvstice.ops.mil> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: <20031204200110.B7F3916A4EB@hub.freebsd.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: IP address conflict (transparent bridge) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: secureplay@sbcglobal.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2003 03:07:22 -0000 I have a bridge configured as follows: Bge0 - management interface, ip a.b.c.d Bge1 - down (not used) Bge2 - "inside" bridge leg, no ip, layer-2 only Bge3 - "outside" bridge leg, no ip, layer-2 only Now, I am seeing some weird behavior. If I try to do any type of net = access over bge0, I get console messages such as (paraphrasing, since I don't = have it in front of me): /kernel: arp: 1.2.3.4.5.6 is using my ip address a.b.c.d! /kernel: arp: 7.8.9.10.11.12 is using my ip address a.b.c.d! 1.2.3.4.5.6 is the mac of the bge0 interface 7.8.9.10.11.12 is the mac of the bge3 interface So in other words, why am I getting a conflict between the management interface and a leg of the bridge? Is there some weird loop going on? = There is no bridging loop happening, this is the only bridge on the subnet and connects two datacenter switches (it's a firewall). The router is = upstream on the bge3 side of the bridge. All these interfaces appear to be working fine, the machine is bridging = and I can use the management interface with no apparent problems. If I ping continuously, I get those two messages with every ping. Same for telnet, etc. These messages only appeared for the past week, after the machine = was brought down and back up.=20 This is freebsd 4.8. stock ipf is in use, ipfw is not in use. Disabling = ipf makes no difference. Any input would be appreciated.=20 From owner-freebsd-net@FreeBSD.ORG Fri Dec 5 00:16:36 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCBEC16A4CE for ; Fri, 5 Dec 2003 00:16:36 -0800 (PST) Received: from nbh-gw.newchem.ru (novbytchem-2.ip.PeterStar.net [81.3.149.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6FF043FDF for ; Fri, 5 Dec 2003 00:16:34 -0800 (PST) (envelope-from a@newchem.ru) Received: from 127.0.0.1 ([192.168.204.4]) by nbh-gw.newchem.ru (8.12.9/8.12.7) with ESMTP id hB58GXOj002877 for ; Fri, 5 Dec 2003 11:16:33 +0300 (MSK) (envelope-from a@newchem.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Date: Fri, 5 Dec 2003 11:16:29 +0300 From: a person X-Mailer: The Bat! (v1.62q) Personal X-Priority: 3 (Normal) Message-ID: <282738540.20031205111629@newchem.ru> To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: NFS: mountd binding to port numbers more then 1024 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: a person List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2003 08:16:36 -0000 Hello freebsd-net, How could I force to work the subject, if it's ever possibly? What does rc.conf's parameter "nfs_reserved_port_only" serves for? -- Best regards, Illia Baidakov From owner-freebsd-net@FreeBSD.ORG Fri Dec 5 13:17:13 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73EEE16A4CE for ; Fri, 5 Dec 2003 13:17:13 -0800 (PST) Received: from smtp-out7.blueyonder.co.uk (smtp-out7.blueyonder.co.uk [195.188.213.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8228743FE9 for ; Fri, 5 Dec 2003 13:17:11 -0800 (PST) (envelope-from jamespi@blueyonder.co.uk) Received: from frodo ([82.34.180.229]) by smtp-out7.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.5600); Fri, 5 Dec 2003 21:17:17 +0000 From: "James Pickett" To: "FreeBSD Mailing list" Date: Fri, 5 Dec 2003 21:25:33 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-OriginalArrivalTime: 05 Dec 2003 21:17:17.0996 (UTC) FILETIME=[2998E6C0:01C3BB75] Subject: X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jamespi@blueyonder.co.uk List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2003 21:17:13 -0000 Hello, I have recently installed a RealTek 8029 NIC into my FreeBSD machine but am unable to get it to work. The kernel finds and loads it at boot time, and ifconfig displays it. But I get no response when I ping it. What I did notice though, when checking my syslog it displays the NIC and IRQ setting, but doesnt display the Ethernet MAC address. Could this mean the card is faulty, or have I done something wrong? * PS The card is second hand and I dont know if it does work or not. Also I have not tested it elsewhere. Thanks --- Begin signature --- :: James Pickett :: james@root.org.za :: www.root.org.za/jp :: "The only way to discover the limits of the possible is to go beyond them into the impossible." -- Arthur C. Clarke, 'Technology and the Future' --- End signature ---