From owner-freebsd-net Sun Feb 24 0:47:31 2002 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 610AD37B402 for ; Sun, 24 Feb 2002 00:47:20 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g1O8l3b32480; Sun, 24 Feb 2002 10:47:03 +0200 (EET) (envelope-from ru) Date: Sun, 24 Feb 2002 10:47:02 +0200 From: Ruslan Ermilov To: cjclark@alum.mit.edu Cc: net@FreeBSD.ORG Subject: Re: TCP Connections to a Broadcast Address Message-ID: <20020224084702.GB31243@sunbay.com> References: <20020222022626.A83807@blossom.cjclark.org> <20020223115033.GB47437@sunbay.com> <20020223042828.E16048@blossom.cjclark.org> <20020223124535.GB52291@sunbay.com> <20020223072520.J16048@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020223072520.J16048@blossom.cjclark.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, Feb 23, 2002 at 07:25:20AM -0800, Crist J. Clark wrote: > On Sat, Feb 23, 2002 at 02:45:35PM +0200, Ruslan Ermilov wrote: > [snip] > > > Router B: if0 (192.168.1.1/24) and if1 (192.168.4.1/24) > > Router A: if0 (192.168.1.2/24) > > > > On router A: route add -net 192.168.4 192.168.1.1, telnet 192.168.4.255. > > > > Or even simpler: > > > > Router: if0 (192.168.1.1/24 and 192.168.100.1/24) > > Host: if0 (192.168.1.2, default gateway 192.168.1.1) > > Did 192.168.4.1/24 just become 192.168.100.1/24? > Yes, these were two different examples. > > On host: > > > > $ ping 192.168.100.255 > > PING 192.168.100.255 (192.168.100.255): 56 data bytes > > 64 bytes from 192.168.100.1: icmp_seq=0 ttl=64 time=0.245 ms > > 64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.207 ms > > 64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=0.207 ms > > ^C > > --- 192.168.100.255 ping statistics --- > > 3 packets transmitted, 3 packets received, 0% packet loss > > round-trip min/avg/max/stddev = 0.207/0.220/0.245/0.018 ms > > $ telnet 192.168.100.255 25 > > Trying 192.168.100.255... > > Connected to 192.168.100.255. > > Escape character is '^]'. > > 220 my.router.local.net ESMTP Sendmail 8.11.6/8.11.2; Sat, 23 Feb 2002 14:39:21 +0200 (EET) > > I can't reproduce this. I was only ever able to connect to the > broadcast on the local interface. > > On victim "router (192.168.64.50):" > > $ netstat -rn -f inet > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 192.168.64.254 UGSc 14 1768 dc0 > 127.0.0.1 127.0.0.1 UH 1 137708 lo0 > 172.16 link#3 UC 3 0 ep0 > 172.16.0.1 0:20:af:17:f:11 UHLW 0 2 lo0 > 192.168.64 link#1 UC 6 0 dc0 > 192.168.64.50 0:4:5a:40:d9:e5 UHLW 11 5310274 lo0 > 192.168.64.60 0:c0:f0:5a:6c:a UHLW 4 11416791 dc0 514 > > On attacker "host (192.168.64.60):" > > $ netstat -rn -f > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 192.168.64.254 UGSc 1 0 dc0 > 127 127.0.0.1 UGSc 0 0 lo0 > 127.0.0.1 127.0.0.1 UH 1 1776 lo0 > 172.16 192.168.64.50 UGSc 1 4 dc0 > 192.168.64 link#1 UC 3 0 dc0 > 192.168.64.50 0:4:5a:40:d9:e5 UHLW 6 1318188 dc0 1003 > > Now on "host," > > $ ping 172.16.0.1 > PING 172.16.0.1 (172.16.0.1): 56 data bytes > 64 bytes from 172.16.0.1: icmp_seq=0 ttl=64 time=0.518 ms > 64 bytes from 172.16.0.1: icmp_seq=1 ttl=64 time=0.541 ms > ^C > --- 172.16.0.1 ping statistics --- > 2 packets transmitted, 2 packets received, 0% packet loss > round-trip min/avg/max/stddev = 0.518/0.530/0.541/0.011 ms > > This works fine as expected with the weak-ES model. But for me, > > $ ping 172.16.255.255 > PING 172.16.255.255 (172.16.255.255): 56 data bytes > ^C > --- 172.16.255.255 ping statistics --- > 4 packets transmitted, 0 packets received, 100% packet loss > $ telnet 172.16.255.255 > Trying 172.16.255.255... > telnet: connect to address 172.16.255.255: Operation timed out > telnet: Unable to connect to remote host > > I can't reach the broadcast on the other interface. The "router" is > FreeBSD 4.5-RELEASE without any patches. > > I'm not sure what I might be doing wrong. > > If you are correct, and you can cross interfaces, this is a much > bigger problem. I didn't mention it in your first mail, but the > in_broadcast() function as used in the patch you sent is different > than the current implementation. in_broadacast() currently takes an > address and an interface. If you are correct, we'd have to loop > through the interface list... which makes this uglier. > No, I can't cross interfaces, /* Check for broadcast addresses. */ in ip_input() doesn't allow this. I'm talking about a different scenario here, multiple IP networks per interface: host# netstat -rn -finet | grep -w default default 192.168.4.65 UGSc 4 387 rl0 gateway# ifconfig fxp0 inet fxp0: flags=8843 mtu 1500 inet 192.168.4.65 netmask 0xffffff00 broadcast 192.168.4.255 inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.100.255 host# telnet 192.168.100.255 25 Trying 192.168.100.255... Connected to 192.168.100.255. Escape character is '^]'. Cheers, -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 24 0:50: 1 2002 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 9000537B404; Sun, 24 Feb 2002 00:49:35 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g1O8nLD32605; Sun, 24 Feb 2002 10:49:21 +0200 (EET) (envelope-from ru) Date: Sun, 24 Feb 2002 10:49:21 +0200 From: Ruslan Ermilov To: Maxim Konovalov Cc: "Crist J. Clark" , net@FreeBSD.ORG, Robert Watson Subject: Re: TCP Connections to a Broadcast Address Message-ID: <20020224084921.GC31243@sunbay.com> References: <20020223042828.E16048@blossom.cjclark.org> <20020223154842.G31228-100000@news1.macomnet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020223154842.G31228-100000@news1.macomnet.ru> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, Feb 23, 2002 at 03:49:55PM +0300, Maxim Konovalov wrote: > On 04:28-0800, Feb 23, 2002, Crist J. Clark wrote: > > > On Sat, Feb 23, 2002 at 01:50:33PM +0200, Ruslan Ermilov wrote: > > [snip] > > > > > Nice catch! > > > > Igor M Podlesny , PR misc/35022, caught it. I just > > analyzed it. > > Isn't kern/19722 about the same bug? > Yes. -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 24 10:18:45 2002 Delivered-To: freebsd-net@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 676C637B404 for ; Sun, 24 Feb 2002 10:18:43 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g1OIIen36375; Sun, 24 Feb 2002 10:18:40 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g1OIIdq43736; Sun, 24 Feb 2002 10:18:39 -0800 (PST) (envelope-from jdp) Date: Sun, 24 Feb 2002 10:18:39 -0800 (PST) Message-Id: <200202241818.g1OIIdq43736@vashon.polstra.com> To: net@freebsd.org From: John Polstra Cc: ras@e-gerbil.net Subject: Re: incorrect checksums with xl? In-Reply-To: <20020222205853.GC413@overlord.e-gerbil.net> References: <3C7547E0.8050805@isi.edu> <3C7682BF.99A66C3B@iprg.nokia.com> <200202221743.g1MHhwh38542@vashon.polstra.com> <20020222205853.GC413@overlord.e-gerbil.net> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In article <20020222205853.GC413@overlord.e-gerbil.net>, Richard A Steenbergen wrote: > On Fri, Feb 22, 2002 at 09:43:58AM -0800, John Polstra wrote: > > Remember, bpf is used by many things besides tcpdump. Adding these > > flags would require extending the bpf API. They couldn't be added for > > the default case, because that would break compatibility with other > > applications. They'd have to be enabled specifically, by means of a > > new ioctl. > > You could always just add a flags field to struct bpf_hdr, and hope noone > is stupid enough to hardcode the size. That would break binary compatibility. Think about third-party applications, not available in source form, which people paid money for. They would suddenly stop working. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 24 10:27:51 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 5499837B402; Sun, 24 Feb 2002 10:27:48 -0800 (PST) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020224182747.YVKE1147.rwcrmhc52.attbi.com@blossom.cjclark.org>; Sun, 24 Feb 2002 18:27:47 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g1OIRkb33740; Sun, 24 Feb 2002 10:27:46 -0800 (PST) (envelope-from cjc) Date: Sun, 24 Feb 2002 10:27:46 -0800 From: "Crist J. Clark" To: Ruslan Ermilov Cc: Maxim Konovalov , net@FreeBSD.ORG, Robert Watson Subject: Re: TCP Connections to a Broadcast Address Message-ID: <20020224102746.Q16048@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <20020223042828.E16048@blossom.cjclark.org> <20020223154842.G31228-100000@news1.macomnet.ru> <20020224084921.GC31243@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020224084921.GC31243@sunbay.com>; from ru@FreeBSD.ORG on Sun, Feb 24, 2002 at 10:49:21AM +0200 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Feb 24, 2002 at 10:49:21AM +0200, Ruslan Ermilov wrote: > On Sat, Feb 23, 2002 at 03:49:55PM +0300, Maxim Konovalov wrote: > > On 04:28-0800, Feb 23, 2002, Crist J. Clark wrote: > > > > > On Sat, Feb 23, 2002 at 01:50:33PM +0200, Ruslan Ermilov wrote: > > > [snip] > > > > > > > Nice catch! > > > > > > Igor M Podlesny , PR misc/35022, caught it. I just > > > analyzed it. > > > > Isn't kern/19722 about the same bug? > > > Yes. I think there are some different issues raised in this PR too. Like the discussion in another part of this thread, PR 19722 states that you can reach the broadcast address of interfaces other than the one to which the attacker is directly attached. I have not been able to reproduce this. I think it was fixed by revision 1.181 of ip_input.c. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 24 10:36:20 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 411B137B402; Sun, 24 Feb 2002 10:36:17 -0800 (PST) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020224183616.RXKE2626.rwcrmhc51.attbi.com@blossom.cjclark.org>; Sun, 24 Feb 2002 18:36:16 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g1OIaG433766; Sun, 24 Feb 2002 10:36:16 -0800 (PST) (envelope-from cjc) Date: Sun, 24 Feb 2002 10:36:16 -0800 From: "Crist J. Clark" To: Ruslan Ermilov Cc: net@FreeBSD.ORG Subject: Re: TCP Connections to a Broadcast Address Message-ID: <20020224103616.S16048@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <20020222022626.A83807@blossom.cjclark.org> <20020223115033.GB47437@sunbay.com> <20020223042828.E16048@blossom.cjclark.org> <20020223124535.GB52291@sunbay.com> <20020223072520.J16048@blossom.cjclark.org> <20020224084702.GB31243@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020224084702.GB31243@sunbay.com>; from ru@FreeBSD.ORG on Sun, Feb 24, 2002 at 10:47:02AM +0200 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Feb 24, 2002 at 10:47:02AM +0200, Ruslan Ermilov wrote: > On Sat, Feb 23, 2002 at 07:25:20AM -0800, Crist J. Clark wrote: [snip] > > If you are correct, and you can cross interfaces, this is a much > > bigger problem. I didn't mention it in your first mail, but the > > in_broadcast() function as used in the patch you sent is different > > than the current implementation. in_broadacast() currently takes an > > address and an interface. If you are correct, we'd have to loop > > through the interface list... which makes this uglier. > > > No, I can't cross interfaces, /* Check for broadcast addresses. */ > in ip_input() doesn't allow this. Exactly, I found that code early on. I had considered possibly dropping all TCP right then and there, but decided that was not the right place to do it. > I'm talking about a different > scenario here, multiple IP networks per interface: > > host# netstat -rn -finet | grep -w default > default 192.168.4.65 UGSc 4 387 rl0 > > gateway# ifconfig fxp0 inet > fxp0: flags=8843 mtu 1500 > inet 192.168.4.65 netmask 0xffffff00 broadcast 192.168.4.255 > inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.100.255 Right. But to me, that seems at best suboptimal and at worst slightly misconfigured. A host shouldn't be routing traffic over one interface. This is the kind of route that will generate ICMP redirects. But none of this really has anything to do with the problem. I am going to test the final revision I made after reviewing the patches you presented earlier in this thread and then make the commit. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 24 12:27: 0 2002 Delivered-To: freebsd-net@freebsd.org Received: from tomts11-srv.bellnexxia.net (tomts11.bellnexxia.net [209.226.175.55]) by hub.freebsd.org (Postfix) with ESMTP id B68DC37B404 for ; Sun, 24 Feb 2002 12:26:53 -0800 (PST) Received: from xena.gsicomp.on.ca ([199.243.128.121]) by tomts11-srv.bellnexxia.net (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP id <20020224202652.QSHT27257.tomts11-srv.bellnexxia.net@xena.gsicomp.on.ca>; Sun, 24 Feb 2002 15:26:52 -0500 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.1) with SMTP id g1OKFIi33927; Sun, 24 Feb 2002 15:15:23 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <00ad01c1bd71$98237820$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Greg Black" Cc: References: Subject: Re: ppp -nat fails with adsl, but ok with modem Date: Sun, 24 Feb 2002 15:26:46 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org What version of FreeBSD are you using? The ppp included in early 4.x distributions doesn't have the TCP MSS fixup code that is required to make things work properly with a PPPoE connection, and cause the kinds of symptoms that you describe. Matt ----- Original Message ----- From: "Greg Black" To: Sent: Friday, February 22, 2002 10:39 PM Subject: ppp -nat fails with adsl, but ok with modem > I've had ppp -nat working just fine over a normal modem link, > but it is not working at all well on my ADSL link to the same > provider. > > To quantify "not working at all well", although I can ping and > traceroute ok from the hosts on my LAN, HTTP and FTP traffic is > so slow and bursty as to be useless. Clicking on a link with > Netscape will see short bursts of data with long periods (of a > minute or more) where it says "stalled". > > Clicking on from > my gateway host gets the page in an eye-blink, but on the NAT > hosts, it will take 40 seconds to load the top banner and the > "FreeBSD GNOME News Flash" heading, then another delay of 40 or > so seconds before the rest of the page will be displayed. Even > then, Netscape thinks it has stalled and keeps waiting for the > last bit of data. > > With FTP, a small transfer (e.g., a directory listing of / on > ftp.freebsd.org) will complete normally; but something slightly > larger (e.g., a listing of /pub/FreeBSD on the same server), > will produce: > > ftp> cd /pub/FreeBSD > 250 CWD command successful. > ftp> dir > 200 PORT command successful. > 150 Opening ASCII mode data connection for '/bin/ls'. > ftp: netin: Connection reset by peer > 226 Transfer complete. > ftp> quit > 421 Timeout (60 seconds): closing control connection. > > If I do the same things from the host that is connected to the > modem(s), everything works fine, for both types of connections. > > I'm finding this very frustrating, and I'm wondering if there's > something weird about PPPoE with the ADSL link that needs some > special magic in order for things to work properly. > > If anybody can point me at the truth, I'd be most grateful. > > Alternatively, if anybody can suggest steps I could take to > identify the nature of the problem, that would also be most > welcome. > > Greg Black > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 24 12:59:14 2002 Delivered-To: freebsd-net@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.143.238.93]) by hub.freebsd.org (Postfix) with SMTP id 5094237B400 for ; Sun, 24 Feb 2002 12:59:09 -0800 (PST) Received: (qmail 44680 invoked by uid 1001); 25 Feb 2002 06:59:07 +1000 X-Posted-By: GJB-Post 2.23 27-Nov-2001 X-Operating-System: FreeBSD 4.2-RELEASE i386 X-Uptime: 46 days, 13:20 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-GPG-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-PGP-Public-Keys: http://www.gbch.net/keys.html Message-Id: Date: Mon, 25 Feb 2002 06:59:07 +1000 From: Greg Black To: "Matthew Emmerton" Cc: freebsd-net@freebsd.org Subject: Re: ppp -nat fails with adsl, but ok with modem References: <00ad01c1bd71$98237820$1200a8c0@gsicomp.on.ca> In-reply-to: <00ad01c1bd71$98237820$1200a8c0@gsicomp.on.ca> of Sun, 24 Feb 2002 15:26:46 EST Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Matthew Emmerton" wrote: | From: "Greg Black" | To: | Sent: Friday, February 22, 2002 10:39 PM | Subject: ppp -nat fails with adsl, but ok with modem | | > I've had ppp -nat working just fine over a normal modem link, | > but it is not working at all well on my ADSL link to the same | > provider. | > | > To quantify "not working at all well", although I can ping and | > traceroute ok from the hosts on my LAN, HTTP and FTP traffic is | > so slow and bursty as to be useless. Clicking on a link with | > Netscape will see short bursts of data with long periods (of a | > minute or more) where it says "stalled". | > | > Clicking on from | > my gateway host gets the page in an eye-blink, but on the NAT | > hosts, it will take 40 seconds to load the top banner and the | > "FreeBSD GNOME News Flash" heading, then another delay of 40 or | > so seconds before the rest of the page will be displayed. Even | > then, Netscape thinks it has stalled and keeps waiting for the | > last bit of data. | > | > With FTP, a small transfer (e.g., a directory listing of / on | > ftp.freebsd.org) will complete normally; but something slightly | > larger (e.g., a listing of /pub/FreeBSD on the same server), | > will produce: | > | > ftp> cd /pub/FreeBSD | > 250 CWD command successful. | > ftp> dir | > 200 PORT command successful. | > 150 Opening ASCII mode data connection for '/bin/ls'. | > ftp: netin: Connection reset by peer | > 226 Transfer complete. | > ftp> quit | > 421 Timeout (60 seconds): closing control connection. | > | > If I do the same things from the host that is connected to the | > modem(s), everything works fine, for both types of connections. | > | > I'm finding this very frustrating, and I'm wondering if there's | > something weird about PPPoE with the ADSL link that needs some | > special magic in order for things to work properly. | > | > If anybody can point me at the truth, I'd be most grateful. | > | > Alternatively, if anybody can suggest steps I could take to | > identify the nature of the problem, that would also be most | > welcome. | > | > Greg Black | > | > To Unsubscribe: send mail to majordomo@FreeBSD.org | > with "unsubscribe freebsd-net" in the body of the message | | What version of FreeBSD are you using? The ppp included in early 4.x | distributions doesn't have the TCP MSS fixup code that is required to make | things work properly with a PPPoE connection, and cause the kinds of | symptoms that you describe. The NAT box is running 4.2-RELEASE -- is that a problem? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 24 14:52:31 2002 Delivered-To: freebsd-net@freebsd.org Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by hub.freebsd.org (Postfix) with ESMTP id 0625B37B400 for ; Sun, 24 Feb 2002 14:52:16 -0800 (PST) Received: from myrealbox.com aangel@smtp-send.myrealbox.com [12.245.232.58] by smtp-send.myrealbox.com with Novell NIMS $Revision: 2.88 $ on Novell NetWare; Sun, 24 Feb 2002 15:52:16 -0700 Message-ID: <3C796E9C.1010306@myrealbox.com> Date: Sun, 24 Feb 2002 17:52:12 -0500 From: Aaron Angel User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.8) Gecko/20020204 X-Accept-Language: en-us MIME-Version: 1.0 To: net@freebsd.org Subject: prefix command outdated? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Out of curiousity, why is the prefix command being phased out? And is there a way to assign an address based on a prefix and EU64 address to a device using ifconfig, or do I have to write a script? I haven't found anything in the man pages regarding this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 24 15:22:42 2002 Delivered-To: freebsd-net@freebsd.org Received: from tomts6-srv.bellnexxia.net (tomts6.bellnexxia.net [209.226.175.26]) by hub.freebsd.org (Postfix) with ESMTP id E304A37B400 for ; Sun, 24 Feb 2002 15:22:35 -0800 (PST) Received: from xena.gsicomp.on.ca ([199.243.128.121]) by tomts6-srv.bellnexxia.net (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP id <20020224232233.YZIQ477.tomts6-srv.bellnexxia.net@xena.gsicomp.on.ca>; Sun, 24 Feb 2002 18:22:33 -0500 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.1) with SMTP id g1ONB3i34351; Sun, 24 Feb 2002 18:11:04 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <001e01c1bd8a$22f347b0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Greg Black" Cc: References: <00ad01c1bd71$98237820$1200a8c0@gsicomp.on.ca> Subject: Re: ppp -nat fails with adsl, but ok with modem Date: Sun, 24 Feb 2002 18:22:27 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > "Matthew Emmerton" wrote: > > | From: "Greg Black" > | To: > | Sent: Friday, February 22, 2002 10:39 PM > | Subject: ppp -nat fails with adsl, but ok with modem > | > | > I've had ppp -nat working just fine over a normal modem link, > | > but it is not working at all well on my ADSL link to the same > | > provider. > | > > | > To quantify "not working at all well", although I can ping and > | > traceroute ok from the hosts on my LAN, HTTP and FTP traffic is > | > so slow and bursty as to be useless. Clicking on a link with > | > Netscape will see short bursts of data with long periods (of a > | > minute or more) where it says "stalled". > | > > | > Clicking on from > | > my gateway host gets the page in an eye-blink, but on the NAT > | > hosts, it will take 40 seconds to load the top banner and the > | > "FreeBSD GNOME News Flash" heading, then another delay of 40 or > | > so seconds before the rest of the page will be displayed. Even > | > then, Netscape thinks it has stalled and keeps waiting for the > | > last bit of data. > | > > | > With FTP, a small transfer (e.g., a directory listing of / on > | > ftp.freebsd.org) will complete normally; but something slightly > | > larger (e.g., a listing of /pub/FreeBSD on the same server), > | > will produce: > | > > | > ftp> cd /pub/FreeBSD > | > 250 CWD command successful. > | > ftp> dir > | > 200 PORT command successful. > | > 150 Opening ASCII mode data connection for '/bin/ls'. > | > ftp: netin: Connection reset by peer > | > 226 Transfer complete. > | > ftp> quit > | > 421 Timeout (60 seconds): closing control connection. > | > > | > If I do the same things from the host that is connected to the > | > modem(s), everything works fine, for both types of connections. > | > > | > I'm finding this very frustrating, and I'm wondering if there's > | > something weird about PPPoE with the ADSL link that needs some > | > special magic in order for things to work properly. > | > > | > If anybody can point me at the truth, I'd be most grateful. > | > > | > Alternatively, if anybody can suggest steps I could take to > | > identify the nature of the problem, that would also be most > | > welcome. > | > > | > Greg Black > | > > | > To Unsubscribe: send mail to majordomo@FreeBSD.org > | > with "unsubscribe freebsd-net" in the body of the message > | > | What version of FreeBSD are you using? The ppp included in early 4.x > | distributions doesn't have the TCP MSS fixup code that is required to make > | things work properly with a PPPoE connection, and cause the kinds of > | symptoms that you describe. > > The NAT box is running 4.2-RELEASE -- is that a problem? Yes. This problem was first fixed in 4.2-STABLE. There are two safe ways to fix this: - upgrade to a newer -RELEASE or -STABLE - run the tcpmssd program (which is in the ports collection - /usr/ports/net/tcpmssd) -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 24 16:20:13 2002 Delivered-To: freebsd-net@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.143.238.93]) by hub.freebsd.org (Postfix) with SMTP id 63E7737B400 for ; Sun, 24 Feb 2002 16:20:06 -0800 (PST) Received: (qmail 52248 invoked by uid 1001); 25 Feb 2002 10:20:05 +1000 X-Posted-By: GJB-Post 2.23 27-Nov-2001 X-Operating-System: FreeBSD 4.2-RELEASE i386 X-Uptime: 46 days, 16:41 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-GPG-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-PGP-Public-Keys: http://www.gbch.net/keys.html Message-Id: Date: Mon, 25 Feb 2002 10:20:05 +1000 From: Greg Black To: "Matthew Emmerton" Cc: freebsd-net@freebsd.org Subject: Re: ppp -nat fails with adsl, but ok with modem References: <00ad01c1bd71$98237820$1200a8c0@gsicomp.on.ca> <001e01c1bd8a$22f347b0$1200a8c0@gsicomp.on.ca> In-reply-to: <001e01c1bd8a$22f347b0$1200a8c0@gsicomp.on.ca> of Sun, 24 Feb 2002 18:22:27 EST Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Matthew Emmerton" wrote: | > | > I've had ppp -nat working just fine over a normal modem link, | > | > but it is not working at all well on my ADSL link to the same | > | > provider. | > | > | > | > To quantify "not working at all well", although I can ping and | > | > traceroute ok from the hosts on my LAN, HTTP and FTP traffic is | > | > so slow and bursty as to be useless. Clicking on a link with | > | > Netscape will see short bursts of data with long periods (of a | > | > minute or more) where it says "stalled". | > | > | > | > Clicking on from | > | > my gateway host gets the page in an eye-blink, but on the NAT | > | > hosts, it will take 40 seconds to load the top banner and the | > | > "FreeBSD GNOME News Flash" heading, then another delay of 40 or | > | > so seconds before the rest of the page will be displayed. Even | > | > then, Netscape thinks it has stalled and keeps waiting for the | > | > last bit of data. | > | > | > | > With FTP, a small transfer (e.g., a directory listing of / on | > | > ftp.freebsd.org) will complete normally; but something slightly | > | > larger (e.g., a listing of /pub/FreeBSD on the same server), | > | > will produce: | > | > | > | > ftp> cd /pub/FreeBSD | > | > 250 CWD command successful. | > | > ftp> dir | > | > 200 PORT command successful. | > | > 150 Opening ASCII mode data connection for '/bin/ls'. | > | > ftp: netin: Connection reset by peer | > | > 226 Transfer complete. | > | > ftp> quit | > | > 421 Timeout (60 seconds): closing control connection. | > | > | > | > If I do the same things from the host that is connected to the | > | > modem(s), everything works fine, for both types of connections. | > | > | > | > I'm finding this very frustrating, and I'm wondering if there's | > | > something weird about PPPoE with the ADSL link that needs some | > | > special magic in order for things to work properly. | > | > | > | > If anybody can point me at the truth, I'd be most grateful. | > | > | > | > Alternatively, if anybody can suggest steps I could take to | > | > identify the nature of the problem, that would also be most | > | > welcome. | > | | > | What version of FreeBSD are you using? The ppp included in early 4.x | > | distributions doesn't have the TCP MSS fixup code that is required to | > | make | > | things work properly with a PPPoE connection, and cause the kinds of | > | symptoms that you describe. | > | > The NAT box is running 4.2-RELEASE -- is that a problem? | | Yes. This problem was first fixed in 4.2-STABLE. There are two safe ways to | fix this: | - upgrade to a newer -RELEASE or -STABLE | - run the tcpmssd program (which is in the ports collection - | /usr/ports/net/tcpmssd) I'll try tcpmssd first -- I have some other systems in a similar situation that are running 4.1-RELEASE and can't be upgraded, so my solution needs to work for them too. Thanks for the information. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 0: 2: 5 2002 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id D16BE37B402; Mon, 25 Feb 2002 00:01:58 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g1P81EJ29324; Mon, 25 Feb 2002 10:01:14 +0200 (EET) (envelope-from ru) Date: Mon, 25 Feb 2002 10:01:14 +0200 From: Ruslan Ermilov To: cjclark@alum.mit.edu Cc: Maxim Konovalov , net@FreeBSD.ORG, Robert Watson Subject: Re: TCP Connections to a Broadcast Address Message-ID: <20020225080114.GA28900@sunbay.com> References: <20020223042828.E16048@blossom.cjclark.org> <20020223154842.G31228-100000@news1.macomnet.ru> <20020224084921.GC31243@sunbay.com> <20020224102746.Q16048@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020224102746.Q16048@blossom.cjclark.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Feb 24, 2002 at 10:27:46AM -0800, Crist J. Clark wrote: > On Sun, Feb 24, 2002 at 10:49:21AM +0200, Ruslan Ermilov wrote: > > On Sat, Feb 23, 2002 at 03:49:55PM +0300, Maxim Konovalov wrote: > > > On 04:28-0800, Feb 23, 2002, Crist J. Clark wrote: > > > > > > > On Sat, Feb 23, 2002 at 01:50:33PM +0200, Ruslan Ermilov wrote: > > > > [snip] > > > > > > > > > Nice catch! > > > > > > > > Igor M Podlesny , PR misc/35022, caught it. I just > > > > analyzed it. > > > > > > Isn't kern/19722 about the same bug? > > > > > Yes. > > I think there are some different issues raised in this PR too. Like > the discussion in another part of this thread, PR 19722 states that > you can reach the broadcast address of interfaces other than the one > to which the attacker is directly attached. I have not been able to > reproduce this. I think it was fixed by revision 1.181 of ip_input.c. > Nope, in revision 1.158. 1.181 only added hashed search optimizations. Cheers, -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 0:43:41 2002 Delivered-To: freebsd-net@freebsd.org Received: from overlord.e-gerbil.net (e-gerbil.net [207.91.110.247]) by hub.freebsd.org (Postfix) with ESMTP id 1055337B417 for ; Mon, 25 Feb 2002 00:43:37 -0800 (PST) Received: by overlord.e-gerbil.net (Postfix, from userid 1001) id E75CCE5008; Sun, 24 Feb 2002 04:50:15 -0500 (EST) Date: Sun, 24 Feb 2002 04:50:15 -0500 From: Richard A Steenbergen To: freebsd-net@freebsd.org Subject: HZ=1000 and NFS Message-ID: <20020224095015.GJ413@overlord.e-gerbil.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Is anyone aware of problems with HZ=1000 and NFS? I was playing around with Luigi's device polling and had no problems (and significant performance improvement under heavy network load), except for one server doing NFS. After playing around with it for a bit I found that it worked perfectly if I did not set HZ=1000. I had a problem with HZ=1000 and NFS once before when playing with ALTQ, but never persued it. The problem I'm experiencing now is a complete system lockup, no panic or crashing or informative errors of any kind. The cursor still blinks but everything else is totally frozen. -- Richard A Steenbergen http://www.e-gerbil.net/ras PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 0:44:59 2002 Delivered-To: freebsd-net@freebsd.org Received: from www.example.org (dhcp-nic-val-26-83.cisco.com [64.103.26.83]) by hub.freebsd.org (Postfix) with SMTP id B624837B405 for ; Mon, 25 Feb 2002 00:44:49 -0800 (PST) Received: (qmail 3747 invoked by uid 1000); 25 Feb 2002 08:44:20 -0000 Date: Mon, 25 Feb 2002 09:44:20 +0100 From: Marco Molteni To: freebsd-net@freebsd.org Subject: [PATCH] comment for struct inpcb (netinet/in_pcb.h) Message-ID: <20020225094420.A3312@cobweb.example.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, I have a small patch to add a comment to struct inpcb, explaining the role of member "vflag" (IP version flag, v4/v6). It took me a while to figure it out so I think it might be better to explicitly explain it. If you are wondering when it has been introduced, here are the results of my digging: It has been introduced in the KAME tree kame-freebsd-30 tree, revision 1.12, 18 Nov 1998: http://orange.kame.net/dev/cvsweb.cgi/src/sys/netinet/in_pcb.h?cvsroot=kame-freebsd-30 Then it has been merged in revision 1.30, 22 Nov 1999, in the FreeBSD source tree: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/in_pcb.h Marco --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="in_pcb.h.patch" --- in_pcb.h.old Mon Feb 25 09:27:00 2002 +++ in_pcb.h Mon Feb 25 09:30:50 2002 @@ -141,7 +141,7 @@ int inp_flags; /* generic IP/datagram flags */ struct inpcbpolicy *inp_sp; /* for IPSEC */ - u_char inp_vflag; + u_char inp_vflag; /* IP version flag (v4/v6) */ #define INP_IPV4 0x1 #define INP_IPV6 0x2 u_char inp_ip_ttl; /* time to live proto */ --envbJBWh7q8WU6mo-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 0:56: 1 2002 Delivered-To: freebsd-net@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id E560A37B405 for ; Mon, 25 Feb 2002 00:55:59 -0800 (PST) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g1P8tmV90013; Mon, 25 Feb 2002 00:55:48 -0800 (PST) (envelope-from rizzo) Date: Mon, 25 Feb 2002 00:55:48 -0800 From: Luigi Rizzo To: Richard A Steenbergen Cc: freebsd-net@FreeBSD.ORG Subject: Re: HZ=1000 and NFS Message-ID: <20020225005547.A89674@iguana.icir.org> References: <20020224095015.GJ413@overlord.e-gerbil.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020224095015.GJ413@overlord.e-gerbil.net> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org There used to be, long ago, some problems with HZ=1000 which were related to some diskless stuff -- now i forget the details but i believe it was some timeout field or the like overflowing. This was fixed years ago, though, and i believe the relevant code was in /sys/nfs/bootp_subr.c and related ones. I am running an NFS server with 4.5 and HZ=1000 (no device_polling though) and it seems to work fine. cheers luigi On Sun, Feb 24, 2002 at 04:50:15AM -0500, Richard A Steenbergen wrote: > Is anyone aware of problems with HZ=1000 and NFS? > > I was playing around with Luigi's device polling and had no problems (and > significant performance improvement under heavy network load), except for > one server doing NFS. After playing around with it for a bit I found that > it worked perfectly if I did not set HZ=1000. I had a problem with HZ=1000 > and NFS once before when playing with ALTQ, but never persued it. > > The problem I'm experiencing now is a complete system lockup, no panic or > crashing or informative errors of any kind. The cursor still blinks but > everything else is totally frozen. > > -- > Richard A Steenbergen http://www.e-gerbil.net/ras > PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 1:42:19 2002 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id C725637B404 for ; Mon, 25 Feb 2002 01:42:11 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 9EE49AE2D8; Mon, 25 Feb 2002 01:42:11 -0800 (PST) Date: Mon, 25 Feb 2002 01:42:11 -0800 From: Alfred Perlstein To: Marco Molteni Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] comment for struct inpcb (netinet/in_pcb.h) Message-ID: <20020225094211.GF80761@elvis.mu.org> References: <20020225094420.A3312@cobweb.example.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020225094420.A3312@cobweb.example.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Marco Molteni [020225 00:45] wrote: > Hi all, > > I have a small patch to add a comment to struct inpcb, explaining the > role of member "vflag" (IP version flag, v4/v6). It took me a while to > figure it out so I think it might be better to explicitly explain it. Your patch has been applied. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 1:45:20 2002 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 0584D37B405 for ; Mon, 25 Feb 2002 01:45:16 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id CFB26AE2D3; Mon, 25 Feb 2002 01:45:15 -0800 (PST) Date: Mon, 25 Feb 2002 01:45:15 -0800 From: Alfred Perlstein To: Marco Molteni Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] comment for struct inpcb (netinet/in_pcb.h) Message-ID: <20020225094515.GG80761@elvis.mu.org> References: <20020225094420.A3312@cobweb.example.org> <20020225094211.GF80761@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020225094211.GF80761@elvis.mu.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Alfred Perlstein [020225 01:43] wrote: > * Marco Molteni [020225 00:45] wrote: > > Hi all, > > > > I have a small patch to add a comment to struct inpcb, explaining the > > role of member "vflag" (IP version flag, v4/v6). It took me a while to > > figure it out so I think it might be better to explicitly explain it. > > Your patch has been applied. Oh, and thank you. :) -- -Alfred Perlstein [alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 2:31:22 2002 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id BF3CE37B417; Mon, 25 Feb 2002 02:31:10 -0800 (PST) Received: from localhost ([3ffe:501:4819:2000:e028:ba95:b8bc:b5a5]) by shuttle.wide.toshiba.co.jp (8.11.6/8.9.1) with ESMTP id g1PAV0o03956; Mon, 25 Feb 2002 19:31:00 +0900 (JST) Date: Mon, 25 Feb 2002 19:30:59 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Edwin Groothuis Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: IPv6-over-IPv4 problems since the upgrade to 4.5 In-Reply-To: <20020223084616.G492@k7.mavetju.org> References: <0D9185CE635BD511ACA50090277A6FCF1359DB@axcs18.cos.agilent.com> <20020216130842.A19081@energyhq.homeip.net> <20020217122510.D491@k7.mavetju.org> <20020222234829.F492@k7.mavetju.org> <20020223084616.G492@k7.mavetju.org> User-Agent: Wanderlust/2.7.5 (Too Funky) Emacs/21.1 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 44 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Sat, 23 Feb 2002 08:46:16 +1100, >>>>> Edwin Groothuis said: >> > And the interface configuration: >> > gif0: flags=8051 mtu 1280 >> > tunnel inet 203.173.130.126 --> 206.123.31.114 >> > inet6 fe80::250:8bff:feb9:2d24%gif0 prefixlen 64 scopeid 0x9 >> > inet6 3ffe:b80:2:460::2 --> 3ffe:b80:2:460::1 prefixlen 128 >> >> Hmm, and what command did you type to cause this problem? If possible, >> please give me the network topology as well. > The problem was when "route add -inet6 default -interface gif0" was > used instead of the "route ... ". For the rest the > configuration and the commands were the same. > This is a layout of the 'network': (snip) > The symptons were that if I setup a TCP-session, the original message > is at: > http://www.freebsd.org/cgi/getmsg.cgi?fetch=279914+284924+/usr/local/www/db/text/2002/freebsd-hackers/20020217.freebsd-hackers Okay, I understand the configuration. I did a similar test on a 4.5-RELEASE box, but could not reproduce the problem. The main difference in my test case is I did not use ppp, so I guess ppp is somehow related to this problem... Now I'd like to know: - did you see the same problem in an environment without ppp? - what is the result of netstat -rnal when the kernel is sending neighbor solicitations? - I guess some process (or kernel) modifies the route to the destination. Could you run 'route -n monitor' while the session to see the modification? Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 2:39:41 2002 Delivered-To: freebsd-net@freebsd.org Received: from ns1.hexanet.fr (ns1.hexanet.fr [194.98.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 5A0A237B400 for ; Mon, 25 Feb 2002 02:39:38 -0800 (PST) Received: from snowflake (olrick@snowflake.hexanet.fr [194.98.140.144]) by ns1.hexanet.fr (8.9.3/8.9.3) with SMTP id LAA30293 for ; Mon, 25 Feb 2002 11:39:37 +0100 (CET) (envelope-from y.grossel@hexanet.fr) Date: Mon, 25 Feb 2002 11:39:38 +0100 From: Yann GROSSEL To: freebsd-net@FreeBSD.ORG Subject: dc TX underrun message Message-Id: <20020225113938.12bf08be.y.grossel@hexanet.fr> Organization: Hexanet X-Mailer: Sylpheed version 0.7.2 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, We have a new machine that is about to become a firewall. For now this machine is running but idle, that is, it has no services running but sshd, and no default route. The machine has been up for about 20 days, wihtout doing anything. However 3 messages has been logged : Feb 5 14:30:18 blade /kernel: dc3: TX underrun -- increasing TX threshold Feb 5 14:58:33 blade /kernel: dc3: TX underrun -- increasing TX threshold Feb 19 09:38:39 blade /kernel: dc3: TX underrun -- increasing TX threshold What do these message mean ? Is there a hardware problem ? The machine has never been tested in real use (that is, with any network traffic), so we don't know if this problem may freeze or crash the machine with heavy real traffic, and we can't afford to test that). Machine details : CPU: Pentium III/Pentium III Xeon/Celeron (699.51-MHz 686-class CPU) FreeBSD blade.hexanet.fr 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE #3: Tue Feb 5 14:16:17 CET 2002 root@blade.hexanet.fr:/usr/obj/usr/src/sys/BLADE i386 src/sys/pci/if_dc.c,v 1.9.2.31 2001/12/19 18:37:34 wpaul Exp $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 3: 7:40 2002 Delivered-To: freebsd-net@freebsd.org Received: from sulphur.cix.co.uk (sulphur.cix.co.uk [212.35.225.149]) by hub.freebsd.org (Postfix) with ESMTP id D36A237B402 for ; Mon, 25 Feb 2002 03:07:35 -0800 (PST) Received: from LEECH (s29.pool.pm3-tele-3.cix.co.uk [194.153.23.29]) by sulphur.cix.co.uk (8.11.3/CIX/8.11.3) with ESMTP id g1PB7nO16628 for ; Mon, 25 Feb 2002 11:07:52 GMT From: owen.grover@ts-associates.com X-Envelope-From: owen.grover@ts-associates.com To: freebsd-net@FreeBSD.ORG Subject: ep0 broadcast problem MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.6a January 17, 2001 Message-ID: Date: Mon, 25 Feb 2002 10:57:41 +0000 X-MIMETrack: Serialize by Idle on Owen Grover(Release 5.0.6a |January 17, 2001) at 25/02/2002 11:05:37, Serialize complete at 25/02/2002 11:05:37 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm using FreeBSD 4.5 on a Toshiba Tecra 8100 with a 3COM 3C589 PCMCIA LAN card. The problem I am having is that when broadcast packets are sent I see them twice in tcpdump running on the same machine, with a split second difference in the timestamp for each packet. I know the broadcast packet is actually only being sent once onto the network as when I run tcpdump on another machine it sees the packet only once. Therefore it would appear that the broadcast packet is being looped back up through the TCP/IP stack. Also if I try this on another machine using Intel cards (fxp0) the problem goes away, so it would seem to point to the PCMCIA card or driver as the source of the problem. If this problem has been documented before, my apologies for dragging up old issues and would someone point me to the relevant document; else any one with any ideas? Owen Grover To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 3:19:14 2002 Delivered-To: freebsd-net@freebsd.org Received: from topaz.mdcc.cx (topaz.mdcc.cx [212.204.230.141]) by hub.freebsd.org (Postfix) with ESMTP id 5E6B937B400; Mon, 25 Feb 2002 03:18:51 -0800 (PST) Received: from k7.mavetju.org (topaz.mdcc.cx [212.204.230.141]) by topaz.mdcc.cx (Postfix) with ESMTP id 6B4B52B79B; Mon, 25 Feb 2002 12:18:38 +0100 (CET) Received: by k7.mavetju.org (Postfix, from userid 1001) id 1AB1E369; Mon, 25 Feb 2002 22:18:27 +1100 (EST) Date: Mon, 25 Feb 2002 22:18:27 +1100 From: Edwin Groothuis To: "JINMEI Tatuya / ?$B?@L@C#:H?(B" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: IPv6-over-IPv4 problems since the upgrade to 4.5 Message-ID: <20020225221827.F491@k7.mavetju.org> Mail-Followup-To: Edwin Groothuis , "JINMEI Tatuya / ?$B?@L@C#:H?(B" , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG References: <0D9185CE635BD511ACA50090277A6FCF1359DB@axcs18.cos.agilent.com> <20020216130842.A19081@energyhq.homeip.net> <20020217122510.D491@k7.mavetju.org> <20020222234829.F492@k7.mavetju.org> <20020223084616.G492@k7.mavetju.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jinmei@isl.rdc.toshiba.co.jp on Mon, Feb 25, 2002 at 07:30:59PM +0900 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Feb 25, 2002 at 07:30:59PM +0900, JINMEI Tatuya / ?$B?@L@C#:H?(B wrote: > >>>>> On Sat, 23 Feb 2002 08:46:16 +1100, > >>>>> Edwin Groothuis said: > > >> > And the interface configuration: > >> > gif0: flags=8051 mtu 1280 > >> > tunnel inet 203.173.130.126 --> 206.123.31.114 > >> > inet6 fe80::250:8bff:feb9:2d24%gif0 prefixlen 64 scopeid 0x9 > >> > inet6 3ffe:b80:2:460::2 --> 3ffe:b80:2:460::1 prefixlen 128 > >> > >> Hmm, and what command did you type to cause this problem? If possible, > >> please give me the network topology as well. > > > The problem was when "route add -inet6 default -interface gif0" was > > used instead of the "route ... ". For the rest the > > configuration and the commands were the same. > > > This is a layout of the 'network': > > (snip) > > > The symptons were that if I setup a TCP-session, the original message > > is at: > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=279914+284924+/usr/local/www/db/text/2002/freebsd-hackers/20020217.freebsd-hackers > > Okay, I understand the configuration. I did a similar test on a > 4.5-RELEASE box, but could not reproduce the problem. The main > difference in my test case is I did not use ppp, so I guess ppp is > somehow related to this problem... > > Now I'd like to know: > > - did you see the same problem in an environment without ppp? That PPP link is my link to the outside world, I'm afraid I can't help you with this one. (Yes I'm living in a backwards country) > - what is the result of netstat -rnal when the kernel is sending > neighbor solicitations? I have three captures for you: one before, one during and one in hang state: *** This one is from before any session: Routing tables Internet: Destination Gateway Flags Refs Use Mtu Netif Expire default 203.109.251.3 UGSc 11 2073 1524 tun0 62.163.31.203 203.109.251.3 UGHW 1 1900 1524 tun0 63.149.6.93 203.109.251.3 UGHW 1 2036 1524 tun0 127.0.0.1 127.0.0.1 UH 7824 496162 16384 lo0 129.127.28.4 203.109.251.3 UGHW 1 1862 1524 tun0 131.155.132.36 203.109.251.3 UGHW 1 2408 1524 tun0 152.163.159.234 203.109.251.3 UGHW3 0 1969 1524 tun0 71 192.168.0 link#7 UC 2 0 1500 vmnet1 192.168.0.1 0:bd:10:10:0:1 UHLW 0 4 1500 lo0 192.168.0.44 link#7 UHLW 1 11 1500 vmnet1 192.168.1 link#1 UC 3 0 1500 fxp0 192.168.1.1 0:50:8b:b9:2d:24 UHLW 0 31541 1500 lo0 192.168.1.2 0:5:2:b1:89:ee UHLW 2 95980 1500 fxp0 1163 192.168.1.255 ff:ff:ff:ff:ff:ff UHLWb 0 38 1500 fxp0 203.12.68.36 203.109.251.3 UGHW 1 1751 1524 tun0 203.109.251.3 203.173.157.67 UH 12 0 1524 tun0 204.57.55.54 203.109.251.3 UGHW 1 1630 1524 tun0 206.123.31.114 203.109.251.3 UGHW 2 2000 1524 tun0 212.204.230.141 203.109.251.3 UGHW 3 649 1524 tun0 217.120.67.246 203.109.251.3 UGHW 1 2049 1524 tun0 254.237.183.234 203.109.251.3 UGHW 2 2065 1500 tun0 Internet6: Destination Gateway Flags Refs Use Mtu Netif Expire ::/96 ::1 UGRSc 0 0 16384 lo0 => default gif0 ULSc 0 0 1280 gif0 ::1 ::1 UH 4 458445 16384 lo0 ::ffff:0.0.0.0/96 ::1 UGRSc 0 0 16384 lo0 3ffe:b80:2:460::1 3ffe:b80:2:460::2 UH 0 0 1280 gif0 3ffe:b80:2:460::2 link#9 UHL 1 0 1280 lo0 fe80::/10 ::1 UGRSc 0 0 16384 lo0 fe80::%fxp0/64 link#1 UC 0 0 1500 fxp0 fe80::250:8bff:feb9:2d24%fxp0 0:50:8b:b9:2d:24 UHL 0 0 1500 lo0 fe80::%lo0/64 fe80::1%lo0 Uc 0 0 16384 lo0 fe80::1%lo0 link#3 UHL 0 0 16384 lo0 fe80::%vmnet1/64 link#7 UC 0 0 1500 vmnet1 fe80::2bd:10ff:fe10:1%vmnet1 0:bd:10:10:0:1 UHL 0 0 1500 lo0 fe80::%tun0/64 fe80::250:8bff:feb9:2d24%tun0 Uc 0 0 1500 tun0 fe80::250:8bff:feb9:2d24%tun0 link#8 UHL 0 0 1500 lo0 fe80::%gif0/64 link#9 UC 0 0 1280 gif0 fe80::250:8bff:feb9:2d24%gif0 link#9 UHL 0 0 1280 lo0 ff01::/32 ::1 U 0 0 16384 lo0 ff02::/16 ::1 UGRS 0 0 16384 lo0 ff02::%fxp0/32 link#1 UC 0 0 1500 fxp0 ff02::%lo0/32 ::1 UC 0 0 16384 lo0 ff02::%vmnet1/32 link#7 UC 0 0 1500 vmnet1 ff02::%tun0/32 fe80::250:8bff:feb9:2d24%tun0 UC 0 0 1500 tun0 ff02::%gif0/32 link#9 UC 0 0 1280 gif0 *** This one is just after the tcp-session is setup: Routing tables Internet: Destination Gateway Flags Refs Use Mtu Netif Expire default 203.109.251.3 UGSc 11 2073 1524 tun0 62.163.31.203 203.109.251.3 UGHW 1 1902 1524 tun0 63.149.6.93 203.109.251.3 UGHW 1 2036 1524 tun0 127.0.0.1 127.0.0.1 UH 7824 496172 16384 lo0 129.127.28.4 203.109.251.3 UGHW 1 1862 1524 tun0 131.155.132.36 203.109.251.3 UGHW 1 2408 1524 tun0 152.163.159.234 203.109.251.3 UGHW3 0 1969 1524 tun0 66 192.168.0 link#7 UC 2 0 1500 vmnet1 192.168.0.1 0:bd:10:10:0:1 UHLW 0 4 1500 lo0 192.168.0.44 link#7 UHLW 1 11 1500 vmnet1 192.168.1 link#1 UC 3 0 1500 fxp0 192.168.1.1 0:50:8b:b9:2d:24 UHLW 0 31541 1500 lo0 192.168.1.2 0:5:2:b1:89:ee UHLW 2 95980 1500 fxp0 1158 192.168.1.255 ff:ff:ff:ff:ff:ff UHLWb 0 38 1500 fxp0 203.12.68.36 203.109.251.3 UGHW 1 1752 1524 tun0 203.109.251.3 203.173.157.67 UH 12 0 1524 tun0 204.57.55.54 203.109.251.3 UGHW 1 1631 1524 tun0 206.123.31.114 203.109.251.3 UGHW 2 2003 1524 tun0 212.204.230.141 203.109.251.3 UGHW 3 649 1524 tun0 217.120.67.246 203.109.251.3 UGHW 1 2049 1524 tun0 254.237.183.234 203.109.251.3 UGHW 2 2065 1500 tun0 Internet6: Destination Gateway Flags Refs Use Mtu Netif Expire ::/96 ::1 UGRSc 0 0 16384 lo0 => default gif0 ULSc 1 0 1280 gif0 ::1 ::1 UH 4 458445 16384 lo0 ::ffff:0.0.0.0/96 ::1 UGRSc 0 0 16384 lo0 3ffe:b80:2:460::1 3ffe:b80:2:460::2 UH 0 0 1280 gif0 3ffe:b80:2:460::2 link#9 UHL 1 0 1280 lo0 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea gif0 UHLW 1 3 1280 gif0 fe80::/10 ::1 UGRSc 0 0 16384 lo0 fe80::%fxp0/64 link#1 UC 0 0 1500 fxp0 fe80::250:8bff:feb9:2d24%fxp0 0:50:8b:b9:2d:24 UHL 0 0 1500 lo0 fe80::%lo0/64 fe80::1%lo0 Uc 0 0 16384 lo0 fe80::1%lo0 link#3 UHL 0 0 16384 lo0 fe80::%vmnet1/64 link#7 UC 0 0 1500 vmnet1 fe80::2bd:10ff:fe10:1%vmnet1 0:bd:10:10:0:1 UHL 0 0 1500 lo0 fe80::%tun0/64 fe80::250:8bff:feb9:2d24%tun0 Uc 0 0 1500 tun0 fe80::250:8bff:feb9:2d24%tun0 link#8 UHL 0 0 1500 lo0 fe80::%gif0/64 link#9 UC 0 0 1280 gif0 fe80::250:8bff:feb9:2d24%gif0 link#9 UHL 0 0 1280 lo0 ff01::/32 ::1 U 0 0 16384 lo0 ff02::/16 ::1 UGRS 0 0 16384 lo0 ff02::%fxp0/32 link#1 UC 0 0 1500 fxp0 ff02::%lo0/32 ::1 UC 0 0 16384 lo0 ff02::%vmnet1/32 link#7 UC 0 0 1500 vmnet1 ff02::%tun0/32 fe80::250:8bff:feb9:2d24%tun0 UC 0 0 1500 tun0 ff02::%gif0/32 link#9 UC 0 0 1280 gif0 *** And this one is after is hangs: Routing tables Internet: Destination Gateway Flags Refs Use Mtu Netif Expire default 203.109.251.3 UGSc 11 2073 1524 tun0 62.163.31.203 203.109.251.3 UGHW 1 1907 1524 tun0 63.149.6.93 203.109.251.3 UGHW 1 2036 1524 tun0 127.0.0.1 127.0.0.1 UH 7824 496188 16384 lo0 129.127.28.4 203.109.251.3 UGHW 1 1862 1524 tun0 131.155.132.36 203.109.251.3 UGHW 1 2408 1524 tun0 152.163.159.234 203.109.251.3 UGHW3 0 1969 1524 tun0 45 192.168.0 link#7 UC 2 0 1500 vmnet1 192.168.0.1 0:bd:10:10:0:1 UHLW 0 4 1500 lo0 192.168.0.44 link#7 UHLW 1 11 1500 vmnet1 192.168.1 link#1 UC 3 0 1500 fxp0 192.168.1.1 0:50:8b:b9:2d:24 UHLW 0 31541 1500 lo0 192.168.1.2 0:5:2:b1:89:ee UHLW 2 95980 1500 fxp0 1137 192.168.1.255 ff:ff:ff:ff:ff:ff UHLWb 0 38 1500 fxp0 203.12.68.36 203.109.251.3 UGHW 1 1755 1524 tun0 203.109.251.3 203.173.157.67 UH 12 0 1524 tun0 204.57.55.54 203.109.251.3 UGHW 1 1631 1524 tun0 206.123.31.114 203.109.251.3 UGHW 2 2017 1524 tun0 212.204.230.141 203.109.251.3 UGHW 3 649 1524 tun0 217.120.67.246 203.109.251.3 UGHW 1 2049 1524 tun0 254.237.183.234 203.109.251.3 UGHW 3 2072 1500 tun0 Internet6: Destination Gateway Flags Refs Use Mtu Netif Expire ::/96 ::1 UGRSc 0 0 16384 lo0 => default gif0 ULSc 1 0 1280 gif0 ::1 ::1 UH 4 458445 16384 lo0 ::ffff:0.0.0.0/96 ::1 UGRSc 0 0 16384 lo0 3ffe:b80:2:460::1 3ffe:b80:2:460::2 UH 0 0 1280 gif0 3ffe:b80:2:460::2 link#9 UHL 1 0 1280 lo0 fe80::/10 ::1 UGRSc 0 0 16384 lo0 fe80::%fxp0/64 link#1 UC 0 0 1500 fxp0 fe80::250:8bff:feb9:2d24%fxp0 0:50:8b:b9:2d:24 UHL 0 0 1500 lo0 fe80::%lo0/64 fe80::1%lo0 Uc 0 0 16384 lo0 fe80::1%lo0 link#3 UHL 0 0 16384 lo0 fe80::%vmnet1/64 link#7 UC 0 0 1500 vmnet1 fe80::2bd:10ff:fe10:1%vmnet1 0:bd:10:10:0:1 UHL 0 0 1500 lo0 fe80::%tun0/64 fe80::250:8bff:feb9:2d24%tun0 Uc 0 0 1500 tun0 fe80::250:8bff:feb9:2d24%tun0 link#8 UHL 0 0 1500 lo0 fe80::%gif0/64 link#9 UC 0 0 1280 gif0 fe80::250:8bff:feb9:2d24%gif0 link#9 UHL 0 0 1280 lo0 ff01::/32 ::1 U 0 0 16384 lo0 ff02::/16 ::1 UGRS 0 0 16384 lo0 ff02::%fxp0/32 link#1 UC 0 0 1500 fxp0 ff02::%lo0/32 ::1 UC 0 0 16384 lo0 ff02::%vmnet1/32 link#7 UC 0 0 1500 vmnet1 ff02::%tun0/32 fe80::250:8bff:feb9:2d24%tun0 UC 0 0 1500 tun0 ff02::%gif0/32 link#9 UC 0 0 1280 gif0 For your convenience, this is in the diff between the first and the second: Internet6: Destination Gateway Flags Refs Use Mtu Netif Expire ::/96 ::1 UGRSc 0 0 16384 lo0 => -default gif0 ULSc 0 0 1280 gif0 +default gif0 ULSc 1 0 1280 gif0 ::1 ::1 UH 4 458445 16384 lo0 ::ffff:0.0.0.0/96 ::1 UGRSc 0 0 16384 lo0 3ffe:b80:2:460::1 3ffe:b80:2:460::2 UH 0 0 1280 gif0 3ffe:b80:2:460::2 link#9 UHL 1 0 1280 lo0 +3ffe:8050:201:1860:2a0:c9ff:feed:b7ea gif0 UHLW 1 3 1280 gif0 fe80::/10 ::1 UGRSc 0 0 16384 lo0 fe80::%fxp0/64 link#1 UC 0 0 1500 fxp0 fe80::250:8bff:feb9:2d24%fxp0 0:50:8b:b9:2d:24 UHL 0 0 1500 lo0 And this in the diff between the second and the third: ::ffff:0.0.0.0/96 ::1 UGRSc 0 0 16384 lo0 3ffe:b80:2:460::1 3ffe:b80:2:460::2 UH 0 0 1280 gif0 3ffe:b80:2:460::2 link#9 UHL 1 0 1280 lo0 -3ffe:8050:201:1860:2a0:c9ff:feed:b7ea gif0 UHLW 1 3 1280 gif0 fe80::/10 ::1 UGRSc 0 0 16384 lo0 fe80::%fxp0/64 link#1 UC 0 0 1500 fxp0 fe80::250:8bff:feb9:2d24%fxp0 0:50:8b:b9:2d:24 UHL 0 0 1500 lo0 > - I guess some process (or kernel) modifies the route to the > destination. Could you run 'route -n monitor' while the session to > see the modification? The first message is when the session is setup, the second one is a short time later (not directly after the last neighbour solicitation message). I don't know what the 254.237.183.234 is. got message of size 260 on Mon Feb 25 22:04:25 2002 RTM_ADD: Add Route: len 260, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea gif0 gif0 fe80::250:8bff:feb9:2d24%gif0 got message of size 124 on Mon Feb 25 22:04:38 2002 RTM_LOSING: Kernel Suspects Partitioning: len 124, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: 254.237.183.234 203.109.251.3 If you need more information, feel free to ask. Edwin -- Edwin Groothuis | Personal website: http://www.MavEtJu.org edwin@mavetju.org | Interested in MUDs? Visit Fatal Dimensions: ------------------+ http://www.FatalDimensions.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 3:51:20 2002 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id B928037B400; Mon, 25 Feb 2002 03:51:13 -0800 (PST) Received: from localhost ([3ffe:501:4819:2000:e028:ba95:b8bc:b5a5]) by shuttle.wide.toshiba.co.jp (8.11.6/8.9.1) with ESMTP id g1PBp9o04573; Mon, 25 Feb 2002 20:51:09 +0900 (JST) Date: Mon, 25 Feb 2002 20:51:09 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Edwin Groothuis Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: IPv6-over-IPv4 problems since the upgrade to 4.5 In-Reply-To: <20020225221827.F491@k7.mavetju.org> References: <0D9185CE635BD511ACA50090277A6FCF1359DB@axcs18.cos.agilent.com> <20020216130842.A19081@energyhq.homeip.net> <20020217122510.D491@k7.mavetju.org> <20020222234829.F492@k7.mavetju.org> <20020223084616.G492@k7.mavetju.org> <20020225221827.F491@k7.mavetju.org> User-Agent: Wanderlust/2.7.5 (Too Funky) Emacs/21.1 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 30 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Mon, 25 Feb 2002 22:18:27 +1100, >>>>> Edwin Groothuis said: > *** And this one is after is hangs: > Internet6: > Destination Gateway Flags Refs Use Mtu Netif Expire > ::/96 ::1 UGRSc 0 0 16384 lo0 => > default gif0 ULSc 1 0 1280 gif0 This means you configured the default route by "-interface gif0", right? If so, wasn't it a workaround of this problem? > got message of size 260 on Mon Feb 25 22:04:25 2002 > RTM_ADD: Add Route: len 260, pid: 0, seq 0, errno 0, flags: > locks: inits: > sockaddrs: > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea gif0 gif0 fe80::250:8bff:feb9:2d24%gif0 Hmm, there's nothing strange here. > If you need more information, feel free to ask. Which interface did you see the neighbor solicitations, on gif0, on tun0, or others? JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 5:20:59 2002 Delivered-To: freebsd-net@freebsd.org Received: from wiprom2mx1.wipro.com (wiprom2mx1.wipro.com [203.197.164.41]) by hub.freebsd.org (Postfix) with ESMTP id 4399337B400 for ; Mon, 25 Feb 2002 05:20:45 -0800 (PST) Received: from m2vwall3.wipro.com (m2vwall3.wipro.com [164.164.29.237]) by wiprom2mx1.wipro.com (8.11.3/8.11.3) with SMTP id g1PDKhe24507 for ; Mon, 25 Feb 2002 18:50:44 +0530 (IST) Received: from 192.168.223.18 by m2vwall3.wipro.com (InterScan E-Mail VirusWall NT); Mon, 25 Feb 2002 18:50:37 +0530 Received: from Ramit ([10.118.3.71]) by platinum.mail.wipro.com (Netscape Messaging Server 4.15) with ESMTP id GS3BQD00.B3M for ; Mon, 25 Feb 2002 18:50:37 +0530 From: "Ramit Bhalla" To: "FreeBSD Net" Subject: Extent of IPv6 support. Date: Mon, 25 Feb 2002 18:50:58 +0530 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPartTM-000-1fd68e1a-29d3-11d6-a219-0000e22173f5" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPartTM-000-1fd68e1a-29d3-11d6-a219-0000e22173f5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, I'm developing a IPv6 stack for VxWorks and since the VxWorks stack is based upon the FreeBSD stack ( smart choice! ) I think the best way to go is to use the FreeBSD implementation. I needed some help in identifing the incomplete modules/unsupported modules. Since this product is going to be a router product, I was hoping someone could outline which modules are complete/incomplete and which ones are un-supported as of now. For instance advanced stuff like Border Gateway protocol, SNMP, firewalling etc - do they support IPv6 ?? Another thing I couldn't understand is that there are 2 branches, netinet and netinet6, but both of them support IPv6, what's the difference ? Thanks a lot and any information would really be appreciated, Ramit. Ramit Bhalla Wipro Technologies, No 8, 7th Main, 1st Block, Koramangala, Bangalore - 560034. Tel(O) - 91-80-5530035 ext 1082. Fax(O) - 91-80-5530086. ------=_NextPartTM-000-1fd68e1a-29d3-11d6-a219-0000e22173f5 Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" **************************Disclaimer************************************ Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. ******************************************************************** ------=_NextPartTM-000-1fd68e1a-29d3-11d6-a219-0000e22173f5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 11:38:40 2002 Delivered-To: freebsd-net@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id C708637B41A for ; Mon, 25 Feb 2002 11:38:37 -0800 (PST) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id g1PJcW210425; Mon, 25 Feb 2002 11:38:32 -0800 Date: Mon, 25 Feb 2002 11:38:32 -0800 From: Brooks Davis To: Jeff Lawton Cc: freebsd-net@FreeBSD.ORG Subject: Re: 3com gigabit 3c996b-t Message-ID: <20020225113832.A29087@Odin.AC.HMC.Edu> References: <20020222235251.A32972@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jeff@idealso.com on Fri, Feb 22, 2002 at 06:58:20PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 22, 2002 at 06:58:20PM -0500, Jeff Lawton wrote: > Bge detects the card and it shows up on ifconfig it does not detect > 1000basetx on autoselect even though the card and the switch both register > 1000baset. I connected it to a 100base t port and it seems to work fine. = How > do I get it to switch to 1000baset >=20 > This is the bge section of ifconfig >=20 > bge0: flags=3D8843 mtu 1500 > options=3D3 > inet 192.168.0.166 netmask 0xffffff00 broadcast 192.168.0.255 > inet6 fe80::204:76ff:fee0:12a9%bge0 prefixlen 64 scopeid 0x1 > ether 00:04:76:e0:12:a9 > media: Ethernet autoselect (100baseTX ) > status: active At least on the systems I'm trying to use 3C996B-T's on, the MII support is clearly hosed. I'm seeing it probe 32 instances on ukphys which is bogus. I'm going to try and look at it some time this week, but someone with more driver experience would probalby have more luck. -- Brooksk -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8epK4XY6L6fI4GtQRAlbMAJ9RCMNr6gStuSVbt+4Kk38cDf0dcQCeOMKo 5umIQlLUAF9tOFF7FU3eoXw= =RaJn -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 14:49:54 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 6F04437B417 for ; Mon, 25 Feb 2002 14:49:48 -0800 (PST) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020225224948.IWBM1147.rwcrmhc52.attbi.com@blossom.cjclark.org>; Mon, 25 Feb 2002 22:49:48 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g1PMnlr53208; Mon, 25 Feb 2002 14:49:47 -0800 (PST) (envelope-from cjc) Date: Mon, 25 Feb 2002 14:49:47 -0800 From: "Crist J. Clark" To: Ramit Bhalla Cc: FreeBSD Net Subject: Re: Extent of IPv6 support. Message-ID: <20020225144947.C52727@blossom.cjclark.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ramit.bhalla@wipro.com on Mon, Feb 25, 2002 at 06:50:58PM +0530 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Feb 25, 2002 at 06:50:58PM +0530, Ramit Bhalla wrote: > Hi, > > I'm developing a IPv6 stack for VxWorks and since the VxWorks stack is based > upon the FreeBSD stack ( smart choice! ) I think the best way to go is to > use the FreeBSD implementation. > > I needed some help in identifing the incomplete modules/unsupported modules. > > Since this product is going to be a router product, I was hoping someone > could outline which modules are complete/incomplete and which ones are > un-supported as of now. > > For instance advanced stuff like Border Gateway protocol, See RFC2545. > SNMP, There is nothing about SNMP that ties it to any particular network protocol. You can run it over UDP in IPv6 just the same as you do in IPv4. (Hell, you can run SNMP over AppleTalk or IPX.) > firewalling On a FreeBSD box, see ip6fw(8). > etc - do they support IPv6 ?? As I have pointed out, the _protocols_ will do fine. OTOH, finding _products_ and applications that run these protocols over IPv6 might be a little harder. > Another thing I couldn't understand is that there are 2 branches, netinet > and netinet6, but both of them support IPv6, what's the difference ? They are not really "two" branches. Most of the IPv6 specific code is in netinet6. There is IPv6 code in netinet where there is interoperability between the two. Most of the IPv6 code you see in netinet is for the transport layer stuff. Duplicating the TCP and UDP code in both would present an opportunity for drift and be difficult to maintain. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 15:25: 3 2002 Delivered-To: freebsd-net@freebsd.org Received: from ns.live.com (ns.live.com [66.80.62.34]) by hub.freebsd.org (Postfix) with ESMTP id 05C1237B41D; Mon, 25 Feb 2002 15:24:51 -0800 (PST) Received: (from rsf@localhost) by ns.live.com (8.9.3/8.9.3) id PAA05049; Mon, 25 Feb 2002 15:24:50 -0800 (PST) (envelope-from rsf) Message-Id: <4.3.1.1.20020225133844.00c90c20@localhost> X-Sender: rsf@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Mon, 25 Feb 2002 13:56:00 -0800 To: freebsd-mobile@FreeBSD.ORG, freebsd-net@FreeBSD.ORG From: Ross Finlayson Subject: Sudden "wi" errors in 4.5-STABLE Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have a Lucent Orinoco 802.11b card (with latest firmware) running in an ISA<->PCMCIA adaptor on a box running 4.5-STABLE. I have found that - on rare occasion - the "wi" driver suddenly starts spazzing out, generating lots of errors like the following: Feb 24 12:52:57 ns /kernel: wi0: timeout in wi_seek to 1f6/0; last status 4000 Feb 24 12:52:57 ns /kernel: wi0: timeout in wi_seek to 1f6/44; last status 4044 Feb 24 12:52:57 ns /kernel: wi0: xmit failed ... Feb 25 11:34:56 ns /kernel: wi0: mgmt. buffer allocation failed Feb 25 11:39:36 ns /kernel: wi0: timeout in wi_seek to 0/0; last status 4000 Feb 25 11:39:36 ns /kernel: wi0: timeout in wi_seek to 0/44; last status 4044 Feb 25 11:39:36 ns /kernel: wi0: xmit failed Feb 25 11:41:55 ns /kernel: wi0: watchdog timeout Feb 25 11:41:55 ns /kernel: wi0: init failed Feb 25 11:41:55 ns /kernel: wi0: failed to allocate 1594 bytes on NIC Feb 25 11:41:55 ns /kernel: wi0: tx buffer allocation failed Feb 25 11:41:55 ns /kernel: wi0: failed to allocate 1594 bytes on NIC Feb 25 11:41:55 ns /kernel: wi0: mgmt. buffer allocation failed When this happens, all subsequent IP-level communication on the "wi0" interface ceases (although "netstat -i" reports that some layer-2 packets continue to be sent/received). Has anyone else seen this happen? Does anyone have a fix? Ross. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 15:38:51 2002 Delivered-To: freebsd-net@freebsd.org Received: from laptop.tenebras.com (laptop.tenebras.com [66.92.188.18]) by hub.freebsd.org (Postfix) with SMTP id AA22A37B402 for ; Mon, 25 Feb 2002 15:38:47 -0800 (PST) Received: (qmail 9820 invoked from network); 25 Feb 2002 23:38:46 -0000 Received: from sapphire.tenebras.com (HELO tenebras.com) (66.92.188.241) by 0 with SMTP; 25 Feb 2002 23:38:46 -0000 Message-ID: <3C7ACB06.6030403@tenebras.com> Date: Mon, 25 Feb 2002 15:38:46 -0800 From: Michael Sierchio User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.8) Gecko/20020218 X-Accept-Language: en-us MIME-Version: 1.0 To: Ross Finlayson Cc: freebsd-mobile@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Sudden "wi" errors in 4.5-STABLE References: <4.3.1.1.20020225133844.00c90c20@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Ross Finlayson wrote: > I have a Lucent Orinoco 802.11b card (with latest firmware) running in > an ISA<->PCMCIA adaptor on a box running 4.5-STABLE. Latest firmware? Which driver version? > > I have found that - on rare occasion - the "wi" driver suddenly starts > spazzing out, generating lots of errors like the following: > > Feb 24 12:52:57 ns /kernel: wi0: timeout in wi_seek to 1f6/0; last > status 4000 > Feb 24 12:52:57 ns /kernel: wi0: timeout in wi_seek to 1f6/44; last > status 4044 > Has anyone else seen this happen? Does anyone have a fix? Yes. These disappeared when I installed the latest rev. of the ORiNOCO driver/firmware. You'll need a Windoze machine to apply the update. ftp ftp://ftp.orinocowireless.com/pub/software/ORiNOCO/PC_Card/Firmware/R7.4winter2002/WSU_810.exe Should do the trick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 18:16:51 2002 Delivered-To: freebsd-net@freebsd.org Received: from idealso.com (idealso.com [216.122.250.84]) by hub.freebsd.org (Postfix) with ESMTP id C190D37B41B for ; Mon, 25 Feb 2002 18:16:48 -0800 (PST) Received: from att (12-245-208-165.client.attbi.com [12.245.208.165]) by idealso.com (8.11.0/8.11.0) with SMTP id g1Q2GVD15387; Mon, 25 Feb 2002 21:16:31 -0500 (EST) (envelope-from jeff@idealso.com) Reply-To: From: "Jeff Lawton" To: "Brooks Davis" , Subject: RE: 3com gigabit 3c996b-t Date: Mon, 25 Feb 2002 21:20:13 -0500 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 V5.50.4807.1700 Importance: Normal In-Reply-To: <20020225113832.A29087@Odin.AC.HMC.Edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Thank you, if you get a functioning driver please let me know. Does any one know if I would be better off returning this card and getting a more supported one like the intel pro1000 or dge-500tx. does any one have a recommendation. My company wants to use this as a btrieve (I know yuk) file server. We have a database that we have been using for years. This is an temporary performance increase while we work on a client server system. Jeff Lawton Ideal Solution, LLC -----Original Message----- From: Brooks Davis [mailto:brooks@one-eyed-alien.net] Sent: Monday, February 25, 2002 2:39 PM To: Jeff Lawton Cc: freebsd-net@FreeBSD.ORG Subject: Re: 3com gigabit 3c996b-t On Fri, Feb 22, 2002 at 06:58:20PM -0500, Jeff Lawton wrote: > Bge detects the card and it shows up on ifconfig it does not detect > 1000basetx on autoselect even though the card and the switch both register > 1000baset. I connected it to a 100base t port and it seems to work fine. How > do I get it to switch to 1000baset > > This is the bge section of ifconfig > > bge0: flags=8843 mtu 1500 > options=3 > inet 192.168.0.166 netmask 0xffffff00 broadcast 192.168.0.255 > inet6 fe80::204:76ff:fee0:12a9%bge0 prefixlen 64 scopeid 0x1 > ether 00:04:76:e0:12:a9 > media: Ethernet autoselect (100baseTX ) > status: active At least on the systems I'm trying to use 3C996B-T's on, the MII support is clearly hosed. I'm seeing it probe 32 instances on ukphys which is bogus. I'm going to try and look at it some time this week, but someone with more driver experience would probalby have more luck. -- Brooksk -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 18:29:47 2002 Delivered-To: freebsd-net@freebsd.org Received: from patrocles.silby.com (d188.as14.nwbl0.wi.voyager.net [169.207.136.62]) by hub.freebsd.org (Postfix) with ESMTP id DCA2537B417 for ; Mon, 25 Feb 2002 18:29:27 -0800 (PST) Received: from patrocles.silby.com (localhost [127.0.0.1]) by patrocles.silby.com (8.12.2/8.12.2) with ESMTP id g1PKXkZM021729; Mon, 25 Feb 2002 20:33:46 GMT (envelope-from silby@silby.com) Received: from localhost (silby@localhost) by patrocles.silby.com (8.12.2/8.12.2/Submit) with ESMTP id g1PKXin2021726; Mon, 25 Feb 2002 20:33:45 GMT X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Mon, 25 Feb 2002 20:33:44 +0000 (GMT) From: Mike Silbersack To: Yann GROSSEL Cc: freebsd-net@FreeBSD.ORG Subject: Re: dc TX underrun message In-Reply-To: <20020225113938.12bf08be.y.grossel@hexanet.fr> Message-ID: <20020225203050.U21168-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 25 Feb 2002, Yann GROSSEL wrote: > Hi, > > We have a new machine that is about to become a firewall. > > For now this machine is running but idle, that is, it has > no services running but sshd, and no default route. The > machine has been up for about 20 days, wihtout doing > anything. > > However 3 messages has been logged : > > Feb 5 14:30:18 blade /kernel: dc3: TX underrun -- increasing TX threshold > Feb 5 14:58:33 blade /kernel: dc3: TX underrun -- increasing TX threshold > Feb 19 09:38:39 blade /kernel: dc3: TX underrun -- increasing TX threshold > > What do these message mean ? Is there a hardware problem ? Don't worry too much about those messages; as far as I understand it, the default mode of the NIC is to start transmitting the packet as it is being DMA'd into the card. However, the default buffer size is too small, and the NIC gets ahead of the DMA transfer. Hence, the buffer is automatically being increased in size until the problem goes away. So, you've really only lost 4 packets to the problem, then it stabilized. You'll probably see the exact same behavior on every reboot. There have been patches to up the default buffer size and/or enable features to work around the problem on certain chipsets, but everything works well enough that I haven't been motivated to give them a serious look. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 19:22:18 2002 Delivered-To: freebsd-net@freebsd.org Received: from pivsbh2.ms.com (pivsbh2.ms.com [199.89.64.104]) by hub.freebsd.org (Postfix) with ESMTP id 96D9F37B417 for ; Mon, 25 Feb 2002 19:22:16 -0800 (PST) Received: from pivsbh2-idmz.ms.com (localhost [127.0.0.1]) by pivsbh2.ms.com (Postfix) with SMTP id 42FC593F8 for ; Mon, 25 Feb 2002 22:22:16 -0500 (EST) Received: from morganstanley.com (unknown [172.19.97.161]) by pivsbh2-idmz.ms.com (Postfix) with ESMTP id E6436AD7B for ; Mon, 25 Feb 2002 22:22:14 -0500 (EST) Message-ID: <3C7AFF65.D8F26C5@morganstanley.com> Date: Tue, 26 Feb 2002 11:22:14 +0800 From: Victor Tayer Reply-To: Victor.Tayer@morganstanley.com Organization: Morgan Stanley X-Mailer: Mozilla 4.76 [en]C-CCK-MCD MS4.76 V20001206.2 (WinNT; U) X-Accept-Language: en,ja MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: test only Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 19:27: 4 2002 Delivered-To: freebsd-net@freebsd.org Received: from sandbox.sandstorm.net (user-v3qtgdr.biz.mindspring.com [199.174.193.187]) by hub.freebsd.org (Postfix) with ESMTP id 2291037B402 for ; Mon, 25 Feb 2002 19:26:58 -0800 (PST) Received: from cjp by sandbox.sandstorm.net with local-esmtp (Exim 2.05 #2 (Debian)) id 16fYGK-0001DC-00; Mon, 25 Feb 2002 22:26:44 -0500 Date: Mon, 25 Feb 2002 22:26:44 -0500 (EST) From: Charles Peterman To: Jeff Lawton Cc: Brooks Davis , Subject: RE: 3com gigabit 3c996b-t In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In our recent tests of gigabit ethernet, cards with the BCM5700 chipset, offered the best performance. The two cards which satisfy that are the 3c996-T and one of the SysKonnect (sp?) cards. If you try hard (pricewatch) you can still find vendors willing to sell the 3c996-T instead of its brain dead pretender, the 3c996b-T. The 3c996b-T is based on the BCM5701, which does away with external memory, thus leaving the card with only 96k of cache. Read the bge source files for more on how this lobotomizes performance. On Mon, 25 Feb 2002, Jeff Lawton wrote: > Thank you, if you get a functioning driver please let me know. Does any one > know if I would be better off returning this card and getting a more > supported one like the intel pro1000 or dge-500tx. does any one have a > recommendation. My company wants to use this as a btrieve (I know yuk) file > server. We have a database that we have been using for years. This is an > temporary performance increase while we work on a client server system. > > Jeff Lawton > Ideal Solution, LLC > > -----Original Message----- > From: Brooks Davis [mailto:brooks@one-eyed-alien.net] > Sent: Monday, February 25, 2002 2:39 PM > To: Jeff Lawton > Cc: freebsd-net@FreeBSD.ORG > Subject: Re: 3com gigabit 3c996b-t > > On Fri, Feb 22, 2002 at 06:58:20PM -0500, Jeff Lawton wrote: > > Bge detects the card and it shows up on ifconfig it does not detect > > 1000basetx on autoselect even though the card and the switch both register > > 1000baset. I connected it to a 100base t port and it seems to work fine. > How > > do I get it to switch to 1000baset > > > > This is the bge section of ifconfig > > > > bge0: flags=8843 mtu 1500 > > options=3 > > inet 192.168.0.166 netmask 0xffffff00 broadcast 192.168.0.255 > > inet6 fe80::204:76ff:fee0:12a9%bge0 prefixlen 64 scopeid 0x1 > > ether 00:04:76:e0:12:a9 > > media: Ethernet autoselect (100baseTX ) > > status: active > > At least on the systems I'm trying to use 3C996B-T's on, the MII support > is clearly hosed. I'm seeing it probe 32 instances on ukphys which is > bogus. I'm going to try and look at it some time this week, but someone > with more driver experience would probalby have more luck. > > -- Brooksk > > -- > Any statement of the form "X is the one, true Y" is FALSE. > PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 21:38:51 2002 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 420F437B400; Mon, 25 Feb 2002 21:38:36 -0800 (PST) Received: from localhost ([3ffe:501:4819:2000:e028:ba95:b8bc:b5a5]) by shuttle.wide.toshiba.co.jp (8.11.6/8.9.1) with ESMTP id g1Q5cTo11094; Tue, 26 Feb 2002 14:38:29 +0900 (JST) Date: Tue, 26 Feb 2002 14:38:28 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Edwin Groothuis Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: IPv6-over-IPv4 problems since the upgrade to 4.5 In-Reply-To: References: <0D9185CE635BD511ACA50090277A6FCF1359DB@axcs18.cos.agilent.com> <20020216130842.A19081@energyhq.homeip.net> <20020217122510.D491@k7.mavetju.org> <20020222234829.F492@k7.mavetju.org> <20020223084616.G492@k7.mavetju.org> <20020225221827.F491@k7.mavetju.org> User-Agent: Wanderlust/2.7.5 (Too Funky) Emacs/21.1 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 52 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Finally I figured out the problem. The essential reason for this weirdness was that the kernel did not set the in_conninfo.inc_isipv6 member of a PCB entry correctly. As a result of this, once a cached route stored in the PCB has become invalid, the kernel would try to get a new route with an AF_INET destination. Neighbor solicitation messages on the gif link, which might invalidate the cached route, are also bogus, but they are not directly related to this particular problem. So, we should deal with this trouble as follows: 1. set the inc_isipv6 member correctly. The patch attached to this message should work for this (I checked the patch on a 4.5 RELEASE box). 2. prohibit the kernel from sending the bogus neighbor solicitations. This can be done by a patch I proposed last week in a different thread: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=345287+0+archive/2002/freebsd-net/20020224.freebsd-net BTW: I believe we should not rely on the inc_isipv6 member, which tends to introduce this type of bug. We should probably detect the correct family by the addresses themselves. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp *** tcp_usrreq.c.orig Tue Feb 26 14:00:22 2002 --- tcp_usrreq.c Tue Feb 26 14:05:43 2002 *************** *** 375,380 **** --- 375,381 ---- } inp->inp_vflag &= ~INP_IPV4; inp->inp_vflag |= INP_IPV6; + inp->inp_inc.inc_isipv6 = 1; if ((error = tcp6_connect(tp, nam, p)) != 0) goto out; error = tcp_output(tp); *** tcp_syncache.c.orig Tue Feb 26 10:52:39 2002 --- tcp_syncache.c Tue Feb 26 10:52:49 2002 *************** *** 552,557 **** --- 552,558 ---- /* * Insert new socket into hash list. */ + inp->inp_inc.inc_isipv6 = sc->sc_inc.inc_isipv6; #ifdef INET6 if (sc->sc_inc.inc_isipv6) { inp->in6p_laddr = sc->sc_inc.inc6_laddr; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 22:31: 9 2002 Delivered-To: freebsd-net@freebsd.org Received: from shark.amis.net (shark.amis.net [212.18.32.14]) by hub.freebsd.org (Postfix) with ESMTP id 4A37237B400; Mon, 25 Feb 2002 22:31:05 -0800 (PST) Received: from baracuda.amis.net (baracuda.amis.net [212.18.32.4]) by shark.amis.net (Postfix) with ESMTP id C73897C98; Tue, 26 Feb 2002 07:31:03 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by baracuda.amis.net (Postfix) with ESMTP id E8FD59B0F; Tue, 26 Feb 2002 07:31:01 +0100 (CET) Received: from titanic.medinet.si (titanic.medinet.si [212.18.42.5]) by baracuda.amis.net (Postfix) with ESMTP id 125BC9B0E; Tue, 26 Feb 2002 07:31:01 +0100 (CET) Received: by titanic.medinet.si (Postfix, from userid 1000) id 5851755412; Tue, 26 Feb 2002 07:30:59 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by titanic.medinet.si (Postfix) with ESMTP id 5577355411; Tue, 26 Feb 2002 07:30:59 +0100 (CET) Date: Tue, 26 Feb 2002 07:30:59 +0100 (CET) From: Blaz Zupan X-X-Sender: blaz@titanic.medinet.si To: Michael Sierchio Cc: Ross Finlayson , , Subject: Re: Sudden "wi" errors in 4.5-STABLE In-Reply-To: <3C7ACB06.6030403@tenebras.com> Message-ID: <20020226072729.J79498-100000@titanic.medinet.si> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > Has anyone else seen this happen? Does anyone have a fix? > > Yes. These disappeared when I installed the latest rev. of the > ORiNOCO driver/firmware. You'll need a Windoze machine to apply > the update. I'm experiencing the same problems. It started out on a new customers' machine. We thought it might be the hardware combination so we swapped the machine out with a known working box (taken out of service on another site the day before) and it started acting the same! To make matters worse, two days ago another customers machine started acting up, this time a 3.3-RELEASE BOX (yeah, I know it should be ugraded). It was running for months (years!) without trouble and now it's suddenly acting up without any visible evidence. The only real change was that we repositioned the Yagi antenna to point at another access point. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 22:40:17 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id AE31937B405; Mon, 25 Feb 2002 22:40:13 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020226064013.XVWF1214.rwcrmhc54.attbi.com@InterJet.elischer.org>; Tue, 26 Feb 2002 06:40:13 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA92055; Mon, 25 Feb 2002 22:37:44 -0800 (PST) Date: Mon, 25 Feb 2002 22:37:43 -0800 (PST) From: Julian Elischer To: Blaz Zupan Cc: Michael Sierchio , Ross Finlayson , freebsd-mobile@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Sudden "wi" errors in 4.5-STABLE In-Reply-To: <20020226072729.J79498-100000@titanic.medinet.si> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org new microwave oven nearby? On Tue, 26 Feb 2002, Blaz Zupan wrote: > > > Has anyone else seen this happen? Does anyone have a fix? > > > > Yes. These disappeared when I installed the latest rev. of the > > ORiNOCO driver/firmware. You'll need a Windoze machine to apply > > the update. > > I'm experiencing the same problems. It started out on a new customers' > machine. We thought it might be the hardware combination so we swapped the > machine out with a known working box (taken out of service on another site the > day before) and it started acting the same! To make matters worse, two days > ago another customers machine started acting up, this time a 3.3-RELEASE BOX > (yeah, I know it should be ugraded). It was running for months (years!) > without trouble and now it's suddenly acting up without any visible evidence. > The only real change was that we repositioned the Yagi antenna to point at > another access point. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 25 23:13: 0 2002 Delivered-To: freebsd-net@freebsd.org Received: from shark.amis.net (shark.amis.net [212.18.32.14]) by hub.freebsd.org (Postfix) with ESMTP id 5CC6237B49D; Mon, 25 Feb 2002 23:11:57 -0800 (PST) Received: from baracuda.amis.net (baracuda.amis.net [212.18.32.4]) by shark.amis.net (Postfix) with ESMTP id 879C17CCE; Tue, 26 Feb 2002 08:11:53 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by baracuda.amis.net (Postfix) with ESMTP id 455259B09; Tue, 26 Feb 2002 08:11:53 +0100 (CET) Received: from titanic.medinet.si (titanic.medinet.si [212.18.42.5]) by baracuda.amis.net (Postfix) with ESMTP id 5DFAD9B08; Tue, 26 Feb 2002 08:11:52 +0100 (CET) Received: by titanic.medinet.si (Postfix, from userid 1000) id 4415555411; Tue, 26 Feb 2002 08:11:51 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by titanic.medinet.si (Postfix) with ESMTP id 3CDE755404; Tue, 26 Feb 2002 08:11:51 +0100 (CET) Date: Tue, 26 Feb 2002 08:11:51 +0100 (CET) From: Blaz Zupan X-X-Sender: blaz@titanic.medinet.si To: Julian Elischer Cc: freebsd-mobile@FreeBSD.ORG, Subject: Re: Sudden "wi" errors in 4.5-STABLE In-Reply-To: Message-ID: <20020226080956.U79498-100000@titanic.medinet.si> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > new microwave oven nearby? Don't think so. Also, putting the same card into one of those ethernet converters (the one where you can put a WaveLAN card into the slot and you just get ethernet out) makes it work just fine with the same firmware and in the same environment. Sigh... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 26 5: 0: 3 2002 Delivered-To: freebsd-net@freebsd.org Received: from ns1.hexanet.fr (ns1.hexanet.fr [194.98.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9D35437B400 for ; Tue, 26 Feb 2002 04:59:57 -0800 (PST) Received: from snowflake (olrick@snowflake.hexanet.fr [194.98.140.144]) by ns1.hexanet.fr (8.9.3/8.9.3) with SMTP id NAA62407 for ; Tue, 26 Feb 2002 13:59:56 +0100 (CET) (envelope-from y.grossel@hexanet.fr) Date: Tue, 26 Feb 2002 13:59:57 +0100 From: Yann GROSSEL To: freebsd-net@FreeBSD.ORG Subject: dc TX underrun message, again Message-Id: <20020226135957.76d64546.y.grossel@hexanet.fr> Organization: Hexanet X-Mailer: Sylpheed version 0.7.2 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Thanks to all people who have answered me about my previous mail (yesterday) about "TX underrun" messages. Today we put this firewall box in production mode. Almost immediately, new messages have been logged (as expected) : Feb 26 13:03:15 blade /kernel: dc2: TX underrun -- increasing TX threshold Feb 26 13:03:18 blade /kernel: dc2: TX underrun -- increasing TX threshold Feb 26 13:03:31 blade /kernel: dc2: TX underrun -- increasing TX threshold Feb 26 13:04:23 blade /kernel: dc3: TX underrun -- increasing TX threshold Feb 26 13:04:23 blade /kernel: dc3: TX underrun -- increasing TX threshold Feb 26 13:05:40 blade /kernel: dc3: TX underrun -- increasing TX threshold But after a few minutes of activity : Feb 26 13:19:22 blade /kernel: dc3: TX underrun -- using store and forward mode Feb 26 13:24:33 blade /kernel: dc2: TX underrun -- using store and forward mode Are these new messages indicating a more serious problem ? Or is it harmless to ignore them ? Thanks for any answers Yann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 26 8:16:16 2002 Delivered-To: freebsd-net@freebsd.org Received: from patrocles.silby.com (d150.as15.nwbl0.wi.voyager.net [169.207.136.88]) by hub.freebsd.org (Postfix) with ESMTP id 64F9637B417 for ; Tue, 26 Feb 2002 08:15:52 -0800 (PST) Received: from patrocles.silby.com (localhost [127.0.0.1]) by patrocles.silby.com (8.12.2/8.12.2) with ESMTP id g1QAJqZM025877; Tue, 26 Feb 2002 10:19:52 GMT (envelope-from silby@silby.com) Received: from localhost (silby@localhost) by patrocles.silby.com (8.12.2/8.12.2/Submit) with ESMTP id g1QAJePk025874; Tue, 26 Feb 2002 10:19:46 GMT X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Tue, 26 Feb 2002 10:19:40 +0000 (GMT) From: Mike Silbersack To: Yann GROSSEL Cc: freebsd-net@FreeBSD.ORG Subject: Re: dc TX underrun message, again In-Reply-To: <20020226135957.76d64546.y.grossel@hexanet.fr> Message-ID: <20020226101713.S25801-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 26 Feb 2002, Yann GROSSEL wrote: > But after a few minutes of activity : > > Feb 26 13:19:22 blade /kernel: dc3: TX underrun -- using store and forward mode > Feb 26 13:24:33 blade /kernel: dc2: TX underrun -- using store and forward mode > > Are these new messages indicating a more serious problem ? > Or is it harmless to ignore them ? > > Thanks for any answers > > Yann That means, "I give up, I'm just going to wait until the whole packet gets sent to me from the PCI bus before I even try sending it over the network." So yes, your system is quite busy. However, it's still not anything to worry about. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 26 10: 8:54 2002 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 1552637B43F for ; Tue, 26 Feb 2002 10:08:20 -0800 (PST) Received: from localhost ([3ffe:501:4819:2000:f8ad:ffb5:f9be:fffd]) by shuttle.wide.toshiba.co.jp (8.11.6/8.9.1) with ESMTP id g1Q9RTo12949; Tue, 26 Feb 2002 18:27:29 +0900 (JST) Date: Tue, 26 Feb 2002 18:27:28 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Aaron Angel Cc: net@FreeBSD.ORG Subject: Re: prefix command outdated? In-Reply-To: <3C796E9C.1010306@myrealbox.com> References: <3C796E9C.1010306@myrealbox.com> User-Agent: Wanderlust/2.7.5 (Too Funky) Emacs/21.1 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Dispatcher: imput version 980905(IM100) Lines: 38 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Sun, 24 Feb 2002 17:52:12 -0500,=20 >>>>> Aaron Angel said: > Out of curiousity, why is the prefix command being phased out? =46rom KAME's latest prefix(8): HISTORY The prefix command first appeared in WIDE/KAME IPv6 protocol stack kit. Previously, this command was used to manipulate prefixes separately fr= om interface identifiers, intending to be used for prefix renumbering. H= ow- ever, it had been known that the manipulation mechanism was not friend= ly with traditional address management engine in the kernel. Thus, the K= AME developers decided to invalidate the prefix manipulation mechanism, and to clarify the entire address/prefix manipulation in February 2001. Since then, this command has almost been obsoleted. All users should = now use ifconfig(8). (Hmm...FreeBSD's releases still have an old version of the man page. We should merge the man page as well.) > And is=20 > there a way to assign an address based on a prefix and EU64 address to a = > device using ifconfig, or do I have to write a script? I haven't found=20 > anything in the man pages regarding this. The current prefix(8) is exactly the script for this purpose. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 26 10:29:31 2002 Delivered-To: freebsd-net@freebsd.org Received: from cheer.mahoroba.org (flets19-017.kamome.or.jp [218.45.19.17]) by hub.freebsd.org (Postfix) with ESMTP id D665737B425 for ; Tue, 26 Feb 2002 10:29:17 -0800 (PST) Received: from mille.mahoroba.org (IDENT:yFgM0H5aWHlmFkDJeYOGddKV6nnlwkjLcuXrk8p8fohYAEQfnYD7gibsPYcfeAtO@mille.mahoroba.org [IPv6:2001:200:301:0:202:2dff:fe0a:6bee]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.2/8.12.2) with ESMTP/inet6 id g1QITEEv000611 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 27 Feb 2002 03:29:15 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 27 Feb 2002 03:29:14 +0900 Message-ID: From: Hajimu UMEMOTO To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= Cc: Aaron Angel , net@FreeBSD.ORG Subject: Re: prefix command outdated? In-Reply-To: References: <3C796E9C.1010306@myrealbox.com> User-Agent: xcite1.38> Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) X-Operating-System: FreeBSD 4.5-RELEASE MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>> Tue, 26 Feb 2002 18:27:28 +0900 >>> JINMEI Tatuya said: jinmei> (Hmm...FreeBSD's releases still have an old version of the man page. jinmei> We should merge the man page as well.) It was my mistake during last KAME mergre. I'll merge recent prefix(8) manpage from KAME. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 26 15:49:52 2002 Delivered-To: freebsd-net@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 7DADE37B41C for ; Tue, 26 Feb 2002 15:49:50 -0800 (PST) Received: from user-uiveqo2.dsl.mindspring.com ([165.247.107.2] helo=compaq) by tisch.mail.mindspring.net with smtp (Exim 3.33 #1) id 16frKj-0007pr-00; Tue, 26 Feb 2002 18:48:33 -0500 Message-ID: <00b601c1bebb$12c2c280$026bf7a5@compaq> From: "Naga R Narayanaswamy" To: "Ramit Bhalla" , "FreeBSD Net" References: Subject: Re: Extent of IPv6 support. Date: Tue, 26 Feb 2002 06:45:10 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > For instance advanced stuff like Border Gateway protocol, SNMP, firewalling > etc - do they support IPv6 ?? BGP, SNMP does not ship with FreeBSD. Zebra is a good open source routing stack and works on FreeBsd. (www.zebra.org) It has support for RIP,OSPF and BGP for IPv4 and v6. By default, IPv6 is even enabled. The only catch is it is distributed under GNU general public license, not the FreeBSD style license. Naga Crofton, MD 21114 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 26 15:58:14 2002 Delivered-To: freebsd-net@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.143.238.93]) by hub.freebsd.org (Postfix) with SMTP id 0656637B41A for ; Tue, 26 Feb 2002 15:58:09 -0800 (PST) Received: (qmail 615 invoked by uid 1001); 27 Feb 2002 09:51:27 +1000 X-Posted-By: GJB-Post 2.23 27-Nov-2001 X-Operating-System: FreeBSD 4.2-RELEASE i386 X-Uptime: 48 days, 16:12 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-GPG-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-PGP-Public-Keys: http://www.gbch.net/keys.html Message-Id: Date: Wed, 27 Feb 2002 09:51:26 +1000 From: Greg Black To: "Matthew Emmerton" Cc: freebsd-net@freebsd.org Subject: Re: ppp -nat fails with adsl, but ok with modem References: <00ad01c1bd71$98237820$1200a8c0@gsicomp.on.ca> <001e01c1bd8a$22f347b0$1200a8c0@gsicomp.on.ca> In-reply-to: of Mon, 25 Feb 2002 10:20:05 +1000 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Greg Black wrote: | "Matthew Emmerton" wrote: | | | > | > I've had ppp -nat working just fine over a normal modem link, | | > | > but it is not working at all well on my ADSL link to the same | | > | > provider. | | > | > | | > | > To quantify "not working at all well", although I can ping and | | > | > traceroute ok from the hosts on my LAN, HTTP and FTP traffic is | | > | > so slow and bursty as to be useless. Clicking on a link with | | > | > Netscape will see short bursts of data with long periods (of a | | > | > minute or more) where it says "stalled". | | > | > | | > | > Clicking on from | | > | > my gateway host gets the page in an eye-blink, but on the NAT | | > | > hosts, it will take 40 seconds to load the top banner and the | | > | > "FreeBSD GNOME News Flash" heading, then another delay of 40 or | | > | > so seconds before the rest of the page will be displayed. Even | | > | > then, Netscape thinks it has stalled and keeps waiting for the | | > | > last bit of data. | | > | > | | > | > With FTP, a small transfer (e.g., a directory listing of / on | | > | > ftp.freebsd.org) will complete normally; but something slightly | | > | > larger (e.g., a listing of /pub/FreeBSD on the same server), | | > | > will produce: | | > | > | | > | > ftp> cd /pub/FreeBSD | | > | > 250 CWD command successful. | | > | > ftp> dir | | > | > 200 PORT command successful. | | > | > 150 Opening ASCII mode data connection for '/bin/ls'. | | > | > ftp: netin: Connection reset by peer | | > | > 226 Transfer complete. | | > | > ftp> quit | | > | > 421 Timeout (60 seconds): closing control connection. | | > | > | | > | > If I do the same things from the host that is connected to the | | > | > modem(s), everything works fine, for both types of connections. | | > | > | | > | > I'm finding this very frustrating, and I'm wondering if there's | | > | > something weird about PPPoE with the ADSL link that needs some | | > | > special magic in order for things to work properly. | | > | > | | > | > If anybody can point me at the truth, I'd be most grateful. | > | > | | > | > Alternatively, if anybody can suggest steps I could take to | | > | > identify the nature of the problem, that would also be most | | > | > welcome. | | > | | | > | What version of FreeBSD are you using? The ppp included in early 4.x | | > | distributions doesn't have the TCP MSS fixup code that is required to | | > | make | | > | things work properly with a PPPoE connection, and cause the kinds of | | > | symptoms that you describe. | | > | | > The NAT box is running 4.2-RELEASE -- is that a problem? | | | | Yes. This problem was first fixed in 4.2-STABLE. There are two safe ways to | | fix this: | | - upgrade to a newer -RELEASE or -STABLE | | - run the tcpmssd program (which is in the ports collection - | | /usr/ports/net/tcpmssd) | | I'll try tcpmssd first -- I have some other systems in a similar | situation that are running 4.1-RELEASE and can't be upgraded, so my | solution needs to work for them too. Thanks for the information. OK, I have setup tcpmssd on my 4.1-R and 4.2-R NAT boxes and it seems to be doing the job, but I am seeing some worrying log messages on one of the machines: tcpmssd: write to divert socket failed: Message too long There have been 26 of these over 10 hours during which 4 Mbytes of data in 21k packets have been through the divert rule. Is there a fix, or do I just ignore it in the hope that things will sort themselves out? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 27 0:44:16 2002 Delivered-To: freebsd-net@freebsd.org Received: from sln01.megadat.com (exchange.megadat.com [195.22.224.154]) by hub.freebsd.org (Postfix) with ESMTP id 848FC37B417; Wed, 27 Feb 2002 00:44:05 -0800 (PST) Received: by sln01.megadat.com with Internet Mail Service (5.5.2653.19) id <15X2T9NN>; Wed, 27 Feb 2002 10:43:53 +0200 Message-ID: <8E9035BABCA0514EB0E574B6A7082FC30531C2@sln01.megadat.com> From: Girnet Vladimir To: "'net@freebsd.org'" Cc: "'questions@freebsd.org'" Subject: Intel EtherExpress card problems Date: Wed, 27 Feb 2002 10:43:47 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="koi8-r" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi I have this ISA card: EtherExpress 10 ISA (TPE) Chip on this card is : 82595 As I found in hardware supported by FreeBSD, this chip is fully supported. But, I cannot install it. Booting with kernel.GENERIC, I got this message: "ex0: manual config... ifmedia_set: no match for 0x23/0xFFFFFFFF panic: ifmedia_set" Please, help me to solve this problem! Are there any ways to install this card under FreeBSD? > Looking forward to your reply, > Vladimir Girnet > "MEGADAT.COM" S.R.L. > MOLDOVA, Chisinau > www.megadat.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 27 3:36:40 2002 Delivered-To: freebsd-net@freebsd.org Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by hub.freebsd.org (Postfix) with ESMTP id 02B5237B400 for ; Wed, 27 Feb 2002 03:36:36 -0800 (PST) Received: from sauna.arved.de (sauna.arved.de [192.168.2.4]) by 21322530218.direct.eti.at (8.11.6/8.11.6) with ESMTP id g1RBigG06179 for ; Wed, 27 Feb 2002 12:44:43 +0100 (CET) (envelope-from tilman@arved.de) Received: (from tilman@localhost) by sauna.arved.de (8.11.6/8.11.6) id g1RBaXR03441; Wed, 27 Feb 2002 12:36:33 +0100 (CET) (envelope-from tilman@arved.de) X-Authentication-Warning: sauna.arved.de: tilman set sender to tilman@arved.de using -f Date: Wed, 27 Feb 2002 12:36:33 +0100 From: Tilman Linneweh To: freebsd-net@freebsd.org Subject: WLAN Kernelpatch from dachb0den.com merging into FreeBSD? Message-Id: <20020227123633.0e291826.tilman@arved.de> X-Mailer: Sylpheed version 0.7.2 (GTK+ 1.2.10; i386--freebsd4.5) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, The people at dachb0den.com have written the bsd-airtools. http://www.dachb0den.com/projects/bsd-airtools.html With the bsd-airtools tarball comes a kernel-patch against 4.4 to get more information from the wi-Driver. Are there any plans to integrate this patch (or something equivalent) into freebsd? regards arved To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 27 4:26:54 2002 Delivered-To: freebsd-net@freebsd.org Received: from brain.cc.rsu.ru (brain.cc.rsu.ru [195.208.252.154]) by hub.freebsd.org (Postfix) with ESMTP id 7827537B402 for ; Wed, 27 Feb 2002 04:26:46 -0800 (PST) Received: from localhost (os@localhost [127.0.0.1]) by brain.cc.rsu.ru (8.11.6/8.11.4) with ESMTP id g1RCQXb02283 for ; Wed, 27 Feb 2002 15:26:33 +0300 (MSK) (envelope-from os@rsu.ru) Date: Wed, 27 Feb 2002 15:26:33 +0300 (MSK) From: Oleg Sharoiko X-X-Sender: os@brain.cc.rsu.ru To: freebsd-net@freebsd.org Subject: Patches to fix MD5 authentication in routed Message-ID: <20020227145812.F425-200000@brain.cc.rsu.ru> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1494285748-1014812048=:425" Content-ID: <20020227152304.R425@brain.cc.rsu.ru> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1494285748-1014812048=:425 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: <20020227151658.H425@brain.cc.rsu.ru> Hello! Recently I've posted a patch on this list to fix the bug in the MD5 authentication in routed. I got no answers though :( Wold you please be so kind as to check my patch and commit it if it's ok or send me e-mail if this patch is wrong. The patch is attached to the message. -- Oleg Sharoiko. Software and Network Engineer Computer Center of Rostov State University. --0-1494285748-1014812048=:425 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="routed.diff" Content-Transfer-Encoding: BASE64 Content-ID: <20020227151408.V425@brain.cc.rsu.ru> Content-Description: Content-Disposition: ATTACHMENT; FILENAME="routed.diff" LS0tIGluY2x1ZGUvcHJvdG9jb2xzL3JvdXRlZC5oCVN1biBTZXAgIDUgMTc6 NDM6MzEgMTk5OQ0KKysrIGluY2x1ZGUvcHJvdG9jb2xzL3JvdXRlZC5oCVdl ZCBGZWIgMjcgMTE6NTg6MTYgMjAwMg0KQEAgLTg0LDYgKzg0LDcgQEANCiAN CiAvKiBSSVB2MiBhdXRoZW50aWNhdGlvbiAqLw0KIHN0cnVjdCBuZXRhdXRo IHsNCisjZGVmaW5lICAgICBSSVBfQVVUSF9IRFJfTEVOIDQNCiAJdV9pbnQx Nl90ICAgYV9mYW1pbHk7CQkvKiBhbHdheXMgUklQX0FGX0FVVEggKi8NCiAJ dV9pbnQxNl90ICAgYV90eXBlOw0KICNkZWZpbmUJICAgIFJJUF9BVVRIX05P TkUgICAwDQotLS0gc2Jpbi9yb3V0ZWQub3JnL2lucHV0LmMJV2VkIEZlYiAy MCAxMDo0ODo1NiAyMDAyDQorKysgc2Jpbi9yb3V0ZWQvaW5wdXQuYwlXZWQg RmViIDIwIDExOjE1OjIxIDIwMDINCkBAIC05NjcsNyArOTY3LDcgQEANCiAJ CQkgKi8NCiAJCQlpZiAoVFJBQ0VQQUNLRVRTKSB7DQogCQkJCWlmIChOQS0+ YXUuYV9tZDUubWQ1X2F1dGhfbGVuDQotCQkJCSAgICAhPSBSSVBfQVVUSF9N RDVfTEVOKQ0KKwkJCQkgICAgIT0gUklQX0FVVEhfSERSX0xFTiArIFJJUF9B VVRIX01ENV9MRU4pDQogCQkJCQltc2dsaW0odXNlX2F1dGhwLCBmcm9tLA0K IAkJCQkJICAgICAgICJ1bmtub3duIE1ENSBSSVB2MiBhdXRoIGxlbiAlI3gi DQogCQkJCQkgICAgICAgIiBpbnN0ZWFkIG9mICUjeCBmcm9tICVzIiwNCkBA IC05ODksNyArOTg5LDcgQEANCiAJCQl9DQogDQogCQkJTUQ1SW5pdCgmbWQ1 X2N0eCk7DQotCQkJTUQ1VXBkYXRlKCZtZDVfY3R4LCAodV9jaGFyICopcmlw LCBsZW4pOw0KKwkJCU1ENVVwZGF0ZSgmbWQ1X2N0eCwgKHVfY2hhciAqKXJp cCwgbGVuK1JJUF9BVVRIX0hEUl9MRU4pOw0KIAkJCU1ENVVwZGF0ZSgmbWQ1 X2N0eCwgYXAtPmtleSwgUklQX0FVVEhfTUQ1X0xFTik7DQogCQkJTUQ1Rmlu YWwoaGFzaCwgJm1kNV9jdHgpOw0KIAkJCWlmICghbWVtY21wKGhhc2gsIG5h Mi0+YXUuYXVfcHcsIHNpemVvZihoYXNoKSkpDQotLS0gc2Jpbi9yb3V0ZWQu b3JnL291dHB1dC5jCVdlZCBGZWIgMjAgMTA6NDc6NDggMjAwMg0KKysrIHNi aW4vcm91dGVkL291dHB1dC5jCVdlZCBGZWIgMjAgMTA6NTA6MDEgMjAwMg0K QEAgLTMwMyw3ICszMDMsNyBAQA0KIAluYTItPmFfdHlwZSA9IGh0b25zKDEp Ow0KIAluYS0+YXUuYV9tZDUubWQ1X3BrdF9sZW4gPSBodG9ucyhsZW4pOw0K IAlNRDVJbml0KCZtZDVfY3R4KTsNCi0JTUQ1VXBkYXRlKCZtZDVfY3R4LCAo dV9jaGFyICopd2ItPmJ1ZiwgbGVuKTsNCisJTUQ1VXBkYXRlKCZtZDVfY3R4 LCAodV9jaGFyICopd2ItPmJ1ZiwgbGVuICsgUklQX0FVVEhfSERSX0xFTik7 DQogCU1ENVVwZGF0ZSgmbWQ1X2N0eCwgYXAtPmtleSwgUklQX0FVVEhfTUQ1 X0xFTik7DQogCU1ENUZpbmFsKG5hMi0+YXUuYXVfcHcsICZtZDVfY3R4KTsN CiAJd2ItPm4rKzsNCg== --0-1494285748-1014812048=:425-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 27 5: 4:36 2002 Delivered-To: freebsd-net@freebsd.org Received: from alijku01.edvz.uni-linz.ac.at (alijku01.edvz.uni-linz.ac.at [140.78.2.62]) by hub.freebsd.org (Postfix) with ESMTP id E302537B400 for ; Wed, 27 Feb 2002 05:04:30 -0800 (PST) Received: from control.edvz.uni-linz.ac.at (k000181@control.edvz.uni-linz.ac.at [140.78.4.60]) by alijku01.edvz.uni-linz.ac.at (8.12.1/8.12.1) with ESMTP id g1RD4TuV032712 for ; Wed, 27 Feb 2002 14:04:29 +0100 Date: Wed, 27 Feb 2002 14:04:27 +0100 (CET) From: Ferdinand Goldmann X-X-Sender: k000181@control.edvz.uni-linz.ac.at To: freebsd-net@freebsd.org Subject: DGE-500SX Gigabit Ethernet Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear *, A colleague and I have tried getting a DGE-500SX to work under FreeBSD 4.5-STABLE. However, without much success. :-( The card is recognized by the kernel: Feb 25 16:41:05 wid /kernel: lge0: port 0xa800-0xa8ff mem 0xdd800000-0xdd8003ff irq 9 at device 13.0 on pci0 Feb 25 16:41:05 wid /kernel: lge0: Ethernet address: 00:50:ba:ec:45:b5 Feb 25 16:41:05 wid /kernel: miibus1: on lge0 Feb 25 16:41:05 wid /kernel: xmphy0: on miibus1 Feb 25 16:41:05 wid /kernel: xmphy0: 1000baseSX, 1000baseSX-FDX, auto lge0: flags=8843 mtu 1500 options=1 inet6 fe80::250:baff:feec:45b5%lge0 prefixlen 64 scopeid 0x2 inet 140.78.6.66 netmask 0xffffff00 broadcast 140.78.6.255 ether 00:50:ba:ec:45:b5 media: Ethernet 1000baseSX status: active However, when trying to ping something, I never get replies, only the Opkts increase: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lge0 1500 00:50:ba:ec:45:b5 0 0 45 0 0 lge0 1500 fe80:2::250 fe80:2::250:baff: 0 - 0 - - lge0 1500 140.78.6/24 140.78.6.66 0 - 6 - - Has anyone got this card to work? I could not find much about it in the mailing list/Usenet archives. TIA for any pointers to further information or useful tips! -- >> Ferdinand Goldmann >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at >> Tel. : +43/732/2468/9398 Fax. : +43/732/2468/9397 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 27 13: 8:11 2002 Delivered-To: freebsd-net@freebsd.org Received: from lh.synack.net (lh.synack.net [204.152.188.7]) by hub.freebsd.org (Postfix) with ESMTP id 45AD037B402 for ; Wed, 27 Feb 2002 13:08:04 -0800 (PST) Received: from lh.synack.net (bbraun@localhost) by lh.synack.net (8.11.6/8.11.6) with ESMTP id g1RL50J21344 for ; Wed, 27 Feb 2002 13:05:00 -0800 Message-Id: <200202272105.g1RL50J21344@lh.synack.net> To: freebsd-net@FreeBSD.ORG From: Rob Braun Subject: proposed changes to getnameinfo() implementation Date: Wed, 27 Feb 2002 13:04:59 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org getnameinfo() takes a struct sockaddr pointer, and a length parameter for the amount of memory pointed to by the struct sockaddr pointer. The current FreeBSD implementation of getnameinfo() does 2 problematic checks against the length parameter. First, it makes sure the length parameter is equal to the length specified in the passed in sockaddr structure. This is problematic because the length parameter refers to the amount of memory pointed to by the first parameter, and the struct sockaddr sa_len field is used to specify the size of the sockaddr structure, since there are different types of sockaddr structures with different lengths. I propose to change this exact match comparison to ensure that the length passed in is at least what the sa_len field is. This will allow a larger structure to be passed in than the size of the sockaddr structure for the desired protocol. The second comparison is similar to the first. The passed in length field is compared to the size of the sockaddr structure for the address family you're using. Again, I propose to make sure that the passed in length is at least as large as the known structure length. With these changes, it still ensure that enough memory is available to proceed, but it also allows more memory than is needed. Rob diff -u -d -b -w -u -d -r1.7 getnameinfo.c --- getnameinfo.c 2001/02/15 10:35:54 1.7 +++ getnameinfo.c 2002/02/27 20:48:14 @@ -119,7 +119,7 @@ if (sa == NULL) return ENI_NOSOCKET; - if (sa->sa_len != salen) + if (sa->sa_len > salen) return ENI_SALEN; family = sa->sa_family; @@ -131,7 +131,7 @@ return ENI_FAMILY; found: - if (salen != afd->a_socklen) + if (salen < afd->a_socklen) return ENI_SALEN; /* network byte order */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 27 20:21: 8 2002 Delivered-To: freebsd-net@freebsd.org Received: from topaz.mdcc.cx (topaz.mdcc.cx [212.204.230.141]) by hub.freebsd.org (Postfix) with ESMTP id A89DA37B41C; Wed, 27 Feb 2002 20:21:05 -0800 (PST) Received: from k7.mavetju.org (topaz.mdcc.cx [212.204.230.141]) by topaz.mdcc.cx (Postfix) with ESMTP id A77552B703; Thu, 28 Feb 2002 05:21:03 +0100 (CET) Received: by k7.mavetju.org (Postfix, from userid 1001) id 1CCD335B; Thu, 28 Feb 2002 15:20:57 +1100 (EST) Date: Thu, 28 Feb 2002 15:20:57 +1100 From: Edwin Groothuis To: "JINMEI Tatuya / ?$B?@L@C#:H?(B" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: IPv6-over-IPv4 problems since the upgrade to 4.5 Message-ID: <20020228152057.A619@k7.mavetju.org> Mail-Followup-To: Edwin Groothuis , "JINMEI Tatuya / ?$B?@L@C#:H?(B" , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG References: <20020216130842.A19081@energyhq.homeip.net> <20020217122510.D491@k7.mavetju.org> <20020222234829.F492@k7.mavetju.org> <20020223084616.G492@k7.mavetju.org> <20020225221827.F491@k7.mavetju.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jinmei@isl.rdc.toshiba.co.jp on Tue, Feb 26, 2002 at 02:38:28PM +0900 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello Jinmei, On Tue, Feb 26, 2002 at 02:38:28PM +0900, JINMEI Tatuya / ?$B?@L@C#:H?(B wrote: > Finally I figured out the problem. Thanks for these two patches, it works like a charm now! Edwin -- Edwin Groothuis | Personal website: http://www.MavEtJu.org edwin@mavetju.org | Interested in MUDs? Visit Fatal Dimensions: ------------------+ http://www.FatalDimensions.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 27 20:24:42 2002 Delivered-To: freebsd-net@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 631F337B417 for ; Wed, 27 Feb 2002 20:24:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by cs.rice.edu (Postfix) with ESMTP id 26016188A for ; Wed, 27 Feb 2002 22:24:35 -0600 (CST) Received: from frosty.cs.rice.edu (frosty.cs.rice.edu [128.42.1.20]) by cs.rice.edu (Postfix) with ESMTP id CCA41188B for ; Wed, 27 Feb 2002 22:24:32 -0600 (CST) Received: from localhost (hykim@localhost) by frosty.cs.rice.edu (8.9.3+Sun/8.9.0) with ESMTP id WAA20938 for ; Wed, 27 Feb 2002 22:24:27 -0600 (CST) X-Authentication-Warning: frosty.cs.rice.edu: hykim owned process doing -bs Date: Wed, 27 Feb 2002 22:24:27 -0600 (CST) From: Hyong-Youb Kim To: Subject: kern.ipc.maxsockets Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20010714 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The server machine I am working on has 2GB of memory and 1.6G Athlon CPU. It currently runs FreeBSD-4.3-RELEASE. I have been trying to get kern.ipc.maxsockets above 64K. I have tried 128K, 100K, and so on. 80K worked but for all others, the system halted during the boot saying 'pager_swap_zone = null'. I am guessing that the kernel zone allocator cannot allocate enough map space for the pager swap? I am wondering if anyone knows how to get around this problem. Thanks. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 27 20:58:37 2002 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 9DBF237B41A for ; Wed, 27 Feb 2002 20:58:34 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 7F453AE24F; Wed, 27 Feb 2002 20:58:34 -0800 (PST) Date: Wed, 27 Feb 2002 20:58:34 -0800 From: Alfred Perlstein To: Hyong-Youb Kim Cc: freebsd-net@FreeBSD.ORG Subject: Re: kern.ipc.maxsockets Message-ID: <20020228045834.GA80761@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Hyong-Youb Kim [020227 20:24] wrote: > > > The server machine I am working on has 2GB of memory and 1.6G Athlon CPU. > It currently runs FreeBSD-4.3-RELEASE. > I have been trying to get kern.ipc.maxsockets above 64K. I have tried > 128K, 100K, and so on. 80K worked but for all others, the system halted > during the boot saying 'pager_swap_zone = null'. I am guessing that the > kernel zone allocator cannot allocate enough map space for the pager swap? > I am wondering if anyone knows how to get around this problem. Thanks. 4-stable has a fix for this. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 27 22: 7:59 2002 Delivered-To: freebsd-net@freebsd.org Received: from cheer.mahoroba.org (flets19-017.kamome.or.jp [218.45.19.17]) by hub.freebsd.org (Postfix) with ESMTP id 5F82E37B417; Wed, 27 Feb 2002 22:07:53 -0800 (PST) Received: from localhost (IDENT:BHicxuhNOymoeoWnBlYX0/gHakUHd03zswn/U2RkwNHFclDmiGKNc1tSepTCtD9D@localhost [IPv6:::1]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.2/8.12.2) with ESMTP/inet6 id g1S67iEv093424 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 28 Feb 2002 15:07:48 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Thu, 28 Feb 2002 15:07:44 +0900 Message-ID: From: Hajimu UMEMOTO To: Rob Braun Cc: freebsd-net@FreeBSD.ORG Subject: Re: proposed changes to getnameinfo() implementation In-Reply-To: <200202272105.g1RL50J21344@lh.synack.net> References: <200202272105.g1RL50J21344@lh.synack.net> User-Agent: xcite1.38> Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) X-Operating-System: FreeBSD 4.5-RELEASE MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, >>>>> On Wed, 27 Feb 2002 13:04:59 -0800 >>>>> Rob Braun said: bbraun> getnameinfo() takes a struct sockaddr pointer, and a length bbraun> parameter for the amount of memory pointed to by the struct bbraun> sockaddr pointer. No, the second parameter is not the amount of memory pointed to by the struct sockaddr pointer. It is the size of the struct sockaddr according to the address family. bbraun> The current FreeBSD implementation of getnameinfo() does bbraun> 2 problematic checks against the length parameter. First, bbraun> it makes sure the length parameter is equal to the length bbraun> specified in the passed in sockaddr structure. This is bbraun> problematic because the length parameter refers to the bbraun> amount of memory pointed to by the first parameter, and bbraun> the struct sockaddr sa_len field is used to specify the bbraun> size of the sockaddr structure, since there are different bbraun> types of sockaddr structures with different lengths. RFC2553 defines two types of struct sockaddr, one has sa_len and the other doesn't has it. Though we *BSD has sa_len, non-BSD doesn't have it. bbraun> I propose to change this exact match comparison to ensure bbraun> that the length passed in is at least what the sa_len bbraun> field is. This will allow a larger structure to be passed bbraun> in than the size of the sockaddr structure for the desired bbraun> protocol. It shouldn't. Though we actually doesn't need the second parameter of getnameinfo(), it is the alternative of the sa_len for the systems which don't have sa_len. To keep the portability of the application, we must set the size of the struct sockaddr according to the address family correctly. So, we should do such sanity checking. Furthermore, all of KAME delivered getnameinfo() including the version shipped by ISC do the checking. Changing to only FreeBSD will cause confusion. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 27 23:10:52 2002 Delivered-To: freebsd-net@freebsd.org Received: from lh.synack.net (lh.synack.net [204.152.188.7]) by hub.freebsd.org (Postfix) with ESMTP id B885337B400 for ; Wed, 27 Feb 2002 23:10:48 -0800 (PST) Received: from lh.synack.net (bbraun@localhost) by lh.synack.net (8.11.6/8.11.6) with ESMTP id g1S77Rg27514; Wed, 27 Feb 2002 23:07:27 -0800 Message-Id: <200202280707.g1S77Rg27514@lh.synack.net> To: Hajimu UMEMOTO Cc: freebsd-net@freebsd.org From: Rob Braun Subject: Re: proposed changes to getnameinfo() implementation In-reply-to: Your message of Thu, 28 Feb 2002 15:07:44 +0900 Date: Wed, 27 Feb 2002 23:07:27 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thursday, Feb 2002 at 15:7:44 Hajimu UMEMOTO wrote: > > RFC2553 defines two types of struct sockaddr, one has sa_len and the > other doesn't has it. Though we *BSD has sa_len, non-BSD doesn't have > it. Regardless of sa_len, the size of the structure is already known by the value of sa_family, which both sockaddrs have. > To keep the portability of the application, we must set the size of > the struct sockaddr according to the address family correctly. So, we > should do such sanity checking. This doesn't impair portability, it improves it. Since it is more permissive, yet still valid, it is compatible with the existing usage. > Furthermore, all of KAME delivered getnameinfo() including the version > shipped by ISC do the checking. Changing to only FreeBSD will cause > confusion. Not meaning to hold up glibc as a shining example, but this is how glibc behaves. FreeBSD would not be the first. In fact, this is needed for compatibility with systems that do honor the second parameter. Just because FreeBSD happens to have the sa_len field doesn't mean it should take precidence over the specified length. In fact for portability, the second parameter *must* be honored. Since sa_len doesn't exist on all systems, and isn't required to exist, it's value should arguably not be trusted as a portable app may have left it uninitialized. The getnameinfo() definition from RFC2553 and the FreeBSD man page does not require the sa_len field to be initialized prior to calling getnameinfo(). Since it's not required, it should not be relied upon. Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 27 23:30: 9 2002 Delivered-To: freebsd-net@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id AB99237B400 for ; Wed, 27 Feb 2002 23:30:04 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by cs.rice.edu (Postfix) with ESMTP id C688A18A7; Thu, 28 Feb 2002 01:30:03 -0600 (CST) Received: from frosty.cs.rice.edu (frosty.cs.rice.edu [128.42.1.20]) by cs.rice.edu (Postfix) with ESMTP id 271C21842; Thu, 28 Feb 2002 01:30:02 -0600 (CST) Received: from localhost (hykim@localhost) by frosty.cs.rice.edu (8.9.3+Sun/8.9.0) with ESMTP id BAA21072; Thu, 28 Feb 2002 01:29:58 -0600 (CST) X-Authentication-Warning: frosty.cs.rice.edu: hykim owned process doing -bs Date: Thu, 28 Feb 2002 01:29:58 -0600 (CST) From: Hyong-Youb Kim To: Alfred Perlstein Cc: Subject: Re: kern.ipc.maxsockets In-Reply-To: <20020228045834.GA80761@elvis.mu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20010714 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > The server machine I am working on has 2GB of memory and 1.6G Athlon CPU. > > It currently runs FreeBSD-4.3-RELEASE. > > I have been trying to get kern.ipc.maxsockets above 64K. I have tried > > 128K, 100K, and so on. 80K worked but for all others, the system halted > > during the boot saying 'pager_swap_zone = null'. I am guessing that the > > kernel zone allocator cannot allocate enough map space for the pager swap? > > I am wondering if anyone knows how to get around this problem. Thanks. > > 4-stable has a fix for this. If the problem doesn't involve many files, is there anyway to get a diff patch against 4.3-RELEASE? Thanks. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 28 0:10: 2 2002 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 5C80437B405 for ; Thu, 28 Feb 2002 00:09:59 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 32B57AE2C5; Thu, 28 Feb 2002 00:09:59 -0800 (PST) Date: Thu, 28 Feb 2002 00:09:59 -0800 From: Alfred Perlstein To: Hyong-Youb Kim Cc: freebsd-net@FreeBSD.ORG Subject: Re: kern.ipc.maxsockets Message-ID: <20020228080959.GF80761@elvis.mu.org> References: <20020228045834.GA80761@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Hyong-Youb Kim [020227 23:30] wrote: > > > > > The server machine I am working on has 2GB of memory and 1.6G Athlon CPU. > > > It currently runs FreeBSD-4.3-RELEASE. > > > I have been trying to get kern.ipc.maxsockets above 64K. I have tried > > > 128K, 100K, and so on. 80K worked but for all others, the system halted > > > during the boot saying 'pager_swap_zone = null'. I am guessing that the > > > kernel zone allocator cannot allocate enough map space for the pager swap? > > > I am wondering if anyone knows how to get around this problem. Thanks. > > > > 4-stable has a fix for this. > > If the problem doesn't involve many files, is there anyway to get a diff > patch against 4.3-RELEASE? Thanks. Sure. Look at src/sys/vm/swap_pager.c near revision 1.150 to 1.162 -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 28 1:14:12 2002 Delivered-To: freebsd-net@freebsd.org Received: from mdv.dhs.org (mdv.xs4all.nl [213.84.209.48]) by hub.freebsd.org (Postfix) with ESMTP id 2343937B400 for ; Thu, 28 Feb 2002 01:13:58 -0800 (PST) Received: (from root@localhost) by mdv.dhs.org (8.11.6/8.11.6) id g1S9Due05794 for freebsd-net@freebsd.org; Thu, 28 Feb 2002 10:13:56 +0100 (CET) (envelope-from mdevries@haveityourway.nl) Received: from marcel.haveityourway.nl (marcel.mdv.int [192.168.1.3]) by mdv.dhs.org (8.11.6/8.11.6av) with ESMTP id g1S9DsQ05787 for ; Thu, 28 Feb 2002 10:13:54 +0100 (CET) (envelope-from mdevries@haveityourway.nl) Message-Id: <5.1.0.14.2.20020228094227.01e325d0@outshine> X-Sender: mdevries@outshine X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 28 Feb 2002 10:14:06 +0100 To: freebsd-net@freebsd.org From: Marcel de Vries Subject: no more buffer problems yes!! Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, The problem I had with 'no buffer available' messages is solved. Mpd seemed to be the problem. I'm using pptpclient-1.0.3 at this very moment, tested my mxstream ADSL inet connection in all kinds of ways with (ICMP traffic, UDP, TCP) and no buffer problems. Mpd was generating these problems, and with al respect of Mpd coders, I applied a patch on Mpd to use mpd in combination with mxstream ADSL. The patch was written for Mpd version 3.2. I applied this patch on v3.7 to meet the requirements for connecting to the internet. For you all unfamiliar with the patch en purpose stick close now: Without C experience, I can tell the function for the patch. I think not ;-) but I'll try! Mpd needs to call this script, that's what a peace of the patch is about I think. Mxstream-up script: #!/bin/sh # ng0 inet 10.162.75.185 195.190.240.193 INTERFACE=$1 PROTOCOL=$2 LOCAL=$3 REMOTE=$4 /sbin/route delete default /sbin/ifconfig ng0 mtu 1492 /sbin/route add default $REMOTE [ -x /sbin/ipnat ] && /sbin/ipnat -CF -f /etc/ipnat.conf && ipf -y && echo -n 'ipnat' -------------- My mpd.conf, peep this: default: load mxstream mxstream: new -i ng0 mxs mxs #log -auth -ccp -chat -fsm -iface -pptp -ipcp -lcp -link -phys set iface disable on-demand set iface idle 0 set iface up-script "/usr/local/sbin/mxstream-up" set bundle disable multilink set bundle authname thuglord@xs4all-fast-adsl set link yes acfcomp protocomp set link no chap set link yes pap set link disable pap set link keep-alive 10 75 set ipcp yes vjcomp set ipcp enable req-pri-dns set ipcp enable req-sec-dns open Please everybody is free to fix the patch below, because my C poor as hell. I liked mpd very much, but I have changed to pptp-client to fix the no buffer space problems. orginal patch source: ----------------------------------------start------------------------------- *** work/mpd-3.2/src/Makefile.orig Tue Oct 10 23:15:28 2000 --- work/mpd-3.2/src/Makefile Wed Feb 21 21:04:01 2001 *************** *** 63,68 **** --- 63,69 ---- COPTS+= -DPATH_CONF_DIR=\"${MPD_CONF_DIR}\" COPTS+= -DSYSLOG_FACILITY=${SYSLOG_FACILITY} COPTS+= -DMPD_VERSION='"${MPD_VERSION}"' + COPTS+= -DMXSTREAM # Standard sources *** work/mpd-3.2/src/pptp.c.orig Tue Oct 10 23:15:28 2000 --- work/mpd-3.2/src/pptp.c Wed Feb 21 21:04:01 2001 *************** *** 20,25 **** --- 20,26 ---- #include #include + /* * DEFINITIONS */ *************** *** 48,53 **** --- 49,57 ---- u_short peer_port; /* Current peer port */ struct optinfo options; struct pptpctrlinfo cinfo; + #ifdef MXSTREAM + char phoneNum[PPTP_PHONE_LEN + 1]; + #endif }; typedef struct pptpinfo *PptpInfo; *************** *** 57,62 **** --- 61,69 ---- SET_PEERADDR, SET_ENABLE, SET_DISABLE, + #ifdef MXSTREAM + SET_PHONENUM, + #endif }; /* Binary options */ *************** *** 132,137 **** --- 139,148 ---- PptpSetCommand, NULL, (void *) SET_ENABLE }, { "disable [opt ...]", "Disable option", PptpSetCommand, NULL, (void *) SET_DISABLE }, + #ifdef MXSTREAM + { "phone string", "Phone number", + PptpSetCommand, NULL, (void *) SET_PHONENUM }, + #endif { NULL }, }; *************** *** 271,280 **** cinfo = PptpCtrlInCall(linfo, ip, port, PPTP_BEARCAP_ANY, PPTP_FRAMECAP_SYNC, PPTP_CALL_MIN_BPS, PPTP_CALL_MAX_BPS, inet_ntoa(gLocalIp), "", ""); ! else cinfo = PptpCtrlOutCall(linfo, ip, port, PPTP_BEARCAP_ANY, PPTP_FRAMECAP_SYNC, PPTP_CALL_MIN_BPS, PPTP_CALL_MAX_BPS, "", ""); if (cinfo.cookie == NULL) return(-1); pptp->peer_addr = ip; --- 282,299 ---- cinfo = PptpCtrlInCall(linfo, ip, port, PPTP_BEARCAP_ANY, PPTP_FRAMECAP_SYNC, PPTP_CALL_MIN_BPS, PPTP_CALL_MAX_BPS, inet_ntoa(gLocalIp), "", ""); ! else { ! #ifdef MXSTREAM ! Log(LG_PPTP, ("[%s] phonenum [%s] used", lnk->name, pptp->phoneNum)); ! cinfo = PptpCtrlOutCall(linfo, ip, port, ! PPTP_BEARCAP_ANY, PPTP_FRAMECAP_SYNC, ! PPTP_CALL_MIN_BPS, PPTP_CALL_MAX_BPS, pptp->phoneNum, ""); ! #else cinfo = PptpCtrlOutCall(linfo, ip, port, PPTP_BEARCAP_ANY, PPTP_FRAMECAP_SYNC, PPTP_CALL_MIN_BPS, PPTP_CALL_MAX_BPS, "", ""); + #endif + } if (cinfo.cookie == NULL) return(-1); pptp->peer_addr = ip; *************** *** 732,737 **** --- 751,761 ---- DisableCommand(ac, av, &pptp->options, gConfList); PptpListenUpdate(); break; + #ifdef MXSTREAM + case SET_PHONENUM: + snprintf(pptp->phoneNum, PPTP_PHONE_LEN + 1, "%s", *av); + break; + #endif default: assert(0); } ---------------------------------end---------------------------- Ok thats all folks, Regards, Marcel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 28 2:28:33 2002 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 20D8337B402 for ; Thu, 28 Feb 2002 02:28:31 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id EDEE0AE27F; Thu, 28 Feb 2002 02:28:30 -0800 (PST) Date: Thu, 28 Feb 2002 02:28:30 -0800 From: Alfred Perlstein To: net@freebsd.org Subject: ipfw+nfs kills both client and server Message-ID: <20020228102830.GA73010@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org If anyone is interested, take this scenario: NFS client and server set up client is doing this: tar cf - /path/to/nfs/mount | tar -xvf - idiot sysadmin (me) does this on client: kldload ipfw Now since the default ruleset is to deny everything, the client locks up spewing 'nfsd send error 13'. Now give it two or three shots and you may get the server to lock up as well! (seems to run out of mbufs) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 28 3:11:14 2002 Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 077BD37B402 for ; Thu, 28 Feb 2002 03:11:08 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 28 Feb 2002 11:11:06 +0000 (GMT) To: Alfred Perlstein Cc: net@freebsd.org Subject: Re: ipfw+nfs kills both client and server In-Reply-To: Your message of "Thu, 28 Feb 2002 02:28:30 PST." <20020228102830.GA73010@elvis.mu.org> Date: Thu, 28 Feb 2002 11:11:06 +0000 From: Ian Dowse Message-ID: <200202281111.aa87624@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <20020228102830.GA73010@elvis.mu.org>, Alfred Perlstein writes: >Now since the default ruleset is to deny everything, the client >locks up spewing 'nfsd send error 13'. > >Now give it two or three shots and you may get the server >to lock up as well! (seems to run out of mbufs) I must have forgotten to commit the fix for this - Garrett noticed the problem a few years ago, and I came across it while testing exactly this scenario more recently (for more details, search for the message ID <200110151653.aa00863@salmon.maths.tcd.ie> on this list). The uio != NULL check that this removes was added in CSRG revision 7.31 (Nov 1991) to support Rick Macklem's NFS work, but I'm fairly sure that it is not needed now. If it was there for performance reasons it should have increased the socket limit, and not removed it alltogether. The patch is below; I'll commit this shortly. Ian Index: uipc_socket.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/sys/kern/uipc_socket.c,v retrieving revision 1.109 diff -u -r1.109 uipc_socket.c --- uipc_socket.c 5 Feb 2002 02:00:53 -0000 1.109 +++ uipc_socket.c 9 Feb 2002 12:52:45 -0000 @@ -549,7 +549,7 @@ if ((atomic && resid > so->so_snd.sb_hiwat) || clen > so->so_snd.sb_hiwat) snderr(EMSGSIZE); - if (space < resid + clen && uio && + if (space < resid + clen && (atomic || space < so->so_snd.sb_lowat || space < clen)) { if (so->so_state & SS_NBIO) snderr(EWOULDBLOCK); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 28 9:21: 9 2002 Delivered-To: freebsd-net@freebsd.org Received: from cheer.mahoroba.org (flets19-017.kamome.or.jp [218.45.19.17]) by hub.freebsd.org (Postfix) with ESMTP id 04CAD37B41B; Thu, 28 Feb 2002 09:21:05 -0800 (PST) Received: from mille.mahoroba.org (IDENT:zMPQAmt/qnJaUSMiQ1wajdMC3SVuYtbzGFfT83uwUDa86LQugb4aNH3vvK/R7rGg@mille.mahoroba.org [IPv6:2001:200:301:0:202:2dff:fe0a:6bee]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.2/8.12.2) with ESMTP/inet6 id g1SHL1Ev086265 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 1 Mar 2002 02:21:02 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Fri, 01 Mar 2002 02:21:01 +0900 Message-ID: From: Hajimu UMEMOTO To: Edwin Groothuis Cc: "JINMEI Tatuya / ?$B?@L@C#:H?(B" , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: IPv6-over-IPv4 problems since the upgrade to 4.5 In-Reply-To: <20020228152057.A619@k7.mavetju.org> References: <20020216130842.A19081@energyhq.homeip.net> <20020217122510.D491@k7.mavetju.org> <20020222234829.F492@k7.mavetju.org> <20020223084616.G492@k7.mavetju.org> <20020225221827.F491@k7.mavetju.org> User-Agent: xcite1.38> Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) X-Operating-System: FreeBSD 4.5-RELEASE MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, >>>>> On Thu, 28 Feb 2002 15:20:57 +1100 >>>>> Edwin Groothuis said: edwin> On Tue, Feb 26, 2002 at 02:38:28PM +0900, JINMEI Tatuya / ?$B?@L@C#:H?(B wrote: > Finally I figured out the problem. edwin> Thanks for these two patches, it works like a charm now! I just committed both patches to -CURRENT. I'll do MFC after 1 week. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 28 9:42:18 2002 Delivered-To: freebsd-net@freebsd.org Received: from mta07.onebox.com (mta07.onebox.com [64.68.77.180]) by hub.freebsd.org (Postfix) with ESMTP id 7F02537B402 for ; Thu, 28 Feb 2002 09:42:13 -0800 (PST) Received: from onebox.com ([10.1.111.10]) by mta07.onebox.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20020228174208.UXLS26106.mta07.onebox.com@onebox.com> for ; Thu, 28 Feb 2002 09:42:08 -0800 Received: from [206.61.34.3] by onebox.com with HTTP; Thu, 28 Feb 2002 09:42:08 -0800 Date: Thu, 28 Feb 2002 11:42:08 -0600 From: "Hamilton Hoover" To: freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Message-Id: <20020228174208.UXLS26106.mta07.onebox.com@onebox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, I'm setting up a site that I'd like to have four separate networks connected through a single gateway/firewall with five network interfaces. Two Public (real IPs) interfaces on the same network with different IPs realIP1 realIP2 Three Private (fake IPS) interfaces on three separate networks 192.168.1 192.168.2 192.168.3 I want to break it down in to two groups site1 realIP1 --> 192.168.1 This is the only one I currently have running and works fine. I basicly allow ftp, http, https. I am using redirect_port for the protocols I want to allow in. I will change to redirect_address when I add site 2. site2 realIP2 --> 192.168.2 realIP2 --> 192.168.3 On this site I want to allow traffic for web to the DMZ 192.168.2 and dns to 192.168.3. I also want to allow certain traffic from 192.168.3 --> 192.168.2. I am unsure if I can have multiple nat devices and will a second nat'ed device conflict with the one from site1? There are no outbound restrications and I'm using ipfw for firewalling. All of the 192.168 wail need to send packets to the internet. So is it possible to list more then one nat interface? Is there a better way to do what I want here and keep three private nets? I currently running FreeBSD 4.4-RELEASE tia! Hamilton __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 28 9:44: 6 2002 Delivered-To: freebsd-net@freebsd.org Received: from mta06.onebox.com (mta06.onebox.com [64.68.77.179]) by hub.freebsd.org (Postfix) with ESMTP id 1B24937B400 for ; Thu, 28 Feb 2002 09:44:03 -0800 (PST) Received: from onebox.com ([10.1.111.8]) by mta06.onebox.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20020228174358.JHLU29423.mta06.onebox.com@onebox.com> for ; Thu, 28 Feb 2002 09:43:58 -0800 Received: from [206.61.34.3] by onebox.com with HTTP; Thu, 28 Feb 2002 09:43:57 -0800 Date: Thu, 28 Feb 2002 11:43:57 -0600 Subject: natd & ipfw config with 5 NICS From: "Hamilton Hoover" To: freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Message-Id: <20020228174358.JHLU29423.mta06.onebox.com@onebox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, I'm setting up a site that I'd like to have four separate networks connected through a single gateway/firewall with five network interfaces. Two Public (real IPs) interfaces on the same network with different IPs realIP1 realIP2 Three Private (fake IPS) interfaces on three separate networks 192.168.1 192.168.2 192.168.3 I want to break it down in to two groups site1 realIP1 --> 192.168.1 This is the only one I currently have running and works fine. I basicly allow ftp, http, https. I am using redirect_port for the protocols I want to allow in. I will change to redirect_address when I add site 2. site2 realIP2 --> 192.168.2 realIP2 --> 192.168.3 On this site I want to allow traffic for web to the DMZ 192.168.2 and dns to 192.168.3. I also want to allow certain traffic from 192.168.3 --> 192.168.2. I am unsure if I can have multiple nat devices and will a second nat'ed device conflict with the one from site1? There are no outbound restrications and I'm using ipfw for firewalling. All of the 192.168 wail need to send packets to the internet. So is it possible to list more then one nat interface? Is there a better way to do what I want here and keep three private nets? I currently running FreeBSD 4.4-RELEASE tia! Hamilton __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 28 11:34:28 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 6B8B237B400 for ; Thu, 28 Feb 2002 11:34:26 -0800 (PST) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020228193426.BCXN2626.rwcrmhc51.attbi.com@blossom.cjclark.org>; Thu, 28 Feb 2002 19:34:26 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g1SJYPa69734; Thu, 28 Feb 2002 11:34:25 -0800 (PST) (envelope-from cjc) Date: Thu, 28 Feb 2002 11:34:25 -0800 From: "Crist J. Clark" To: Hamilton Hoover Cc: freebsd-net@FreeBSD.ORG Subject: Re: natd & ipfw config with 5 NICS Message-ID: <20020228113425.L66092@blossom.cjclark.org> References: <20020228174358.JHLU29423.mta06.onebox.com@onebox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020228174358.JHLU29423.mta06.onebox.com@onebox.com>; from hamilton.hoover@onebox.com on Thu, Feb 28, 2002 at 11:43:57AM -0600 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Feb 28, 2002 at 11:43:57AM -0600, Hamilton Hoover wrote: > Hi all, > > I'm setting up a site that I'd like to have four separate networks connected > > through a single gateway/firewall with five network interfaces. > > Two Public (real IPs) interfaces on the same network with different IPs > realIP1 > realIP2 You will need to run an individual instance of natd(8) for each external physical interface. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 28 11:54:30 2002 Delivered-To: freebsd-net@freebsd.org Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.109]) by hub.freebsd.org (Postfix) with ESMTP id 7644637B402 for ; Thu, 28 Feb 2002 11:54:20 -0800 (PST) Received: from pooh.int (pooh.int [10.0.1.2]) by kanga.honeypot.net (8.11.6/8.11.6) with ESMTP id g1SJs5a91258 for ; Thu, 28 Feb 2002 13:54:05 -0600 (CST) (envelope-from kirk@strauser.com) Received: (from kirk@localhost) by pooh.int (8.11.6/8.11.6) id g1SJs5E73278; Thu, 28 Feb 2002 13:54:05 -0600 (CST) (envelope-from kirk@strauser.com) To: freebsd-net@FreeBSD.ORG Subject: My DNS is giving wrong answers (sometimes) From: Kirk Strauser Date: 28 Feb 2002 13:52:50 -0600 Message-ID: <87u1s1tmct.fsf@pooh.int> Lines: 108 X-Mailer: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Ack! I just migrated my primary DNS from one machine (ds10.honeypot.net) to another (kanga.honeypot.net), both running FreeBSD 4.5-STABLE. I'm trying to serve the honeypot.net domain. Here is the entry from named.conf: zone "honeypot.net" { type master; file "db/db.honeypot.net"; }; and this is the contents of db/db.honeypot.net: $TTL 86400 $ORIGIN net. honeypot IN SOA ns2.honeypot.net. root.kanga.honeypot.net. ( 2002022803 10800 3600 604800 86400 ) IN NS ns1.honeypot.net. IN NS ns2.honeypot.net. IN A 12.28.57.99 IN MX 0 mail.honeypot.net. IN MX 10 ds10.dialnet.net. $ORIGIN honeypot.net. ns1 IN A 12.28.57.99 ns2 IN A 208.162.254.109 psmg IN A 12.28.57.99 www IN A 12.28.57.99 stats IN A 12.28.57.99 subwiki IN A 208.162.254.109 kanga IN A 208.162.254.109 pooh IN CNAME kanga.honeypot.net. tigger IN CNAME kanga.honeypot.net. mail IN A 208.162.254.109 ds10 IN A 12.28.57.99 zope IN A 208.162.254.109 On of my users notified me that he was now getting the wrong answer when he queried for ds10.honeypot.net. Being skeptical, I tried a query from kanga: root@kanga:/etc/namedb/db# dig @kanga.honeypot.net ds10.honeypot.net ; <<>> DiG 8.3 <<>> @kanga.honeypot.net ds10.honeypot.net ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUERY SECTION: ;; ds10.honeypot.net, type = A, class = IN ;; ANSWER SECTION: ds10.honeypot.net. 1D IN A 12.28.57.99 ;; AUTHORITY SECTION: honeypot.net. 1D IN NS ns1.honeypot.net. honeypot.net. 1D IN NS ns2.honeypot.net. ;; ADDITIONAL SECTION: ns1.honeypot.net. 1D IN A 12.28.57.99 ns2.honeypot.net. 1D IN A 208.162.254.109 ;; Total query time: 4 msec ;; FROM: kanga.int to SERVER: kanga.honeypot.net 208.162.254.109 ;; WHEN: Thu Feb 28 13:44:12 2002 ;; MSG SIZE sent: 35 rcvd: 119 The anwers were correct, as far as I can tell, so I didn't think too much about it. However, my user insisted that he was still getting wrong answers. I ssh'ed into a remote machine and was surprised to get: strauser@csc ~$ dig @kanga.honeypot.net ds10.honeypot.net ; <<>> DiG 8.3 <<>> @kanga.honeypot.net ds10.honeypot.net ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUERY SECTION: ;; ds10.honeypot.net, type = A, class = IN ;; ANSWER SECTION: ds10.honeypot.net. 0S IN A 208.162.254.109 ;; AUTHORITY SECTION: honeypot.net. 0S IN NS ns1.honeypot.net. honeypot.net. 0S IN NS ns2.honeypot.net. ;; ADDITIONAL SECTION: ns1.honeypot.net. 0S IN A 208.162.254.109 ns2.honeypot.net. 0S IN A 208.162.254.109 ;; Total query time: 112 msec ;; FROM: csc.smsu.edu to SERVER: kanga.honeypot.net 208.162.254.109 ;; WHEN: Thu Feb 28 13:43:56 2002 ;; MSG SIZE sent: 35 rcvd: 119 Basically, if I query $host.honeypot.net, and $host is defined, then I always get the answer of kanga.honeypot.net's own IP. I don't *think* it would matter, but I'm on a permanent DSL connection with a static IP, and my LAN (and kanga.honeypot.net itself) is numbered in the 10/8 netblock. My Cisco 678 router is handling NAT, with dynamic mapped outbound connections, and a small set of static mapped inbound rules (DNS, SMTP, HTTP, etc.). Any suggestions? This is a Really Bad Thing, and I have no idea what's causing the problem. Please take pity on a desperate sysadmin! -- Kirk Strauser To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 28 22: 0: 9 2002 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 0CE2C37B417 for ; Thu, 28 Feb 2002 22:00:06 -0800 (PST) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id VAA48777; Thu, 28 Feb 2002 21:47:20 -0800 (PST) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.6/8.11.6) id g215l7W17784; Thu, 28 Feb 2002 21:47:07 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200203010547.g215l7W17784@arch20m.dellroad.org> Subject: Re: no more buffer problems yes!! In-Reply-To: "from Marcel de Vries at Feb 28, 2002 10:14:06 am" To: Marcel de Vries Date: Thu, 28 Feb 2002 21:47:07 -0800 (PST) Cc: freebsd-net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Marcel de Vries writes: > Please everybody is free to fix the patch below, because my C poor as hell. Thanks for the patch, I've included it in the next version. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 28 23:46:42 2002 Delivered-To: freebsd-net@freebsd.org Received: from mail.realtek.com.tw (ms1.realtek.com.tw [203.69.112.3]) by hub.freebsd.org (Postfix) with ESMTP id 315D837B417 for ; Thu, 28 Feb 2002 23:46:34 -0800 (PST) Received: from RTCN3848 ([172.20.33.135]) by mail.realtek.com.tw (Lotus Domino Release 5.0.8) with SMTP id 2002030115450185:5279 ; Fri, 1 Mar 2002 15:45:01 +0800 Message-ID: <001301c1c0f6$1e517ff0$872114ac@RTCN3848> From: "cfliu" To: Subject: Is recv/sendmsg important for AF_INET only sockets? Date: Fri, 1 Mar 2002 15:53:04 +0800 MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-MIMETrack: Itemize by SMTP Server on ms1/Realtek(Release 5.0.8 |June 18, 2001) at 03/01/2002 03:45:01 PM, Serialize by Router on ms1/Realtek(Release 5.0.8 |June 18, 2001) at 03/01/2002 03:45:09 PM, Serialize complete at 03/01/2002 03:45:09 PM Content-Type: multipart/alternative; boundary="----=_NextPart_000_0010_01C1C139.2C63F710" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0010_01C1C139.2C63F710 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="big5" Hi, I am implementing a small BSD socket layer which supports only the = AF_INET family. I am wondering whether recvmsg() and sendmsg() calls are = required for the INET protocol family. I don't know if I should = implemented it or not. I have looked up some open source projects and = grepped for recvmsg and sendmsg calls but couldn't find any. How often = do people use recvmsg/sendmsg() calls (also readv()/writev()) in their = BSD socket based Internet applications? Is it safe NOT to implement = these functions for a INET socket? Thanks. ------=_NextPart_000_0010_01C1C139.2C63F710 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="big5"
Hi, I am implementing a small BSD socket layer=20 which supports only the AF_INET family. I am wondering whether = recvmsg()=20 and sendmsg() calls are required for the INET protocol family. I don't = know if I=20 should implemented it or not. I have looked up some open source projects = and=20 grepped for recvmsg and sendmsg calls but couldn't find any.   = How=20 often do people use recvmsg/sendmsg() calls (also readv()/writev()) in = their BSD=20 socket based Internet applications? Is it safe NOT to implement these = functions=20 for a INET socket?
 
