From owner-freebsd-net Sun Feb 25 2:11:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id 55DF237B491 for ; Sun, 25 Feb 2001 02:11:40 -0800 (PST) (envelope-from pherman@frenchfries.net) Received: from husten.security.at12.de (dial-213-168-72-230.netcologne.de [213.168.72.230]) by mr200.netcologne.de (Mirapoint) with ESMTP id ABT33922; Sun, 25 Feb 2001 11:11:36 +0100 (CET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.2/8.11.2) with ESMTP id f1PAAsQ65112; Sun, 25 Feb 2001 11:10:54 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Sun, 25 Feb 2001 11:10:54 +0100 (CET) From: Paul Herman To: Jonathan Lemon Cc: Mark Peek , Garrett Wollman , Subject: Re: I have delayed ACK problems In-Reply-To: <20010224142742.T5714@prism.flugsvamp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 24 Feb 2001, Jonathan Lemon wrote: > On Sat, Feb 24, 2001 at 11:19:02AM -0800, Mark Peek wrote: > > Was there ever a final resolution to this problem? > > The patches are still sitting in my tree, as I've been unable > to come up with a test case that actually makes a difference. > > The "tar cf host:..." example is bogus, as the problem here is Jonathan is right, the patch doesn't solve the general "tar cf host:" problem, but it was similar enough to what we were seeing in production -- changing the MTU on lo0 to 1500 will make the "tar cf host:" problem/solution more apparent, when host == localhost. In anycase, we are very happy with the patch on our production servers, as it really did solve our problem. I believe the patch is 100% correct, it just doesn't fix 100% of the delayed ACK problems. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 6:49:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id 2D6AE37B401 for ; Sun, 25 Feb 2001 06:49:38 -0800 (PST) (envelope-from Peter.Blok@inter.NL.net) Received: from ntpc by altrade.nijmegen.inter.nl.net via 1Cust46.tnt15.rtm1.nl.uu.net [213.116.124.46] with SMTP id PAA14872 (8.8.8/1.3); Sun, 25 Feb 2001 15:49:32 +0100 (MET) Reply-To: From: "Peter Blok" To: "'Julian Elischer'" , Cc: "'Stefan Arentz'" , Subject: RE: netgraph pptp and alcatel adsl modems Date: Sun, 25 Feb 2001 15:47:43 +0100 Message-ID: <000801c09f39$e9786e30$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0009_01C09F42.4B3CD630" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3A98A112.19BDA328@elischer.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0009_01C09F42.4B3CD630 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit I'm sorry. I don't know what went wrong. Here it is again. -----Original Message----- From: julian@inter.nl.net [mailto:julian@inter.nl.net]On Behalf Of Julian Elischer Sent: Sunday, February 25, 2001 07:07 To: Peter.Blok@inter.NL.net Cc: 'Stefan Arentz'; freebsd-net@FreeBSD.ORG Subject: Re: netgraph pptp and alcatel adsl modems Peter Blok wrote: > ------------------------------------------------------------------------ -------- > Name: mxstream.tar.gz > mxstream.tar.gz Type: Unix Tape Archive (application/x-tar) > Encoding: base64 this file is empty -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v ------=_NextPart_000_0009_01C09F42.4B3CD630 Content-Type: application/x-gzip; name="mxstream.tar.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="mxstream.tar.gz" H4sICBgamToAA214c3RyZWFtLnRhcgDtWntz2kgSz7/wKdp4H5hIIImXH+dUYVnEXHiogOzFlU1R QhpAZyHp9LCXSvm7X88gYcBysrk7e2+z8zNgqXumu6dnuuchLX2rbHru7NUzQpakhiTBKwCoyrv/ KZAtATSVWl2SG81GAymy3FRegfScRqWIw8gIAF75U8e7+WI5EoQvYdDLwiIzI3ai03zO8QwLlr+F UUCMZT6fXiHHJXcg2uDOJcqnX1p6DqIRRwsQTdPHn4URgTgLl1hyZpgERN+PkG77lOuwH9u9QfJi hdVDEsG6nGWHxtQh4LmiRZaGa20zbQs50jYl8OIISWX2V9lhxb4YmoHtR1CoxGFQcTzTcCokMitL 36qk7RFjv7CuNY1dKj41YIlusKmNO1zaRNdYEii0P6RI6rP2rEgIhjkzvaUPfuBFHr3a4rseoGv8 vRr+DiW1YJd6Q4gvGo59SzBCoFlPmkr9SUXc/vNBEyMSlwkJyL9EP7BFyw2zmSEx10zPJ24eXVOm 6p5zaH8l/kGRH8V/tdbk8f8SwLA4zacdsRl70crH4YgBvMNiEe0TEuCAZAEoV48zCiw8F8PFN+XC Y2YyDr3AntuugZGM4YxR6uT/aD/8VUHjHzNCQKLn0/G1+AelsR//eMnj/yXQ/iAlsxoUWgkKPBr/ MthaFj2bDoz/5hfjv1nfj3+84/H/Ejg8qExttxIu8qYFlQhXlF9eO4vTOfyUJ7/ZEa7L/2jjOf5r 7Hbt8+j4WvzLyn78K1WlweP/JYDxT+Od5gDXW8Q+pOkgdHD/CfU8SwK+72+SAIgW+I7hkkhsS9V8 JaQVbH8G4ornhT8dfCMyF+W0b59HB13/12pPxn+9Vqum8d9E0Piv1Xn8vwhKpRLcecENnefFalmp hIFZ6Rk3ZGY7pEz36blxTGBgRvQUSqmeyvVT5RgUSZLyoig+XTf3D2JBm0xBkfFzKtVOJZlWk/Ol XdB7aFSFxjGwWyqV3p4AXol5AHWgj0evz3M58VJvja8m6qDfnlx2hue/Fn743NMvN4T7Xwu7xUfX o+7g7aTdUjvdzvj6/IfPe5T73fJU2C/acNQZ9M9/ToQn9/eFn/Ovd8p+GI2HWquHEvBzCKPIcC0j sCD04sAkIaVnOpeeg5TN/8S165rf5lhFEnB23TiW3jZSxx7arunEFoG/YTKfB4a/qLjzCdUyD0h5 8SazyJqOvsDfSome8JTgUmt3+p0xumnECJVMU2rHQr36YErtRKg3U1Mo4km48IIol6NHTBMfL89y lRKocRAQN1ofPFEqlZ8cK0VBjN7z/Mh2Z16O/vfc8GyXS9tjRoHDipj09wytP7RnFpnlNr34mlUx F0aA+ukJVj9eftT1sT7RrwZ9bdLV+vAa5E+sLnEte8a03K+V0fMyFLetkqkr6XjVYSrXw+GRU+pN oaFsDXx5a+BTjLTxRNe0Yevycihs0bR+66KrbVMuO6M16anGMVG0Mf33PSGjGewKHX5hu0awgsSb T/WmXFUEudp8MF2unghy7Tg1PkebPiKR6i3pqb4A/ffdrgDFW8+2oHS01Qi4T5vxGQrpWfhHVA/l cvlTQcjlCpfpQwJmU0H4nfITl1AFqVNgzymocn1giV1nu3OmTWcEN15OSVCgVX+PrtSzibIH31Id tHzazPsnx4LSlAXlWFq7dF2VjVc4B2qAioO446qG4xTZYBbA9gUWEcLmoJWN2AutNVRb+qTVvxbW lPaw1dMoaXTdV/dKq61ud9Lr9CcX+kjYJrU+rEk2hv7EjTyjOO/SbWHHPxKgUKDfo7P8AcohTkie MHgQRy9v8cY4WsWeQZFZVTY978YmcH7O+uMoERqQKA7coign5Wnwim9YDjIsK8C22P7ZOnkeK4Jy shOef57+gc94uZ8YDpiarjcvdt9OqGgc1IWPP4af1qf4GALA7nDxY6FAx70R39CnYULqpSRTHiWK vqH/D77JIwff5JFd4zaOOPy/HaebhEGT0v3/cNhmpZkmZu7mduZu1mWh2ZC3xzVAknKTlFc0TAGM WwF+WutJJgcB5qrnzrp2GB2dPTQei1AScd/7lhGR4hZvituMmy9MwAaO1O10epowcDp3fczQ0ay4 37uPZ2n06o8h+rZk3DLn7qveTs6bB+CphUaIK/2oKCVG33/fu9lwFT736x9f2/8puO1L9n94KTXZ +x/1Kt//vQQOIV3YF2tHZdDWz2ejBYEpDcWUCaaHm4A7O1owXl8bvx229KtkQVbOH0IHY+rWtmLD AZeWpUviEOPZhSlJHvtaDwJMDxf1oe9hJXeeSEEhDs0aFtZwvLszWHh35JYEAtawQ8CP60VsnWZG zgpNw11WSFeqRrixE2Xc2Y5DX9vwlkZk02fLK2CvtjxW+657CUvPirHBmG0pf2M5ykn0GQ6mDWsF 9G0Lm7YBc5DHCt+QwCUO+swwF+sn5sxuWKA9BgrYVYZZFHxjjlMnKc/LAuBOywhXrlk8Pirn07V2 LnVsLne41S+AURqR5eNikxaddjLoF3o7g6p2Ruogg66pV5nk8ZU2zKCzOW8y1Lqt6wzu1aCrZZA7 uOfOor8bDdR32jiD0+110Is9XVeZ89GXIZag77DEdkBfogk8nBFIRIcAPXEIoUg7LNmxWkf5w8cy qbSJOujpQ21Et/UZalkRra8Or/VxdgmcaZQeLgEyWLquZ1MHWW2nM9fbYRZn2Fbl2omUwXnSXWMt S9B4nGXm+04G8Ze/q9/3XMfBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHB8b3g 38vh6DsAUAAA ------=_NextPart_000_0009_01C09F42.4B3CD630-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 6:57:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 1E6AE37B4EC for ; Sun, 25 Feb 2001 06:57:30 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1PEuQ268719; Sun, 25 Feb 2001 08:56:26 -0600 (CST) (envelope-from jlemon) Date: Sun, 25 Feb 2001 08:56:26 -0600 From: Jonathan Lemon To: Paul Herman Cc: Jonathan Lemon , Mark Peek , Garrett Wollman , net@FreeBSD.ORG Subject: Re: I have delayed ACK problems Message-ID: <20010225085626.V5714@prism.flugsvamp.com> References: <20010224142742.T5714@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Feb 25, 2001 at 11:10:54AM +0100, Paul Herman wrote: > On Sat, 24 Feb 2001, Jonathan Lemon wrote: > > > On Sat, Feb 24, 2001 at 11:19:02AM -0800, Mark Peek wrote: > > > Was there ever a final resolution to this problem? > > > > The patches are still sitting in my tree, as I've been unable > > to come up with a test case that actually makes a difference. > > > > The "tar cf host:..." example is bogus, as the problem here is > > Jonathan is right, the patch doesn't solve the general "tar cf host:" > problem, but it was similar enough to what we were seeing in > production -- changing the MTU on lo0 to 1500 will make the > "tar cf host:" problem/solution more apparent, when host == localhost. Hmm, yes, by doing that, I'm able to reproduce the condition locally, thanks for pointing out a good test case. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 7:25: 2 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 179E437B503 for ; Sun, 25 Feb 2001 07:24:57 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1PFNtp69595; Sun, 25 Feb 2001 09:23:55 -0600 (CST) (envelope-from jlemon) Date: Sun, 25 Feb 2001 09:23:55 -0600 From: Jonathan Lemon To: Jesper Skriver Cc: Jonathan Lemon , net@freebsd.org Subject: Re: ICMP unreachables, take II. Message-ID: <20010225092355.W5714@prism.flugsvamp.com> References: <20010222185412.E5714@prism.flugsvamp.com> <20010223034952.A6694@skriver.dk> <20010222212044.H5714@prism.flugsvamp.com> <20010223043405.B6694@skriver.dk> <20010223052012.A39613@skriver.dk> <20010224235618.C57625@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20010224235618.C57625@skriver.dk> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Feb 24, 2001 at 11:56:18PM +0100, Jesper Skriver wrote: > jesper@tam% time telnet 195.41.23.1 > Trying 195.41.23.1... > telnet: connect to address 195.41.23.1: No route to host > telnet: Unable to connect to remote host > 0.000u 0.020s 0:00.70 2.8% 88+164k 0+0io 12pf+0w > > But that is probably too fast, what if we delay the retransmit by say > 100ms efter recieving the host unreachable ? I was thinking of a slightly more generic solution, something like the patch below. This isn't explicitly tied to ICMP unreachables, though. -- Jonathan Index: tcp_timer.c =================================================================== RCS file: /ncvs/src/sys/netinet/tcp_timer.c,v retrieving revision 1.39 diff -u -r1.39 tcp_timer.c --- tcp_timer.c 2000/10/02 15:00:13 1.39 +++ tcp_timer.c 2001/02/25 05:48:00 @@ -153,6 +153,9 @@ callout_stop(tp->tt_rexmt); } +int tcp_syn_backoff[TCP_MAXRXTSHIFT + 1] = + { 1, 1, 1, 1, 1, 2, 4, 8, 16, 32, 64, 64, 64 }; + int tcp_backoff[TCP_MAXRXTSHIFT + 1] = { 1, 2, 4, 8, 16, 32, 64, 64, 64, 64, 64, 64, 64 }; @@ -393,7 +396,10 @@ tp->t_badrxtwin = ticks + (tp->t_srtt >> (TCP_RTT_SHIFT + 1)); } tcpstat.tcps_rexmttimeo++; - rexmt = TCP_REXMTVAL(tp) * tcp_backoff[tp->t_rxtshift]; + if (tp->t_state == TCPS_SYN_SENT) + rexmt = TCP_REXMTVAL(tp) * tcp_syn_backoff[tp->t_rxtshift]; + else + rexmt = TCP_REXMTVAL(tp) * tcp_backoff[tp->t_rxtshift]; TCPT_RANGESET(tp->t_rxtcur, rexmt, tp->t_rttmin, TCPTV_REXMTMAX); /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 7:49:11 2001 Delivered-To: freebsd-net@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id 52B4037B503; Sun, 25 Feb 2001 07:49:00 -0800 (PST) (envelope-from Peter.Blok@inter.NL.net) Received: from ntpc by altrade.nijmegen.inter.nl.net via 1Cust46.tnt15.rtm1.nl.uu.net [213.116.124.46] with SMTP id QAA17757 (8.8.8/1.3); Sun, 25 Feb 2001 16:48:38 +0100 (MET) Reply-To: From: "Peter Blok" To: "'Julian Elischer'" Cc: "'Mike Tancsa'" , , Subject: RE: 802.1q vlans and STABLE Date: Sun, 25 Feb 2001 16:46:47 +0100 Message-ID: <000001c09f42$29b109a0$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3A9631C0.C3A7C351@elischer.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The panic occurs in ng_ether_output, during the ifconfig of the first vlan interface. It is coming from SIOCSIFADDR. It tries to do an arp request. The reason of the the panic is NULL pointer to the netgraph structure. I am not an expert to this code, but I believe this should have been done in ng_ether_attach. I had difficulty re-producing this on my test machine, because the conf file was different. In my configuration the attach is probably not done because I don't have a couple of drivers configured in. I'm still looking at it. Peter -----Original Message----- From: julian@inter.nl.net [mailto:julian@inter.nl.net]On Behalf Of Julian Elischer Sent: Friday, February 23, 2001 10:48 To: Peter.Blok@inter.NL.net Cc: 'Mike Tancsa'; stable@freebsd.org; freebsd-net@freebsd.org Subject: Re: 802.1q vlans and STABLE Peter Blok wrote: > > I am working with VLANs and a BayStack 450-T without stability problems, > except when you configure NETGRAPH at the same time. The kernel crashes > during boot-up. > huh? can you give me more on this? -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 8:34:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id B740937B491 for ; Sun, 25 Feb 2001 08:34:32 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 456473E55; Sun, 25 Feb 2001 17:34:31 +0100 (CET) Date: Sun, 25 Feb 2001 17:34:31 +0100 From: Jesper Skriver To: Jonathan Lemon Cc: net@freebsd.org Subject: Re: ICMP unreachables, take II. Message-ID: <20010225173431.A67100@skriver.dk> References: <20010222185412.E5714@prism.flugsvamp.com> <20010223034952.A6694@skriver.dk> <20010222212044.H5714@prism.flugsvamp.com> <20010223043405.B6694@skriver.dk> <20010223052012.A39613@skriver.dk> <20010224235618.C57625@skriver.dk> <20010225092355.W5714@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010225092355.W5714@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Sun, Feb 25, 2001 at 09:23:55AM -0600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Feb 25, 2001 at 09:23:55AM -0600, Jonathan Lemon wrote: > On Sat, Feb 24, 2001 at 11:56:18PM +0100, Jesper Skriver wrote: > > jesper@tam% time telnet 195.41.23.1 > > Trying 195.41.23.1... > > telnet: connect to address 195.41.23.1: No route to host > > telnet: Unable to connect to remote host > > 0.000u 0.020s 0:00.70 2.8% 88+164k 0+0io 12pf+0w > > > > But that is probably too fast, what if we delay the retransmit by say > > 100ms efter recieving the host unreachable ? > > I was thinking of a slightly more generic solution, something like > the patch below. This isn't explicitly tied to ICMP unreachables, > though. Looks good to me, and it cut's the timout from 75 secs to 12 secs when we get ICMP unreachables, and remain the 75 secs as it should, when we get no ICMP unreachables. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 8:50:36 2001 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (pm01p04.wintek.com [206.230.3.84]) by hub.freebsd.org (Postfix) with ESMTP id 4C49F37B491 for ; Sun, 25 Feb 2001 08:50:28 -0800 (PST) (envelope-from csg@waterspout.com) Received: from waterspout.com (csg@localhost [127.0.0.1]) by dustdevil.waterspout.com (8.11.1/8.11.1) with ESMTP id f1PGpE850331; Sun, 25 Feb 2001 11:51:14 -0500 (EST) (envelope-from csg@waterspout.com) Message-Id: <200102251651.f1PGpE850331@dustdevil.waterspout.com> To: Mike Tancsa Cc: freebsd-net@freebsd.org Subject: Re: 802.1q vlans and STABLE In-Reply-To: Your message of "Sat, 24 Feb 2001 12:13:03 EST." <4.2.2.20010224121224.03f12370@marble.sentex.net> From: csg@waterspout.com (C. Stephen Gunn) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <50327.983119874.1@waterspout.com> Date: Sun, 25 Feb 2001 11:51:14 -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 24 Feb 2001 12:13:03 EST, Mike Tancsa wrote: > At 11:17 AM 2/24/2001 -0500, C. Stephen Gunn wrote: > > >2/3 of our traffic started showing up on the wrong logical network. > > How did you work around it ? Or were you able to ? We had to disable CEF on those subnets. Or only have two vlan's per interface card. I also hacked together a weird patch to mutate the MAC address from the parent card, but that didn't help since the Cisco threw away too much info in the hash (apparently). I'm sure that I could have gotten that to work, but it was the wrong solution. Cisco opened a bug on it for PU, so there may be an option in newer CEF capable switches for how to deal with hash collisions. - Steve -- C. Stephen Gunn | WaterSpout Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 10:21:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from ady.warpnet.ro (ftp.warpnet.ro [194.102.224.8]) by hub.freebsd.org (Postfix) with ESMTP id 9425D37B401; Sun, 25 Feb 2001 10:20:37 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id UAA00953; Sun, 25 Feb 2001 20:26:40 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Sun, 25 Feb 2001 20:26:40 +0200 (EET) From: Adrian Penisoara To: freebsd-stable@freebsd.org, freebsd-net@freebsd.org Subject: Kernel crush due to frag attack Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-693727142-983125600=:446" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk 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-693727142-983125600=:446 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, As we are facing a heavy fragments attack (40-60byte packets in a ~ 1000 pkts/sec flow) I see some sporadic panics. Kernel/world is 4.2-STABLE as of 18 Jan 2001 -- it's a production machine and I hadn't yet the chance for another update; if it's been fixed in the mean time I would be glad to hear it... I have attached a gdb trace and a snip of a tcpdump log. When I rebuilt the kernel with debug options it seemed to crush less often. I remember that at the time of this panic I had an ipfw rule to deny IP fragments. If you need further data just ask, I'd be glad to help, Ady (@warpnet.ro) --0-693727142-983125600=:446 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; name="gdb.log" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: gdb -k log Content-Disposition: attachment; filename="gdb.log" U2NyaXB0IHN0YXJ0ZWQgb24gU3VuIEZlYiAyNSAyMDowMDoxNCAyMDAxDQpH TlUgZ2RiIDQuMTgNDQpDb3B5cmlnaHQgMTk5OCBGcmVlIFNvZnR3YXJlIEZv dW5kYXRpb24sIEluYy4NDQpHREIgaXMgZnJlZSBzb2Z0d2FyZSwgY292ZXJl ZCBieSB0aGUgR05VIEdlbmVyYWwgUHVibGljIExpY2Vuc2UsIGFuZCB5b3Ug YXJlDQ0Kd2VsY29tZSB0byBjaGFuZ2UgaXQgYW5kL29yIGRpc3RyaWJ1dGUg Y29waWVzIG9mIGl0IHVuZGVyIGNlcnRhaW4gY29uZGl0aW9ucy4NDQpUeXBl ICJzaG93IGNvcHlpbmciIHRvIHNlZSB0aGUgY29uZGl0aW9ucy4NDQpUaGVy ZSBpcyBhYnNvbHV0ZWx5IG5vIHdhcnJhbnR5IGZvciBHREIuICBUeXBlICJz aG93IHdhcnJhbnR5IiBmb3IgZGV0YWlscy4NDQpUaGlzIEdEQiB3YXMgY29u ZmlndXJlZCBhcyAiaTM4Ni11bmtub3duLWZyZWVic2QiLg0NCihrZ2RiKSBz eW1ib2wtZmlsZSBrZXJuZWwuZGVidWcNDQpSZWFkaW5nIHN5bWJvbHMgZnJv bSBrZXJuZWwuZGVidWcuLi5kb25lLg0NCihrZ2RiKSBleGVjLWZpbGUgL3Zh ci9jcmFzaC9rZXJuZWwuMA0NCihrZ2RiKSBjb3JlLWZpbGUgL3Zhci9jcmFz aC92bWNvcmUuMA0NCklkbGVQVEQgMjkyODY0MA0NCmluaXRpYWwgcGNiIGF0 IDI0ZDFhMA0NCnBhbmljc3RyOiBwYWdlIGZhdWx0DQ0KcGFuaWMgbWVzc2Fn ZXM6DQ0KLS0tDQ0KRmF0YWwgdHJhcCAxMjogcGFnZSBmYXVsdCB3aGlsZSBp biBrZXJuZWwgbW9kZQ0NCmZhdWx0IHZpcnR1YWwgYWRkcmVzcwk9IDB4ODlj MGM4MDANDQpmYXVsdCBjb2RlCQk9IHN1cGVydmlzb3IgcmVhZCwgcGFnZSBu b3QgcHJlc2VudA0NCmluc3RydWN0aW9uIHBvaW50ZXIJPSAweDg6MHhjMDE0 ZGU5OA0NCnN0YWNrIHBvaW50ZXIJICAgICAgICA9IDB4MTA6MHhjMDIzMTM0 MA0NCmZyYW1lIHBvaW50ZXIJICAgICAgICA9IDB4MTA6MHhjMDIzMTM1Yw0N CmNvZGUgc2VnbWVudAkJPSBiYXNlIDB4MCwgbGltaXQgMHhmZmZmZiwgdHlw ZSAweDFiDQ0KCQkJPSBEUEwgMCwgcHJlcyAxLCBkZWYzMiAxLCBncmFuIDEN DQpwcm9jZXNzb3IgZWZsYWdzCT0gaW50ZXJydXB0IGVuYWJsZWQsIHJlc3Vt ZSwgSU9QTCA9IDANDQpjdXJyZW50IHByb2Nlc3MJCT0gSWRsZQ0NCmludGVy cnVwdCBtYXNrCQk9IG5ldCANDQp0cmFwIG51bWJlcgkJPSAxMg0NCnBhbmlj OiBwYWdlIGZhdWx0DQ0KDQ0Kc3luY2luZyBkaXNrcy4uLiANDQoNDQpGYXRh bCB0cmFwIDEyOiBwYWdlIGZhdWx0IHdoaWxlIGluIGtlcm5lbCBtb2RlDQ0K ZmF1bHQgdmlydHVhbCBhZGRyZXNzCT0gMHgzMA0NCmZhdWx0IGNvZGUJCT0g c3VwZXJ2aXNvciByZWFkLCBwYWdlIG5vdCBwcmVzZW50DQ0KaW5zdHJ1Y3Rp b24gcG9pbnRlcgk9IDB4ODoweGMwMWE5MDM0DQ0Kc3RhY2sgcG9pbnRlcgkg ICAgICAgID0gMHgxMDoweGMwMjMxMTcwDQ0KZnJhbWUgcG9pbnRlcgkgICAg ICAgID0gMHgxMDoweGMwMjMxMTc0DQ0KY29kZSBzZWdtZW50CQk9IGJhc2Ug MHgwLCBsaW1pdCAweGZmZmZmLCB0eXBlIDB4MWINDQoJCQk9IERQTCAwLCBw cmVzIDEsIGRlZjMyIDEsIGdyYW4gMQ0NCnByb2Nlc3NvciBlZmxhZ3MJPSBp bnRlcnJ1cHQgZW5hYmxlZCwgcmVzdW1lLCBJT1BMID0gMA0NCmN1cnJlbnQg cHJvY2VzcwkJPSBJZGxlDQ0KaW50ZXJydXB0IG1hc2sJCT0gbmV0IGJpbyBj YW0gDQ0KdHJhcCBudW1iZXIJCT0gMTINDQpwYW5pYzogcGFnZSBmYXVsdA0N ClVwdGltZTogNWQxNGg0NW00MnMNDQoNDQpkdW1waW5nIHRvIGRldiAjYWQv MHgyMDAwMSwgb2Zmc2V0IDUyNTk1Mw0NCmR1bXAgYXRhMDogcmVzZXR0aW5n IGRldmljZXMgLi4gZG9uZQ0NCjEyNiAxMjUgMTI0IDEyMyAxMjIgMTIxIDEy MCAxMTkgMTE4IDExNyAxMTYgMTE1IDExNCAxMTMgMTEyIDExMSAxMTAgMTA5 IDEwOCAxMDcgMTA2IDEwNSAxMDQgMTAzIDEwMiAxMDEgMTAwIDk5IDk4IDk3 IDk2IDk1IDk0IDkzIDkyIDkxIDkwIDg5IDg4IDg3IDg2IDg1IDg0IDgzIDgy IDgxIDgwIDc5IDc4IDc3IDc2IDc1IDc0IDczIDcyIDcxIDcwIDY5IDY4IDY3 IDY2IDY1IDY0IDYzIDYyIDYxIDYwIDU5IDU4IDU3IDU2IDU1IDU0IDUzIDUy IDUxIDUwIDQ5IDQ4IDQ3IDQ2IDQ1IDQ0IDQzIDQyIDQxIDQwIDM5IDM4IDM3 IDM2IDM1IDM0IDMzIDMyIDMxIDMwIDI5IDI4IDI3IDI2IDI1IDI0IDIzIDIy IDIxIDIwIDE5IDE4IDE3IDE2IDE1IDE0IDEzIDEyIDExIDEwIDkgOCA3IDYg NSA0IDMgMiAxIDAgDQ0KLS0tDQ0KIzAgIGR1bXBzeXMgKCkgYXQgLi4vLi4v a2Vybi9rZXJuX3NodXRkb3duLmM6NDY5DQ0KNDY5CQlpZiAoZHVtcGluZysr KSB7DQ0KKGtnZGIpIGJ0DQ0KIzAgIGR1bXBzeXMgKCkgYXQgLi4vLi4va2Vy bi9rZXJuX3NodXRkb3duLmM6NDY5DQ0KIzEgIDB4YzAxMzJkNjcgaW4gYm9v dCAoaG93dG89MjYwKSBhdCAuLi8uLi9rZXJuL2tlcm5fc2h1dGRvd24uYzoz MDkNDQojMiAgMHhjMDEzMzBlNCBpbiBwb3dlcm9mZl93YWl0IChqdW5rPTB4 YzAyMjkyYWYsIGhvd3RvPTApDQ0KICAgIGF0IC4uLy4uL2tlcm4va2Vybl9z aHV0ZG93bi5jOjU1Ng0NCiMzICAweGMwMWY4ZTA1IGluIHRyYXBfZmF0YWwg KGZyYW1lPTB4YzAyMzExMzAsIGV2YT00OCkNDQogICAgYXQgLi4vLi4vaTM4 Ni9pMzg2L3RyYXAuYzo5NTENDQojNCAgMHhjMDFmOGFkZCBpbiB0cmFwX3Bm YXVsdCAoZnJhbWU9MHhjMDIzMTEzMCwgdXNlcm1vZGU9MCwgZXZhPTQ4KQ0N CiAgICBhdCAuLi8uLi9pMzg2L2kzODYvdHJhcC5jOjg0NA0NCiM1ICAweGMw MWY4NmMzIGluIHRyYXAgKGZyYW1lPXt0Zl9mcyA9IDE2LCB0Zl9lcyA9IDE2 LCB0Zl9kcyA9IC0xMDcyNTYyMTYwLCANDQogICAgICB0Zl9lZGkgPSAwLCB0 Zl9lc2kgPSAtMTA3MTI0NTc5MiwgdGZfZWJwID0gLTEwNzE0NDM1OTYsIA0N CiAgICAgIHRmX2lzcCA9IC0xMDcxNDQzNjIwLCB0Zl9lYnggPSAtMTA3MTM4 NTA2MCwgdGZfZWR4ID0gNjg2NDk2MCwgDQ0KICAgICAgdGZfZWN4ID0gNSwg dGZfZWF4ID0gMCwgdGZfdHJhcG5vID0gMTIsIHRmX2VyciA9IDAsIA0NCiAg ICAgIHRmX2VpcCA9IC0xMDcyMDAwOTcyLCB0Zl9jcyA9IDgsIHRmX2VmbGFn cyA9IDY2MDU0LCB0Zl9lc3AgPSAwLCANDQogICAgICB0Zl9zcyA9IC0xMDcx NDQzNTY4fSkgYXQgLi4vLi4vaTM4Ni9pMzg2L3RyYXAuYzo0NDMNDQojNiAg MHhjMDFhOTAzNCBpbiBhY3F1aXJlX2xvY2sgKGxrPTB4YzAyM2Y2MWMpDQ0K ICAgIGF0IC4uLy4uL3Vmcy9mZnMvZmZzX3NvZnRkZXAuYzoyNjgNDQojNyAg MHhjMDFhZDJjZSBpbiBzb2Z0ZGVwX2ZzeW5jX21vdW50ZGV2ICh2cD0weGM4 ODBmYTgwKQ0NCiAgICBhdCAuLi8uLi91ZnMvZmZzL2Zmc19zb2Z0ZGVwLmM6 Mzg0Ng0NCiM4ICAweGMwMWIxNDNhIGluIGZmc19mc3luYyAoYXA9MHhjMDIz MTFlOCkgYXQgLi4vLi4vdWZzL2Zmcy9mZnNfdm5vcHMuYzoxMzQNDQojOSAg MHhjMDFiMDEzYSBpbiBmZnNfc3luYyAobXA9MHhjMGNkNGMwMCwgd2FpdGZv cj0yLCBjcmVkPTB4YzA3MmM5MDAsIA0NCiAgICBwPTB4YzAyNjE2MjApIGF0 IHZub2RlX2lmLmg6NTM3DQ0KIzEwIDB4YzAxNjEwOWIgaW4gc3luYyAocD0w eGMwMjYxNjIwLCB1YXA9MHgwKSBhdCAuLi8uLi9rZXJuL3Zmc19zeXNjYWxs cy5jOjU0NQ0NCiMxMSAweGMwMTMyYjNhIGluIGJvb3QgKGhvd3RvPTI1Nikg YXQgLi4vLi4va2Vybi9rZXJuX3NodXRkb3duLmM6MjMzDQ0KIzEyIDB4YzAx MzMwZTQgaW4gcG93ZXJvZmZfd2FpdCAoanVuaz0weGMwMjI5MmFmLCBob3d0 bz0wKQ0NCiAgICBhdCAuLi8uLi9rZXJuL2tlcm5fc2h1dGRvd24uYzo1NTYN DQojMTMgMHhjMDFmOGUwNSBpbiB0cmFwX2ZhdGFsIChmcmFtZT0weGMwMjMx MzAwLCBldmE9MjMxMTExMjcwNCkNDQogICAgYXQgLi4vLi4vaTM4Ni9pMzg2 L3RyYXAuYzo5NTENDQojMTQgMHhjMDFmOGFkZCBpbiB0cmFwX3BmYXVsdCAo ZnJhbWU9MHhjMDIzMTMwMCwgdXNlcm1vZGU9MCwgZXZhPTIzMTExMTI3MDQp DQ0KICAgIGF0IC4uLy4uL2kzODYvaTM4Ni90cmFwLmM6ODQ0DQ0KIzE1IDB4 YzAxZjg2YzMgaW4gdHJhcCAoZnJhbWU9e3RmX2ZzID0gLTEwNzIyMzQ0ODAs IHRmX2VzID0gNjQyMjU0NCwgDQ0KICAgICAgdGZfZHMgPSAxNiwgdGZfZWRp ID0gLTEwNzE0NDMxMTIsIHRmX2VzaSA9IDY0MjI1MjgsIA0NCiAgICAgIHRm X2VicCA9IC0xMDcxNDQzMTA4LCB0Zl9pc3AgPSAtMTA3MTQ0MzE1NiwgdGZf ZWJ4ID0gMSwgDQ0KICAgICAgdGZfZWR4ID0gLTE5ODM4NTQ1OTIsIHRmX2Vj eCA9IDEsIHRmX2VheCA9IDY0MjI1MjgsIHRmX3RyYXBubyA9IDEyLCANDQog ICAgICB0Zl9lcnIgPSAwLCB0Zl9laXAgPSAtMTA3MjM3NDEyMCwgdGZfY3Mg PSA4LCB0Zl9lZmxhZ3MgPSA2NjE4MiwgDQ0KICAgICAgdGZfZXNwID0gLTEw NjAwMjMwNDAsIHRmX3NzID0gLTEwNzEzMjM5MTZ9KSBhdCAuLi8uLi9pMzg2 L2kzODYvdHJhcC5jOjQ0Mw0NCiMxNiAweGMwMTRkZTk4IGluIG1fY29weW0g KG09MHhjMDdlN2MwMCwgb2ZmMD0wLCBsZW49NDAsIHdhaXQ9MSkNDQogICAg YXQgLi4vLi4va2Vybi91aXBjX21idWYuYzo2MjENDQojMTcgMHhjMDE3ZDgz ZiBpbiBpcF9mb3J3YXJkIChtPTB4YzA3ZTdjMDAsIHNyY3J0PTApDQ0KICAg IGF0IC4uLy4uL25ldGluZXQvaXBfaW5wdXQuYzoxNTA4DQ0KIzE4IDB4YzAx N2NhY2EgaW4gaXBfaW5wdXQgKG09MHhjMDdlN2MwMCkgYXQgLi4vLi4vbmV0 aW5ldC9pcF9pbnB1dC5jOjU2Mw0NCi0tLVR5cGUgPHJldHVybj4gdG8gY29u dGludWUsIG9yIHEgPHJldHVybj4gdG8gcXVpdC0tLQ0NCiMxOSAweGMwMTdj ZDE3IGluIGlwaW50ciAoKSBhdCAuLi8uLi9uZXRpbmV0L2lwX2lucHV0LmM6 NzU5DQ0KKGtnZGIpIHVwIDE2DQ0KIzE2IDB4YzAxNGRlOTggaW4gbV9jb3B5 bSAobT0weGMwN2U3YzAwLCBvZmYwPTAsIGxlbj00MCwgd2FpdD0xKQ0NCiAg ICBhdCAuLi8uLi9rZXJuL3VpcGNfbWJ1Zi5jOjYyMQ0NCjYyMQkJCQkJbi0+ bV9wa3RoZHIubGVuIC09IG9mZjA7DQ0KKGtnZGIpIGxpc3QNDQo2MTYJCQlp ZiAobiA9PSAwKQ0NCjYxNwkJCQlnb3RvIG5vc3BhY2U7DQ0KNjE4CQkJaWYg KGNvcHloZHIpIHsNDQo2MTkJCQkJTV9DT1BZX1BLVEhEUihuLCBtKTsNDQo2 MjAJCQkJaWYgKGxlbiA9PSBNX0NPUFlBTEwpDQ0KNjIxCQkJCQluLT5tX3Br dGhkci5sZW4gLT0gb2ZmMDsNDQo2MjIJCQkJZWxzZQ0NCjYyMwkJCQkJbi0+ bV9wa3RoZHIubGVuID0gbGVuOw0NCjYyNAkJCQljb3B5aGRyID0gMDsNDQo2 MjUJCQl9DQ0KKGtnZGIpIHByaW50IG4NDQokMSA9IChzdHJ1Y3QgbWJ1ZiAq KSAweDY2MWMyMA0NCihrZ2RiKSBwcmludCAqbg0NCmNhbm5vdCByZWFkIHBy b2MgYXQgMA0NCihrZ2RiKSBwcmludCBtDQ0KJDIgPSAoc3RydWN0IG1idWYg KikgMHhjMDdlN2MwMA0NCihrZ2RiKSBwcmludCAqbQ0NCiQzID0ge21faGRy ID0ge21oX25leHQgPSAweDAsIG1oX25leHRwa3QgPSAweDAsIG1oX2RhdGEg PSAweGMwODVjODIwICJFIiwgDQ0KICAgIG1oX2xlbiA9IDQwLCBtaF90eXBl ID0gMSwgbWhfZmxhZ3MgPSAzfSwgTV9kYXQgPSB7TUggPSB7TUhfcGt0aGRy ID0gew0NCiAgICAgICAgcmN2aWYgPSAweGMwYzc2YzAwLCBsZW4gPSA0MCwg aGVhZGVyID0gMHgwLCBjc3VtX2ZsYWdzID0gMCwgDQ0KICAgICAgICBjc3Vt X2RhdGEgPSA2LCBhdXggPSAweDB9LCBNSF9kYXQgPSB7TUhfZXh0ID0gew0N CiAgICAgICAgICBleHRfYnVmID0gMHhjMDg1YzgwMCAiIiwgZXh0X2ZyZWUg PSAwLCBleHRfc2l6ZSA9IDIwNDgsIA0NCiAgICAgICAgICBleHRfcmVmID0g MH0sIA0NCiAgICAgICAgTUhfZGF0YWJ1ZiA9ICJcMDAwyFwyMDXAXDAwMFww MDBcMDAwXDAwMFwwMDBcYlwwMDBcMDAwXDAwMFwwMDBcMDAwXDAwMEVcMDAw XDAwMCxWXDIxMkBcMDAwQFwwMDbVa8JcMjMx81wwMDHPLlwyMTJcZlwwMDRc MDM1XDAwMDXD6s4qXDAwMFwwMDBcMDAwXDAwMGBcMDAyQFwwMDCy6FwwMDBc MDAwXDAwMlwwMDRcMDA1tFwwMDBcMDAxXDAwMFwwMDFcMDAwXDAwMFwwMDZc MjIwXDAwMFwwMDTNtXBMXDAwNVpETkVUXDAwM2NvbVwwMDBcMDAwXDAwMlww MDBcMDAxXDAwMFwwMDDq3FwwMDBcMDI3XGJETlNBVVRIMVwwMDNTWVNcMDA0 R1RFSVwwMDNcMDAwXDAwMCFF33tcMDAwXDIyMCdcMjMzeeRcYlwwMDBFXDAw MFwwMDBcMDAwXGZ10nVcMDAwwMpcMDIw33FcYlwwMDBFXDAwMFwwMDBCYv9c MDAwXDAwMEBcMDIx8fzCXDIzMfNcMDAxz/GgXCJcMDA0XDAzNVwwMDA1XDAw MC5cMjEyJqu3XDAwMVwwMDBcMDAwXDAwMVwwMDBcMDAwXDAwMFwwMDBcMDAw XDAwMFxidWx0cmFtYW5cMDA0emVcMDAwXDAwMCFFIi4uLn19LCANDQogICAg TV9kYXRhYnVmID0gIlwwMDBsx8AoIiwgJ1wwMDAnIDxyZXBlYXRzIDExIHRp bWVzPiwgIlwwMDZcMDAwXDAwMFwwMDBcMDAwXDAwMFwwMDBcMDAwXDAwMMhc MjA1wFwwMDBcMDAwXDAwMFwwMDBcMDAwXGJcMDAwXDAwMFwwMDBcMDAwXDAw MFwwMDBFXDAwMFwwMDAsVlwyMTJAXDAwMEBcMDA21WvCXDIzMfNcMDAxzy5c MjEyXGZcMDA0XDAzNVwwMDA1w+rOKlwwMDBcMDAwXDAwMFwwMDBgXDAwMkBc MDAwsuhcMDAwXDAwMFwwMDJcMDA0XDAwNbRcMDAwXDAwMVwwMDBcMDAxXDAw MFwwMDBcMDA2XDIyMFwwMDBcMDA0zbVwTFwwMDVaRE5FVFwwMDNjb21cMDAw XDAwMFwwMDJcMDAwXDAwMVwwMDBcMDAw6txcMDAwXDAyN1xiRE5TQVVUSDFc MDAzU1lTXDAwNEdURUlcMDAzXDAwMFwwMDAhRd97XDAwMFwyMjAnXDIzM3nk XGJcMDAwRVwwMDBcMDAwXDAwMFxmddJ1XDAwMMDKXDAyMN9xXGJcMDAwRVww MDBcMDAwQmL/XDAwMFwwMDBAXDAyMfH8wlwyMzHzXDAwMc/xoFwiXDAwNFww MzVcMDAwNVwwMDAuXDIxMiart1wwMDFcMDAwXDAwMCIuLi59fQ0NCihrZ2Ri KSBwcmludCAwZmYwCCAICCAICCAICCAIb2ZmMA0NCiQ0ID0gMA0NCihrZ2Ri KSBwcmludCBsZW4NDQokNSA9IDQwDQ0KKGtnZGIpIHVwDQ0KIzE3IDB4YzAx N2Q4M2YgaW4gaXBfZm9yd2FyZCAobT0weGMwN2U3YzAwLCBzcmNydD0wKQ0N CiAgICBhdCAuLi8uLi9uZXRpbmV0L2lwX2lucHV0LmM6MTUwOA0NCjE1MDgJ CW1jb3B5ID0gbV9jb3B5KG0sIDAsIGltaW4oKGludClpcC0+aXBfbGVuLCA2 NCkpOw0NCihrZ2RiKSBsaXN0DQ0KMTUwMwkNDQoxNTA0CQkvKg0NCjE1MDUJ CSAqIFNhdmUgYXQgbW9zdCA2NCBieXRlcyBvZiB0aGUgcGFja2V0IGluIGNh c2UNDQoxNTA2CQkgKiB3ZSBuZWVkIHRvIGdlbmVyYXRlIGFuIElDTVAgbWVz c2FnZSB0byB0aGUgc3JjLg0NCjE1MDcJCSAqLw0NCjE1MDgJCW1jb3B5ID0g bV9jb3B5KG0sIDAsIGltaW4oKGludClpcC0+aXBfbGVuLCA2NCkpOw0NCjE1 MDkJCWlmIChtY29weSAmJiAobWNvcHktPm1fZmxhZ3MgJiBNX0VYVCkpDQ0K MTUxMAkJCW1fY29weWRhdGEobWNvcHksIDAsIHNpemVvZihzdHJ1Y3QgaXAp LCBtdG9kKG1jb3B5LCBjYWRkcl90KSk7DQ0KMTUxMQkNDQoxNTEyCSNpZmRl ZiBJUFNURUFMVEgNDQooa2dkYikgcHJpbnQgbQ0NCiQ2ID0gKHN0cnVjdCBt YnVmICopIDB4YzA3ZTdjMDANDQooa2dkYikgcHJpbnQgaXAtPmlwX2xlbg0N CiQ3ID0gNDANDQooa2dkYikgdXANDQojMTggMHhjMDE3Y2FjYSBpbiBpcF9p bnB1dCAobT0weGMwN2U3YzAwKSBhdCAuLi8uLi9uZXRpbmV0L2lwX2lucHV0 LmM6NTYzDQ0KNTYzCQkJaXBfZm9yd2FyZChtLCAwKTsNDQooa2dkYikgdXAN DQojMTkgMHhjMDE3Y2QxNyBpbiBpcGludHIgKCkgYXQgLi4vLi4vbmV0aW5l dC9pcF9pbnB1dC5jOjc1OQ0NCjc1OQkJCWlwX2lucHV0KG0pOw0NCihrZ2Ri KSB1cA0NCkluaXRpYWwgZnJhbWUgc2VsZWN0ZWQ7IHlvdSBjYW5ub3QgZ28g dXAuDQ0KKGtnZGIpIHENDQoNClNjcmlwdCBkb25lIG9uIFN1biBGZWIgMjUg MjA6MDI6MzIgMjAwMQ0K --0-693727142-983125600=:446 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="frag.log" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: tcpdump log Content-Disposition: attachment; filename="frag.log" MDA6MDc6MDguODkxNjYzIDUwLjIwMi45Mi4zNiA+IDE5NC4xMDIuMjI0Ljk6 IChmcmFnIDIwMTU4OjIwQDI1NikgW3RvcyAweGU4XSAgKHR0bCAyMzkpDQow MDowNzowOC44OTE5MTEgNTAuMjAyLjkyLjM2ID4gMTk0LjEwMi4yMjQuMTAz OiAoZnJhZyAyMDE1ODoyMEAyNTYpIFt0b3MgMHhlOF0gICh0dGwgMjM5KQ0K MDA6MDc6MDguODkyMzk3IDUwLjIwMi45Mi4zNiA+IDE5NC4xMDIuMjI0LjEw MzogKGZyYWcgMjAxNTg6MjBAMjU2KSBbdG9zIDB4ZThdICAodHRsIDIzOSkN CjAwOjA3OjA4Ljg5MjY4MyA1MC4yMDIuOTIuMzYgPiAxOTQuMTAyLjIyNC4x MDM6IChmcmFnIDIwMTU4OjIwQDI1NikgW3RvcyAweGU4XSAgKHR0bCAyMzkp DQowMDowNzowOC44OTI5MTkgNTAuMjAyLjkyLjM2ID4gMTk0LjEwMi4yMjQu MTAzOiAoZnJhZyAyMDE1ODoyMEAyNTYpIFt0b3MgMHhlOF0gICh0dGwgMjM5 KQ0KMDA6MDc6MDguODkzMTUxIDUwLjIwMi45Mi4zNiA+IDE5NC4xMDIuMjI0 LjEwMzogKGZyYWcgMjAxNTg6MjBAMjU2KSBbdG9zIDB4ZThdICAodHRsIDIz OSkNCjAwOjA3OjA4Ljg5NTQ4OSA1MC4yMDIuOTIuMzYgPiAxOTQuMTAyLjIy NC45OiAoZnJhZyAyMDE1ODoyMEAyNTYpIFt0b3MgMHhlOF0gICh0dGwgMjM5 KQ0KMDA6MDc6MDguODk1OTQ4IDUwLjIwMi45Mi4zNiA+IDE5NC4xMDIuMjI0 Ljk6IChmcmFnIDIwMTU4OjIwQDI1NikgW3RvcyAweGU4XSAgKHR0bCAyMzkp DQowMDowNzowOC44OTYyMDAgNTAuMjAyLjkyLjM2ID4gMTk0LjEwMi4yMjQu MTAzOiAoZnJhZyAyMDE1ODoyMEAyNTYpIFt0b3MgMHhlOF0gICh0dGwgMjM5 KQ0KMDA6MDc6MDguODk2NDM1IDUwLjIwMi45Mi4zNiA+IDE5NC4xMDIuMjI0 Ljk6IChmcmFnIDIwMTU4OjIwQDI1NikgW3RvcyAweGU4XSAgKHR0bCAyMzkp DQowMDowNzowOC44OTY3MDMgNTAuMjAyLjkyLjM2ID4gMTk0LjEwMi4yMjQu MTAzOiAoZnJhZyAyMDE1ODoyMEAyNTYpIFt0b3MgMHhlOF0gICh0dGwgMjM5 KQ0KMDA6MDc6MDguODk5OTcwIDUwLjIwMi45Mi4zNiA+IDE5NC4xMDIuMjI0 Ljk6IChmcmFnIDIwMTU4OjIwQDI1NikgW3RvcyAweGU4XSAgKHR0bCAyMzkp DQowMDowNzowOC45MDA0NDYgNTAuMjAyLjkyLjM2ID4gMTk0LjEwMi4yMjQu MTAzOiAoZnJhZyAyMDE1ODoyMEAyNTYpIFt0b3MgMHhlOF0gICh0dGwgMjM5 KQ0KMDA6MDc6MDguOTAwNzM2IDUwLjIwMi45Mi4zNiA+IDE5NC4xMDIuMjI0 Ljk6IChmcmFnIDIwMTU4OjIwQDI1NikgW3RvcyAweGU4XSAgKHR0bCAyMzkp DQowMDowNzowOC45MDA5NzIgNTAuMjAyLjkyLjM2ID4gMTk0LjEwMi4yMjQu OTogKGZyYWcgMjAxNTg6MjBAMjU2KSBbdG9zIDB4ZThdICAodHRsIDIzOSkN CjAwOjA3OjA4LjkwMTIxMCA1MC4yMDIuOTIuMzYgPiAxOTQuMTAyLjIyNC4x MDM6IChmcmFnIDIwMTU4OjIwQDI1NikgW3RvcyAweGU4XSAgKHR0bCAyMzkp DQowMDowNzowOC45MDE1MDYgNTAuMjAyLjkyLjM2ID4gMTk0LjEwMi4yMjQu MTAzOiAoZnJhZyAyMDE1ODoyMEAyNTYpIFt0b3MgMHhlOF0gICh0dGwgMjM5 KQ0KMDA6MDc6MDguOTA0MDY3IDUwLjIwMi45Mi4zNiA+IDE5NC4xMDIuMjI0 Ljk6IChmcmFnIDIwMTU4OjIwQDI1NikgW3RvcyAweGU4XSAgKHR0bCAyMzkp DQowMDowNzowOC45MjQwODggNTAuMjAyLjkyLjM2ID4gMTk0LjEwMi4yMjQu MTAzOiAoZnJhZyAyMDE1ODoyMEAyNTYpIFt0b3MgMHhlOF0gICh0dGwgMjM5 KQ0K --0-693727142-983125600=:446-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 13: 7:44 2001 Delivered-To: freebsd-net@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 9262737B401 for ; Sun, 25 Feb 2001 13:07:41 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 601483E60; Sun, 25 Feb 2001 22:07:40 +0100 (CET) Date: Sun, 25 Feb 2001 22:07:40 +0100 From: Jesper Skriver To: net@FreeBSD.org Subject: Check tcp sequence number for all ICMP messages Message-ID: <20010225220740.A76033@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We recently introduced a check for tcp sequence numbers when processing ICMP messages, it has so far only been used for the ICMP messages that trigger the session to be dropped, but it makes sense to have this check for all ICMP messages which only act on a single session. diff below, please review. Index: tcp_subr.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_subr.c,v retrieving revision 1.93 diff -u -r1.93 tcp_subr.c --- tcp_subr.c 2001/02/23 21:07:06 1.93 +++ tcp_subr.c 2001/02/25 19:36:06 @@ -978,14 +978,12 @@ struct tcphdr *th; void (*notify) __P((struct inpcb *, int)) = tcp_notify; tcp_seq tcp_sequence = 0; - int tcp_seq_check = 0; if (cmd == PRC_QUENCH) notify = tcp_quench; - else if (icmp_may_rst && cmd == PRC_UNREACH_ADMIN_PROHIB && ip) { - tcp_seq_check = 1; + else if (icmp_may_rst && cmd == PRC_UNREACH_ADMIN_PROHIB && ip) notify = tcp_drop_syn_sent; - } else if (cmd == PRC_MSGSIZE) + else if (cmd == PRC_MSGSIZE) notify = tcp_mtudisc; else if (PRC_IS_REDIRECT(cmd)) { /* @@ -1005,10 +1003,9 @@ if (ip) { th = (struct tcphdr *)((caddr_t)ip + (IP_VHL_HL(ip->ip_vhl) << 2)); - if (tcp_seq_check == 1) - tcp_sequence = ntohl(th->th_seq); + tcp_sequence = ntohl(th->th_seq); in_pcbnotify(&tcb, sa, th->th_dport, ip->ip_src, th->th_sport, - cmd, notify, tcp_sequence, tcp_seq_check); + cmd, notify, tcp_sequence, 1); } else in_pcbnotifyall(&tcb, sa, cmd, notify); } /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 13:13:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id A51AE37B401 for ; Sun, 25 Feb 2001 13:13:12 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 811A93E53; Sun, 25 Feb 2001 22:13:11 +0100 (CET) Date: Sun, 25 Feb 2001 22:13:11 +0100 From: Jesper Skriver To: net@FreeBSD.org Subject: optimize src/sys/netinet/in_pcb.c:in_pcblookup() Message-ID: <20010225221311.B76033@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org src/sys/netinet/in_pcb.c:in_pcblookup() currently do a linear search of all sessions, below is a diff that use in_pcblookup_hash instead, this should minimize the impact of a ICMP flood. please review. /Jesper Index: in_pcb.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/in_pcb.c,v retrieving revision 1.78 diff -u -r1.78 in_pcb.c --- in_pcb.c 2001/02/22 21:23:45 1.78 +++ in_pcb.c 2001/02/25 20:32:00 @@ -680,7 +680,7 @@ u_int32_t tcp_sequence; int tcp_seq_check; { - register struct inpcb *inp, *oinp; + register struct inpcb *inp; struct in_addr faddr; u_short fport = fport_arg, lport = lport_arg; int errno, s; @@ -693,36 +693,28 @@ errno = inetctlerrmap[cmd]; s = splnet(); - for (inp = LIST_FIRST(head); inp != NULL;) { + inp = in_pcblookup_hash(head->lh_first->inp_pcbinfo, faddr, fport, + laddr, lport, 0, NULL); + if (inp == NULL || inp->inp_socket == NULL) + goto out; #ifdef INET6 - if ((inp->inp_vflag & INP_IPV4) == 0) { - inp = LIST_NEXT(inp, inp_list); - continue; - } + if ((inp->inp_vflag & INP_IPV4) == 0) + goto out; #endif - if (inp->inp_faddr.s_addr != faddr.s_addr || - inp->inp_socket == 0 || inp->inp_lport != lport || - inp->inp_laddr.s_addr != laddr.s_addr || - inp->inp_fport != fport) { - inp = LIST_NEXT(inp, inp_list); - continue; - } - /* - * If tcp_seq_check is set, then skip sessions where - * the sequence number is not one of a unacknowledged - * packet. - * - * If it doesn't match, we break the loop, as only a - * single session can match on src/dst ip addresses - * and TCP port numbers. - */ - if ((tcp_seq_check == 1) && (tcp_seq_vs_sess(inp, tcp_sequence) == 0)) - break; - oinp = inp; - inp = LIST_NEXT(inp, inp_list); - if (notify) - (*notify)(oinp, errno); - } + /* + * If tcp_seq_check is set, then skip sessions where + * the sequence number is not one of a unacknowledged + * packet. + * + * If it doesn't match, we break the loop, as only a + * single session can match on src/dst ip addresses + * and TCP port numbers. + */ + if ((tcp_seq_check == 1) && (tcp_seq_vs_sess(inp, tcp_sequence) == 0)) + goto out; + if (notify) + (*notify)(inp, errno); +out: splx(s); } /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 14: 1:11 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id B3F1F37B401; Sun, 25 Feb 2001 14:01:08 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1PM07e81495; Sun, 25 Feb 2001 16:00:07 -0600 (CST) (envelope-from jlemon) Date: Sun, 25 Feb 2001 16:00:07 -0600 (CST) From: Jonathan Lemon Message-Id: <200102252200.f1PM07e81495@prism.flugsvamp.com> To: jesper@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: Check tcp sequence number for all ICMP messages X-Newsgroups: local.mail.freebsd-net In-Reply-To: Organization: Cc: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: >We recently introduced a check for tcp sequence numbers when processing >ICMP messages, it has so far only been used for the ICMP messages that >trigger the session to be dropped, but it makes sense to have this check >for all ICMP messages which only act on a single session. I was just looking at this today (as well as the hash lookup you mentioned in your other message). The big problem with both is that the TCP sequence check should not be in in_pcb.c; it should be in the tcp/udp specific files. Also, I'm not sure whether all ICMP replies (source quench, mtu) have sequence numbers within the tcp window. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 14:10:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (pm01p04.wintek.com [206.230.3.84]) by hub.freebsd.org (Postfix) with ESMTP id 2451637B401 for ; Sun, 25 Feb 2001 14:10:56 -0800 (PST) (envelope-from csg@waterspout.com) Received: from waterspout.com (csg@localhost [127.0.0.1]) by dustdevil.waterspout.com (8.11.1/8.11.2) with ESMTP id f1PMBgc51779; Sun, 25 Feb 2001 17:11:43 -0500 (EST) (envelope-from csg@waterspout.com) Message-Id: <200102252211.f1PMBgc51779@dustdevil.waterspout.com> To: Peter Blok Cc: freebsd-net@freebsd.org From: "C. Stephen Gunn" Subject: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <51774.983139091.1@waterspout.com> Date: Sun, 25 Feb 2001 17:11:31 -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Feb 25, 2001 at 04:46:47PM +0100, Peter Blok wrote: > The panic occurs in ng_ether_output, during the ifconfig of the first vlan > interface. It is coming from SIOCSIFADDR. It tries to do an arp request. The > reason of the the panic is NULL pointer to the netgraph structure. I am not > an expert to this code, but I believe this should have been done in > ng_ether_attach. > > I had difficulty re-producing this on my test machine, because the conf file > was different. In my configuration the attach is probably not done because I > don't have a couple of drivers configured in. Is it possible that the parent interface is not "ifconfig up" at the point you SIOCSIFADDR the vlan interface? Setting an address on an ethernet interface sets IFF_UP, in ether_ioctl(). So calling SIOCSIFADDR on the vlan interface eventually transmits an arp who-has on the parent interface (with 802.1q encap for the current VLAN of course) as a part of the AF_INET interface semantics. The problem is that unless you do an "ifconfig up" or some other "ifconfig" that results in if_init() getting called on the parent, some drivers (and sometimes NetGraph) aren't initialized. The vlan to arp_ifinit() -> parent->if_start() never verifies the interface is up. BOOM. I had a patch around somewhere that made vlan respect parent->if_flags, but I'm not sure where it went. I wasn't a good solution since the initial ARP who-has broadcasts were lost, which could confuse ARP handling sometimes, when there was an IP address conflict. Unfortunately I no longer work for Purdue U where I did the vlan stuff, and had a testing lab setup.. - Steve -- C. Stephen Gunn | Waterspout Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 14:15:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id 1A04F37B4EC for ; Sun, 25 Feb 2001 14:15:36 -0800 (PST) (envelope-from Peter.Blok@inter.NL.net) Received: from ntpc by altrade.nijmegen.inter.nl.net via 1Cust46.tnt15.rtm1.nl.uu.net [213.116.124.46] with SMTP id XAA08248 (8.8.8/1.3); Sun, 25 Feb 2001 23:15:22 +0100 (MET) Reply-To: From: "Peter Blok" To: "'C. Stephen Gunn'" Cc: Subject: RE: 802.1q vlans and STABLE Date: Sun, 25 Feb 2001 23:13:33 +0100 Message-ID: <000601c09f78$31bff710$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20010225170315.A50555@waterspout.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Steve, It is the order of initialization that causes this to happen. vlaninit happens before the hooks to ng_ether_attach_p are set. vlaninit is doing ether_ifattach, but without the hooks being called. Later on the first attempt to sent something (ARP) the code assumes ng_ether_attach has been called and crashes. Im am now changing the load order of ng_ether to load in an earlier stage. I am not quite sure why it is not going wrong everytime. I have two configs. The one that is working fine only loads the i4b stuff. The other doesn't. Peter -----Original Message----- From: C. Stephen Gunn [mailto:csg@waterspout.com] Sent: Sunday, February 25, 2001 23:03 To: Peter Blok Cc: freebsd-net@freebsd.org Subject: Re: 802.1q vlans and STABLE On Sun, Feb 25, 2001 at 04:46:47PM +0100, Peter Blok wrote: > The panic occurs in ng_ether_output, during the ifconfig of the first vlan > interface. It is coming from SIOCSIFADDR. It tries to do an arp request. The > reason of the the panic is NULL pointer to the netgraph structure. I am not > an expert to this code, but I believe this should have been done in > ng_ether_attach. > > I had difficulty re-producing this on my test machine, because the conf file > was different. In my configuration the attach is probably not done because I > don't have a couple of drivers configured in. Is it possible that the parent interface is not "ifconfig up" at the point you SIOCSIFADDR the vlan interface? Setting an address on an ethernet interface sets IFF_UP, in ether_ioctl(). So calling SIOCSIFADDR on the vlan interface eventually transmits an arp who-has on the parent interface (with 802.1q encap for the current VLAN of course) as a part of the AF_INET interface semantics. The problem is that unless you do an "ifconfig up" or some other "ifconfig" that results in if_init() getting called on the parent, some drivers (and sometimes NetGraph) aren't initialized. The vlan to arp_ifinit() -> parent->if_start() never verifies the interface is up. BOOM. I had a patch around somewhere that made vlan respect parent->if_flags, but I'm not sure where it went. I wasn't a good solution since the initial ARP who-has broadcasts were lost, which could confuse ARP handling sometimes, when there was an IP address conflict. Unfortunately I no longer work for Purdue U where I did the vlan stuff, and had a testing lab setup.. - Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 16:44:28 2001 Delivered-To: freebsd-net@freebsd.org Received: from VL-MS-MR002.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id 256A537B401; Sun, 25 Feb 2001 16:44:18 -0800 (PST) (envelope-from bmilekic@technokratis.com) Received: from jehovah ([24.202.203.190]) by VL-MS-MR002.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G9CA1K01.LG4; Sun, 25 Feb 2001 19:44:08 -0500 Message-ID: <00d001c09f8d$8ee4d360$becbca18@jehovah> From: "Bosko Milekic" To: "Adrian Penisoara" , , References: Subject: Re: Kernel crush due to frag attack Date: Sun, 25 Feb 2001 19:46:29 -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.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Adrian Penisoara wrote: > Hi, > > As we are facing a heavy fragments attack (40-60byte packets in a > ~ 1000 pkts/sec flow) I see some sporadic panics. Kernel/world is > 4.2-STABLE as of 18 Jan 2001 -- it's a production machine and I hadn't yet > the chance for another update; if it's been fixed in the mean time I would > be glad to hear it... > > I have attached a gdb trace and a snip of a tcpdump log. When I rebuilt > the kernel with debug options it seemed to crush less often. I remember > that at the time of this panic I had an ipfw rule to deny IP fragments. This is one of those "odd" faults I've seen in -STABLE sometimes. Thanks to good debugging information you've provided, to be noted: #16 0xc014de98 in m_copym (m=0xc07e7c00, off0=0, len=40, wait=1) at ../../kern/uipc_mbuf.c:621 621 n->m_pkthdr.len -= off0; (kgdb) list 616 if (n == 0) 617 goto nospace; 618 if (copyhdr) { 619 M_COPY_PKTHDR(n, m); 620 if (len == M_COPYALL) 621 n->m_pkthdr.len -= off0; <-- fault happens here (XXX) 622 else 623 n->m_pkthdr.len = len; 624 copyhdr = 0; 625 } (kgdb) print n $1 = (struct mbuf *) 0x661c20 (kgdb) print *n cannot read proc at 0 (kgdb) print m $2 = (struct mbuf *) 0xc07e7c00 Where the fault happens (XXX), the possible problem is that the mbuf pointer n is bad, and as printed from the debugger, it does appear to be bad. However, there are two things to note: 1. the fault virtual address displayed in the trap message: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x89c0c800 [...] is different from the one printed in your analysis (even though 0x89c0c800 seems bogus as well, although it is at a correct boundry). 2. Nothing bad happens in M_COPY_PKTHDR() which dereferences an equivalent pointer. Something seriously evil is happening here and, unfortunately, I have no idea what. Does this only happen on this one machine? Or is it reproducable on several different machines? I used to stress test -STABLE for mbuf starvation and never stumbled upon one of these `spontaneous pointer deaths' myself. Although I have seen other weird problems reported by other people, but only in RELENG_3. If you cannot reproduce it on any other machines, I would start looking at possibly bad hardware... unless someone else sees something I'm not. > If you need further data just ask, I'd be glad to help, > Ady (@warpnet.ro) Regards, Bosko. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 25 21:22: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 8442A37B401 for ; Sun, 25 Feb 2001 21:22:03 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id QAA04669; Mon, 26 Feb 2001 16:20:05 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01K0KM3W0OVK8ZKTO2@cim.alcatel.com.au>; Mon, 26 Feb 2001 16:20:04 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f1Q5K2W91359; Mon, 26 Feb 2001 16:20:02 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Mon, 26 Feb 2001 16:20:01 +1100 From: Peter Jeremy Subject: Re: 802.1q vlans and STABLE In-reply-to: ; from pjlobo@euitt.upm.es on Fri, Feb 23, 2001 at 10:52:17AM +0100 To: "Pedro J. Lobo" Cc: freebsd-net@FreeBSD.ORG Message-id: <20010226162001.E84807@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20010223152257.K36182@gsmx07.alcatel.com.au> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 2001-Feb-23 10:52:17 +0100, "Pedro J. Lobo" wrote: >On Fri, 23 Feb 2001, Peter Jeremy wrote: >> - VLAN support in driver modules for the above drivers > >Including fxp? My code only supports vlan in modules for the 558 and 559 >controllers, not for the old 557. I suspect not. I only have 559's to test on. >> - fix VLAN handling in arp(8) > >Can you ellaborate a bit more on this one? arp(8) needs to know that VLANs are an `ethernet-like' device so it can add and delete ARP entries. My code is based on kern/19436 and I've attached my changed to that PR. For Wes's benefit, this doesn't change the kernel's ARP handling at all. >> - support VLANs in tcpdump(8) [this may be in the generic tree by now] > >It's been for quite some time. I used it when doing my first version of >the patches on a 3.2-stable system. I added patches to allow matching on the VLAN id and made the BPF compiler generate code to look inside VLAN packets and allow matching on the packet contents. I sent these both to FreeBSD (bin/21880) and the tcpdump maintainers. This lets me do things like: aalp02# tcpdump -i fxp0 -c 5 vlan and host aald09-tu0 tcpdump: listening on fxp0 16:16:12.474266 802.1Q vlan#158 P0 aald11-tu0.1160 > aald09-tu0.pdap-np: P 429682654:429682683(29) ack 359725302 win 33580 (DF) 16:16:12.474708 802.1Q vlan#158 P0 aald09-tu0.pdap-np > aald11-tu0.1160: P 1:17(16) ack 29 win 33580 (DF) 16:16:12.525298 802.1Q vlan#156 P0 aald09-tu0.pdap-np > aald11-tu0.1160: P 1:17(16) ack 29 win 33580 (DF) 16:16:12.525755 802.1Q vlan#156 P0 aald11-tu0.1160 > aald09-tu0.pdap-np: P 29:249(220) ack 17 win 33580 (DF) 16:16:12.576825 802.1Q vlan#158 P0 aald11-tu0.1160 > aald09-tu0.pdap-np: P 29:249(220) ack 17 win 33580 (DF) aalp02# Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 4:18: 6 2001 Delivered-To: freebsd-net@freebsd.org Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by hub.freebsd.org (Postfix) with ESMTP id 9A8ED37B491 for ; Mon, 26 Feb 2001 04:18:01 -0800 (PST) (envelope-from rik@cronyx.ru) Received: from cronyx.ru by hanoi.cronyx.ru with ESMTP id PAA01978; (8.9.3/vak/2.1) Mon, 26 Feb 2001 15:16:24 +0300 (MSK) Message-ID: <3A9A4B03.4010700@cronyx.ru> Date: Mon, 26 Feb 2001 15:24:35 +0300 From: Kurakin Roman User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20001108 Netscape6/6.0 X-Accept-Language: ru, en MIME-Version: 1.0 To: Jean-Christophe Varaillon Cc: freebsd-net@FreeBSD.ORG Subject: Re: - RISCom card: lcp illegal conf-req in state initial - References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, It's seems you have some hardware problems, but also sppp have some problems. So if you are using it I sugest to take update for it. You could look at this patch: http://www.freebsd.org/cgi/query-pr.cgi?pr=21771 Or better take last version of driver for Cronyx adapters, where is the most recent version of sppp: http://www.cronyx.ru/pub/cronyx/adapters/cfbsd341.tgz Also I want to remind to freebsd team, that we sent two patches for sppp first one about year and a half and last about half a year and they still not processed. Kurakin Roman Jean-Christophe Varaillon wrote: > Hi all, > > I am actualy trying to establish the communication between a cisco router > and my Free BSD machine. > > +-------+ +---------------+ > | cisco |serial interface | FreeBSD 4.1 | > | 3600 +-----------------------+ | > | | RISCom | | > +-------+ card +---------------+ > x.x.x.145 x.x.x.146 > > I beleive that the router is correclty configured but NOT the FreeBSD > machine. > > This is what dmesg | grep sr1 shows: > -------- > sr1: Adapter 0, port 1. > sr1 XXX: driver didn't set ifq_maxlen > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > ... > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01. > sr1: Down event, taking interface down. > ... > sr1: Down event, taking interface down. > sr1: Down event, taking interface down. > sr1: lcp illegal conf-req in state initial > ... > sr1: lcp illegal conf-req in state initial > sr1: lcp illegal conf-req in state initial > -------- > > This is the ifconfig: > ------- > sr1: flags=8451 mtu 1500 > inet6 fe80::2d0:b7ff:fe09:3333%sr1 --> :: prefixlen 64 > scopeid 0x2 > inet x.x.x.146 --> x.x.x.145 netmask 0xfffffffc > ------ > > > > any suggestion... > > Thanks, > > JC. > > > 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 26 4:49:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from secure.webhotel.net (secure.webhotel.net [195.41.202.80]) by hub.freebsd.org (Postfix) with SMTP id 85DB837B491 for ; Mon, 26 Feb 2001 04:49:29 -0800 (PST) (envelope-from hroi@chewbacca.netgroup.dk) Received: (qmail 91258563 invoked from network); 26 Feb 2001 12:52:11 -0000 Received: from mail-gateway.webhotel.net (195.41.202.215) by mail.webhotel.net with SMTP; 26 Feb 2001 12:52:11 -0000 X-Authenticated-Timestamp: 13:52:11(CET) on February 26, 2001 Received: (from hroi@localhost) by chewbacca.netgroup.dk (8.11.2/8.9.3) id f1QCnKo90419 for freebsd-net@freebsd.org; Mon, 26 Feb 2001 13:49:20 +0100 (CET) (envelope-from hroi) Date: Mon, 26 Feb 2001 13:49:20 +0100 From: Hroi Sigurdsson To: freebsd-net@freebsd.org Subject: mpd and mschap v2? Message-ID: <20010226134920.A89577@chewbacca.netgroup.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does mpd/netgraph support MSCHAP v2? I'm trying to connect via PPTP to a firewall which requires MSCHAPv2 and having no luck. -- Hroi Sigurdsson hroi@netgroup.dk Netgroup A/S http://www.netgroup.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 5: 4:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from toolbox.yok.utu.fi (toolbox.yok.utu.fi [130.232.132.159]) by hub.freebsd.org (Postfix) with ESMTP id BFD6E37B491 for ; Mon, 26 Feb 2001 05:04:38 -0800 (PST) (envelope-from juha@toolbox.yok.utu.fi) Received: from localhost (juha@localhost) by toolbox.yok.utu.fi (8.11.1/8.11.1) with ESMTP id f1QD4el06733 for ; Mon, 26 Feb 2001 15:04:41 +0200 (EET) (envelope-from juha@toolbox.yok.utu.fi) Date: Mon, 26 Feb 2001 15:04:40 +0200 (EET) From: Juha Lindstrom To: freebsd-net@freebsd.org Subject: gateway/proxy arp Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! I have a somewhat tricky situation with a gateway/proxy arp setup. Let me quickly tell you some backgrounds: 1) I'm connected to internet via university LAN 2) university only allows one MAC address to communicate with the outside world at a time, thus I can not use a HUB 3) I have 2 real IP addresses which I want to assing to 2 different computers, one for fbsd and one for windows Ok, I'm new to fbsd but I have used slackware linux earlier and managed to get this system to work in the following way: 1) setup eth0 to communicate with outside world using DHCP to get the necessary info 2) ifconfig eth1 (=interface to connect with windows) 192.168.1.1 up 3) arp -i eth0 -s pub 4) route add metric 1 dev eth1 Now, I managed to get those commands to work with fbsd with one exception - the ARP comman. Seems that fbsd doesn't allow me to specify the interface like it does in the linux implemation. And this results in windows discovering another computer using it's MAC address and then shutting down network. So, the question is - how would I accomplish this in fbsd? Please, give as detailed information as you possibly can since I'm new to fbsd. Thank you in advance Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 5:48:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id B182137B503 for ; Mon, 26 Feb 2001 05:48:54 -0800 (PST) (envelope-from julian@elischer.org) Received: from elischer.org (i080-201.nv.iinet.net.au [203.59.80.201]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id VAA13786; Mon, 26 Feb 2001 21:48:44 +0800 Message-ID: <3A9A5E92.A9837700@elischer.org> Date: Mon, 26 Feb 2001 05:48:02 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Juha Lindstrom Cc: freebsd-net@freebsd.org Subject: Re: gateway/proxy arp References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Juha Lindstrom wrote: > > Hi! > > I have a somewhat tricky situation with a gateway/proxy arp setup. Let me > quickly tell you some backgrounds: > > 1) I'm connected to internet via university LAN > 2) university only allows one MAC address to communicate with the outside > world at a time, thus I can not use a HUB > 3) I have 2 real IP addresses which I want to assing to 2 different > computers, one for fbsd and one for windows > > Ok, I'm new to fbsd but I have used slackware linux earlier and managed to > get this system to work in the following way: > > 1) setup eth0 to communicate with outside world using DHCP to get the > necessary info > 2) ifconfig eth1 (=interface to connect with windows) 192.168.1.1 up > 3) arp -i eth0 -s pub > 4) route add metric 1 dev eth1 > > Now, I managed to get those commands to work with fbsd with one exception > - the ARP comman. Seems that fbsd doesn't allow me to specify the > interface like it does in the linux implemation. And this results in > windows discovering another computer using it's MAC address and then > shutting down network. > > So, the question is - how would I accomplish this in fbsd? Please, give as > detailed information as you possibly can since I'm new to fbsd. use natd # man 8 natd NATD(8) FreeBSD System Manager's Manual NATD(8) NAME natd - Network Address Translation Daemon SYNOPSIS natd [-unregistered_only | -u] [-log | -l] [-proxy_only] [-reverse] [-deny_incoming | -d] [-use_sockets | -s] [-same_ports | -m] [-verbose | -v] [-dynamic] [-in_port | -i port] [-out_port | -o port] [-port | -p port] [-alias_address | -a address] [-target_address | -t address] [-interface | -n interface] [-proxy_rule proxyspec] [-redirect_port linkspec] [-redirect_proto linkspec] [-redirect_address linkspec] [-config | -f configfile] [-log_denied] [-log_facility facility_name] [-punch_fw firewall_range] DESCRIPTION This program provides a Network Address Translation facility for use with divert(4) sockets under FreeBSD. It is intended for use with NICs - if you want to do NAT on a PPP link, use the -nat switch to ppp(8). The natd normally runs in the background as a daemon. It is passed raw IP packets as they travel into and out of the machine, and will possibly change these before re-injecting them back into the IP packet stream. [...] everything will appear to come from the one (freeBSD) machine. > > Thank you in advance > > Juha > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 7:14:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailman.thenap.com (mailman.thenap.com [209.190.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 09AF637B401 for ; Mon, 26 Feb 2001 07:14:41 -0800 (PST) (envelope-from drew.weaver@thenap.com) Received: by mailman.thenap.com with Internet Mail Service (5.5.2650.21) id ; Mon, 26 Feb 2001 10:27:17 -0500 Message-ID: From: "Drew J. Weaver" To: "'freebsd-net@freebsd.org'" Subject: Quick question about IP aliasing Date: Mon, 26 Feb 2001 10:27:17 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0A008.9A3C97FE" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0A008.9A3C97FE Content-Type: text/plain; charset="iso-8859-1" Say I have a main server Ip address of (This is completely made up) 209.190.53.51, and I have 32 IP addresses blocked to it on 209.51.193.32-64 (or whatever, this is an example) would this alias line still be valid for that? I've never done a server where the MAIN IP and the aliased IPs were on different IP classes. ifconfig_fxp0_alias0="inet 209.51.193.32 netmask 255.255.255.0" (is an example of what im using for the aliases.) Is there something special I need to do since these aren't on the same net? Thanks, -Drew ------_=_NextPart_001_01C0A008.9A3C97FE Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Quick question about IP aliasing

        Say I have a main server Ip address of (This is = completely made up) 209.190.53.51, and I have 32 IP addresses blocked = to it on 209.51.193.32-64 (or whatever, this is an example) would this = alias line still be valid for that? I've never done a server where the = MAIN IP and the aliased IPs were on different IP classes.