Thanks.
------=_NextPart_000_0010_01C1C139.2C63F710-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 1:58: 0 2002 Delivered-To: freebsd-net@freebsd.org Received: from mail.spc.org (insomnia.spc.org [195.224.94.183]) by hub.freebsd.org (Postfix) with SMTP id B112537B400 for ; Fri, 1 Mar 2002 01:57:55 -0800 (PST) Received: (qmail 9512 invoked by uid 1031); 1 Mar 2002 09:47:14 -0000 Date: Fri, 1 Mar 2002 09:47:14 +0000 From: Bruce M Simpson To: freebsd-net@freebsd.org Subject: IPSEC offloading on Intel PRO/100 S Message-ID: <20020301094714.B5099@spc.org> Mail-Followup-To: Bruce M Simpson , freebsd-net@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Guys, A few questions regarding the Intel PRO/100 S Ethernet adapter: o Has anybody experimented with using the IPSEC ESP 3DES hardware offload capability of the Intel 82550EY ASIC used within the above NIC? o Have Intel ever released specs for this ASIC publicly? o Would anybody be interested in my adding support for this beast's crypto features to the fxp driver? Please let me know your thoughts. Regards, Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 1:58:47 2002 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 06BB337B400 for ; Fri, 1 Mar 2002 01:58:45 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id E6C51AE27E; Fri, 1 Mar 2002 01:58:44 -0800 (PST) Date: Fri, 1 Mar 2002 01:58:44 -0800 From: Alfred Perlstein To: Bruce M Simpson Cc: freebsd-net@freebsd.org Subject: Re: IPSEC offloading on Intel PRO/100 S Message-ID: <20020301095844.GK77980@elvis.mu.org> References: <20020301094714.B5099@spc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020301094714.B5099@spc.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Bruce M Simpson [020301 01:58] wrote: > > o Would anybody be interested in my adding support for this beast's crypto > features to the fxp driver? Yes. :) -- -Alfred Perlstein [alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 2:15:14 2002 Delivered-To: freebsd-net@freebsd.org Received: from cc.kmu.edu.tw (cc.kmu.edu.tw [163.15.154.1]) by hub.freebsd.org (Postfix) with ESMTP id 5D74E37B417 for ; Fri, 1 Mar 2002 02:15:10 -0800 (PST) Received: from cc.kmu.edu.tw (c198.cc.kmu.edu.tw [163.15.154.198]) by cc.kmu.edu.tw (8.11.6/8.11.6) with ESMTP id g21AF5a78079 for ; Fri, 1 Mar 2002 18:15:09 +0800 (CST) (envelope-from cch@cc.kmu.edu.tw) Message-ID: <3C7F54B2.5040300@cc.kmu.edu.tw> Date: Fri, 01 Mar 2002 18:15:14 +0800 From: Chih-Chang Hsieh Reply-To: cch@cc.kmu.edu.tw Organization: KMU Computer Center User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.8) Gecko/20020206 X-Accept-Language: zh-tw, en-us MIME-Version: 1.0 To: freebsd-net@FreeBSD.org Subject: Re: DGE-500SX Gigabit Ethernet References: Content-Type: text/plain; charset=Big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Ferdinand.Goldmann@zid.uni-linz.ac.at wrote: >A colleague and I have tried getting a DGE-500SX to work >under FreeBSD 4.5-STABLE. > We had tried it on 4.4-STABLE. When we use it to connect to Nortel 8600 GBIC, the TX/RX LEDs on the switch are off. But when we use two DGE-500SX cards to connect to each other, it works but with low throughputs (about 13 MB/s). P.S.: We plug it on a 32-bits PCI slot. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 2:33:15 2002 Delivered-To: freebsd-net@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 1436137B405 for ; Fri, 1 Mar 2002 02:33:11 -0800 (PST) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 46BEF16B22 for ; Fri, 1 Mar 2002 11:33:09 +0100 (CET) Received: from LenConrad.Go2France.com [66.64.14.18] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id AD6176F02F0; Fri, 01 Mar 2002 11:52:17 +0100 Message-Id: <5.1.0.14.2.20020301043209.0358c418@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 01 Mar 2002 04:33:04 -0600 To: freebsd-net@freebsd.org From: Len Conrad Subject: Re: IPSEC offloading on Intel PRO/100 S In-Reply-To: <20020301095844.GK77980@elvis.mu.org> References: <20020301094714.B5099@spc.org> <20020301094714.B5099@spc.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > o Would anybody be interested in my adding support for this beast's crypto > > features to the fxp driver? > >Yes. :) Is there ANY hardware encryption support in FreeBSD? Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 2:51:38 2002 Delivered-To: freebsd-net@freebsd.org Received: from mail.spc.org (insomnia.spc.org [195.224.94.183]) by hub.freebsd.org (Postfix) with SMTP id 576F837B41C for ; Fri, 1 Mar 2002 02:51:35 -0800 (PST) Received: (qmail 28889 invoked by uid 1031); 1 Mar 2002 10:40:54 -0000 Date: Fri, 1 Mar 2002 10:40:35 +0000 From: Bruce M Simpson To: Len Conrad Subject: Re: IPSEC offloading on Intel PRO/100 S Message-ID: <20020301104035.D5099@spc.org> References: <20020301094714.B5099@spc.org> <20020301094714.B5099@spc.org> <20020301095844.GK77980@elvis.mu.org> <5.1.0.14.2.20020301043209.0358c418@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <5.1.0.14.2.20020301043209.0358c418@mail.Go2France.com>; from LConrad@Go2France.com on Fri, Mar 01, 2002 at 04:33:04AM -0600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Mar 01, 2002 at 04:33:04AM -0600, Len Conrad wrote: > > > > o Would anybody be interested in my adding support for this beast's crypto > > > features to the fxp driver? > > > >Yes. :) > > Is there ANY hardware encryption support in FreeBSD? Things are gradually being rearranged to facilitate this, as part of SMPng. At the moment the IP stack runs solely as a software interrupt. Since 4.4, there has been the notion of interface capabilities. Normally this is only used for TCP/UDP/IP checksum offloading. BMS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 3: 1:12 2002 Delivered-To: freebsd-net@freebsd.org Received: from mail.spc.org (insomnia.spc.org [195.224.94.183]) by hub.freebsd.org (Postfix) with SMTP id 859FB37B400 for ; Fri, 1 Mar 2002 03:01:09 -0800 (PST) Received: (qmail 28429 invoked by uid 1031); 1 Mar 2002 10:50:28 -0000 Date: Fri, 1 Mar 2002 10:50:28 +0000 From: Bruce M Simpson To: Len Conrad Cc: freebsd-net@freebsd.org Subject: Re: IPSEC offloading on Intel PRO/100 S Message-ID: <20020301105028.E5099@spc.org> Mail-Followup-To: Bruce M Simpson , Len Conrad , freebsd-net@freebsd.org References: <20020301094714.B5099@spc.org> <20020301094714.B5099@spc.org> <20020301095844.GK77980@elvis.mu.org> <5.1.0.14.2.20020301043209.0358c418@mail.Go2France.com> <20020301104035.D5099@spc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020301104035.D5099@spc.org>; from bms@spc.org on Fri, Mar 01, 2002 at 10:40:35AM +0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Pardon my lack of caffiene; I have a pint mug of tea on my desk now. On Fri, Mar 01, 2002 at 10:40:35AM +0000, Bruce M Simpson wrote: > > > > Is there ANY hardware encryption support in FreeBSD? > > Things are gradually being rearranged to facilitate this, as part of SMPng. > At the moment the IP stack runs solely as a software interrupt. Since 4.4, ^^^^^^^^^^^^^^^^^^^^^^^^^ That should be 'solely within a software interrupt context, splnet()'. It's also going to require some reworking of the imported KAME tree. BMS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 7:19:35 2002 Delivered-To: freebsd-net@freebsd.org Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by hub.freebsd.org (Postfix) with ESMTP id 6DBD037B405 for ; Fri, 1 Mar 2002 07:19:29 -0800 (PST) Received: from melange (melange.errno.com [66.127.85.82]) (authenticated bits=0) by ebb.errno.com (8.12.1/8.12.1) with ESMTP id g21FJQOs032412 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 1 Mar 2002 07:19:28 -0800 (PST)?g (envelope-from sam@errno.com)œ Message-ID: <17f401c1c134$7ad73970$52557f42@errno.com> From: "Sam Leffler" To: , "Len Conrad" References: <20020301094714.B5099@spc.org> <20020301094714.B5099@spc.org> <5.1.0.14.2.20020301043209.0358c418@mail.Go2France.com> Subject: Re: IPSEC offloading on Intel PRO/100 S Date: Fri, 1 Mar 2002 07:19:26 -0800 Organization: Errno Consulting MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have working crypto support for -stable. I'll distribute it when I've completed integration with KAME IPSEC. My stuff is derived from the openbsd crypto framework. Sam ----- Original Message ----- From: "Len Conrad" To: Sent: Friday, March 01, 2002 2:33 AM Subject: Re: IPSEC offloading on Intel PRO/100 S > Is there ANY hardware encryption support in FreeBSD? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 8:29:20 2002 Delivered-To: freebsd-net@freebsd.org Received: from tokyo.ccrle.nec.de (tokyo.ccrle.nec.de [195.37.70.2]) by hub.freebsd.org (Postfix) with ESMTP id BD51737B421 for ; Fri, 1 Mar 2002 08:29:01 -0800 (PST) Received: from wallace.heidelberg.ccrle.nec.de (root@wallace.heidelberg.ccrle.nec.de [192.168.102.1]) by tokyo.ccrle.nec.de (8.11.6/8.11.6) with ESMTP id g21GT0Q55505; Fri, 1 Mar 2002 17:29:00 +0100 (CET) (envelope-from Martin.Stiemerling@ccrle.nec.de) Received: from imap.heidelberg.ccrle.nec.de (imap.heidelberg.ccrle.nec.de [192.168.102.11]) by wallace.heidelberg.ccrle.nec.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id RAA10499; Fri, 1 Mar 2002 17:28:59 +0100 Received: from elgar (elgar.heidelberg.ccrle.nec.de [192.168.102.180]) by imap.heidelberg.ccrle.nec.de (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 8C55B28463; Fri, 1 Mar 2002 17:28:58 +0100 (CET) Date: Fri, 01 Mar 2002 17:28:56 +0100 From: Martin Stiemerling To: cch@cc.kmu.edu.tw, freebsd-net@FreeBSD.ORG Subject: Re: DGE-500SX Gigabit Ethernet Message-ID: <12740000.1015000136@elgar> In-Reply-To: <3C7F54B2.5040300@cc.kmu.edu.tw> References: <3C7F54B2.5040300@cc.kmu.edu.tw> X-Mailer: Mulberry/2.1.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --On Freitag, M=E4rz 01, 2002 18:15:14 +0800 Chih-Chang Hsieh=20 wrote: > Ferdinand.Goldmann@zid.uni-linz.ac.at wrote: > >> A colleague and I have tried getting a DGE-500SX to work >> under FreeBSD 4.5-STABLE. >> > We had tried it on 4.4-STABLE. > > When we use it to connect to Nortel 8600 GBIC, the TX/RX LEDs The problem is perhaps that the Nortel device uses a long range card (look=20 for abbreviation LX) and the DGE-500SX is a short range card (=3DSX). Cheers Martin > > on the switch are off. But when we use two DGE-500SX cards to > > connect to each other, it works but with low throughputs > > (about 13 MB/s). > > P.S.: We plug it on a 32-bits PCI slot. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message Martin Stiemerling NEC Europe Ltd. -- Network Laboratories = Martin.Stiemerling@ccrle.nec.de IPv4: http://www.ccrle.nec.de IPv6: = http://www.ipv6.ccrle.nec.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 9:34:27 2002 Delivered-To: freebsd-net@freebsd.org Received: from odin.egate.net (as2.dm.egate.net [216.235.1.5]) by hub.freebsd.org (Postfix) with ESMTP id CBDAB37B417; Fri, 1 Mar 2002 09:34:17 -0800 (PST) Received: from as2.dm.egate.net (as2.dm.egate.net [216.235.1.5]) by odin.egate.net (8.11.6/8.11.4) with ESMTP id g21HYH901745; Fri, 1 Mar 2002 12:34:17 -0500 (EST) Date: Fri, 1 Mar 2002 12:34:16 -0500 (EST) From: Ryan Morris To: , Subject: Multiple connections to MPD-netgraph as PPTP server Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello everyone, I recently (successfully) configured MPD-netgraph as a pptp server on my FreeBSD machine. It works great... for one user. When I change my configuration to support multiple PPTP bundles/links I get the following error when starting mpd: bsd# mpd Multi-link PPP for FreeBSD, by Archie L. Cobbs. Based on iij-ppp, by Toshiharu OHNO. mpd: pid 518, version 3.7 (root@bsd.imagineering.ca 16:39 28-Feb-2002) [pptpbundle0] ppp node is "mpd518-pptpbund" mpd: local IP address for PPTP is 192.168.0.253 [pptpbundle0] using interface ng0 [pptpbundle1] can't name ppp node: Address already in use [pptpbundle1] netgraph initialization failed I have varied the IP address assignments in my configuration files, and examples on the web have duplicated IP addresses between bundles without causing this problem. Does this make reference to the ppp node name (mpd518-pptpbund)? And if so, how do I change what the ppp node name will be? Best regards, Ryan Morris Here are my configuration files: --- mpd.conf: default: load pptp0 load pptp1 pptp0: new -i ng0 pptpbundle0 pptplink0 set iface disable on-demand set iface enable proxy-arp set iface idle 1800 set bundle disable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set ipcp yes vjcomp set ipcp ranges 192.168.0.253/32 192.168.0.128/29 set ipcp dns 192.168.0.1 set ipcp nbns 192.168.0.253 #Enable Microsoft Point-to-Point Encryption: set bundle enable compression set ccp yes mppc set ccp no mpp-e40 set ccp yes mpp-e128 set ccp no mpp-stateless pptp1: new -i ng1 pptpbundle1 pptplink1 set iface disable on-demand set iface enable proxy-arp set iface idle 1800 set bundle disable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set ipcp yes vjcomp set ipcp ranges 192.168.0.252/32 192.168.0.128/29 set ipcp dns 192.168.0.1 set ipcp nbns 192.168.0.253 #Enable Microsoft Point-to-Point Encryption: set bundle enable compression set ccp yes mppc set ccp no mpp-e40 set ccp yes mpp-e128 set ccp no mpp-stateless # END --- mpd.links: pptplink0: set link type pptp set pptp self 192.168.0.253 set pptp enable incoming set pptp disable originate pptplink1: set link type pptp set pptp self 192.168.0.253 set pptp enable incoming set pptp disable originate #END --- "Some mornings, it's just not worth chewing through the leather straps." - Emo Philips To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 9:55:19 2002 Delivered-To: freebsd-net@freebsd.org Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by hub.freebsd.org (Postfix) with ESMTP id 9491437B417 for ; Fri, 1 Mar 2002 09:55:10 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g21Ht6s51598; Fri, 1 Mar 2002 09:55:06 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id JAA1829498; Fri, 1 Mar 2002 09:54:18 -0800 (PST) Message-Id: <200203011754.JAA1829498@meer.meer.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "cfliu" Cc: freebsd-net@FreeBSD.ORG Subject: Re: Is recv/sendmsg important for AF_INET only sockets? In-Reply-To: Message from "cfliu" of "Fri, 01 Mar 2002 15:53:04 +0800." <001301c1c0f6$1e517ff0$872114ac@RTCN3848> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Mar 2002 09:54:12 -0800 From: "George V. Neville-Neil" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Hi, I am implementing a small BSD socket layer which supports only the = > AF_INET family. I am wondering whether recvmsg() and sendmsg() calls are = > required for the INET protocol family. I don't know if I should = > implemented it or not. I have looked up some open source projects and = > grepped for recvmsg and sendmsg calls but couldn't find any. How often = > do people use recvmsg/sendmsg() calls (also readv()/writev()) in their = > BSD socket based Internet applications? Is it safe NOT to implement = > these functions for a INET socket? These are used by applications that are implemented on top of UDP and they're very useful. If I were a consumer of your product I'd be pretty disappointed if these calls were not there. Later, George -- George V. Neville-Neil gnn@neville-neil.com NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 11: 0:21 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 2BA2737B405 for ; Fri, 1 Mar 2002 11:00:17 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020301190016.LBUI1147.rwcrmhc52.attbi.com@InterJet.elischer.org>; Fri, 1 Mar 2002 19:00:16 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA12416; Fri, 1 Mar 2002 10:58:32 -0800 (PST) Date: Fri, 1 Mar 2002 10:58:32 -0800 (PST) From: Julian Elischer To: Archie Cobbs Cc: freebsd-net@freebsd.org Subject: Re: no more buffer problems yes!! In-Reply-To: <200203010547.g215l7W17784@arch20m.dellroad.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ok, so if thre is a new version cooking, can we co-operate with adding radius to it? (using PAP)? you DO support PAP right? :-) On Thu, 28 Feb 2002, Archie Cobbs wrote: > Marcel de Vries writes: > > Please everybody is free to fix the patch below, because my C poor as hell. > > Thanks for the patch, I've included it in the next version. > > -Archie > > __________________________________________________________________________ > Archie Cobbs * Packet Design * http://www.packetdesign.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 11:20:26 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id EC9D937B41B for ; Fri, 1 Mar 2002 11:20:20 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020301192020.ESDQ2951.rwcrmhc53.attbi.com@InterJet.elischer.org>; Fri, 1 Mar 2002 19:20:20 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA12495; Fri, 1 Mar 2002 11:17:40 -0800 (PST) Date: Fri, 1 Mar 2002 11:17:39 -0800 (PST) From: Julian Elischer To: Jason Hoffman Cc: freebsd-net@freebsd.org Subject: Re: Netgraph LMC T3 Support? In-Reply-To: <001601c1b4a7$da834a60$3e033a40@jason> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org what driver are you using? On Wed, 13 Feb 2002, Jason Hoffman wrote: > Does netgraph support the LMC T3 interface? > I am having trouble getting netgraph to find the interface. > > Any reply would be greatly appreciated. > > Thanks in advance, > > Jay Hoffman > MHO Networks > (303) 584-9711 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 11:20:33 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 1741F37B41D for ; Fri, 1 Mar 2002 11:20:22 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020301192021.ESEA2951.rwcrmhc53.attbi.com@InterJet.elischer.org>; Fri, 1 Mar 2002 19:20:21 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA12473; Fri, 1 Mar 2002 11:03:40 -0800 (PST) Date: Fri, 1 Mar 2002 11:03:38 -0800 (PST) From: Julian Elischer To: "George V. Neville-Neil" Cc: cfliu , freebsd-net@FreeBSD.ORG Subject: Re: Is recv/sendmsg important for AF_INET only sockets? In-Reply-To: <200203011754.JAA1829498@meer.meer.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 1 Mar 2002, George V. Neville-Neil wrote: > > Hi, I am implementing a small BSD socket layer which supports only the = > > AF_INET family. I am wondering whether recvmsg() and sendmsg() calls are = > > required for the INET protocol family. I don't know if I should = > > implemented it or not. I have looked up some open source projects and = > > grepped for recvmsg and sendmsg calls but couldn't find any. How often = > > do people use recvmsg/sendmsg() calls (also readv()/writev()) in their = > > BSD socket based Internet applications? Is it safe NOT to implement = > > these functions for a INET socket? > > These are used by applications that are implemented on top of UDP > and they're very useful. If I were a consumer of your product I'd be > pretty disappointed if these calls were not there. which, readv or recvmsg? Personally I've used recvmsg() quite a bit but usually on special NON IP protocols. I've never used readv(), so if you're writing the stack for embedded use you may be able to do without these. You may consider writing an extension module that gives these extra interfaces if people want them. > > Later, > George > > -- > George V. Neville-Neil gnn@neville-neil.com > NIC:GN82 > > "Those who would trade liberty for temporary security deserve neither" > - Benjamin Franklin > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 11:20:50 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 9CBD337B41E; Fri, 1 Mar 2002 11:20:27 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020301192027.ESFY2951.rwcrmhc53.attbi.com@InterJet.elischer.org>; Fri, 1 Mar 2002 19:20:27 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA12493; Fri, 1 Mar 2002 11:16:18 -0800 (PST) Date: Fri, 1 Mar 2002 11:16:15 -0800 (PST) From: Julian Elischer To: Ryan Morris Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Multiple connections to MPD-netgraph as PPTP server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 1 Mar 2002, Ryan Morris wrote: > Hello everyone, > > I recently (successfully) configured MPD-netgraph as a pptp server on my > FreeBSD machine. It works great... for one user. When I change my > configuration to support multiple PPTP bundles/links I get the following > error when starting mpd: > > bsd# mpd > Multi-link PPP for FreeBSD, by Archie L. Cobbs. > Based on iij-ppp, by Toshiharu OHNO. > mpd: pid 518, version 3.7 (root@bsd.imagineering.ca 16:39 28-Feb-2002) > [pptpbundle0] ppp node is "mpd518-pptpbund" > mpd: local IP address for PPTP is 192.168.0.253 > [pptpbundle0] using interface ng0 > [pptpbundle1] can't name ppp node: Address already in use > [pptpbundle1] netgraph initialization failed > > I have varied the IP address assignments in my configuration files, and > examples on the web have duplicated IP addresses between bundles without > causing this problem. > > Does this make reference to the ppp node name (mpd518-pptpbund)? And if > so, how do I change what the ppp node name will be? > > Best regards, > > Ryan Morris > > > Here are my configuration files: > --- > mpd.conf: > Hi I rewrote this ruleset .. look better? :-) > default: > load pptp0 > load pptp1 > > pptp0: > new -i ng0 pptpbundle0 pptplink0 > set ipcp ranges 192.168.0.253/32 192.168.0.128/29 > load pptp_standard > pptp1: > new -i ng1 pptpbundle1 pptplink1 > set ipcp ranges 192.168.0.252/32 192.168.0.128/29 > load pptp_standard compare this to mine: pptp1: new -i ng0 pptp1 pptp1 set ipcp ranges 208.206.78.1/32 208.206.78.4/32 load pptp_standard pptp2: new -i ng1 pptp2 pptp2 set ipcp ranges 208.206.78.1/32 208.206.78.5/32 load pptp_standard the local end should stay the same. change the far end only > > pptp_standard: > set iface disable on-demand > set iface enable proxy-arp > set iface idle 1800 > set bundle disable multilink > set link yes acfcomp protocomp > set link no pap chap > set link enable chap > set link keep-alive 10 60 > set ipcp yes vjcomp > set ipcp dns 192.168.0.1 > set ipcp nbns 192.168.0.253 > #Enable Microsoft Point-to-Point Encryption: > set bundle enable compression > set ccp yes mppc > set ccp no mpp-e40 > set ccp yes mpp-e128 > set ccp no mpp-stateless > > # END > > --- > mpd.links: > > pptplink0: > set link type pptp > set pptp self 192.168.0.253 > set pptp enable incoming > set pptp disable originate > > pptplink1: > set link type pptp > set pptp self 192.168.0.253 > set pptp enable incoming > set pptp disable originate > > #END > > --- > "Some mornings, it's just not worth chewing through the leather straps." > - Emo Philips > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 12:20:22 2002 Delivered-To: freebsd-net@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 07BC537B41E for ; Fri, 1 Mar 2002 12:20:14 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020301202013.NIIU1147.rwcrmhc52.attbi.com@InterJet.elischer.org>; Fri, 1 Mar 2002 20:20:13 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA12739; Fri, 1 Mar 2002 12:17:16 -0800 (PST) Date: Fri, 1 Mar 2002 12:17:14 -0800 (PST) From: Julian Elischer To: Tilman Linneweh Cc: freebsd-net@freebsd.org Subject: Re: WLAN Kernelpatch from dachb0den.com merging into FreeBSD? In-Reply-To: <20020227123633.0e291826.tilman@arved.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm looking at it and awaiting answers from the authors. there are a few details: Like the patches include one of their .h files we don't want that.. etc. On Wed, 27 Feb 2002, Tilman Linneweh wrote: > Hi, > > The people at dachb0den.com have written the bsd-airtools. > http://www.dachb0den.com/projects/bsd-airtools.html > With the bsd-airtools tarball comes a kernel-patch against 4.4 to get > more information from the wi-Driver. > > Are there any plans to integrate this patch (or something equivalent) into freebsd? > > regards arved > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 1 15: 9:34 2002 Delivered-To: freebsd-net@freebsd.org Received: from artemis.drwilco.net (diana.drwilco.net [66.48.127.79]) by hub.freebsd.org (Postfix) with ESMTP id 789FA37B417; Fri, 1 Mar 2002 15:09:29 -0800 (PST) Received: from ceres.drwilco.net (docwilco.xs4all.nl [213.84.68.230]) by artemis.drwilco.net (8.11.6/8.11.6) with ESMTP id g21N9OV96378 (using TLSv1/SSLv3 with cipher DES-CBC3-SHA (168 bits) verified NO); Fri, 1 Mar 2002 18:09:26 -0500 (EST) (envelope-from drwilco@drwilco.net) Message-Id: <5.1.0.14.0.20020301233259.01bf4300@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 02 Mar 2002 00:20:10 +0100 To: freebsd-net@freebsd.org, freebsd-mobile@freebsd.org From: "Rogier R. Mulhuijzen" Subject: Xircom RealPort not working on ThinkPad A22m (includes working patch) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, I plugged my RealPort card into my brand new IBM ThinkPad a few days ago and found that it was not working. I knew it worked on my old notebook with an older release of FreeBSD so I went digging. At first I thought the fact that my PCMCIA controller doesn't like 0xd0000 as base address was the culprit, but read on. It turned out that the xe driver was having trouble reading the CIS tuples. But 'pccardc dumpcis' showed the right stuff. So I looked at how xe was reading them. The answer is through bus_alloc_resource and bus_alloc_read. This makes me suspect that this method is either faulty in the current RELENG_4 or that it does not work with pccardmem settings other than 0xd0000. Looking at the ed driver I found that that doesn't use bus_ stuff at all, but read()s from the /dev/card* devices. So I implemented that in the xe driver and 'lo behold, it works! I also added a few debugging messages along the way, and made the xe driver aware of the bootverbose option. The patch is available at: http://www.bsdchicks.com/xe.patch PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=35466 Greets, Doc P.S.: I'm not subscribed to to -mobile so include me in CCs there. P.P.S.: I'm having a few people who mailed -questions try the patch too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Mar 2 2:36:59 2002 Delivered-To: freebsd-net@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [217.156.25.2]) by hub.freebsd.org (Postfix) with ESMTP id 8E43A37B400 for ; Sat, 2 Mar 2002 02:36:52 -0800 (PST) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id MAA03259; Sat, 2 Mar 2002 12:36:49 +0200 (EET) (envelope-from ady@freebsd.ady.ro) Date: Sat, 2 Mar 2002 12:36:49 +0200 (EET) From: Adrian Penisoara X-Sender: ady@ady.warpnet.ro To: freebsd-net@freebsd.org, altq@csl.sony.co.jp, snap-users@kame.net Subject: ALTQ integration in FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, For my diploma exam I will study the state of QoS in today's networking and further directions and I probably will concentrate on ALTQ in FreeBSD (as I'm pretty familiar w/ FreeBSD). I see that most of today's OSes have a default QoS implementation (at least Win2000 and OpenBSD come to my mind) and there is a growing need for QoS integration into the OS. I was wondering what kept FreeBSD from integrating a QoS implementation (as it did with Kame IPv6) -- for example what are pro and cons of integration ALTQ in FreeBSD (I saw there was a thread launched sometime in the beginning of May 2001). I also saw that ALTQ on FreeBSD seems to be used pretty much even in production. What other QoS implementation alternatives are available for FreeBSD ? Why didn't FreeBSD follow tracks along OpenBSD's integration of ALTQ ? I would be delighted to know that FreeBSD will integrate a QoS implementation (ALTQ) and I would like to contribute in this direction. Thank you, Ady (@freebsd.ady.ro) _______________________________________________________________________ | Programming in BASIC causes brain damage. | | (Edsger Wybe Dijkstra) | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Mar 2 15:26:25 2002 Delivered-To: freebsd-net@freebsd.org Received: from tnt.yi.org (possamai.xs4all.nl [213.84.64.160]) by hub.freebsd.org (Postfix) with ESMTP id 9FF1C37B400; Sat, 2 Mar 2002 15:26:02 -0800 (PST) Received: from localhost (tnt@localhost) by tnt.yi.org (8.11.6/8.11.6) with ESMTP id g22NPuU07211; Sun, 3 Mar 2002 00:26:00 +0100 (CET) (envelope-from tnt@tnt.yi.org) Date: Sun, 3 Mar 2002 00:25:56 +0100 (CET) From: Michele Possamai X-X-Sender: tnt@localhost Reply-To: possamai@xs4all.nl To: Ryan Morris Cc: freebsd-net@FreeBSD.ORG, Subject: Re: Multiple connections to MPD-netgraph as PPTP server In-Reply-To: Message-ID: <20020303002414.Q7205-100000@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org What if you change the self ipaddress in mpd.links? they are the same in both connections On Fri, 1 Mar 2002, Ryan Morris wrote: > Hello everyone, > > I recently (successfully) configured MPD-netgraph as a pptp server on my > FreeBSD machine. It works great... for one user. When I change my > configuration to support multiple PPTP bundles/links I get the following > error when starting mpd: > > bsd# mpd > Multi-link PPP for FreeBSD, by Archie L. Cobbs. > Based on iij-ppp, by Toshiharu OHNO. > mpd: pid 518, version 3.7 (root@bsd.imagineering.ca 16:39 28-Feb-2002) > [pptpbundle0] ppp node is "mpd518-pptpbund" > mpd: local IP address for PPTP is 192.168.0.253 > [pptpbundle0] using interface ng0 > [pptpbundle1] can't name ppp node: Address already in use > [pptpbundle1] netgraph initialization failed > > I have varied the IP address assignments in my configuration files, and > examples on the web have duplicated IP addresses between bundles without > causing this problem. > > Does this make reference to the ppp node name (mpd518-pptpbund)? And if > so, how do I change what the ppp node name will be? > > Best regards, > > Ryan Morris > > > Here are my configuration files: > --- > mpd.conf: > > default: > load pptp0 > load pptp1 > > pptp0: > new -i ng0 pptpbundle0 pptplink0 > set iface disable on-demand > set iface enable proxy-arp > set iface idle 1800 > set bundle disable multilink > set link yes acfcomp protocomp > set link no pap chap > set link enable chap > set link keep-alive 10 60 > set ipcp yes vjcomp > set ipcp ranges 192.168.0.253/32 192.168.0.128/29 > set ipcp dns 192.168.0.1 > set ipcp nbns 192.168.0.253 > #Enable Microsoft Point-to-Point Encryption: > set bundle enable compression > set ccp yes mppc > set ccp no mpp-e40 > set ccp yes mpp-e128 > set ccp no mpp-stateless > > pptp1: > new -i ng1 pptpbundle1 pptplink1 > set iface disable on-demand > set iface enable proxy-arp > set iface idle 1800 > set bundle disable multilink > set link yes acfcomp protocomp > set link no pap chap > set link enable chap > set link keep-alive 10 60 > set ipcp yes vjcomp > set ipcp ranges 192.168.0.252/32 192.168.0.128/29 > set ipcp dns 192.168.0.1 > set ipcp nbns 192.168.0.253 > #Enable Microsoft Point-to-Point Encryption: > set bundle enable compression > set ccp yes mppc > set ccp no mpp-e40 > set ccp yes mpp-e128 > set ccp no mpp-stateless > > # END > > --- > mpd.links: > > pptplink0: > set link type pptp > set pptp self 192.168.0.253 > set pptp enable incoming > set pptp disable originate > > pptplink1: > set link type pptp > set pptp self 192.168.0.253 > set pptp enable incoming > set pptp disable originate > > #END > > --- > "Some mornings, it's just not worth chewing through the leather straps." > - Emo Philips > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Mar 2 15:48:26 2002 Delivered-To: freebsd-net@freebsd.org Received: from creme-brulee.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id 05D5037B417; Sat, 2 Mar 2002 15:48:11 -0800 (PST) Received: from shumai.marcuscom.com (shumai.marcuscom.com [192.168.1.4]) by creme-brulee.marcuscom.com (8.11.6/8.11.6) with ESMTP id g22Nm1K06838; Sat, 2 Mar 2002 18:48:01 -0500 (EST) (envelope-from marcus@marcuscom.com) Subject: Re: Multiple connections to MPD-netgraph as PPTP server From: Joe Clarke To: possamai@xs4all.nl Cc: Ryan Morris , freebsd-net@FreeBSD.ORG, FreeBSD User Questions List In-Reply-To: <20020303002414.Q7205-100000@localhost> References: <20020303002414.Q7205-100000@localhost> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 02 Mar 2002 18:48:27 -0500 Message-Id: <1015112907.73601.9.camel@shumai.marcuscom.com> Mime-Version: 1.0 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 2002-03-02 at 18:25, Michele Possamai wrote: > What if you change the self ipaddress in mpd.links? > they are the same in both connections In my setup the pptp self address is always the same, but it isn't the same address I use as the server VPN endpoint address. For my setup, I use the following in mpd.conf: load pptpuser1 load pptpuser2 pptpuser1: new -i ng0 pptp1 pptp1 set iface disable on-demand set iface enable proxy-arp set iface idle 1800 set bundle disable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set ipcp yes vjcomp set ipcp ranges 192.168.100.1/32 192.168.100.246/32 set ipcp dns 192.168.100.1 set ipcp nbns 192.168.100.1 set bundle enable compression set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless pptpuser2: new -i ng1 pptp2 pptp2 set iface disable on-demand set iface enable proxy-arp set iface idle 1800 set bundle disable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set ipcp yes vjcomp set ipcp ranges 192.168.100.1/32 192.168.100.247/32 set ipcp dns 192.168.100.1 set ipcp nbns 192.168.100.1 set bundle enable compression set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless Then, for the .links entries: pptp1: set link type pptp set pptp self 63.x.x.x set pptp enable incoming set pptp disable originate pptp2: set link type pptp set pptp self 63.x.x.x set pptp enable incoming set pptp disable originate The 63.x.x.x address is the public external address, and 192.168.100.1 is my server VPN endpoint address as well as my internal IP address on my LAN. Joe > > On Fri, 1 Mar 2002, Ryan Morris wrote: > > > Hello everyone, > > > > I recently (successfully) configured MPD-netgraph as a pptp server on my > > FreeBSD machine. It works great... for one user. When I change my > > configuration to support multiple PPTP bundles/links I get the following > > error when starting mpd: > > > > bsd# mpd > > Multi-link PPP for FreeBSD, by Archie L. Cobbs. > > Based on iij-ppp, by Toshiharu OHNO. > > mpd: pid 518, version 3.7 (root@bsd.imagineering.ca 16:39 28-Feb-2002) > > [pptpbundle0] ppp node is "mpd518-pptpbund" > > mpd: local IP address for PPTP is 192.168.0.253 > > [pptpbundle0] using interface ng0 > > [pptpbundle1] can't name ppp node: Address already in use > > [pptpbundle1] netgraph initialization failed > > > > I have varied the IP address assignments in my configuration files, and > > examples on the web have duplicated IP addresses between bundles without > > causing this problem. > > > > Does this make reference to the ppp node name (mpd518-pptpbund)? And if > > so, how do I change what the ppp node name will be? > > > > Best regards, > > > > Ryan Morris > > > > > > Here are my configuration files: > > --- > > mpd.conf: > > > > default: > > load pptp0 > > load pptp1 > > > > pptp0: > > new -i ng0 pptpbundle0 pptplink0 > > set iface disable on-demand > > set iface enable proxy-arp > > set iface idle 1800 > > set bundle disable multilink > > set link yes acfcomp protocomp > > set link no pap chap > > set link enable chap > > set link keep-alive 10 60 > > set ipcp yes vjcomp > > set ipcp ranges 192.168.0.253/32 192.168.0.128/29 > > set ipcp dns 192.168.0.1 > > set ipcp nbns 192.168.0.253 > > #Enable Microsoft Point-to-Point Encryption: > > set bundle enable compression > > set ccp yes mppc > > set ccp no mpp-e40 > > set ccp yes mpp-e128 > > set ccp no mpp-stateless > > > > pptp1: > > new -i ng1 pptpbundle1 pptplink1 > > set iface disable on-demand > > set iface enable proxy-arp > > set iface idle 1800 > > set bundle disable multilink > > set link yes acfcomp protocomp > > set link no pap chap > > set link enable chap > > set link keep-alive 10 60 > > set ipcp yes vjcomp > > set ipcp ranges 192.168.0.252/32 192.168.0.128/29 > > set ipcp dns 192.168.0.1 > > set ipcp nbns 192.168.0.253 > > #Enable Microsoft Point-to-Point Encryption: > > set bundle enable compression > > set ccp yes mppc > > set ccp no mpp-e40 > > set ccp yes mpp-e128 > > set ccp no mpp-stateless > > > > # END > > > > --- > > mpd.links: > > > > pptplink0: > > set link type pptp > > set pptp self 192.168.0.253 > > set pptp enable incoming > > set pptp disable originate > > > > pptplink1: > > set link type pptp > > set pptp self 192.168.0.253 > > set pptp enable incoming > > set pptp disable originate > > > > #END > > > > --- > > "Some mornings, it's just not worth chewing through the leather straps." > > - Emo Philips > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Mar 2 18:16:19 2002 Delivered-To: freebsd-net@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id 5C1AD37B402; Sat, 2 Mar 2002 18:16:13 -0800 (PST) Received: from elischer.org ([64.170.121.0]) by mta5.snfc21.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GSD004ZHKROJR@mta5.snfc21.pbi.net>; Sat, 02 Mar 2002 18:11:49 -0800 (PST) Date: Sat, 02 Mar 2002 18:11:19 -0800 From: Julian Elischer Subject: Re: Multiple connections to MPD-netgraph as PPTP server To: Joe Clarke Cc: possamai@xs4all.nl, Ryan Morris , freebsd-net@FreeBSD.ORG, FreeBSD User Questions List Message-id: <3C818647.1FED0C86@elischer.org> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) Content-type: text/plain; charset=iso-8859-2 Content-transfer-encoding: 7BIT X-Accept-Language: en, hu References: <20020303002414.Q7205-100000@localhost> <1015112907.73601.9.camel@shumai.marcuscom.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Joe Clarke wrote: > > In my setup the pptp self address is always the same, but it isn't the > same address I use as the server VPN endpoint address. just a hint.... To increase readability try do your pptp rules as so: > > load pptpuser1 > load pptpuser2 > >pptp_common_settings: > set iface disable on-demand > set iface enable proxy-arp > set iface idle 1800 > set bundle disable multilink > set link yes acfcomp protocomp > set link no pap chap > set link enable chap > set link keep-alive 10 60 > set ipcp yes vjcomp > set ipcp dns 192.168.100.1 > set ipcp nbns 192.168.100.1 > set bundle enable compression > set ccp yes mppc > set ccp yes mpp-e40 > set ccp yes mpp-e128 > set ccp yes mpp-stateless > > pptpuser1: > new -i ng0 pptp1 pptp1 > set ipcp ranges 192.168.100.1/32 192.168.100.246/32 > load pptp_common_settings > > pptpuser2: > new -i ng1 pptp2 pptp2 > set ipcp ranges 192.168.100.1/32 192.168.100.247/32 > load pptp_common_settings -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message