ifconfig_fxp0_alias0=3D"inet 209.51.193.32 netmask = 255.255.255.0" (is an example of what im using for the = aliases.)

Is there something special I = need to do since these aren't on the same net?

Thanks,

-Drew




------_=_NextPart_001_01C0A008.9A3C97FE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 13:19:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from samar.sasi.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 6D31337B503 for ; Mon, 26 Feb 2001 13:19:13 -0800 (PST) (envelope-from sseth@sasken.com) Received: from samar (samar.sasi.com [164.164.56.2]) by samar.sasi.com (8.9.3/8.9.3) with SMTP id CAA27027 for ; Tue, 27 Feb 2001 02:49:08 +0530 (IST) Received: from suns3.sasi.com ([10.0.36.3]) by samar.sasi.com; Tue, 27 Feb 2001 02:49:06 +0000 (IST) Received: from localhost (sseth@localhost) by suns3.sasi.com (8.9.3/8.9.3) with ESMTP id CAA29417 for ; Tue, 27 Feb 2001 02:49:05 +0530 (IST) Date: Tue, 27 Feb 2001 02:49:05 +0530 (IST) From: Satyajeet Seth To: Subject: Problem in configuring netgraph Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I tried to use ng_ether and ng_bpf as follows: fxp0(lower) --- (bhook)[bpf](nomatch)(hook1)----(upper)fxp0 [ ]( match )(hook2)----not connected $ ngctl mkpeer fxp0: bpf divert bhook $ ngctl name fxp0:divert bpf0 $ ngctl + msg bpf0: setprogram { thisHook="bhook" ifMatch="hook2" ifNotMatch="hook1" bpf_prog_len=1 bpf_prog=[ { code=6 } ] } Now 'nghook -a bpf0: hook1' shows output while 'nghook -a bpf0: hook2' doesn't. $ ngctl connect fxp0: bpf0: upper hook1 1. After this I am unable to ping any of the lan machines. Could you suggest what I could be doing wrong? 2. I am writing a BPF program(for filtering packets destined to particular MAC addresses) by converting instructions like: BPF_STMT(BPF_LD+BPF_H+BPF_ABS,12), BPF_STMT(BPF_RET+BPF_K,0) into: [ {code=28 jt=0 jf=0 k=0x0c} {code=6 jt=0 jf=0 k=0}] After seeing the definitions of BPF_STMT,BPF_LD etc. in /sys/net/bpf.h. Is this the correct way? 3. I noticed a problem that the filter could not be set as : ngctl msg bpf0: setprogram {...} It gave the message: ngctl: send msg: Invalid argument I am using FreeBSD 4.1. Thanks Satya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 13:46: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id 20A2537B491 for ; Mon, 26 Feb 2001 13:46:03 -0800 (PST) (envelope-from mark@whistle.com) Received: from [10.1.10.113] (PBG3.whistle.com [207.76.207.169]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA11201; Mon, 26 Feb 2001 13:42:46 -0800 (PST) Mime-Version: 1.0 X-Sender: mark@207.76.206.1 Message-Id: In-Reply-To: <20010225085626.V5714@prism.flugsvamp.com> References: <20010224142742.T5714@prism.flugsvamp.com> <20010225085626.V5714@prism.flugsvamp.com> Date: Mon, 26 Feb 2001 13:39:37 -0800 To: Jonathan Lemon , Paul Herman From: Mark Peek Subject: Re: I have delayed ACK problems Cc: Jonathan Lemon , Garrett Wollman , net@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 8:56 AM -0600 2/25/01, Jonathan Lemon wrote: >On Sun, Feb 25, 2001 at 11:10:54AM +0100, Paul Herman wrote: >> On Sat, 24 Feb 2001, Jonathan Lemon wrote: >> >> > On Sat, Feb 24, 2001 at 11:19:02AM -0800, Mark Peek wrote: >> > > Was there ever a final resolution to this problem? >> > >> > The patches are still sitting in my tree, as I've been unable >> > to come up with a test case that actually makes a difference. >> > >> > The "tar cf host:..." example is bogus, as the problem here is >> >> Jonathan is right, the patch doesn't solve the general "tar cf host:" >> problem, but it was similar enough to what we were seeing in >> production -- changing the MTU on lo0 to 1500 will make the >> "tar cf host:" problem/solution more apparent, when host == localhost. > >Hmm, yes, by doing that, I'm able to reproduce the condition locally, >thanks for pointing out a good test case. Thanks for the update. Jonathan, does it make sense to commit the current patch since it solves Paul's problem (and presumably doesn't break existing networking) or should it wait until the "tar cf host:" problem can be solved? I'm basically neutral on which way to go but it sounded like a big network performance issue for Paul when he initially reported the bug. (It might be affecting more people but they probably haven't done the analysis to better understand the problem.) Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 15: 6:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from curly.chiaro.com (us.chiaro.com [63.88.196.33]) by hub.freebsd.org (Postfix) with ESMTP id 59E3237B491 for ; Mon, 26 Feb 2001 15:06:17 -0800 (PST) (envelope-from plawthers@chiaro.com) Received: from chiaro.com (192-168-25-122.chiaro.com [192.168.25.122]) by curly.chiaro.com (8.9.3+Sun/8.9.1) with ESMTP id RAA20515; Mon, 26 Feb 2001 17:06:16 -0600 (CST) Message-ID: <3A9AE15D.103DFBB7@chiaro.com> Date: Mon, 26 Feb 2001 17:06:05 -0600 From: Peter Lawthers Organization: Chiaro Networks X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: sendfile with headers (struct sf_hdtr) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When using sendfile(2) with the optional headers, it appears that sendfile inadvertently returns the number of bytes written via writev (writev updates p_retval[0]). I checked through the archives, and it doesn't appear that I'm using sendfile(2) incorrectly, although that's always a possibility. What happens is that sendfile(2) always returns the number of header/trailer bytes written, rather than the errno. What's the accepted procedure for logging this? You can hit this is you specify the optional headers to sendfile, thusly: struct sf_hdtr hdr; .... bzero(&hdr, sizeof(hdr); hdr.headers = &iov; /* iov set up elsewhere */ hdr.hdr_cnt = 1; error = sendfile(fd, sockfd, 0, 0, &hdr, &sendbytes, 0); Here's a diff of what I changed to make it happy. I believe this to be "safe", but I'm certain someone out there knows more than me and can tell me why I'm wrong. :-) diff -aur sys/kern/uipc_syscalls.c /tmp/bsd/src/sys/kern/uipc_syscalls.c --- sys/kern/uipc_syscalls.c Mon Feb 26 16:15:26 2001 +++ /tmp/bsd/src/sys/kern/uipc_syscalls.c Tue Aug 15 14:29:27 2000 @@ -1552,7 +1552,6 @@ if (error) goto done; sbytes += p->p_retval[0]; - p->p_retval[0] = 0; } } @@ -1773,7 +1772,6 @@ if (error) goto done; sbytes += p->p_retval[0]; - p->p_retval[0] = 0; } done: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 15: 9:32 2001 Delivered-To: freebsd-net@freebsd.org Received: from hera.drwilco.net (10dyn61.dh.casema.net [212.64.31.61]) by hub.freebsd.org (Postfix) with ESMTP id 10EDD37B4EC for ; Mon, 26 Feb 2001 15:09:16 -0800 (PST) (envelope-from drwilco@drwilco.nl) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.2/8.11.1) with ESMTP id f1QNWpo16345; Tue, 27 Feb 2001 00:32:53 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010227000742.00d24820@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 27 Feb 2001 00:09:15 +0100 To: "Drew J. Weaver" From: "Rogier R. Mulhuijzen" Subject: Re: Quick question about IP aliasing Cc: freebsd-net@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_1063673668==_.ALT" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --=====================_1063673668==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed At 10:27 26-2-01 -0500, you wrote: > Say I have a main server Ip address of (This is completely made > up) 209.190.53.51, and I have 32 IP addresses blocked to it on > 209.51.193.32-64 (or whatever, this is an example) would this alias line > still be valid for that? I've never done a server where the MAIN IP and > the aliased IPs were on different IP classes. > >ifconfig_fxp0_alias0="inet 209.51.193.32 netmask 255.255.255.0" (is an >example of what im using for the aliases.) > >Is there something special I need to do since these aren't on the same net? No, you can just use the regular netmask for the first IP in a new subnet. It's only when you have more than one IP in the same subnet that you need to use 255.255.255.255 (or 0xffffffff, which I prefer) as a subnetmask. DocWilco --=====================_1063673668==_.ALT Content-Type: text/html; charset="us-ascii" At 10:27 26-2-01 -0500, you wrote:

        Say I have a main server Ip address of (This is completely made up) 209.190.53.51, and I have 32 IP addresses blocked to it on 209.51.193.32-64 (or whatever, this is an example) would this alias line still be valid for that? I've never done a server where the MAIN IP and the aliased IPs were on different IP classes.

ifconfig_fxp0_alias0="inet 209.51.193.32 netmask 255.255.255.0" (is an example of what im using for the aliases.)

Is there something special I need to do since these aren't on the same net?

No, you can just use the regular netmask for the first IP in a new subnet. It's only when you have more than one IP in the same subnet that you need to use 255.255.255.255 (or 0xffffffff, which I prefer) as a subnetmask.

        DocWilco --=====================_1063673668==_.ALT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 16: 9:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from worldclass.jolt.nu (lgh637b.hn-krukan.AC [212.217.139.112]) by hub.freebsd.org (Postfix) with ESMTP id F324837B491 for ; Mon, 26 Feb 2001 16:09:30 -0800 (PST) (envelope-from c4@worldclass.jolt.nu) Received: by worldclass.jolt.nu (Postfix, from userid 1000) id 0BD774D; Tue, 27 Feb 2001 01:06:56 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by worldclass.jolt.nu (Postfix) with ESMTP id 656C449; Tue, 27 Feb 2001 01:06:56 +0100 (CET) Date: Tue, 27 Feb 2001 01:06:55 +0100 (CET) From: Tobias Fredriksson To: "Drew J. Weaver" Cc: "'freebsd-net@freebsd.org'" Subject: Re: Quick question about IP aliasing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 26 Feb 2001, Drew J. Weaver wrote: > Say I have a main server Ip address of (This is completely made up) > 209.190.53.51, and I have 32 IP addresses blocked to it on 209.51.193.32-64 > (or whatever, this is an example) would this alias line still be valid for > that? I've never done a server where the MAIN IP and the aliased IPs were on > different IP classes. > > ifconfig_fxp0_alias0="inet 209.51.193.32 netmask 255.255.255.0" (is an > example of what im using for the aliases.) do 'netmask 255.255.255.255' instead or 'netmask 0xffffffff' since this is an alias... for some reason otherwise services may not bind to the ip correctly > Is there something special I need to do since these aren't on the same net? > > Thanks, > > -Drew > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 16:26:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from hera.drwilco.net (10dyn61.dh.casema.net [212.64.31.61]) by hub.freebsd.org (Postfix) with ESMTP id B69B337B491 for ; Mon, 26 Feb 2001 16:26:42 -0800 (PST) (envelope-from drwilco@drwilco.nl) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.2/8.11.1) with ESMTP id f1R0oHo16489; Tue, 27 Feb 2001 01:50:18 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010227012505.00c6b340@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 27 Feb 2001 01:26:41 +0100 To: Tobias Fredriksson , "Drew J. Weaver" From: "Rogier R. Mulhuijzen" Subject: Re: Quick question about IP aliasing Cc: "'freebsd-net@freebsd.org'" In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 01:06 27-2-01 +0100, Tobias Fredriksson wrote: >On Mon, 26 Feb 2001, Drew J. Weaver wrote: > > > Say I have a main server Ip address of (This is completely made up) > > 209.190.53.51, and I have 32 IP addresses blocked to it on 209.51.193.32-64 > > (or whatever, this is an example) would this alias line still be valid for > > that? I've never done a server where the MAIN IP and the aliased IPs > were on > > different IP classes. > > > > ifconfig_fxp0_alias0="inet 209.51.193.32 netmask 255.255.255.0" (is an > > example of what im using for the aliases.) > >do 'netmask 255.255.255.255' instead or 'netmask 0xffffffff' since this is >an alias... for some reason otherwise services may not bind to the ip >correctly Not if the alias is in a different subnet though. Or am I missing something? DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 17: 8:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from molly.straylight.com (molly.straylight.com [209.68.199.242]) by hub.freebsd.org (Postfix) with ESMTP id 967C737B401 for ; Mon, 26 Feb 2001 17:08:02 -0800 (PST) (envelope-from jonathan@graehl.org) Received: from dickie (case.straylight.com [209.68.199.244]) by molly.straylight.com (8.11.0/8.10.0) with SMTP id f1R17im03393 for ; Mon, 26 Feb 2001 17:07:44 -0800 From: "Jonathan Graehl" To: Subject: RE: Quick question about IP aliasing Date: Mon, 26 Feb 2001 17:09:15 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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.4522.1200 In-Reply-To: Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > do 'netmask 255.255.255.255' instead or 'netmask 0xffffffff' since this is > an alias... for some reason otherwise services may not bind to the ip > correctly Why would this be? The two are numerically equivalent. -Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 18: 8:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from online.tmx.com.au (online.tmx.com.au [192.150.129.1]) by hub.freebsd.org (Postfix) with ESMTP id 4929637B491; Mon, 26 Feb 2001 18:08:22 -0800 (PST) (envelope-from mtaylor@bytecraft.com.au) Received: from melexc01.bytecraft.com.au ([203.9.250.249]) by online.tmx.com.au (8.9.3/8.8.8) with ESMTP id NAA04576; Tue, 27 Feb 2001 13:08:13 +1100 (EST) Received: by MELEXC01 with Internet Mail Service (5.5.2448.0) id <183XYPN4>; Tue, 27 Feb 2001 10:15:27 +1100 Message-ID: <710709BB8B02D311942E006067441810544267@MELEXC01> From: Murray Taylor To: "'freebsd-net@freebsd.org'" , "'freebsd-questions@freebsd.org'" Subject: Frame Relay in Australia with Telstra Date: Tue, 27 Feb 2001 10:14:37 +1100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am establishing FreeBSD 4.2 Release (from the CD Roms) on a Compaq A550 and I need to setup a connection to a Telstra frame relay interface (which has yet to be installed) (A) Has anyone in .AU done this? (B) What interface card did you use? and which driver ( sr, ar, cx, ?? ) (C) Which distributor did you get the card from? (D) what software i/face are you using, do you recommend (sppp / netgraph / ?? ) (I have read the frame_relay item in the netgraph examples, but otherwise have no direct experience with netgraph) I have recompiled the kernel to add IPFW, NETGRAPH and drop some uneeded net devices and am quite OK do do so as needed again. (FreeBSD on my home machine since 2.2.2) Note the hostname in the dmesg is a dummy used for internal testing prior to domain registration Murray Taylor Project Engineer Bytecraft P/L +61 3 9587 2555 +61 3 9580 7690 fax mtaylor@bytecraft.com.au Current dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #0: Mon Feb 19 10:01:04 EST 2001 root@spyder.bytecraft.com.xxx:/usr/src/sys/compile/SPYDER Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 863933901 Hz CPU: Pentium III/Pentium III Xeon/Celeron (863.93-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 536805376 (524224K bytes) avail memory = 519200768 (507032K bytes) Preloaded elf kernel "kernel" at 0xc0350000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc035009c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 pcib2: at device 30.0 on pci0 pci2: on pcib2 fxp0: port 0x5400-0x543f mem 0xefe00000-0xefefffff,0xefd00000-0xefd00fff irq 11 at device 2.0 on pci2 fxp0: Ethernet address 00:50:8b:f1:de:df ahc0: port 0x5000-0x50ff mem 0xeff00000-0xeff00fff irq 11 at device 7.0 on pci2 aic7892: Wide Channel A, SCSI Id=7, 32/255 SCBs pci2: (vendor=0x1274, dev=0x5880) at 11.0 irq 11 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x6460-0x646f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x6440-0x645f irq 11 at device 31.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: (vendor=0x8086, dev=0x2413) at 31.3 irq 11 chip1: port 0x6400-0x643f,0x6000-0x60ff irq 11 at device 31.5 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/13 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed acd0: CDROM at ata1-master using PIO4 Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s2a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 19:48:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 7919837B4EC for ; Mon, 26 Feb 2001 19:48:43 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.9.3) with SMTP id f1R3kmi13734; Mon, 26 Feb 2001 22:46:48 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <001501c0a070$3a14d900$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Jonathan Graehl" , References: Subject: Re: Quick question about IP aliasing Date: Mon, 26 Feb 2001 22:49:02 -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.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > do 'netmask 255.255.255.255' instead or 'netmask 0xffffffff' since this is > > an alias... for some reason otherwise services may not bind to the ip > > correctly > > Why would this be? The two are numerically equivalent. Yes, but you're missing the point. The point is that you need to use a netmask of 255.255.255.255 for aliased IPs on FreeBSD, regardless of the alias of the primary (non-alias) IP. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 19:50:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id D697D37B67D for ; Mon, 26 Feb 2001 19:50:37 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id WAA71013; Mon, 26 Feb 2001 22:50:36 -0500 (EST) (envelope-from wollman) Date: Mon, 26 Feb 2001 22:50:36 -0500 (EST) From: Garrett Wollman Message-Id: <200102270350.WAA71013@khavrinen.lcs.mit.edu> To: Peter Lawthers Cc: freebsd-net@FreeBSD.ORG Subject: sendfile with headers (struct sf_hdtr) In-Reply-To: <3A9AE15D.103DFBB7@chiaro.com> References: <3A9AE15D.103DFBB7@chiaro.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > When using sendfile(2) with the optional headers, it appears > that sendfile inadvertently returns the number of bytes written > via writev If any data was sent, sendfile() should tell you so. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 21:58: 3 2001 Delivered-To: freebsd-net@freebsd.org Received: from femail11.sdc1.sfba.home.com (femail11.sdc1.sfba.home.com [24.0.95.107]) by hub.freebsd.org (Postfix) with ESMTP id 4FD3337B425 for ; Mon, 26 Feb 2001 21:58:00 -0800 (PST) (envelope-from justin@mac.com) Received: from lilith ([65.11.111.111]) by femail11.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010227055759.FFEA10024.femail11.sdc1.sfba.home.com@lilith> for ; Mon, 26 Feb 2001 21:57:59 -0800 Date: Mon, 26 Feb 2001 17:29:58 -0800 Content-Type: text/plain; format=flowed; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v379) From: Justin C.Walker To: X-Mailer: Apple Mail (2.379) In-Reply-To: Subject: Re: Quick question about IP aliasing Content-Transfer-Encoding: 7bit Message-Id: <20010227055759.FFEA10024.femail11.sdc1.sfba.home.com@lilith> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think that Roger meant something like: "... instead, or ..." <-- "," added. He's saying they are the same. FWIW, there used to be an "IP alias" tutorial (not the "pedantic ppp" tutorial) referenced from the freebsd web site, but it's disappeared. The former went into a bit of detail on what is going on when you install an alias. Basically, it's like this (the essence of this has already been mentioned): - if you install an alias on an interface whose network number matches an existing address, you can do one of two things: -- specify the netmask as "-1" -- specify the "correct" netmask, ignore the returned error (the alias is installed), and then add an appropriate route for the new address. The former seems like less work. - if the alias is not on an existing subnet, then use the correct netmask. For the original requestor's case, the first alias is installed with the "correct" netmask, and the subsequent ones (on the subnet defined by the first alias) get installed with the "-1" netmask. Regards, Justin On Monday, February 26, 2001, at 05:09 PM, Jonathan Graehl wrote: >> do 'netmask 255.255.255.255' instead or 'netmask 0xffffffff' since >> this is >> an alias... for some reason otherwise services may not bind to the ip >> correctly > > Why would this be? The two are numerically equivalent. > > -Jon > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | | When lutefiske is outlawed Nexsi Corp. | Only outlaws will have lutefiske 1959 Concourse Drive | San Jose, CA 95131 | *-------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 26 22:16:28 2001 Delivered-To: freebsd-net@freebsd.org Received: from hera.drwilco.net (10dyn61.dh.casema.net [212.64.31.61]) by hub.freebsd.org (Postfix) with ESMTP id 22D9437B444 for ; Mon, 26 Feb 2001 22:16:24 -0800 (PST) (envelope-from drwilco@drwilco.nl) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.2/8.11.1) with ESMTP id f1R6doo17525; Tue, 27 Feb 2001 07:39:52 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010227070424.00d25c10@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 27 Feb 2001 07:16:14 +0100 To: "Matthew Emmerton" , "Jonathan Graehl" , From: "Rogier R. Mulhuijzen" Subject: Re: Quick question about IP aliasing In-Reply-To: <001501c0a070$3a14d900$1200a8c0@gsicomp.on.ca> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 22:49 26-2-01 -0500, Matthew Emmerton wrote: > > > do 'netmask 255.255.255.255' instead or 'netmask 0xffffffff' since this >is > > > an alias... for some reason otherwise services may not bind to the ip > > > correctly > > > > Why would this be? The two are numerically equivalent. He's saying 'instead or' not 'instead of', I nearly fell for this too. >Yes, but you're missing the point. > >The point is that you need to use a netmask of 255.255.255.255 for aliased >IPs on FreeBSD, regardless of the alias of the primary (non-alias) IP. Everybody is saying use 255.255.255.255 for an alias. Noone is giving reasons why. Aliassing is the only way to bind more than one IP to an interface (well only simple way..) and aliasses are no different from the primary IP. If you couldn't use the right subnetmask for an alias outside the main IP's subnet, the FreeBSD machine wouldn't be able to fully participate in that subnet's traffic. (It couldn't receive subnet broadcasts for one) The only reason to use 255.255.255.255 is when the IPs are in the same subnet, or you'll get routing and broadcast problems. If you use 10.1.1.1:255.255.255.0 and the 2nd IP is 10.1.1.2 you need to use 255.255.255.255 for the 2nd IP If you use 10.1.1.1:255.255.255.0 and the 2nd IP is 10.2.2.2 you can use 255.255.255.0 for the 2nd IP (if that is the subnetmask for that network) If you use 10.1.1.1:255.0.0.0 and the 2nd IP is 10.2.2.2 you need to use 255.255.255.255 again (same subnet) If you use 10.1.1.1:255.255.255.0 and 10.2.2.2:255.255.255.0, and the 3rd IP is 10.2.2.4 you use 255.255.255.255 only for the 3rd IP. DocWilco P.S.: If this is not the case with FreeBSD, we've got major problems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 0:39:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by hub.freebsd.org (Postfix) with ESMTP id 31D5437B719; Tue, 27 Feb 2001 00:39:29 -0800 (PST) (envelope-from rik@cronyx.ru) Received: from cronyx.ru by hanoi.cronyx.ru with ESMTP id LAA01372; (8.9.3/vak/2.1) Tue, 27 Feb 2001 11:36:25 +0300 (MSK) Message-ID: <3A9B68F1.6050007@cronyx.ru> Date: Tue, 27 Feb 2001 11:44:33 +0300 From: Kurakin Roman User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20001108 Netscape6/6.0 X-Accept-Language: ru, en MIME-Version: 1.0 To: Murray Taylor Cc: "'freebsd-net@freebsd.org'" , "'freebsd-questions@freebsd.org'" Subject: Re: Frame Relay in Australia with Telstra References: <710709BB8B02D311942E006067441810544267@MELEXC01> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, If you want to use sppp with Frame Relay, you should update your sppp driver. Here you will find not only sppp driver but also cx, ct and cp drivers: http://www.cronyx.ru/pub/cronyx/adapters/cfbsd341.tgz Kurakin Roman Murray Taylor wrote: > I am establishing FreeBSD 4.2 Release (from the CD Roms) on a Compaq A550 > and > I need to setup a connection to a Telstra frame relay interface (which has > yet to be installed) > > (A) Has anyone in .AU done this? > > (B) What interface card did you use? and which driver ( sr, ar, cx, ?? ) > > (C) Which distributor did you get the card from? > > (D) what software i/face are you using, do you recommend (sppp / netgraph / > ?? ) > (I have read the frame_relay item in the netgraph examples, but > otherwise have no > direct experience with netgraph) > > I have recompiled the kernel to add IPFW, NETGRAPH and drop some uneeded net > devices and am > quite OK do do so as needed again. (FreeBSD on my home machine since 2.2.2) > > Note the hostname in the dmesg is a dummy used for internal testing prior to > domain registration > > Murray Taylor > Project Engineer > > Bytecraft P/L +61 3 9587 2555 > +61 3 9580 7690 fax > mtaylor@bytecraft.com.au > > > > > Current dmesg: > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.2-RELEASE #0: Mon Feb 19 10:01:04 EST 2001 > root@spyder.bytecraft.com.xxx:/usr/src/sys/compile/SPYDER > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 863933901 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (863.93-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x683 Stepping = 3 > > Features=0x383fbff CMOV,PAT,PSE36,MMX,FXSR,SSE> > real memory = 536805376 (524224K bytes) > avail memory = 519200768 (507032K bytes) > Preloaded elf kernel "kernel" at 0xc0350000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc035009c. > Pentium Pro MTRR support enabled > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at 0.0 irq 11 > pcib2: at device 30.0 on pci0 > pci2: on pcib2 > fxp0: port 0x5400-0x543f mem > 0xefe00000-0xefefffff,0xefd00000-0xefd00fff irq 11 at device 2.0 on pci2 > fxp0: Ethernet address 00:50:8b:f1:de:df > ahc0: port 0x5000-0x50ff mem > 0xeff00000-0xeff00fff irq 11 at device 7.0 on pci2 > aic7892: Wide Channel A, SCSI Id=7, 32/255 SCBs > pci2: (vendor=0x1274, dev=0x5880) at 11.0 irq 11 > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0x6460-0x646f at device 31.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > uhci0: port 0x6440-0x645f irq 11 at > device 31.2 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > pci0: (vendor=0x8086, dev=0x2413) at 31.3 irq 11 > chip1: port > 0x6400-0x643f,0x6000-0x60ff irq 11 at device 31.5 on pci0 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/13 bytes threshold > lpt0: on ppbus0 > lpt0: Interrupt-driven port > IP packet filtering initialized, divert disabled, rule-based forwarding > disabled, default to accept, logging limited to 100 packets/entry by default > ata1-slave: ata_command: timeout waiting for intr > ata1-slave: identify failed > acd0: CDROM at ata1-master using PIO4 > Waiting 5 seconds for SCSI devices to settle > Mounting root from ufs:/dev/da0s2a > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing > Enabled > da0: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C) > > > 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 Tue Feb 27 4:11:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 1AE3B37B71A for ; Tue, 27 Feb 2001 04:11:32 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 10613 invoked by uid 666); 27 Feb 2001 12:23:27 -0000 Received: from i076-133.nv.iinet.net.au (HELO elischer.org) (203.59.76.133) by mail.m.iinet.net.au with SMTP; 27 Feb 2001 12:23:27 -0000 Message-ID: <3A9B9948.E8C919E7@elischer.org> Date: Tue, 27 Feb 2001 04:10:48 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Murray Taylor Cc: "'freebsd-net@freebsd.org'" , "'freebsd-questions@freebsd.org'" Subject: Re: Frame Relay in Australia with Telstra References: <710709BB8B02D311942E006067441810544267@MELEXC01> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Murray Taylor wrote: > > I am establishing FreeBSD 4.2 Release (from the CD Roms) on a Compaq A550 > and > I need to setup a connection to a Telstra frame relay interface (which has > yet to be installed) > > (A) Has anyone in .AU done this? ummm not in AU but it is a standard right? (I've had it working in europe and USA. > > (B) What interface card did you use? and which driver ( sr, ar, cx, ?? ) proprietary, but several should work. a bug in the 'sr' driver was just fixed that may fix problems I was seeing with this last year in Australia. > > (C) Which distributor did you get the card from? > > (D) what software i/face are you using, do you recommend (sppp / netgraph / > ?? ) > (I have read the frame_relay item in the netgraph examples, but > otherwise have no > direct experience with netgraph) As I wrote netgraph, I recommend it.. I had the frame-relay module passed through the protocol verification labs at MCI and we ended up being very 'complying' :-) > > I have recompiled the kernel to add IPFW, NETGRAPH and drop some uneeded net > devices and am > quite OK do do so as needed again. (FreeBSD on my home machine since 2.2.2) well you'll need the sr or ar driver either way unless you can get some of the other cards that phk has been playing with. LMC? I BELIEVE than sangoma have a card and driver for freebsd/frame too, and I am pretty sure that Emerging technology can do it too. > > Note the hostname in the dmesg is a dummy used for internal testing prior to > domain registration > > Murray Taylor > Project Engineer > > Bytecraft P/L +61 3 9587 2555 > +61 3 9580 7690 fax bummer, eastern states.. otherwise I could help.. > mtaylor@bytecraft.com.au > > -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 5: 6:51 2001 Delivered-To: freebsd-net@freebsd.org Received: from mip.co.za (puck.mip.co.za [209.212.106.44]) by hub.freebsd.org (Postfix) with ESMTP id A9BE937B71C for ; Tue, 27 Feb 2001 05:06:39 -0800 (PST) (envelope-from patrick@mip.co.za) Received: from patrick (patrick.mip.co.za [10.3.13.181]) by puck.mip.co.za (8.9.3/8.9.3) with SMTP id IAA89255; Fri, 23 Feb 2001 08:28:47 +0200 (SAST) (envelope-from patrick@mip.co.za) From: "Patrick O'Reilly" To: "Peter Brezny" , Subject: RE: nat forwarding Date: Fri, 23 Feb 2001 08:28:47 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter, Some of the questions here (aliasing multiple interfaces individually) were answered in my other email on your ipfw question. But let's look at the nat forwarding issue. My rc.conf contains these lines: ---- natd_enable="YES" natd_interface="ed1" natd_flags="-f /etc/natd.conf" ---- Now, the trick is that the syntax required in the natd config file is different from that in rc.conf. In rc.conf the syntax is for a shell script setting variables to contain certain values, but the natd.conf file will be read by natd when it starts and must have the syntax expected by natd. This is explained in the man page for natd, but you need to read it a few times before it makes any sense (well that was the case with me anyway!) My /etc/natd.conf looks like this: ---- redirect_port tcp 10.3.13.131:8080 x.x.x.x:8080 redirect_port tcp 10.3.13.131:1494 x.x.x.x:1494 redirect_port tcp 10.3.13.131:1604 x.x.x.x:1604 ---- The x.x.x.x represents the registered ip on the external interface. These lines cause all packets arriving at port 8080 (etc) on ip address x.x.x.x to be redirected to port 8080 on 10.3.13.131 (my citrix server). This is working just fine for me. In your case, where you are running nat on multiple interfaces, I expect you will need nat forwarding configured differently for each interface, so you will probably want to have a /etc/natd1.conf with one set of redirection rules, and /etc/natd2.conf with another set, etc. In this case you will need to add the "-f /etc/natd1.conf" to the natd command in the rc script. Compare this sample to my earlier email: ---- oif1=ed1 # your first external interface oif2=ed2 # your second external interface natdport1=8668 # port to use for nat on first interface natdport2=8669 # port to use for nat on second interface natd -port ${natdport1} -interface ${oif1} -f /etc/natd1.conf natd -port ${natdport2} -interface ${oif2} -f /etc/natd2.conf ---- I hope this work out. Regards, Patrick O'Reilly --- "I do not feel obliged to believe that the same God who has endowed us with sense, reason, and intellect has intended us to forego their use." -- Galileo Galilei -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Peter Brezny Sent: 23 February 2001 03:07 To: freebsd-net@FreeBSD.ORG Subject: nat forwarding After reading through the natd man page, I think I understand what I need to do to redirect requests to one specified ip to another, however, I don't understand where I put this config info. i currently start natd with rc.conf with the following lines: natd_enable="YES" #natd_config="/etc/rc.natd" natd_interface="fpx1" natd_flags="-dynamic" as you can see, i've attempted creating a file with natd config options in it, but things don't seem to jive when i use it and comment out the last two lines in the example above (specifying them inside rc.natd) Also, i'd like to have multiple external interfaces with natd aliasing each one respectively. is this possible? how would i configure that? TIA pb 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 Tue Feb 27 5: 7: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from mip.co.za (puck.mip.co.za [209.212.106.44]) by hub.freebsd.org (Postfix) with ESMTP id 2D93737B71E for ; Tue, 27 Feb 2001 05:06:50 -0800 (PST) (envelope-from patrick@mip.co.za) Received: from patrick (patrick.mip.co.za [10.3.13.181]) by puck.mip.co.za (8.9.3/8.9.3) with SMTP id IAA88968; Fri, 23 Feb 2001 08:11:24 +0200 (SAST) (envelope-from patrick@mip.co.za) From: "Patrick O'Reilly" To: "Peter Brezny" , Subject: RE: ipfw simple question Date: Fri, 23 Feb 2001 08:11:24 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter, I speak under correction - I am a user, not an author, of natd and ipfw. I'm sure that someone will correct me if I'm wrong.... ipfw does not allow you to specify multiple if names for the incoming or outgoing packets, although you can specify both the in- and out- if names in one rule. ipfw does not allow you to specify multiple ip addresses for the from or to ip. The only provision made is to use an ip with a subnet mask, but you are obviously aware of this is your first example uses that syntax (0.0.0.0/8). as for natd: here is the theory I have seen, but I have never tested it myself: The natd_interface entry in rc.conf basically provides a default value for the -interface argument for natd. There is an entry for 'divert' in /etc/services which specifies the default port number to be used for the -port argument for natd. The default value for this is 8668. In your case you should be able to start the natd daemon by simply using the command # natd (this is obviously in your rc scripts already). My understanding is that you should be able to achieve what you want by doing something like this in your rc scripts: ---- oif1=ed1 # your first external interface oif2=ed2 # your second external interface natdport1=8668 # port to use for nat on first interface natdport2=8669 # port to use for nat on second interface natd -port ${natdport1} -interface ${oif1} natd -port ${natdport2} -interface ${oif2} ---- Now you should have two natd daemons running. You need to divert packets correctly using ipfw, so you will need to add two rules something like: ---- oif1=ed1 # your first external interface oif2=ed2 # your second external interface natdport1=8668 # port to use for nat on first interface natdport2=8669 # port to use for nat on second interface $fwcmd add 1 divert ${natdport1} all from any to any via ${oif1} $fwcmd add 1 divert ${natdport2} all from any to any via ${oif2} ---- Please experiment or check this with another real expert before you put this into your production environment! One thing worries me about this - I suspect that if your box routes packets in and out between these two external interfaces it will nat the packets just the same is if the packets were from/to internal interfaces. However, there is an argument for natd called -unregistered_only which will only perform nat on packets where the source address falls within the correct ranges of unregistered addresses specified in RFC1918. If you have been a good boy and used unregistered addresses on your private network then it should be safe (and correct I think) to add the -unregistered_only argument to both of the natd commands above. Please let me know how it goes.... Regards, Patrick O'Reilly --- "I do not feel obliged to believe that the same God who has endowed us with sense, reason, and intellect has intended us to forego their use." -- Galileo Galilei -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Peter Brezny Sent: 23 February 2001 01:07 To: freebsd-net@FreeBSD.ORG Subject: ipfw simple quesiton Hello, I've just added a second external interface to a machine. I'd like to not have to duplicate all the rules that involve outside interfaces. I've got rules like $fwcmd add deny all from 0.0.0.0/8 to any in via $oif is it possible to specify multiple interfaces for one rule by letting oif= ed0,ed1 ? Similarly, would that work for the ip's of the outside if's? $fwcmd add allow ip from $oip to any keep-state out via $oif oip= 10.10.1.1,10.10.1.2 ? And finally, my rc.conf defines the interface for natd like this: natd_interface="xl0" is it possible to have natd run on both external interfaces without causing problems? how would i configure that? TIA pb 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 Tue Feb 27 5:10:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 5734937B71C for ; Tue, 27 Feb 2001 05:10:38 -0800 (PST) (envelope-from julian@elischer.org) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id VAA15756; Tue, 27 Feb 2001 21:10:35 +0800 Received: from elischer.org (i076-133.nv.iinet.net.au [203.59.76.133]) by muzak.iinet.net.au (8.8.5/8.8.5) with ESMTP id VAA25740; Tue, 27 Feb 2001 21:07:36 +0800 Message-ID: <3A9BA720.3AFB0A9@elischer.org> Date: Tue, 27 Feb 2001 05:09:52 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Satyajeet Seth Cc: net@freebsd.org Subject: Re: Problem in configuring netgraph References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satyajeet Seth wrote: > > Hi > > I tried to use ng_ether and ng_bpf as follows: > > fxp0(lower) --- (bhook)[bpf](nomatch)(hook1)----(upper)fxp0 > [ ]( match )(hook2)----not connected > > $ ngctl mkpeer fxp0: bpf divert bhook > > $ ngctl name fxp0:divert bpf0 > > $ ngctl > + msg bpf0: setprogram { thisHook="bhook" ifMatch="hook2" > ifNotMatch="hook1" bpf_prog_len=1 bpf_prog=[ { code=6 } ] } > > Now 'nghook -a bpf0: hook1' shows output while 'nghook -a bpf0: hook2' > doesn't. > > $ ngctl connect fxp0: bpf0: upper hook1 > > 1. After this I am unable to ping any of the lan machines. > Could you suggest what I could be doing wrong? > > 2. I am writing a BPF program(for filtering packets destined to particular > MAC addresses) by converting instructions like: > BPF_STMT(BPF_LD+BPF_H+BPF_ABS,12), BPF_STMT(BPF_RET+BPF_K,0) > into: > [ {code=28 jt=0 jf=0 k=0x0c} {code=6 jt=0 jf=0 k=0}] > After seeing the definitions of BPF_STMT,BPF_LD etc. in /sys/net/bpf.h. Is > this the correct way? > > 3. I noticed a problem that the filter could not be set as : > ngctl msg bpf0: setprogram {...} > It gave the message: > ngctl: send msg: Invalid argument that's becaue you must escape the arguments so that the shell does not try to interpret things. > > I am using FreeBSD 4.1. > > Thanks > Satya > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message the man page for -current ng_bpf (you can get it from http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man4/ng_bpf.4 shows how to program a bpf node with a good example (it was not in the 4.x man page) -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 6:20:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from online.tmx.com.au (online.tmx.com.au [192.150.129.1]) by hub.freebsd.org (Postfix) with ESMTP id 71D2437B71F; Tue, 27 Feb 2001 06:20:08 -0800 (PST) (envelope-from mtaylor@bytecraft.com.au) Received: from melexc01.bytecraft.com.au ([203.9.250.249]) by online.tmx.com.au (8.9.3/8.8.8) with ESMTP id BAA18334; Wed, 28 Feb 2001 01:19:51 +1100 (EST) Received: by MELEXC01 with Internet Mail Service (5.5.2448.0) id <183XYPVT>; Wed, 28 Feb 2001 01:03:21 +1100 Message-ID: <710709BB8B02D311942E00606744181054426D@MELEXC01> From: Murray Taylor To: "'Julian Elischer'" , Murray Taylor Cc: "'freebsd-net@freebsd.org'" , "'freebsd-questions@freebsd.org'" Subject: RE: Frame Relay in Australia with Telstra Date: Wed, 28 Feb 2001 01:03:00 +1100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for the reply Julian ... and I have a few more questions now.. Telstra are asking ME to tell THEM what protocol and interface we will be using, chosen from the following: Protocols 1) ITU-T (CCITT) Q933 Annex A 2) ANSI T1.617 Annex D ---- Telstra default 3) LMI (FRF Doc#001-208966) Connection method a) X.21bis/V35 b) X.21 c) G.704 Based on the sr(4) page I would tell them X.21 as the connection method, but what do I tell them about the protocol?? BTW, I am using the code from the 4.2 CDROM, do I need to catch up anything w.r.t. the bug comment? I'm chasing up the WANic 405 card using the sr driver. (reading on) very complying is good, I too like elements that match to standards... If you wish to chat, call us at the office as in the sig mjt > -----Original Message----- > From: Julian Elischer [SMTP:julian@elischer.org] > Sent: Tuesday, 27 February 2001 23:11 > To: Murray Taylor > Cc: 'freebsd-net@freebsd.org'; 'freebsd-questions@freebsd.org' > Subject: Re: Frame Relay in Australia with Telstra > > Murray Taylor wrote: > > > > I am establishing FreeBSD 4.2 Release (from the CD Roms) on a Compaq > A550 > > and > > I need to setup a connection to a Telstra frame relay interface (which > has > > yet to be installed) > > > > (A) Has anyone in .AU done this? > > ummm not in AU > but it is a standard right? (I've had it working in europe and USA. > > > > > (B) What interface card did you use? and which driver ( sr, ar, cx, ?? ) > > proprietary, but several should work. > > a bug in the 'sr' driver was just fixed that may fix problems I was seeing > with > this > last year in Australia. > > > > > (C) Which distributor did you get the card from? > > > > > (D) what software i/face are you using, do you recommend (sppp / > netgraph / > > ?? ) > > (I have read the frame_relay item in the netgraph examples, but > > otherwise have no > > direct experience with netgraph) > > > As I wrote netgraph, I recommend it.. > I had the frame-relay module passed through the protocol verification labs > at > MCI and we ended up being very 'complying' :-) > > > > > > I have recompiled the kernel to add IPFW, NETGRAPH and drop some uneeded > net > > devices and am > > quite OK do do so as needed again. (FreeBSD on my home machine since > 2.2.2) > > well you'll need the sr or ar driver either way > unless you can get some of the other cards that phk > has been playing with. LMC? > > I BELIEVE than sangoma have a card and driver for freebsd/frame too, and I > am pretty sure that Emerging technology can do it too. > > > > > Note the hostname in the dmesg is a dummy used for internal testing > prior to > > domain registration > > > > Murray Taylor > > Project Engineer > > > > Bytecraft P/L +61 3 9587 2555 > > +61 3 9580 7690 fax > > bummer, eastern states.. otherwise I could help.. > > > mtaylor@bytecraft.com.au > > > > > > -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000-2001 > ---> X_.---._/ > v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 7: 5:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 6B98837B718 for ; Tue, 27 Feb 2001 07:05:27 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 23632 invoked by uid 666); 27 Feb 2001 15:17:23 -0000 Received: from i079-084.nv.iinet.net.au (HELO elischer.org) (203.59.79.84) by mail.m.iinet.net.au with SMTP; 27 Feb 2001 15:17:23 -0000 Message-ID: <3A9BC20D.C32C0FE7@elischer.org> Date: Tue, 27 Feb 2001 07:04:45 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Murray Taylor Cc: "'freebsd-net@freebsd.org'" , "'freebsd-questions@freebsd.org'" Subject: Re: Frame Relay in Australia with Telstra References: <710709BB8B02D311942E00606744181054426D@MELEXC01> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Murray Taylor wrote: > > Thanks for the reply Julian ... and I have a few more questions now.. > > Telstra are asking ME to tell THEM what protocol and interface we will be > using, > chosen from the following: > > Protocols > 1) ITU-T (CCITT) Q933 Annex A > 2) ANSI T1.617 Annex D ---- Telstra default > 3) LMI (FRF Doc#001-208966) FreeBSD netgraph supports all three and will autodetect which is in use if asked to. telstra SHOULD support ITU by default because it's ISO/ITU/CCITT and we are not in AMerica (ANSI == American National Standards Institute or something, but I guess that's the market forces at work.) LMI-FRF works but is ancient and should not be selected.. > > Connection method > a) X.21bis/V35 > b) X.21 > c) G.704 this is dependent on the card. > > Based on the sr(4) page I would tell them X.21 as the connection method, but > what do I > tell them about the protocol?? > > BTW, I am using the code from the 4.2 CDROM, do I need to catch up anything > w.r.t. > the bug comment? I think that john hay (jhay@freebsd.org) may know better but probably copying the newer sr driver from -current might be a good idea, or at least seeing if the patch he did yesterday to it (it's moved to /sys/dev/sr) can be applied to the old drivers in /sys/i386/isa that 4.2 has. > > I'm chasing up the WANic 405 card using the sr driver. > > (reading on) very complying is good, I too like elements that match to > standards... > > If you wish to chat, call us at the office as in the sig > > mjt > > > -----Original Message----- > > From: Julian Elischer [SMTP:julian@elischer.org] > > Sent: Tuesday, 27 February 2001 23:11 > > To: Murray Taylor > > Cc: 'freebsd-net@freebsd.org'; 'freebsd-questions@freebsd.org' > > Subject: Re: Frame Relay in Australia with Telstra > > > > Murray Taylor wrote: > > > > > > I am establishing FreeBSD 4.2 Release (from the CD Roms) on a Compaq > > A550 > > > and > > > I need to setup a connection to a Telstra frame relay interface (which > > has > > > yet to be installed) > > > > > > (A) Has anyone in .AU done this? > > > > ummm not in AU > > but it is a standard right? (I've had it working in europe and USA. > > > > > > > > (B) What interface card did you use? and which driver ( sr, ar, cx, ?? ) > > > > proprietary, but several should work. > > > > a bug in the 'sr' driver was just fixed that may fix problems I was seeing > > with > > this > > last year in Australia. > > > > > > > > (C) Which distributor did you get the card from? > > > > > > > > (D) what software i/face are you using, do you recommend (sppp / > > netgraph / > > > ?? ) > > > (I have read the frame_relay item in the netgraph examples, but > > > otherwise have no > > > direct experience with netgraph) > > > > > > As I wrote netgraph, I recommend it.. > > I had the frame-relay module passed through the protocol verification labs > > at > > MCI and we ended up being very 'complying' :-) > > > > > > > > > > I have recompiled the kernel to add IPFW, NETGRAPH and drop some uneeded > > net > > > devices and am > > > quite OK do do so as needed again. (FreeBSD on my home machine since > > 2.2.2) > > > > well you'll need the sr or ar driver either way > > unless you can get some of the other cards that phk > > has been playing with. LMC? > > > > I BELIEVE than sangoma have a card and driver for freebsd/frame too, and I > > am pretty sure that Emerging technology can do it too. > > > > > > > > Note the hostname in the dmesg is a dummy used for internal testing > > prior to > > > domain registration > > > > > > Murray Taylor > > > Project Engineer > > > > > > Bytecraft P/L +61 3 9587 2555 > > > +61 3 9580 7690 fax > > > > bummer, eastern states.. otherwise I could help.. > > > > > mtaylor@bytecraft.com.au > > > > > > > > > > -- > > __--_|\ Julian Elischer > > / \ julian@elischer.org > > ( OZ ) World tour 2000-2001 > > ---> X_.---._/ > > v -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 10: 1:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from samar.sasi.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 9FD8E37B71A for ; Tue, 27 Feb 2001 10:01:32 -0800 (PST) (envelope-from sseth@sasken.com) Received: from samar (samar.sasi.com [164.164.56.2]) by samar.sasi.com (8.9.3/8.9.3) with SMTP id XAA24001 for ; Tue, 27 Feb 2001 23:31:25 +0530 (IST) Received: from suns3.sasi.com ([10.0.36.3]) by samar.sasi.com; Tue, 27 Feb 2001 23:31:24 +0000 (IST) Received: from localhost (sseth@localhost) by suns3.sasi.com (8.9.3/8.9.3) with ESMTP id XAA14132 for ; Tue, 27 Feb 2001 23:31:23 +0530 (IST) Date: Tue, 27 Feb 2001 23:31:23 +0530 (IST) From: Satyajeet Seth To: Subject: Re: Problem in configuring netgraph In-Reply-To: <3A9BA720.3AFB0A9@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I tried the example at: http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man4/ng_bpf.4 When I type: tcpdump -ddd ether dest xx:xx:xx:xx:xx:xx in a telnet session the command gave the raw BPF instructions, as expected. However, at the system console the same command gave the message: fxp0: promiscuous mode enabled tcpdump: syntax error xp0: promiscuous mode disabled Could you suggest what could be wrong? I also tried the following: 1. reboot 2. ping -f & 3. nghook -a fxp0: lower Now I get identical packets. 4. ngctl mkpeer fxp0: bpf divert bhook 5. ngctl name fxp0:divert bpf0 6. ngctl msg bpf0: setprogram { thisHook="bhook" ifMatch="hook2" ifNotMatch="hook1" bpf_prog_len=1 bpf_prog=[ { code=6 } ] } Now all the packets are sent to hook1. 7. nghook -a bpf0: hook1 gives packets differing from point 3. 8. ping to any machine on the lan does not work. By default the upper and lower hooks of fxp0 are effectively connected. Our setup also does the same. Could you suggest why the ping does not work? Thanks Satya > > I tried to use ng_ether and ng_bpf as follows: > > > > fxp0(lower) --- (bhook)[bpf](nomatch)(hook1)----(upper)fxp0 > > [ ]( match )(hook2)----not connected > > > > $ ngctl mkpeer fxp0: bpf divert bhook > > > > $ ngctl name fxp0:divert bpf0 > > > > $ ngctl > > + msg bpf0: setprogram { thisHook="bhook" ifMatch="hook2" > > ifNotMatch="hook1" bpf_prog_len=1 bpf_prog=[ { code=6 } ] } > > > > Now 'nghook -a bpf0: hook1' shows output while 'nghook -a bpf0: hook2' > > doesn't. > > > > $ ngctl connect fxp0: bpf0: upper hook1 > > > > After this I am unable to ping any of the lan machines. > > Could you suggest what I could be doing wrong? > > > > I am using FreeBSD 4.1. > > the man page for -current ng_bpf (you can get it from > http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man4/ng_bpf.4 > > shows how to program a bpf node with a good example > (it was not in the 4.x man page) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 10:50:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 2E49137B71B for ; Tue, 27 Feb 2001 10:50:35 -0800 (PST) (envelope-from julian@elischer.org) Received: from elischer.org (i078-108.nv.iinet.net.au [203.59.78.108]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id CAA01636; Wed, 28 Feb 2001 02:50:08 +0800 Message-ID: <3A9BF6B7.703C3A3@elischer.org> Date: Tue, 27 Feb 2001 10:49:27 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Satyajeet Seth Cc: net@freebsd.org Subject: Re: Problem in configuring netgraph References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satyajeet Seth wrote: > > Hi > > I tried the example at: > http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man4/ng_bpf.4 > > When I type: > > tcpdump -ddd ether dest xx:xx:xx:xx:xx:xx > > in a telnet session the command gave the raw BPF instructions, as > expected. > > However, at the system console the same command gave the message: > > fxp0: promiscuous mode enabled > tcpdump: syntax error > xp0: promiscuous mode disabled > > Could you suggest what could be wrong? > > I also tried the following: > > 1. reboot > 2. ping -f & > 3. nghook -a fxp0: lower > Now I get identical packets. > > 4. ngctl mkpeer fxp0: bpf divert bhook > > 5. ngctl name fxp0:divert bpf0 > > 6. ngctl msg bpf0: setprogram { thisHook="bhook" ifMatch="hook2" > ifNotMatch="hook1" bpf_prog_len=1 bpf_prog=[ { code=6 } ] } > > Now all the packets are sent to hook1. > 7. nghook -a bpf0: hook1 > gives packets differing from point 3. how different? > > 8. ping to any machine on the lan does not work. > By default the upper and lower hooks of fxp0 are effectively connected. Our setup also does the > same. > > Could you suggest why the ping does not work? because the incoming packets are still being diverted to the bpf node. > > Thanks > Satya > -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 11:41: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from worldclass.jolt.nu (lgh637b.hn-krukan.AC [212.217.139.112]) by hub.freebsd.org (Postfix) with ESMTP id 776CF37B71A for ; Tue, 27 Feb 2001 11:41:01 -0800 (PST) (envelope-from c4@worldclass.jolt.nu) Received: by worldclass.jolt.nu (Postfix, from userid 1000) id 1F7CD4E; Tue, 27 Feb 2001 20:38:33 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by worldclass.jolt.nu (Postfix) with ESMTP id BAD6B44; Tue, 27 Feb 2001 20:38:33 +0100 (CET) Date: Tue, 27 Feb 2001 20:38:33 +0100 (CET) From: Tobias Fredriksson To: Jonathan Graehl Cc: freebsd-net@freebsd.org Subject: RE: Quick question about IP aliasing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org yeah and thats the reason for the 'or' in that sentance... On Mon, 26 Feb 2001, Jonathan Graehl wrote: > > do 'netmask 255.255.255.255' instead or 'netmask 0xffffffff' since this is > > an alias... for some reason otherwise services may not bind to the ip > > correctly > > Why would this be? The two are numerically equivalent. > > -Jon > > 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 Tue Feb 27 11:42:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from worldclass.jolt.nu (lgh637b.hn-krukan.AC [212.217.139.112]) by hub.freebsd.org (Postfix) with ESMTP id 3668937B71A for ; Tue, 27 Feb 2001 11:42:11 -0800 (PST) (envelope-from c4@worldclass.jolt.nu) Received: by worldclass.jolt.nu (Postfix, from userid 1000) id 88B774E; Tue, 27 Feb 2001 20:39:44 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by worldclass.jolt.nu (Postfix) with ESMTP id 868FA44; Tue, 27 Feb 2001 20:39:44 +0100 (CET) Date: Tue, 27 Feb 2001 20:39:44 +0100 (CET) From: Tobias Fredriksson To: "Rogier R. Mulhuijzen" Cc: "Drew J. Weaver" , "'freebsd-net@freebsd.org'" Subject: Re: Quick question about IP aliasing In-Reply-To: <4.3.2.7.0.20010227012505.00c6b340@mail.bsdchicks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 27 Feb 2001, Rogier R. Mulhuijzen wrote: > At 01:06 27-2-01 +0100, Tobias Fredriksson wrote: > > > >On Mon, 26 Feb 2001, Drew J. Weaver wrote: > > > > > Say I have a main server Ip address of (This is completely made up) > > > 209.190.53.51, and I have 32 IP addresses blocked to it on 209.51.193.32-64 > > > (or whatever, this is an example) would this alias line still be valid for > > > that? I've never done a server where the MAIN IP and the aliased IPs > > were on > > > different IP classes. > > > > > > ifconfig_fxp0_alias0="inet 209.51.193.32 netmask 255.255.255.0" (is an > > > example of what im using for the aliases.) > > > >do 'netmask 255.255.255.255' instead or 'netmask 0xffffffff' since this is > >an alias... for some reason otherwise services may not bind to the ip > >correctly > > Not if the alias is in a different subnet though. Or am I missing something? > > DocWilco > no not if its on another subnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 11:53:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from kanga.honeypot.net (kanga.honeypot.net [216.224.193.50]) by hub.freebsd.org (Postfix) with ESMTP id 911B137B718 for ; Tue, 27 Feb 2001 11:53:41 -0800 (PST) (envelope-from kirk@honeypot.net) Received: from pooh.honeypot (mail@pooh.honeypot [10.0.1.2]) by kanga.honeypot.net (8.11.2/8.11.2) with ESMTP id f1RJrdJ18555 for ; Tue, 27 Feb 2001 13:53:39 -0600 (CST) (envelope-from kirk@honeypot.net) Received: from kirk by pooh.honeypot with local (Exim 3.12 #1 (Debian)) id 14XqBn-0006TW-00 for ; Tue, 27 Feb 2001 13:53:39 -0600 To: freebsd-net@freebsd.org Subject: Freenet6, IPv6 tunnels, and rc.conf From: Kirk Strauser Date: 27 Feb 2001 13:53:39 -0600 Message-ID: <87d7c3ewcc.fsf@pooh.honeypot> Lines: 44 X-Mailer: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I hope this is the right place to ask; if not, a gentle nudge in the right direction would be most appreciated. I registered for an IPv6 tunnel from www.freenet6.net, and they send me the following Perl script (modified to work behind a NAT router according to the "IPv6-behind-NAT" instructions at ): ---8<----- $if='gif0'; # Via ifconfig | grep # Somes informations about tunnels values print "This script will create a tunnel between this computer\n"; print "and the Freenet6 server (tunnels server)\n"; print "Your IPv6 address (your tunnel end point) is 3ffe:b00:c18:1fff:0:0:0:461 \n"; print "We establish a tunnel to the Freenet6 server at 3ffe:b00:c18:1fff:0:0:0:460 \n"; print "Your IPv4 address is : 216.224.193.50 \n"; print "The IPv4 address of the Freenet6 server is : 206.123.31.102 \n"; # Setup the tunnel with values from Freenet6 system(`gifconfig $if 10.0.0.2 206.123.31.102`); system(`ifconfig $if inet6 3ffe:b00:c18:1fff:0:0:0:461 3ffe:b00:c18:1fff:0:0:0:460 prefixlen 128 alias`); system(`ifconfig $if up`); system(`route add -inet6 default 3ffe:b00:c18:1fff:0:0:0:461`); ---8<----- This works well; I can ping6 the world to my heart's content. The next step I want to try, though is integrating this IPv6-over-4 tunnel into my rc.conf (4.2-STABLE, BTW). Frankly, I'm completely bewildered by the IPv6 section of that file. What values do I plug in, and where? I want this machine to be a IPv6 gateway for the other machines on my LAN, too. Any help appreciated! -- Kirk Strauser To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 13:45:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from kiop.wiredmedia.co.uk (wiredmedia-2.dsl.easynet.co.uk [212.135.181.114]) by hub.freebsd.org (Postfix) with ESMTP id 2C02D37B722 for ; Tue, 27 Feb 2001 13:45:30 -0800 (PST) (envelope-from joe@tao.org.uk) Received: from tao.org.uk (postfix@genius.tao.org.uk [212.135.162.50] (may be forged)) by kiop.wiredmedia.co.uk (8.11.2/8.11.2) with ESMTP id f1RLpJ348694 for ; Tue, 27 Feb 2001 21:51:24 GMT (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id 785B031C5; Tue, 27 Feb 2001 19:45:56 +0000 (GMT) Date: Tue, 27 Feb 2001 19:45:56 +0000 From: Josef Karthauser To: "Rogier R. Mulhuijzen" Cc: Matthew Emmerton , Jonathan Graehl , freebsd-net@FreeBSD.ORG Subject: Re: Quick question about IP aliasing Message-ID: <20010227194556.C737@tao.org.uk> References: <001501c0a070$3a14d900$1200a8c0@gsicomp.on.ca> <4.3.2.7.0.20010227070424.00d25c10@mail.bsdchicks.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="4ZLFUWh1odzi/v6L" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4.3.2.7.0.20010227070424.00d25c10@mail.bsdchicks.com>; from drwilco@drwilco.nl on Tue, Feb 27, 2001 at 07:16:14AM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --4ZLFUWh1odzi/v6L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 27, 2001 at 07:16:14AM +0100, Rogier R. Mulhuijzen wrote: > > >The point is that you need to use a netmask of 255.255.255.255 for alias= ed > >IPs on FreeBSD, regardless of the alias of the primary (non-alias) IP. >=20 > Everybody is saying use 255.255.255.255 for an alias. Noone is giving=20 > reasons why. I don't understand this either. To my mind it's a bug if it doesn't work with the full netmask for an IP alias address. Joe --4ZLFUWh1odzi/v6L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqcA/MACgkQXVIcjOaxUBajYQCfWYL3MN4PbJRPTgdPkqoa9Xrz cpYAoJtjnAMsyGnlWyTd4DJ9rtIE8aa4 =RJa6 -----END PGP SIGNATURE----- --4ZLFUWh1odzi/v6L-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 13:47:43 2001 Delivered-To: freebsd-net@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id A77DB37B719 for ; Tue, 27 Feb 2001 13:47:39 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.16 #1) id 14Xrxo-000ErD-00; Tue, 27 Feb 2001 13:47:20 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Josef Karthauser Cc: freebsd-net@freebsd.org Subject: Re: Quick question about IP aliasing References: <001501c0a070$3a14d900$1200a8c0@gsicomp.on.ca> <4.3.2.7.0.20010227070424.00d25c10@mail.bsdchicks.com> <20010227194556.C737@tao.org.uk> Message-Id: Date: Tue, 27 Feb 2001 13:47:20 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I don't understand this either. To my mind it's a bug if it doesn't > work with the full netmask for an IP alias address. you're right. submit patch. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 17:57: 0 2001 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id CB71C37B71A for ; Tue, 27 Feb 2001 17:56:57 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id CAA29214; Wed, 28 Feb 2001 02:56:57 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200102280156.CAA29214@info.iet.unipi.it> Subject: Re: Quick question about IP aliasing In-Reply-To: <20010227194556.C737@tao.org.uk> from Josef Karthauser at "Feb 27, 2001 07:45:56 pm" To: Josef Karthauser Date: Wed, 28 Feb 2001 02:56:57 +0100 (CET) Cc: "Rogier R. Mulhuijzen" , Matthew Emmerton , Jonathan Graehl , freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Tue, Feb 27, 2001 at 07:16:14AM +0100, Rogier R. Mulhuijzen wrote: > > > > >The point is that you need to use a netmask of 255.255.255.255 for aliased > > >IPs on FreeBSD, regardless of the alias of the primary (non-alias) IP. no this is incorrect. you just have to make sure that the aliased IP&mask do not generate info which is already in the routing table. E.g. if your primary addr is 1.2.3.4/24 , an alias of 1.2.3.5/24 will give a warning, but an alias of 1.2.4.4/24 will not, and most likely even 1.2.3.5/25 will not. > > > > Everybody is saying use 255.255.255.255 for an alias. Noone is giving > > reasons why. > > I don't understand this either. To my mind it's a bug if it doesn't > work with the full netmask for an IP alias address. it does work, you just have tomake sure that you use the correct parameters. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 19:56:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from samar.sasi.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 03B4B37B718 for ; Tue, 27 Feb 2001 19:56:10 -0800 (PST) (envelope-from sseth@sasken.com) Received: from samar (samar.sasi.com [164.164.56.2]) by samar.sasi.com (8.9.3/8.9.3) with SMTP id JAA07311 for ; Wed, 28 Feb 2001 09:26:04 +0530 (IST) Received: from suns3.sasi.com ([10.0.36.3]) by samar.sasi.com; Wed, 28 Feb 2001 09:26:04 +0000 (IST) Received: from localhost (sseth@localhost) by suns3.sasi.com (8.9.3/8.9.3) with ESMTP id JAA15261 for ; Wed, 28 Feb 2001 09:26:03 +0530 (IST) Date: Wed, 28 Feb 2001 09:26:03 +0530 (IST) From: Satyajeet Seth To: Subject: Re: Problem in configuring netgraph In-Reply-To: <3A9BF6B7.703C3A3@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Please read my comments below: > > I tried the example at: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man4/ng_bpf.4 > > > > When I type: > > > > tcpdump -ddd ether dest xx:xx:xx:xx:xx:xx > > > > in a telnet session the command gave the raw BPF instructions, as > > expected. > > > > However, at the system console the same command gave the message: > > > > fxp0: promiscuous mode enabled > > tcpdump: syntax error > > xp0: promiscuous mode disabled > > > > Could you suggest what could be wrong? > > > > I also tried the following: > > > > 1. reboot > > 2. ping -f & > > 3. nghook -a fxp0: lower > > Now I get identical packets. > > > > 4. ngctl mkpeer fxp0: bpf divert bhook > > > > 5. ngctl name fxp0:divert bpf0 > > > > 6. ngctl msg bpf0: setprogram { thisHook="bhook" ifMatch="hook2" > > ifNotMatch="hook1" bpf_prog_len=1 bpf_prog=[ { code=6 } ] } > > > > Now all the packets are sent to hook1. > > > 7. nghook -a bpf0: hook1 > > gives packets differing from step 3. > > how different? I experimented again and found that the packets printed by nghook are same in step 3 and 7. (i)For a few seconds, the first six bytes contained the MAC address of the machine and the next six bytes contained the MAC address of the machine being pinged. (ii)After the few seconds the first six bytes contain all f's. The next six bytes contain varying MAC addresses. I compared (i) for step 3 with (ii) for step 7 earlier. > > > > 8. ping to any machine on the lan does not work. > > By default the upper and lower hooks of fxp0 are effectively connected. Our setup also does the > > same. > > > > Could you suggest why the ping does not work? > > because the incoming packets are still being diverted to the bpf node. I mentioned in my previous mail but forgot to mention in this one that, ngctl connect bpf0: fxp0: hook1 upper was used before the ping in step 8. Thanks Satya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 19:58:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 19C9A37B71A for ; Tue, 27 Feb 2001 19:58:44 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.9.3) with SMTP id f1S3tgi16924; Tue, 27 Feb 2001 22:55:42 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <007901c0a13a$b4480dd0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Luigi Rizzo" , "Josef Karthauser" Cc: "Rogier R. Mulhuijzen" , "Jonathan Graehl" , References: <200102280156.CAA29214@info.iet.unipi.it> Subject: Re: Quick question about IP aliasing Date: Tue, 27 Feb 2001 22:58:15 -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.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > On Tue, Feb 27, 2001 at 07:16:14AM +0100, Rogier R. Mulhuijzen wrote: > > > > > > > [ Matt Emmerton wrote: ] > > > >The point is that you need to use a netmask of 255.255.255.255 for aliased > > > >IPs on FreeBSD, regardless of the alias of the primary (non-alias) IP. > > no this is incorrect. you just have to make sure that the aliased > IP&mask do not generate info which is already in the routing table. > E.g. if your primary addr is 1.2.3.4/24 , an alias of 1.2.3.5/24 will > give a warning, but an alias of 1.2.4.4/24 will not, and most likely even > 1.2.3.5/25 will not. I'm just reiterating what I was told 1.5 years ago when I complained that the following setup wouldn't work: Primary IP: 192.168.0.1/255.255.255.0 Aliased IP: 192.168.0.10/255.255.255.0 With this setup, I could not ping, traceroute or connect to the aliased IP. In order to make the aliased IP functional, I had to use a netmask of 255.255.255.255 -- a fact which I find totally confusing and counter-intuitive, but one that seems to work. > > > Everybody is saying use 255.255.255.255 for an alias. Noone is giving > > > reasons why. Exactly. I never got a good answer to this when I first stumbled upon it, and I still haven't. All I know is that this is the way it needs to be done in order for things to work properly. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 20:11:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 379DD37B719 for ; Tue, 27 Feb 2001 20:11:38 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id FAA30065; Wed, 28 Feb 2001 05:12:26 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200102280412.FAA30065@info.iet.unipi.it> Subject: Re: Quick question about IP aliasing In-Reply-To: <007901c0a13a$b4480dd0$1200a8c0@gsicomp.on.ca> from Matthew Emmerton at "Feb 27, 2001 10:58:15 pm" To: Matthew Emmerton Date: Wed, 28 Feb 2001 05:12:25 +0100 (CET) Cc: Josef Karthauser , "Rogier R. Mulhuijzen" , Jonathan Graehl , freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Charset iso-8859-1 unsupported, filtering to ASCII...] > > > On Tue, Feb 27, 2001 at 07:16:14AM +0100, Rogier R. Mulhuijzen wrote: > > > > > > > > > [ Matt Emmerton wrote: ] > > > > >The point is that you need to use a netmask of 255.255.255.255 for > aliased > > > > >IPs on FreeBSD, regardless of the alias of the primary (non-alias) > IP. > > > > no this is incorrect. you just have to make sure that the aliased > > IP&mask do not generate info which is already in the routing table. > > E.g. if your primary addr is 1.2.3.4/24 , an alias of 1.2.3.5/24 will > > give a warning, but an alias of 1.2.4.4/24 will not, and most likely even > > 1.2.3.5/25 will not. > > I'm just reiterating what I was told 1.5 years ago when I complained that > the following setup wouldn't work: > > Primary IP: 192.168.0.1/255.255.255.0 > Aliased IP: 192.168.0.10/255.255.255.0 > > With this setup, I could not ping, traceroute or connect to the aliased IP. > In order to make the aliased IP functional, I had to use a netmask of > 255.255.255.255 -- a fact which I find totally confusing and > counter-intuitive, but one that seems to work. the source of confusion is just the fact that when you ifconfig an interface, you really give two distinct pieces of information: 1. an ip address that the machine recognises as its own 2. an address for a subnet connected to that interface. With aliases you can assign multiple instances of 1 and 2, as long as they are distinct. In your example the subnet address that you try to set with the alias is the same as the one you have already set with the primary ip, so the info is already there and you get the warning/error. > > > > Everybody is saying use 255.255.255.255 for an alias. Noone is giving > > > > reasons why. > > Exactly. I never got a good answer to this when I first stumbled upon it, > and I still haven't. All I know is that this is the way it needs to be done > in order for things to work properly. the reason is above. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone (510) 666 2927 . ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 21: 7:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from measurement-factory.com (measurement-factory.com [206.168.0.5]) by hub.freebsd.org (Postfix) with ESMTP id D11C437B71A for ; Tue, 27 Feb 2001 21:07:14 -0800 (PST) (envelope-from rousskov@measurement-factory.com) Received: (from rousskov@localhost) by measurement-factory.com (8.9.3/8.9.3) id WAA43278; Tue, 27 Feb 2001 22:06:58 -0700 (MST) (envelope-from rousskov) Date: Tue, 27 Feb 2001 22:06:58 -0700 (MST) From: Alex Rousskov To: Luigi Rizzo Cc: freebsd-net@FreeBSD.ORG Subject: Re: Quick question about IP aliasing In-Reply-To: <200102280412.FAA30065@info.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 28 Feb 2001, Luigi Rizzo wrote: > the source of confusion is just the fact that when you ifconfig an > interface, you really give two distinct pieces of information: > 1. an ip address that the machine recognises as its own > 2. an address for a subnet connected to that interface. > With aliases you can assign multiple instances of 1 and 2, as long > as they are distinct. In your example the subnet address that > you try to set with the alias is the same as the one you have > already set with the primary ip, so the info is already there and > you get the warning/error. Luigi, Can you be more specific please? Is it just a harmless warning message or a true error? In other words, will anything break if I use a.b.c.2/24 alias on the interface with the a.b.c.1/24 primary address? I hate to admit, but this thread is very confusing to me -- several people are claiming opposite things with confidence. Unfortunately, I cannot simply ignore the discussion. For benchmarking purposes, we routinely use thousands of IP aliases that belong to the same subnet on one interface without any known problems. I want to know if we are doing something wrong. I do not care about the ifconfig warning by itself. We do not even use ifconfig to manage aliases. I care about the actual run-time code that handles the addresses. Could you please clarify whether there is anything wrong with using, say, 10.0.0-3.1-250/16 aliases on the same interface? Thanks a lot, Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 21:15: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from worldclass.jolt.nu (lgh637b.hn-krukan.AC [212.217.139.112]) by hub.freebsd.org (Postfix) with ESMTP id 62A3337B71B for ; Tue, 27 Feb 2001 21:15:00 -0800 (PST) (envelope-from c4@worldclass.jolt.nu) Received: by worldclass.jolt.nu (Postfix, from userid 1000) id A069B4D; Wed, 28 Feb 2001 06:12:29 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by worldclass.jolt.nu (Postfix) with ESMTP id 75B624C; Wed, 28 Feb 2001 06:12:29 +0100 (CET) Date: Wed, 28 Feb 2001 06:12:28 +0100 (CET) From: Tobias Fredriksson To: Alex Rousskov Cc: Luigi Rizzo , freebsd-net@FreeBSD.ORG Subject: Re: Quick question about IP aliasing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 27 Feb 2001, Alex Rousskov wrote: > On Wed, 28 Feb 2001, Luigi Rizzo wrote: > > > the source of confusion is just the fact that when you ifconfig an > > interface, you really give two distinct pieces of information: > > 1. an ip address that the machine recognises as its own > > 2. an address for a subnet connected to that interface. > > With aliases you can assign multiple instances of 1 and 2, as long > > as they are distinct. In your example the subnet address that > > you try to set with the alias is the same as the one you have > > already set with the primary ip, so the info is already there and > > you get the warning/error. > > Luigi, > > Can you be more specific please? Is it just a harmless warning > message or a true error? In other words, will anything break if I use > a.b.c.2/24 alias on the interface with the a.b.c.1/24 primary address? No you will be able to bind normaly to a.b.c.1, but i have had the problems where if i specify anything to bind a.b.c.2 and it has bound on all ip's aliased on the computer. > I hate to admit, but this thread is very confusing to me -- > several people are claiming opposite things with confidence. > Unfortunately, I cannot simply ignore the discussion. For benchmarking > purposes, we routinely use thousands of IP aliases that belong to the > same subnet on one interface without any known problems. I want to > know if we are doing something wrong. > > I do not care about the ifconfig warning by itself. We do not > even use ifconfig to manage aliases. I care about the actual run-time > code that handles the addresses. Could you please clarify whether > there is anything wrong with using, say, 10.0.0-3.1-250/16 aliases on > the same interface? > > Thanks a lot, > > Alex. > > > 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 Tue Feb 27 21:41:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from measurement-factory.com (measurement-factory.com [206.168.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 6FDB037B719 for ; Tue, 27 Feb 2001 21:41:18 -0800 (PST) (envelope-from rousskov@measurement-factory.com) Received: (from rousskov@localhost) by measurement-factory.com (8.9.3/8.9.3) id WAA44406; Tue, 27 Feb 2001 22:41:02 -0700 (MST) (envelope-from rousskov) Date: Tue, 27 Feb 2001 22:41:02 -0700 (MST) From: Alex Rousskov To: Tobias Fredriksson Cc: freebsd-net@FreeBSD.ORG Subject: Re: Quick question about IP aliasing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 28 Feb 2001, Tobias Fredriksson wrote: > No you will be able to bind normaly to a.b.c.1, but i have had the > problems where if i specify anything to bind a.b.c.2 and it has bound on > all ip's aliased on the computer. Tobias, I know that I can bind to any (and all) of the 1000+ aliases without any visible problems. We are running thousands of simulated HTTP clients and servers that way, each sending from or listening on its own alias... That is exactly why I am asking for a definitive answer based on how things are implemented in the kernel rather than case studies. Thanks, Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 21:46:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id EEA6F37B718 for ; Tue, 27 Feb 2001 21:46:53 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id GAA30434; Wed, 28 Feb 2001 06:47:49 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200102280547.GAA30434@info.iet.unipi.it> Subject: Re: Quick question about IP aliasing In-Reply-To: from Alex Rousskov at "Feb 27, 2001 10:06:58 pm" To: Alex Rousskov Date: Wed, 28 Feb 2001 06:47:49 +0100 (CET) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alex, > Can you be more specific please? Is it just a harmless warning > message or a true error? In other words, will anything break if I use > a.b.c.2/24 alias on the interface with the a.b.c.1/24 primary address? technically i think it is a real error to use a /24 alias, but i am not 100% sure about the amt of problems it causes. > Unfortunately, I cannot simply ignore the discussion. For benchmarking > purposes, we routinely use thousands of IP aliases that belong to the > same subnet on one interface without any known problems. I want to > know if we are doing something wrong. > > I do not care about the ifconfig warning by itself. We do not > even use ifconfig to manage aliases. I care about the actual run-time > code that handles the addresses. Could you please clarify whether if you do care about this, you may want to restructure the data structure used to store/match interface addresses. At the moment it is a linear list, so the matching of incoming packets is probably Very Time Comsuming! cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone (510) 666 2927 . ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 22:13:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 2785037B71E for ; Tue, 27 Feb 2001 22:13:36 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14Y01n-0000G6-00; Tue, 27 Feb 2001 23:23:59 -0700 Message-ID: <3A9C997F.51F81F8D@softweyr.com> Date: Tue, 27 Feb 2001 23:23:59 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Josef Karthauser Cc: "Rogier R. Mulhuijzen" , Matthew Emmerton , Jonathan Graehl , freebsd-net@FreeBSD.ORG Subject: Re: Quick question about IP aliasing References: <001501c0a070$3a14d900$1200a8c0@gsicomp.on.ca> <4.3.2.7.0.20010227070424.00d25c10@mail.bsdchicks.com> <20010227194556.C737@tao.org.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Josef Karthauser wrote: > > On Tue, Feb 27, 2001 at 07:16:14AM +0100, Rogier R. Mulhuijzen wrote: > > > > >The point is that you need to use a netmask of 255.255.255.255 for aliased > > >IPs on FreeBSD, regardless of the alias of the primary (non-alias) IP. > > > > Everybody is saying use 255.255.255.255 for an alias. Noone is giving > > reasons why. > > I don't understand this either. To my mind it's a bug if it doesn't > work with the full netmask for an IP alias address. Because if you don't, it won't work. ifconfig(8) may not be telling the entire truth here: alias Establish an additional network address for this interface. This is sometimes useful when changing network numbers, and one wishes to accept packets addressed to the old interface. If the address is on the same subnet as the first network address for this in- terface, a netmask of 0xffffffff has to be specified. Somebody should look to see if the man page is true, or if you have to use a netmask of 0xffffffff for all aliases. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 22:43:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 9AC8337B71C for ; Tue, 27 Feb 2001 22:43:52 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.9.3) with SMTP id f1S6fdi17565; Wed, 28 Feb 2001 01:41:39 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <010d01c0a151$ddfca980$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Wes Peters" , "Josef Karthauser" Cc: "Rogier R. Mulhuijzen" , "Jonathan Graehl" , References: <001501c0a070$3a14d900$1200a8c0@gsicomp.on.ca> <4.3.2.7.0.20010227070424.00d25c10@mail.bsdchicks.com> <20010227194556.C737@tao.org.uk> <3A9C997F.51F81F8D@softweyr.com> Subject: Re: Quick question about IP aliasing Date: Wed, 28 Feb 2001 01:44:14 -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.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Josef Karthauser wrote: > > > > On Tue, Feb 27, 2001 at 07:16:14AM +0100, Rogier R. Mulhuijzen wrote: > > > > > > >The point is that you need to use a netmask of 255.255.255.255 for aliased > > > >IPs on FreeBSD, regardless of the alias of the primary (non-alias) IP. > > > > > > Everybody is saying use 255.255.255.255 for an alias. Noone is giving > > > reasons why. > > > > I don't understand this either. To my mind it's a bug if it doesn't > > work with the full netmask for an IP alias address. > > Because if you don't, it won't work. ifconfig(8) may not be telling the > entire truth here: > > alias Establish an additional network address for this interface. This > is sometimes useful when changing network numbers, and one wishes > to accept packets addressed to the old interface. If the address > is on the same subnet as the first network address for this in- > terface, a netmask of 0xffffffff has to be specified. > > Somebody should look to see if the man page is true, or if you have to use > a netmask of 0xffffffff for all aliases. I just had a short off-line conversation with Luigi Rizzo about this, and the manpage is true. (You must use a netmask of 0xffffffff for aliases on the same subnet as the primary IP, otherwise you use the appropriate netmask for the alias IP.) Since the more intuitive method is to use the 'appropriate' netmask all the time (and is what AIX and SCO do), I'm looking into seeing what it would take to add this functionality to FreeBSD. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 23:27:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 76DFB37B71A; Tue, 27 Feb 2001 23:27:12 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id XAA03780; Tue, 27 Feb 2001 23:27:11 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id XAA24555; Tue, 27 Feb 2001 23:27:10 -0800 (PST) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id XAA04777; Tue, 27 Feb 2001 23:27:10 -0800 (PST) From: Don Lewis Message-Id: <200102280727.XAA04777@salsa.gv.tsc.tdk.com> Date: Tue, 27 Feb 2001 23:27:10 -0800 In-Reply-To: <200102271943.f1RJhFn26351@freefall.freebsd.org> References: <200102271943.f1RJhFn26351@freefall.freebsd.org> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Jonathan Lemon , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/netinet ip_input.c Cc: freebsd-net@FreeBSD.org Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Feb 27, 11:43am, Jonathan Lemon wrote: } Subject: cvs commit: src/sys/netinet ip_input.c } jlemon 2001/02/27 11:43:14 PST } } Modified files: } sys/netinet ip_input.c } Log: } When iterating over our list of interface addresses in order to determine } if an arriving packet belongs to us, also check that the packet arrived } through the correct interface. Skip this check if the packet was locally } generated. } } Revision Changes Path } 1.156 +19 -15 src/sys/netinet/ip_input.c } }-- End of excerpt from Jonathan Lemon This (at least the non-IPFIREWALL_FORWARD case) doesn't look right to me. If I have a server dual homed on two networks with the IP addresses 192.168.1.1 and 192.168.2.1, and a client on the 192.168.1.0 network sends a packet to the 192.168.2.1 address to the 192.168.1.1 interface, it looks like the "ours" test will fail. I suspect this will cause the server to attempt to forward this packet out to the 192.168.2.0 network, if it has IP forwarding enabled. On the other hand, it looks like the server will accept a packet received on the 192.168.1.1 interface with the destination address 192.168.2.255. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 27 23:39: 6 2001 Delivered-To: freebsd-net@freebsd.org Received: from hera.drwilco.net (10dyn130.dh.casema.net [212.64.31.130]) by hub.freebsd.org (Postfix) with ESMTP id 5578B37B71A for ; Tue, 27 Feb 2001 23:39:01 -0800 (PST) (envelope-from drwilco@drwilco.nl) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.2/8.11.1) with ESMTP id f1S82Lo20602; Wed, 28 Feb 2001 09:02:21 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010228083627.0233f3c0@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 28 Feb 2001 08:38:41 +0100 To: "Matthew Emmerton" , "Luigi Rizzo" , "Josef Karthauser" From: "Rogier R. Mulhuijzen" Subject: Re: Quick question about IP aliasing Cc: "Jonathan Graehl" , In-Reply-To: <007901c0a13a$b4480dd0$1200a8c0@gsicomp.on.ca> References: <200102280156.CAA29214@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > Everybody is saying use 255.255.255.255 for an alias. Noone is giving > > > > reasons why. > >Exactly. I never got a good answer to this when I first stumbled upon it, >and I still haven't. All I know is that this is the way it needs to be done >in order for things to work properly. Ok, I meant everyone is saying use 255.255.255.255 for an alias even if it's on a different subnet. I've been preaching to use the real subnet when the alias is on a different subnet from the start of this thread =) DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 2:10:15 2001 Delivered-To: freebsd-net@freebsd.org Received: from ajax1.sovam.com (ajax1.sovam.com [194.67.1.172]) by hub.freebsd.org (Postfix) with ESMTP id 3B51737B71D for ; Wed, 28 Feb 2001 02:10:12 -0800 (PST) (envelope-from avn@any.ru) Received: from ts9-a405.dial.sovam.com ([195.239.71.149]:1065 "EHLO [195.239.71.149]" ident: "avn" whoson: "-unregistered-" smtp-auth: TLS-CIPHER: TLS-PEER: ) by ajax1.sovam.com with ESMTP id ; Wed, 28 Feb 2001 13:10:01 +0300 Date: Wed, 28 Feb 2001 13:10:50 +0300 (MSK) From: avn X-X-Sender: To: Subject: natd/ipfw or something else? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello there! I need to setup the following network: net A --+ | ------> ISP 1 v / (if1)GATEWAY(if2)------> ISP 2 ^ ^ \ | | ------> ISP n net B --+ | net C----------------+ .... While net A has normal network addresses; nets B,C have local addresses (like 10.0.0.0/8) and thus should diverted on a GATEWAY. Gateway has two network interfaces, and nets may be attached on both them. It should be possible to configure routing to specify which ISP each net is using, e.g. nets A and B should use ISP 1, while net C should use ISP2. I suppose the following: * having a natd running for each ISP we have * each natd is configured to use alias which is appropriate for given ISP (alias1, alias2) * allocate different ports for each ISP (as far as I understand, this is required by natd) (designated lower as port1, port2 etc) * the following rules in firewall ------------------------------------------------------------ fwd ISP1 all from (alias1) to any fwd ISP2 all from (alias2) to any ... divert (port1) all from (net B) to any via (if1) divert (port1) all from any to (alias1) via (if2) divert (port2) all from (net C) to any via (if2) divert (port2) all from any to (alias2) via (if2) ... ------------------------------------------------------------ Will this work? Am I missing something, or maybe there is less ugly way of setting up this? Regards, Alexey. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 3:23:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from cobweb.example.org (par-ilm-dhcp1-vl132-24.cisco.com [144.254.57.219]) by hub.freebsd.org (Postfix) with SMTP id 1EEA437B71A for ; Wed, 28 Feb 2001 03:23:54 -0800 (PST) (envelope-from molter@tin.it) Received: (qmail 1757 invoked by uid 1000); 28 Feb 2001 11:23:44 -0000 Date: Wed, 28 Feb 2001 12:23:44 +0100 From: Marco Molteni To: freebsd-net@freebsd.org Subject: How to implement a transport protocol with netgraph? Message-ID: <20010228122343.A425@cobweb.example.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I have to implement a kernel version of the transport protocol SCTP (Stream Control Transmission Protocol, RFC 2960), plus a socket interface to it as in draft-ietf-stewart-sctpsocket-sigtran-01.txt (the RFC has an ad hoc user interface). It seems to me that the modularity of netgraph would help a lot in this project, as opposed to go hacking half the kernel networking stack to put SCTP in it (and yes, this is my first big project in kernel land). I read the netgraph blueprint article on Daemonnews and the various netgraph manpages. The problem is that all the examples and applications I could find are layer 2 and layer 3, there is no example of a transport protocol done with netgraph. Since SCTP is reliable, at the very minimum I will have to handle timers, buffers, retransmissions and friends. So my questions are: o Any example of a transport protocol done with netgraph, or any hints (the more detailed the better :-) on how to tackle this task? Is netgraph suited for this (I think yes) ? o Let's say the socket interface will be something like sd = socket(PF_INET, SOCK_STREAM, IPPROTO_SCTP) How (or where) do I connect the socket system call to the netgraph framework? Thanks for the help Marco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 5: 2:37 2001 Delivered-To: freebsd-net@freebsd.org Received: from brisefer.cediti.be (brisefer.cediti.be [193.190.156.67]) by hub.freebsd.org (Postfix) with ESMTP id C76C737B719 for ; Wed, 28 Feb 2001 05:02:34 -0800 (PST) (envelope-from Olivier.Cherrier@cediti.be) Received: by brisefer.cediti.be with Internet Mail Service (5.5.2650.21) id <1TDVLFHV>; Wed, 28 Feb 2001 14:02:11 +0100 Message-ID: From: Olivier Cherrier To: freebsd-net@freebsd.org Subject: RE: mpd and mschap v2? Date: Wed, 28 Feb 2001 14:02:11 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Does mpd/netgraph support MSCHAP v2? I'm trying to connect via >PPTP to a firewall which requires MSCHAPv2 and having no luck. > I think that mpd 3.2 doesn't support MSCHAP 2. Olivier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 5: 4:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from smtp2.vol.cz (smtp2.vol.cz [195.250.128.42]) by hub.freebsd.org (Postfix) with ESMTP id 21C0B37B71A for ; Wed, 28 Feb 2001 05:04:52 -0800 (PST) (envelope-from michal.kutnohorsky@asp1000.com) Received: from server.asp1000.cz (mail.asp1000.cz [212.27.223.156]) by smtp2.vol.cz (8.11.1/8.11.1) with ESMTP id f1SD4pa14763 for ; Wed, 28 Feb 2001 14:04:51 +0100 (CET) Received: by server.asp1000.cz with Internet Mail Service (5.5.2650.21) id ; Wed, 28 Feb 2001 14:02:30 +0100 Message-ID: <381F2A6B1CC4C449B19CA48BA7A2A87B0E1C23@server.asp1000.cz> From: michal.kutnohorsky@asp1000.com To: freebsd-net@freebsd.org Subject: FW: traffic monitoring Date: Wed, 28 Feb 2001 14:02:26 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-2" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > hi, > > im lookin for some easy and simple program which will allow me to watching > how many MB transfer which ip in my local net thru freebsd server and by > which services it was transfered /www,ftp etc./ > > any know about some simple program? > > thanx > > michal > > x--------------------------x > |-- Michal Kutnohorsky -- | > |-- michalk@asp1000.com -- | > |-- icq 24864416 -- | > | \_/ -- dej si taky -- | > x--------------------------x > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 6:24:36 2001 Delivered-To: freebsd-net@freebsd.org Received: from measurement-factory.com (measurement-factory.com [206.168.0.5]) by hub.freebsd.org (Postfix) with ESMTP id AC78D37B71C for ; Wed, 28 Feb 2001 06:24:34 -0800 (PST) (envelope-from rousskov@measurement-factory.com) Received: (from rousskov@localhost) by measurement-factory.com (8.9.3/8.9.3) id HAA57191; Wed, 28 Feb 2001 07:24:21 -0700 (MST) (envelope-from rousskov) Date: Wed, 28 Feb 2001 07:24:21 -0700 (MST) From: Alex Rousskov To: Luigi Rizzo Cc: freebsd-net@FreeBSD.ORG Subject: Re: Quick question about IP aliasing In-Reply-To: <200102280547.GAA30434@info.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 28 Feb 2001, Luigi Rizzo wrote: > if you do care about this, you may want to restructure the data structure > used to store/match interface addresses. At the moment it is a linear list, > so the matching of incoming packets is probably Very Time Comsuming! We have a patch (posted to this list long time ago) that optimizes the lookup for incoming packets: http://polygraph.ircache.net/Tips/FreeBSD-3.3/ip_addr_hash.patch You are right that an unpatched kernel cannot handle more than ~500 aliases efficiently: http://www.ircache.net/~wessels/Junk/aliases/ Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 7:30:29 2001 Delivered-To: freebsd-net@freebsd.org Received: from curly.chiaro.com (us.chiaro.com [63.88.196.33]) by hub.freebsd.org (Postfix) with ESMTP id 2948637B71A for ; Wed, 28 Feb 2001 07:30:27 -0800 (PST) (envelope-from plawthers@chiaro.com) Received: from chiaro.com (192-168-25-122.chiaro.com [192.168.25.122]) by curly.chiaro.com (8.9.3+Sun/8.9.1) with ESMTP id JAA19730; Wed, 28 Feb 2001 09:30:06 -0600 (CST) Message-ID: <3A9D196F.49310D36@chiaro.com> Date: Wed, 28 Feb 2001 09:29:51 -0600 From: Peter Lawthers Organization: Chiaro Networks X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Garrett Wollman Cc: freebsd-net@FreeBSD.ORG Subject: Re: sendfile with headers (struct sf_hdtr) References: <3A9AE15D.103DFBB7@chiaro.com> <200102270350.WAA71013@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Actually, sendfile(2) returns either 0 or -1 (with errno set). The optional 'sbytes' argument indicates how many bytes were sent. Maybe I wasn't clear in my original posting. If you use the optional headers, then the *return value* from sendfile is non-zero, and is *only * the amount sent via writev. Not 0, or -1 as the code and the man page lead one to believe. Garrett Wollman wrote: > > < said: > > > When using sendfile(2) with the optional headers, it appears > > that sendfile inadvertently returns the number of bytes written > > via writev > > If any data was sent, sendfile() should tell you so. > > -GAWollman > > 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 Wed Feb 28 7:39:45 2001 Delivered-To: freebsd-net@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 617A237B718 for ; Wed, 28 Feb 2001 07:39:41 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.9.3) with SMTP id f1SFbMi18995; Wed, 28 Feb 2001 10:37:22 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <002a01c0a19c$bd692a90$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Luigi Rizzo" , "Josef Karthauser" , "Rogier R. Mulhuijzen" Cc: "Jonathan Graehl" , References: <200102280156.CAA29214@info.iet.unipi.it> <4.3.2.7.0.20010228083627.0233f3c0@mail.drwilco.net> Subject: Re: Quick question about IP aliasing Date: Wed, 28 Feb 2001 10:40:04 -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.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > > Everybody is saying use 255.255.255.255 for an alias. Noone is giving > > > > > reasons why. > > > >Exactly. I never got a good answer to this when I first stumbled upon it, > >and I still haven't. All I know is that this is the way it needs to be done > >in order for things to work properly. > > Ok, I meant everyone is saying use 255.255.255.255 for an alias even if > it's on a different subnet. I've been preaching to use the real subnet when > the alias is on a different subnet from the start of this thread =) That's partly my fault, as I wasn't aware that you are to use the real subnet when your aliased IP is on a different subnet. At least I'm straightened out now :) -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 7:50:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from femail11.sdc1.sfba.home.com (femail11.sdc1.sfba.home.com [24.0.95.107]) by hub.freebsd.org (Postfix) with ESMTP id D4EFC37B718 for ; Wed, 28 Feb 2001 07:50:47 -0800 (PST) (envelope-from justin@mac.com) Received: from lilith ([65.11.111.111]) by femail11.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010228155047.MAEY10024.femail11.sdc1.sfba.home.com@lilith> for ; Wed, 28 Feb 2001 07:50:47 -0800 Date: Tue, 27 Feb 2001 20:13:12 -0800 Content-Type: text/plain; format=flowed; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v379) From: Justin C.Walker To: X-Mailer: Apple Mail (2.379) In-Reply-To: <007901c0a13a$b4480dd0$1200a8c0@gsicomp.on.ca> Subject: Re: Quick question about IP aliasing Content-Transfer-Encoding: 7bit Message-Id: <20010228155047.MAEY10024.femail11.sdc1.sfba.home.com@lilith> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tuesday, February 27, 2001, at 07:58 PM, Matthew Emmerton wrote: >>> On Tue, Feb 27, 2001 at 07:16:14AM +0100, Rogier R. Mulhuijzen wrote: >>>> >>>>> [snip] >> no this is incorrect. you just have to make sure that the aliased >> IP&mask do not generate info which is already in the routing table. >> E.g. if your primary addr is 1.2.3.4/24 , an alias of 1.2.3.5/24 will >> give a warning, but an alias of 1.2.4.4/24 will not, and most likely >> even >> 1.2.3.5/25 will not. > > I'm just reiterating what I was told 1.5 years ago when I complained > that > the following setup wouldn't work: > > Primary IP: 192.168.0.1/255.255.255.0 > Aliased IP: 192.168.0.10/255.255.255.0 > > With this setup, I could not ping, traceroute or connect to the aliased > IP. > In order to make the aliased IP functional, I had to use a netmask of > 255.255.255.255 -- a fact which I find totally confusing and > counter-intuitive, but one that seems to work. It's only confusing because you're not looking deep enough into the mechanics of routing on a BSD system. The problem is that, using the "proper" netmask, assigning an alias leaves the system unable to process incoming frames for that IP address. As was mentioned in a now-defunct tutorial page on IP aliasing, if you take this approach (using the "proper" netmask) and the alias is on the same subnet as an existing address for this interface, you have to add a step in the configuration, namely, to install a static route to permit the handling of this new address. If you use the netmask 255.255.255.255, you are, in essence, saying that this needs a host route to the local box, on the interface to which the alias is assigned. The system graciously supplies one. It can't, in the previous case, because it's not clear what you are trying to do. At least, that's how I understand it. > >>>> Everybody is saying use 255.255.255.255 for an alias. Noone is giving >>>> reasons why. > > Exactly. I never got a good answer to this when I first stumbled upon > it, > and I still haven't. All I know is that this is the way it needs to be > done > in order for things to work properly. Hope this helps. Clarifications and corrections requested. Regards, Justin Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | | Men are from Earth Nexsi Corp. | Women are from Earth 1959 Concourse Drive | Deal with it. San Jose, CA 95131 | *-------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 7:53: 3 2001 Delivered-To: freebsd-net@freebsd.org Received: from black.purplecat.net (ns1.purplecat.net [209.16.228.148]) by hub.freebsd.org (Postfix) with ESMTP id 4FAA737B71A for ; Wed, 28 Feb 2001 07:53:00 -0800 (PST) (envelope-from peter@black.purplecat.net) Received: from localhost (peter@localhost) by black.purplecat.net (8.8.8/8.8.8) with ESMTP id KAA27261 for ; Wed, 28 Feb 2001 10:55:21 -0500 (EST) (envelope-from peter@black.purplecat.net) Date: Wed, 28 Feb 2001 10:55:21 -0500 (EST) From: Peter Brezny To: freebsd-net@freebsd.org Subject: DNS problems with hub.freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This isn't a support question but I figured someone who had some influence over the DNS server at hub.freebsd.org might see this message if i posted here. My mail has been refused from freebsd.org for the past two weeks or so, due to a change in mail server DNS. The rest of the internet appears to have figured out the forward and reverse lookups for ns1.sysadmin-inc.com <--> 209.16.228.145 but eventhough hub.freebsd.org knows 209.16.228.145 --> ns1.sysadmin-inc.com It's still under the incorrect assumption (for the past two weeks or more) that: ns1.sysadmin-inc.com --> 209.16.228.150 Could someone please bump that system and have it update the cache.?... TIA Peter Brezny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 8: 0: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id A6D5037B718 for ; Wed, 28 Feb 2001 08:00:03 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 22025 invoked by uid 1001); 28 Feb 2001 16:00:01 +0000 (GMT) To: peter@black.purplecat.net Cc: freebsd-net@freebsd.org Subject: Re: DNS problems with hub.freebsd.org From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 28 Feb 2001 10:55:21 -0500 (EST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 28 Feb 2001 17:00:00 +0100 Message-ID: <22021.983376000@verdi.nethelp.no> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The rest of the internet appears to have figured out the forward and > reverse lookups for > > ns1.sysadmin-inc.com <--> 209.16.228.145 > > but eventhough hub.freebsd.org knows > 209.16.228.145 --> ns1.sysadmin-inc.com > > It's still under the incorrect assumption (for the past two weeks or more) > that: > ns1.sysadmin-inc.com --> 209.16.228.150 > > Could someone please bump that system and have it update the cache.?... The problem isn't hub.freebsd.org or its name servers. The problem is the .com name servers which have a glue record for ns1.sysadmin-inc.com: % dig ns sysadmin-inc.com @b.gtld-servers.net ; <<>> DiG 8.3 <<>> ns sysadmin-inc.com @b.gtld-servers.net ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 4 ;; QUERY SECTION: ;; sysadmin-inc.com, type = NS, class = IN ;; ANSWER SECTION: sysadmin-inc.com. 2D IN NS NS2.DELTACOM.NET. sysadmin-inc.com. 2D IN NS NS1.DELTACOM.NET. sysadmin-inc.com. 2D IN NS NS1.sysadmin-inc.com. sysadmin-inc.com. 2D IN NS VIRTUAL.sysadmin-inc.com. ;; ADDITIONAL SECTION: NS2.DELTACOM.NET. 2D IN A 207.230.75.50 NS1.DELTACOM.NET. 2D IN A 207.230.75.34 NS1.sysadmin-inc.com. 2D IN A 209.16.228.150 VIRTUAL.sysadmin-inc.com. 2D IN A 209.16.228.140 Until this glue record is corrected, you *will* have problems with the rest of the net. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 8: 9:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from cat.acs.sk (cat.acs.sk [212.89.228.4]) by hub.freebsd.org (Postfix) with ESMTP id 032D237B719 for ; Wed, 28 Feb 2001 08:09:11 -0800 (PST) (envelope-from tomas@hodan.sk) Received: from th (frodo.traco.sk [195.168.45.193]) by cat.acs.sk (8.11.2/8.11.1) with SMTP id f1SGA5G48604 for ; Wed, 28 Feb 2001 17:10:06 +0100 (CET) (envelope-from tomas@hodan.sk) From: "Tomas Hodan" To: Subject: custom queues Date: Wed, 28 Feb 2001 17:08:47 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi all, is there any way to make custome queues under freebsd like in cisco? if, yes could you also send me some example? thx tomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 8:12:34 2001 Delivered-To: freebsd-net@freebsd.org Received: from cosmo.jt.org (cosmo.jt.org [206.14.191.190]) by hub.freebsd.org (Postfix) with SMTP id 68A4037B718 for ; Wed, 28 Feb 2001 08:12:30 -0800 (PST) (envelope-from danp@danp.net) Received: (qmail 76919 invoked by uid 1000); 28 Feb 2001 16:12:27 -0000 Date: Wed, 28 Feb 2001 08:12:27 -0800 From: Dan Peterson To: freebsd-net@freebsd.org Subject: Re: DNS problems with hub.freebsd.org Message-ID: <20010228081227.A76505@danp.net> 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 peter@black.purplecat.net on Wed, Feb 28, 2001 at 10:55:21AM -0500 X-PGP-Key: http://danp.net/pubkey.asc Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Brezny wrote: > The rest of the internet appears to have figured out the forward and > reverse lookups for > > ns1.sysadmin-inc.com <--> 209.16.228.145 > > but eventhough hub.freebsd.org knows > 209.16.228.145 --> ns1.sysadmin-inc.com > > It's still under the incorrect assumption (for the past two weeks or more) > that: > ns1.sysadmin-inc.com --> 209.16.228.150 Using the handy dnstrace utility from the djbdns suite (http://cr.yp.to/djbdns.html), it's easy to see where the problem comes from. The root com/net/org servers have their own idea what "ns1.sysadmin-inc.com" points to. Since all queries for this host start at the roots and then move up to the com/net/org roots, resolvers stop when they get to the com/net/org roots because they provide an authoritive answer. Observe: 1 ns1._sysadmin-inc.com_ 207.230.75.50 135439 A 209.16.228.150 1 ns1.sysadmin-inc.com 192.36.144.133 172800 A 209.16.228.150 1 ns1.sysadmin-inc.com 192.41.162.30 172800 A 209.16.228.150 1 ns1.sysadmin-inc.com 198.17.208.67 172800 A 209.16.228.150 1 ns1.sysadmin-inc.com 198.41.3.101 172800 A 209.16.228.150 1 ns1.sysadmin-inc.com 198.41.3.38 172800 A 209.16.228.150 1 ns1.sysadmin-inc.com 203.181.106.5 172800 A 209.16.228.150 1 ns1.sysadmin-inc.com 205.188.185.18 172800 A 209.16.228.150 1 ns1.sysadmin-inc.com 207.200.81.69 172800 A 209.16.228.150 1 ns1.sysadmin-inc.com 208.206.240.5 172800 A 209.16.228.150 1 ns1.sysadmin-inc.com 210.132.100.101 172800 A 209.16.228.150 1 ns1.sysadmin-inc.com 213.177.194.5 172800 A 209.16.228.150 1 ns1._sysadmin-inc.com_ 207.230.75.34 86400 A 209.16.228.145 1 ns1._sysadmin-inc.com_ 209.16.228.140 86400 A 209.16.228.145 1 ns1._sysadmin-inc.com_ 209.16.228.145 86400 A 209.16.228.145 1 ns1._sysadmin-inc.com_ 209.16.228.150 86400 A 209.16.228.145 "1" is the query type. 1 is A. the second field is what the IP in the third field was being queried for. Naturally, the last section is what was returned. I've inserted underscores to underline (as dnstracesort does, but with actual underline terminal codes) what the IP being queried is supposed to be authoritive for. Since I started my dnstrace with [a-l].gtld-servers.net listed as my "roots," queries to them have no underlining since they're authoritive for everything. All the root servers say ns1.sysadmin-inc.com is 209.16.228.150. Notice how one of the sysadmin-inc.com servers even says ns1.sysadmin-inc.com is 209.16.228.150. This is all caused, of course, by ns1.sysadmin-inc.com being used to register domains (whois -h whois.networksolutions.com "host ns1.sysadmin-inc.com" and whois -h whois.networksolutions.com "server ns73505-hst"). It seems few people realize that when they register a nameserver with Internic, the root servers get their own A record for that host. This is why it's a bad idea to use normal machine names for domain registration and, on the flip side, a bad idea to use nameserver names for normal machine tasks. Hope this helps. -- Dan Peterson http://danp.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 8:22:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id A189B37B718 for ; Wed, 28 Feb 2001 08:22:20 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id RAA35750; Wed, 28 Feb 2001 17:23:11 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200102281623.RAA35750@info.iet.unipi.it> Subject: Re: custom queues In-Reply-To: from Tomas Hodan at "Feb 28, 2001 05:08:47 pm" To: Tomas Hodan Date: Wed, 28 Feb 2001 17:23:11 +0100 (CET) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > is there any way to make custome queues under freebsd like in cisco? > if, yes could you also send me some example? not sure on what you mean but maybe dummynet does something close to your needs. See http://www.iet.unipi.it/~luigi/ip_dummynet/ cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone (510) 666 2927 . ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 10:15:43 2001 Delivered-To: freebsd-net@freebsd.org Received: from black.purplecat.net (ns1.purplecat.net [209.16.228.148]) by hub.freebsd.org (Postfix) with ESMTP id B4AB037B71A for ; Wed, 28 Feb 2001 10:15:38 -0800 (PST) (envelope-from peter@black.purplecat.net) Received: from localhost (peter@localhost) by black.purplecat.net (8.8.8/8.8.8) with ESMTP id NAA28123 for ; Wed, 28 Feb 2001 13:18:00 -0500 (EST) (envelope-from peter@black.purplecat.net) Date: Wed, 28 Feb 2001 13:18:00 -0500 (EST) From: Peter Brezny To: freebsd-net@freebsd.org Subject: static nat problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I want to be able to forward all traffic coming to an external ip to an internal ip. I currently have nat configured and working so that all private internal addresses are translated to a public ip as they leave the firewall machine on their way out, but after reading the man page a couple of times, i've been unable to set up static nat for a single public ip to private ip translation using just the man page as a guide. What I've done to try and get this working is to start natd from rc.conf with both the -dynamic and -f /etc/natd.conf flags (see below). /etc/natd.conf currently has a single line: redirect_address 10.10.1.4 209.16.228.146 To try and clear up any weirdness, i've reduced my firewall to two lines: # BEGIN NAT TEST ENTRIES $fwcmd add divert natd all from any to any via $oif $fwcmd add allow all from any to any I know that natd is doing _something_ because when i remove the -f /etc/natd.conf section from rc.conf, http://209.16.228.146 gives me the default page. When i include the -f /etc/natd.conf flag in rc.conf _any_ connection to the external ip times out. I think I must have just missed something simple. TIA pb my rc.conf firewall options are as follows: # Firewall options by pab 001128 syslogd_flags="-ss" gateway_enable="YES" firewall_enable="YES" natd_enable="YES" natd_interface="fxp0" natd_flags="-dynamic -f /etc/natd.conf" firewall_script="/etc/rc.firewall.nattest" # end firewall options To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 28 20:32:17 2001 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 CE83437B718 for ; Wed, 28 Feb 2001 20:32:13 -0800 (PST) (envelope-from archie@dellroad.org) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id UAA15446; Wed, 28 Feb 2001 20:32:08 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.11.2/8.11.2) id f214W8V02297; Wed, 28 Feb 2001 20:32:08 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200103010432.f214W8V02297@curve.dellroad.org> Subject: Re: mpd and mschap v2? In-Reply-To: "from Olivier Cherrier at Feb 28, 2001 02:02:11 pm" To: Olivier Cherrier Date: Wed, 28 Feb 2001 20:32:08 -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 X-Loop: FreeBSD.org Olivier Cherrier writes: > >Does mpd/netgraph support MSCHAP v2? I'm trying to connect via > >PPTP to a firewall which requires MSCHAPv2 and having no luck. > > > > I think that mpd 3.2 doesn't support MSCHAP 2. Correct: it does not.. patches welcome :-) -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 Wed Feb 28 20:36:37 2001 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 3E77E37B718 for ; Wed, 28 Feb 2001 20:36:35 -0800 (PST) (envelope-from archie@dellroad.org) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id UAA15466; Wed, 28 Feb 2001 20:36:34 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.11.2/8.11.2) id f214aX302344; Wed, 28 Feb 2001 20:36:33 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200103010436.f214aX302344@curve.dellroad.org> Subject: Re: pptp, mpd and chap msoftv2 In-Reply-To: <20010221190335.A97793@chewbacca.netgroup.dk> "from Hroi Sigurdsson at Feb 21, 2001 07:03:35 pm" To: Hroi Sigurdsson Date: Wed, 28 Feb 2001 20:36:33 -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 X-Loop: FreeBSD.org Hroi Sigurdsson writes: > I'm trying to establish a pptp tunnel to a Watchguard Firebox II with > mpd-netgraph. > I'm getting LCP rejects and the Firebox II is complaining about out-of-order > GRE packets but not sure if that is the cause of problems :-( > Also I think there is a problem negotiating an auth protocol. CHAP MSOFT vs > MSOFTv2? > Any ideas what is actually going wrong? Unfortunately mpd doesn't support MS-CHAPv2 yet, only MS-CHAPv1. Patches would be gladly welcomed. -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 Mar 1 4:30:53 2001 Delivered-To: freebsd-net@freebsd.org Received: from cobweb.example.org (par-ilm-dhcp1-vl132-24.cisco.com [144.254.57.219]) by hub.freebsd.org (Postfix) with SMTP id 54E7537B719 for ; Thu, 1 Mar 2001 04:30:47 -0800 (PST) (envelope-from molter@tin.it) Received: (qmail 1502 invoked by uid 1000); 1 Mar 2001 12:30:45 -0000 Date: Thu, 1 Mar 2001 13:30:45 +0100 From: Marco Molteni To: freebsd-net@freebsd.org Subject: How to implement a transport protocol with netgraph? (2) Message-ID: <20010301133045.A1485@cobweb.example.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Since I didn't received a reply on my first posting, I am trying once more] Hi all, I have to implement a kernel version of the transport protocol SCTP (Stream Control Transmission Protocol, RFC 2960), plus a socket interface to it as in draft-ietf-stewart-sctpsocket-sigtran-01.txt (the RFC has an ad hoc user interface). It seems to me that the modularity of netgraph would help a lot in this project, as opposed to go hacking half the kernel networking stack to put SCTP in it (and yes, this is my first big project in kernel land). I read the netgraph blueprint article on Daemonnews and the various netgraph manpages. The problem is that all the examples and applications I could find are layer 2 and layer 3, there is no example of a transport protocol done with netgraph. Since SCTP is reliable, at the very minimum I will have to handle timers, buffers, retransmissions and friends. So my questions are: o Any example of a transport protocol done with netgraph, or any hints (the more detailed the better :-) on how to tackle this task? Is netgraph suited for this (I think yes) ? o Let's say the socket interface will be something like sd = socket(PF_INET, SOCK_STREAM, IPPROTO_SCTP) How (or where) do I connect the socket system call to the netgraph framework? Thanks for the help Marco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Mar 1 4:37:43 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 4780D37B71A for ; Thu, 1 Mar 2001 04:37:39 -0800 (PST) (envelope-from brandt@fokus.gmd.de) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id NAA20704; Thu, 1 Mar 2001 13:37:32 +0100 (MET) Date: Thu, 1 Mar 2001 13:37:32 +0100 (CET) From: Harti Brandt To: Marco Molteni Cc: Subject: Re: How to implement a transport protocol with netgraph? (2) In-Reply-To: <20010301133045.A1485@cobweb.example.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 1 Mar 2001, Marco Molteni wrote: MM>[Since I didn't received a reply on my first posting, I am trying once more] MM> MM>Hi all, MM> MM>I have to implement a kernel version of the transport protocol SCTP MM>(Stream Control Transmission Protocol, RFC 2960), plus a socket MM>interface to it as in draft-ietf-stewart-sctpsocket-sigtran-01.txt MM>(the RFC has an ad hoc user interface). MM> MM>It seems to me that the modularity of netgraph would help a lot in MM>this project, as opposed to go hacking half the kernel networking MM>stack to put SCTP in it (and yes, this is my first big project in MM>kernel land). MM> MM>I read the netgraph blueprint article on Daemonnews and the various MM>netgraph manpages. The problem is that all the examples and MM>applications I could find are layer 2 and layer 3, there is no example MM>of a transport protocol done with netgraph. MM> MM>Since SCTP is reliable, at the very minimum I will have to handle MM>timers, buffers, retransmissions and friends. MM> MM>So my questions are: MM> MM>o Any example of a transport protocol done with netgraph, or any hints MM> (the more detailed the better :-) on how to tackle this task? Is MM> netgraph suited for this (I think yes) ? MM> MM>o Let's say the socket interface will be something like MM> sd = socket(PF_INET, SOCK_STREAM, IPPROTO_SCTP) MM> How (or where) do I connect the socket system call to the netgraph MM> framework? MM> MM>Thanks for the help MM>Marco I have implemented SSCOP for ATM signalling in netgraph lately. If it helps you, I can send you the current code. There are however still a number of issues: - It has no socket interface yet. I plan to do one base on the ng_socket code. There should be a lot of similarities. - How to do flow control is not very clear up to now. There are a number of messages defined in netgraph.h for this and I have used them, but had no time to do a thourough test. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Mar 1 6:15:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 4C52337B719 for ; Thu, 1 Mar 2001 06:15:40 -0800 (PST) (envelope-from julian@elischer.org) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id WAA07139; Thu, 1 Mar 2001 22:15:33 +0800 Received: from elischer.org (i078-240.nv.iinet.net.au [203.59.78.240]) by muzak.iinet.net.au (8.8.5/8.8.5) with ESMTP id WAA26032; Thu, 1 Mar 2001 22:12:28 +0800 Message-ID: <3A9E597A.D3387FC2@elischer.org> Date: Thu, 01 Mar 2001 06:15:22 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Harti Brandt Cc: Marco Molteni , freebsd-net@FreeBSD.ORG Subject: Re: How to implement a transport protocol with netgraph? (2) References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Harti Brandt wrote: > > On Thu, 1 Mar 2001, Marco Molteni wrote: > > MM>[Since I didn't received a reply on my first posting, I am trying once more] > MM> > MM>Hi all, > MM> > MM>I have to implement a kernel version of the transport protocol SCTP > MM>(Stream Control Transmission Protocol, RFC 2960), plus a socket > MM>interface to it as in draft-ietf-stewart-sctpsocket-sigtran-01.txt > MM>(the RFC has an ad hoc user interface). > MM> > MM>It seems to me that the modularity of netgraph would help a lot in > MM>this project, as opposed to go hacking half the kernel networking > MM>stack to put SCTP in it (and yes, this is my first big project in > MM>kernel land). good luck! We all start somewhere. > MM> > MM>I read the netgraph blueprint article on Daemonnews and the various > MM>netgraph manpages. The problem is that all the examples and > MM>applications I could find are layer 2 and layer 3, there is no example > MM>of a transport protocol done with netgraph. that is true. Netgraph ws designed to be a link-layer framework, but it turns out that it can also be used for complete protocols. > MM> > MM>Since SCTP is reliable, at the very minimum I will have to handle > MM>timers, buffers, retransmissions and friends. you can certainly do that in netgraph. there are issues with locking in that a timer must not jump into a node while the node is locked, but there is a method for doing that. I will be adding more support for it so that it is easier to do. Add a small 'stub' function that does nothing but call the 'real' timer function through the locking mechanism. > MM> > MM>So my questions are: > MM> > MM>o Any example of a transport protocol done with netgraph, or any hints > MM> (the more detailed the better :-) on how to tackle this task? Is > MM> netgraph suited for this (I think yes) ? not at the moment. > MM> > MM>o Let's say the socket interface will be something like > MM> sd = socket(PF_INET, SOCK_STREAM, IPPROTO_SCTP) > MM> How (or where) do I connect the socket system call to the netgraph > MM> framework? make something that looks a bit like the ng_socket node type. but it can be a lot simpler as you won;t need two channels (control+data) you would have only ONE such node in a system and new sockets of that type would attach to that node (inside the module) just like tcp does. You may find that netgraph sockets give you a pointer in how to make a loadable protocol module, but they will have to be different too. check out divert sockets as another example of a simple protocol. (but it is connected to IP in some way) Hopefully I can help if you have problems > MM> > MM>Thanks for the help > MM>Marco > > I have implemented SSCOP for ATM signalling in netgraph lately. If it > helps you, I can send you the current code. There are however still a > number of issues: > > - It has no socket interface yet. I plan to do one base on the ng_socket > code. There should be a lot of similarities. why can you not use the netgraph sockets? > > - How to do flow control is not very clear up to now. There are a number > of messages defined in netgraph.h for this and I have used them, but > had no time to do a thourough test. flow control has been added to -current using the messages you saw but support is still not in most nodes. Only tee and UI nodes know how to pass them on... hopefully people who find that node type 'X' blocks their flow control messages can add the code to support them to 'X' and send me the diffs :-) I'm also looking to add some mechanism that makes this trivial but I don't know what it will be yet. > > harti > -- > harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private > brandt@fokus.gmd.de, harti@begemot.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Mar 1 6:17: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with SMTP id 6535337B718 for ; Thu, 1 Mar 2001 06:17:00 -0800 (PST) (envelope-from paulo@nlink.com.br) Received: (qmail 89804 invoked by uid 501); 1 Mar 2001 14:06:42 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Mar 2001 14:06:42 -0000 Date: Thu, 1 Mar 2001 11:06:42 -0300 (EST) From: Paulo Fragoso To: freebsd-net@freebsd.org Subject: Deamon with perl Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I've written a little server using perl, it's working fine using FBSD 4.x but when I try with FBSD 3.x it don't work: bind: Can't assign requested address at ... I've ever changed all /usr/libdata/perl directory to same used on FBSD 4.x, but I've got same error. Are there any problem with socket and perl on FBSD 3.x? Thanks, Paulo. -- __O _-\<,_ Why drive when you can bike? (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Mar 1 6:31:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 20F5437B719 for ; Thu, 1 Mar 2001 06:31:15 -0800 (PST) (envelope-from brandt@fokus.gmd.de) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id PAA05613; Thu, 1 Mar 2001 15:30:52 +0100 (MET) Date: Thu, 1 Mar 2001 15:30:51 +0100 (CET) From: Harti Brandt To: Julian Elischer Cc: Marco Molteni , Subject: Re: How to implement a transport protocol with netgraph? (2) In-Reply-To: <3A9E597A.D3387FC2@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 1 Mar 2001, Julian Elischer wrote: JE>Harti Brandt wrote: JE>> JE>> I have implemented SSCOP for ATM signalling in netgraph lately. If it JE>> helps you, I can send you the current code. There are however still a JE>> number of issues: JE>> JE>> - It has no socket interface yet. I plan to do one base on the ng_socket JE>> code. There should be a lot of similarities. JE> JE>why can you not use the netgraph sockets? Well, I want to be able to say fd = socket(PF_ATM, SOCK_STREAM, ATMPROTO_SSCOP); or something along that line. And netgraph sockets didn't generate flow control messages when I last locked at them (three weeks ago). JE>> - How to do flow control is not very clear up to now. There are a number JE>> of messages defined in netgraph.h for this and I have used them, but JE>> had no time to do a thourough test. JE> JE>flow control has been added to -current using the messages you saw but JE>support is still not in most nodes. Only tee and UI nodes know how to pass them JE>on... JE> JE>hopefully people who find that node type 'X' blocks their flow control messages JE>can add the code to support them to 'X' and send me the diffs :-) JE> JE>I'm also looking to add some mechanism that makes this trivial but I JE>don't know what it will be yet. Well, the problem is with the semantics of those messages. TCP, for example, thinks in bytes, SSCOP thinks in messages. So you have to generate the flow control messages differently for different consumers. (Or have them support both types). harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Mar 1 8: 0:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from tao.org.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 9763D37B718 for ; Thu, 1 Mar 2001 08:00:11 -0800 (PST) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id E891D313F; Thu, 1 Mar 2001 16:00:08 +0000 (GMT) Date: Thu, 1 Mar 2001 16:00:08 +0000 From: Josef Karthauser To: net@freebsd.org Subject: Stat counters for interfaces. Message-ID: <20010301160008.E726@tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ILuaRSyQpoVaJ1HG" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ILuaRSyQpoVaJ1HG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline A few months ago I added a struct if_data to struct ifaddr for keeping stats on a per interface address basis. Not all protocols current use this though, and not all values are meaningful. What I'd like to do is preload the members that aren't being used with -1, and then detect this in 'netstat -in' and print '-' instead of '0'. Does this make sense, or is it a hack :) ? The members of this structure carrying statistics are currently u_long, and so maybe I should use ULONG_MAX instead? Any opinions? Joe --ILuaRSyQpoVaJ1HG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqecgcACgkQXVIcjOaxUBYslQCgzLnDabxeiTjxbyQhRs0sIVOa 6n4AoMjyRVP5xJ5/AYosti8N/RBd6aHP =0RE5 -----END PGP SIGNATURE----- --ILuaRSyQpoVaJ1HG-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Mar 1 8:16:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id BEFED37B718 for ; Thu, 1 Mar 2001 08:16:00 -0800 (PST) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:DrS8M1hIWwJtA6Fo5i54NUAsu/2LmJYLCiqTvuFPHQSNF/7wNOwwcit0TiDz9Hgh@localhost [::1]) (authenticated as ume with CRAM-MD5) by peace.mahoroba.org (8.11.3/8.11.3/peace) with ESMTP/inet6 id f21GD3317593; Fri, 2 Mar 2001 01:13:03 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Fri, 02 Mar 2001 01:13:02 +0900 (JST) Message-Id: <20010302.011302.78721419.ume@mahoroba.org> To: kirk@strauser.com Cc: freebsd-net@freebsd.org Subject: Re: Freenet6, IPv6 tunnels, and rc.conf From: Hajimu UMEMOTO In-Reply-To: <87d7c3ewcc.fsf@pooh.honeypot> References: <87d7c3ewcc.fsf@pooh.honeypot> X-Mailer: xcite1.38> Mew version 1.95b97 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> On 27 Feb 2001 13:53:39 -0600 >>>>> Kirk Strauser said: kirk> I registered for an IPv6 tunnel from www.freenet6.net, and they kirk> send me the following Perl script (modified to work behind a NAT kirk> router according to the "IPv6-behind-NAT" instructions at kirk> ): kirk> ---8<----- kirk> $if='gif0'; # Via ifconfig | grep kirk> # Somes informations about tunnels values kirk> print "This script will create a tunnel between this kirk> computer\n"; kirk> print "and the Freenet6 server (tunnels server)\n"; kirk> print "Your IPv6 address (your tunnel end point) is kirk> 3ffe:b00:c18:1fff:0:0:0:461 \n"; kirk> print "We establish a tunnel to the Freenet6 server at kirk> 3ffe:b00:c18:1fff:0:0:0:460 \n"; kirk> print "Your IPv4 address is : 216.224.193.50 \n"; kirk> print "The IPv4 address of the Freenet6 server is : kirk> 206.123.31.102 \n"; kirk> # Setup the tunnel with values from Freenet6 kirk> system(`gifconfig $if 10.0.0.2 206.123.31.102`); kirk> system(`ifconfig $if inet6 3ffe:b00:c18:1fff:0:0:0:461 kirk> 3ffe:b00:c18:1fff:0:0:0:460 prefixlen 128 alias`); kirk> system(`ifconfig $if up`); kirk> system(`route add -inet6 default 3ffe:b00:c18:1fff:0:0:0:461`); kirk> ---8<----- kirk> This works well; I can ping6 the world to my heart's content. kirk> The next step I want to try, though is integrating this kirk> IPv6-over-4 tunnel into my rc.conf (4.2-STABLE, BTW). Frankly, kirk> I'm completely bewildered by the IPv6 section of that file. kirk> What values do I plug in, and where? Though I have never try Freenet6, it should work: ipv6_enable="YES" gif_interfaces="gif0" gifconfig_gif0="10.0.0.2 206.123.31.102" ipv6_network_interfaces="gif0" ipv6_ifconfig_gif0="3ffe:b00:c18:1fff:0:0:0:461 3ffe:b00:c18:1fff:0:0:0:460 prefixlen 128" ipv6_defaultrouter="3ffe:b00:c18:1fff:0:0:0:461" kirk> I want this machine to be a IPv6 gateway for the other machines kirk> on my LAN, too. Since Freenet6 serve only one host address, it is impossible. If you want to connect your LAN to 6bone, you need prefix assignment. -- 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 Mar 1 8:27:26 2001 Delivered-To: freebsd-net@freebsd.org Received: from kanga.honeypot.net (kanga.honeypot.net [216.224.193.50]) by hub.freebsd.org (Postfix) with ESMTP id 86AA637B718 for ; Thu, 1 Mar 2001 08:27:23 -0800 (PST) (envelope-from kirk@honeypot.net) Received: from pooh.honeypot (mail@pooh.honeypot [10.0.1.2]) by kanga.honeypot.net (8.11.2/8.11.2) with ESMTP id f21GRMJ30313 for ; Thu, 1 Mar 2001 10:27:22 -0600 (CST) (envelope-from kirk@honeypot.net) Received: from kirk by pooh.honeypot with local (Exim 3.12 #1 (Debian)) id 14YVvF-0006sc-00 for ; Thu, 01 Mar 2001 10:27:21 -0600 To: freebsd-net@freebsd.org Subject: Re: Freenet6, IPv6 tunnels, and rc.conf References: <87d7c3ewcc.fsf@pooh.honeypot> <20010302.011302.78721419.ume@mahoroba.org> From: Kirk Strauser Date: 01 Mar 2001 10:27:21 -0600 In-Reply-To: <20010302.011302.78721419.ume@mahoroba.org> Message-ID: <87y9upbgk6.fsf@pooh.honeypot> Lines: 19 X-Mailer: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 2001-03-01T16:13:02Z, Hajimu UMEMOTO writes: > Though I have never try Freenet6, it should work: Thanks for the assistance. I'm not yet at the point where I know enough about the subject to learn on my own. > kirk> I want this machine to be a IPv6 gateway for the other > kirk> machines on my LAN, too. > Since Freenet6 serve only one host address, it is impossible. > If you want to connect your LAN to 6bone, you need prefix > assignment. That's a beginner's mistake - I'm embarassed that I did not catch it. -- 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 Mar 1 16:39:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.andy.de (fw.andy.de [212.8.198.74]) by hub.freebsd.org (Postfix) with ESMTP id 97AD537B71F for ; Thu, 1 Mar 2001 16:39:21 -0800 (PST) (envelope-from andy@andy.de) Received: from windoze.andy.de (windoze.andy.de [212.8.199.4]) by mail.andy.de (Postfix) with ESMTP id A2B967CFF1 for ; Fri, 2 Mar 2001 01:39:20 +0100 (CET) Date: Fri, 02 Mar 2001 01:38:22 +0100 From: Andreas Gerstenberg To: freebsd-net@FreeBSD.org Subject: Re: vlan panics? Message-ID: <4244559283.983497102@windoze.andy.de> In-Reply-To: <3A8C0614.3131FB3@elischer.org> X-Mailer: Mulberry/2.0.6 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, -- Julian Elischer wrote: > Adrian Chadd wrote: >> I've discovered that on the fxp, if I ifconfig a vlan up without >> ifconfig'ing the parent interface (fxp) up, I'll get a panic. >> I don't have the bt handy at the moment but basically the codepath >> is bringing the vlan interface up, sending the gratuituous(sp)? arp >> request out the vlan interface, which sends it out the parent interface. >> The fxp code doesn't check whether the interface has been initialised >> when it attempts to queue a packet for outbound, and you get a panic. I had the same problem yesterday which took some hours to figure out, whats going wrong. I have opened a PR for this problem (25478), there is also a backtrace in. But now I'm reading my freebsd-net archive..I think in the future I'll have to take a look here before :-) > there's an fxp-Vlan patch floating around somewhere. Yes, http://www.euitt.upm.es/~pjlobo/fbsdvlan.html. This patch only helps you to receive long frames. But the panic described above happens independent of this patch. There is a workaround for this problem, but it can take hours to find out what happens or even to find out that you have to "ifconfig up" the parent interface before. regards, Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 2 0:38: 2 2001 Delivered-To: freebsd-net@freebsd.org Received: from ns.any.ru (ns.any.ru [194.67.127.11]) by hub.freebsd.org (Postfix) with ESMTP id AE51037B71B for ; Fri, 2 Mar 2001 00:37:57 -0800 (PST) (envelope-from avn@ns.any.ru) Received: (from avn@localhost) by ns.any.ru (8.11.2/8.11.2) id f228bPi94034 for freebsd-net@freebsd.org.AVP; Fri, 2 Mar 2001 11:37:25 +0300 (MSK) (envelope-from avn@ns.any.ru) X-Authentication-Warning: ns.any.ru: avn set sender to avn@ns.any.ru using -f Received: from localhost (avn@localhost) by ns.any.ru (8.11.2/8.11.2) with ESMTP id f228bJL94024 for ; Fri, 2 Mar 2001 11:37:24 +0300 (MSK) (envelope-from avn@ns.any.ru) X-Authentication-Warning: ns.any.ru: avn owned process doing -bs Date: Fri, 2 Mar 2001 11:37:19 +0300 (MSK) From: "Alexey V. Neyman" To: Subject: ipfw/natd or something else? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello there! [ please keep CC'ing me ] I need to setup the following network: net A --+ | ------> ISP 1 v / (if1)GATEWAY(if2)------> ISP 2 ^ ^ \ | | ------> ISP n net B --+ | net C----------------+ ... While net A has normal network addresses; nets B,C have local addresses (like 10.0.0.0/8) and thus should diverted on a GATEWAY. Gateway has two network interfaces, and nets may be attached on both them. It should be possible to configure routing to specify which ISP each net is using, e.g. nets A and B should use ISP 1, while net C should use ISP2. I suppose the following: * having a natd running for each ISP we have * each natd is configured to use alias which is appropriate for given ISP (alias1, alias2) * allocate different ports for each ISP (as far as I understand, this is required by natd) (designated lower as port1, port2 etc) * the following rules in firewall ------------------------------------------------------------ fwd ISP1 all from (alias1) to any fwd ISP2 all from (alias2) to any .. divert (port1) all from (net B) to any via (if1) divert (port1) all from any to (alias1) via (if2) divert (port2) all from (net C) to any via (if2) divert (port2) all from any to (alias2) via (if2) .. ------------------------------------------------------------ Will this work? Am I missing something, or maybe there is less ugly way of setting up this? Regards, Alexey. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 2 0:57:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from molly.straylight.com (molly.straylight.com [209.68.199.242]) by hub.freebsd.org (Postfix) with ESMTP id 7290037B71B for ; Fri, 2 Mar 2001 00:57:11 -0800 (PST) (envelope-from jonathan@graehl.org) Received: from dickie (case.straylight.com [209.68.199.244]) by molly.straylight.com (8.11.0/8.10.0) with SMTP id f228vAJ01751 for ; Fri, 2 Mar 2001 00:57:10 -0800 From: "Jonathan Graehl" To: "Freebsd-Net" Subject: safety from EINTR Date: Fri, 2 Mar 2001 00:58:39 -0800 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.4522.1200 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If a UDP socket selects readable, am I assured that the next read call will not block? If a socket is nonblocking, can I use setitimer and handle SIGALRM, and be assured that the process will not be put to sleep waiting for I/O on the socket, thus returning EINTR due to the signal? -- Jonathan Graehl email: jonathan@graehl.org web: http://jonathan.graehl.org/ phone: 858-642-7562 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 2 1: 1:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id CBF5837B71A for ; Fri, 2 Mar 2001 01:01:23 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id f2291K369675; Fri, 2 Mar 2001 10:01:20 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.2/8.11.0) id f228js103315; Fri, 2 Mar 2001 09:45:54 +0100 (CET) (envelope-from asmodai) Date: Fri, 2 Mar 2001 09:45:53 +0100 From: Jeroen Ruigrok/Asmodai To: Hajimu UMEMOTO Cc: kirk@strauser.com, freebsd-net@freebsd.org Subject: Re: Freenet6, IPv6 tunnels, and rc.conf Message-ID: <20010302094553.A3038@daemon.ninth-circle.org> References: <87d7c3ewcc.fsf@pooh.honeypot> <20010302.011302.78721419.ume@mahoroba.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010302.011302.78721419.ume@mahoroba.org>; from ume@mahoroba.org on Fri, Mar 02, 2001 at 01:13:02AM +0900 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20010301 17:24], Hajimu UMEMOTO (ume@mahoroba.org) wrote: >>>>>> On 27 Feb 2001 13:53:39 -0600 >>>>>> Kirk Strauser said: >kirk> I want this machine to be a IPv6 gateway for the other machines >kirk> on my LAN, too. > >Since Freenet6 serve only one host address, it is impossible. If you >want to connect your LAN to 6bone, you need prefix assignment. UMEMOTO-san, I really need to get myself up to date on IPv6, but is it still possible to do NAT like stuff with IPv6 though? -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 2 3:19:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 4F09437B71D for ; Fri, 2 Mar 2001 03:19:35 -0800 (PST) (envelope-from brandt@fokus.gmd.de) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id MAA18466; Fri, 2 Mar 2001 12:19:28 +0100 (MET) Date: Fri, 2 Mar 2001 12:19:27 +0100 (CET) From: Harti Brandt To: Julian Elischer Cc: Marco Molteni , Subject: Re: How to implement a transport protocol with netgraph? (2) In-Reply-To: <3A9E597A.D3387FC2@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 1 Mar 2001, Julian Elischer wrote: JE>> MM>timers, buffers, retransmissions and friends. JE> JE>you can certainly do that in netgraph. JE>there are issues with locking in that a timer must not jump into a node while JE>the node is locked, but there is a method for doing that. I will be adding more JE>support for it so that it is easier to do. Add a small 'stub' function that does JE>nothing but call the 'real' timer function through the locking mechanism. From reading the man page or the articel I was under the impression, that the entire netgraph runs at splnet. So I thought I just do a splnet in the timer function and that's it. No problems on my UP machine so far :-) I'm wrong? harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.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 2 3:48:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 35C7037B71A for ; Fri, 2 Mar 2001 03:48:12 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id UAA12947; Fri, 2 Mar 2001 20:47:54 +0900 (JST) To: Jeroen Ruigrok/Asmodai Cc: Hajimu UMEMOTO , kirk@strauser.com, freebsd-net@freebsd.org In-reply-to: asmodai's message of Fri, 02 Mar 2001 09:45:53 +0100. <20010302094553.A3038@daemon.ninth-circle.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: Freenet6, IPv6 tunnels, and rc.conf From: itojun@iijlab.net Date: Fri, 02 Mar 2001 20:47:54 +0900 Message-ID: <12945.983533674@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I really need to get myself up to date on IPv6, but is it still possible >to do NAT like stuff with IPv6 though? you shouldn't need to. this is just a freenet6's restriction that it does not give you subnets instead of /128 host address. if you have a permanent IPv4 address, you may want to talk with other upstreams to establish permanent tunnel, and give you /48 address space. (64K subnets!) if you are using dynamic IP address assigned from upstream provider, maybe try to talk with freenet6 guys so that they'd give you subnets... itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 2 4:16:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 0CBFD37B71B for ; Fri, 2 Mar 2001 04:16:33 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 29264 invoked by uid 666); 2 Mar 2001 12:28:11 -0000 Received: from i087-141.nv.iinet.net.au (HELO elischer.org) (203.59.87.141) by mail.m.iinet.net.au with SMTP; 2 Mar 2001 12:28:11 -0000 Message-ID: <3A9F8F15.8DE2B815@elischer.org> Date: Fri, 02 Mar 2001 04:16:21 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Harti Brandt Cc: Marco Molteni , freebsd-net@FreeBSD.ORG Subject: Re: How to implement a transport protocol with netgraph? (2) References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Harti Brandt wrote: > > On Thu, 1 Mar 2001, Julian Elischer wrote: > > JE>> MM>timers, buffers, retransmissions and friends. > JE> > JE>you can certainly do that in netgraph. > JE>there are issues with locking in that a timer must not jump into a node while > JE>the node is locked, but there is a method for doing that. I will be adding more > JE>support for it so that it is easier to do. Add a small 'stub' function that does > JE>nothing but call the 'real' timer function through the locking mechanism. > > >From reading the man page or the articel I was under the impression, that > the entire netgraph runs at splnet. So I thought I just do a splnet in the > timer function and that's it. No problems on my UP machine so far :-) I'm > wrong? that is correct for -stable (4.x) for 5.x it will have to be different as there are no spl levels any more. I will have a function specifically for timeouts and timers but I haven't finished writing it yet. > > harti > -- > harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private > brandt@fokus.gmd.de, harti@begemot.org -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 2 8:37:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 32FE037B71E for ; Fri, 2 Mar 2001 08:37:08 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA14200; Fri, 2 Mar 2001 11:37:01 -0500 (EST) (envelope-from wollman) Date: Fri, 2 Mar 2001 11:37:01 -0500 (EST) From: Garrett Wollman Message-Id: <200103021637.LAA14200@khavrinen.lcs.mit.edu> To: Jeroen Ruigrok/Asmodai Cc: freebsd-net@FreeBSD.ORG Subject: Re: Freenet6, IPv6 tunnels, and rc.conf In-Reply-To: <20010302094553.A3038@daemon.ninth-circle.org> References: <87d7c3ewcc.fsf@pooh.honeypot> <20010302.011302.78721419.ume@mahoroba.org> <20010302094553.A3038@daemon.ninth-circle.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > I really need to get myself up to date on IPv6, but is it still possible > to do NAT like stuff with IPv6 though? It should not be necessary. 6to4 provides a convenient alternative that's available to anyone with an IPv4 address. One problem is the lack of reverse-mapping support in the DNS; our servers are configured to consider themselves authoritative for 2002:121a::/16 as a work-around. (Do a traceroute to lampang.ipv6.lcs.mit.edu to see how this works.) -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 2 8:38:29 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 9514B37B718 for ; Fri, 2 Mar 2001 08:38:27 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA14213; Fri, 2 Mar 2001 11:38:17 -0500 (EST) (envelope-from wollman) Date: Fri, 2 Mar 2001 11:38:17 -0500 (EST) From: Garrett Wollman Message-Id: <200103021638.LAA14213@khavrinen.lcs.mit.edu> To: "Jonathan Graehl" Cc: "Freebsd-Net" Subject: safety from EINTR In-Reply-To: References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > If a UDP socket selects readable, am I assured that the next read > call will not block? Not in the general case. If you can be certain that there is no other process with a file handle on the same socket, and considering blocking only due to socket buffer exhaustion, then that assumption *should* be valid. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 2 8:40:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from server1.manmail.norlight.net (server1.manmail.norlight.net [207.170.4.2]) by hub.freebsd.org (Postfix) with SMTP id 67A6337B71A for ; Fri, 2 Mar 2001 08:40:27 -0800 (PST) (envelope-from hyun@staff.norlight.net) Received: (qmail 31786 invoked from network); 2 Mar 2001 16:40:18 -0000 Received: from gw-app-eng.norlight.net (HELO staff.norlight.net) (207.170.1.30) by server1.manmail.norlight.net with SMTP; 2 Mar 2001 16:40:18 -0000 Message-ID: <3A9FCCF8.F05F4C3E@staff.norlight.net> Date: Fri, 02 Mar 2001 10:40:24 -0600 From: Hyunseog Ryu Organization: Norlight Telecommunications X-Mailer: Mozilla 4.72 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: BIND 9.1.1 and FBSD 4.2-stable Content-Type: multipart/mixed; boundary="------------271251D22325AA635DDF2B01" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------271251D22325AA635DDF2B01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, folks I have questions for BIND version 9.1.1rc2. I submitted original question to freebsd-isp@freebsd.org, but couldn't get an answer for this. Recently I installed BIND 9.1.1rc2 into one of FreeBSD 4.2-stable version. After installation of BIND, it works fine for a while. But when I look at the "top" command output, it says that memory consumption of named is increasing continuously. Yesterday I saw that named consumed more than 67MB memory. And today named suddenly stopped to respond. Do you guys have similar problem? > uname -a FreeBSD weiss.norlight.net 4.2-STABLE FreeBSD 4.2-STABLE #0: Mon Feb 19 18:35:06 CST 2001 root@test.norlight.net:/usr/src/sys/compile/weiss i386 > > top last pid: 43099; load averages: 0.22, 0.21, 0.17 up 9+05:05:33 18:10:51 26 processes: 1 running, 25 sleeping CPU states: 8.6% user, 0.0% nice, 2.7% system, 0.0% interrupt, 88.7% idle Mem: 35M Active, 22M Inact, 25M Wired, 5424K Cache, 22M Buf, 35M Free Swap: 256M Total, 1612K Used, 254M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 42818 dns 2 0 29472K 28528K poll 18:02 10.79% 10.79% named 43099 admin 28 0 1872K 1020K RUN 0:00 1.21% 0.44% top 81 root 2 0 916K 268K select 6:36 0.00% 0.00% syslogd 36216 admin 2 0 1884K 604K select 4:51 0.00% 0.00% top 114 root 2 0 2404K 588K select 3:20 0.00% 0.00% sshd 110 root 2 0 2496K 728K select 0:21 0.00% 0.00% sendmail 107 root 10 0 960K 236K nanslp 0:07 0.00% 0.00% cron 42846 root 2 0 2344K 1500K select 0:03 0.00% 0.00% ssh 42997 root 2 0 2436K 1532K select 0:01 0.00% 0.00% sshd I don't know what caused this problem. Please give me some idea to resolve this. Second, when named leaves syslog, timestamp looks like GMT. Not CST that we configured. Is there any way I can change this? Thanks for your help in advance. Best regards, Hyun --------------271251D22325AA635DDF2B01 Content-Type: text/x-vcard; charset=us-ascii; name="hyun.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Hyunseog Ryu Content-Disposition: attachment; filename="hyun.vcf" begin:vcard n:Ryu;Hyunseig tel;fax:262-792-7655 tel;work:262-792-7965 x-mozilla-html:FALSE org:Norlight Telecommunications;Applications Engineering adr:;;275 North Corporate Drive;Brookfield;WI;53045;USA version:2.1 email;internet:hyun@staff.norlight.net title:Network Engineer note:MCSE, CCDA fn:Hyunseig Ryu end:vcard --------------271251D22325AA635DDF2B01-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 2 9: 1: 1 2001 Delivered-To: freebsd-net@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id D5FBB37B71A for ; Fri, 2 Mar 2001 09:00:56 -0800 (PST) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:VhgXfNVtPYGXU16hbBx/vb8SHbTvtL1X2dFnpLO84TpBhWNuNJI/NeAR1we2ND3w@localhost [::1]) (authenticated as ume with CRAM-MD5) by peace.mahoroba.org (8.11.3/8.11.3/peace) with ESMTP/inet6 id f22Gvf312112; Sat, 3 Mar 2001 01:57:42 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sat, 03 Mar 2001 01:57:39 +0900 (JST) Message-Id: <20010303.015739.55481890.ume@mahoroba.org> To: itojun@iijlab.net Cc: asmodai@wxs.nl, kirk@strauser.com, freebsd-net@freebsd.org Subject: Re: Freenet6, IPv6 tunnels, and rc.conf From: Hajimu UMEMOTO In-Reply-To: <12945.983533674@coconut.itojun.org> References: <20010302094553.A3038@daemon.ninth-circle.org> <12945.983533674@coconut.itojun.org> X-Mailer: xcite1.38> Mew version 1.95b97 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> On Fri, 02 Mar 2001 20:47:54 +0900 >>>>> itojun@iijlab.net said: itojun> if you are using dynamic IP address assigned from upstream provider, itojun> maybe try to talk with freenet6 guys so that they'd give you itojun> subnets... Don't your ISP assign prefix using DTCP (Dynamic Tunnel Configuration Protocol)? I believe IIJ is good location. ;-) -- 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 Fri Mar 2 9: 2:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 5F83C37B71B for ; Fri, 2 Mar 2001 09:02:53 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14Yt7e-0000AT-00; Fri, 02 Mar 2001 10:13:42 -0700 Message-ID: <3A9FD4C6.230D7EB7@softweyr.com> Date: Fri, 02 Mar 2001 10:13:42 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Paulo Fragoso Cc: freebsd-net@freebsd.org Subject: Re: Deamon with perl References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Paulo Fragoso wrote: > > Hi, > > I've written a little server using perl, it's working fine using FBSD 4.x > but when I try with FBSD 3.x it don't work: > > bind: Can't assign requested address at ... > > I've ever changed all /usr/libdata/perl directory to same used on FBSD > 4.x, but I've got same error. > > Are there any problem with socket and perl on FBSD 3.x? Is your daemon trying to bind to a privileged port - i.e. port < 1024? If so, you're probably running suidperl on 4.x. You have to have root privs to bind to a port < 1024. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 2 9: 8:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 6788637B718 for ; Fri, 2 Mar 2001 09:08:24 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id CAA17172; Sat, 3 Mar 2001 02:08:07 +0900 (JST) To: Hajimu UMEMOTO Cc: asmodai@wxs.nl, kirk@strauser.com, freebsd-net@freebsd.org In-reply-to: ume's message of Sat, 03 Mar 2001 01:57:39 JST. <20010303.015739.55481890.ume@mahoroba.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: Freenet6, IPv6 tunnels, and rc.conf From: itojun@iijlab.net Date: Sat, 03 Mar 2001 02:08:07 +0900 Message-ID: <17170.983552887@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> if you are using dynamic IP address assigned from upstream provider, >> maybe try to talk with freenet6 guys so that they'd give you >> subnets... >Don't your ISP assign prefix using DTCP (Dynamic Tunnel Configuration >Protocol)? I believe IIJ is good location. ;-) I guess the operational cost is too high for us, and there are way too high possibility for abuse. you know, iijlab have only few people and they all are dead busy :-) itojun@I'm not speaking for my company. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 2 9:52:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with SMTP id 6299B37B71C for ; Fri, 2 Mar 2001 09:52:14 -0800 (PST) (envelope-from paulo@nlink.com.br) Received: (qmail 53283 invoked by uid 501); 2 Mar 2001 17:52:08 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 Mar 2001 17:52:08 -0000 Date: Fri, 2 Mar 2001 14:52:08 -0300 (EST) From: Paulo Fragoso To: Wes Peters Cc: freebsd-net@freebsd.org Subject: Re: Deamon with perl In-Reply-To: <3A9FD4C6.230D7EB7@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 2 Mar 2001, Wes Peters wrote: > Paulo Fragoso wrote: > > > > Hi, > > > > I've written a little server using perl, it's working fine using FBSD 4.x > > but when I try with FBSD 3.x it don't work: > > > > bind: Can't assign requested address at ... > > > > I've ever changed all /usr/libdata/perl directory to same used on FBSD > > 4.x, but I've got same error. > > > > Are there any problem with socket and perl on FBSD 3.x? > > Is your daemon trying to bind to a privileged port - i.e. port < 1024? > If so, you're probably running suidperl on 4.x. You have to have root > privs to bind to a port < 1024. No, it's trying to bind to a port > 1024. I've solved this problem changing this line in my code: $local_socket = sockaddr_in($port, inet_aton(INADDR_ANY) ); to $local_socket = sockaddr_in($port,INADDR_ANY ); now is working fine on FBSD 3.x. Thanks, Paulo. > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > wes@softweyr.com http://softweyr.com/ > -- __O _-\<,_ Why drive when you can bike? (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Mar 2 14: 5:37 2001 Delivered-To: freebsd-net@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 8667B37B718; Fri, 2 Mar 2001 14:05:32 -0800 (PST) (envelope-from DougB@gorean.org) Received: from slave (Studded@slave [10.0.0.1]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA30555; Fri, 2 Mar 2001 14:05:29 -0800 (PST) (envelope-from DougB@gorean.org) Date: Fri, 2 Mar 2001 14:05:28 -0800 (PST) From: Doug Barton X-X-Sender: To: Hyunseog Ryu Cc: , Subject: Re: BIND 9.1.1 and FBSD 4.2-stable In-Reply-To: <3A9FCCF8.F05F4C3E@staff.norlight.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 2 Mar 2001, Hyunseog Ryu wrote: > > Hi, folks > > I have questions for BIND version 9.1.1rc2. > I submitted original question to freebsd-isp@freebsd.org, > but couldn't get an answer for this. You're not getting answers because you are sending to the wrong lists. Your question belongs on freebsd-questions only. > Recently I installed BIND 9.1.1rc2 into one of FreeBSD 4.2-stable > version. Please update to rc3. It fixes several bugs, and may help your situation. > After installation of BIND, it works fine for a while. > But when I look at the "top" command output, > it says that memory consumption of named is increasing continuously. What are you doing with this named? Are you using it as a resolver? If so, it's normal for the size of the cache to grow. How much ram is it adding per day? You might also consider using/installing 8.2.3 and see if you get the same results. In any case, please respond to freebsd-questions@freebsd.org with your answer. Doug -- "Pain heals. Chicks dig scars. Glory . . . lasts forever." -- Keanu Reeves as Shane Falco in "The Replacements" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Mar 3 1:41:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 348AE37B71E for ; Sat, 3 Mar 2001 01:13:24 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14Z8HN-0000Dd-00; Sat, 03 Mar 2001 02:24:45 -0700 Message-ID: <3AA0B85D.72020281@softweyr.com> Date: Sat, 03 Mar 2001 02:24:45 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Paulo Fragoso Cc: freebsd-net@freebsd.org Subject: Re: Deamon with perl References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Paulo Fragoso wrote: > > On Fri, 2 Mar 2001, Wes Peters wrote: > > > Paulo Fragoso wrote: > > > > > > Hi, > > > > > > I've written a little server using perl, it's working fine using FBSD 4.x > > > but when I try with FBSD 3.x it don't work: > > > > > > bind: Can't assign requested address at ... > > > > > > I've ever changed all /usr/libdata/perl directory to same used on FBSD > > > 4.x, but I've got same error. > > > > > > Are there any problem with socket and perl on FBSD 3.x? > > > > Is your daemon trying to bind to a privileged port - i.e. port < 1024? > > If so, you're probably running suidperl on 4.x. You have to have root > > privs to bind to a port < 1024. > > No, it's trying to bind to a port > 1024. > > I've solved this problem changing this line in my code: > > $local_socket = sockaddr_in($port, inet_aton(INADDR_ANY) ); > > to > > $local_socket = sockaddr_in($port,INADDR_ANY ); > > now is working fine on FBSD 3.x. Ah. Ick. Perl. Bleh. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Mar 3 2:39: 2 2001 Delivered-To: freebsd-net@freebsd.org Received: from hotmail.com (f31.law4.hotmail.com [216.33.149.31]) by hub.freebsd.org (Postfix) with ESMTP id D227637B71B for ; Sat, 3 Mar 2001 02:39:00 -0800 (PST) (envelope-from guruchakravarthy@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 3 Mar 2001 02:39:00 -0800 Received: from 202.9.175.244 by lw4fd.law4.hotmail.msn.com with HTTP; Sat, 03 Mar 2001 10:39:00 GMT X-Originating-IP: [202.9.175.244] From: "guru chakravarthy" To: ilugc@aero.iitm.ernet.in, freebsd-net@FreeBSD.ORG, molter@tin.it, brandt@fokus.gmd.de Subject: how to implement TCP using RAW sockets Date: Sat, 03 Mar 2001 10:39:00 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 03 Mar 2001 10:39:00.0471 (UTC) FILETIME=[28841870:01C0A3CE] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hai As a final year UG project we are doing implementation of TCP with some modifications to it using IP Raw sockets in linux can any one show me some help pages where i can find help on Raw socket implementation and other details . Is there any such implementation help on the net . ? It would be of great help if u can do this . thanks guru _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Mar 3 3: 5:21 2001 Delivered-To: freebsd-net@freebsd.org Received: from molly.straylight.com (molly.straylight.com [209.68.199.242]) by hub.freebsd.org (Postfix) with ESMTP id 1040837B71A for ; Sat, 3 Mar 2001 02:02:52 -0800 (PST) (envelope-from jonathan@graehl.org) Received: from dickie (case.straylight.com [209.68.199.244]) by molly.straylight.com (8.11.0/8.10.0) with SMTP id f23A2ox11213 for ; Sat, 3 Mar 2001 02:02:50 -0800 From: "Jonathan Graehl" To: "Freebsd-Net" Subject: RE: Deamon with perl Date: Sat, 3 Mar 2001 02:04:22 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" 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.4522.1200 In-Reply-To: <3AA0B85D.72020281@softweyr.com> Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > $local_socket = sockaddr_in($port, inet_aton(INADDR_ANY) ); > > > > to > > > > $local_socket = sockaddr_in($port,INADDR_ANY ); > > > > now is working fine on FBSD 3.x. > > Ah. Ick. Perl. Bleh. He'd have the same problem in C (except that the compiler would catch it - INADDR_ANY is not a string, I guess that is your point?) -Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Mar 3 8:33:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id CC7D137B71E for ; Sat, 3 Mar 2001 08:33:06 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14ZF8c-0000L1-00; Sat, 03 Mar 2001 09:44:11 -0700 Message-ID: <3AA11F5A.E398BCB@softweyr.com> Date: Sat, 03 Mar 2001 09:44:10 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Jonathan Graehl Cc: Freebsd-Net Subject: Re: Deamon with perl References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jonathan Graehl wrote: > > > > $local_socket = sockaddr_in($port, inet_aton(INADDR_ANY) ); > > > > > > to > > > > > > $local_socket = sockaddr_in($port,INADDR_ANY ); > > > > > > now is working fine on FBSD 3.x. > > > > Ah. Ick. Perl. Bleh. > > He'd have the same problem in C (except that the compiler would catch it - > INADDR_ANY is not a string, I guess that is your point?) Yeah, it should either check the type or convert it appropriately: the C way, or the Python way. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Mar 3 9: 0:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.clickarray.com (clickwall.clickarray.com [216.132.92.2]) by hub.freebsd.org (Postfix) with ESMTP id 698AF37B718 for ; Sat, 3 Mar 2001 09:00:38 -0800 (PST) (envelope-from sshah@clickarray.com) Received: by mail.clickarray.com (Postfix, from userid 2000) id 90BF95EF09; Sat, 3 Mar 2001 09:07:13 -0800 (PST) Date: Sat, 3 Mar 2001 09:07:13 -0800 From: Steve Shah To: guru chakravarthy Cc: ilugc@aero.iitm.ernet.in, freebsd-net@FreeBSD.ORG, molter@tin.it, brandt@fokus.gmd.de Subject: Re: how to implement TCP using RAW sockets Message-ID: <20010303090713.A23571@clickarray.com> 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 guruchakravarthy@hotmail.com on Sat, Mar 03, 2001 at 10:39:00AM +0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Guru, Read the man pages on socket -- then follow the suggestions in "SEE ALSO" and read those man pages. Of course, getting a hold of Unix Network Programming 2nd Ed. (vol 1 is enough) will be immensely helpful. You may also want to look for some programs on the net that use raw sockets. If you are still having problems, you may want to try the linux-net list (linux-net@vger.rutgers.edu) since you are doing your work on linux. ;-) -Steve On Sat, Mar 03, 2001 at 10:39:00AM +0000, guru chakravarthy wrote: > As a final year UG project we are doing implementation of TCP with some > modifications to it using IP Raw sockets in linux can any one show me some > help pages where i can find help on Raw socket implementation and other > details . > Is there any such implementation help on the net . ? -- ______________________________________________________________________________ Steve Shah (sshah@clickarray.com) | Voice: 408.284.4226 Pager: 408.989.4247 http://www.clickarray.com | Pager E-Mail: pagesshah@clickarray.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Beating code into submission, one OS at a time... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Mar 3 11:25:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id BEDD837B722 for ; Sat, 3 Mar 2001 11:25:18 -0800 (PST) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.9.0/8.8.7) with ESMTP id TAA32675; Sat, 3 Mar 2001 19:25:17 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Sat, 3 Mar 2001 19:25:16 +0000 (GMT) From: "E.B. Dreger" To: guru chakravarthy Cc: freebsd-net@FreeBSD.ORG Subject: Re: how to implement TCP using RAW sockets In-Reply-To: <20010303090713.A23571@clickarray.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Read the man pages on socket -- then follow the suggestions > in "SEE ALSO" and read those man pages. Of course, getting a hold of > Unix Network Programming 2nd Ed. (vol 1 is enough) will be immensely > helpful. You may also want to look for some programs on the net that > use raw sockets. I suggest looking at 'nmap'. http://www.insecure.org/nmap/ It uses raw sockets, runs on many platforms, and is handy for probing [your own] machines for security purposes. > If you are still having problems, you may want to try the > linux-net list (linux-net@vger.rutgers.edu) since you are doing your > work on linux. ;-) Or, better yet, do the work on FreeBSD. ;-) Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division E-Mail: eddy@everquick.net Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message