From owner-freebsd-net Sun Jan 30 8:29:37 2000 Delivered-To: freebsd-net@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 4F2C414DC9; Sun, 30 Jan 2000 08:29:06 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id QAA05771; Sun, 30 Jan 2000 16:21:30 GMT (envelope-from n_hibma@webweaving.org) Date: Sun, 30 Jan 2000 16:21:29 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Donald Burr Cc: freebsd-net@FreeBSD.ORG, FreeBSD Hardware Subject: Re: Drivers for Davicom DM9102 10/100 NIC chip 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 If this is one of those USB only (USB keyboard, mouse, etc.) thingies you might want to be careful. I have not yet tried that and so far the only report I've had was that it did not work on an Acer. 1) there is a problem with ISA not being there I expect 2) Is the USB support amture enough to keep you going. Could you specify a location where one can find more information on this device? Cheers, Nick On Sat, 29 Jan 2000, Donald Burr wrote: > One of my suppliers has just started carrying a new item, called the > "BookPC", a really nice fully integrated PC (built in AGP video, USB, > 10/100 NIC, 56K modem, and AC97 audio) in an extremely small case > (even smaller than MicroATX). I'd like to buy a couple of these and turn > them into "tiny FreeBSD workstations". unfortunately, they use an > ethernet controller that is not supported. It is the Davicom DM9102 > (http://www.davicom8.com/lan/dm9102.htm). Fortunately it looks like this > company is pretty open-source friendly, there is a datasheet that you can > get right off the Web site, and there is even *source* for a Linux driver > (also available on the web site). > > It would be great if this chip were supported under > FreeBSD. Unfortunately, I lack the necessary mojo to pull this off. > > Any takers? Many thanks in advance! > -- > Donald Burr Resistance is Futile | FreeBSD: The > WWW: http://www.borg-cube.com/ ICQ: UIN#16997506 | Power to > Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | Serve! http:// > Phone: (805) 957-9666 FAX: (800) 492-5954 | www.freebsd.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 30 14:28: 7 2000 Delivered-To: freebsd-net@freebsd.org Received: from borg-cube.com (226-193.adsl2.avtel.net [207.71.226.193]) by hub.freebsd.org (Postfix) with ESMTP id 68EC214E0D; Sun, 30 Jan 2000 14:28:02 -0800 (PST) (envelope-from dburr@borg-cube.com) Received: from hugh.collective.borg-cube.com (IDENT:dburr@hugh.collective.borg-cube.com [192.168.0.6]) by borg-cube.com (8.9.3/8.9.3) with ESMTP id OAA09673; Sun, 30 Jan 2000 14:27:58 -0800 (PST) (envelope-from dburr@borg-cube.com) Date: Sun, 30 Jan 2000 06:28:38 -0800 (PST) From: Donald Burr To: Nick Hibma Cc: freebsd-net@FreeBSD.ORG, FreeBSD Hardware Subject: Re: Drivers for Davicom DM9102 10/100 NIC chip 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 Sun, 30 Jan 2000, Nick Hibma wrote: NH>If this is one of those USB only (USB keyboard, mouse, etc.) thingies NH>you might want to be careful. I have not yet tried that and so far the NH>only report I've had was that it did not work on an Acer. No, it has a PS/2 mouse and keyboard port. NH>1) there is a problem with ISA not being there I expect NH>2) Is the USB support amture enough to keep you going. NH>Could you specify a location where one can find more information on this NH>device? It is an extremely small (12"x11"x3.5") completely self contained PC. intel 810 chipset motherboard, socket 370 (celeron CPU), 2 x DIMM slots, room for a CD-ROM, hard drive, and floppy drive. No slots (everything is built in). 56K modem, 10/100 ethernet, USB, PS/2 mouse and keyboard, printer port, built in video, built in PCI AC97 sound card. I figure a stack of these will make a nice little FreeBSD cluster. Here are a couple of websites where you can see pictures of them, get more information, etc.: http://www.eastoncomputerworks.com/ecw/bookpc.htm http://www.arnoldco.com/bookpc/bookpc.html and here are some pictures of me assembling mine (I bought a "bare bones" unit without memory, CPU, or hard drive, since I have some spare components lying around) http://www.borg-cube.com/pix/hugh/ -- Donald Burr Resistance is Futile | FreeBSD: The WWW: http://www.borg-cube.com/ ICQ: UIN#16997506 | Power to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | Serve! http:// Phone: (805) 957-9666 FAX: (800) 492-5954 | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 30 14:50:57 2000 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 61E601529D for ; Sun, 30 Jan 2000 14:50:55 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id OAA97566; Sun, 30 Jan 2000 14:50:13 -0800 (PST) From: Archie Cobbs Message-Id: <200001302250.OAA97566@bubba.whistle.com> Subject: Re: netgraph documentation? In-Reply-To: <14481.1066.490661.673416@trooper.velocet.net> from David Gilbert at "Jan 27, 2000 09:51:22 pm" To: dgilbert@velocet.ca (David Gilbert) Date: Sun, 30 Jan 2000 14:50:13 -0800 (PST) Cc: julian_elischer@yahoo.com (Julian Elischer), kbyanc@posi.net (Kelly Yancey), freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 David Gilbert writes: > ng_pptpgre appears to be at least part of the protocol that I need to > speak, but some of the documentation implies that this intended to > work with a future work that will implement the rest of the rest of > the protocol. > > Now the current ng_pppoe works with the current pppd... and the > question arises if this pppd is capable of working with ng_pptpgre. Right now, the ng_pptpgre(8) netgraph module is only used by the net/mpd-netgraph port. Eventually ppp(8) may also support it. You should be able to have a working PPTP client or server using mpd, albeit without MPPE encryption. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 30 15:33:19 2000 Delivered-To: freebsd-net@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 3D4A714FFB; Sun, 30 Jan 2000 15:33:13 -0800 (PST) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id RAA22043; Sun, 30 Jan 2000 17:32:55 -0600 (CST) Date: Sun, 30 Jan 2000 17:32:54 -0600 From: Tim Tsai To: Donald Burr Cc: Nick Hibma , freebsd-net@FreeBSD.ORG, FreeBSD Hardware Subject: Re: Drivers for Davicom DM9102 10/100 NIC chip Message-ID: <20000130173254.A21957@futuresouth.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We've used one of these for awhile (I brought one back from Taiwan a few months ago). It makes a nice compact size workstation but the TV output is really pretty crappy. I wouldn't get it to connect to the TV. Tim On Sun, Jan 30, 2000 at 06:28:38AM -0800, Donald Burr wrote: > On Sun, 30 Jan 2000, Nick Hibma wrote: > > NH>If this is one of those USB only (USB keyboard, mouse, etc.) thingies > NH>you might want to be careful. I have not yet tried that and so far the > NH>only report I've had was that it did not work on an Acer. > > No, it has a PS/2 mouse and keyboard port. > > NH>1) there is a problem with ISA not being there I expect > NH>2) Is the USB support amture enough to keep you going. > NH>Could you specify a location where one can find more information on this > NH>device? > > It is an extremely small (12"x11"x3.5") completely self contained PC. > intel 810 chipset motherboard, socket 370 (celeron CPU), 2 x DIMM slots, > room for a CD-ROM, hard drive, and floppy drive. No slots (everything is > built in). 56K modem, 10/100 ethernet, USB, PS/2 mouse and keyboard, > printer port, built in video, built in PCI AC97 sound card. I figure a > stack of these will make a nice little FreeBSD cluster. > > Here are a couple of websites where you can see pictures of them, get more > information, etc.: > > http://www.eastoncomputerworks.com/ecw/bookpc.htm > http://www.arnoldco.com/bookpc/bookpc.html > > and here are some pictures of me assembling mine (I bought a "bare bones" > unit without memory, CPU, or hard drive, since I have some spare > components lying around) > > http://www.borg-cube.com/pix/hugh/ > -- > Donald Burr Resistance is Futile | FreeBSD: The > WWW: http://www.borg-cube.com/ ICQ: UIN#16997506 | Power to > Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | Serve! http:// > Phone: (805) 957-9666 FAX: (800) 492-5954 | www.freebsd.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 30 19:37:32 2000 Delivered-To: freebsd-net@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 383DC14F85 for ; Sun, 30 Jan 2000 19:37:30 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 88526137FB6; Sun, 30 Jan 2000 22:37:21 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id WAA37899; Sun, 30 Jan 2000 22:37:31 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14485.890.587777.715364@trooper.velocet.net> Date: Sun, 30 Jan 2000 22:37:30 -0500 (EST) To: Archie Cobbs Cc: dgilbert@velocet.ca (David Gilbert), julian_elischer@yahoo.com (Julian Elischer), kbyanc@posi.net (Kelly Yancey), freebsd-net@FreeBSD.ORG Subject: Re: netgraph documentation? In-Reply-To: <200001302250.OAA97566@bubba.whistle.com> References: <14481.1066.490661.673416@trooper.velocet.net> <200001302250.OAA97566@bubba.whistle.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Archie" == Archie Cobbs writes: Archie> David Gilbert writes: >> ng_pptpgre appears to be at least part of the protocol that I need >> to speak, but some of the documentation implies that this intended >> to work with a future work that will implement the rest of the rest >> of the protocol. >> >> Now the current ng_pppoe works with the current pppd... and the >> question arises if this pppd is capable of working with ng_pptpgre. Archie> Right now, the ng_pptpgre(8) netgraph module is only used by Archie> the net/mpd-netgraph port. Eventually ppp(8) may also support Archie> it. Archie> You should be able to have a working PPTP client or server Archie> using mpd, albeit without MPPE encryption. What resources might need to come to bear to bring this to fruition? Moreover, how great is this distance? I don't have a complete grasp of the network protocols involved, but I do have a budget and a desire. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 30 21:42:30 2000 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 6DF8214F03 for ; Sun, 30 Jan 2000 21:42:28 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id VAA98787; Sun, 30 Jan 2000 21:40:36 -0800 (PST) From: Archie Cobbs Message-Id: <200001310540.VAA98787@bubba.whistle.com> Subject: Re: netgraph documentation? In-Reply-To: <14485.890.587777.715364@trooper.velocet.net> from David Gilbert at "Jan 30, 2000 10:37:30 pm" To: dgilbert@velocet.ca (David Gilbert) Date: Sun, 30 Jan 2000 21:40:36 -0800 (PST) Cc: archie@whistle.com (Archie Cobbs), julian_elischer@yahoo.com (Julian Elischer), kbyanc@posi.net (Kelly Yancey), freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 David Gilbert writes: > Archie> Right now, the ng_pptpgre(8) netgraph module is only used by > Archie> the net/mpd-netgraph port. Eventually ppp(8) may also support > Archie> it. > > Archie> You should be able to have a working PPTP client or server > Archie> using mpd, albeit without MPPE encryption. > > What resources might need to come to bear to bring this to fruition? > Moreover, how great is this distance? Which 'distance' are you referring to? Mpd works now, without MPPE. Adding MPPE is easy, but held back by the ususal crypto crap... the netgraph and mpd parts are done, you just need to add a couple of easy-to-find files in /usr/src/sys/crypto (rc4.c and rc4.h). As for ppp(8) and netgraph and/or PPTP, you'd have to ask brian@freebsd.org. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 31 3:55:33 2000 Delivered-To: freebsd-net@freebsd.org Received: from zirafe.carrier.kiev.ua (sivka.carrier.kiev.ua [193.193.193.101]) by hub.freebsd.org (Postfix) with ESMTP id 2787F14A20 for ; Mon, 31 Jan 2000 03:55:27 -0800 (PST) (envelope-from samj@itcj.kiev.ua) Received: from mails.itci.kiev.ua (gw1.itci.kiev.ua [62.244.54.196]) by zirafe.carrier.kiev.ua (8.Who.Cares/Kilkenny_is_better) with ESMTP id NVH40921 for ; Mon, 31 Jan 2000 13:55:18 +0200 (EET) (envelope-from samj@itcj.kiev.ua) Received: from itcj.kiev.ua (primsrv.itci.kiev.ua [62.244.54.220]) by mails.itci.kiev.ua (8.8.8/8.8.8) with ESMTP id NAA01474 for ; Mon, 31 Jan 2000 13:53:03 +0200 (EET) (envelope-from samj@itcj.kiev.ua) Message-ID: <38957815.19F257FA@itcj.kiev.ua> Date: Mon, 31 Jan 2000 13:55:01 +0200 From: Yuriy Samartsev X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: Compile failed with mdp-2.0b2 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have compile failed during with error: msoft.c:16:des.h: No such file or directory I have try with 2.2.7 Release and 3.01 Release. Can anybody help me? Thanks in advance. Yuriy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 31 9:30: 5 2000 Delivered-To: freebsd-net@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id A6A7814EC9; Mon, 31 Jan 2000 09:30:01 -0800 (PST) (envelope-from T.Pagtzis@cs.ucl.ac.uk) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Mon, 31 Jan 2000 17:29:44 +0000 X-Mailer: exmh version 2.0.2 To: freebsd-net@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: NFS and removable disks Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Jan 2000 17:29:43 +0000 Message-ID: <1268.949339783@cs.ucl.ac.uk> From: Theo PAGTZIS Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I have the following problem. I have moved my disk with Fbsd 3.3 onto a diff machine with exactly the same network interface on both machines de0. However when I am trying to do mount on the machines NFS responds with NFS Portmap: RPC: Port mapper failure - RPC: Timed out When I ask people what does NFS depend on between client and servers I get the response of only IP address. So since the IP address is the same I am puzzled as to why there is port map failure. Could anyone enlighten on the reason of why this happens? BTW when I ping the ping works ok as well as telnet does Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 31 10: 2:17 2000 Delivered-To: freebsd-net@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id E676914A16; Mon, 31 Jan 2000 10:02:10 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 840C7137FC0; Mon, 31 Jan 2000 13:02:08 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id NAA56406; Mon, 31 Jan 2000 13:02:19 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14485.52778.650233.910218@trooper.velocet.net> Date: Mon, 31 Jan 2000 13:02:18 -0500 (EST) To: Archie Cobbs Cc: dgilbert@velocet.ca (David Gilbert), julian_elischer@yahoo.com (Julian Elischer), kbyanc@posi.net (Kelly Yancey), freebsd-net@FreeBSD.ORG, brian@FreeBSD.ORG Subject: Re: netgraph documentation? In-Reply-To: <200001310540.VAA98787@bubba.whistle.com> References: <14485.890.587777.715364@trooper.velocet.net> <200001310540.VAA98787@bubba.whistle.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Archie" == Archie Cobbs writes: Archie> David Gilbert writes: Right now, the ng_pptpgre(8) netgraph >> What resources might need to come to bear to bring this to >> fruition? Moreover, how great is this distance? Archie> Which 'distance' are you referring to? Mpd works now, without Archie> MPPE. Adding MPPE is easy, but held back by the ususal crypto Archie> crap... the netgraph and mpd parts are done, you just need to Archie> add a couple of easy-to-find files in /usr/src/sys/crypto Archie> (rc4.c and rc4.h). Archie> As for ppp(8) and netgraph and/or PPTP, you'd have to ask Archie> brian@freebsd.org. Well... I see lots of talk about pptp and then some discussion of l2tp --- and the Bell tech is telling me they're differrent... the mpe-netgraph stuff appears to claim that it supports pptp, not l2tp. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 31 10:34:34 2000 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id A2EB914E9C; Mon, 31 Jan 2000 10:34:30 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id KAA01451; Mon, 31 Jan 2000 10:33:43 -0800 (PST) From: Archie Cobbs Message-Id: <200001311833.KAA01451@bubba.whistle.com> Subject: Re: netgraph documentation? In-Reply-To: <14485.52778.650233.910218@trooper.velocet.net> from David Gilbert at "Jan 31, 2000 01:02:18 pm" To: dgilbert@velocet.ca (David Gilbert) Date: Mon, 31 Jan 2000 10:33:43 -0800 (PST) Cc: archie@whistle.com (Archie Cobbs), julian_elischer@yahoo.com (Julian Elischer), kbyanc@posi.net (Kelly Yancey), freebsd-net@FreeBSD.ORG, brian@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 David Gilbert writes: > >> What resources might need to come to bear to bring this to > >> fruition? Moreover, how great is this distance? > > Archie> Which 'distance' are you referring to? Mpd works now, without > Archie> MPPE. Adding MPPE is easy, but held back by the ususal crypto > Archie> crap... the netgraph and mpd parts are done, you just need to > Archie> add a couple of easy-to-find files in /usr/src/sys/crypto > Archie> (rc4.c and rc4.h). > > Archie> As for ppp(8) and netgraph and/or PPTP, you'd have to ask > Archie> brian@freebsd.org. > > Well... I see lots of talk about pptp and then some discussion of l2tp > --- and the Bell tech is telling me they're differrent... the > mpe-netgraph stuff appears to claim that it supports pptp, not l2tp. Right.. PPTP and L2TP are different things. Mpd only supports PPTP at this point. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 31 10:52:35 2000 Delivered-To: freebsd-net@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 46E4614FB1; Mon, 31 Jan 2000 10:52:33 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id D6039137F6D; Mon, 31 Jan 2000 13:52:24 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id NAA57587; Mon, 31 Jan 2000 13:52:27 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14485.55786.748236.209806@trooper.velocet.net> Date: Mon, 31 Jan 2000 13:52:26 -0500 (EST) To: Archie Cobbs Cc: dgilbert@velocet.ca (David Gilbert), julian_elischer@yahoo.com (Julian Elischer), kbyanc@posi.net (Kelly Yancey), freebsd-net@FreeBSD.ORG, brian@FreeBSD.ORG Subject: Re: netgraph documentation? In-Reply-To: <200001311833.KAA01451@bubba.whistle.com> References: <14485.52778.650233.910218@trooper.velocet.net> <200001311833.KAA01451@bubba.whistle.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Archie" == Archie Cobbs writes: Archie> Right.. PPTP and L2TP are different things. Mpd only supports Archie> PPTP at this point. Well... this is what I wanted to know --- what is the distance between the two. How much effort needs be mustered to close that gap? Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 31 11:39: 0 2000 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 8FB8F15048; Mon, 31 Jan 2000 11:38:57 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id LAA01724; Mon, 31 Jan 2000 11:37:54 -0800 (PST) From: Archie Cobbs Message-Id: <200001311937.LAA01724@bubba.whistle.com> Subject: Re: netgraph documentation? In-Reply-To: <14485.55786.748236.209806@trooper.velocet.net> from David Gilbert at "Jan 31, 2000 01:52:26 pm" To: dgilbert@velocet.ca (David Gilbert) Date: Mon, 31 Jan 2000 11:37:54 -0800 (PST) Cc: archie@whistle.com (Archie Cobbs), julian_elischer@yahoo.com (Julian Elischer), kbyanc@posi.net (Kelly Yancey), freebsd-net@FreeBSD.ORG, brian@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 David Gilbert writes: > Archie> Right.. PPTP and L2TP are different things. Mpd only supports > Archie> PPTP at this point. > > Well... this is what I wanted to know --- what is the distance > between the two. How much effort needs be mustered to close that gap? They are somewhat similar, since L2TP evovled from PPTP (and L2F). However, I believe they are sufficiently different that it would take a fair amount of work to write a L2TP server from a PPTP server. I haven't read the L2TP spec in detail yet though. The way mpd works right now, it treats PPTP as just another physical layer type, like modem or netgraph node. So perhaps L2TP could be implemented in the same fashion.. ? I think ppp(8) has a similar device abstraction layer too. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 31 12:35:14 2000 Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id F2F8314C05; Mon, 31 Jan 2000 12:35:05 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 31 Jan 2000 20:35:03 +0000 (GMT) Date: Mon, 31 Jan 2000 20:35:02 +0000 From: David Malone To: Theo PAGTZIS Cc: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: NFS and removable disks Message-ID: <20000131203502.A61674@walton.maths.tcd.ie> References: <1268.949339783@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <1268.949339783@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Mon, Jan 31, 2000 at 05:29:43PM +0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jan 31, 2000 at 05:29:43PM +0000, Theo PAGTZIS wrote: > NFS Portmap: RPC: Port mapper failure - RPC: Timed out Check you've enableld the portmapper on the server in rc.conf. (Or check it's running "ps -auxwww | fgrep portmap"). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 31 23:15:40 2000 Delivered-To: freebsd-net@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by builder.freebsd.org (Postfix) with ESMTP id 259AA3D25 for ; Mon, 31 Jan 2000 23:15:35 -0800 (PST) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id VAA19282; Mon, 31 Jan 2000 21:10:24 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp.simianscience.com (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id VAA24372; Mon, 31 Jan 2000 21:10:20 -0500 (EST) From: mike@sentex.net (Mike Tancsa) To: archie@whistle.com (Archie Cobbs) Cc: freebsd-net@freebsd.org Subject: Re: netgraph documentation? Date: Tue, 01 Feb 2000 02:09:06 GMT Message-ID: <38963f7f.337386886@mail.sentex.net> References: <14485.55786.748236.209806@trooper.velocet.net> In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 31 Jan 2000 14:40:20 -0500, in sentex.lists.freebsd.net you wrote: >David Gilbert writes: >> Archie> Right.. PPTP and L2TP are different things. Mpd only supports >> Archie> PPTP at this point. >> >> Well... this is what I wanted to know --- what is the distance >> between the two. How much effort needs be mustered to close that gap? > >They are somewhat similar, since L2TP evovled from PPTP (and L2F). >However, I believe they are sufficiently different that it would >take a fair amount of work to write a L2TP server from a PPTP server. >I haven't read the L2TP spec in detail yet though. > >The way mpd works right now, it treats PPTP as just another physical >layer type, like modem or netgraph node. So perhaps L2TP could be >implemented in the same fashion.. ? > >I think ppp(8) has a similar device abstraction layer too. There is a daemon with source code available at http://www.marko.net/l2tp/ There is a bit of work to be done on it according to the readme. ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 1 2:50:50 2000 Delivered-To: freebsd-net@freebsd.org Received: from mc-qout4.whowhere.com (mc-qout4.whowhere.com [209.185.123.18]) by builder.freebsd.org (Postfix) with SMTP id 5C4C13DA3 for ; Tue, 1 Feb 2000 02:50:48 -0800 (PST) Received: from Unknown/Local ([?.?.?.?]) by my-deja.com; Tue Feb 1 02:50:15 2000 To: freebsd-net@FreeBSD.ORG Date: Tue, 01 Feb 2000 02:50:15 -0800 From: "gbnaidu " Message-ID: Mime-Version: 1.0 X-Sent-Mail: off X-Mailer: MailCity Service Subject: some problem with my mails... X-Sender-Ip: 164.164.56.2 Organization: My Deja Email (http://www.my-deja.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Length: 1269 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I am sorry if I am not supposed to post this question on this list. I need help from those who are able to post questions to this list. I have subscribed to this list under the address gbnaidu@sasi.com I have been receiving mails from the list. But what ever questions I am trying to post to the list, they are bouncing back. I have checked the major domo server by finding whether I am subscribed or not. Here is the results of it: Can somebody help me out whether do I neeed to do anything more to subscribe to this list? please reply to list and cc it to gbnaidu@sasi.com regards --gb -------------------------------------- Date: Tue, 1 Feb 2000 02:38:43 -0800 (PST) From: Majordomo@FreeBSD.ORG To: gbnaidu@sasi.com Subject: Majordomo results -- >>>> which NOTE: the "which" command does not show subscriptions to either freebsd-arch or freebsd-security-notifications The string 'gbnaidu@sasi.com' appears in the following entries in lists served by Majordomo@FreeBSfreebsd-net gbnaidu@sasi.com >>>> >>>> >>>> >>>>D.ORG: List Address ==== ======= --== Sent via Deja.com http://www.deja.com/ ==-- Share what you know. Learn what you don't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 1 2:59:48 2000 Delivered-To: freebsd-net@freebsd.org Received: from mc-qout4.whowhere.com (mc-qout4.whowhere.com [209.185.123.18]) by builder.freebsd.org (Postfix) with SMTP id 53F763DA4 for ; Tue, 1 Feb 2000 02:59:46 -0800 (PST) Received: from Unknown/Local ([?.?.?.?]) by my-deja.com; Tue Feb 1 02:59:13 2000 To: freebsd-net@FreeBSD.ORG Date: Tue, 01 Feb 2000 02:59:13 -0800 From: "gbnaidu " Message-ID: Mime-Version: 1.0 X-Sent-Mail: off X-Mailer: MailCity Service Subject: please see my earlier mail... X-Sender-Ip: 164.164.56.2 Organization: My Deja Email (http://www.my-deja.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Length: 664 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Here is the results from the major domo server: Date: Tue, 1 Feb 2000 02:38:43 -0800 (PST) From: Majordomo@FreeBSD.ORG To: gbnaidu@sasi.com Subject: Majordomo results -- >>>> which NOTE: the "which" command does not show subscriptions to either freebsd-arch or freebsd-security-notifications The string 'gbnaidu@sasi.com' appears in the following entries in lists served by Majordomo@FreeBSD.ORG: List Address ==== ======= freebsd-net gbnaidu@sasi.com >>>> >>>> >>>> >>>> --== Sent via Deja.com http://www.deja.com/ ==-- Share what you know. Learn what you don't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 1 7:26:57 2000 Delivered-To: freebsd-net@freebsd.org Received: from isis.uniandes.edu.co (isis.uniandes.edu.co [157.253.54.5]) by builder.freebsd.org (Postfix) with ESMTP id B62523E03 for ; Tue, 1 Feb 2000 07:25:57 -0800 (PST) Received: from isis.uniandes.edu.co (isis.uniandes.edu.co [157.253.54.5]) by isis.uniandes.edu.co (8.9.3/8.9.3) with SMTP id KAA05650 for ; Tue, 1 Feb 2000 10:22:22 -0500 (GMT+5) Date: Tue, 1 Feb 2000 10:22:22 -0500 (GMT+5) From: Yonny Cardenas Baron To: freebsd-net@FreeBSD.org Subject: Theme for thesis with 4.4BSD (FreeBSD) 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; I am an student of a M.Sc. in Computer Science, I am looking a theme for my thesis and I would like to work on networking with 4.4BSD (FreeBSD). I am not an expert but I have studied Unix for some time now, and I use FreeBSD too. I would like suggestions to make a contribution to the project. Thanks in advance for any ideas. +------------------------------------------------------------------+ | YONNY CARDENAS B. Apartado Aereo 22828 | | Systems Engineer Santafe de Bogota D.C. | | Colombia - South America | | Student M.Sc. Tels: +571 2929451 +571 2929493 | | UNIVERSIDAD DE LOS ANDES mailto: y-carden@uniandes.edu.co | | ycardena@yahoo.com | +------------------------------------------------------------------+ UNIX is BSD, and FreeBSD is an advanced 4.4BSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 1 16:40: 9 2000 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by builder.freebsd.org (Postfix) with ESMTP id 6495F3FBD for ; Tue, 1 Feb 2000 16:40:04 -0800 (PST) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id QAA73837; Tue, 1 Feb 2000 16:39:10 -0800 (PST) From: Archie Cobbs Message-Id: <200002020039.QAA73837@bubba.whistle.com> Subject: Re: Compile failed with mdp-2.0b2 In-Reply-To: <38957815.19F257FA@itcj.kiev.ua> from Yuriy Samartsev at "Jan 31, 2000 01:55:01 pm" To: samj@itcj.kiev.ua (Yuriy Samartsev) Date: Tue, 1 Feb 2000 16:39:10 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Yuriy Samartsev writes: > I have compile failed during with error: > msoft.c:16:des.h: No such file or directory > I have try with 2.2.7 Release and 3.01 Release. > Can anybody help me? You don't have the security stuff installed.. Just turn off the ENCRYPTION_DES option in the Makefile and try compiling again. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.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 1 21:49:26 2000 Delivered-To: freebsd-net@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id 054393DD7 for ; Tue, 1 Feb 2000 21:49:23 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA38871 for freebsd-net@FreeBSD.ORG; Tue, 1 Feb 2000 22:48:59 -0700 (MST) (envelope-from ken) Date: Tue, 1 Feb 2000 22:48:59 -0700 From: "Kenneth D. Merry" To: freebsd-net@FreeBSD.ORG Subject: anyone know about 802.3x flow control? Message-ID: <20000201224859.A38780@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got an Intel 410T standalone switch for my home network: http://www.intel.com/network/products/exp410t.htm I've got four machines hooked to it, which have: Card Speed Driver no-name DEC 21140A 100Mbps, full duplex de SMC 8216 10Mbps, half duplex ed Intel 82559 100Mbps, full duplex fxp HP JetDirect 100Mbps, full duplex (it's a printer) Everything works fine, but I noticed something odd on the machine with the Intel ethernet board tonight. It was getting tons of packets every second (several screens full) from the switch. The packets looked like this in tcpdump: 22:15:53.313742 0:0:0:0:0:10 1:80:c2:0:0:1 8808 60: 0001 0000 0000 8808 0001 0000 0000 8808 0001 0000 0000 8808 0001 0000 0000 8808 0001 0000 0000 8808 0001 0000 0000 22:15:53.355673 0:0:0:0:0:10 1:80:c2:0:0:1 8808 60: 0001 0000 0000 8808 0001 0000 0000 8808 0001 0000 0000 8808 0001 0000 0000 8808 0001 0000 0000 8808 0001 0000 0000 The last octet of the source hardware address changes based on what port in the switch I'm plugged into. (It's in port 10 now. If I plug it into say port 11, it'll be 0x20, 12, 0x30, and so on.) I ran tcpdump on the other two FreeBSD boxes (with the SMC and DEC cards), and didn't notice any packets like that. So my guess was that it must be some autonegotiated parameter between the switch and the card that caused that to happen. So I went into the switch configuration menu (via the serial port) and disabled flow control on port 10. The packets above stopped. Now, occasionally (once every minute or two, maybe?) I get packets like this: 22:40:13.958917 ff:ff:ff:ff:0:90 2:0:0:0:ff:ff 27d1 322: 7776 0800 4500 0130 cf09 0000 4011 95b3 0a00 0002 0a00 00ff 0201 0201 011c 4e86 0101 0000 3897 c33d 0000 0000 7061 6e7a 6572 0000 0000 I assume the above storm of packets was due to the "IEEE 802.3x standards-based flow control." that the switch supports, but what I don't understand is why the packets kept coming. Is this something that the card is supposed to intercept somehow and deal with, or is it something that the OS is supposed to intercept and deal with? I'd guess the latter, but I'd like to know more about it, and perhaps why my switch kept spewing. (Naturally, Intel's web site didn't have much helpful information that I could find.) Anyone know anything about this? Thanks, Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 1 21:58:47 2000 Delivered-To: freebsd-net@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id D664C3DD2 for ; Tue, 1 Feb 2000 21:58:42 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA39055 for freebsd-net@FreeBSD.ORG; Tue, 1 Feb 2000 22:58:22 -0700 (MST) (envelope-from ken) Date: Tue, 1 Feb 2000 22:58:22 -0700 From: "Kenneth D. Merry" To: freebsd-net@FreeBSD.ORG Subject: Re: anyone know about 802.3x flow control? Message-ID: <20000201225822.A39005@panzer.kdm.org> References: <20000201224859.A38780@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000201224859.A38780@panzer.kdm.org>; from ken@kdm.org on Tue, Feb 01, 2000 at 10:48:59PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Feb 01, 2000 at 22:48:59 -0700, Kenneth D. Merry wrote: [ ... ] > Everything works fine, but I noticed something odd on the machine with > the Intel ethernet board tonight. It was getting tons of packets every > second (several screens full) from the switch. > > The packets looked like this in tcpdump: > > 22:15:53.313742 0:0:0:0:0:10 1:80:c2:0:0:1 8808 60: > 0001 0000 0000 8808 0001 0000 0000 8808 > 0001 0000 0000 8808 0001 0000 0000 8808 > 0001 0000 0000 8808 0001 0000 0000 > 22:15:53.355673 0:0:0:0:0:10 1:80:c2:0:0:1 8808 60: > 0001 0000 0000 8808 0001 0000 0000 8808 > 0001 0000 0000 8808 0001 0000 0000 8808 > 0001 0000 0000 8808 0001 0000 0000 > > The last octet of the source hardware address changes based on what port in > the switch I'm plugged into. (It's in port 10 now. If I plug it into say > port 11, it'll be 0x20, 12, 0x30, and so on.) > > I ran tcpdump on the other two FreeBSD boxes (with the SMC and DEC cards), > and didn't notice any packets like that. So my guess was that it must be > some autonegotiated parameter between the switch and the card that caused > that to happen. > > So I went into the switch configuration menu (via the serial port) and > disabled flow control on port 10. The packets above stopped. Now, > occasionally (once every minute or two, maybe?) I get packets like this: [ ... ] One other note on this -- when I disable flow control, throughput with netperf (ports/benchmarks/netperf) is horrible. With the default sysctl parameters (16K socket buffers, no rfc1323), I can normally get 65Mbps or so between the Pentium box with the 21140A and the Pentium Pro with the i82559. Without flow control, however, I only get at most 1.5Mbps. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 1 22:45:36 2000 Delivered-To: freebsd-net@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by builder.freebsd.org (Postfix) with ESMTP id 842023E50 for ; Tue, 1 Feb 2000 22:45:33 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id BAA28972 for ; Wed, 2 Feb 2000 01:45:28 -0500 Date: Wed, 2 Feb 2000 01:45:28 -0500 (EST) From: Mike Nowlin To: freebsd-net@freebsd.org Subject: 802.1Q VLANs 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 What's the current status of 802.1Q VLAN support in -STABLE? I'm rapidly heading towards an impass -- FreeBSD, or Cisco? :) I saw a few messages about this about 4-6 weeks ago, and they kind of died after that -- last mod date of /usr/src/sys/net/*vlan* is Dec. 27 on my test box..... If the decision is that FBSD is NOT "really ready" to support the 802.1Q stuff now, I'll buy the $3K Cisco router (and associated cards & "Plus" software packages), then start working on the support so I don't have to buy the 2nd & 3rd routers in about three months... :) I could do the routing with multiple NICs in the FBSD box, but with the way I have to break apart this network, I'm going to run out of PCI slots pretty quickly.... Input? Thanks - Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 1 23:18:13 2000 Delivered-To: freebsd-net@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by builder.freebsd.org (Postfix) with ESMTP id 4D3CC3E39; Tue, 1 Feb 2000 23:18:11 -0800 (PST) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA77806; Tue, 1 Feb 2000 23:18:08 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 1 Feb 2000 23:18:07 -0800 (PST) From: Kris Kennaway To: Yonny Cardenas Baron Cc: freebsd-net@FreeBSD.org Subject: Re: Theme for thesis with 4.4BSD (FreeBSD) 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, 1 Feb 2000, Yonny Cardenas Baron wrote: > I am an student of a M.Sc. in Computer Science, I am looking a theme for > my thesis and I would like to work on networking with 4.4BSD (FreeBSD). > > I am not an expert but I have studied Unix for some time now, and I use > FreeBSD too. I would like suggestions to make a contribution to the > project. One thing I'd really like to see is a port of the MIT Exokernel packet filtering (DPF) code to FreeBSD. There's lots of potential for research in this area, and it would be darn useful too :-) I have never looked at the code in depth, so I don't know how tied it is to the other parts of the exokernel, but it's worth at least a look. See http://www.pdos.lcs.mit.edu/exo/ for more.. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 0:26:11 2000 Delivered-To: freebsd-net@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by builder.freebsd.org (Postfix) with ESMTP id EC6363E1C; Wed, 2 Feb 2000 00:26:09 -0800 (PST) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id AAA91012; Wed, 2 Feb 2000 00:26:07 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 2 Feb 2000 00:26:07 -0800 (PST) From: Kris Kennaway To: Yuriy Samartsev Cc: freebsd-net@FreeBSD.ORG Subject: Re: Compile failed with mdp-2.0b2 In-Reply-To: <38957815.19F257FA@itcj.kiev.ua> 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, 31 Jan 2000, Yuriy Samartsev wrote: > I have compile failed during with error: > msoft.c:16:des.h: No such file or directory > I have try with 2.2.7 Release and 3.01 Release. > Can anybody help me? Install the FreeBSD crypto sources through /stand/sysinstall, cvsup, or whatever you normally use. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 10:40:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from amalthea.salford.ac.uk (amalthea.salford.ac.uk [146.87.255.61]) by builder.freebsd.org (Postfix) with SMTP id EF6D2410A for ; Wed, 2 Feb 2000 10:40:31 -0800 (PST) Received: (qmail 23326 invoked by alias); 2 Feb 2000 18:34:56 -0000 Received: (qmail 23320 invoked from network); 2 Feb 2000 18:34:56 -0000 Received: from plato.salford.ac.uk (146.87.255.76) by amalthea.salford.ac.uk with SMTP; 2 Feb 2000 18:34:56 -0000 Received: (qmail 22683 invoked by uid 141); 2 Feb 2000 18:34:55 -0000 Date: Wed, 2 Feb 2000 18:34:55 +0000 (GMT) From: Mark Powell To: freebsd-net@freebsd.org Subject: Can 3.4-S cope with packets not addressed to 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 We want to force the use of our web caches. Our boundary router is a 3Com NetBuilder II, which we can get to forward port 80 traffic to another IP address. However, it does not rewrite the destination IP address in the IP header. Thus the machine has to be directly connected to the router to actually get the packets. What I'm wondering, is can FreeBSD cope with this? Will it be able to process these packets, with an IP address that is not it's own, at all or is this a non-starter? I suppose if it can then a more elegant solution to our caching needs can be found. We have two caches and would ideally like to spread this forwarded traffic across them. Could a 3rd FreeBSD box be plugged directly into the router and selectively forward packets to both servers? This would enable load balancing of this enforced traffic. Thanks for any help, as it's the first time I've even attempted anything like this. I'm assuming that ipfw or ipfilter will be what I want, but I have little experience of them. Cheers. Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@ais.salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 10:48:10 2000 Delivered-To: freebsd-net@freebsd.org Received: from redbox.venux.net (redbox.venux.net [216.47.238.10]) by builder.freebsd.org (Postfix) with ESMTP id B937240AC for ; Wed, 2 Feb 2000 10:48:07 -0800 (PST) Received: from thunder (net4842.hcv.com [216.93.48.42]) by redbox.venux.net (Postfix) with ESMTP id ED74E2E20B for ; Wed, 2 Feb 2000 13:35:59 -0500 (EST) Message-Id: <4.2.2.20000202134145.00c7a850@dns.venux.net> X-Sender: mhagerty@dns.venux.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 02 Feb 2000 13:45:02 -0500 To: freebsd-net@FreeBSD.ORG From: Matthew Hagerty Subject: IPFW with NATd 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 Greetings, I hope this is the proper place to post this. If not, please excuse me and kindly point me to the proper list. I tried the IPFW list but I think I'm the only one subscribed. I am running NATd and IPFW on FreeBSD-3.4-Release as a dual-homed packet filter gateway for my internal network (assigned 10.0.0.0) and a perimeter network with real IP assignment. I was wondering if it is possible to split the divert rule of IPFW so that I can have my rules apply to the internal addresses? The initial IPFW rule, when NATd is used, is the first one in the list, like this (from rc.firewall): $fwcmd add divert natd all from any to any via ${natd_interface} From what I understand of the man page, this hands all packets to NATd for translation prior to the rest of the rules. So my IPFW rules will only see the external (real) IP address for all hosts on the internal network. I.e. if host 10.0.0.10 tries to send a packet, the first IPFW rule is the divert which will change the address to the external IP, so the only address I have to work with in the IPFW rules is the real external IP. What I would like to be able to do is have rules that I can base on the internal IP addresses. I started to experiment with this a little, this is what I tried: $fwcmd add divert natd all from ${onet}:${omask} to any in via ${oif} . . . IPFW rules here have both sets of IP addresses, real addresses and fake to work with. . . . $fwcmd add divert natd all from ${inet}:${imask} to any out via ${oif} So in essence the incoming packets from the real world get sent through NATd prior to the rules and outgoing packets from the internal network get sent through NATd last, after the rules. This (I was hoping) would allow me to make rules based on certain internal hosts, i.e. my internal DNS host needs to talk to my external fake DNS on the bastion host, but no other internal host should be allowed to query the external DNS (bastion) host directly, unless a rule is written specifically for it. I did actually get this to work with the DNS example, my fake DNS on the external network could communicate with the internal DNS and vice-versa. But when I tried to add a rule to allow the rest of the internal hosts to surf, etc. it broke. The only error I got was a "can't send packet back" error on the terminal. Any insight on this would be greatly appreciated. Thanks, Matthew Hagerty To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 10:49:19 2000 Delivered-To: freebsd-net@freebsd.org Received: from www.geocrawler.com (sourceforge.net [198.186.203.33]) by builder.freebsd.org (Postfix) with ESMTP id D74DD4072 for ; Wed, 2 Feb 2000 10:49:16 -0800 (PST) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id KAA09144; Wed, 2 Feb 2000 10:46:04 -0800 Date: Wed, 2 Feb 2000 10:46:04 -0800 Message-Id: <200002021846.KAA09144@www.geocrawler.com> To: freebsd-net@freebsd.org Subject: help PPPoE From: "miv" Reply-To: "miv" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message was sent from Geocrawler.com by "miv" Be sure to reply to that address. i cant seem to get ppp to even to connect i get this error when i start up ppp No default entry found in config file. ppp [350]: Warning: Bad rule in /etc/ppp/ppp.conf (line 9) -missing colon ppp [350]: Warning: Bad rule in /etc/ppp/ppp.conf (line 10) - missing colon. it goes on and on till (line 24)- missing clon. what does this mean? and what am i doing wrong. please HELP!! THANK you Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 10:54:17 2000 Delivered-To: freebsd-net@freebsd.org Received: from www.geocrawler.com (sourceforge.net [198.186.203.33]) by builder.freebsd.org (Postfix) with ESMTP id 151F8410E for ; Wed, 2 Feb 2000 10:54:14 -0800 (PST) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id KAA09478; Wed, 2 Feb 2000 10:49:45 -0800 Date: Wed, 2 Feb 2000 10:49:45 -0800 Message-Id: <200002021849.KAA09478@www.geocrawler.com> To: freebsd-net@freebsd.org Subject: FreeBSD and PPPoE From: "Nassar Carnegie" Reply-To: "Nassar Carnegie" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message was sent from Geocrawler.com by "Nassar Carnegie" Be sure to reply to that address. Will FreeBSD support PPPoE in the near future or is someone working on it?... I have xDSL with Bellsouth and a Efficient Networks 3060 ADSL modem.. Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 11:48:15 2000 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by builder.freebsd.org (Postfix) with ESMTP id 5E8C33DD7 for ; Wed, 2 Feb 2000 11:48:08 -0800 (PST) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id UAA06935; Wed, 2 Feb 2000 20:48:46 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200002021948.UAA06935@info.iet.unipi.it> Subject: Re: Can 3.4-S cope with packets not addressed to it? In-Reply-To: from Mark Powell at "Feb 2, 2000 06:34:55 pm" To: Mark Powell Date: Wed, 2 Feb 2000 20:48:46 +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 > We want to force the use of our web caches. Our boundary router is a 3Com > NetBuilder II, which we can get to forward port 80 traffic to another IP > address. However, it does not rewrite the destination IP address in the IP you mean in the reply ? because otherwise how can it forward the traffic to another address! cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 11:59:28 2000 Delivered-To: freebsd-net@freebsd.org Received: from stingray.ivision.co.uk (avengers.ivision.co.uk [195.50.91.40]) by builder.freebsd.org (Postfix) with ESMTP id 3177B40F3 for ; Wed, 2 Feb 2000 11:59:02 -0800 (PST) Received: from stingray.ivision.co.uk ([195.50.91.40]) by stingray.ivision.co.uk with esmtp (Exim 2.04 #1) id 12G5uy-0003xh-00; Wed, 2 Feb 2000 19:58:24 +0000 Date: Wed, 2 Feb 2000 19:58:24 +0000 (BST) From: Jasper Wallace To: Mike Nowlin Cc: freebsd-net@freebsd.org Subject: Re: 802.1Q VLANs In-Reply-To: Message-ID: X-NCC-RegID: uk.instant-web 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, 2 Feb 2000, Mike Nowlin wrote: > > What's the current status of 802.1Q VLAN support in -STABLE? I'm rapidly > heading towards an impass -- FreeBSD, or Cisco? :) I saw a few messages > about this about 4-6 weeks ago, and they kind of died after that -- last > mod date of /usr/src/sys/net/*vlan* is Dec. 27 on my test box..... > > If the decision is that FBSD is NOT "really ready" to support the 802.1Q > stuff now, I'll buy the $3K Cisco router (and associated cards & "Plus" > software packages), then start working on the support so I don't have to > buy the 2nd & 3rd routers in about three months... :) I could do the > routing with multiple NICs in the FBSD box, but with the way I have to > break apart this network, I'm going to run out of PCI slots pretty > quickly.... We are using the vlan patches from: http://www.euitt.upm.es/~pjlobo/fbsdvlan.html quite happily - they only work with fxp's tho, and don't do proper interface statistics reporting... -- Internet Vision Internet Consultancy Tel: 0171 589 4500 60 Albert Court & Web development Fax: 0171 589 4522 Prince Consort Road vision@ivision.co.uk London SW7 2BE http://www.ivision.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 12:28:20 2000 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by builder.freebsd.org (Postfix) with ESMTP id 058634138 for ; Wed, 2 Feb 2000 12:28:16 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id PAA40659; Wed, 2 Feb 2000 15:28:03 -0500 (EST) Date: Wed, 2 Feb 2000 15:28:02 -0500 (EST) From: "Matthew N. Dodd" To: Jasper Wallace Cc: Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs 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, 2 Feb 2000, Jasper Wallace wrote: > We are using the vlan patches from: > > http://www.euitt.upm.es/~pjlobo/fbsdvlan.html > > quite happily - they only work with fxp's tho, and don't do proper interface > statistics reporting... ifconfig in both -STABLE and -CURRENT has support for setting up vlan devices. ifconfig vlanX vlan N vlandev foo0 ... I've got a switch that supports vlans and have tested the code by configuring vlan devices on 2 machine and pinging. It works enough for that but there are unrelated bugs in the network driver I'm using that have prevented further testing. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 12:31:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from stingray.ivision.co.uk (avengers.ivision.co.uk [195.50.91.40]) by builder.freebsd.org (Postfix) with ESMTP id CB22A4186 for ; Wed, 2 Feb 2000 12:31:35 -0800 (PST) Received: from stingray.ivision.co.uk ([195.50.91.40]) by stingray.ivision.co.uk with esmtp (Exim 2.04 #1) id 12G6Qe-0004Gt-00; Wed, 2 Feb 2000 20:31:08 +0000 Date: Wed, 2 Feb 2000 20:31:08 +0000 (BST) From: Jasper Wallace To: "Matthew N. Dodd" Cc: Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: Message-ID: X-NCC-RegID: uk.instant-web 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, 2 Feb 2000, Matthew N. Dodd wrote: > On Wed, 2 Feb 2000, Jasper Wallace wrote: > > We are using the vlan patches from: > > > > http://www.euitt.upm.es/~pjlobo/fbsdvlan.html > > > > quite happily - they only work with fxp's tho, and don't do proper interface > > statistics reporting... > > ifconfig in both -STABLE and -CURRENT has support for setting up vlan > devices. > > ifconfig vlanX vlan N vlandev foo0 ... yeah, i don't bother with vlanconfig - it's the kernal patches that matter. > I've got a switch that supports vlans and have tested the code by > configuring vlan devices on 2 machine and pinging. It works enough for > that but there are unrelated bugs in the network driver I'm using that > have prevented further testing. oh well, with the vlan code in -stable i could ping, but tcp or udp packets would eventually panic the machine, it's fine with the patches from the above url. -- Internet Vision Internet Consultancy Tel: 0171 589 4500 60 Albert Court & Web development Fax: 0171 589 4522 Prince Consort Road vision@ivision.co.uk London SW7 2BE http://www.ivision.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 12:34:16 2000 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by builder.freebsd.org (Postfix) with ESMTP id A7DB04190 for ; Wed, 2 Feb 2000 12:33:48 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id PAA40727; Wed, 2 Feb 2000 15:33:35 -0500 (EST) Date: Wed, 2 Feb 2000 15:33:35 -0500 (EST) From: "Matthew N. Dodd" To: Jasper Wallace Cc: Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs 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, 2 Feb 2000, Jasper Wallace wrote: > oh well, with the vlan code in -stable i could ping, but tcp or udp > packets would eventually panic the machine, it's fine with the patches > from the above url. Humm... That sounds like whats happening to me. I suspected the network driver since I've had other issues with it. I'll take a look at the patches tonite. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 13:14:26 2000 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by builder.freebsd.org (Postfix) with ESMTP id 30A144163 for ; Wed, 2 Feb 2000 13:14:20 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id QAA41294; Wed, 2 Feb 2000 16:13:48 -0500 (EST) Date: Wed, 2 Feb 2000 16:13:48 -0500 (EST) From: "Matthew N. Dodd" To: Jasper Wallace Cc: Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs 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, 2 Feb 2000, Jasper Wallace wrote: > oh well, with the vlan code in -stable i could ping, but tcp or udp > packets would eventually panic the machine, it's fine with the patches > from the above url. Does the kernel patch work with any other adapters? I'm not sure I see the need to patch if_fxp. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 15:50: 9 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-51.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.179]) by builder.freebsd.org (Postfix) with ESMTP id 916F04331 for ; Wed, 2 Feb 2000 15:50:05 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA63300; Wed, 2 Feb 2000 23:50:08 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA03408; Wed, 2 Feb 2000 23:50:12 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002022350.XAA03408@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "miv" Cc: freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: help PPPoE In-Reply-To: Message from "miv" of "Wed, 02 Feb 2000 10:46:04 PST." <200002021846.KAA09144@www.geocrawler.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Feb 2000 23:50:12 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This message was sent from Geocrawler.com by "miv" > Be sure to reply to that address. > > i cant seem to get ppp to even to connect > i get this error when i start up ppp > > No default entry found in config file. > ppp [350]: Warning: Bad rule in /etc/ppp/ppp.conf > (line 9) -missing colon > ppp [350]: Warning: Bad rule in /etc/ppp/ppp.conf > (line 10) - missing colon. > > it goes on and on till (line 24)- missing clon. > what does this mean? and what am i doing wrong. > please HELP!! > > THANK you I don't wish to be rude, but how to you expect anyone to help you with syntax errors in a configuration file if you haven't attached the file ? It means what it says, there are missing colons in the file. Please re-read the man page and look at the examples in /usr/share/examples/ppp. If you still have problems, please repost the question with your ppp.conf file. > Geocrawler.com - The Knowledge Archive -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 15:51:21 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-51.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.179]) by builder.freebsd.org (Postfix) with ESMTP id ADCE94123 for ; Wed, 2 Feb 2000 15:51:18 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA63304; Wed, 2 Feb 2000 23:51:21 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA03423; Wed, 2 Feb 2000 23:51:25 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002022351.XAA03423@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Nassar Carnegie" Cc: freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: FreeBSD and PPPoE In-Reply-To: Message from "Nassar Carnegie" of "Wed, 02 Feb 2000 10:49:45 PST." <200002021849.KAA09478@www.geocrawler.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Feb 2000 23:51:25 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This message was sent from Geocrawler.com by "Nassar Carnegie" > Be sure to reply to that address. > > Will FreeBSD support PPPoE in the near future or is someone working on it?... > > I have xDSL with Bellsouth and a Efficient Networks 3060 ADSL modem.. I take it you haven't read the manual page then ? > Geocrawler.com - The Knowledge Archive -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 2 17:53:32 2000 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by builder.freebsd.org (Postfix) with ESMTP id 624F4422A for ; Wed, 2 Feb 2000 17:53:22 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id UAA44045; Wed, 2 Feb 2000 20:53:09 -0500 (EST) Date: Wed, 2 Feb 2000 20:53:09 -0500 (EST) From: "Matthew N. Dodd" To: Jasper Wallace Cc: Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1845923715-949542789=:479" 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-1845923715-949542789=:479 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 2 Feb 2000, Jasper Wallace wrote: > oh well, with the vlan code in -stable i could ping, but tcp or udp packets > would eventually panic the machine, it's fine with the patches from the > above url. Ok, I've reviewed the patches (crap) and fixed the problem (easy). I'm not terribly happy with how the double queuing ends up working but its much better than polluting sys/net/if_ethersubr.c with all sorts of VLAN defines. The correct solution will be to write a vlan_output() routine that does the right thing so we can place packets right on the parent interface's queue instead of calling ether_output twice. I'm not inclined to do this so close to release so the brief patch will have to do. Patch follows: Index: if_vlan.c =================================================================== RCS file: /cvs/src/sys/net/if_vlan.c,v retrieving revision 1.13 diff -u -1 -2 -r1.13 if_vlan.c --- if_vlan.c 2000/01/29 16:56:24 1.13 +++ if_vlan.c 2000/02/02 22:36:55 @@ -184,25 +184,25 @@ static void vlan_ifinit(void *foo) { return; } static void vlan_start(struct ifnet *ifp) { struct ifvlan *ifv; struct ifnet *p; struct ether_vlan_header *evl; - struct mbuf *m; + struct mbuf *m, *m0; ifv = ifp->if_softc; p = ifv->ifv_p; ifp->if_flags |= IFF_OACTIVE; for (;;) { IF_DEQUEUE(&ifp->if_snd, m); if (m == 0) break; if (ifp->if_bpf) bpf_mtap(ifp, m); @@ -220,27 +220,39 @@ * valid. We need to do this because sometimes mbufs will * be allocated by other parts of the system that contain * garbage in the rcvif pointer. Using the M_PROTO1 flag * lets the driver perform a proper sanity check and avoid * following potentially bogus rcvif pointers off into * never-never land. */ if (ifp->if_flags & IFF_LINK0) { m->m_pkthdr.rcvif = ifp; m->m_flags |= M_PROTO1; } else { M_PREPEND(m, EVL_ENCAPLEN, M_DONTWAIT); - if (m == 0) + if (m == NULL) { + printf("vlan%d: M_PREPEND failed", ifp->if_unit ); + ifp->if_ierrors++; continue; + } /* M_PREPEND takes care of m_len, m_pkthdr.len for us */ + + m0 = m_pullup(m, ETHER_HDR_LEN + EVL_ENCAPLEN); + if (m0 == NULL) { + printf("vlan%d: m_pullup failed", ifp->if_unit ); + ifp->if_ierrors++; + m_freem(m); + continue; + } + m = m0; /* * Transform the Ethernet header into an Ethernet header * with 802.1Q encapsulation. */ bcopy(mtod(m, char *) + EVL_ENCAPLEN, mtod(m, char *), sizeof(struct ether_header)); evl = mtod(m, struct ether_vlan_header *); evl->evl_proto = evl->evl_encap_proto; evl->evl_encap_proto = htons(vlan_proto); evl->evl_tag = htons(ifv->ifv_tag); #ifdef DEBUG -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | --0-1845923715-949542789=:479 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="if_vlan.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="if_vlan.patch" SW5kZXg6IGlmX3ZsYW4uYw0KPT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KUkNT IGZpbGU6IC9jdnMvc3JjL3N5cy9uZXQvaWZfdmxhbi5jLHYNCnJldHJpZXZp bmcgcmV2aXNpb24gMS4xMw0KZGlmZiAtdSAtMSAtMiAtcjEuMTMgaWZfdmxh bi5jDQotLS0gaWZfdmxhbi5jCTIwMDAvMDEvMjkgMTY6NTY6MjQJMS4xMw0K KysrIGlmX3ZsYW4uYwkyMDAwLzAyLzAyIDIyOjM2OjU1DQpAQCAtMTg0LDI1 ICsxODQsMjUgQEANCiBzdGF0aWMgdm9pZA0KIHZsYW5faWZpbml0KHZvaWQg KmZvbykNCiB7DQogCXJldHVybjsNCiB9DQogDQogc3RhdGljIHZvaWQNCiB2 bGFuX3N0YXJ0KHN0cnVjdCBpZm5ldCAqaWZwKQ0KIHsNCiAJc3RydWN0IGlm dmxhbiAqaWZ2Ow0KIAlzdHJ1Y3QgaWZuZXQgKnA7DQogCXN0cnVjdCBldGhl cl92bGFuX2hlYWRlciAqZXZsOw0KLQlzdHJ1Y3QgbWJ1ZiAqbTsNCisJc3Ry dWN0IG1idWYgKm0sICptMDsNCiANCiAJaWZ2ID0gaWZwLT5pZl9zb2Z0YzsN CiAJcCA9IGlmdi0+aWZ2X3A7DQogDQogCWlmcC0+aWZfZmxhZ3MgfD0gSUZG X09BQ1RJVkU7DQogCWZvciAoOzspIHsNCiAJCUlGX0RFUVVFVUUoJmlmcC0+ aWZfc25kLCBtKTsNCiAJCWlmIChtID09IDApDQogCQkJYnJlYWs7DQogCQlp ZiAoaWZwLT5pZl9icGYpDQogCQkJYnBmX210YXAoaWZwLCBtKTsNCiANCkBA IC0yMjAsMjcgKzIyMCwzOSBAQA0KIAkJICogdmFsaWQuIFdlIG5lZWQgdG8g ZG8gdGhpcyBiZWNhdXNlIHNvbWV0aW1lcyBtYnVmcyB3aWxsDQogCQkgKiBi ZSBhbGxvY2F0ZWQgYnkgb3RoZXIgcGFydHMgb2YgdGhlIHN5c3RlbSB0aGF0 IGNvbnRhaW4NCiAJCSAqIGdhcmJhZ2UgaW4gdGhlIHJjdmlmIHBvaW50ZXIu IFVzaW5nIHRoZSBNX1BST1RPMSBmbGFnDQogCQkgKiBsZXRzIHRoZSBkcml2 ZXIgcGVyZm9ybSBhIHByb3BlciBzYW5pdHkgY2hlY2sgYW5kIGF2b2lkDQog CQkgKiBmb2xsb3dpbmcgcG90ZW50aWFsbHkgYm9ndXMgcmN2aWYgcG9pbnRl cnMgb2ZmIGludG8NCiAJCSAqIG5ldmVyLW5ldmVyIGxhbmQuDQogCQkgKi8N CiAJCWlmIChpZnAtPmlmX2ZsYWdzICYgSUZGX0xJTkswKSB7DQogCQkJbS0+ bV9wa3RoZHIucmN2aWYgPSBpZnA7DQogCQkJbS0+bV9mbGFncyB8PSBNX1BS T1RPMTsNCiAJCX0gZWxzZSB7DQogCQkJTV9QUkVQRU5EKG0sIEVWTF9FTkNB UExFTiwgTV9ET05UV0FJVCk7DQotCQkJaWYgKG0gPT0gMCkNCisJCQlpZiAo bSA9PSBOVUxMKSB7DQorCQkJCXByaW50ZigidmxhbiVkOiBNX1BSRVBFTkQg ZmFpbGVkIiwgaWZwLT5pZl91bml0ICk7DQorCQkJCWlmcC0+aWZfaWVycm9y cysrOw0KIAkJCQljb250aW51ZTsNCisJCQl9DQogCQkJLyogTV9QUkVQRU5E IHRha2VzIGNhcmUgb2YgbV9sZW4sIG1fcGt0aGRyLmxlbiBmb3IgdXMgKi8N CisNCisJCQltMCA9IG1fcHVsbHVwKG0sIEVUSEVSX0hEUl9MRU4gKyBFVkxf RU5DQVBMRU4pOw0KKwkJCWlmIChtMCA9PSBOVUxMKSB7DQorCQkJCXByaW50 ZigidmxhbiVkOiBtX3B1bGx1cCBmYWlsZWQiLCBpZnAtPmlmX3VuaXQgKTsN CisJCQkJaWZwLT5pZl9pZXJyb3JzKys7DQorCQkJCW1fZnJlZW0obSk7DQor CQkJCWNvbnRpbnVlOw0KKwkJCX0NCisJCQltID0gbTA7DQogDQogCQkJLyoN CiAJCQkgKiBUcmFuc2Zvcm0gdGhlIEV0aGVybmV0IGhlYWRlciBpbnRvIGFu IEV0aGVybmV0IGhlYWRlcg0KIAkJCSAqIHdpdGggODAyLjFRIGVuY2Fwc3Vs YXRpb24uDQogCQkJICovDQogCQkJYmNvcHkobXRvZChtLCBjaGFyICopICsg RVZMX0VOQ0FQTEVOLCBtdG9kKG0sIGNoYXIgKiksDQogCQkJICAgICAgc2l6 ZW9mKHN0cnVjdCBldGhlcl9oZWFkZXIpKTsNCiAJCQlldmwgPSBtdG9kKG0s IHN0cnVjdCBldGhlcl92bGFuX2hlYWRlciAqKTsNCiAJCQlldmwtPmV2bF9w cm90byA9IGV2bC0+ZXZsX2VuY2FwX3Byb3RvOw0KIAkJCWV2bC0+ZXZsX2Vu Y2FwX3Byb3RvID0gaHRvbnModmxhbl9wcm90byk7DQogCQkJZXZsLT5ldmxf dGFnID0gaHRvbnMoaWZ2LT5pZnZfdGFnKTsNCiAjaWZkZWYgREVCVUcNCg== --0-1845923715-949542789=:479-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 1:24:18 2000 Delivered-To: freebsd-net@freebsd.org Received: from amalthea.salford.ac.uk (amalthea.salford.ac.uk [146.87.255.61]) by builder.freebsd.org (Postfix) with SMTP id E00B94390 for ; Thu, 3 Feb 2000 01:24:14 -0800 (PST) Received: (qmail 11207 invoked by alias); 3 Feb 2000 09:24:16 -0000 Received: (qmail 11193 invoked from network); 3 Feb 2000 09:24:15 -0000 Received: from plato.salford.ac.uk (146.87.255.76) by amalthea.salford.ac.uk with SMTP; 3 Feb 2000 09:24:15 -0000 Received: (qmail 26346 invoked by uid 141); 3 Feb 2000 09:24:14 -0000 Date: Thu, 3 Feb 2000 09:24:14 +0000 (GMT) From: Mark Powell To: Wim Livens Cc: freebsd-net@freebsd.org Subject: Re: Can 3.4-S cope with packets not addressed to it? In-Reply-To: <20000203100939.A290@rc.bel.alcatel.be> 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, 3 Feb 2000, Wim Livens wrote: > On Wed, Feb 02, 2000 at 06:34:55PM +0000, Mark Powell wrote: > > We want to force the use of our web caches. Our boundary router is a 3Com > > NetBuilder II, which we can get to forward port 80 traffic to another IP > > address. However, it does not rewrite the destination IP address in the IP > > header. Thus the machine has to be directly connected to the router to > > actually get the packets. > > What I'm wondering, is can FreeBSD cope with this? Will it be able to > > process these packets, with an IP address that is not it's own, at all or > > maybe this helps: > ifconfig ... alias Hmmm. Hadn't though of that. Now how many web servers are there in the world. Could you provide a list and I'll start setting the aliases up. Seriously, is there any way to get FreeBSD to accept any IP packets? Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@ais.salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 1:32:38 2000 Delivered-To: freebsd-net@freebsd.org Received: from zirafe.carrier.kiev.ua (sivka.carrier.kiev.ua [193.193.193.101]) by builder.freebsd.org (Postfix) with ESMTP id ECC984342 for ; Thu, 3 Feb 2000 01:32:29 -0800 (PST) Received: from mails.itci.kiev.ua (gw1.itci.kiev.ua [62.244.54.196]) by zirafe.carrier.kiev.ua (8.Who.Cares/Kilkenny_is_better) with ESMTP id LMM64348 for ; Thu, 3 Feb 2000 11:32:26 +0200 (EET) (envelope-from samj@itcj.kiev.ua) Received: from primsrv (primsrv.itci.kiev.ua [62.244.54.220]) by mails.itci.kiev.ua (8.8.8/8.8.8) with ESMTP id LAA03852 for ; Thu, 3 Feb 2000 11:30:16 +0200 (EET) (envelope-from samj@itcj.kiev.ua) Message-Id: <200002030930.LAA03852@mails.itci.kiev.ua> From: "Yuriy" To: Subject: PPP do not break connection Date: Thu, 3 Feb 2000 11:32:16 +0200 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sometimes my ppp process do not break connection after the user hang up modem. Process ppp -direct go on without end until I kill it. Why? What I have to do ? Any ideas. Thanks on advance. _______ Yuriy Samartsev, Firm ITC Ltd, http://www.itci.net. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 1:47:58 2000 Delivered-To: freebsd-net@freebsd.org Received: from tilion.sgn.sca.se (tilion.sgn.sca.se [195.124.135.5]) by builder.freebsd.org (Postfix) with ESMTP id B9FB14340 for ; Thu, 3 Feb 2000 01:47:53 -0800 (PST) Received: from hygiene.sca.se ([10.80.9.236]) by tilion.sgn.sca.se (8.9.3/8.9.3) with ESMTP id KAA15794 for ; Thu, 3 Feb 2000 10:47:55 +0100 (CET) Message-ID: <38994E0F.5C662774@hygiene.sca.se> Date: Thu, 03 Feb 2000 10:44:47 +0100 From: =?iso-8859-1?Q?Edstr=F6m?= Johan Organization: SCA IT Services X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: Re: Can 3.4-S cope with packets not addressed to it? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Isn't transparent proxying close to what you look for? there's a FAQ at squid if you wish to use that. /JE Mark Powell wrote: > > On Thu, 3 Feb 2000, Wim Livens wrote: > > On Wed, Feb 02, 2000 at 06:34:55PM +0000, Mark Powell wrote: > > > We want to force the use of our web caches. Our boundary router is a 3Com > > > NetBuilder II, which we can get to forward port 80 traffic to another IP > > > address. However, it does not rewrite the destination IP address in the IP > > > header. Thus the machine has to be directly connected to the router to > > > actually get the packets. > > > What I'm wondering, is can FreeBSD cope with this? Will it be able to > > > process these packets, with an IP address that is not it's own, at all or > > > > maybe this helps: > > ifconfig ... alias > > Hmmm. Hadn't though of that. Now how many web servers are there in the > world. Could you provide a list and I'll start setting the aliases up. > Seriously, is there any way to get FreeBSD to accept any IP packets? > > Mark Powell - UNIX System Administrator - Clifford Whitworth Building > A.I.S., University of Salford, Salford, Manchester, UK. > Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key > M.S.Powell@ais.salfrd.ac.uk (spell salford correctly to reply to me) > > 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 Thu Feb 3 1:52:22 2000 Delivered-To: freebsd-net@freebsd.org Received: from amalthea.salford.ac.uk (amalthea.salford.ac.uk [146.87.255.61]) by builder.freebsd.org (Postfix) with SMTP id 64ECB432C for ; Thu, 3 Feb 2000 01:52:14 -0800 (PST) Received: (qmail 28651 invoked by alias); 3 Feb 2000 09:52:20 -0000 Received: (qmail 28644 invoked from network); 3 Feb 2000 09:52:19 -0000 Received: from plato.salford.ac.uk (146.87.255.76) by amalthea.salford.ac.uk with SMTP; 3 Feb 2000 09:52:19 -0000 Received: (qmail 26433 invoked by uid 141); 3 Feb 2000 09:52:19 -0000 Date: Thu, 3 Feb 2000 09:52:19 +0000 (GMT) From: Mark Powell To: Luigi Rizzo Cc: freebsd-net@FreeBSD.ORG Subject: Re: Can 3.4-S cope with packets not addressed to it? In-Reply-To: <200002021948.UAA06935@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, 2 Feb 2000, Luigi Rizzo wrote: > > We want to force the use of our web caches. Our boundary router is a 3Com > > NetBuilder II, which we can get to forward port 80 traffic to another IP > > address. However, it does not rewrite the destination IP address in the IP > > you mean in the reply ? because otherwise how can it forward the > traffic to another address! That's why the machine has to be plugged directly into the router. The router can of course forward the packet to a directly connected IP address. On the NBII an incoming firewall filter of the form: permit next hop tcp dst=80 achieves this for http traffic. However, due to the router not modifying the destination address in a packet, the machine will then recieve a packet which is not actually addressed to it. On the face of it, this seems useless. However, I wanted to know from someone with a better grip on the networking of FreeBSD, whether it would be able to make use of this facility. Specifically to provide enforced web caching. Cheers. Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@ais.salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 2: 0:46 2000 Delivered-To: freebsd-net@freebsd.org Received: from vidle.i.cz (vidle.i.cz [193.179.36.138]) by builder.freebsd.org (Postfix) with ESMTP id 33C5642CF for ; Thu, 3 Feb 2000 02:00:42 -0800 (PST) Received: from ns.i.cz (brana.i.cz [193.179.36.134]) by vidle.i.cz (Postfix) with ESMTP id 1F6063072C for ; Thu, 3 Feb 2000 11:00:48 +0100 (CET) Received: from woody.i.cz (woody.i.cz [192.168.18.29]) by ns.i.cz (Postfix) with ESMTP id 232BB36415 for ; Thu, 3 Feb 2000 11:00:47 +0100 (CET) Content-Length: 1695 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 03 Feb 2000 11:00:47 +0100 (MET) Reply-To: mm@i.cz From: Martin Machacek To: freebsd-net@freebsd.org Subject: Re: Can 3.4-S cope with packets not addressed to it? Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 03-Feb-00 Mark Powell wrote: > Hmmm. Hadn't though of that. Now how many web servers are there in the > world. Could you provide a list and I'll start setting the aliases up. > Seriously, is there any way to get FreeBSD to accept any IP packets? You cannot use alias address on any of your interfaces since you won't be able to reach the real server to fetch the content into your cache. However, you can use the ipfw fwd ... rule to feed the request to your cache (squid?) no matter what IP address is the packet header. The cache can then use the getsockname call to find out the "real" address and fetch the content from the real server. If you're using some recent version of squid it should work out of the box (just add the ipfw fwd rules). In order to redirect all HTTP requests to the cache you should add something like this: ipfw add 1000 fwd 127.0.0.1,3128 tcp from to any 80 in via assuming yor web cache listens on 127.0.0.1 port 3128. You should substitute addresses of your clients for (e.g. 10.0.0.0/8) and name of your ethernet interface for (e.g. fxp0). It is critical that you put the "in" keyword in the rule in order to avoid loops triggered by your cache trying to fetch the content from the real server. See man 8 ipfw for more. If you're using squid as the cache you could eventually use WCCP to redirect HTTP requests to it. Recent version of squid support it out of the box you only have to configure the address of your "home router". However your router has to support WCCP. All Ciscos (with IOS 11.2 and higher) do. Don't know about 3Com. WCCP is Cisco invention :-). Martin --- [PGP KeyID F3F409C4] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 3:41:10 2000 Delivered-To: freebsd-net@freebsd.org Received: from euitt.upm.es (haddock.euitt.upm.es [138.100.52.102]) by builder.freebsd.org (Postfix) with ESMTP id 63E28439B for ; Thu, 3 Feb 2000 03:40:53 -0800 (PST) Received: from localhost (pjlobo@localhost) by euitt.upm.es (8.9.3/8.9.3) with ESMTP id MAA32673; Thu, 3 Feb 2000 12:38:10 +0100 (MET) Date: Thu, 3 Feb 2000 12:38:10 +0100 (MET) From: "Pedro J. Lobo" To: "Matthew N. Dodd" Cc: Jasper Wallace , Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 2 Feb 2000, Matthew N. Dodd wrote: >Does the kernel patch work with any other adapters? I'm not sure I see >the need to patch if_fxp. if_fxp does have to be patched. You have to tell the card not to drop frames with errors (oversized frames among them) or you won't receive packets with sizes from 1497 to 1500 bytes (remember that 802.1Q adds 4 bytes to each frame). Then you have to drop by hand undersized frames and frames with crc errors. I know (from the Intel documentation) that the 82559 controller (and maybe 82558 too, don't remember right now) adds a bit of vlan support and you can tell it not to drop oversized frames. However I haven't any programming info for it, so I don't know how it can be done. Cheers, Pedro. -- ------------------------------------------------------------------- Pedro José Lobo Perea Tel: +34 91 336 78 19 Centro de Cálculo Fax: +34 91 331 92 29 E.U.I.T. Telecomunicación e-mail: pjlobo@euitt.upm.es Universidad Politécnica de Madrid Ctra. de Valencia, Km. 7 E-28031 Madrid - Espańa / Spain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 3:43:56 2000 Delivered-To: freebsd-net@freebsd.org Received: from euitt.upm.es (haddock.euitt.upm.es [138.100.52.102]) by builder.freebsd.org (Postfix) with ESMTP id C20164384 for ; Thu, 3 Feb 2000 03:43:46 -0800 (PST) Received: from localhost (pjlobo@localhost) by euitt.upm.es (8.9.3/8.9.3) with ESMTP id MAA24043; Thu, 3 Feb 2000 12:30:33 +0100 (MET) Date: Thu, 3 Feb 2000 12:30:33 +0100 (MET) From: "Pedro J. Lobo" To: "Matthew N. Dodd" Cc: Jasper Wallace , Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 2 Feb 2000, Matthew N. Dodd wrote: >Ok, I've reviewed the patches (crap) and fixed the problem (easy). I agree that the patches aren't the perfect solution. As I said, they were a quick and dirty hack. When I posted them, I received a commment from Garrett Wollman (which I never answered, sorry Garrett), who also didn't like them. >I'm not terribly happy with how the double queuing ends up working but its >much better than polluting sys/net/if_ethersubr.c with all sorts of VLAN >defines. Also agreed. I did it that way because although I didn't like the double queuing, it should have worked, and I didn't find any obvious error. >The correct solution will be to write a vlan_output() routine that does >the right thing so we can place packets right on the parent interface's >queue instead of calling ether_output twice. Yes, that would be a nice approach. >I'm not inclined to do this so close to release so the brief patch will >have to do. I have *tons* of "real" work to do right now, but I'll test it as soon as I can. Cheers, Pedro. -- ------------------------------------------------------------------- Pedro José Lobo Perea Tel: +34 91 336 78 19 Centro de Cálculo Fax: +34 91 331 92 29 E.U.I.T. Telecomunicación e-mail: pjlobo@euitt.upm.es Universidad Politécnica de Madrid Ctra. de Valencia, Km. 7 E-28031 Madrid - Espańa / Spain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 3:46: 2 2000 Delivered-To: freebsd-net@freebsd.org Received: from amalthea.salford.ac.uk (amalthea.salford.ac.uk [146.87.255.61]) by builder.freebsd.org (Postfix) with SMTP id 3EBD843AF for ; Thu, 3 Feb 2000 03:45:47 -0800 (PST) Received: (qmail 2049 invoked by alias); 3 Feb 2000 11:45:54 -0000 Received: (qmail 2043 invoked from network); 3 Feb 2000 11:45:53 -0000 Received: from plato.salford.ac.uk (146.87.255.76) by amalthea.salford.ac.uk with SMTP; 3 Feb 2000 11:45:53 -0000 Received: (qmail 26801 invoked by uid 141); 3 Feb 2000 11:45:53 -0000 Date: Thu, 3 Feb 2000 11:45:53 +0000 (GMT) From: Mark Powell To: =?iso-8859-1?Q?Edstr=F6m?= Johan Cc: freebsd-net@freebsd.org Subject: Re: Can 3.4-S cope with packets not addressed to it? In-Reply-To: <38994D95.B78301A4@hygiene.sca.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 3 Feb 2000, Edstr=F6m Johan wrote: > Check out transparent proxy at the squid site. I think the stumbling block was that I'd never used any of this filtering stuff before. I was thinking that BSD wouldn't accept a packet addressed to it, but obviously if it can perform as a router, it must be able to, doh! On a web cache connected to the router: ipfw add 49 allow tcp from 10.0.1.1 to any ipfw add 50 fwd 127.0.0.1,3128 tcp from any to any 80 will achieve what I want. However, we have two caches and I'd like both utilised. There seems no way to get the router to forward based on any criteria apart from IP address. Thus I'd have to get the packets forwarded to one machine A and then get it to conditionally forward to the caches, B or C (all three on the same network.) =09=09=09-------- Internet --------| NBII |-------- Campus =09=09=09-------- =09=09=09 | =09=09------------------------ =09=09|=09 |=09 | =09=09A=09 B=09 C e.g. A - 10.0.1.1 - Port 80 distributor B - 10.0.1.2 - Web cache 1 C - 10.0.1.3 - Web cache 2 Thus on the NBII, incoming from our campus interface: permit next hop 10.0.1.1 tcp dst=3D80 On machine A: ipfw add 49 allow tcp from 10.0.0.1 to any ipfw add 50 fwd 10.0.1.2 tcp from 0.0.0.0/1 to any 80 ipfw add 51 fwd 10.0.1.3 tcp from 1.0.0.0/1 to any 80 On machine B: ipfw add 49 allow tcp from 10.0.1.2 to any ipfw add 50 fwd 127.0.0.1,3128 tcp from any to any 80 On machine C: ipfw add 49 allow tcp from 10.0.1.3 to any ipfw add 50 fwd 127.0.0.1,3128 tcp from any to any 80 Does this seem right or have I missed something? Would it be possible to just get A to forward directly to the correct port on the caches? On machine A: ipfw add 50 fwd 10.0.1.2,3128 tcp from 0.0.0.0/1 to any 80 ipfw add 51 fwd 10.0.1.3,3128 tcp from 1.0.0.0/1 to any 80 Thanks for anyone that's stayed with this :) Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@ais.salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 7:58: 9 2000 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by builder.freebsd.org (Postfix) with ESMTP id 8A2493EFE for ; Thu, 3 Feb 2000 07:58:05 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id KAA50942; Thu, 3 Feb 2000 10:56:23 -0500 (EST) Date: Thu, 3 Feb 2000 10:56:23 -0500 (EST) From: "Matthew N. Dodd" To: "Pedro J. Lobo" Cc: Jasper Wallace , Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs 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 Thu, 3 Feb 2000, Pedro J. Lobo wrote: > if_fxp does have to be patched. You have to tell the card not to drop > frames with errors (oversized frames among them) or you won't receive > packets with sizes from 1497 to 1500 bytes (remember that 802.1Q adds 4 > bytes to each frame). Then you have to drop by hand undersized frames and > frames with crc errors. If the size of our header increases then the payload we can carry decreases. Violating ethernet frame lengths doesn't strike me as a good idea. Besides, there is little we can do about hardware that doesn't allow us to send/receive larger packets. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 8:21:47 2000 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by builder.freebsd.org (Postfix) with ESMTP id 0A8C8405E for ; Thu, 3 Feb 2000 08:21:42 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id LAA51232; Thu, 3 Feb 2000 11:21:14 -0500 (EST) Date: Thu, 3 Feb 2000 11:21:14 -0500 (EST) From: "Matthew N. Dodd" To: "Pedro J. Lobo" Cc: Jasper Wallace , Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs 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 Thu, 3 Feb 2000, Pedro J. Lobo wrote: > >I'm not inclined to do this so close to release so the brief patch will > >have to do. > > I have *tons* of "real" work to do right now, but I'll test it as soon > as I can. I've committed this to -CURRENT (after a bunch of testing) and will MFC in a week or so. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 8:32:12 2000 Delivered-To: freebsd-net@freebsd.org Received: from euitt.upm.es (haddock.euitt.upm.es [138.100.52.102]) by builder.freebsd.org (Postfix) with ESMTP id 264C240F5 for ; Thu, 3 Feb 2000 08:31:39 -0800 (PST) Received: from localhost (pjlobo@localhost) by euitt.upm.es (8.9.3/8.9.3) with ESMTP id RAA32286; Thu, 3 Feb 2000 17:29:28 +0100 (MET) Date: Thu, 3 Feb 2000 17:29:28 +0100 (MET) From: "Pedro J. Lobo" To: "Matthew N. Dodd" Cc: Jasper Wallace , Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 3 Feb 2000, Matthew N. Dodd wrote: >On Thu, 3 Feb 2000, Pedro J. Lobo wrote: >> if_fxp does have to be patched. You have to tell the card not to drop >> frames with errors (oversized frames among them) or you won't receive >> packets with sizes from 1497 to 1500 bytes (remember that 802.1Q adds 4 >> bytes to each frame). Then you have to drop by hand undersized frames and >> frames with crc errors. > >If the size of our header increases then the payload we can carry >decreases. But then you won't be able to interact with other machines that send 1500-byte frames, which are perfectly legal. Keep reading... >Violating ethernet frame lengths doesn't strike me as a good idea. But you *aren't* violating ethernet frame lengths. 802.1Q frames *can* be 4 bytes longer than traditional ethernet frames. One of the strengths of 802.1Q (IMHO) is that its frames can coexist with traditional ethernet frames even in the same wire (cable, hub, etc.). The machines that doesn't recognize 802.1Q frames see them as "unknown type" frames, or as oversized frames, and simply ignore them. You can even think of another scenario (which is what I have here): you can configure one port in a switch as a "tagged" port (i.e. it will expect and transmit 802.1Q frames) and another one as a "untagged" port (i.e. a traditional ethernet port, an both of them can belong to the same VLAN. When a machine plugged to the untagged port sends a 1500-byte frame, it will appear at the tagged port 4 bytes longer. You can check it with a sniffer. And it is perfectly legal. The 802.1Q standard does allow frames with those 4 extra bytes, and the machines that "speak" 802.1Q must be able to recognize those long frames as valid. >Besides, there is little we can do about hardware that doesn't allow us to >send/receive larger packets. You are completely right on this. Not all cards will be able to support 802.1Q. The Etherexpress Pro/100 (fxp driver) certainly is. I don't know about other cards, but I suspect that many of them will offer you the posibility of send and receive extra-large frames. Cheers, Pedro. -- ------------------------------------------------------------------- Pedro José Lobo Perea Tel: +34 91 336 78 19 Centro de Cálculo Fax: +34 91 331 92 29 E.U.I.T. Telecomunicación e-mail: pjlobo@euitt.upm.es Universidad Politécnica de Madrid Ctra. de Valencia, Km. 7 E-28031 Madrid - Espańa / Spain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 9:22:18 2000 Delivered-To: freebsd-net@freebsd.org Received: from stingray.ivision.co.uk (avengers.ivision.co.uk [195.50.91.40]) by builder.freebsd.org (Postfix) with ESMTP id C64FF422D for ; Thu, 3 Feb 2000 09:22:14 -0800 (PST) Received: from stingray.ivision.co.uk ([195.50.91.40]) by stingray.ivision.co.uk with esmtp (Exim 2.04 #1) id 12GPwx-0000ZM-00; Thu, 3 Feb 2000 17:21:47 +0000 Date: Thu, 3 Feb 2000 17:21:46 +0000 (BST) From: Jasper Wallace To: "Matthew N. Dodd" Cc: Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: Message-ID: X-NCC-RegID: uk.instant-web MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 2 Feb 2000, Matthew N. Dodd wrote: > On Wed, 2 Feb 2000, Jasper Wallace wrote: > > oh well, with the vlan code in -stable i could ping, but tcp or udp > > packets would eventually panic the machine, it's fine with the patches > > from the above url. >=20 > Does the kernel patch work with any other adapters? I'm not sure I see > the need to patch if_fxp. From=20what i've heard it *only* works with fxp... The problem is that a tagged packet will be bigger than 1500 bytes, so most nic's will drop it as an error, the fxp's can have a flag set that stops this behaviour. --=20 Internet Vision Internet Consultancy Tel: 0171 589 4500 60 Albert Court & Web development Fax: 0171 589 4522 Prince Consort Road vision@ivision.co.uk London SW7 2BE http://www.ivision.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 9:29:43 2000 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by builder.freebsd.org (Postfix) with ESMTP id 0BDED3D38 for ; Thu, 3 Feb 2000 09:29:31 -0800 (PST) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id SAA11195; Thu, 3 Feb 2000 18:29:25 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200002031729.SAA11195@info.iet.unipi.it> Subject: Re: 802.1Q VLANs In-Reply-To: from Jasper Wallace at "Feb 3, 2000 05:21:46 pm" To: Jasper Wallace Date: Thu, 3 Feb 2000 18:29:25 +0100 (CET) Cc: "Matthew N. Dodd" , Mike Nowlin , 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 > The problem is that a tagged packet will be bigger than 1500 bytes, so most > nic's will drop it as an error, the fxp's can have a flag set that stops > this behaviour. it's not the nic (ie hardware), in many cases it is just the driver which drops the pkt as an error. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 9:42:24 2000 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by builder.freebsd.org (Postfix) with ESMTP id 240C641C4 for ; Thu, 3 Feb 2000 09:42:21 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id MAA52401; Thu, 3 Feb 2000 12:40:47 -0500 (EST) Date: Thu, 3 Feb 2000 12:40:47 -0500 (EST) From: "Matthew N. Dodd" To: "Pedro J. Lobo" Cc: freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs 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 Thu, 3 Feb 2000, Pedro J. Lobo wrote: > You can even think of another scenario (which is what I have here): > you can configure one port in a switch as a "tagged" port (i.e. it > will expect and transmit 802.1Q frames) and another one as a > "untagged" port (i.e. a traditional ethernet port, an both of them can > belong to the same VLAN. When a machine plugged to the untagged port > sends a 1500-byte frame, it will appear at the tagged port 4 bytes > longer. You can check it with a sniffer. And it is perfectly legal. Yea, that makes a bit more sense. > The 802.1Q standard does allow frames with those 4 extra bytes, and > the machines that "speak" 802.1Q must be able to recognize those long > frames as valid. Humm... Ideally the VLAN driver should be able to set the MTU for its parent and deal with being able to set the MTU > 1500. This prevents us from making VLAN specific hacks to the other drivers and relegates the problem to one of supporting 'large frames'. > You are completely right on this. Not all cards will be able to > support 802.1Q. The Etherexpress Pro/100 (fxp driver) certainly is. I > don't know about other cards, but I suspect that many of them will > offer you the posibility of send and receive extra-large frames. Well, I see no reason to restrict people to cards that don't support large frames; if they really need to use VLANs they can adjust the MTU down. In the real world MTU discovery will insure that they aren't too big of a problem. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 10:51:43 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by builder.freebsd.org (Postfix) with ESMTP id 237DE3F66 for ; Thu, 3 Feb 2000 10:51:39 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA62013; Thu, 3 Feb 2000 13:47:08 -0500 (EST) (envelope-from wollman) Date: Thu, 3 Feb 2000 13:47:08 -0500 (EST) From: Garrett Wollman Message-Id: <200002031847.NAA62013@khavrinen.lcs.mit.edu> To: "Matthew N. Dodd" Cc: "Pedro J. Lobo" , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Humm... Ideally the VLAN driver should be able to set the MTU for its > parent and deal with being able to set the MTU > 1500. No, you've got it the wrong way 'round. If the interface driver is written to be able to accept 1500-byte frames with an 18-byte header (as opposed to the ``normal'' 14-byte header), it needs to inform the upper layers of this by setting its advertised header length (ifi_hdrlen) to 18 rather than 14. The driver should always do this, if the hardware is capable, so that those frames will be made available to bpf. > Well, I see no reason to restrict people to cards that don't support large > frames; if they really need to use VLANs they can adjust the MTU down. In > the real world MTU discovery will insure that they aren't too big of a > problem. No, it won't. In the real world, MTU discovery will never be invoked, because switches do not allow users to reconfigure the MTU. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 10:54:38 2000 Delivered-To: freebsd-net@freebsd.org Received: from euitt.upm.es (haddock.euitt.upm.es [138.100.52.102]) by builder.freebsd.org (Postfix) with ESMTP id 918EA3FFE for ; Thu, 3 Feb 2000 10:54:22 -0800 (PST) Received: from localhost (pjlobo@localhost) by euitt.upm.es (8.9.3/8.9.3) with ESMTP id TAA06969; Thu, 3 Feb 2000 19:48:31 +0100 (MET) Date: Thu, 3 Feb 2000 19:48:31 +0100 (MET) From: "Pedro J. Lobo" To: "Matthew N. Dodd" Cc: freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 3 Feb 2000, Matthew N. Dodd wrote: >On Thu, 3 Feb 2000, Pedro J. Lobo wrote: > >> The 802.1Q standard does allow frames with those 4 extra bytes, and >> the machines that "speak" 802.1Q must be able to recognize those long >> frames as valid. > >Humm... Ideally the VLAN driver should be able to set the MTU for its >parent and deal with being able to set the MTU > 1500. No, the MTU doesn't need to be changed. In fact, changing it would probably mean trouble. The maximum ethernet frame size is 1518 bytes. Substract 6 + 6 + 2 + 4 (destination address, source address, frame type and frame crc) and you get 1500 bytes, which is the maximum payload that a frame can carry. That is the MTU. 802.1Q adds 4 bytes to the maximum frame size, but the payload length doesn't change. So, the MTU is still 1500 bytes. From the IP stack point of view, a 802.1Q interface is exactly the same as a traditional ethernet one. And everything works flawlessly: the interfaces that doesn't speak 802.1Q will discard some frames as oversized, but that doesn't matter because they wouldn't know how to process them anyway. If you lower the MTU to 1496 bytes you will have to accept 1500-byte IP packets anyway, because other machines can (legally) send them to you. Accepting a packet that's bigger than the interface's MTU is at least strange. And, if the machine is a router (which in fact was my goal when I made the patch) you would have to fragment and re-assemble a lot of packets, which is very inefficient. >This prevents us from making VLAN specific hacks to the other drivers >and relegates the problem to one of supporting 'large frames'. You *can't* avoid making modifications to the drivers. The driver must accept ethernet frames up to 1522 bytes *if and only if* they are 802.1Q frames, and it *can't* drop them or it will break the standards. >> You are completely right on this. Not all cards will be able to >> support 802.1Q. The Etherexpress Pro/100 (fxp driver) certainly is. I >> don't know about other cards, but I suspect that many of them will >> offer you the posibility of send and receive extra-large frames. > >Well, I see no reason to restrict people to cards that don't support large >frames; if they really need to use VLANs they can adjust the MTU down. In Well, I do see a reason: to keep the standards compliance. A network card is cheap: I buy the fxp's for less than $50. I think it isn't a big price for being compatible with the rest of the world. And I would be fairly surprised if recent network controllers from other vendors (3Com, DEC, etc, etc) didn't have the ability to support long frames, though I can't assure it. Of course if you *really* need it you can lower the MTU and work with frames 4 bytes shorter, but I think that the VLAN code should fully support the standards when the NIC allows it. Cheers, Pedro. -- ------------------------------------------------------------------- Pedro José Lobo Perea Tel: +34 91 336 78 19 Centro de Cálculo Fax: +34 91 331 92 29 E.U.I.T. Telecomunicación e-mail: pjlobo@euitt.upm.es Universidad Politécnica de Madrid Ctra. de Valencia, Km. 7 E-28031 Madrid - Espańa / Spain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 12:29:36 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by builder.freebsd.org (Postfix) with ESMTP id 8A4BE3DE5 for ; Thu, 3 Feb 2000 12:29:33 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id PAA63379; Thu, 3 Feb 2000 15:25:32 -0500 (EST) (envelope-from wollman) Date: Thu, 3 Feb 2000 15:25:32 -0500 (EST) From: Garrett Wollman Message-Id: <200002032025.PAA63379@khavrinen.lcs.mit.edu> To: "Matthew N. Dodd" Cc: Garrett Wollman , "Pedro J. Lobo" , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: References: <200002031847.NAA62013@khavrinen.lcs.mit.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Humm... Isn't this going to confuse BPF when its receiving normal > ethernet headers? No. If it's listening on the vlan interface, it will get the decapsulated packets. If it's listening on the master interface, it will get everything. tcpdump, at least, understands (or can easily be made to understand) 802.1Q tagging. The libpcap filter compiler doesn't actually know about 802.1Q, but it doesn't know about ifi_hdrlen either! This is important as a debugging facility. > I'm not sure we want to have the drivers always accept large > packets, just because we've compiled a kernel with VLAN devices in it. Not because we've compiled a kernel with VLAN devices in it; because we've compiled a kernel with a NIC driver that supports large packets. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 12:32:18 2000 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by builder.freebsd.org (Postfix) with ESMTP id B23503F58 for ; Thu, 3 Feb 2000 12:32:05 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id PAA54272; Thu, 3 Feb 2000 15:28:18 -0500 (EST) Date: Thu, 3 Feb 2000 15:28:18 -0500 (EST) From: "Matthew N. Dodd" To: Garrett Wollman Cc: "Pedro J. Lobo" , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: <200002032025.PAA63379@khavrinen.lcs.mit.edu> 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, 3 Feb 2000, Garrett Wollman wrote: > > I'm not sure we want to have the drivers always accept large > > packets, just because we've compiled a kernel with VLAN devices in it. > > Not because we've compiled a kernel with VLAN devices in it; because > we've compiled a kernel with a NIC driver that supports large packets. But do we want a device to -always- accept large frames just because it supports them? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 12:40:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by builder.freebsd.org (Postfix) with ESMTP id 2C1BC400D for ; Thu, 3 Feb 2000 12:40:48 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id PAA54042; Thu, 3 Feb 2000 15:04:29 -0500 (EST) Date: Thu, 3 Feb 2000 15:04:29 -0500 (EST) From: "Matthew N. Dodd" To: Garrett Wollman Cc: "Pedro J. Lobo" , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: <200002031847.NAA62013@khavrinen.lcs.mit.edu> 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, 3 Feb 2000, Garrett Wollman wrote: > No, you've got it the wrong way 'round. > > If the interface driver is written to be able to accept 1500-byte > frames with an 18-byte header (as opposed to the ``normal'' 14-byte > header), it needs to inform the upper layers of this by setting its > advertised header length (ifi_hdrlen) to 18 rather than 14. The > driver should always do this, if the hardware is capable, so that > those frames will be made available to bpf. Humm... Isn't this going to confuse BPF when its receiving normal ethernet headers? Regardless, any further effort on my part for the VLAN driver is going to be restricted to vlan_output(); someone else can wrangle with the MTU issues since they're outside of the scope of things I'm willing to fix. (I'd like to see 802.1Q work with FDDI and Token Ring, but thats another issue; we'd probably need to move the encapsulation/decapsulation code into sys/net/if_{ether,fddi,iso88025}subr.c.) My questions about large packets and MTU assumed that we would rather that network drivers only receive large frames when we tell them to (setting the MTU) or when we attach a VLAN device to a physical network interface. I'm not sure we want to have the drivers always accept large packets, just because we've compiled a kernel with VLAN devices in it. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 18: 2:20 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by builder.freebsd.org (Postfix) with ESMTP id 6B8D53FD4 for ; Thu, 3 Feb 2000 18:02:18 -0800 (PST) Received: from brisbane.wrs.com (brisbane [147.11.38.9]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id SAA19916 for ; Thu, 3 Feb 2000 18:02:12 -0800 (PST) From: Stephen Macmanus Received: (from stephenm@localhost) by brisbane.wrs.com (8.9.1/8.9.0) id SAA01528 for freebsd-net@freebsd.org; Thu, 3 Feb 2000 18:02:30 -0800 (PST) Date: Thu, 3 Feb 2000 18:02:30 -0800 (PST) Message-Id: <200002040202.SAA01528@brisbane.wrs.com> To: freebsd-net@freebsd.org Subject: Path MTU discovery Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have found some puzzling behavior in the path MTU discovery implementation in Free BSD 3.4 which I hope someone can shed light on. The tcp_mtudisc routine adjusts the MSS for a connection in response to the ICMP error which triggers adjustment of the path MTU estimate to a new value. That routine includes the following code: struct tcpcb *tp = intotcpcb(inp); struct rtentry *rt; struct rmxp_tao *taop; struct socket *so = inp->inp_socket; int offered; int mss; if (tp) { rt = tcp_rtlookup(inp); if (!rt || !rt->rt_rmx.rmx_mtu) { tp->t_maxopd = tp->t_maxseg = tcp_mssdflt; return; } taop = rmx_taop(rt->rt_rmx); offered = taop->tao_mssopt; mss = rt->rt_rmx.rmx_mtu - sizeof(struct tcpiphdr); if (offered) mss = min(mss, offered); . . . Both this routine and the tcp_mss routine examine the results of tcp_rtlookup() to verify that a route to the destination address exists. That test appears to be redundant. I can't see a situation where the system is unable to find a route to the remote address given that the routine can only execute after the socket assigns local and remote address information, which includes the route lookup. Similarly, I don't entirely understand the conditional execution of the min() operation. It can only apply before the remote peer sends the initial SYN since tao_mssopt is always non-zero after that point. That could occur if the host generates the ICMP error by sending a TCP segment which includes data along with the SYN flag. Examining the tcp_output() routine, that behavior doesn't seem possible. Does anyone know how it can occur? Thanks, Stephen ------------------ Stephen Macmanus #include Software Engineer Wind River Systems To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 18: 7:11 2000 Delivered-To: freebsd-net@freebsd.org Received: from pooky.bmk.com.au (pooky.bmk.com.au [203.36.170.246]) by builder.freebsd.org (Postfix) with ESMTP id 07ACB3D60 for ; Thu, 3 Feb 2000 18:07:06 -0800 (PST) Received: from garfield (gateway.ozi.nu [203.36.170.241]) by pooky.bmk.com.au (8.8.7/8.8.7) with SMTP id NAA23990 for ; Fri, 4 Feb 2000 13:06:47 +1100 Date: Fri, 4 Feb 2000 13:08:06 +1100 (EST) From: Brendan Kosowski X-Sender: brendan@garfield To: FreeBSD Networking Subject: Syncro. PPP and Serial Line Load Balancing 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 would like to establish a ppp link between 2 boxes using both serial ports ( com1 and com2 ) synchronously. Does the kernel automatically do the Serial Line Load Balancing to achieve this ??? Can I just start 2 pppd's ( both using the same IP addresses but different com ports ) ??? If not, how do I achieve Syncho. ppp ??? Best Regards, Brendan Kosowski... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 18:45:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id C17684270 for ; Thu, 3 Feb 2000 18:45:38 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id SAA18273; Thu, 3 Feb 2000 18:45:48 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id SAA08839; Thu, 3 Feb 2000 18:45:48 -0800 Received: from softweyr.com (dyn5.utah.xylan.com [198.206.184.241]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id SAA11092; Thu, 3 Feb 2000 18:45:46 -0800 (PST) Message-ID: <389A3EA9.446F9ACF@softweyr.com> Date: Thu, 03 Feb 2000 19:51:21 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Powell Cc: Wim Livens , freebsd-net@freebsd.org Subject: Re: Can 3.4-S cope with packets not addressed to it? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mark Powell wrote: > > On Thu, 3 Feb 2000, Wim Livens wrote: > > On Wed, Feb 02, 2000 at 06:34:55PM +0000, Mark Powell wrote: > > > We want to force the use of our web caches. Our boundary router is a 3Com > > > NetBuilder II, which we can get to forward port 80 traffic to another IP > > > address. However, it does not rewrite the destination IP address in the IP > > > header. Thus the machine has to be directly connected to the router to > > > actually get the packets. > > > What I'm wondering, is can FreeBSD cope with this? Will it be able to > > > process these packets, with an IP address that is not it's own, at all or > > > > maybe this helps: > > ifconfig ... alias > > Hmmm. Hadn't though of that. Now how many web servers are there in the > world. Could you provide a list and I'll start setting the aliases up. > Seriously, is there any way to get FreeBSD to accept any IP packets? Sure - put the interface in promiscuous mode. The TCP/IP stack doesn't do this because a big part of it's reason for existing is to filter out packets that don't belong to you. If you want to do this, look at the berkeley packet filter manpage - bpf(4). -- "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 Thu Feb 3 22:17:34 2000 Delivered-To: freebsd-net@freebsd.org Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by builder.freebsd.org (Postfix) with SMTP id 7721D4411 for ; Thu, 3 Feb 2000 22:17:28 -0800 (PST) Received: (qmail 85977 invoked by uid 8031); 4 Feb 2000 06:17:31 -0000 Message-ID: <20000204061731.85976.qmail@scam.xcf.berkeley.edu> To: freebsd-net@freebsd.org Subject: Non-blocking sockets and network outages X-Common-Yaroslav-Version: 2.0 X-Editor: nvi Date: Thu, 03 Feb 2000 22:17:31 -0800 From: Gene Kan Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got an interesting problem involving non-blocking sockets and network outages. In all cases, SO_KEEPALIVE is on, and net.inet.tcp.always_keepalive: 1. The problem manifests itself when there is a net partition, the other endpoint loses power, or something of that sort. Basically, when a connection dies without first notifying with RST or FIN. If I mark a socket for reading, the fd will just never become active, and I have an ESTABLISHED connection (verified with netstat) forever. If I do a non-blocking write, the write will return -1 with errno==EAGAIN. Obviously, since it just looks like the other side isn't slurping up the data because I'm not getting a window update. Finally...I can't figure out why the keepalives aren't taking care of all this for me, and discovering the connections are dead. I waited for hours, which surely should have been more than all timeouts... Thanks for any help. Gene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 23:53:34 2000 Delivered-To: freebsd-net@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by builder.freebsd.org (Postfix) with ESMTP id 5BBE643F1 for ; Thu, 3 Feb 2000 23:52:27 -0800 (PST) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id JAA17293; Fri, 4 Feb 2000 09:51:59 +0200 (EET) (envelope-from ru) Date: Fri, 4 Feb 2000 09:51:59 +0200 From: Ruslan Ermilov To: Stephen Macmanus Cc: freebsd-net@FreeBSD.ORG Subject: Re: Path MTU discovery Message-ID: <20000204095159.C10334@relay.ucb.crimea.ua> Mail-Followup-To: Stephen Macmanus , freebsd-net@FreeBSD.ORG References: <200002040202.SAA01528@brisbane.wrs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <200002040202.SAA01528@brisbane.wrs.com>; from Stephen Macmanus on Thu, Feb 03, 2000 at 06:02:30PM -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Feb 03, 2000 at 06:02:30PM -0800, Stephen Macmanus wrote: > I have found some puzzling behavior in the path MTU discovery > implementation in Free BSD 3.4 which I hope someone can shed light > on. > > The tcp_mtudisc routine adjusts the MSS for a connection in > response to the ICMP error which triggers adjustment of the path > MTU estimate to a new value. That routine includes the following > code: > > struct tcpcb *tp = intotcpcb(inp); > struct rtentry *rt; > struct rmxp_tao *taop; > struct socket *so = inp->inp_socket; > int offered; > int mss; > > if (tp) { > rt = tcp_rtlookup(inp); > if (!rt || !rt->rt_rmx.rmx_mtu) { > tp->t_maxopd = tp->t_maxseg = tcp_mssdflt; > return; > } > taop = rmx_taop(rt->rt_rmx); > offered = taop->tao_mssopt; > mss = rt->rt_rmx.rmx_mtu - sizeof(struct tcpiphdr); > if (offered) > mss = min(mss, offered); > > . > . > . > > Both this routine and the tcp_mss routine examine the results of > tcp_rtlookup() to verify that a route to the destination address > exists. That test appears to be redundant. I can't see a situation > where the system is unable to find a route to the remote address > given that the routine can only execute after the socket assigns > local and remote address information, which includes the route lookup. > No, they do so to check the current mtu value along this route. > Similarly, I don't entirely understand the conditional execution > of the min() operation. It can only apply before the remote peer sends > the initial SYN since tao_mssopt is always non-zero after that point. > That could occur if the host generates the ICMP error by sending a TCP > segment which includes data along with the SYN flag. Examining the > tcp_output() routine, that behavior doesn't seem possible. Does anyone > know how it can occur? > > Thanks, > > Stephen > > ------------------ > Stephen Macmanus #include > Software Engineer > Wind River Systems > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 3 23:54:17 2000 Delivered-To: freebsd-net@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by builder.freebsd.org (Postfix) with ESMTP id 302244407 for ; Thu, 3 Feb 2000 23:54:15 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA11070 for ; Fri, 4 Feb 2000 02:54:29 -0500 Date: Fri, 4 Feb 2000 02:54:29 -0500 (EST) From: Mike Nowlin To: freebsd-net@freebsd.org Subject: PPP handling of multiple connection options (long-ish) 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 (Best subject I could think of... :) ) I've been digging into some of the more "rarely used" options in ppp(8) in 3.4-STABLE, and have a few questions/ideas... Got PPP over UDP working between two internet-connected hosts, which I'm (possibly) planning on using to connect one of our satellite offices to our LAN -- drop a cheap dynamic-IP'd cable modem line in at the remote office, and have PPP create a sorta-static address for the remote machine.. So far, so good. Noticing that you can "set device /dev/cuaa0 /dev/cuaa1 /dev/cuaa2" to have it select the first possible modem, and I'm able to type in "set device rimmer:6669/udp /dev/cuac04" without generating tons of errors, will that actually work -- try the direct udp connection first, and if it times out/fails, try the serial device? Assuming THAT works, we come to the dialing/logging-in portion of it... Obviously, the cable modem won't respond to ATDT555-1212 the same way that a modem will... It seems to me that although you can specify multiple serial ports to use, you can only specify one dial chat script... The chat script required for the modem is "ABORT BUSY...OK-AT-OK \\dATDT\\T..." (stuff removed), and the chat script for the UDP connection is "". Is it possible, or would it be helpful for me to add, the ability to do something like: set dial "ATDTblahblah" <-- set the default dial script set foodial rimmer:6669/udp "" <-- set the dial script for the udp conn. ... same with some other values, such as authname, authkey, timeout, etc... This would also be useful when dealing with multiple serial ports with modems connected that require completely different dial strings, or if you want to connect to different ISPs with "ppp -background anyisp"... 98.6% of this is to provide an automatic dial-backup of the UDP-based PPP connection -- if somebody at MCI decides to trip over another cable, PPP will blow up, try the UDP connection again, fail, and then try dialing directly into the main LAN over the modem... If THAT fails, (like if the corporate head office goes up in flames, which might not be a bad idea), try dialing into a local ISP instead. Now that I've typed all this in, I realize that this could be done with "ppp -background" and checking the return value, but I'll send it anyway.. Some of the ideas still make sense, such as the different dial strings for different modems...... :) --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 4 2:25:48 2000 Delivered-To: freebsd-net@freebsd.org Received: from euitt.upm.es (haddock.euitt.upm.es [138.100.52.102]) by builder.freebsd.org (Postfix) with ESMTP id 7472D4459 for ; Fri, 4 Feb 2000 02:25:32 -0800 (PST) Received: from localhost (pjlobo@localhost) by euitt.upm.es (8.9.3/8.9.3) with ESMTP id LAA03803; Fri, 4 Feb 2000 11:23:52 +0100 (MET) Date: Fri, 4 Feb 2000 11:23:51 +0100 (MET) From: "Pedro J. Lobo" To: Garrett Wollman Cc: "Matthew N. Dodd" , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: <200002032025.PAA63379@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 3 Feb 2000, Garrett Wollman wrote: >< said: > >> I'm not sure we want to have the drivers always accept large >> packets, just because we've compiled a kernel with VLAN devices in it. > >Not because we've compiled a kernel with VLAN devices in it; because >we've compiled a kernel with a NIC driver that supports large packets. But the drivers won't accept *all* large packets! I mean, the driver must make sure that the NIC won't drop oversized frames so it can examine them, but if it sees a 1522-byte frame that doesn't belong to a 802.1Q VLAN it will drop that frame (as well as any frame longer than 1522 bytes). To put it in short, no frame with more than 1500 bytes of payload will be accepted. Cheers, Pedro. -- ------------------------------------------------------------------- Pedro José Lobo Perea Tel: +34 91 336 78 19 Centro de Cálculo Fax: +34 91 331 92 29 E.U.I.T. Telecomunicación e-mail: pjlobo@euitt.upm.es Universidad Politécnica de Madrid Ctra. de Valencia, Km. 7 E-28031 Madrid - Espańa / Spain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 4 12: 8: 8 2000 Delivered-To: freebsd-net@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by builder.freebsd.org (Postfix) with ESMTP id B408F496D for ; Fri, 4 Feb 2000 12:08:00 -0800 (PST) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.9.3/8.9.3) id IAA82481; Fri, 4 Feb 2000 08:17:44 -0800 (PST) Message-Id: <200002041617.IAA82481@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.1-cvs 10/15/1999 To: freebsd-net@freebsd.org Cc: bmah@CA.Sandia.GOV Subject: Starting up IPv6 on -CURRENT From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_221775372P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 04 Feb 2000 08:17:40 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --==_Exmh_221775372P Content-Type: text/plain; charset=us-ascii Hi all-- I just got a 4.0-CURRENT machine up and running (sources cvsup-ed yesterday), and I've been playing with the integrated IPv6 stack a bit. On my 3.4-RELEASE + KAME 20000110 snapshot machine, /usr/local/v6/ rc.net6 is a script to bring up either one interface (in the case of a single-homed, possibly-autoconfigured host) or several interfaces (in the case of a router). I can't seem to find anything analogous in /etc on my -CURRENT machine. This would seem to make it somewhat difficult for someone without prior experience with the KAME stack (and an rc.net6 file to look at) to actually bring up IPv6 on -CURRENT. Am I missing something? Thanks! Bruce. PS. When I put rc.net6 into /etc on my -CURRENT machine and set it to be called from /etc/rc.local (trying to emulate my KAME-ified system), it seemed to Do The Right Thing (TM), but with the following differences: 1. Paths are different. Fortunately, most of them are set in shell variables near the top of the script, so they're easy to change. 2. ndp works a little differently than in the KAME snapshot I have (it doesn't have a -I option to set a default interface). At least on this system, it wasn't fatal, although it caused ndp to exit with an error when it was called. --==_Exmh_221775372P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: iwv/jphJ1xbjBNQS6/usyACIYUhAiF0g iQA/AwUBOJr7pNjKMXFboFLDEQL+HQCdFbeEGtazDDCbhxuq+KYPhelOlrMAn3ZY +ya6AXed6u+obL63ex+v1/Rw =DYug -----END PGP SIGNATURE----- --==_Exmh_221775372P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 4 12:38:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by builder.freebsd.org (Postfix) with ESMTP id 99F87437B for ; Fri, 4 Feb 2000 12:38:42 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA68266; Fri, 4 Feb 2000 11:05:18 -0500 (EST) (envelope-from wollman) Date: Fri, 4 Feb 2000 11:05:18 -0500 (EST) From: Garrett Wollman Message-Id: <200002041605.LAA68266@khavrinen.lcs.mit.edu> To: "Pedro J. Lobo" Cc: freebsd-net@freebsd.org Subject: Re: 802.1Q VLANs In-Reply-To: References: <200002032025.PAA63379@khavrinen.lcs.mit.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > make sure that the NIC won't drop oversized frames so it can examine them, > but if it sees a 1522-byte frame that doesn't belong to a 802.1Q VLAN it > will drop that frame (as well as any frame longer than 1522 bytes). No, it should not. When debugging networks, all frames should be made available (including true error frames, although that's a bit harder). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 4 12:42:45 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail2.sol.net (mail2.sol.net [206.55.64.73]) by builder.freebsd.org (Postfix) with ESMTP id A9ABD4314 for ; Fri, 4 Feb 2000 12:42:42 -0800 (PST) Received: from aurora.sol.net (jgreco@aurora.sol.net [206.55.65.76]) by mail2.sol.net (8.8.8/8.8.8/SNNS-1.02) with ESMTP id JAA20883 for ; Fri, 4 Feb 2000 09:59:25 -0600 (CST) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id JAA38965 for freebsd-net@freebsd.org; Fri, 4 Feb 2000 09:59:17 -0600 (CST) From: Joe Greco Message-Id: <200002041559.JAA38965@aurora.sol.net> Subject: dc driver, SNMP, etc. To: freebsd-net@freebsd.org Date: Fri, 4 Feb 2000 09:59:17 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL43 (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 Hello, I was wondering if any comments were to be had: I've been using SMC 9334BDT (SMC dual Etherpower 10/100) cards in PCI machines for several years, to give me 8-port 10/100 routers. Works great. With the price point available on the D-Link 4-port card, apparently supported by the "dc" driver, I'm really tempted to start buying those instead, and gain 16-port routers in the fallout. First, does anyone know if UCD-SNMP will be updated to work with 4.0, since it appears that it is marked BROKEN? I understand that the dc driver will not be backported to 3.x (or I'd go that route). I've read various messages on the dc driver, and it is clear that only (some?) 21143-based cards (which would also probably be supported by de) are supported by this driver. Am I wrong? If not, for that intersection of support, what happens? Which driver will claim the card? Thanks, ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 4 14:43:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-32.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.160]) by builder.freebsd.org (Postfix) with ESMTP id E7D8A3F49 for ; Fri, 4 Feb 2000 14:43:31 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA59693; Fri, 4 Feb 2000 22:43:50 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00702; Fri, 4 Feb 2000 08:59:11 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002040859.IAA00702@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brendan Kosowski Cc: FreeBSD Networking , brian@hak.lan.Awfulhak.org Subject: Re: Syncro. PPP and Serial Line Load Balancing In-Reply-To: Message from Brendan Kosowski of "Fri, 04 Feb 2000 13:08:06 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Feb 2000 08:59:11 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I would like to establish a ppp link between 2 boxes using both serial > ports ( com1 and com2 ) synchronously. > > Does the kernel automatically do the Serial Line Load Balancing to achieve > this ??? > > Can I just start 2 pppd's ( both using the same IP addresses but different > com ports ) ??? If not, how do I achieve Syncho. ppp ??? It's called Multi-link Protocol (MP) and pppd doesn't support it. ppp(8) does however. The idea is to clone your link, point the second link at the second device (or point both links at both devices), set up gettys that'll pick up and exec ppp(8) on the other end, and ensure that you've got ``set mrru ....'' in all configurations. Check the man page for details. > Best Regards, Brendan Kosowski... -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 4 14:43:42 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-32.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.160]) by builder.freebsd.org (Postfix) with ESMTP id 1211D41BC for ; Fri, 4 Feb 2000 14:43:37 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA59700; Fri, 4 Feb 2000 22:43:50 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA00756; Fri, 4 Feb 2000 09:08:36 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002040908.JAA00756@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gene Kan Cc: freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Non-blocking sockets and network outages In-Reply-To: Message from Gene Kan of "Thu, 03 Feb 2000 22:17:31 PST." <20000204061731.85976.qmail@scam.xcf.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Feb 2000 09:08:36 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've got an interesting problem involving non-blocking sockets and network > outages. In all cases, SO_KEEPALIVE is on, and > net.inet.tcp.always_keepalive: 1. The problem manifests itself when > there is a net partition, the other endpoint loses power, or something of > that sort. Basically, when a connection dies without first notifying with > RST or FIN. > > If I mark a socket for reading, the fd will just never become active, and > I have an ESTABLISHED connection (verified with netstat) forever. > > If I do a non-blocking write, the write will return -1 with errno==EAGAIN. > Obviously, since it just looks like the other side isn't slurping up the > data because I'm not getting a window update. > > Finally...I can't figure out why the keepalives aren't taking care of all > this for me, and discovering the connections are dead. I waited for hours, > which surely should have been more than all timeouts... Keepalives are by default very infrequent: $ sysctl -a | fgrep keepi net.inet.tcp.keepidle: 7200000 net.inet.tcp.keepintvl: 75000 net.inet.tcp.keepinit: 75000 hak:/sys/netinet $ fgrep KEEPCNT /sys/netinet/*.h /sys/netinet/tcp_timer.h:#define TCPTV_KEEPCNT 8 /* max probes before drop */ This means that the first keepalive won't be sent for 2 hours, at which point up to 8 will be sent with 75 seconds in between each. If there are no responses after that, the connection is dropped. > Thanks for any help. > > Gene -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 4 14:43:45 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-32.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.160]) by builder.freebsd.org (Postfix) with ESMTP id 82F7840EE for ; Fri, 4 Feb 2000 14:43:34 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA59690; Fri, 4 Feb 2000 22:43:49 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00680; Fri, 4 Feb 2000 08:56:22 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002040856.IAA00680@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Yuriy" Cc: freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: PPP do not break connection In-Reply-To: Message from "Yuriy" of "Thu, 03 Feb 2000 11:32:16 +0200." <200002030930.LAA03852@mails.itci.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Feb 2000 08:56:22 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Sometimes my ppp process do not break connection after the user hang up > modem. > Process ppp -direct go on without end until I kill it. > Why? What I have to do ? > Any ideas. > Thanks on advance. If you're running the version that came with FreeBSD-3.3, you'll need to get a more recent version (http://www.Awfulhak.org/ppp.html). Otherwise, enable debug logging to make ppp report the carrier status every second. It's possible your modem is configured to fake CD. > _______ > Yuriy Samartsev, > Firm ITC Ltd, http://www.itci.net. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 4 15:23:30 2000 Delivered-To: freebsd-net@freebsd.org Received: from prserv.net (out4.prserv.net [32.97.166.34]) by builder.freebsd.org (Postfix) with ESMTP id D803D3DF0 for ; Fri, 4 Feb 2000 15:23:24 -0800 (PST) Received: from TIGGER ([139.92.4.53]) by prserv.net (out4) with SMTP id <2000020423234423901upmore>; Fri, 4 Feb 2000 23:23:44 +0000 Message-Id: <4.2.0.58.20000205001643.00afb778@tim> X-Sender: dermot@tim X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sat, 05 Feb 2000 00:25:50 +0100 To: freebsd-net@FreeBSD.ORG From: Dermot McNally Subject: PPPoE connection almost working 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 Hi, I've been following the discussions so far on the development of PPPoE support and the experience of users so far. This week, I finally got my ADSL service connected (Deutsche Telekom's T-DSL service with Internet access through T-Online). I can connect using Windows, so I'm now trying to get it going under FreeBSD. The connect gets part of the way, then goes no further. My best guess is that I either need to give a Service name (in which case, anybody know what it is?) or I'm seeing the same kind of MAC address affinity that other users reported. Hopefully my tcpdump and log outputs will help somebody to tell me where the problem might lie. Basically, I get a PADO from the provider, and then nothing further happens. I'm using a quite recent version of stable. Any ideas? Config: dsl: set device PPPoE:ed0 set mru 1492 set mtu 1942 deny chap accept pap set speed sync set cd 5 enable lqr set redial 0 0 set dial add 0 0 HISADDR set login set authname xxxxxxxxxxxxxxxxxxxxxxxx set authkey xxxxxxxxxxxxxx set timeout 120 enable dns 23:14:41.096562 0:0:e8:4f:be:4b Broadcast 8863 32: PPPoE PADI v1, type 1, sess 0 len 12 [Service-Name] [Host-Uniq 004888c0] 23:14:41.141794 0:d0:c0:f9:b6:23 0:0:e8:4f:be:4b 8863 67: PPPoE PADO v1, type 1, sess 0 len 47 [Service-Name] [Host-Uniq 004888c0] [AC-Name MUNC12-nrp2] [AC-Cookie 372992470f60c417cd68e17dcde89eb4] Feb 5 00:21:59 tim ppp[581]: tun0: Command: /dev/tty: dial dsl Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: set device PPPoE:ed0 Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: set mru 1492 Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: set mtu 1942 Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: deny chap Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: accept pap Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: set speed sync Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: set cd 5 Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: enable lqr Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: set redial 0 0 Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: set dial Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: add 0 0 HISADDR Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: set login Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: set authname xxxxxxxxxxx Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: set authkey ******** Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: set timeout 120 Feb 5 00:21:59 tim ppp[581]: tun0: Command: dsl: enable dns Feb 5 00:21:59 tim ppp[581]: tun0: Phase: bundle: Establish Feb 5 00:21:59 tim ppp[581]: tun0: Phase: deflink: closed -> opening Feb 5 00:21:59 tim ppp[581]: tun0: Warning: deflink: Reducing MTU to 1492 Feb 5 00:21:59 tim ppp[581]: tun0: Phase: deflink: Connected! Feb 5 00:21:59 tim ppp[581]: tun0: Phase: deflink: opening -> dial Feb 5 00:21:59 tim ppp[581]: tun0: Phase: deflink: dial -> carrier Feb 5 00:22:04 tim ppp[581]: tun0: Phase: deflink: Disconnected! Feb 5 00:22:04 tim ppp[581]: tun0: Phase: deflink: carrier -> hangup Feb 5 00:22:04 tim ppp[581]: tun0: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out Feb 5 00:22:04 tim ppp[581]: tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Sat Feb 5 00:22:04 2000 Feb 5 00:22:04 tim ppp[581]: tun0: Phase: deflink: hangup -> closed Feb 5 00:22:04 tim ppp[581]: tun0: Phase: bundle: Dead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 4 17: 0:54 2000 Delivered-To: freebsd-net@freebsd.org Received: from kinkajou.arc.nasa.gov (kinkajou.arc.nasa.gov [128.102.132.150]) by builder.freebsd.org (Postfix) with ESMTP id 93F8B44A5 for ; Fri, 4 Feb 2000 17:00:51 -0800 (PST) Received: from localhost (lamaster@localhost) by kinkajou.arc.nasa.gov (8.9.3+Sun/8.9.1) with ESMTP id RAA04574 for ; Fri, 4 Feb 2000 17:01:10 -0800 (PST) X-Authentication-Warning: kinkajou.arc.nasa.gov: lamaster owned process doing -bs Date: Fri, 4 Feb 2000 17:01:10 -0800 (PST) From: Hugh LaMaster X-Sender: lamaster@kinkajou.arc.nasa.gov To: "FreeBSD-Net (FreeBSD.Org)" Subject: Re: 802.1Q VLANs In-Reply-To: <200002041605.LAA68266@khavrinen.lcs.mit.edu> 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, 4 Feb 2000, Garrett Wollman wrote: > > make sure that the NIC won't drop oversized frames so it can examine them, > > but if it sees a 1522-byte frame that doesn't belong to a 802.1Q VLAN it > > will drop that frame (as well as any frame longer than 1522 bytes). > > No, it should not. When debugging networks, all frames should be > made available (including true error frames, although that's a bit > harder). I think it may have been mentioned in one of these threads, but, I didn't see it in this one, so, I thought I should mention that even longer frames have been around for a while. Cisco provided ISL before 802.1Q was defined, and, it can have frame sizes of up to 1548 on Ethernet, according to the Cisco documentation. Since many of the Cisco FastEthernet ports are based on the DEC21140 chipset, at least the Cisco variant can handle frame sizes that large (perhaps all variants can, I don't know). The DEC21140 chipset came out about 5 years ago, IIRC. So, anyone who wants to dump ethernet frames on ISL trunks should be ready for framesize of 1548. Additions/corrections more than welcome. -- Hugh LaMaster, M/S 233-21, Email: lamaster@nren.nasa.gov NASA Ames Research Center Or: lamaster@nas.nasa.gov Moffett Field, CA 94035-1000 Or: lamaster@george.arc.nasa.gov Phone: 650/604-1056 Disc: Unofficial, personal *opinion*. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 4 21: 8: 2 2000 Delivered-To: freebsd-net@freebsd.org Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by builder.freebsd.org (Postfix) with SMTP id 2EED54282 for ; Fri, 4 Feb 2000 21:08:01 -0800 (PST) Received: (qmail 24061 invoked by uid 8031); 5 Feb 2000 05:08:12 -0000 Message-ID: <20000205050812.24060.qmail@scam.xcf.berkeley.edu> To: Brian Somers Cc: freebsd-net@FreeBSD.ORG Subject: Re: Non-blocking sockets and network outages In-reply-to: Your message of "Fri, 04 Feb 2000 09:08:36 GMT." <200002040908.JAA00756@hak.lan.Awfulhak.org> X-Common-Yaroslav-Version: 2.0 Date: Fri, 04 Feb 2000 21:08:12 -0800 From: Gene Kan Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Keepalives are by default very infrequent: > > This means that the first keepalive won't be sent for 2 hours, at > which point up to 8 will be sent with 75 seconds in between each. If > there are no responses after that, the connection is dropped. Thanks so much! Problem solved. [straight6:~]sysctl -a | grep keep net.inet.ip.keepfaith: 0 net.inet.tcp.keepidle: 75000 net.inet.tcp.keepintvl: 1000 net.inet.tcp.keepinit: 75000 Aggressive, but who puts up with lagged net, anyway? :) (Is there any way to set these intervals per-socket with setsockopt?) Gene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 5 2:18: 4 2000 Delivered-To: freebsd-net@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id 4B5A2456E for ; Sat, 5 Feb 2000 02:17:53 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id DAA00787 for freebsd-net@FreeBSD.ORG; Sat, 5 Feb 2000 03:18:12 -0700 (MST) (envelope-from ken) Date: Sat, 5 Feb 2000 03:18:12 -0700 From: "Kenneth D. Merry" To: freebsd-net@FreeBSD.ORG Subject: Re: anyone know about 802.3x flow control? (SOLVED!) Message-ID: <20000205031812.A755@panzer.kdm.org> References: <20000201224859.A38780@panzer.kdm.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="oyUTqETQ0mS9luUI" X-Mailer: Mutt 1.0i In-Reply-To: <20000201224859.A38780@panzer.kdm.org>; from ken@kdm.org on Tue, Feb 01, 2000 at 10:48:59PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii [ I've solved the problem, parts of my original message are included for context ] On Tue, Feb 01, 2000 at 22:48:59 -0700, Kenneth D. Merry wrote: > > I've got an Intel 410T standalone switch for my home network: > > http://www.intel.com/network/products/exp410t.htm > > I've got four machines hooked to it, which have: > > Card Speed Driver > no-name DEC 21140A 100Mbps, full duplex de > SMC 8216 10Mbps, half duplex ed > Intel 82559 100Mbps, full duplex fxp > HP JetDirect 100Mbps, full duplex (it's a printer) > > Everything works fine, but I noticed something odd on the machine with > the Intel ethernet board tonight. It was getting tons of packets every > second (several screens full) from the switch. > > The packets looked like this in tcpdump: > > 22:15:53.313742 0:0:0:0:0:10 1:80:c2:0:0:1 8808 60: > 0001 0000 0000 8808 0001 0000 0000 8808 > 0001 0000 0000 8808 0001 0000 0000 8808 > 0001 0000 0000 8808 0001 0000 0000 > 22:15:53.355673 0:0:0:0:0:10 1:80:c2:0:0:1 8808 60: > 0001 0000 0000 8808 0001 0000 0000 8808 > 0001 0000 0000 8808 0001 0000 0000 8808 > 0001 0000 0000 8808 0001 0000 0000 [ ... ] > So I went into the switch configuration menu (via the serial port) and > disabled flow control on port 10. The packets above stopped. Now, > occasionally (once every minute or two, maybe?) I get packets like this: [ ... ] > I assume the above storm of packets was due to the "IEEE 802.3x > standards-based flow control." that the switch supports, but what I don't > understand is why the packets kept coming. > > Is this something that the card is supposed to intercept somehow and deal > with, or is it something that the OS is supposed to intercept and deal > with? I'd guess the latter, but I'd like to know more about it, and > perhaps why my switch kept spewing. (Naturally, Intel's web site didn't > have much helpful information that I could find.) Just for the record, I've managed to solve (I think!) the problem. I no longer get the spurious packets, and my throughput seems fine. I spent some time looking through the Linux driver for the EtherExpress Pro boards, and found that there *is* a flow control setting on the card, and that it wasn't being set in the fxp driver. The attached patch seems to work fine for me, but there are a few caveats with it: 1. I don't know what the bits do, or whether all of them are necessary for flow control. 2. I have only tested this on my 82559 "InBusiness" board, so I don't know what it will do to say a vanilla 82557. 3. The Linux driver has some sort of timeout routine that checks to see if the link is down, and then queries the PHY about the flow control settings, and optionally changes the flow control setting on the chip. I don't know whether that timeout routine is called regularly, in a polling type manner, or whether it is more like the watchdog routines in BSD network drivers. It doesn't quite look to be the equivalent of the BSD watchdog routines, so I didn't see an analogous routine in the fxp driver to put in the flow control check. Anyway, here's the patch, it works for me, and maybe it'll help someone else out. Ken -- Kenneth Merry ken@kdm.org --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="if_fxp.flow_control.20000205" ==== //depot/FreeBSD-ken/src/sys/pci/if_fxp.c#2 - /a/ken/perforce/FreeBSD-ken/src/sys/pci/if_fxp.c ==== *** /tmp/tmp.568.0 Sat Feb 5 02:53:13 2000 --- /a/ken/perforce/FreeBSD-ken/src/sys/pci/if_fxp.c Sat Feb 5 02:33:33 2000 *************** *** 1427,1432 **** --- 1427,1433 ---- cbp->stripping = !prm; /* truncate rx packet to byte count */ cbp->padding = 1; /* (do) pad short tx packets */ cbp->rcv_crc_xfer = 0; /* (don't) xfer CRC to host */ + cbp->flow_control = 0x3d; /* turn on 802.3x flow control */ cbp->force_fdx = 0; /* (don't) force full duplex */ cbp->fdx_pin_en = 1; /* (enable) FDX# pin */ cbp->multi_ia = 0; /* (don't) accept multiple IAs */ ==== //depot/FreeBSD-ken/src/sys/pci/if_fxpreg.h#2 - /a/ken/perforce/FreeBSD-ken/src/sys/pci/if_fxpreg.h ==== *** /tmp/tmp.568.1 Sat Feb 5 02:53:13 2000 --- /a/ken/perforce/FreeBSD-ken/src/sys/pci/if_fxpreg.h Sat Feb 5 02:52:29 2000 *************** *** 161,167 **** padding:1, rcv_crc_xfer:1, :5; ! volatile u_int :6, force_fdx:1, fdx_pin_en:1; volatile u_int :6, --- 161,172 ---- padding:1, rcv_crc_xfer:1, :5; ! /* ! * IEEE 802.3x flow control: ! * 0 == off ! * 0x3d == on ! */ ! volatile u_int flow_control:6, force_fdx:1, fdx_pin_en:1; volatile u_int :6, --oyUTqETQ0mS9luUI-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 5 6:46:50 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-22.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.150]) by builder.freebsd.org (Postfix) with ESMTP id C2179439C for ; Sat, 5 Feb 2000 06:46:45 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id OAA04471; Sat, 5 Feb 2000 14:47:08 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id OAA35690; Sat, 5 Feb 2000 14:47:07 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002051447.OAA35690@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gene Kan Cc: Brian Somers , freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Non-blocking sockets and network outages In-Reply-To: Message from Gene Kan of "Fri, 04 Feb 2000 21:08:12 PST." <20000205050812.24060.qmail@scam.xcf.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Feb 2000 14:47:07 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Keepalives are by default very infrequent: > > > > This means that the first keepalive won't be sent for 2 hours, at > > which point up to 8 will be sent with 75 seconds in between each. If > > there are no responses after that, the connection is dropped. > > Thanks so much! Problem solved. > > [straight6:~]sysctl -a | grep keep > net.inet.ip.keepfaith: 0 > net.inet.tcp.keepidle: 75000 > net.inet.tcp.keepintvl: 1000 > net.inet.tcp.keepinit: 75000 > > Aggressive, but who puts up with lagged net, anyway? :) (Is there any > way to set these intervals per-socket with setsockopt?) I don't believe so - a bit of a shame really. I think this sort of thing should be available rather than having to implement at the application level :-( > Gene > -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 5 17:49:55 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-15.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.143]) by builder.freebsd.org (Postfix) with ESMTP id 387D146B6 for ; Sat, 5 Feb 2000 17:49:45 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA66422; Sun, 6 Feb 2000 00:39:33 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA37732; Sun, 6 Feb 2000 00:39:30 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002060039.AAA37732@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Nowlin Cc: freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: PPP handling of multiple connection options (long-ish) In-Reply-To: Message from Mike Nowlin of "Fri, 04 Feb 2000 02:54:29 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Feb 2000 00:39:30 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > (Best subject I could think of... :) ) > > I've been digging into some of the more "rarely used" options in ppp(8) in > 3.4-STABLE, and have a few questions/ideas... > > Got PPP over UDP working between two internet-connected hosts, which I'm > (possibly) planning on using to connect one of our satellite offices to > our LAN -- drop a cheap dynamic-IP'd cable modem line in at the remote > office, and have PPP create a sorta-static address for the remote > machine.. So far, so good. > > Noticing that you can "set device /dev/cuaa0 /dev/cuaa1 /dev/cuaa2" to > have it select the first possible modem, and I'm able to type in > "set device rimmer:6669/udp /dev/cuac04" without generating tons of > errors, will that actually work -- try the direct udp connection first, > and if it times out/fails, try the serial device? It'll work, but not as expected. Ppp goes through the list of devices attempting to ``open'' them. Opening a serial port consists of obtaining the lock and achieving an open(). Opening a udp connection consists of connect()ing the udp socket. The udp open will only fail if nothing's listening. > Assuming THAT works, we come to the dialing/logging-in portion of it... > Obviously, the cable modem won't respond to ATDT555-1212 the same way that > a modem will... It seems to me that although you can specify multiple > serial ports to use, you can only specify one dial chat script... The > chat script required for the modem is "ABORT BUSY...OK-AT-OK > \\dATDT\\T..." (stuff removed), and the chat script for the UDP connection > is "". Is it possible, or would it be helpful for me to add, the ability > to do something like: > > set dial "ATDTblahblah" <-- set the default dial script > set foodial rimmer:6669/udp "" <-- set the dial script for the udp conn. At the moment, ppp doesn't allow this sort of thing :-( It expects all the devices to be of the same type. > ... same with some other values, such as authname, authkey, timeout, > etc... This would also be useful when dealing with multiple serial ports > with modems connected that require completely different dial strings, > or if you want to connect to different ISPs with "ppp -background anyisp"... > > 98.6% of this is to provide an automatic dial-backup of the UDP-based PPP > connection -- if somebody at MCI decides to trip over another cable, PPP > will blow up, try the UDP connection again, fail, and then try dialing > directly into the main LAN over the modem... If THAT fails, (like if the > corporate head office goes up in flames, which might not be a bad idea), > try dialing into a local ISP instead. > > > > Now that I've typed all this in, I realize that this could be done with > "ppp -background" and checking the return value, but I'll send it anyway.. > Some of the ideas still make sense, such as the different dial strings for > different modems...... :) Indeed. I'll put it on my TODO list, but that's a pretty big list... Bear in mind that with PPPoUDP, the server side is a bit stupid at the moment and doesn't realize when other hosts talk to the same udp port - allowing anybody to interfere with your conversation. This is dangerous and needs to be fixed. The udp device needs to do more processing on the sockaddr obtained from the recvfrom() in udp_RecvFrom(), and each udp link needs to know of the existence of all other udp links - passing packets to other link input routines as necessary and creating new incoming udp links when required. This should be fairly easy, but also fairly easy to screw up... > --mike -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 5 18:19: 9 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-55.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.183]) by builder.freebsd.org (Postfix) with ESMTP id B9A6346BB for ; Sat, 5 Feb 2000 18:18:46 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA72652; Sun, 6 Feb 2000 00:54:02 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA37872; Sun, 6 Feb 2000 00:53:59 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002060053.AAA37872@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dermot McNally Cc: freebsd-net@FreeBSD.org, Brian Somers , Julian Elischer Subject: Re: PPPoE connection almost working In-Reply-To: Message from Dermot McNally of "Sat, 05 Feb 2000 00:25:50 +0100." <4.2.0.58.20000205001643.00afb778@tim> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Feb 2000 00:53:59 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > I've been following the discussions so far on the development of PPPoE > support and the experience of users so far. This week, I finally got my > ADSL service connected (Deutsche Telekom's T-DSL service with Internet > access through T-Online). I can connect using Windows, so I'm now trying to > get it going under FreeBSD. The connect gets part of the way, then goes no > further. My best guess is that I either need to give a Service name (in > which case, anybody know what it is?) or I'm seeing the same kind of MAC > address affinity that other users reported. Hopefully my tcpdump and log > outputs will help somebody to tell me where the problem might lie. > Basically, I get a PADO from the provider, and then nothing further > happens. I'm using a quite recent version of stable. > > Any ideas? > > Config: > > dsl: > set device PPPoE:ed0 > set mru 1492 > set mtu 1942 Spot the deliberate mistake... hence the warning in the log :*] > deny chap > accept pap > set speed sync > set cd 5 > enable lqr > set redial 0 0 > set dial > add 0 0 HISADDR > set login > set authname xxxxxxxxxxxxxxxxxxxxxxxx > set authkey xxxxxxxxxxxxxx > set timeout 120 > enable dns > > > 23:14:41.096562 0:0:e8:4f:be:4b Broadcast 8863 32: PPPoE PADI v1, type 1, > sess 0 len 12 [Service-Name] [Host-Uniq 004888c0] > 23:14:41.141794 0:d0:c0:f9:b6:23 0:0:e8:4f:be:4b 8863 67: PPPoE PADO v1, > type 1, sess 0 len 47 [Service-Name] [Host-Uniq 004888c0] [AC-Name > MUNC12-nrp2] [AC-Cookie 372992470f60c417cd68e17dcde89eb4] This is the sort of thing I get when testing locally - the -current tcpdump looks a bit different as it's been upgraded and the tcpdump people added pppoe support (they mustn't have liked the look of my output :-): 00:45:09.541584 PPPoE PADI [Service-Name "pppoe-in"] [Host-Uniq UTF8] 00:45:09.547521 PPPoE PADO [AC-Name "dev"] [Service-Name "pppoe-in"] [Host-Uniq UTF8] [AC-Cookie UTF8] 00:45:09.547613 PPPoE PADR [Service-Name "pppoe-in"] [AC-Cookie UTF8] [AC-Name "dev"] [Host-Uniq UTF8] 00:45:09.547876 PPPoE PADS [ses 0xa] [AC-Name "dev"] [Service-Name "pppoe-in"] [Host-Uniq UTF8] [AC-Cookie UTF8] 00:45:11.277897 PPPoE [ses 0xa] LCP ConfReq id=0x1 00:45:11.284368 PPPoE [ses 0xa] LCP ConfReq id=0x1 00:45:11.284465 PPPoE [ses 0xa] LCP ConfAck id=0x1 00:45:11.334003 PPPoE [ses 0xa] LCP ConfAck id=0x1 00:45:11.335013 PPPoE [ses 0xa] LQM 00:45:11.335956 PPPoE [ses 0xa] proto-0x80fd 00:45:11.336902 PPPoE [ses 0xa] IPCP 00:45:11.343641 PPPoE [ses 0xa] LQM [.....] So as you can see, the local side *should* be sending a PADR. [.....] > Feb 5 00:21:59 tim ppp[581]: tun0: Warning: deflink: Reducing MTU to 1492 > Feb 5 00:21:59 tim ppp[581]: tun0: Phase: deflink: Connected! > Feb 5 00:21:59 tim ppp[581]: tun0: Phase: deflink: opening -> dial > Feb 5 00:21:59 tim ppp[581]: tun0: Phase: deflink: dial -> carrier > Feb 5 00:22:04 tim ppp[581]: tun0: Phase: deflink: Disconnected! > Feb 5 00:22:04 tim ppp[581]: tun0: Phase: deflink: carrier -> hangup [.....] I don't really know why the PPPoE node isn't responding to the PADO. it looks good from here. Are there any odd looking kernel messages on your console or in /var/log/messages ? I've cc'd Julian as he's the netgraph guru. Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 6 8: 6:28 2000 Delivered-To: freebsd-net@freebsd.org Received: from roam.psg.com (mg128-107.ricochet.net [204.179.128.107]) by builder.freebsd.org (Postfix) with ESMTP id 678A53D07 for ; Sun, 6 Feb 2000 08:06:10 -0800 (PST) Received: from randy by roam.psg.com with local (Exim 3.12 #1) id 12HUCM-0000Zg-00 for freebsd-net@freebsd.org; Sun, 06 Feb 2000 08:06:06 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-net@freebsd.org Subject: Re: backoff recovery? Message-Id: Date: Sun, 06 Feb 2000 08:06:06 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org the following message may have been missed in the excitement of stream.c. i have retested, and *really* do believe we see non-recovery from backoff. randy From: Randy Bush To: freebsd-net@freebsd.org Subject: backoff recovery? Date: Fri, 21 Jan 2000 10:33:29 -0800 Message-Id: on a metricom in a san jose hotel. really bad link packet loss. stack's response to the poor link seemed a bit strange to me. so i sent the traces to some friends, and in discussion with vern, ... From: Vern Paxson To: Randy Bush > you may or not be interested in a trace. Interesting trace. I don't think the basic problem is SCP/SSH. From the look of it, there's (1) significant packet loss; (2) a bug in the TCP that it isn't collapsing down the exponentially backed-off timer after the retransmitted data is acked (this surprises me in a stack as mature as FreeBSD); (3) a shutdown bug in which one side gets stuck sending FINs and they don't elicit FIN-acks or RSTs (perhaps they're being dropped due to an erroneous conclusion that their timestamp is bad). It may be that SCP is suffering from more loses than FTP because it's not managing to packetize its data well, and that could in turn reflect interactions between crypto operations and buffering; but I don't know whether in the trace it actually makes it out of its initial crypto negotiation or not. Hmmmm, a thought: perhaps Metricom is particularly bad at dealing with bidirectional transfers, and the fact that SCP is doing that initially (and some of it collides, due to retransmissions, due in turn to the loss) means it does significantly worse than the unidirectional FTP data transfer, which also suffers from loss, but not as bad. Dunno ... Vern of course, the horrible link may be obscuring things. the traces ... 204.179.135.13 is 3.4+PAO 147.28.0.39 is 4.0-current a few weeks old 09:11:11.471846 204.179.135.13.970 > 147.28.0.39.22: F 2285079120:2285079120(0) ack 3637246625 win 17376 (DF) [tos 0x8] 09:11:14.929037 204.179.137.61.969 > 147.28.0.39.22: S 2415896350:2415896350(0) win 16384 (DF) 09:11:17.873883 204.179.137.61.969 > 147.28.0.39.22: S 2415896350:2415896350(0) win 16384 (DF) 09:11:18.175014 147.28.0.39.22 > 204.179.137.61.969: S 3786450220:3786450220(0) ack 2415896351 win 17376 (DF) 09:11:18.175116 204.179.137.61.969 > 147.28.0.39.22: . ack 1 win 17376 (DF) 09:11:18.285493 147.28.0.39.22 > 204.179.137.61.969: . ack 1 win 17376 (DF) 09:11:19.873923 204.179.135.13.970 > 147.28.0.39.22: F 0:0(0) ack 1 win 17376 (DF) [tos 0x8] 09:11:20.415333 147.28.0.39.22 > 204.179.137.61.969: P 1:16(15) ack 1 win 17376 (DF) [tos 0x10] 09:11:20.415768 204.179.137.61.969 > 147.28.0.39.22: P 1:16(15) ack 16 win 17376 (DF) [tos 0x10] 09:11:30.874292 204.179.137.61.969 > 147.28.0.39.22: P 1:16(15) ack 16 win 17376 (DF) [tos 0x10] 09:11:31.685822 147.28.0.39.22 > 204.179.137.61.969: P 16:292(276) ack 16 win 17376 (DF) [tos 0x10] 09:11:31.696890 147.28.0.39.22 > 204.179.137.61.969: . ack 16 win 17376 (DF) [tos 0x10] 09:11:31.711505 204.179.137.61.969 > 147.28.0.39.22: P 16:172(156) ack 292 win 17376 (DF) [tos 0x10] 09:11:35.495767 147.28.0.39.22 > 204.179.137.61.969: . ack 172 win 17376 (DF) [tos 0x10] 09:11:35.615775 147.28.0.39.22 > 204.179.137.61.969: P 292:304(12) ack 172 win 17376 (DF) [tos 0x10] 09:11:35.615964 204.179.137.61.969 > 147.28.0.39.22: P 172:192(20) ack 304 win 17376 (DF) [tos 0x10] 09:11:36.874418 204.179.135.13.970 > 147.28.0.39.22: F 0:0(0) ack 1 win 17376 (DF) [tos 0x8] 09:11:49.206191 147.28.0.39.22 > 204.179.137.61.969: P 304:376(72) ack 192 win 17376 (DF) [tos 0x10] 09:11:49.207551 204.179.137.61.969 > 147.28.0.39.22: P 192:348(156) ack 376 win 17376 (DF) [tos 0x10] 09:11:49.736176 147.28.0.39.22 > 204.179.137.61.969: P 376:516(140) ack 348 win 17376 (DF) [tos 0x10] 09:11:49.738303 147.28.0.39.22 > 204.179.137.61.969: P 516:528(12) ack 348 win 17376 (DF) [tos 0x10] 09:11:49.874830 204.179.137.61.969 > 147.28.0.39.22: . ack 528 win 17376 (DF) [tos 0x10] 09:11:58.731953 204.179.137.61.1323 > 192.96.22.18.25: S 2424678315:2424678315(0) win 16384 (DF) 09:12:00.266387 192.96.22.18.25 > 204.179.137.61.1323: R 0:0(0) ack 2424678316 win 0 09:12:10.875442 204.179.135.13.970 > 147.28.0.39.22: F 0:0(0) ack 1 win 17376 (DF) [tos 0x8] 09:12:12.761727 204.179.137.61.969 > 147.28.0.39.22: P 348:376(28) ack 528 win 17376 (DF) [tos 0x10] 09:12:13.176893 147.28.0.39.22 > 204.179.137.61.969: P 528:540(12) ack 376 win 17376 (DF) [tos 0x10] 09:12:13.178538 204.179.137.61.969 > 147.28.0.39.22: P 376:412(36) ack 540 win 17376 (DF) [tos 0x8] 09:12:13.666890 147.28.0.39.22 > 204.179.137.61.969: . ack 412 win 17376 (DF) [tos 0x8] 09:12:13.666948 204.179.137.61.969 > 147.28.0.39.22: P 412:432(20) ack 540 win 17376 (DF) [tos 0x8] 09:12:33.876076 204.179.137.61.969 > 147.28.0.39.22: P 412:432(20) ack 540 win 17376 (DF) [tos 0x8] 09:12:37.417574 147.28.0.39.22 > 204.179.137.61.969: . ack 432 win 17376 (DF) [tos 0x8] 09:12:42.677739 147.28.0.39.22 > 204.179.137.61.969: P 540:584(44) ack 432 win 17376 (DF) [tos 0x8] 09:12:42.678810 204.179.137.61.969 > 147.28.0.39.22: P 432:452(20) ack 584 win 17376 (DF) [tos 0x8] 09:12:58.876825 204.179.137.61.969 > 147.28.0.39.22: P 432:452(20) ack 584 win 17376 (DF) [tos 0x8] 09:13:02.168295 147.28.0.39.22 > 204.179.137.61.969: . ack 452 win 17376 (DF) [tos 0x8] 09:13:14.877260 204.179.135.13.970 > 147.28.0.39.22: F 0:0(0) ack 1 win 17376 (DF) [tos 0x8] 09:13:37.277965 204.179.137.61.123 > 129.250.0.49.123: v4 client strat 4 poll 10 prec -28 09:13:53.819596 207.126.101.100.119 > 204.179.130.75.1231: P 1183230998:1183231406(408) ack 57933214 win 33768 (DF) 09:13:53.819647 207.126.101.100.119 > 204.179.130.75.1231: P 0:408(408) ack 1 win 33768 (DF) 09:13:58.754096 204.179.137.61.1324 > 192.96.22.18.25: S 2448056994:2448056994(0) win 16384 (DF) 09:14:01.378531 204.179.137.61.1324 > 192.96.22.18.25: S 2448056994:2448056994(0) win 16384 (DF) 09:14:05.299848 192.96.22.18.25 > 204.179.137.61.1324: R 0:0(0) ack 2448056995 win 0 09:14:18.879117 204.179.135.13.970 > 147.28.0.39.22: F 0:0(0) ack 1 win 17376 (DF) [tos 0x8] 09:14:26.279371 204.179.137.61.123 > 129.250.0.27.123: v4 client strat 4 poll 10 prec -28 09:14:26.650471 129.250.0.27.123 > 204.179.137.61.123: v4 server strat 2 poll 10 prec -24 09:14:28.279422 204.179.137.61.123 > 129.250.0.10.123: v4 client strat 4 poll 10 prec -28 09:14:28.970534 129.250.0.10.123 > 204.179.137.61.123: v4 server strat 2 poll 10 prec -24 09:14:42.279827 204.179.137.61.123 > 129.250.0.49.123: v4 client strat 4 poll 6 prec -28 09:14:42.980932 129.250.0.49.123 > 204.179.137.61.123: v4 server strat 2 poll 6 prec -24 09:15:22.880975 204.179.135.13.970 > 147.28.0.39.22: F 0:0(0) ack 1 win 17376 (DF) [tos 0x8] 09:15:47.281680 204.179.137.61.123 > 129.250.0.49.123: v4 client strat 4 poll 6 prec -28 09:15:47.972895 129.250.0.49.123 > 204.179.137.61.123: v4 server strat 2 poll 6 prec -24 09:15:58.777625 204.179.137.61.1325 > 192.96.22.18.25: S 2470865643:2470865643(0) win 16384 (DF) 09:16:01.382000 204.179.137.61.1325 > 192.96.22.18.25: S 2470865643:2470865643(0) win 16384 (DF) 09:16:05.243302 192.96.22.18.25 > 204.179.137.61.1325: R 0:0(0) ack 2470865644 win 0 09:16:26.882813 204.179.135.13.970 > 147.28.0.39.22: F 0:0(0) ack 1 win 17376 (DF) [tos 0x8] 09:16:35.283077 204.179.137.61.123 > 129.250.0.27.123: v4 client strat 4 poll 7 prec -28 09:16:38.283160 204.179.137.61.123 > 129.250.0.10.123: v4 client strat 4 poll 7 prec -28 09:16:38.843426 129.250.0.10.123 > 204.179.137.61.123: v4 server strat 3 poll 7 prec -24 09:16:53.283585 204.179.137.61.123 > 129.250.0.49.123: v4 client strat 4 poll 6 prec -28 09:17:30.884691 204.179.135.13.970 > 147.28.0.39.22: F 0:0(0) ack 1 win 17376 (DF) [tos 0x8] 09:17:58.800710 204.179.137.61.1326 > 192.96.22.18.25: S 2493553322:2493553322(0) win 16384 (DF) 09:17:59.836675 192.96.22.18.25 > 204.179.137.61.1326: R 0:0(0) ack 2493553323 win 0 09:18:34.886513 204.179.135.13.970 > 147.28.0.39.22: F 0:0(0) ack 1 win 17376 (DF) [tos 0x8] 09:18:38.958300 204.179.137.61 > 147.28.0.39: icmp: echo request 09:18:39.517785 147.28.0.39 > 204.179.137.61: icmp: echo reply 09:18:39.976600 204.179.137.61 > 147.28.0.39: icmp: echo request 09:18:40.986641 204.179.137.61 > 147.28.0.39: icmp: echo request 09:18:41.996658 204.179.137.61 > 147.28.0.39: icmp: echo request 09:18:43.006690 204.179.137.61 > 147.28.0.39: icmp: echo request 09:18:44.016721 204.179.137.61 > 147.28.0.39: icmp: echo request 09:18:44.297894 147.28.0.39 > 204.179.137.61: icmp: echo reply 09:18:47.099336 147.28.0.39 > 204.179.137.61: icmp: echo reply 09:18:47.118111 147.28.0.39 > 204.179.137.61: icmp: echo reply 09:19:38.888379 204.179.135.13.970 > 147.28.0.39.22: F 0:0(0) ack 1 win 17376 (DF) [tos 0x8] 09:19:58.824681 204.179.137.61.1327 > 192.96.22.18.25: S 2517030525:2517030525(0) win 16384 (DF) 09:20:00.010189 192.96.22.18.25 > 204.179.137.61.1327: R 0:0(0) ack 2517030526 win 0 but ftp makes it through, albeit barely 09:20:42.890232 204.179.135.13.970 > 147.28.0.39.22: F 0:0(0) ack 1 win 17376 (DF) [tos 0x8] 09:21:46.892088 204.179.135.13.970 > 147.28.0.39.22: F 0:0(0) ack 1 win 17376 (DF) [tos 0x8] 09:21:58.848083 204.179.137.61.1328 > 192.96.22.18.25: S 2540143257:2540143257(0) win 16384 (DF) 09:22:01.392409 204.179.137.61.1328 > 192.96.22.18.25: S 2540143257:2540143257(0) win 16384 (DF) 09:22:02.813651 192.96.22.18.25 > 204.179.137.61.1328: R 0:0(0) ack 2540143258 win 0 09:22:20.090484 204.179.137.61.969 > 147.28.0.39.22: F 452:452(0) ack 584 win 17376 (DF) [tos 0x8] 09:22:23.284492 147.28.0.39.22 > 204.179.137.61.969: . ack 453 win 17376 (DF) [tos 0x8] 09:22:24.205432 204.179.137.61.1329 > 147.28.0.39.21: S 2544965268:2544965268(0) win 16384 (DF) 09:22:26.893202 204.179.137.61.1329 > 147.28.0.39.21: S 2544965268:2544965268(0) win 16384 (DF) 09:22:30.144783 147.28.0.39.21 > 204.179.137.61.1329: . ack 2544965269 win 17376 (DF) 09:22:30.154422 147.28.0.39.21 > 204.179.137.61.1329: S 3931814626:3931814626(0) ack 2544965269 win 17376 (DF) 09:22:30.154508 204.179.137.61.1329 > 147.28.0.39.21: . ack 1 win 17376 (DF) 09:22:30.714829 147.28.0.39.21 > 204.179.137.61.1329: P 1:53(52) ack 1 win 17376 (DF) [tos 0x10] 09:22:30.893378 204.179.137.61.1329 > 147.28.0.39.21: . ack 53 win 17376 (DF) [tos 0x10] 09:22:50.893919 204.179.135.13.970 > 147.28.0.39.22: R 1:1(0) ack 1 win 17376 (DF) [tos 0x8] 09:22:51.148182 204.179.137.61.1329 > 147.28.0.39.21: P 1:13(12) ack 53 win 17376 (DF) [tos 0x10] 09:22:51.635314 147.28.0.39.21 > 204.179.137.61.1329: P 53:87(34) ack 13 win 17376 (DF) [tos 0x10] 09:22:51.693838 204.179.137.61.1329 > 147.28.0.39.21: . ack 87 win 17376 (DF) [tos 0x10] 09:22:55.495193 204.179.137.61.1329 > 147.28.0.39.21: P 13:28(15) ack 87 win 17376 (DF) [tos 0x10] 09:22:55.965439 147.28.0.39.21 > 204.179.137.61.1329: P 87:114(27) ack 28 win 17376 (DF) [tos 0x10] 09:22:55.966317 204.179.137.61.1329 > 147.28.0.39.21: P 28:34(6) ack 114 win 17376 (DF) [tos 0x10] 09:22:56.435456 147.28.0.39.21 > 204.179.137.61.1329: P 114:153(39) ack 34 win 17376 (DF) [tos 0x10] 09:22:56.493980 204.179.137.61.1329 > 147.28.0.39.21: . ack 153 win 17376 (DF) [tos 0x10] 09:23:15.104327 204.179.137.61.1329 > 147.28.0.39.21: P 34:42(8) ack 153 win 17376 (DF) [tos 0x10] 09:23:27.894970 204.179.137.61.1329 > 147.28.0.39.21: P 34:42(8) ack 153 win 17376 (DF) [tos 0x10] 09:23:28.326360 147.28.0.39.21 > 204.179.137.61.1329: P 153:173(20) ack 42 win 17376 (DF) [tos 0x10] 09:23:28.326557 204.179.137.61.1329 > 147.28.0.39.21: P 42:62(20) ack 173 win 17376 (DF) [tos 0x10] 09:23:40.395254 204.179.137.61.1329 > 147.28.0.39.21: P 42:62(20) ack 173 win 17376 (DF) [tos 0x10] 09:23:42.266777 147.28.0.39.21 > 204.179.137.61.1329: . ack 62 win 17376 (DF) [tos 0x10] 09:23:58.871382 204.179.137.61.1330 > 192.96.22.18.25: S 2562807967:2562807967(0) win 16384 (DF) 09:23:59.067279 147.28.0.39.21 > 204.179.137.61.1329: P 173:184(11) ack 62 win 17376 (DF) [tos 0x10] 09:23:59.067644 204.179.137.61.1329 > 147.28.0.39.21: P 62:89(27) ack 184 win 17376 (DF) [tos 0x10] 09:23:59.757321 147.28.0.39.21 > 204.179.137.61.1329: P 184:214(30) ack 89 win 17376 (DF) [tos 0x10] 09:23:59.758237 204.179.137.61.1329 > 147.28.0.39.21: P 89:109(20) ack 214 win 17376 (DF) [tos 0x10] 09:24:01.395876 204.179.137.61.1330 > 192.96.22.18.25: S 2562807967:2562807967(0) win 16384 (DF) 09:24:03.067125 147.28.0.39.20 > 204.179.137.61.49152: S 3952726335:3952726335(0) win 16384 (DF) [tos 0x8] 09:24:03.067248 204.179.137.61.49152 > 147.28.0.39.20: S 2563803235:2563803235(0) ack 3952726336 win 17376 (DF) 09:24:05.867269 192.96.22.18.25 > 204.179.137.61.1330: R 0:0(0) ack 2562807968 win 0 09:24:05.877391 147.28.0.39.20 > 204.179.137.61.49152: S 3952726335:3952726335(0) win 16384 (DF) [tos 0x8] 09:24:05.877468 204.179.137.61.49152 > 147.28.0.39.20: . ack 1 win 17376 (DF) 09:24:05.887512 147.28.0.39.20 > 204.179.137.61.49152: . ack 1 win 17376 (DF) [tos 0x8] 09:24:05.907514 147.28.0.39.21 > 204.179.137.61.1329: P 214:290(76) ack 109 win 17376 (DF) [tos 0x10] 09:24:06.096008 204.179.137.61.1329 > 147.28.0.39.21: . ack 290 win 17376 (DF) [tos 0x10] 09:24:38.078387 147.28.0.39.21 > 204.179.137.61.1329: P 290:314(24) ack 109 win 17376 (DF) [tos 0x10] 09:24:38.096911 204.179.137.61.1329 > 147.28.0.39.21: . ack 314 win 17352 (DF) [tos 0x10] 09:25:58.894426 204.179.137.61.1331 > 192.96.22.18.25: S 2586126435:2586126435(0) win 16384 (DF) 09:26:01.399330 204.179.137.61.1331 > 192.96.22.18.25: S 2586126435:2586126435(0) win 16384 (DF) 09:26:05.330634 192.96.22.18.25 > 204.179.137.61.1331: R 0:0(0) ack 2586126436 win 0 09:27:58.919306 204.179.137.61.1332 > 192.96.22.18.25: S 2609119057:2609119057(0) win 16384 (DF) 09:28:01.902863 204.179.137.61.1332 > 192.96.22.18.25: S 2609119057:2609119057(0) win 16384 (DF) 09:28:07.903038 204.179.137.61.1332 > 192.96.22.18.25: S 2609119057:2609119057(0) win 16384 (DF) 09:28:19.903405 204.179.137.61.1332 > 192.96.22.18.25: S 2609119057:2609119057(0) win 16384 (DF) 09:28:30.535320 147.28.0.39.20 > 204.179.137.61.49152: . 1:1449(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:30.703622 204.179.137.61.49152 > 147.28.0.39.20: . ack 1449 win 17376 (DF) [tos 0x8] 09:28:31.975336 147.28.0.39.20 > 204.179.137.61.49152: . 1449:2897(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:32.103677 204.179.137.61.49152 > 147.28.0.39.20: . ack 2897 win 17376 (DF) [tos 0x8] 09:28:32.225899 147.28.0.39.20 > 204.179.137.61.49152: . 2897:4345(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:32.303662 204.179.137.61.49152 > 147.28.0.39.20: . ack 4345 win 17376 (DF) [tos 0x8] 09:28:33.265474 147.28.0.39.20 > 204.179.137.61.49152: . 4345:5793(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:33.303715 204.179.137.61.49152 > 147.28.0.39.20: . ack 5793 win 17376 (DF) [tos 0x8] 09:28:33.525895 147.28.0.39.20 > 204.179.137.61.49152: . 5793:7241(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:33.703704 204.179.137.61.49152 > 147.28.0.39.20: . ack 7241 win 17376 (DF) [tos 0x8] 09:28:34.445361 147.28.0.39.20 > 204.179.137.61.49152: . 7241:8689(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:34.503725 204.179.137.61.49152 > 147.28.0.39.20: . ack 8689 win 17376 (DF) [tos 0x8] 09:28:34.835355 147.28.0.39.20 > 204.179.137.61.49152: . 8689:10137(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:34.903840 204.179.137.61.49152 > 147.28.0.39.20: . ack 10137 win 17376 (DF) [tos 0x8] 09:28:35.445385 147.28.0.39.20 > 204.179.137.61.49152: . 10137:11585(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:35.503752 204.179.137.61.49152 > 147.28.0.39.20: . ack 11585 win 17376 (DF) [tos 0x8] 09:28:36.615475 147.28.0.39.20 > 204.179.137.61.49152: . 11585:13033(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:36.703808 204.179.137.61.49152 > 147.28.0.39.20: . ack 13033 win 17376 (DF) [tos 0x8] 09:28:37.206061 147.28.0.39.20 > 204.179.137.61.49152: . 13033:14481(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:37.303826 204.179.137.61.49152 > 147.28.0.39.20: . ack 14481 win 17376 (DF) [tos 0x8] 09:28:37.465458 147.28.0.39.20 > 204.179.137.61.49152: . 14481:15929(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:37.503830 204.179.137.61.49152 > 147.28.0.39.20: . ack 15929 win 17376 (DF) [tos 0x8] 09:28:37.735460 147.28.0.39.20 > 204.179.137.61.49152: . 15929:17377(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:37.903925 204.179.137.61.49152 > 147.28.0.39.20: . ack 17377 win 17376 (DF) [tos 0x8] 09:28:38.335467 147.28.0.39.20 > 204.179.137.61.49152: . 17377:18825(1448) ack 1 win 17376 (DF) [tos 0x8] 09:28:38.503862 204.179.137.61.49152 > 147.28.0.39.20: . ack 18825 win 17376 (DF) [tos 0x8] 09:28:38.745216 147.28.0.39.20 > 204.179.137.61.49152: FP 18825:20248(1423) ack 1 win 17376 (DF) [tos 0x8] 09:28:38.745297 204.179.137.61.49152 > 147.28.0.39.20: . ack 20249 win 15953 (DF) [tos 0x8] 09:28:38.746658 204.179.137.61.49152 > 147.28.0.39.20: F 1:1(0) ack 20249 win 17376 (DF) [tos 0x8] 09:28:38.746937 204.179.137.61.1329 > 147.28.0.39.21: P 109:129(20) ack 314 win 17376 (DF) [tos 0x10] 09:28:39.405454 147.28.0.39.20 > 204.179.137.61.49152: . ack 2 win 17376 (DF) [tos 0x8] 09:28:39.415372 147.28.0.39.21 > 204.179.137.61.1329: P 314:334(20) ack 129 win 17376 (DF) [tos 0x10] 09:28:39.503877 204.179.137.61.1329 > 147.28.0.39.21: . ack 334 win 17376 (DF) [tos 0x10] 09:28:43.904094 204.179.137.61.1332 > 192.96.22.18.25: S 2609119057:2609119057(0) win 16384 (DF) randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 6 13: 1: 3 2000 Delivered-To: freebsd-net@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by builder.freebsd.org (Postfix) with ESMTP id EC9F23D56 for ; Sun, 6 Feb 2000 13:00:57 -0800 (PST) Received: from localhost ([127.0.0.1] helo=in-addr.com) by noop.colo.erols.net with esmtp (Exim 3.12 #1) id 12HYmE-0005mJ-00; Sun, 06 Feb 2000 15:59:26 -0500 To: Joe Greco Cc: freebsd-net@freebsd.org From: Gary Palmer Subject: Re: dc driver, SNMP, etc. In-Reply-To: Message from Joe Greco of "Fri, 04 Feb 2000 09:59:17 CST." <200002041559.JAA38965@aurora.sol.net> Date: Sun, 06 Feb 2000 15:59:25 -0500 Message-ID: <22214.949870765@in-addr.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Joe Greco wrote in message ID <200002041559.JAA38965@aurora.sol.net>: > First, does anyone know if UCD-SNMP will be updated to work with 4.0, > since it appears that it is marked BROKEN? I understand that the dc > driver will not be backported to 3.x (or I'd go that route). I tried my best with the ucd-snmp agent, and had to give up after it went into a realloc loop and I couldn't track back to why it was doing that. It works for the most part, just don't snmpwalk it :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 6 15:12:59 2000 Delivered-To: freebsd-net@freebsd.org Received: from prserv.net (out2.prserv.net [32.97.166.32]) by builder.freebsd.org (Postfix) with ESMTP id 242363E67 for ; Sun, 6 Feb 2000 15:12:56 -0800 (PST) Received: from TIGGER ([139.92.4.179]) by prserv.net (out2) with SMTP id <2000020623133122902n8mupe>; Sun, 6 Feb 2000 23:13:33 +0000 Message-Id: <4.2.0.58.20000207000333.00b04c70@tim> X-Sender: dermot@tim X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 07 Feb 2000 00:16:12 +0100 To: Brian Somers From: Dermot McNally Subject: Re: PPPoE connection almost working Cc: freebsd-net@FreeBSD.org, Brian Somers , Julian Elischer In-Reply-To: <200002060053.AAA37872@hak.lan.Awfulhak.org> References: <4.2.0.58.20000205001643.00afb778@tim> 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 00:53 06.02.2000 +0000, Brian Somers wrote: > > dsl: > > set device PPPoE:ed0 > > set mru 1492 > > set mtu 1942 > >Spot the deliberate mistake... hence the warning in the log :*] Yup, I spotted that too afterwards. Fixing it cured the warning, as you'd expect, but had otherwise no effect. > > 23:14:41.096562 0:0:e8:4f:be:4b Broadcast 8863 32: PPPoE PADI v1, type 1, > > sess 0 len 12 [Service-Name] [Host-Uniq 004888c0] > > 23:14:41.141794 0:d0:c0:f9:b6:23 0:0:e8:4f:be:4b 8863 67: PPPoE PADO v1, > > type 1, sess 0 len 47 [Service-Name] [Host-Uniq 004888c0] [AC-Name > > MUNC12-nrp2] [AC-Cookie 372992470f60c417cd68e17dcde89eb4] > >This is the sort of thing I get when testing locally - the -current >tcpdump looks a bit different as it's been upgraded and the tcpdump >people added pppoe support (they mustn't have liked the look of my >output :-): Some people are just fussy - your output beats what was there before. >So as you can see, the local side *should* be sending a PADR. That's what I would have thought. One difference between us is that the PADO in your case specifies a service name, whereas mine doesn't (nor does my PADI, because I don't know what name to use...). >I don't really know why the PPPoE node isn't responding to the PADO. >it looks good from here. > >Are there any odd looking kernel messages on your console or in >/var/log/messages ? [checks] Nope. Right, I think I'll do the following: * Assume that MAC Address affinity isn't the problem - if it was, I probably wouldn't get a PADO, right? * Update the box to current. I wanted to do it anyway, and it'll bring my configuration a little closer to yours. * If I really have to, I'll try packet-sniffing a working connection from Windows. This will be a pain, because the "modem" Telekom supplies is intended to connect direct to a NIC, so to connect it correctly to a hub requires a crossed over cable that I don't currently have. Still, if we don't get anywhere by other means, I'll try this route. It will at least tell me if the official software specifies a service name in its PADI. Thanks for the ideas (not to mention the software), Dermot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 7 5:21: 1 2000 Delivered-To: freebsd-net@freebsd.org Received: from svstud.win.tue.nl (svstud.win.tue.nl [131.155.69.100]) by builder.freebsd.org (Postfix) with ESMTP id 69F3B3EC3 for ; Mon, 7 Feb 2000 05:20:57 -0800 (PST) Received: from n135.dial.tue.nl [131.155.209.134] by svstud.win.tue.nl (8.8.8) id OAA17989 (SMTP). Mon, 7 Feb 2000 14:21:34 +0100 (MET) Message-ID: <000101bf716e$253477c0$0100000a@orion> From: "Laurens Vrijnsen" To: Cc: Subject: RE: fxp driver causing lockup Date: Mon, 7 Feb 2000 09:38:02 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Wes! Thank you very much for your email of March 18, 1999 to the freebsd-net list! Your fix of if_fxp.c allowed me to start using my i82557 ethernet controller. Here's some data on my box: I have an IBM PC300PL (Pentium 233) with an onboard i82557 chipset. I'm still using FreeBSD-3.1 (but waiting for my 3.4-copy). The kernel compiled very well without the fix and ifconfig recognized the interface. BUT, as soon as I ran the command ifconfig fxp0 inet 10.0.0.1 netmask 0xffffff00 (or any other inet options...) the computer simply halted operation. Changing the source (pci/if_fxp.c) was the solution. For some reason, your diff was not handled well by patch (chunks 2 and 3 failed), but vi does the job as well :-) A copy of this is sent to freebsd-net because that's where I found your patch (thanks to egroups.com). I hope that your e-mail may help some more people having problems with their fxp-driver. Thanks again! Best wishes, _-= Laurens Vrijnsen =-_ (l.j.g.vrijnsen@stud.tue.nl) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 7 8:30: 0 2000 Delivered-To: freebsd-net@freebsd.org Received: from mc-qout4.whowhere.com (mc-qout4.whowhere.com [209.185.123.18]) by builder.freebsd.org (Postfix) with SMTP id 56D8E3F59 for ; Mon, 7 Feb 2000 08:29:57 -0800 (PST) Received: from Unknown/Local ([?.?.?.?]) by my-deja.com; Sun Feb 6 21:17:21 2000 To: freebsd-net@FreeBSD.org Date: Sun, 06 Feb 2000 21:17:21 -0800 From: "gbnaidu " Message-ID: Mime-Version: 1.0 X-Sent-Mail: off X-Mailer: MailCity Service Subject: How to get outgoing interface... X-Sender-Ip: 164.164.56.2 Organization: My Deja Email (http://www.my-deja.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Length: 764 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am trying to dump the routing table using the sysctl system call. I am able to get the destination address, gateway, mask all these entries. But How do I get the outgoing interface for a particular entry in the routing table? One way I could think of is to try to find the interface on my system whose subnet id is same as the subnet id of the gateway for a routing entry.This should work because the gateway should be directly connnected to my system through on of the interfaces. Is this correct? Is there any other simple way to find the outgoing interface for a routing entry? Please reply to: gbnaidu@sasi.com and to the list also. thanks --gb --== Sent via Deja.com http://www.deja.com/ ==-- Share what you know. Learn what you don't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 7 8:42:59 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by builder.freebsd.org (Postfix) with ESMTP id 2F7394007 for ; Mon, 7 Feb 2000 08:42:42 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA27059; Mon, 7 Feb 2000 11:42:26 -0500 (EST) (envelope-from wollman) Date: Mon, 7 Feb 2000 11:42:26 -0500 (EST) From: Garrett Wollman Message-Id: <200002071642.LAA27059@khavrinen.lcs.mit.edu> To: "gbnaidu " Cc: freebsd-net@FreeBSD.ORG Subject: How to get outgoing interface... In-Reply-To: References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: [Paragraph reformatted for legibility. In the future, please press return at the end of each 72-character line.] > I am trying to dump the routing table using the sysctl system > call. I am able to get the destination address, gateway, mask all > these entries. But How do I get the outgoing interface for a > particular entry in the routing table? Keep on looking in the routing message. A typical response will look like this: sockaddrs: default anacreon default fxp0:0.a0.c9.3c.76.5c khavrinen You have found the first three sockaddrs in the message; the RTA_IFP sockaddr will tell you which interface is being used, and the RTA_IFA one will tell you the IP address configured on that interface. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 7 9: 2:39 2000 Delivered-To: freebsd-net@freebsd.org Received: from zirafe.carrier.kiev.ua (sivka.carrier.kiev.ua [193.193.193.101]) by builder.freebsd.org (Postfix) with ESMTP id 168D73F9F for ; Mon, 7 Feb 2000 09:02:35 -0800 (PST) Received: from mails.itci.kiev.ua (gw1.itci.kiev.ua [62.244.54.196]) by zirafe.carrier.kiev.ua (8.Who.Cares/Kilkenny_is_better) with ESMTP id TAG37563 for ; Mon, 7 Feb 2000 19:00:37 +0200 (EET) (envelope-from samj@itcj.kiev.ua) Received: from primsrv (primsrv.itci.kiev.ua [62.244.54.220]) by mails.itci.kiev.ua (8.8.8/8.8.8) with ESMTP id SAA01327 for ; Mon, 7 Feb 2000 18:58:26 +0200 (EET) (envelope-from samj@itcj.kiev.ua) Message-Id: <200002071658.SAA01327@mails.itci.kiev.ua> From: "Yuriy" To: Subject: mpd via dump modems Date: Mon, 7 Feb 2000 18:59:52 +0200 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am use mpd-2.0b2 for permanent connection with my provider. When I have set my modems with script for control via replys from modem all work fine. But when i set my modem in dump mode without scripts or with script for null-modems connect is not setting. Both modems send each other SendConfigReq and never das not happen. How can I do connection wia mpd without programming modems ? Any ideas. Thanks on advance. _______ Yuriy Samartsev, Firm ITC Ltd, http://www.itci.net. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 7 10:54:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by builder.freebsd.org (Postfix) with ESMTP id C92C04352 for ; Mon, 7 Feb 2000 10:54:12 -0800 (PST) Received: from cichlids.com (pC19F546D.dip0.t-ipconnect.de [193.159.84.109]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id SAA12872 for ; Mon, 7 Feb 2000 18:30:12 +0100 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 7F3E1AC26 for ; Mon, 7 Feb 2000 18:30:33 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id SAA04259 for net@freebsd.org; Mon, 7 Feb 2000 18:31:15 +0100 (CET) (envelope-from alex) Date: Mon, 7 Feb 2000 18:31:15 +0100 From: Alexander Langer To: net@freebsd.org Subject: IPV6_DROP_MEMBERSHIP not defined Message-ID: <20000207183115.A4246@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! This is not defined in -current yet. Please do. Someone :) it's used by programs, as port net/libunp. And I think, Stevens knows, which consts need to be defined :) Thanks Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 7 13: 7:29 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-12.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.140]) by builder.freebsd.org (Postfix) with ESMTP id 66082408E for ; Mon, 7 Feb 2000 13:07:21 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA04724; Mon, 7 Feb 2000 21:05:06 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA03261; Mon, 7 Feb 2000 21:05:12 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002072105.VAA03261@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dermot McNally Cc: Brian Somers , freebsd-net@freebsd.org, Julian Elischer Subject: Re: PPPoE connection almost working In-Reply-To: Message from Dermot McNally of "Mon, 07 Feb 2000 00:16:12 +0100." <4.2.0.58.20000207000333.00b04c70@tim> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Feb 2000 21:05:12 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > At 00:53 06.02.2000 +0000, Brian Somers wrote: > > > > > dsl: > > > set device PPPoE:ed0 > > > set mru 1492 > > > set mtu 1942 > > > >Spot the deliberate mistake... hence the warning in the log :*] > > Yup, I spotted that too afterwards. Fixing it cured the warning, as you'd > expect, but had otherwise no effect. > > > > 23:14:41.096562 0:0:e8:4f:be:4b Broadcast 8863 32: PPPoE PADI v1, type 1, > > > sess 0 len 12 [Service-Name] [Host-Uniq 004888c0] > > > 23:14:41.141794 0:d0:c0:f9:b6:23 0:0:e8:4f:be:4b 8863 67: PPPoE PADO v1, > > > type 1, sess 0 len 47 [Service-Name] [Host-Uniq 004888c0] [AC-Name > > > MUNC12-nrp2] [AC-Cookie 372992470f60c417cd68e17dcde89eb4] > > > >This is the sort of thing I get when testing locally - the -current > >tcpdump looks a bit different as it's been upgraded and the tcpdump > >people added pppoe support (they mustn't have liked the look of my > >output :-): > > Some people are just fussy - your output beats what was there before. > > > >So as you can see, the local side *should* be sending a PADR. > > That's what I would have thought. One difference between us is that the > PADO in your case specifies a service name, whereas mine doesn't (nor does > my PADI, because I don't know what name to use...). > > >I don't really know why the PPPoE node isn't responding to the PADO. > >it looks good from here. > > > >Are there any odd looking kernel messages on your console or in > >/var/log/messages ? > > [checks] Nope. > > Right, I think I'll do the following: > > * Assume that MAC Address affinity isn't the problem - if it was, I > probably wouldn't get a PADO, right? I would think so. > * Update the box to current. I wanted to do it anyway, and it'll bring my > configuration a little closer to yours. I believe netgraph is just about the same in both. > * If I really have to, I'll try packet-sniffing a working connection from > Windows. This will be a pain, because the "modem" Telekom supplies is > intended to connect direct to a NIC, so to connect it correctly to a hub > requires a crossed over cable that I don't currently have. Still, if we > don't get anywhere by other means, I'll try this route. It will at least > tell me if the official software specifies a service name in its PADI. You could also try bringing up your own pppoed. It's pretty straight forward - just add a few variables to /etc/rc.conf and take a look at the pppoe profile in /usr/share/examples/ppp/ppp.conf.sample. > Thanks for the ideas (not to mention the software), > Dermot I've cc'd a better email address for Julian - perhaps he's got some suggestions :*] -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 7 13:37: 4 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-56.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.184]) by builder.freebsd.org (Postfix) with ESMTP id 20DAB3E1F for ; Mon, 7 Feb 2000 13:36:59 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA04813; Mon, 7 Feb 2000 21:26:59 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA03499; Mon, 7 Feb 2000 21:27:04 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002072127.VAA03499@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Garrett Wollman Cc: "gbnaidu " , freebsd-net@freebsd.org, brian@hak.lan.Awfulhak.org Subject: Re: How to get outgoing interface... In-Reply-To: Message from Garrett Wollman of "Mon, 07 Feb 2000 11:42:26 EST." <200002071642.LAA27059@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Feb 2000 21:27:04 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > < said: > > [Paragraph reformatted for legibility. In the future, please press > return at the end of each 72-character line.] > > > I am trying to dump the routing table using the sysctl system > > call. I am able to get the destination address, gateway, mask all > > these entries. But How do I get the outgoing interface for a > > particular entry in the routing table? > > Keep on looking in the routing message. A typical response will look > like this: > > sockaddrs: > default anacreon default fxp0:0.a0.c9.3c.76.5c khavrinen > > You have found the first three sockaddrs in the message; the RTA_IFP > sockaddr will tell you which interface is being used, and the RTA_IFA > one will tell you the IP address configured on that interface. FWIW an example can be found in src/usr.sbin/ppp/route.c - clearer (but less functional) than the ifconfig sources IMHO. > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 7 14:41:12 2000 Delivered-To: freebsd-net@freebsd.org Received: from mailout05.sul.t-online.de (mailout05.sul.t-online.de [194.25.134.82]) by builder.freebsd.org (Postfix) with ESMTP id 5C1113D7C for ; Mon, 7 Feb 2000 14:41:04 -0800 (PST) Received: from fwd00.sul.t-online.de by mailout05.sul.t-online.de with smtp id 12HwqH-0007Hg-00; Mon, 7 Feb 2000 23:41:13 +0100 Received: from TIGGER (320096206837-0001@[62.158.207.230]) by fwd00.sul.t-online.de with esmtp id 12HwqF-0pLC9QC; Mon, 7 Feb 2000 23:41:11 +0100 Message-Id: <4.2.0.58.20000207232329.00b06178@tim> X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 07 Feb 2000 23:43:21 +0100 To: Brian Somers From: 320096206837-0001@t-online.de (Dermot McNally) Subject: Re: PPPoE connection almost working Cc: freebsd-net@FreeBSD.ORG, Brian Somers , Julian Elischer In-Reply-To: <200002060053.AAA37872@hak.lan.Awfulhak.org> References: <4.2.0.58.20000205001643.00afb778@tim> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: 320096206837-0001@t-dialin.net Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 00:53 06.02.2000 +0000, Brian Somers wrote: >So as you can see, the local side *should* be sending a PADR. > >[.....] > > Feb 5 00:21:59 tim ppp[581]: tun0: Warning: deflink: Reducing MTU to 1492 > > Feb 5 00:21:59 tim ppp[581]: tun0: Phase: deflink: Connected! > > Feb 5 00:21:59 tim ppp[581]: tun0: Phase: deflink: opening -> dial > > Feb 5 00:21:59 tim ppp[581]: tun0: Phase: deflink: dial -> carrier > > Feb 5 00:22:04 tim ppp[581]: tun0: Phase: deflink: Disconnected! > > Feb 5 00:22:04 tim ppp[581]: tun0: Phase: deflink: carrier -> hangup >[.....] > >I don't really know why the PPPoE node isn't responding to the PADO. >it looks good from here. I can now report success. I updated to current and it Just Worked. I must admit to being very pleasantly surprised - I expected at least one nasty hurdle, and was preparing to dissect the output of tcpdump when I realised there was a lot more of it than there had been before. I looked at ppp and noticed that the link was alive. You can't complain, can you? Anyway, well done to Julian and Brian for the code that does all this. You've done a phenomenal job. The link comes up in a fraction of a second (which is important, since Deutsche Telekom doesn't offer an always-on connection at decent rates) and I've done a test download at 87 K-bytes/s, pretty much on the edge of the claimed bandwidth of my pipe. One further question - with reference to the ppp log below, is it normal that I should have all those LCP entries? They keep repeating as long as the link is up. I can just stop logging them, of course, but is there something else I should tweak instead? Thanks again, Dermot Feb 7 23:04:20 tim ppp[312]: tun0: Command: /dev/tty: dial dsl Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: set device PPPoE:ed0 Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: set mru 1490 Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: set mtu 1490 Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: deny chap Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: accept pap Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: set speed sync Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: set cd 5 Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: enable lqr Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: set redial 0 0 Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: set dial Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: add 0 0 HISADDR Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: set login Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: set authname xxxxxxxxxxxxxxxxxx@t-online.de Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: set authkey ******** Feb 7 23:04:20 tim ppp[312]: tun0: Command: dsl: set timeout 120 Feb 7 23:04:20 tim ppp[312]: tun0: Phase: bundle: Establish Feb 7 23:04:20 tim ppp[312]: tun0: Phase: deflink: closed -> opening Feb 7 23:04:20 tim ppp[312]: tun0: Phase: deflink: Connected! Feb 7 23:04:20 tim ppp[312]: tun0: Phase: deflink: opening -> dial Feb 7 23:04:20 tim ppp[312]: tun0: Phase: deflink: dial -> carrier Feb 7 23:04:21 tim ppp[312]: tun0: Phase: Received NGM_PPPOE_SUCCESS (hook "tun0") Feb 7 23:04:21 tim ppp[312]: tun0: Phase: deflink: carrier -> login Feb 7 23:04:21 tim ppp[312]: tun0: Phase: deflink: login -> lcp Feb 7 23:04:21 tim ppp[312]: tun0: LCP: FSM: Using "deflink" as a transport Feb 7 23:04:21 tim ppp[312]: tun0: LCP: deflink: State change Initial --> Closed Feb 7 23:04:21 tim ppp[312]: tun0: LCP: deflink: State change Closed --> Stopped Feb 7 23:04:21 tim ppp[312]: tun0: LCP: deflink: RecvConfigReq(231) state = Stopped Feb 7 23:04:21 tim ppp[312]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Feb 7 23:04:21 tim ppp[312]: tun0: LCP: MAGICNUM[6] 0x076d5d32 Feb 7 23:04:21 tim ppp[312]: tun0: LCP: deflink: SendConfigReq(1) state = Stopped Feb 7 23:04:21 tim ppp[312]: tun0: LCP: MRU[4] 1490 Feb 7 23:04:21 tim ppp[312]: tun0: LCP: MAGICNUM[6] 0x346e9523 Feb 7 23:04:21 tim ppp[312]: tun0: LCP: QUALPROTO[8] proto c025, interval 30000ms Feb 7 23:04:21 tim ppp[312]: tun0: LCP: deflink: SendConfigAck(231) state = Stopped Feb 7 23:04:21 tim ppp[312]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Feb 7 23:04:21 tim ppp[312]: tun0: LCP: MAGICNUM[6] 0x076d5d32 Feb 7 23:04:21 tim ppp[312]: tun0: LCP: deflink: LayerStart Feb 7 23:04:21 tim ppp[312]: tun0: LCP: deflink: State change Stopped --> Ack-Sent Feb 7 23:04:21 tim ppp[312]: tun0: LCP: deflink: RecvConfigNak(1) state = Ack-Sent Feb 7 23:04:21 tim ppp[312]: tun0: LCP: MRU[4] 1500 Feb 7 23:04:21 tim ppp[312]: tun0: LCP: deflink: SendConfigReq(2) state = Ack-Sent Feb 7 23:04:21 tim ppp[312]: tun0: LCP: MRU[4] 1500 Feb 7 23:04:21 tim ppp[312]: tun0: LCP: MAGICNUM[6] 0x346e9523 Feb 7 23:04:21 tim ppp[312]: tun0: LCP: QUALPROTO[8] proto c025, interval 30000ms Feb 7 23:04:21 tim ppp[312]: tun0: LCP: deflink: RecvConfigAck(2) state = Ack-Sent Feb 7 23:04:21 tim ppp[312]: tun0: LCP: deflink: State change Ack-Sent --> Opened Feb 7 23:04:21 tim ppp[312]: tun0: LCP: deflink: LayerUp Feb 7 23:04:21 tim ppp[312]: tun0: Phase: bundle: Authenticate Feb 7 23:04:21 tim ppp[312]: tun0: Phase: deflink: his = PAP, mine = none Feb 7 23:04:21 tim ppp[312]: tun0: Phase: Pap Output: xxxxxxxxxxxxxx@t-online.de ******** Feb 7 23:04:21 tim ppp[312]: tun0: Phase: Pap Input: SUCCESS () Feb 7 23:04:21 tim ppp[312]: tun0: Phase: deflink: lcp -> open Feb 7 23:04:21 tim ppp[312]: tun0: Phase: bundle: Network Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: FSM: Using "deflink" as a transport Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: deflink: State change Initial --> Closed Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: deflink: LayerStart. Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: deflink: SendConfigReq(1) state = Closed Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: IPADDR[6] 192.168.0.254 Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: deflink: State change Closed --> Req-Sent Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: deflink: RecvConfigReq(244) state = Req-Sent Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: IPADDR[6] 193.158.139.181 Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: deflink: SendConfigAck(244) state = Req-Sent Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: IPADDR[6] 193.158.139.181 Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: deflink: State change Req-Sent --> Ack-Sent Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: deflink: RecvConfigNak(1) state = Ack-Sent Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: IPADDR[6] 62.158.208.217 Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: IPADDR[6] changing address: 192.168.0.254 --> 62.158.208.217 Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: deflink: SendConfigReq(2) state = Ack-Sent Feb 7 23:04:21 tim ppp[312]: tun0: IPCP: IPADDR[6] 62.158.208.217 Feb 7 23:04:22 tim ppp[312]: tun0: IPCP: deflink: RecvConfigAck(2) state = Ack-Sent Feb 7 23:04:22 tim ppp[312]: tun0: IPCP: deflink: State change Ack-Sent --> Opened Feb 7 23:04:22 tim ppp[312]: tun0: IPCP: deflink: LayerUp. Feb 7 23:04:22 tim ppp[312]: tun0: IPCP: myaddr 62.158.208.217 hisaddr = 193.158.139.181 Feb 7 23:04:22 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(1) state = Opened Feb 7 23:04:22 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(1) state = Opened Feb 7 23:04:25 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(2) state = Opened Feb 7 23:04:25 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(2) state = Opened Feb 7 23:04:28 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(3) state = Opened Feb 7 23:04:28 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(3) state = Opened Feb 7 23:04:31 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(4) state = Opened Feb 7 23:04:31 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(4) state = Opened Feb 7 23:04:34 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(5) state = Opened Feb 7 23:04:34 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(5) state = Opened Feb 7 23:04:37 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(6) state = Opened Feb 7 23:04:37 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(6) state = Opened Feb 7 23:04:40 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(7) state = Opened Feb 7 23:04:40 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(7) state = Opened Feb 7 23:04:43 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(8) state = Opened Feb 7 23:04:43 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(8) state = Opened Feb 7 23:04:46 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(9) state = Opened Feb 7 23:04:46 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(9) state = Opened Feb 7 23:04:49 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(10) state = Opened Feb 7 23:04:49 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(10) state = Opened Feb 7 23:04:52 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(11) state = Opened Feb 7 23:04:52 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(11) state = Opened Feb 7 23:04:55 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(12) state = Opened Feb 7 23:04:55 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(12) state = Opened Feb 7 23:04:58 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(13) state = Opened Feb 7 23:04:58 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(13) state = Opened Feb 7 23:05:01 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(14) state = Opened Feb 7 23:05:01 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(14) state = Opened Feb 7 23:05:04 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(15) state = Opened Feb 7 23:05:04 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(15) state = Opened Feb 7 23:05:07 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(16) state = Opened Feb 7 23:05:07 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(16) state = Opened Feb 7 23:05:10 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(17) state = Opened Feb 7 23:05:10 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(17) state = Opened Feb 7 23:05:13 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(18) state = Opened Feb 7 23:05:13 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(18) state = Opened Feb 7 23:05:16 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(19) state = Opened Feb 7 23:05:16 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(19) state = Opened Feb 7 23:05:19 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(20) state = Opened Feb 7 23:05:19 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(20) state = Opened Feb 7 23:05:22 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(21) state = Opened Feb 7 23:05:22 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(21) state = Opened Feb 7 23:05:25 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(22) state = Opened Feb 7 23:05:25 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(22) state = Opened Feb 7 23:05:28 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(23) state = Opened Feb 7 23:05:28 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(23) state = Opened Feb 7 23:05:31 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(24) state = Opened Feb 7 23:05:31 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(24) state = Opened Feb 7 23:05:34 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(25) state = Opened Feb 7 23:05:34 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(25) state = Opened Feb 7 23:05:37 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(26) state = Opened Feb 7 23:05:37 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(26) state = Opened Feb 7 23:05:40 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(27) state = Opened Feb 7 23:05:40 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(27) state = Opened Feb 7 23:05:43 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(28) state = Opened Feb 7 23:05:43 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(28) state = Opened Feb 7 23:05:46 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(29) state = Opened Feb 7 23:05:46 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(29) state = Opened Feb 7 23:05:49 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(30) state = Opened Feb 7 23:05:49 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(30) state = Opened Feb 7 23:05:52 tim ppp[312]: tun0: LCP: deflink: RecvEchoRequest(31) state = Opened Feb 7 23:05:52 tim ppp[312]: tun0: LCP: deflink: SendEchoReply(31) state = Opened Feb 7 23:05:54 tim ppp[312]: tun0: Command: /dev/tty: close Feb 7 23:05:54 tim ppp[312]: tun0: IPCP: deflink: LayerDown: 62.158.208.217 Feb 7 23:05:54 tim ppp[312]: tun0: IPCP: deflink: SendTerminateReq(3) state = Opened Feb 7 23:05:54 tim ppp[312]: tun0: IPCP: deflink: State change Opened --> Closing Feb 7 23:05:54 tim ppp[312]: tun0: IPCP: deflink: RecvTerminateAck(3) state = Closing Feb 7 23:05:54 tim ppp[312]: tun0: IPCP: deflink: LayerFinish. Feb 7 23:05:54 tim ppp[312]: tun0: IPCP: Connect time: 93 secs: 8505 octets in, 4845 octets out Feb 7 23:05:54 tim ppp[312]: tun0: IPCP: total 143 bytes/sec, peak 1167 bytes/sec on Mon Feb 7 23:05:54 2000 Feb 7 23:05:54 tim ppp[312]: tun0: IPCP: deflink: State change Closing --> Closed Feb 7 23:05:54 tim ppp[312]: tun0: Phase: bundle: Terminate Feb 7 23:05:54 tim ppp[312]: tun0: LCP: deflink: LayerDown Feb 7 23:05:54 tim ppp[312]: tun0: LCP: deflink: SendTerminateReq(3) state = Opened Feb 7 23:05:54 tim ppp[312]: tun0: LCP: deflink: State change Opened --> Closing Feb 7 23:05:54 tim ppp[312]: tun0: Phase: deflink: open -> lcp Feb 7 23:05:54 tim ppp[312]: tun0: IPCP: deflink: State change Closed --> Initial Feb 7 23:05:54 tim ppp[312]: tun0: LCP: deflink: RecvTerminateAck(3) state = Closing Feb 7 23:05:54 tim ppp[312]: tun0: LCP: deflink: LayerFinish Feb 7 23:05:54 tim ppp[312]: tun0: LCP: deflink: State change Closing --> Closed Feb 7 23:05:54 tim ppp[312]: tun0: LCP: deflink: State change Closed --> Initial Feb 7 23:05:54 tim ppp[312]: tun0: Phase: deflink: Disconnected! Feb 7 23:05:54 tim ppp[312]: tun0: Phase: deflink: lcp -> logout Feb 7 23:05:54 tim ppp[312]: tun0: Phase: deflink: logout -> hangup Feb 7 23:05:54 tim ppp[312]: tun0: Phase: deflink: Disconnected! Feb 7 23:05:54 tim ppp[312]: tun0: Phase: deflink: Connect time: 94 secs: 9360 octets in, 5771 octets out Feb 7 23:05:54 tim ppp[312]: tun0: Phase: total 160 bytes/sec, peak 1207 bytes/sec on Mon Feb 7 23:05:54 2000 Feb 7 23:05:54 tim ppp[312]: tun0: Phase: deflink: hangup -> closed Feb 7 23:05:54 tim ppp[312]: tun0: Phase: bundle: Dead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 7 15: 7: 4 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-103.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.231]) by builder.freebsd.org (Postfix) with ESMTP id 2CBB04204 for ; Mon, 7 Feb 2000 15:06:58 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA05036; Mon, 7 Feb 2000 23:00:04 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA03978; Mon, 7 Feb 2000 23:00:09 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002072300.XAA03978@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: 320096206837-0001@t-online.de (Dermot McNally) Cc: Brian Somers , freebsd-net@FreeBSD.ORG, Julian Elischer , brian@hak.lan.Awfulhak.org Subject: Re: PPPoE connection almost working In-Reply-To: Message from 320096206837-0001@t-online.de (Dermot McNally) of "Mon, 07 Feb 2000 23:43:21 +0100." <4.2.0.58.20000207232329.00b06178@tim> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Feb 2000 23:00:09 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I can now report success. I updated to current and it Just Worked. I must > admit to being very pleasantly surprised - I expected at least one nasty > hurdle, and was preparing to dissect the output of tcpdump when I realised > there was a lot more of it than there had been before. I looked at ppp and > noticed that the link was alive. You can't complain, can you? Excellent ! I *didn't* expect that :-) > Anyway, well done to Julian and Brian for the code that does all this. > You've done a phenomenal job. The link comes up in a fraction of a second > (which is important, since Deutsche Telekom doesn't offer an always-on > connection at decent rates) and I've done a test download at 87 K-bytes/s, > pretty much on the edge of the claimed bandwidth of my pipe. > > One further question - with reference to the ppp log below, is it normal > that I should have all those LCP entries? They keep repeating as long as > the link is up. I can just stop logging them, of course, but is there > something else I should tweak instead? Hmm, I think I'll move them to the lqm log level. They're strictly LCP, but they're also pretty annoying for someone that wants to see what link characteristics were negotiated.... TODO list ! > Thanks again, > Dermot It's worth it when you get emails from people saying they're happy :-) -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 7 21: 4:17 2000 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by builder.freebsd.org (Postfix) with ESMTP id 6159B4011 for ; Mon, 7 Feb 2000 21:04:13 -0800 (PST) Received: from localhost (condor.v6.kame.net [3ffe:501:4819:2000:2a0:24ff:fe66:1350]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id NAA01077; Tue, 8 Feb 2000 13:54:34 +0900 (JST) Date: Tue, 08 Feb 2000 14:05:17 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: alex@big.endian.de Cc: net@FreeBSD.ORG Subject: Re: IPV6_DROP_MEMBERSHIP not defined In-Reply-To: In your message of "Mon, 7 Feb 2000 18:31:15 +0100" <20000207183115.A4246@cichlids.cichlids.com> References: <20000207183115.A4246@cichlids.cichlids.com> User-Agent: Wanderlust/2.2.15 (More Than Words) Emacs/20.5 Mule/4.0 (HANANOEN) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 21 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> On Mon, 7 Feb 2000 18:31:15 +0100, >>>>> Alexander Langer said: > This is not defined in -current yet. > Please do. Someone :) > it's used by programs, as port net/libunp. > And I think, Stevens knows, which consts need to be defined :) IPV6_ADD_MEMBERSHIP, which was defined in RFC2133, was replaced with IPV6_JOIN_GROUP defined in RFC2553. I think applications should basically migrate to the new macros, and hence the KAME code (on which FreeBSD-current is based) has discarded the old ones includeing IPV6_ADD_MEMBERSHIP. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 7 21:53:13 2000 Delivered-To: freebsd-net@freebsd.org Received: from mc-qout4.whowhere.com (mc-qout4.whowhere.com [209.185.123.18]) by builder.freebsd.org (Postfix) with SMTP id 1F2E53D4D for ; Mon, 7 Feb 2000 21:53:09 -0800 (PST) Received: from Unknown/Local ([?.?.?.?]) by my-deja.com; Mon Feb 7 21:29:55 2000 To: "Garrett Wollman" Date: Mon, 07 Feb 2000 21:29:55 -0800 From: "gbnaidu " Message-ID: Mime-Version: 1.0 Cc: freebsd-net@FreeBSD.ORG X-Sent-Mail: off X-Mailer: MailCity Service Subject: Re: How to get outgoing interface... X-Sender-Ip: 164.164.56.2 Organization: My Deja Email (http://www.my-deja.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Length: 1874 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -- On Mon, 7 Feb 2000 11:42:26 Garrett Wollman wrote: >< said: > >[Paragraph reformatted for legibility. In the future, please press >return at the end of each 72-character line.] > >> I am trying to dump the routing table using the sysctl system >> call. I am able to get the destination address, gateway, mask all >> these entries. But How do I get the outgoing interface for a >> particular entry in the routing table? > >Keep on looking in the routing message. A typical response will look >like this: > >sockaddrs: > default anacreon default fxp0:0.a0.c9.3c.76.5c khavrinen > >You have found the first three sockaddrs in the message; the RTA_IFP >sockaddr will tell you which interface is being used, and the RTA_IFA >one will tell you the IP address configured on that interface. > >-GAWollman I tried looking in to those structures(RTA_IFP)also. But the structure is NULL. This is how I defined: mib[0] = CTL_NET; mib[1] = AF_ROUTE; mib[2] = 0; mib[3] = family; /* AF_INET */ mib[4] = NET_RT_DUMP; mib[5] = 0; /* Here do I need to set any flags? */ After calling sysctl, I am trying to read the structures by checking them whether they are null: rti_info contains all the returned sockaddr structrues by sysctl: if ( (sa = rti_info[RTAX_DST]) != NULL) { process the destination address; if ( (sa = rti_info[RTAX_GATEWAY]) != NULL) Similarly I amtrying to get the name of the interface: if ( (sa = rti_info[RTAX_IFP]) != NULL): here this condition fails. Do I need to give any other information like flags(RTA_IFP) to mib[5]? thank you gb --== Sent via Deja.com http://www.deja.com/ ==-- Share what you know. Learn what you don't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 8 3: 9:50 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by builder.freebsd.org (Postfix) with ESMTP id 441AA41EC for ; Tue, 8 Feb 2000 03:09:47 -0800 (PST) Received: from cichlids.com (pC19F5495.dip0.t-ipconnect.de [193.159.84.149]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id MAA04531; Tue, 8 Feb 2000 12:10:19 +0100 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 25D84AC26; Tue, 8 Feb 2000 12:10:45 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id MAA02723; Tue, 8 Feb 2000 12:11:28 +0100 (CET) (envelope-from alex) Date: Tue, 8 Feb 2000 12:11:28 +0100 From: Alexander Langer To: "JINMEI Tatuya / ?$B?@L@C#:H?(B" Cc: net@FreeBSD.ORG Subject: Re: IPV6_DROP_MEMBERSHIP not defined Message-ID: <20000208121128.A2675@cichlids.cichlids.com> References: <20000207183115.A4246@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from jinmei@isl.rdc.toshiba.co.jp on Tue, Feb 08, 2000 at 02:05:17PM +0900 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake JINMEI Tatuya / ?$B?@L@C#:H?(B (jinmei@isl.rdc.toshiba.co.jp): > > > And I think, Stevens knows, which consts need to be defined :) > IPV6_ADD_MEMBERSHIP, which was defined in RFC2133, was replaced with > IPV6_JOIN_GROUP defined in RFC2553. I think applications should > basically migrate to the new macros, and hence the KAME code (on which > FreeBSD-current is based) has discarded the old ones includeing > IPV6_ADD_MEMBERSHIP. Ah, ok, sorry. I'll patch it then. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 8 3:13:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from prince.net.ebina.hitachi.co.jp (kame196.kame.net [203.178.141.196]) by builder.freebsd.org (Postfix) with ESMTP id 1D0C041CB for ; Tue, 8 Feb 2000 03:13:30 -0800 (PST) Received: from ebina.hitachi.co.jp (localhost [127.0.0.1]) by prince.net.ebina.hitachi.co.jp (8.9.3/3.7W) with SMTP id UAA06835; Tue, 8 Feb 2000 20:14:04 +0900 (JST) From: sumikawa@ebina.hitachi.co.jp Message-Id: <200002081114.UAA06835@prince.net.ebina.hitachi.co.jp> Date: Tue, 8 Feb 2000 20:14:04 +0900 (JST) To: alex@big.endian.de Cc: jinmei@isl.rdc.toshiba.co.jp, net@FreeBSD.ORG Cc: sumikawa@ebina.hitachi.co.jp Subject: Re: IPV6_DROP_MEMBERSHIP not defined In-Reply-To: <20000208121128.A2675@cichlids.cichlids.com> References: <20000207183115.A4246@cichlids.cichlids.com> <20000208121128.A2675@cichlids.cichlids.com> X-Mailer: xcite1.31> Mew version 1.95b10 on Emacs 20.4 / Mule 4.0 (HANANOEN) 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> Ah, ok, sorry. alex> I'll patch it then. I've already made the following patch and send it to the maintainer. Could you try it? --- Munechika SUMIKAWA @ KAME Project / FreeBSD.org Index: Makefile =================================================================== RCS file: /home/ncvs/ports/net/libunp/Makefile,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 Makefile --- Makefile 1999/10/02 19:13:05 1.1.1.1 +++ Makefile 2000/02/08 06:20:29 @@ -8,7 +8,7 @@ DISTNAME= unpv12e PKGNAME= libunp-1.0 -CATEGORIES= net +CATEGORIES= net ipv6 MASTER_SITES= ftp://ftp.kohala.com/pub/rstevens/ \ http://www.cs.columbia.edu/networks98/stevens/ Index: patches/patch-ar =================================================================== RCS file: patch-ar diff -N patch-ar --- /dev/null Tue Feb 8 14:09:55 2000 +++ patch-ar Tue Feb 8 15:20:30 2000 @@ -0,0 +1,11 @@ +--- lib/mcast_leave.c- Tue Feb 8 15:10:50 2000 ++++ lib/mcast_leave.c Tue Feb 8 15:05:53 2000 +@@ -23,7 +23,7 @@ + &((struct sockaddr_in6 *) sa)->sin6_addr, + sizeof(struct in6_addr)); + mreq6.ipv6mr_interface = 0; +- return(setsockopt(sockfd, IPPROTO_IPV6, IPV6_DROP_MEMBERSHIP, ++ return(setsockopt(sockfd, IPPROTO_IPV6, IPV6_LEAVE_GROUP, + &mreq6, sizeof(mreq6))); + } + #endif Index: patches/patch-as =================================================================== RCS file: patch-as diff -N patch-as --- /dev/null Tue Feb 8 14:09:55 2000 +++ patch-as Tue Feb 8 15:20:30 2000 @@ -0,0 +1,11 @@ +--- lib/mcast_join.c- Tue Feb 8 15:12:14 2000 ++++ lib/mcast_join.c Tue Feb 8 15:12:37 2000 +@@ -56,7 +56,7 @@ + else + mreq6.ipv6mr_interface = 0; + +- return(setsockopt(sockfd, IPPROTO_IPV6, IPV6_ADD_MEMBERSHIP, ++ return(setsockopt(sockfd, IPPROTO_IPV6, IPV6_JOIN_GROUP, + &mreq6, sizeof(mreq6))); + } + #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 8 3:22:27 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by builder.freebsd.org (Postfix) with ESMTP id CC25741C3 for ; Tue, 8 Feb 2000 03:22:24 -0800 (PST) Received: from cichlids.com (pC19F5495.dip0.t-ipconnect.de [193.159.84.149]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id MAA06035; Tue, 8 Feb 2000 12:23:03 +0100 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 6977CAC26; Tue, 8 Feb 2000 12:23:27 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id MAA05837; Tue, 8 Feb 2000 12:24:11 +0100 (CET) (envelope-from alex) Date: Tue, 8 Feb 2000 12:24:11 +0100 From: Alexander Langer To: sumikawa@ebina.hitachi.co.jp Cc: jinmei@isl.rdc.toshiba.co.jp, net@FreeBSD.ORG Subject: Re: IPV6_DROP_MEMBERSHIP not defined Message-ID: <20000208122411.C2675@cichlids.cichlids.com> References: <20000207183115.A4246@cichlids.cichlids.com> <20000208121128.A2675@cichlids.cichlids.com> <200002081114.UAA06835@prince.net.ebina.hitachi.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002081114.UAA06835@prince.net.ebina.hitachi.co.jp>; from sumikawa@ebina.hitachi.co.jp on Tue, Feb 08, 2000 at 08:14:04PM +0900 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake sumikawa@ebina.hitachi.co.jp (sumikawa@ebina.hitachi.co.jp): > I've already made the following patch and send it to the maintainer. > Could you try it? the patching of the port fails, but the patches seem ok. Maybe I was just too dumb to extrac the patches from the mail. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 8 6:20:44 2000 Delivered-To: freebsd-net@freebsd.org Received: from bigphred.greycat.com (bigphred.greycat.com [207.173.133.2]) by builder.freebsd.org (Postfix) with ESMTP id 8C6C841BD for ; Tue, 8 Feb 2000 06:20:37 -0800 (PST) Received: (from dann@localhost) by bigphred.greycat.com (8.9.3/8.9.3) id GAA78277 for net@freebsd.org; Tue, 8 Feb 2000 06:22:23 -0800 (PST) (envelope-from dann) Date: Tue, 8 Feb 2000 06:22:23 -0800 From: Dann Lunsford To: net@freebsd.org Subject: Ethernet Frame types Message-ID: <20000208062223.A78211@greycat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been trying to get Boris Popov's NCPLIB working, and have run into a somewhat wierd snag. It seems that the Novell people at my site (apparently at the advice of Novell) have decreed that all IPX shall be encapsulated in Frame type 802.3. As near as I can tell (tcpdump, ethereal, etc.) PreeBSD generates everything in Ethernet II frames. Thus, the Novell servers can't see me at all. IP functionality is all there, this just affects IPX. I've been trying to dig through the code, but can't find where the frame type is specified. Is there someone out there with a clue they could send my way? Thanks! -- Dann Lunsford The only thing necessary for the triumph of evil dann@greycat.com is that men of good will do nothing. -- Cicero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 8 7:46:27 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by builder.freebsd.org (Postfix) with ESMTP id DC055429F for ; Tue, 8 Feb 2000 07:46:18 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA33886; Tue, 8 Feb 2000 10:47:05 -0500 (EST) (envelope-from wollman) Date: Tue, 8 Feb 2000 10:47:05 -0500 (EST) From: Garrett Wollman Message-Id: <200002081547.KAA33886@khavrinen.lcs.mit.edu> To: "gbnaidu " Cc: freebsd-net@FreeBSD.ORG Subject: Re: How to get outgoing interface... In-Reply-To: References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > if ( (sa = rti_info[RTAX_DST]) != NULL) { process the destination address; Stop right there. The routing message isn't in this format. See the code Brian Somers pointed out, or route.c, for an example of how to interpret a routing message. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 8 8: 0:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id AA7B3429D for ; Tue, 8 Feb 2000 08:00:22 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id IAA13107; Tue, 8 Feb 2000 08:00:58 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id IAA24937; Tue, 8 Feb 2000 08:00:58 -0800 Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id IAA20393; Tue, 8 Feb 2000 08:00:54 -0800 (PST) Message-ID: <38A03F1A.F6338FD9@softweyr.com> Date: Tue, 08 Feb 2000 09:06:50 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dann Lunsford Cc: net@freebsd.org Subject: Re: Ethernet Frame types References: <20000208062223.A78211@greycat.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dann Lunsford wrote: > > I've been trying to get Boris Popov's NCPLIB working, and have run > into a somewhat wierd snag. It seems that the Novell people at my > site (apparently at the advice of Novell) have decreed that all > IPX shall be encapsulated in Frame type 802.3. As near as I can > tell (tcpdump, ethereal, etc.) PreeBSD generates everything in > Ethernet II frames. Thus, the Novell servers can't see me at all. > IP functionality is all there, this just affects IPX. I've been > trying to dig through the code, but can't find where the frame type > is specified. Is there someone out there with a clue they could > send my way? Thanks! /usr/src/sys/net/if_ethersubr.c -- "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 8 8: 1:31 2000 Delivered-To: freebsd-net@freebsd.org Received: from p0016c23.us.kpmg.com (p0016c23.us.kpmg.com [199.207.255.23]) by builder.freebsd.org (Postfix) with ESMTP id 8169E3DB8 for ; Tue, 8 Feb 2000 08:01:28 -0800 (PST) Received: from p0016c56.kweb.us.kpmg.com by p0016c23.us.kpmg.com(Pro-8.9.3/Pro-8.9.3) with SMTP id LAA28789 for ; Tue, 8 Feb 2000 11:02:20 -0500 (EST) Received: from p0016c22.kweb.us.kpmg.com by p0016c56.kweb.us.kpmg.com via smtpd (for p0016c23.us.kpmg.com [199.207.255.23]) with SMTP; 8 Feb 2000 16:02:34 UT Received: from usnssexc19.kweb.us.kpmg.com by kpmg.com(Pro-8.9.2/Pro-8.9.2) with ESMTP id LAA23889 for ; Tue, 8 Feb 2000 11:02:20 -0500 (EST) Received: from usnssexc19.kweb.us.kpmg.com (unverified) by usnssexc19.kweb.us.kpmg.com (Content Technologies SMTPRS 2.0.15) with ESMTP id for ; Tue, 08 Feb 2000 10:52:01 -0500 Received: by usnssexc19.kweb.us.kpmg.com with Internet Mail Service (5.5.2650.21) id ; Tue, 8 Feb 2000 10:52:01 -0500 Message-Id: <8389C74A65EFD111B03800805FA7658F06C04882@USDALEXC01> From: "Fisch, Eric" To: freebsd-net@freebsd.org Subject: PPP Gateway Routing Problem Date: Tue, 8 Feb 2000 10:58:28 -0500 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 I am having what appears to be a routing problem with a PPP gateway and am hoping someone can shed some light on the issue. I have a small network of windows/UNIX systems behind a FreeBSD gateway box. The gateway box is providing DNS and DHCP services to the other systems without any problem. I have tried to set up the gateway box to do PPP-on-demand for the entire network with limited success. PPP works flawlessly on the gateway box. When I am on the "inside", however, I get nothing. I am able to connect to the gateway, but no further. Interestingly enough, when I "ping" a system from the inside box, I get proper name resolution, but "Host is Unreachable" errors as well. This leads me to believe that I have a routing issue from the gateway to the inside boxes. I think I am missing something in my rc.conf settings. Heck, if I had any clue what was wrong I would not be posting. Obligatory Diagram: ISP | <- PPP on Demand (ISP assigned IP address of a.b.c.d) FreeBSD gateway <- DNS and DHCP servers to inside (border.mydomain.com) | <- gateway internal ip: 192.168.169.1 ---------------- | | | Win95 UNIX Win95 <- all "inside" boxes (all in the range of: 192.168.169.x) rc.conf file: network_interfaces="ed0 lo0 tun0" ifconfig_ed0="inet 192.168.169.1 netmask 255.255.255.0" ifconfig_lo0="inet 127.0.0.1" ifconfig_tun0="" hostname="border.mydomain.com" linux_enable="YES" dhcpd_enable="YES" lpd_enable="YES" moused_port="/dev/psm0" moused_enable="YES" saver="blank" gateway_enable="YES" defaultrouter="NO" named_enable="YES" route_enable="NO" ppp_enable="YES" ppp_nat="YES" ppp_mode="auto" ppp_profile="demand" Any assistance would be great! Thanks, Eric Fisch efisch@kpmg.com ***************************************************************************** The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing KPMG client engagement letter. ***************************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 8 8:33:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from merlin.ilstu.edu (merlin.ilstu.edu [138.87.4.8]) by builder.freebsd.org (Postfix) with ESMTP id 51038426E for ; Tue, 8 Feb 2000 08:33:38 -0800 (PST) Received: from Zaphod (south212038.resnet.ilstu.edu [138.87.212.38]) by merlin.ilstu.edu (8.9.2/8.9.2) with SMTP id KAA08375 for ; Tue, 8 Feb 2000 10:34:30 -0600 (CST) Message-Id: <3.0.3.32.20000208103137.00718050@pop.interaccess.com> X-Sender: fordp@pop.interaccess.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 08 Feb 2000 10:31:37 -0600 To: freebsd-net@freebsd.org From: Ford Prefect Subject: Etherchannel support? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been reading through the archives and found some discussion back in Feburary of 99 and then again in July about doing this using the netgraph library. The consensus at the time seemd to be that it could be done with netgraph but no one had. I'd very much like to be able to tie multiple interfaces together so I was wondering if anyone had done this yet? Or perhaps has some pointers in what would be involved in doing it myself? I need to do something akin to Channel Bonding in a beowulf system. -Steve *=====================================================* \ Ford Prefect Ahead of my time. \ \ fordp@guide.chi.il.us but only by a week. \ \ homepage.interaccess.com/~fordp \ \ \ \ ((In esperanto where available)) \ *=====================================================* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 8 19:22:22 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail-03-real.cdsnet.net (mail-03-real.cdsnet.net [204.118.244.93]) by builder.freebsd.org (Postfix) with SMTP id 6FD12471D for ; Tue, 8 Feb 2000 15:39:44 -0800 (PST) Received: (qmail 48627 invoked from network); 8 Feb 2000 23:39:10 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-03-real.cdsnet.net with SMTP; 8 Feb 2000 23:39:10 -0000 Date: Tue, 8 Feb 2000 15:36:48 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: freebsd-net@freebsd.org Subject: OSPF route propogation via zebra, gated with FreeBSD 3.4 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 My Cisco OSPF networks works just like I think it should. But I've been putting in FreeBSD routers for it's more sophisticated abilities, but I'm getting stuck in one small area. With the following configuration: Internet -> A -> B -> C -> D where A/B/C/D are all FreeBSD boxes/routers, some running gated, some running zebra while I experiment. Given that the total # of routers will be small, I plan on just lumping everything into the backbone area. As it sits right now, with everything configured in area 0, A B C see all their connected/static routes. C sees routes from D, but doesn't propogate them to B or A. If D is in area 0 as well, is it a requirement that there be a virtual link from D to A? My understanding of the virtual link requirement was only if D was in a different area, then D also needed connectivity to the backbone area. I'm tempted to convert everything to bgp, which I have more experience with, and see if it works getter. Either way is fine with me... Any tips appreciated. Can send config files on request, they're changing pretty fast as I try stuff. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 9 1: 9:23 2000 Delivered-To: freebsd-net@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by builder.freebsd.org (Postfix) with ESMTP id 5B4164404 for ; Tue, 8 Feb 2000 18:08:07 -0800 (PST) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12IMX6-0005Uv-00; Wed, 09 Feb 2000 08:07:08 +0600 Date: Wed, 9 Feb 2000 08:07:08 +0600 (ALMT) From: Boris Popov To: Dann Lunsford Cc: net@freebsd.org Subject: Re: Ethernet Frame types In-Reply-To: <20000208062223.A78211@greycat.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, 8 Feb 2000, Dann Lunsford wrote: > I've been trying to get Boris Popov's NCPLIB working, and have run > into a somewhat wierd snag. It seems that the Novell people at my > site (apparently at the advice of Novell) have decreed that all > IPX shall be encapsulated in Frame type 802.3. As near as I can If you're runnig -current see man ef(4), for the 3.4-stable branch download if_ef driver separately: ftp://ftp.butya.kz/pub/ipx/ifef-1.3.tar.gz -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 9 10:10: 3 2000 Delivered-To: freebsd-net@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by builder.freebsd.org (Postfix) with ESMTP id 45907401F for ; Wed, 9 Feb 2000 10:09:57 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id TAA15683 for net@freebsd.org; Wed, 9 Feb 2000 19:09:24 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id B1C388877; Wed, 9 Feb 2000 08:09:02 +0100 (CET) Date: Wed, 9 Feb 2000 08:09:02 +0100 From: Ollivier Robert To: net@freebsd.org Subject: Re: Ethernet Frame types Message-ID: <20000209080902.A17706@keltia.freenix.fr> Mail-Followup-To: net@freebsd.org References: <20000208062223.A78211@greycat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000208062223.A78211@greycat.com>; from dann@greycat.com on Tue, Feb 08, 2000 at 06:22:23AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Dann Lunsford: > trying to dig through the code, but can't find where the frame type > is specified. Is there someone out there with a clue they could > send my way? Thanks! Use the if_ef driver (see ef(4)). It will create 4 different sub-interfaces to support multiple frame types. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 9 10:50:37 2000 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by builder.freebsd.org (Postfix) with ESMTP id A7CB0412B; Wed, 9 Feb 2000 10:50:26 -0800 (PST) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id TAA38288; Wed, 9 Feb 2000 19:50:14 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200002091850.TAA38288@info.iet.unipi.it> Subject: HEADS-UP, upcoming changes to ipfw: keep-state To: current@freebsd.org Date: Wed, 9 Feb 2000 19:50:14 +0100 (CET) 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 [Bcc to -net as also relevant there] People, in the next day or so, with Jordan's approval, and in response to many queries i got about this, i am going to commit to -current (and then to -stable when it settles a bit) some ipfw patches which make the firewall stateful (only if you use the new features; otherwise ipfw behaves as usual). This will let you write things like (taken from a live -current): rizzo# ipfw show 00100 313 15907 allow tcp from any to any keep-state setup 00200 0 0 deny tcp from any to any 65535 1433 309926 allow ip from any to any ## Dynamic rules: 00100 279 13151 tcp 131.114.9.26 513 <-> 131.114.9.236 where the 'Dynamic rules' part is generated as a result of a match of rule 100. This should be useful to protect slow machines from attacks such as stream.c and the like. Also, the code should be fully integrated with bridging and dummynet. I would like people to give a try to the new code, point out bugs and possibly suggest enhancements if they have some ideas. The way the code works now: dynamic rules match the tuple They are stored in a hash table, whose size is configurable through a sysctl variable (default is 256). The max number of dynamic rules is limited with another sysctl variable (default 1000, but it can easily go up 2 orders of magnitude i think). When the max # of dynamic rules is reached, new ones are not added until the old ones expire. The expire time is set again using sysctl variables, defaults to a few seconds for SYN/FIN/RST and minutes for regular packets. (this will not save you from idle ssh/telnet connections timing out, but i have seen the same behaviour with commercial firewalls as well). Dynamic rules are checked before the whole ruleset (although by the time i commit the code there will be probably a way to tell exactly at which point to check dynamic rules). Note, this behaviour is probably appropriate for a workstation. If you build a router+ipfw/bridge+ipfw, then you might want different types of dynamic rules which only check part of the headers -- HERE I NEED YOUR INPUT!!! And of course, if you need some customized version of this stuff, feel free to talk to me. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 9 12: 8:15 2000 Delivered-To: freebsd-net@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by builder.freebsd.org (Postfix) with ESMTP id E05074183 for ; Wed, 9 Feb 2000 12:07:59 -0800 (PST) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 67B2A137F68 for ; Wed, 9 Feb 2000 15:07:29 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id PAA66031; Wed, 9 Feb 2000 15:07:29 -0500 (EST) (envelope-from dgilbert) From: David Gilbert Message-ID: <14497.51456.635308.156936@trooper.velocet.net> Date: Wed, 9 Feb 2000 15:07:28 -0500 (EST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="5Wcwg9B2VV" Content-Transfer-Encoding: 7bit To: freebsd-net@freebsd.org Subject: L2tp thoughts an implementations. X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --5Wcwg9B2VV Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit Probably about the third mailing list that I have send the message below to, but Archie recomended that I forwarde it on here. Anyways... I also recently said: Archie> Yes, that sounds like a good idea (though I don't know much Archie> about VLAN). VLan is an exceedingly simple protocol. As I understand it, you add a 4 byte "number" to a raw ethernet packet. The 4 byte number is the vlan number. Having finished some of the packet munging stuff for l2tp, I'd have to say that this is so exceedingly simple, it might be worth just putting inside the ethernet node itself... maybe. I suppose it could go either way. Now... I started vaguely wondering to myself if we could create a ng_route node... which would have a routing table similar to the kernel's. This would give you CISCO-like vlan power --- you'd create a "vrouter" by attaching certain vlans to a route node. (which is also a relavant, but separate topic for this list --- it would seem that netgraph tech would make a more "appropriate" or "correct" vlan config ... considering the possibilities) --5Wcwg9B2VV Content-Type: message/rfc822 Content-Description: forwarded message Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <14497.40372.136664.641305@trooper.velocet.net> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid From: David Gilbert Subject: Netgraph and l2tp Date: Wed, 9 Feb 2000 12:02:44 -0500 (EST) Netgraph is seriously cool technology. I think we've briefly touched on this before, but I've been spending most of my week creating an l2tp node for it, so I thought I'd comment more on it's structure and use. For further reading, see your local FreeBSD (or NetBSD, but I believe Theo has rejected it) machine or http://www.FreeBSD.org/cgi/man.cgi?query=netgraph&apropos=0&sektion=0&manpath=FreeBSD+3.4-RELEASE&format=html Anyways, l2tp is somewhat like pptp in that encapsulates ppp over UDP. It is unlike pptp in that it encapsulates many PPP connections over one UDP tunnel. From RFC-2661: +-----+ +-----+ | |~~~~~~~~~~L2TP Tunnel~~~~~~~~~~| | | LAC | | LNS | | #######Control Connection######## | [Remote] | | | | [System]------Call----------*============L2TP Session=============* | PPP +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ | | | | | [Remote] | | | | [System]------Call----------*============L2TP Session=============* | PPP +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ | | | | | | |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | +-----+ +-----+ ... and I'm implementing the "LNS" (for now). Basically, in the ADSL case, remote system to LAC is PPPoE and the LAC then forwards the PPP frames inside the L2TP tunnel. What this means at my end that I have to manage the L2TP "glue," but the majority of the processing concerns stripping off the L2TP header (or adding it) with the remainder of the processing being straight PPP. Now, netgraph already has the following general PPP setup: ksocket <--> ppp <--> bpf <--> iface (UDP) ^ (ng0) | v socket <--> mpd (userland) mpd manages the whole lot, communicating through the ng_socket node. MPD does authentication and other administration, but the ng_ppp node does all the regular PPP stuff. Encryption and/or compression are provided by hooks on the ng_ppp node (hooks and nodes for this arn't shown). The ng_bpf node is simply present to detect packets to bring up the link on certain kinds of traffic. Now... to do L2TP, we're modifying this picture somewhat. In the following <-=> means "one to many." ksocket <--> l2tp <-=> ppp <--> iface ^ // | // v / socket <--> mpd In this case, mpd manages one (or more) l2tp nodes which each manage many (potentially thousands) of ppp nodes. I'm axeing the bpf node since the remote end will always initiate the connection. The cool part of this is that everything but the l2tp "glue" is already written. I've had to learn a few things about mbufs to work on ng_l2tp, but I'm getting around it. I've been thinking lately of working on adding vlan hooks to ethernet interfaces when I'm done this ... there already is vlan stuff in FreeBSD, but it would appear more elegant to use the netgraph stuff (and painfully simple) to do vlans. Using netgraph would also allow me to (basically) create vrouter type capability in FreeBSD. (In doing this, you might connect the vlan10 hook of fxp0 to the vlan35 hook of fxp1 --- effectively bridging the vlan. With a few more netgraph nodes, you could mix in things like bpf and/or some forms of firewalling or routing netgraph nodes.) Anyways... enough cool toys for now. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ --5Wcwg9B2VV-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 9 15:57:47 2000 Delivered-To: freebsd-net@freebsd.org Received: from garfield.bmk.com.au (bmkind.lnk.telstra.net [139.130.51.118]) by builder.freebsd.org (Postfix) with ESMTP id E03D64280 for ; Wed, 9 Feb 2000 15:57:42 -0800 (PST) Received: from garfield (garfield [203.36.170.241]) by garfield.bmk.com.au (8.8.7/8.8.7) with SMTP id KAA02928 for ; Thu, 10 Feb 2000 10:57:26 +1100 (EST) (envelope-from brendan@bmk.com.au) Date: Thu, 10 Feb 2000 10:57:26 +1100 (EST) From: Brendan Kosowski X-Sender: brendan@garfield To: FreeBSD Networking Subject: sendmail hogs ppp link ? 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 have noticed that sendmail realy hogs my ppp link, especialy if my system is diverting email ( ie. receiving and sending at the same time ). When this is happening viewing internet web pages is painfully slow and ping delays are very high. Is it possible to fine tune the system or sendmail so that the rate of receiving and sending email is restricted ( therefore allowing other packets to get through ) ??? Thanks, Brendan Kosowski ------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 9 17: 5: 4 2000 Delivered-To: freebsd-net@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by builder.freebsd.org (Postfix) with ESMTP id 3033C4220 for ; Wed, 9 Feb 2000 17:04:58 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id UAA04680; Wed, 9 Feb 2000 20:04:14 -0500 Date: Wed, 9 Feb 2000 20:04:13 -0500 (EST) From: Mike Nowlin To: Brendan Kosowski Cc: FreeBSD Networking Subject: Re: sendmail hogs ppp link ? 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 > Is it possible to fine tune the system or sendmail so that the rate of > receiving and sending email is restricted ( therefore allowing other > packets to get through ) ??? Take a look at dummynet(4).... I've never actually used it myself (but always wanted to), but I believe it'll help solve your problem. mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 9 23:29:23 2000 Delivered-To: freebsd-net@freebsd.org Received: from etri.re.kr (mail.etri.re.kr [129.254.113.113]) by builder.freebsd.org (Postfix) with ESMTP id 66EAF43A0 for ; Wed, 9 Feb 2000 23:29:19 -0800 (PST) Received: from etri.re.kr (kimch.etri.re.kr [129.254.191.142]) by etri.re.kr (8.9.3/8.9.3) with ESMTP id QAA15588; Thu, 10 Feb 2000 16:26:29 +0900 (KST) Message-ID: <38A26863.D6D499D0@etri.re.kr> Date: Thu, 10 Feb 2000 16:27:31 +0900 From: Changhoon Kim X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: ko,en MIME-Version: 1.0 To: Brendan Kosowski Cc: FreeBSD Net Subject: Re: sendmail hogs ppp link ? References: Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brendan Kosowski wrote: > Is it possible to fine tune the system or sendmail so that the rate of > receiving and sending email is restricted ( therefore allowing other > packets to get through ) ??? Dummynet is exactly what you want. Because It was designed to enable flexible bandwidth management and delay emulation. To use dummynet, first, turn on two options "IPFIREWALL" and "DUMMYNET" in the kernel configuration file and rebuild it. Then you can use "ipfw" commands to control the new installed firewall. Specifically, you can set up specific filters and enforce some limitations for bandwidth and delay on them, using "pipe" rules among IP firewall funtions. For example, "ipfw add pipe 1 tcp from localhost 25 to any" "ipfw pipe 1 config bw 20Kbit/s" mean that bandwidth of a tcp data stream from port number 25(smtp) of your localhost to any hosts in the Internet will be restricted to 20Kbit/s at most. In similar context, you will be able to interprete following commands; ipfw add pipe 2 udp from localhost 25 to any ipfw add pipe 3 tcp from localhost to any 25 ipfw add pipe 4 udp from localhost to any 25 ipfw pipe 2 config bw ... ipfw pipe 3 config bw ... ipfw pipe 4 config bw ... For more information, "man dummynet" or "man ipfw". Regards. Chang. -- ========================================================== Changhoon Kim Internet Technology Research Dept. Switching & Transmission Technology Lab. Electronics and Telecommunications Research Institute(ETRI) 161 Kajong-dong, Yusong-gu, Taejon, 305-350, KOREA Tel: (Office) +82-42-860-5801, (Cell) +82-19-226-6305 E-mail: kimch@etri.re.kr * All Smiles, Everywhere and Everytime ! =========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 0: 6: 2 2000 Delivered-To: freebsd-net@freebsd.org Received: from vidle.i.cz (vidle.i.cz [193.179.36.138]) by builder.freebsd.org (Postfix) with ESMTP id 919AB43D0 for ; Thu, 10 Feb 2000 00:06:00 -0800 (PST) Received: from ns.i.cz (brana.i.cz [193.179.36.134]) by vidle.i.cz (Postfix) with ESMTP id 45B5130702 for ; Thu, 10 Feb 2000 09:05:38 +0100 (CET) Received: from woody.i.cz (woody.i.cz [192.168.18.29]) by ns.i.cz (Postfix) with ESMTP id 7A69C36415 for ; Thu, 10 Feb 2000 09:05:37 +0100 (CET) Content-Length: 751 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <14497.51456.635308.156936@trooper.velocet.net> Date: Thu, 10 Feb 2000 09:05:37 +0100 (MET) Reply-To: mm@i.cz From: Martin Machacek To: freebsd-net@FreeBSD.ORG Subject: RE: L2tp thoughts an implementations. Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 09-Feb-00 David Gilbert wrote: > Now... I started vaguely wondering to myself if we could create a > ng_route node... which would have a routing table similar to the > kernel's. This would give you CISCO-like vlan power --- you'd create > a "vrouter" by attaching certain vlans to a route node. Why would you like to bridge VLANs? If I want some stations to be on the same LAN segment I put them to the same VLAN. If I want them to be on different segments I put them in separate VLANs and route (or if you wish switch on layer three) between corresponding interfaces. I don't see any use for bridging VLANs. In any case I would definitely like to see solid implementation of 802.1q VLANs in FreeBSD. Martin --- [PGP KeyID F3F409C4] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 2:20: 5 2000 Delivered-To: freebsd-net@freebsd.org Received: from mc-qout4.whowhere.com (mc-qout4.whowhere.com [209.185.123.18]) by builder.freebsd.org (Postfix) with SMTP id 9A537420F for ; Thu, 10 Feb 2000 02:20:02 -0800 (PST) Received: from Unknown/Local ([?.?.?.?]) by my-deja.com; Thu Feb 10 02:19:23 2000 To: freebsd-net@FreeBSD.ORG Date: Thu, 10 Feb 2000 02:19:23 -0800 From: "gbnaidu " Message-ID: Mime-Version: 1.0 X-Sent-Mail: off X-Mailer: MailCity Service Subject: Defn of SIOCGARP... X-Sender-Ip: 164.164.56.2 Organization: My Deja Email (http://www.my-deja.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Length: 477 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I would like to know where these contants are defined in FreeBSD: SIOCGARP, SIOCSARP, SIOCDARP. Other ioctl commands are defined in sys/sockio.h but these commands are not defiend atleast in my 3.1 FreeBSD release. Also where will I get FreeBSD 2.2.6 release? On the server only 2.2.8 release on wards available. Can somebody give me ponter to this. thanks a lot --gb --== Sent via Deja.com http://www.deja.com/ ==-- Share what you know. Learn what you don't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 4: 9:16 2000 Delivered-To: freebsd-net@freebsd.org Received: from d016.gold.gellivare.se (comnix.com [195.196.65.16]) by builder.freebsd.org (Postfix) with SMTP id 1AF92440F for ; Thu, 10 Feb 2000 04:08:23 -0800 (PST) Received: (qmail 3723 invoked from network); 10 Feb 2000 12:08:01 -0000 Received: from pc5241153.han.telia.se (HELO olle) (131.115.241.153) by comnix.com with SMTP; 10 Feb 2000 12:08:01 -0000 Message-ID: <009d01bf73bf$8947e000$0201a8c0@telia.se> From: "John Angelmo" To: Subject: Date: Thu, 10 Feb 2000 13:08:26 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org auth 01b7f77a subscribe freebsd-net john@veidit.net end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 6: 9:48 2000 Delivered-To: freebsd-net@freebsd.org Received: from d016.gold.gellivare.se (comnix.com [195.196.65.16]) by builder.freebsd.org (Postfix) with SMTP id D3CA54436 for ; Thu, 10 Feb 2000 06:09:42 -0800 (PST) Received: (qmail 7165 invoked from network); 10 Feb 2000 14:09:13 -0000 Received: from pc5241153.han.telia.se (HELO olle) (131.115.241.153) by comnix.com with SMTP; 10 Feb 2000 14:09:13 -0000 Message-ID: <001a01bf73d0$7635eaa0$0201a8c0@telia.se> From: "John Angelmo" To: Subject: local pppoe Date: Thu, 10 Feb 2000 15:09:35 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello This is my netconfig and I wonder if any1 here have any hints forme = regardin my pppoe connection.. I can't get it to work..=20 > _________ > | Internet | > | | > |_________| > | > | > _____|____ > | | > | ed1 | <-ed1 get real IP from DHCP server > | | | <-Freebsd 3.4 stable > | vr0 | <- VR0 har 192.168.1.1 > |_________| > | > | <--Want pppoe > ___|______ > | | > | eth0 | <- RH 6.1 BOX > |_________| <- I want eth0 to get a IP from the 192.168.1.*=20 > sub 255.255.255.0 net This is the messages I get: I'm trying to put up a server and a client for pppoe on the serverside Freebsd 3.4 pppoed on the clientside RHL 6.1 pppoe from www.roaringpenguin.com. When I connect I get the server get this message: bash-2.03# /usr/libexec/pppoed -Fd -p telia vr0 Sending NGM_LISTHOOKS to vr0: Got reply from id [1]: Type ether with 0 hooks Send MKPEER: vr0:orphans -> [type pppoe]:ethernet Sending PPPOE_LISTEN to .:pppoe-1951, provider telia pppoed[1951]: Listening as provider telia pppoed[1951]: Got 60 bytes of data: = ffffffffffff0000f8780bbd8863110900000004010100000000000000000000000000000= 00000000000000000000000000000000000000000000000 pppoed[1951]: Listening as provider telia pppoed[1953]: Creating a new socket node pppoed[1953]: Sending CONNECT from .:exec-1953 -> vr0:orphans.exec-1953 pppoed[1953]: Sending NGM_SOCK_CMD_NOLINGER to socket pppoed[1953]: Offering to .:exec-1953 as access concentrator lisa pppoed[1953]: Sending original request to .:exec-1953 (60 bytes) pppoed[1953]: Waiting for a SUCCESS reply .:exec-1953 pppoed[1953]: Received NGM_PPPOE_SUCCESS (hook "exec-1953") pppoed[1953]: Executing: exec /usr/sbin/ppp -direct telia Feb 10 14:41:05 lisa ppp[1953]: tun0: Warning: Unindented command = (/etc/ppp/ppp.conf line 33) - ignored=20 Feb 10 14:41:05 lisa ppp[1953]: tun0: Warning: deflink: Reducing MRU to = 1492 The client side generates this Using interface ppp0 Connect: ppp0 <--> /dev/pts/1 sent [LCP ConfReq id=3D0x5 ] rcvd [proto=3D0x7eff] 7d 23 c0 21 7d 21 7d 21 7d 20 7d 38 7d 28 7d 22 7d = 27 7d 22 7d 22 7d 26 7d 20 7d 20 7d 20 7d 20 ... sent [LCP ConfReq id=3D0x5 ] Terminating on signal 2. sent [LCP TermReq id=3D0x6 "User request"] Modem hangup Connection terminated. Child process /usr/local/bin/pppoe -I eth0 -T 80 -m 1412 (pid 654) = terminated with signal 2 Using interface ppp0 Connect: ppp0 <--> /dev/pts/1 sent [LCP ConfReq id=3D0x1 ] write: warning: Input/output error (5) Modem hangup Connection terminated. Script /usr/local/bin/pppoe -I eth0 -T 80 -m 1412 finished (pid 658), = status =3D 0x0 Does any1 have any hints? /John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 7:16: 9 2000 Delivered-To: freebsd-net@freebsd.org Received: from proxy.telecoms.bg (proxy.telecoms.bg [193.200.17.2]) by builder.freebsd.org (Postfix) with ESMTP id A2CBC44A9 for ; Thu, 10 Feb 2000 07:15:55 -0800 (PST) Received: from www.bgzone.com (bgzone [193.200.17.161]) by proxy.telecoms.bg (8.9.3/8.9.3) with ESMTP id RAA11000 for ; Thu, 10 Feb 2000 17:15:26 +0200 Received: from www.koral.bg (www.koral.bg [194.12.241.161]) by www.bgzone.com (8.9.2/8.9.2) with ESMTP id RAA12534 for ; Sun, 31 Jan 1999 17:19:59 +0200 (EET) (envelope-from mitko@www.koral.bg) Received: (from mitko@localhost) by www.koral.bg (8.9.2/8.9.2) id RAA08453 for freebsd-net@freebsd.org; Thu, 10 Feb 2000 17:12:55 +0200 (EET) (envelope-from mitko) Date: Thu, 10 Feb 2000 17:12:55 +0200 (EET) From: Dimitar Peikov Message-Id: <200002101512.RAA08453@www.koral.bg> To: freebsd-net@freebsd.org Subject: net problem Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have the following problem and cant see where I wrong or there is another way to do it. Problem: I have one segment in wich are connected different networks. in this case I try to use one workstation using Windows with alone IP -> let it be 192.168.1.1/32 and my freebsd uses 192.168.0.1/24 . The other Win I could setup to see this alone workstation using routing information but in my freebsd machine when I set using : route add -host 192.168.1.1 -netmask 255.255.255.255 -interface ed0 My arp table says that ed0 has IP 192.168.1.1 ????? If set using : route add -host 192.168.1.1 -netmask 255.255.255.255 192.168.0.1 My arp says nothing, but ping returns routing errors???? Could someone can explain me how to solve that problem? I see that 2 Windowses in this configuration have ping between, but ping between freebsd and that Windows - no! Mitko P.S.: I forgot that currently I use 3.1 release. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 8:52:44 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by builder.freebsd.org (Postfix) with ESMTP id 06D9A44C4 for ; Thu, 10 Feb 2000 08:52:39 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA42481; Thu, 10 Feb 2000 11:52:13 -0500 (EST) (envelope-from wollman) Date: Thu, 10 Feb 2000 11:52:13 -0500 (EST) From: Garrett Wollman Message-Id: <200002101652.LAA42481@khavrinen.lcs.mit.edu> To: "gbnaidu " Cc: freebsd-net@FreeBSD.ORG Subject: Defn of SIOCGARP... In-Reply-To: References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Hi > I would like to know where these contants are defined in FreeBSD: > SIOCGARP, SIOCSARP, SIOCDARP. Other ioctl commands are defined in > sys/sockio.h but these commands are not defiend atleast in my 3.1 > FreeBSD release. They don't exist, and will not. See route(4). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 10:18:34 2000 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by builder.freebsd.org (Postfix) with ESMTP id E74294501 for ; Thu, 10 Feb 2000 10:18:27 -0800 (PST) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id TAA42862; Thu, 10 Feb 2000 19:18:21 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200002101818.TAA42862@info.iet.unipi.it> Subject: new dummynet page To: net@freebsd.org Date: Thu, 10 Feb 2000 19:18:21 +0100 (CET) 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 I have spent some time trying to cleanup the dummynet page, now it should contain a lot more information and also an updated picobsd image based on 3.4 and with the new stateful ipfw things. Have a look if you like, the address is the usual one http://www.iet.unipi.it/~luigi/ip_dummynet/ cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 12: 4:51 2000 Delivered-To: freebsd-net@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 4E9D245B0 for ; Thu, 10 Feb 2000 12:04:43 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id MAA01601; Thu, 10 Feb 2000 12:04:18 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id MAA18217; Thu, 10 Feb 2000 12:04:17 -0800 Received: from softweyr.com (dyn5.utah.xylan.com [198.206.184.241]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id MAA14571; Thu, 10 Feb 2000 12:04:15 -0800 (PST) Message-ID: <38A31B2F.434FBA74@softweyr.com> Date: Thu, 10 Feb 2000 13:10:23 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mm@i.cz Cc: freebsd-net@freebsd.org Subject: Re: L2tp thoughts an implementations. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin Machacek wrote: > > On 09-Feb-00 David Gilbert wrote: > > Now... I started vaguely wondering to myself if we could create a > > ng_route node... which would have a routing table similar to the > > kernel's. This would give you CISCO-like vlan power --- you'd create > > a "vrouter" by attaching certain vlans to a route node. > > Why would you like to bridge VLANs? If I want some stations to be on the same > LAN segment I put them to the same VLAN. If I want them to be on different > segments I put them in separate VLANs and route (or if you wish switch on > layer three) between corresponding interfaces. I don't see any use for bridging > VLANs. To allow your engineers to snoop accounting data and figure out what the executive staff is making? > In any case I would definitely like to see solid implementation of 802.1q VLANs > in FreeBSD. As usual, we await your patches... ;^) FWIW, I'd like to see a solid implementation of 802.1q, too. Including the important but always overlooked stuff like per-VLAN arp tables, in case you have a Sun sitting on two VLANs using the same MAC address on both, and per-VLAN routing tables so you can have different VLANs with their own unique internet connections. I know, I know, we await my patches as well. -- "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 Thu Feb 10 12:56:19 2000 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by builder.freebsd.org (Postfix) with ESMTP id 64AE04515 for ; Thu, 10 Feb 2000 12:56:16 -0800 (PST) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.2) id MAA51311; Thu, 10 Feb 2000 12:54:57 -0800 (PST) From: Archie Cobbs Message-Id: <200002102054.MAA51311@bubba.whistle.com> Subject: Re: mpd via dump modems In-Reply-To: <200002071658.SAA01327@mails.itci.kiev.ua> from Yuriy at "Feb 7, 2000 06:59:52 pm" To: samj@itcj.kiev.ua (Yuriy) Date: Thu, 10 Feb 2000 12:54:57 -0800 (PST) Cc: Freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Yuriy writes: > I am use mpd-2.0b2 for permanent connection with my provider. > When I have set my modems with script for control via replys from modem all > work fine. > But when i set my modem in dump mode without scripts or with script for > null-modems connect is not setting. Both modems send each other > SendConfigReq and never das not happen. > How can I do connection wia mpd without programming modems ? If you email me a log trace with lots of debugging turned on then I'll take a look.. If you're using null-modem connection, you may need to add this command: set modem watch -cd -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 13:41:10 2000 Delivered-To: freebsd-net@freebsd.org Received: from cd.mbn.or.jp (cd.mbn.or.jp [202.217.0.53]) by builder.freebsd.org (Postfix) with ESMTP id A91DB45D7 for ; Thu, 10 Feb 2000 13:41:05 -0800 (PST) Received: from gateway (cse7-14.kokubunji.mbn.or.jp [210.144.135.222]) by cd.mbn.or.jp (8.9.1/cd.mbn.or.jp-2.0) with SMTP id GAA14764 for ; Fri, 11 Feb 2000 06:40:47 +0900 (JST) Message-ID: <001101bf740f$4b529ce0$064ca8c0@gateway> From: "Masahiro Ariga" To: Subject: arp wrongs in Multicast Date: Fri, 11 Feb 2000 06:39:02 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear FeeBSD seniors, My name is Masahiro Ariga. I am in a predicament,so I beseech you to help me. I am doing video transmission in the next system from server to client. WindowNT Multicast Multicast Multicast WindowNT PC --- Server(host) --- Router --- Router --- Client Server,Routers are implemented FreeBSD2.2.7. Client enters multicast group which address is 234.5.6.7 and sends Sart command to Server. Server start to send video to multicast address 234.5.6.7. Before starting data transmission,I confirm the address resolusion of interfaces in Sever,Routers by arp command like next. arp -a ? (192.168.75.8) at 0:0:e2:1f:87:77 ? (192.168.76.68) at 0:0:e2:1f:30:9f ? (192.168.76.69) at 0:a0:c9:93:ba:2f permanent ($B!)(B is because I don't specify host names.192.168.-.- are interfaces' IP address.) After I confirmed all interfaces' addresses resoluted,start data transmission. It works fine,untill 20 minutes passed. Then suddenly,just 20 minutes passed,even though I don't touch anything,sendto errors happen in Server and stops. Errors are "No route to host". At that time,I do arp command,and it sure to occure "incomplete" in one of machines like next. arp -a ? (192.168.75.8) at 0:0:e2:1f:87:77 ? (192.168.76.68) at (incomplete) ? (192.168.76.69) at 0:a0:c9:93:ba:2f permanent I did tracedump arp in Server and the result is the next. tcpdump -e arp 09:29:41.233608 0:0:e2:1f:30:9f Broadcast arp 60: arp who-has 192.168.76.69 tell 192.168.76.68 09:29:41.233632 0:a0:c9:93:ba:2f 0:0:e2:1f:30:9f arp 60: arp reply 192.168.76.69 is-at 0:a0:c9:93:ba:2f 09:49:41.074747 0:a0:c9:93:ba:2f Broadcast arp 42: arp who-has 234.5.6.7 tell 192.168.76.69 09:49:42.012409 0:a0:c9:93:ba:2f Broadcast arp 42: arp who-has 234.5.6.7 tell 192.168.76.69 09:49:43.032187 0:a0:c9:93:ba:2f Broadcast arp 42: arp who-has 234.5.6.7 tell 192.168.76.69 09:49:44.056173 0:a0:c9:93:ba:2f Broadcast arp 42: arp who-has 234.5.6.7 tell 192.168.76.69 09:49:45.001329 0:a0:c9:93:ba:2f Broadcast arp 42: arp who-has 234.5.6.7 tell 192.168.76.69 192.168.76.69 is a Server's own output interface IP. It looks like there's no reply for multicast address 234.5.6.7. My questions are: 1.Does arp correctly work during multicast transmission ? 2.If it works,why one of interfaces' address becomes "incomplete" after 20 minutes. 3.How to fix it. My rc.conf settings are, In Server(in which's config file,"option multicast" is added.), defaultrouter="192.168.76.68" # Set next router's address. static_routes="" gateway_enable="NO" router_enable="NO" router="routed" router_flags="" mrouted_enable="NO" mrouted_flags="" ipxgateway_enable="NO" ipxrouted_enable="NO" ipxrouted_flags="" arpproxy_all="" forward_sourceroute="YES" accept_sourceroute="NO" natd_enable="NO" natd_interface="fxp0" natd_flags="" In Routers, multicast option ON defaultrouter="192.168.-.-" # Set next router's address. static_routes="" gateway_enable="YES" router_enable="YES" router="routed" router_flags="" mrouted_enable="YES" mrouted_flags="" FeeBSD seniors, Please enlighten me. Masahiro Ariga mariga@cd.mbn.or.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 15: 8:48 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by builder.freebsd.org (Postfix) with ESMTP id 84C4D4581 for ; Thu, 10 Feb 2000 15:08:36 -0800 (PST) Received: from brisbane.wrs.com (brisbane [147.11.38.9]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id PAA27355 for ; Thu, 10 Feb 2000 15:08:03 -0800 (PST) From: Stephen Macmanus Received: (from stephenm@localhost) by brisbane.wrs.com (8.9.1/8.9.0) id PAA18465 for freebsd-net@freeBSD.org; Thu, 10 Feb 2000 15:08:02 -0800 (PST) Date: Thu, 10 Feb 2000 15:08:02 -0800 (PST) Message-Id: <200002102308.PAA18465@brisbane.wrs.com> To: freebsd-net@freeBSD.org Subject: Path MTU discovery cutoff Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org RFC 1191 specifies a minimum path MTU estimate of 68 bytes for a participating host. The FreeBSD 3.4 implementation uses a cutoff of 296 bytes. Why does it have a larger minimum? ------------------ Stephen Macmanus #include Software Engineer Wind River Systems To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 18:31:18 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by builder.freebsd.org (Postfix) with ESMTP id 6B67C463A for ; Thu, 10 Feb 2000 18:31:12 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id UAA44355; Thu, 10 Feb 2000 20:46:46 -0500 (EST) (envelope-from wollman) Date: Thu, 10 Feb 2000 20:46:46 -0500 (EST) From: Garrett Wollman Message-Id: <200002110146.UAA44355@khavrinen.lcs.mit.edu> To: Stephen Macmanus Cc: freebsd-net@FreeBSD.ORG Subject: Path MTU discovery cutoff In-Reply-To: <200002102308.PAA18465@brisbane.wrs.com> References: <200002102308.PAA18465@brisbane.wrs.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > RFC 1191 specifies a minimum path MTU estimate of 68 bytes for a > participating host. The FreeBSD 3.4 implementation uses a cutoff > of 296 bytes. Why does it have a larger minimum? Because when I felt that the RFC-specified minimum was unreasonably small, and if people want to have links with tiny MTUs then they should bear the costs themselves. It's also protection against a PMTU-DoS attack. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 20: 0:20 2000 Delivered-To: freebsd-net@freebsd.org Received: from bigphred.greycat.com (bigphred.greycat.com [207.173.133.2]) by builder.freebsd.org (Postfix) with ESMTP id 1D894465E for ; Thu, 10 Feb 2000 20:00:14 -0800 (PST) Received: (from dann@localhost) by bigphred.greycat.com (8.9.3/8.9.3) id UAA96550 for net@freebsd.org; Thu, 10 Feb 2000 20:01:08 -0800 (PST) (envelope-from dann) Date: Thu, 10 Feb 2000 20:01:08 -0800 From: Dann Lunsford To: net@freebsd.org Subject: Re: Ethernet Frame types Message-ID: <20000210200108.C96327@greycat.com> References: <20000208062223.A78211@greycat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from bp@butya.kz on Wed, Feb 09, 2000 at 08:07:08AM +0600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Feb 09, 2000 at 08:07:08AM +0600, Boris Popov wrote: > On Tue, 8 Feb 2000, Dann Lunsford wrote: > > > I've been trying to get Boris Popov's NCPLIB working, and have run > > into a somewhat wierd snag. It seems that the Novell people at my > > site (apparently at the advice of Novell) have decreed that all > > IPX shall be encapsulated in Frame type 802.3. As near as I can > > If you're runnig -current see man ef(4), for the 3.4-stable branch > download if_ef driver separately: > > ftp://ftp.butya.kz/pub/ipx/ifef-1.3.tar.gz Thanks for the pointer, Boris. I've had no time to deal with this for the last couple of days, but next week should be less hectic. I've tried tweaking a couple of things (ETHERTYPE_IPX for one) but I still can't get a response. I did manage to see 802.3 Raw frames being sent, but the Novell servers are pure 802.3. Why did they make this so sensitive to frame type? Never mind, rhetorical question... -- Dann Lunsford The only thing necessary for the triumph of evil dann@greycat.com is that men of good will do nothing. -- Cicero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 20: 3:34 2000 Delivered-To: freebsd-net@freebsd.org Received: from bigphred.greycat.com (bigphred.greycat.com [207.173.133.2]) by builder.freebsd.org (Postfix) with ESMTP id 55CFD44F5 for ; Thu, 10 Feb 2000 20:03:31 -0800 (PST) Received: (from dann@localhost) by bigphred.greycat.com (8.9.3/8.9.3) id UAA96560 for net@freebsd.org; Thu, 10 Feb 2000 20:04:26 -0800 (PST) (envelope-from dann) Date: Thu, 10 Feb 2000 20:04:26 -0800 From: Dann Lunsford To: net@freebsd.org Subject: Re: Ethernet Frame types Message-ID: <20000210200426.D96327@greycat.com> References: <20000208062223.A78211@greycat.com> <20000209080902.A17706@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000209080902.A17706@keltia.freenix.fr>; from roberto@keltia.freenix.fr on Wed, Feb 09, 2000 at 08:09:02AM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Feb 09, 2000 at 08:09:02AM +0100, Ollivier Robert wrote: > According to Dann Lunsford: > > trying to dig through the code, but can't find where the frame type > > is specified. Is there someone out there with a clue they could > > send my way? Thanks! > > Use the if_ef driver (see ef(4)). It will create 4 different sub-interfaces to > support multiple frame types. So I see. Interesting. Will give this a good going over next week. This week has been...Oh, nevermind :-/ -- Dann Lunsford The only thing necessary for the triumph of evil dann@greycat.com is that men of good will do nothing. -- Cicero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 10 20: 6:54 2000 Delivered-To: freebsd-net@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 538E74639 for ; Thu, 10 Feb 2000 20:06:46 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id UAA09909; Thu, 10 Feb 2000 20:05:16 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id UAA20113; Thu, 10 Feb 2000 20:05:16 -0800 Received: from softweyr.com (dyn5.utah.xylan.com [198.206.184.241]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id UAA09269; Thu, 10 Feb 2000 20:05:14 -0800 (PST) Message-ID: <38A38BEA.146E6526@softweyr.com> Date: Thu, 10 Feb 2000 21:11:22 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Garrett Wollman Cc: Stephen Macmanus , freebsd-net@freebsd.org Subject: Re: Path MTU discovery cutoff References: <200002102308.PAA18465@brisbane.wrs.com> <200002110146.UAA44355@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 Garrett Wollman wrote: > > < said: > > > RFC 1191 specifies a minimum path MTU estimate of 68 bytes for a > > participating host. The FreeBSD 3.4 implementation uses a cutoff > > of 296 bytes. Why does it have a larger minimum? > > Because when I felt that the RFC-specified minimum was unreasonably > small, and if people want to have links with tiny MTUs then they > should bear the costs themselves. It's also protection against a > PMTU-DoS attack. Is this a candidate for a sysctl knob? sys.net.inet.ip.minmtu, with a default value of 296, so we can be fully RFC compliant and yet sensible? -- "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 Feb 11 0:23:56 2000 Delivered-To: freebsd-net@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by builder.freebsd.org (Postfix) with ESMTP id A1F9F46A6 for ; Fri, 11 Feb 2000 00:23:54 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id DAA20327 for ; Fri, 11 Feb 2000 03:23:00 -0500 Date: Fri, 11 Feb 2000 03:22:59 -0500 (EST) From: Mike Nowlin To: freebsd-net@freebsd.org Subject: IPFW forward 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 Trying to get something working with "ipfw...forward", and starting to remove hair follicles... Just built up a -current box so I can play with IPv6, and I'm having a difficult time getting my 3.4-STABLE machine (the proxy to the rest of the world) to forward the appropriate packets back to the -current machine... Basically, 38.153.104.192/29 is my home network, and 24.93.181.58 is the connection to the Inet. Between NATD and IPFW, I have "normal" stuff being proxied through the gateway correctly. After configuring the IPv6->IPv4 tunnel on the -current machine, I can "ping6 {whatever}" (through gif0), and the packets are going out to the tunnel remote end, and the response is coming back into the proxy. Unfortunately, the proxy never forwards the packets back to the -current machine. I have an IPFW rule of the following near the beginning of rc.firewall on the gateway machine: $fwcmd add 500 fwd 38.153.104.196 ipv6 from any to any in via ed0 ... which, by my thinking, should forward anything coming in from ed0 (cable modem) on IP port 41 (ipv6) to the -current machine (38.153.104.196). No-go -- the packets aren't ever hitting the local ethernet that .196 is connected to. Ideas? Am I too brain-fried to make this work right now? (That's a STRONG possibility, due to the way this week has gone at work..:) ) Thanks - Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 11 8:21:47 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by builder.freebsd.org (Postfix) with ESMTP id 73C6B47E7 for ; Fri, 11 Feb 2000 08:21:43 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA46673; Fri, 11 Feb 2000 11:21:25 -0500 (EST) (envelope-from wollman) Date: Fri, 11 Feb 2000 11:21:25 -0500 (EST) From: Garrett Wollman Message-Id: <200002111621.LAA46673@khavrinen.lcs.mit.edu> To: Wes Peters Cc: Garrett Wollman , Stephen Macmanus , freebsd-net@freebsd.org Subject: Re: Path MTU discovery cutoff In-Reply-To: <38A38BEA.146E6526@softweyr.com> References: <200002102308.PAA18465@brisbane.wrs.com> <200002110146.UAA44355@khavrinen.lcs.mit.edu> <38A38BEA.146E6526@softweyr.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Is this a candidate for a sysctl knob? sys.net.inet.ip.minmtu, with > a default value of 296, so we can be fully RFC compliant and yet > sensible? No skin off my back... -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 11 17: 8:13 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-84.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.212]) by builder.freebsd.org (Postfix) with ESMTP id A7BBB3E28 for ; Fri, 11 Feb 2000 17:08:01 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA16473; Sat, 12 Feb 2000 00:32:36 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA00418; Fri, 11 Feb 2000 21:28:33 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002112128.VAA00418@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brendan Kosowski Cc: FreeBSD Networking , brian@hak.lan.Awfulhak.org Subject: Re: sendmail hogs ppp link ? In-Reply-To: Message from Brendan Kosowski of "Thu, 10 Feb 2000 10:57:26 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Feb 2000 21:28:33 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have noticed that sendmail realy hogs my ppp link, especialy if my > system is diverting email ( ie. receiving and sending at the same time ). > When this is happening viewing internet web pages is painfully slow and > ping delays are very high. > > Is it possible to fine tune the system or sendmail so that the rate of > receiving and sending email is restricted ( therefore allowing other > packets to get through ) ??? Dummynet (as suggested by others) is probably a better option, but within ppp you can use the ``set urgent'' command to make your port 80 traffic skip over the port 25 stuff. It will help a bit, but not a huge amount. > Thanks, Brendan Kosowski > > ------------------------ -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 11 17: 8:19 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-84.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.212]) by builder.freebsd.org (Postfix) with ESMTP id 7AE7E3EA7 for ; Fri, 11 Feb 2000 17:08:10 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA16474; Sat, 12 Feb 2000 00:32:36 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA00392; Fri, 11 Feb 2000 21:22:53 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002112122.VAA00392@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Fisch, Eric" Cc: freebsd-net@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: PPP Gateway Routing Problem In-Reply-To: Message from "Fisch, Eric" of "Tue, 08 Feb 2000 10:58:28 EST." <8389C74A65EFD111B03800805FA7658F06C04882@USDALEXC01> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Feb 2000 21:22:53 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am having what appears to be a routing problem with a PPP gateway and am > hoping someone can shed some light on the issue. I have a small network of > windows/UNIX systems behind a FreeBSD gateway box. The gateway box is > providing DNS and DHCP services to the other systems without any problem. I > have tried to set up the gateway box to do PPP-on-demand for the entire > network with limited success. PPP works flawlessly on the gateway box. > When I am on the "inside", however, I get nothing. I am able to connect to > the gateway, but no further. Interestingly enough, when I "ping" a system > from the inside box, I get proper name resolution, but "Host is Unreachable" > errors as well. This leads me to believe that I have a routing issue from > the gateway to the inside boxes. I think I am missing something in my > rc.conf settings. Heck, if I had any clue what was wrong I would not be > posting. [.....] > gateway_enable="YES" Aww, that was my first suggestion ! Your best bet is probably to run tcpdump on your internal interface to ensure the packets are getting that far. If they're not, you need to add a default route to your dhcpd config. If packets are getting that far, enable tcp/ip logging in ppp and see if the packets are getting that far - proving that you're acting as a gateway. If the packets get that far, enable physical logging to ensure that they're being written to the link. Any eye-openers ? -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 11 17: 8:22 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-84.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.212]) by builder.freebsd.org (Postfix) with ESMTP id BD00B3E34 for ; Fri, 11 Feb 2000 17:08:01 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA16476; Sat, 12 Feb 2000 00:32:36 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA00361; Fri, 11 Feb 2000 21:17:05 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002112117.VAA00361@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Garrett Wollman Cc: "gbnaidu " , freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: How to get outgoing interface... In-Reply-To: Message from Garrett Wollman of "Tue, 08 Feb 2000 10:47:05 EST." <200002081547.KAA33886@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Feb 2000 21:17:05 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > < said: > > > if ( (sa = rti_info[RTAX_DST]) != NULL) { process the destination address; > > Stop right there. The routing message isn't in this format. > > See the code Brian Somers pointed out, or route.c, for an example of > how to interpret a routing message. And be careful of src/usr.sbin/ppp/route.c - it has a bug in it where it fails to align itself properly in the data returned by the NET_RT_IFLIST mib... I have a patch queued for when the code freeze is lifted (queued behind some IPv6 changes), so if you're interested, drop me a line. > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 11 17: 8:26 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-84.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.212]) by builder.freebsd.org (Postfix) with ESMTP id D5D1840AF for ; Fri, 11 Feb 2000 17:08:15 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA16475; Sat, 12 Feb 2000 00:32:36 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA00449; Fri, 11 Feb 2000 21:34:17 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002112134.VAA00449@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "John Angelmo" Cc: freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: local pppoe In-Reply-To: Message from "John Angelmo" of "Thu, 10 Feb 2000 15:09:35 +0100." <001a01bf73d0$7635eaa0$0201a8c0@telia.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Feb 2000 21:34:17 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please don't post the same message to more than one list. Include both in the recipient list so that people don't either have to answer you twice or look as if they're ignoring you. This message has been replied to on freebsd-isp (in fact, it's still in my outbound queue waiting for me to plug my laptop into the real world). > Hello > > This is my netconfig and I wonder if any1 here have any hints forme regardin my pppoe connection.. I can't get it to work.. > > > > _________ > > | Internet | > > | | > > |_________| > > | > > | > > _____|____ > > | | > > | ed1 | <-ed1 get real IP from DHCP server > > | | | <-Freebsd 3.4 stable > > | vr0 | <- VR0 har 192.168.1.1 > > |_________| > > | > > | <--Want pppoe > > ___|______ > > | | > > | eth0 | <- RH 6.1 BOX > > |_________| <- I want eth0 to get a IP from the 192.168.1.* > > sub 255.255.255.0 net > > > > This is the messages I get: > > > I'm trying to put up a server and a client for pppoe > > on the serverside Freebsd 3.4 pppoed > on the clientside RHL 6.1 pppoe from www.roaringpenguin.com. > > When I connect I get the server get this message: > > bash-2.03# /usr/libexec/pppoed -Fd -p telia vr0 > Sending NGM_LISTHOOKS to vr0: > Got reply from id [1]: Type ether with 0 hooks > Send MKPEER: vr0:orphans -> [type pppoe]:ethernet > Sending PPPOE_LISTEN to .:pppoe-1951, provider telia > pppoed[1951]: Listening as provider telia > pppoed[1951]: Got 60 bytes of data: ffffffffffff0000f8780bbd886311090000000401010000000000000000000000000000000000000000000000000000000000000000000000000000 > pppoed[1951]: Listening as provider telia > pppoed[1953]: Creating a new socket node > pppoed[1953]: Sending CONNECT from .:exec-1953 -> vr0:orphans.exec-1953 > pppoed[1953]: Sending NGM_SOCK_CMD_NOLINGER to socket > pppoed[1953]: Offering to .:exec-1953 as access concentrator lisa > pppoed[1953]: Sending original request to .:exec-1953 (60 bytes) > pppoed[1953]: Waiting for a SUCCESS reply .:exec-1953 > pppoed[1953]: Received NGM_PPPOE_SUCCESS (hook "exec-1953") > pppoed[1953]: Executing: exec /usr/sbin/ppp -direct telia > Feb 10 14:41:05 lisa ppp[1953]: tun0: Warning: Unindented command (/etc/ppp/ppp.conf line 33) - ignored > Feb 10 14:41:05 lisa ppp[1953]: tun0: Warning: deflink: Reducing MRU to 1492 > > > The client side generates this > > Using interface ppp0 > Connect: ppp0 <--> /dev/pts/1 > sent [LCP ConfReq id=0x5 ] > rcvd [proto=0x7eff] 7d 23 c0 21 7d 21 7d 21 7d 20 7d 38 7d 28 7d 22 7d 27 7d 22 7d 22 7d 26 7d 20 7d 20 7d 20 7d 20 ... > sent [LCP ConfReq id=0x5 ] > Terminating on signal 2. > sent [LCP TermReq id=0x6 "User request"] > Modem hangup > Connection terminated. > Child process /usr/local/bin/pppoe -I eth0 -T 80 -m 1412 (pid 654) terminated with signal 2 > Using interface ppp0 > Connect: ppp0 <--> /dev/pts/1 > sent [LCP ConfReq id=0x1 ] > write: warning: Input/output error (5) > Modem hangup > Connection terminated. > Script /usr/local/bin/pppoe -I eth0 -T 80 -m 1412 finished (pid 658), status = 0x0 > > > > Does any1 have any hints? > > /John -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 11 21:33:13 2000 Delivered-To: freebsd-net@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by builder.freebsd.org (Postfix) with ESMTP id 57C6D3F85 for ; Fri, 11 Feb 2000 21:33:09 -0800 (PST) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 659A1137FB9; Sat, 12 Feb 2000 00:33:01 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id AAA62940; Sat, 12 Feb 2000 00:33:00 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14500.61580.441181.119033@trooper.velocet.net> Date: Sat, 12 Feb 2000 00:33:00 -0500 (EST) To: Gregory Sutter Cc: Archie Cobbs , dgilbert@velocet.ca, Freebsd-net@freebsd.org Subject: Re: VLAN on ethernet nodes? In-Reply-To: <20000211134205.A13236@azazel.zer0.org> References: <20000211112034.A4306@azazel.zer0.org> <200002112122.NAA73362@bubba.whistle.com> <20000211134205.A13236@azazel.zer0.org> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Gregory" == Gregory Sutter writes: Gregory> Is there anything that netgraph _can't_ do? Swedish massage, Gregory> perhaps? When I first read about netgraph, it took awhile to sink in. It certainly solved the problem at hand --- all sorts of different serial protocols and encapsulations being wrapped and unwrapped --- it was a good BSD solution and I liked it. As I started to work on my own netgraph node (out of sheer necesity), I suddenly began to realize the thinly disguised power available in netgraph... I mentioned to Archie that with a ng_route node and a few bits of goo (largly vlan hooks on ethernet nodes, etc.) that the entire netgraph system could give FreeBSD "VRouter" capability --- something that none of the other UN*X's have... and something that you'd pay Cisco a lot of money for. I was idly rolling all these thoughts over in my mind ... and the fact that the standard networking in the kernel _could_ be replaced with this framework (the vrouter concept easily extends to vfirewall, too!), and I happened upon the idea of an ng_local node --- a node that represents the view that the "local" host should see in terms of packets (gone would be the assumption that you'd see anything on any interface by default). It was then that I realized that a _particular_ ng_local node could be bound to a _particular_ instance of jail(8) --- which would fundamentally solve (in an almost perfect manner) the quandry that each jail(8) only has one IP address. By binding each jail(8) to an ng_local, not only could your ng_local have multiple IP addresses (although it's world view is further controlled by how it is connected into the graph), but your jail(8) could interact with non-IP protocols as dictated by the connections of the graph. (See if that idea doesn't just knock you over, eh?) Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 13 5:18:58 2000 Delivered-To: freebsd-net@freebsd.org Received: from terminal.sil.at (terminal.sil.at [194.152.178.15]) by builder.freebsd.org (Postfix) with ESMTP id 3B4FE4181 for ; Sun, 13 Feb 2000 05:18:55 -0800 (PST) Received: from terminal.sil.at (localhost [127.0.0.1]) by terminal.sil.at (8.9.2/8.9.2) with ESMTP id OAA03816 for ; Sun, 13 Feb 2000 14:19:07 +0100 (CET) Message-Id: <200002131319.OAA03816@terminal.sil.at> X-Mailer: exmh version 2.1.1 01/07/2000 To: freebsd-net@FreeBSD.ORG Subject: Re: Etherchannel support? In-reply-to: fordp's message of Tue, 08 Feb 2000 10:31:37 -0600. <3.0.3.32.20000208103137.00718050@pop.interaccess.com> X-Face: "0|_!}6Ay;=lSa@qs\q$u2RZUTyW(m(?80f[OF3eR:4uk6rd&+9lUw"6ACgq]hyak/Io Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've been reading through the archives and found some discussion back in > Feburary of 99 and then again in July about doing this using the netgraph > library. The consensus at the time seemd to be that it could be done with > netgraph but no one had. > > I'd very much like to be able to tie multiple interfaces together so I was > wondering if anyone had done this yet? Or perhaps has some pointers in what > would be involved in doing it myself? > > I need to do something akin to Channel Bonding in a beowulf system. Hallo, Have the same problem - I would need to bundle more than 2 ethernet connections together (to bundle DSL lines) - _theoretical it should be possible to use PPP/FrameRelay over Ethernet and then bundle it with the netgraph multilink-ppp daemon.... but _practical_ ? I think a netgraph HOWTO would be very useful for lots of people. regards, cjm -- SILVER SERVER \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\ \\ \ cjm@sil.at www.sil.at -- PGP-Key-ID: 0xA941452D - CJM17(-RIPE),SIL-MNT http://www.enemy.org -- You can't spell evil with vi. Can you? - No, my name is John Rambo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 13 12:44: 5 2000 Delivered-To: freebsd-net@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by builder.freebsd.org (Postfix) with ESMTP id 6DD774139 for ; Sun, 13 Feb 2000 12:44:01 -0800 (PST) Received: from dukie (Newmarket-ppp90469.sympatico.ca [216.209.38.196]) by smtp11.bellglobal.com (8.8.5/8.8.5) with SMTP id PAA07172 for ; Sun, 13 Feb 2000 15:49:05 -0500 (EST) From: "Marco Rodrigues" To: Subject: natd redirect_port Date: Sun, 13 Feb 2000 15:39:56 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone ever got the redirect_port switch to work with natd? It seems i've tried everything and I can't never get it to work. -redirect_port tcp externalip:telnet internalip:telnet should pass all requests to port 23 on the computer with both nics to a internal box at port 23 correct? I've also tried using ipfw but I haven't seem to get that to work. If someone knows what i'm doing wrong, or what i'm not doing any help would be appreicated. Thanx! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 13 13: 2:56 2000 Delivered-To: freebsd-net@freebsd.org Received: from vidle.i.cz (vidle.i.cz [193.179.36.138]) by builder.freebsd.org (Postfix) with ESMTP id C52913E59 for ; Sun, 13 Feb 2000 13:02:53 -0800 (PST) Received: from ns.i.cz (brana.i.cz [193.179.36.134]) by vidle.i.cz (Postfix) with ESMTP id E36AF30708 for ; Sun, 13 Feb 2000 22:02:58 +0100 (CET) Received: from woody.i.cz (woody.i.cz [192.168.18.29]) by ns.i.cz (Postfix) with ESMTP id 154D836415 for ; Sun, 13 Feb 2000 22:02:58 +0100 (CET) Content-Length: 765 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 13 Feb 2000 22:02:57 +0100 (MET) Reply-To: mm@i.cz From: Martin Machacek To: freebsd-net@freebsd.org Subject: RE: natd redirect_port Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 13-Feb-00 Marco Rodrigues wrote: > Has anyone ever got the redirect_port switch to work with natd? Works flawlessly for me (FreeBSD 3.3). Fo example to redirect incoming TCP packets on address and port to and you have to use: -redirect_port tcp : : > It seems i've tried everything and I can't never get it to work. > -redirect_port tcp externalip:telnet internalip:telnet should pass all > requests to port 23 on the computer with both nics to a internal box at port > 23 correct? Nope. You should swap externalip:telnet and internalip:telnet (real address comes first,e xtenal address second). Martin --- [PGP KeyID F3F409C4] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 13 14:44:57 2000 Delivered-To: freebsd-net@freebsd.org Received: from ns3.khmere.com (216-59-86-175.usa2.flashcom.net [216.59.86.175]) by builder.freebsd.org (Postfix) with ESMTP id 9654C43CA; Sun, 13 Feb 2000 14:44:52 -0800 (PST) Received: from khmere.com (IDENT:nathan@ns4.khmere.com [216.59.86.177]) by ns3.khmere.com (8.9.3/8.8.7) with ESMTP id OAA02106; Sun, 13 Feb 2000 14:45:04 -0800 (PST) Message-ID: <38A7344C.71BA918C@khmere.com> Date: Sun, 13 Feb 2000 14:46:37 -0800 From: nathan@khmere.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i586) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-net@FreeBSD.ORG" , "hackers@FreeBSD.ORG" Subject: Setting the default gw (with c) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings ! I have a question, I need to write a small program that sets the default gw. It is written in C and I have looked at several way to do it. One way is using ioctl but that way seems a little "old" and not very well documented. Here is a simple snippet of my code, now when I run it I get an error "error 22" invalid arg. Does anyone have experience with this and can point out what I am doing wrong ? I did have it to where it would work but the kernel never added my netmask to the routing table. So the route would kinda "hang" their and not do anything. I did tell it that it was being sent but..... also the flags never where set proper on the route (when doing route -dvn flush ) Any help would be great ! (oh if this looks familiar, I learned this from reading both ruote.c and netstat.c. ) struct rt_data_msg{ struct rt_msghdr add_rtm; union{ struct sockaddr sa; struct sockaddr_in sin; struct sockaddr_dl sdl; }rt_dst, rt_gate, rt_mask; }; int set_droute(char *gw){ int sockfd, i, err = 0; int flags = 0, r_addrs = 0; u_long inits; char t_gw[32]; register int l; struct rt_data_msg add_rt; pid_t pid; /* check to see if we have a gateway address or quit */ if(!gw){ ERR("set_droute: FREEBSD no route sent ! %d"); return(BAD); } else{ /* convet this address if not valid quit */ if((inet_aton(gw, &so_gate.sin.sin_addr)) < 0){ ERR("set_droute: FREEBSD route not valid ! %d"); return(BAD); } } memset(&add_rt, 0, sizeof(struct rt_data_msg)); /* check to see if thier is an existing route or not make an entry from scratch */ if( (i = get_droute(t_gw)) == BAD){ /* make the address and netmasks */ if((inet_aton("0.0.0.0", &add_rt.rt_mask.sin.sin_addr)) < 0){ err++; } if((inet_aton("0.0.0.0", &add_rt.rt_dst.sin.sin_addr)) < 0) { err++; } if((inet_aton(gw, &add_rt.rt_gate.sin.sin_addr)) < 0){ err++; } if(err > 0){ ERR("get_droute: FREEBSD cannot set mask or dst or gw invalid addresses %d"); return(BAD); } inits = RTV_EXPIRE; inits |= RTV_RPIPE; inits |= RTV_SPIPE; inits |= RTV_SSTHRESH; r_addrs = RTAX_DST; r_addrs |= RTAX_GATEWAY; r_addrs |= RTAX_NETMASK; flags = RTF_UP; flags |= RTF_GATEWAY; flags |= RTF_STATIC; flags |= RTF_PRCLONING; /* add thier size */ #define ADD_SIZE(w) l = ROUNDUP(w.sa.sa_len) #define ROUNDUP(a) ((a) > 0 ? (1 + (((a) - 1) | (sizeof(long) - 1))) : sizeof(long)); ADD_SIZE(add_rt.rt_dst); ADD_SIZE(add_rt.rt_gate); ADD_SIZE(add_rt.rt_mask); /* add their address family */ #define ADD_FAM(x) x.sin.sin_family = AF_INET; ADD_FAM(add_rt.rt_dst); ADD_FAM(add_rt.rt_gate); ADD_FAM(add_rt.rt_mask); ADD_FAM(add_rt.rt_genmask); /* set up all of the flags and tables */ #define RD add_rt.add_rtm RD.rtm_msglen = l; RD.rtm_version = RTM_VERSION; RD.rtm_type = RTM_ADD; RD.rtm_flags = flags; RD.rtm_addrs = rtm_addrs; RD.rtm_inits = RTF_GATEWAY; RD.rtm_pid = pid = getpid(); RD.rtm_seq = ++SEQ; if( (sockfd = socket(PF_ROUTE, SOCK_RAW, 0)) < 0){ ERR("set_droute: FREEBSD cannot open socket %d"); } /* send it to the kernel */ i = write(sockfd, (char *)&add_rt, l); syslog(LOG_ERR, "errno = %d ", errno); } else{ /* get a buffer for the data */ ERR("get_droute returned ok %d "); } return(GOOD); } Thank you nathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 13 21:21:35 2000 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (dustdevil.waterspout.com [208.13.60.151]) by builder.freebsd.org (Postfix) with ESMTP id A81C34839; Sun, 13 Feb 2000 21:21:31 -0800 (PST) Received: by dustdevil.waterspout.com (Postfix, from userid 1000) id A7ED24B; Mon, 14 Feb 2000 00:21:42 -0500 (EST) Date: Mon, 14 Feb 2000 00:21:42 -0500 From: "C. Stephen Gunn" To: freebsd-net@freebsd.org Cc: wollman@freebsd.org, wpaul@freebsd.org, mdodd@freebsd.org, csg@waterspout.com Subject: Re: 802.1Q VLANs Message-ID: <20000214002142.A12511@dustdevil.waterspout.com> References: <200002031847.NAA62013@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200002031847.NAA62013@khavrinen.lcs.mit.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Feb 03, 2000 at 01:47:08PM -0500, Garrett Wollman wrote: > If the interface driver is written to be able to accept 1500-byte > frames with an 18-byte header (as opposed to the ``normal'' 14-byte > header), it needs to inform the upper layers of this by setting its > advertised header length (ifi_hdrlen) to 18 rather than 14. The > driver should always do this, if the hardware is capable, so that > those frames will be made available to bpf. But this isn't necissairly true. IEEE 802.1Q says that proper implementations will be able to handle tagged and untagged packets on the same physical link. So we have some packets that arrive with tags (18 bytes), and some untagged, on the "native" vlan for the given interface (14 bytes). Right now untagged traffic (on a mixed link) is presented to the upper protocol layers by the parent device. This isn't quite kosher since 802.1Q states this should be routed to the "default" VLAN for the given interface. It _IS_ permissable to mark a given interface as "Tagged" traffic only. In this case we should increase ifi_hdrlen, but only in this case. This also requires some awareness elsewhere that a given interface in the kernel is a "trunk" and not a normal interface. Any untagged traffic should generate an error condition, as should attempts to set the network address/netmask, etc. > > Well, I see no reason to restrict people to cards that don't support large > > frames; if they really need to use VLANs they can adjust the MTU down. In > > the real world MTU discovery will insure that they aren't too big of a > > problem. > > No, it won't. In the real world, MTU discovery will never be invoked, > because switches do not allow users to reconfigure the MTU. I agree that adjusting the MTU is simply not a viable option. Most of the world (incorrectly, albeit) assumes that ETHERMTU will always be 1500 bytes. (This includes the guys who run the routers that connect me to the world. ) With the gracious assistance of Bill Paul (wpaul@freebsd.org), I've hacked up the xl(4) driver to accomodate 1522 byte payloads. It works in my experiments. According to Bill, this hack will only operate on the newer 3c905B-TX xl cards from 3com. There's a lot of missing infrastructure to support 802.1Q well in FreeBSD. This is a kludge to get VLANs working with a 1500 byte MTU _NOW_. Nothing more. If VLANs are compiled into the kernel, it simply adjusts the "MAXPKTSIZE" register on the card on if_attach() and when handling SIOCSIMTU. It does not adjust ifi_hdrlen for the reasons state above. I'd appreciate review/suggestions on the changes and how to implement the features "across the board." - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc. Email: csg@waterspout.com 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 13 21:26:50 2000 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (dustdevil.waterspout.com [208.13.60.151]) by builder.freebsd.org (Postfix) with ESMTP id 1058E4971; Sun, 13 Feb 2000 21:26:45 -0800 (PST) Received: by dustdevil.waterspout.com (Postfix, from userid 1000) id D6E054B; Mon, 14 Feb 2000 00:26:56 -0500 (EST) Date: Mon, 14 Feb 2000 00:26:56 -0500 From: "C. Stephen Gunn" To: freebsd-net@freebsd.org Cc: wollman@freebsd.org, wpaul@freebsd.org, mdodd@freebsd.org, csg@waterspout.com Subject: Re: 802.1Q VLANs Message-ID: <20000214002656.A12799@dustdevil.waterspout.com> References: <200002031847.NAA62013@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200002031847.NAA62013@khavrinen.lcs.mit.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oh yeah.. Here's the patch: Index: if_xl.c =================================================================== RCS file: /project/cvs/FreeBSD/src/sys/pci/if_xl.c,v retrieving revision 1.22.2.24 diff -c -r1.22.2.24 if_xl.c *** if_xl.c 1999/12/17 15:58:13 1.22.2.24 --- if_xl.c 2000/02/10 18:35:19 *************** *** 117,122 **** --- 117,127 ---- #include #endif + #include "vlan.h" + #if NVLAN > 0 + #include + #endif + #include /* for vtophys */ #include /* for vtophys */ #include /* for DELAY */ *************** *** 1805,1810 **** --- 1810,1830 ---- if_attach(ifp); ether_ifattach(ifp); + #if NVLAN > 0 + /* + * XXX: If this is a 3C905B card, we program the card to accept + * ETHERMTU + ETHER_HDR_LEN +EVL_ENCAPLEN packets. This allows + * VLAN interfaces to operate with 1500 byte MTUs. + */ + if (sc->xl_type == XL_TYPE_905B) { + XL_SEL_WIN(3); + CSR_WRITE_2(sc, XL_W3_MAXPKTSIZE, + ETHERMTU + ETHER_HDR_LEN + EVL_ENCAPLEN); + printf("xl%d: VLANs Enabled - set MAXPKTSIZE= %d\n", + sc->xl_unit, ETHERMTU + ETHER_HDR_LEN + EVL_ENCAPLEN); + } + #endif /* NVLAN */ + #if NBPFILTER > 0 bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif *************** *** 3017,3022 **** --- 3037,3059 ---- case SIOCGIFADDR: case SIOCSIFMTU: error = ether_ioctl(ifp, command, data); + #if NVLAN > 0 + /* + * XXX: If this is a 3C905B Card, adjust the onboard MAXPKTSIZE + * register to allow (mtu + ETHER_HDR_LEN +EVL_ENCAPLEN) size + * frames. The hardware rejects larger frames as giants. + * This makes room for VLAN Tags in the ethernet header on + * 802.1Q-tagged links. + */ + if ((error == 0) && (sc->xl_type == XL_TYPE_905B)) { + XL_SEL_WIN(3); + CSR_WRITE_2(sc, XL_W3_MAXPKTSIZE, + ifr->ifr_mtu + ETHER_HDR_LEN + EVL_ENCAPLEN); + printf("xl%d: VLANs Enabled - changed MAXPKTSIZE= %d\n", + sc->xl_unit, + ifr->ifr_mtu + ETHER_HDR_LEN + EVL_ENCAPLEN); + #endif /* NVLAN */ + } break; case SIOCSIFFLAGS: XL_SEL_WIN(5); Index: if_xlreg.h =================================================================== RCS file: /project/cvs/FreeBSD/src/sys/pci/if_xlreg.h,v retrieving revision 1.9.2.10 diff -c -r1.9.2.10 if_xlreg.h *** if_xlreg.h 1999/12/17 15:58:14 1.9.2.10 --- if_xlreg.h 2000/02/10 15:58:09 *************** *** 256,261 **** --- 256,262 ---- #define XL_W3_FREE_TX 0x0C #define XL_W3_FREE_RX 0x0A #define XL_W3_MAC_CTRL 0x06 + #define XL_W3_MAXPKTSIZE 0x04 #define XL_ICFG_CONNECTOR_MASK 0x00F00000 #define XL_ICFG_CONNECTOR_BITS 20 -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc. Email: csg@waterspout.com 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 0:37: 1 2000 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by builder.freebsd.org (Postfix) with ESMTP id 3F1F34955 for ; Mon, 14 Feb 2000 00:36:58 -0800 (PST) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.04) with ESMTP id RAA14499; Mon, 14 Feb 2000 17:36:59 +0900 (JST) To: v6-bsd-related: ; Subject: KAME IPv6/IPsec stack, STABLE kit 20000214 From: core@kame.net Date: Mon, 14 Feb 2000 17:36:59 +0900 Message-ID: <14496.950517419@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (sorry if you have received this more than once) As usual, KAME Project has released by-monthly "STABLE" kit of IPv6/IPsec network code for the following platforms (yes, we have 6 supported platforms): BSD/OS 3.1 and 4.1 FreeBSD 2.2.8 and 3.4 NetBSD 1.4.1 OpenBSD 2.6 Our code has been tested by the TAHI IPv6 conformance test suite (http://www.tahi.org/). They are redistributable under BSD-like license, i.e. free of charge but absolutely no warranty. They are avaiable from the following web site: http://www.kame.net/ To know the changes and improvements from the previous STABLE kit, please refer to the CHANGELOG file in the distribution. There are bunch of good changes happened since the previous STABLE kit, like the complete integration of ALTQ, more stabilization of IPsec portion, advanced API clarifications and others. Bunch of documents are included in tar.gz file so please be sure to check those. NOTE: KAME code is being merged into {Free,Net,Open}BSD-current tree. The difference between KAME kit and merged tree are like below: (1) KAME kit comes with more experimental protocols/APIs support and userland programs (which may attract researchers more), (2) KAME kit is based on public release version of *BSD, and (3) the merged tree will give tightly integrated IPv6-ready operating system when it gets released as public release version of *BSD than KAME kit. --KAME Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 8:25:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by builder.freebsd.org (Postfix) with ESMTP id E23E2499F for ; Mon, 14 Feb 2000 08:25:33 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA65769; Mon, 14 Feb 2000 11:25:23 -0500 (EST) (envelope-from wollman) Date: Mon, 14 Feb 2000 11:25:23 -0500 (EST) From: Garrett Wollman Message-Id: <200002141625.LAA65769@khavrinen.lcs.mit.edu> To: "C. Stephen Gunn" Cc: freebsd-net@freebsd.org Subject: Re: 802.1Q VLANs In-Reply-To: <20000214002142.A12511@dustdevil.waterspout.com> References: <200002031847.NAA62013@khavrinen.lcs.mit.edu> <20000214002142.A12511@dustdevil.waterspout.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Right now untagged traffic (on a mixed link) is presented to the > upper protocol layers by the parent device. This isn't quite > kosher since 802.1Q states this should be routed to the "default" > VLAN for the given interface. 802.1Q defines how bridges work, not how operating systems work. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 9:16:14 2000 Delivered-To: freebsd-net@freebsd.org Received: from netserver.pth.com (fx3-1-125.mgfairfax.rr.com [24.28.200.125]) by builder.freebsd.org (Postfix) with ESMTP id 4B95F3DE3 for ; Mon, 14 Feb 2000 09:16:11 -0800 (PST) Received: from [172.30.136.11] (helo=dell) by netserver.pth.com with smtp (Exim 3.03 #1) id 12KP6f-0002Mf-00 for freebsd-net@freebsd.org; Mon, 14 Feb 2000 12:16:17 -0500 Message-ID: <005301bf770e$75f98ec0$0b881eac@marcgroup.com> From: "Paul Haddad" To: Subject: Compatible VPN software & NAT Date: Mon, 14 Feb 2000 12:10:57 -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.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All, Has anyone been able to get Compatible Software's VPN software to work through freebsd's NAT? My current setup is I have a single DHCP acquired IP that my freebsd box uses to NAT to the outside world. I'd like to get the VPN software working on a linux box, but don't want to put that box dirrectly on the internet. Compatible's VPN software contains some linux kernel modules so I'm pretty certain it won't run on freebsd. Assuming natd can't handle the packets that this VPN software generates would it be possible to have the following setup. The freebsd box requests 2 different IP addresses from the DHCP server The linux box default interface gets set to the second IP address The freebsd box forwards only certain packets to the linux box Thanks in advance, --- Paul Haddad (paul@pth.com) Do not meddle in the affairs of troff, for it is subtle and quick to anger. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 9:20:10 2000 Delivered-To: freebsd-net@freebsd.org Received: from p0016c23.us.kpmg.com (p0016c23.us.kpmg.com [199.207.255.23]) by builder.freebsd.org (Postfix) with ESMTP id B624C4008 for ; Mon, 14 Feb 2000 09:20:06 -0800 (PST) Received: from p0016c56.kweb.us.kpmg.com by p0016c23.us.kpmg.com(Pro-8.9.3/Pro-8.9.3) with SMTP id MAA27824 for ; Mon, 14 Feb 2000 12:20:18 -0500 (EST) Received: from p0016c22.kweb.us.kpmg.com by p0016c56.kweb.us.kpmg.com via smtpd (for p0016c23.us.kpmg.com [199.207.255.23]) with SMTP; 14 Feb 2000 17:20:31 UT Received: from usnssexc19.kweb.us.kpmg.com by kpmg.com(Pro-8.9.2/Pro-8.9.2) with ESMTP id MAA21690 for ; Mon, 14 Feb 2000 12:20:18 -0500 (EST) Received: from usnssexc19.kweb.us.kpmg.com (unverified) by usnssexc19.kweb.us.kpmg.com (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Mon, 14 Feb 2000 12:09:31 -0500 Received: by usnssexc19.kweb.us.kpmg.com with Internet Mail Service (5.5.2650.21) id ; Mon, 14 Feb 2000 12:09:31 -0500 Message-Id: <8389C74A65EFD111B03800805FA7658F06D71F6A@USDALEXC01> From: "Fisch, Eric" To: Brian Somers Cc: freebsd-net@freebsd.org Subject: RE: PPP Gateway Routing Problem Date: Mon, 14 Feb 2000 12:16:02 -0500 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 Yes.. Eye-openers.. As it turns out, DHCP was (a big part of) the problem. Before starting ppp, a 'netstat -nr' would indicate the gateway IP address as the "default" route. This worked great for all dhcp requests. When ppp started, however, it changed the default route to the ISP's IP address. So, network clients would properly get an IP address from their dhcp-requesting broadcast, but then they would see a default route to an IP address they could never reach. By using my dhcpd.conf to force clients to have the gateway be the default route, all of the routing problems worked out. The clients route everything to the gateway and the gateway's default route to the ISP picks it up from there. Now my problem is that some service is preventing my ppp from timing out properly. When the system boots, it connects to the ISP (I don't know why). The ppp.conf file is set to timeout at 10 minutes, but it never does. I have to pick up the phone receiver to disrupt traffic and force a disconnect. Interestingly, it does NOT reconnect until I manually force an out-bound packet (ftp, telent, ping, etc.), and when it does connect, it stays connected until I pick up the receiver again. The hunt goes on... Thanks for all your suggestions, Eric -----Original Message----- From: Brian Somers [mailto:brian@Awfulhak.org] Sent: Friday, February 11, 2000 3:23 PM To: Fisch, Eric Cc: freebsd-net@FreeBSD.ORG; brian@hak.lan.Awfulhak.org Subject: Re: PPP Gateway Routing Problem > I am having what appears to be a routing problem with a PPP gateway and am > hoping someone can shed some light on the issue. I have a small network of > windows/UNIX systems behind a FreeBSD gateway box. The gateway box is > providing DNS and DHCP services to the other systems without any problem. I > have tried to set up the gateway box to do PPP-on-demand for the entire > network with limited success. PPP works flawlessly on the gateway box. > When I am on the "inside", however, I get nothing. I am able to connect to > the gateway, but no further. Interestingly enough, when I "ping" a system > from the inside box, I get proper name resolution, but "Host is Unreachable" > errors as well. This leads me to believe that I have a routing issue from > the gateway to the inside boxes. I think I am missing something in my > rc.conf settings. Heck, if I had any clue what was wrong I would not be > posting. [.....] > gateway_enable="YES" Aww, that was my first suggestion ! Your best bet is probably to run tcpdump on your internal interface to ensure the packets are getting that far. If they're not, you need to add a default route to your dhcpd config. If packets are getting that far, enable tcp/ip logging in ppp and see if the packets are getting that far - proving that you're acting as a gateway. If the packets get that far, enable physical logging to ensure that they're being written to the link. Any eye-openers ? -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message ***************************************************************************** The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing KPMG client engagement letter. ***************************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 9:43:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by builder.freebsd.org (Postfix) with ESMTP id 1D4924C75; Mon, 14 Feb 2000 09:43:20 -0800 (PST) Received: from localhost (lloyd@localhost) by brunel.uk1.vbc.net (8.9.3/8.9.3) with ESMTP id RAA40840; Mon, 14 Feb 2000 17:43:36 GMT Date: Mon, 14 Feb 2000 17:43:36 +0000 (GMT) From: Lloyd Rennie To: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: GateD returns 'No buffer space available' upon a routing table build... 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 Hey all; We have several routers storing a full global routing table. Recently, this table has grown rather large (currently at ~75k routes). All are behaving in the same way; When GateD starts, I can watch it growing on a 'top', as it builds a routing table. Suddenly, it stops growing, cpu usage drops to nill, and many kernel messages are spewed-out; Feb 14 13:47:34 gate3 /kernel: arp_rtrequest: malloc failed Feb 14 13:47:34 gate3 /kernel: arplookup 194.207.0.32 failed: could not allocate llinfo Feb 14 13:47:34 gate3 /kernel: arpresolve: can't allocate llinfo for 194.207.0.32rt Feb 14 13:47:34 gate3 gated[88]: KRT SENT type ADD(1)flags UP GW(3) error 55: Nobuffer space available Feb 14 13:47:34 gate3 gated[88]: KRT SENT dest 204.0.41 gateway 194.207.0.46 netmask 255.255.255 Feb 14 13:47:37 gate3 /kernel: arplookup 194.207.0.32 failed: could not allocate llinfo etc... The first symptom seems always to be the malloc failure. This happens within the first minute of uptime on this particular machine, a p2-400/128Mb. All machines run FreeBSD-3.2. The others take longer to develop the fault, but have slower processors. My assumption is that the global routing table has grown to such a size that there is no longer enough kernel memory available to store it. I checked through the LINT file, but couldn't find any useful options. Started looking tentatively through the kernel source, but (bear in mind I'd rather not lower maxusers anymore) came to a dead end with a 0-byte file called vm_opt.h :( So I'd like to ask... * Which particular type of 'buffer space' is this? * What can I do to 'tweak' it (ie. assign more) * Is the issue resolved in a later release of FreeBSD (pref in the STABLE tree, which reminds me - when's the codefreeze on v4 end?) Any help with this issue would be appreciated... -- Lloyd Rennie VBCnet GB Ltd lloyd@vbc.net tel +44 (0) 117 929 1316 http://www.vbc.net fax +44 (0) 117 927 2015 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 9:55:13 2000 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (dustdevil.waterspout.com [208.13.60.151]) by builder.freebsd.org (Postfix) with ESMTP id 4B7EB3DBF; Mon, 14 Feb 2000 09:55:11 -0800 (PST) Received: by dustdevil.waterspout.com (Postfix, from userid 1000) id E163E4B; Mon, 14 Feb 2000 12:55:27 -0500 (EST) Date: Mon, 14 Feb 2000 12:55:27 -0500 From: "C. Stephen Gunn" To: freebsd-net@freebsd.org Cc: wollman@freebsd.org, csg@waterspout.com Subject: Re: 802.1Q VLANs Message-ID: <20000214125527.A14822@dustdevil.waterspout.com> References: <200002031847.NAA62013@khavrinen.lcs.mit.edu> <20000214002142.A12511@dustdevil.waterspout.com> <200002141625.LAA65769@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200002141625.LAA65769@khavrinen.lcs.mit.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Right now untagged traffic (on a mixed link) is presented to the > > upper protocol layers by the parent device. This isn't quite > > kosher since 802.1Q states this should be routed to the "default" > > VLAN for the given interface. > > 802.1Q defines how bridges work, not how operating systems work. Your FreeBSD box is hooked to 802.1Q compliant bridge. It's still true that you could see tagged and untagged frames on the same wire. The only point of running the VLAN code (currently, note- priority support would be nice as well) is to have the lower protocol layers function as a VLAN aware bridge. They forward frames to the correct logical network interface. I believe it appropriate to make the lower protocol layers on FreeBSD comply with the specification for a bridge. This means associating a native VLAN with any trunk interface. Then, routing untagged packets to the specified VLAN interface. This approach unifies the way you should configure your bridge/switch and your FreeBSD Box. This could also force traffic to be routed through the VLAN interfaces not the physical "trunk" device. - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc. Email: csg@waterspout.com 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 11:35:35 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by builder.freebsd.org (Postfix) with ESMTP id 6A6D04DA0 for ; Mon, 14 Feb 2000 11:35:29 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA66996; Mon, 14 Feb 2000 14:35:39 -0500 (EST) (envelope-from wollman) Date: Mon, 14 Feb 2000 14:35:39 -0500 (EST) From: Garrett Wollman Message-Id: <200002141935.OAA66996@khavrinen.lcs.mit.edu> To: "C. Stephen Gunn" Cc: freebsd-net@freebsd.org Subject: Re: 802.1Q VLANs In-Reply-To: <20000214125527.A14822@dustdevil.waterspout.com> References: <200002031847.NAA62013@khavrinen.lcs.mit.edu> <20000214002142.A12511@dustdevil.waterspout.com> <200002141625.LAA65769@khavrinen.lcs.mit.edu> <20000214125527.A14822@dustdevil.waterspout.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > The only point of running the VLAN code (currently, note- priority > support would be nice as well) is to have the lower protocol layers > function as a VLAN aware bridge. Um, no. The point of running the VLAN code is to usefully interpret frames with VLAN tags on them. As the designer of the code in question, I think I can say that with some certainty. I originally considered implementing VLAN support through ``subinterfaces'' a la Sun, but decided that this would require a huge ABI change which we didn't want to make. > I believe it appropriate to make the lower protocol layers on FreeBSD > comply with the specification for a bridge. I do not, unless bridging is actually configured. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 11:53:10 2000 Delivered-To: freebsd-net@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 1D2AE3EC8; Mon, 14 Feb 2000 11:53:07 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA11486; Mon, 14 Feb 2000 11:53:07 -0800 (PST) (envelope-from dillon) Date: Mon, 14 Feb 2000 11:53:07 -0800 (PST) From: Matthew Dillon Message-Id: <200002141953.LAA11486@apollo.backplane.com> To: Lloyd Rennie Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: GateD returns 'No buffer space available' upon a routing table build... References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :etc... : :The first symptom seems always to be the malloc failure. This happens :within the first minute of uptime on this particular machine, a :p2-400/128Mb. All machines run FreeBSD-3.2. The others take longer to :develop the fault, but have slower processors. 'vmstat -m' before, during, and after the gated startup. You are probably running into the malloc pool KVM limit. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 14: 7:39 2000 Delivered-To: freebsd-net@freebsd.org Received: from ns3.khmere.com (216-59-86-175.usa2.flashcom.net [216.59.86.175]) by builder.freebsd.org (Postfix) with ESMTP id 5656D4B9E for ; Mon, 14 Feb 2000 14:06:55 -0800 (PST) Received: from getrelevant.com (IDENT:nathan@newwerk.getrelevant.com [63.211.149.44]) by ns3.khmere.com (8.9.3/8.8.7) with ESMTP id OAA01958 for ; Mon, 14 Feb 2000 14:07:15 -0800 (PST) Message-ID: <38A87C88.33D15062@getrelevant.com> Date: Mon, 14 Feb 2000 14:07:04 -0800 From: Nathan Organization: Getrelevant X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13_SIS i686) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-net@FreeBSD.ORG" Subject: HELP ! programing routes ?? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry if this is a repeat ! I have a question, I need to write a small program that sets the default gw. It is written in C and I have looked at several way to do it. One way is using ioctl but that way seems a little "old" and not very well documented. Here is a simple snippet of my code, now when I run it I get an error "error 22" invalid arg. Does anyone have experience with this and can point out what I am doing wrong ? I did have it to where it would work but the kernel never added my netmask to the routing table. So the route would kinda "hang" their and not do anything. I did tell it that it was being sent but..... also the flags never where set proper on the route (when doing route -dvn flush ) Any help would be great ! (oh if this looks familiar, I learned this from reading both ruote.c and netstat.c. ) struct rt_data_msg{ struct rt_msghdr add_rtm; union{ struct sockaddr sa; struct sockaddr_in sin; struct sockaddr_dl sdl; }rt_dst, rt_gate, rt_mask; }; int set_droute(char *gw){ int sockfd, i, err = 0; int flags = 0, r_addrs = 0; u_long inits; char t_gw[32]; register int l; struct rt_data_msg add_rt; pid_t pid; /* check to see if we have a gateway address or quit */ if(!gw){ ERR("set_droute: FREEBSD no route sent ! %d"); return(BAD); } else{ /* convet this address if not valid quit */ if((inet_aton(gw, &so_gate.sin.sin_addr)) < 0){ ERR("set_droute: FREEBSD route not valid ! %d"); return(BAD); } } memset(&add_rt, 0, sizeof(struct rt_data_msg)); /* check to see if thier is an existing route or not make an entry from scratch */ if( (i = get_droute(t_gw)) == BAD){ /* make the address and netmasks */ if((inet_aton("0.0.0.0", &add_rt.rt_mask.sin.sin_addr)) < 0){ err++; } if((inet_aton("0.0.0.0", &add_rt.rt_dst.sin.sin_addr)) < 0) { err++; } if((inet_aton(gw, &add_rt.rt_gate.sin.sin_addr)) < 0){ err++; } if(err > 0){ ERR("get_droute: FREEBSD cannot set mask or dst or gw invalid addresses %d"); return(BAD); } inits = RTV_EXPIRE; inits |= RTV_RPIPE; inits |= RTV_SPIPE; inits |= RTV_SSTHRESH; r_addrs = RTAX_DST; r_addrs |= RTAX_GATEWAY; r_addrs |= RTAX_NETMASK; flags = RTF_UP; flags |= RTF_GATEWAY; flags |= RTF_STATIC; flags |= RTF_PRCLONING; /* add thier size */ #define ADD_SIZE(w) l = ROUNDUP(w.sa.sa_len) #define ROUNDUP(a) ((a) > 0 ? (1 + (((a) - 1) | (sizeof(long) - 1))) : sizeof(long)); ADD_SIZE(add_rt.rt_dst); ADD_SIZE(add_rt.rt_gate); ADD_SIZE(add_rt.rt_mask); /* add their address family */ #define ADD_FAM(x) x.sin.sin_family = AF_INET; ADD_FAM(add_rt.rt_dst); ADD_FAM(add_rt.rt_gate); ADD_FAM(add_rt.rt_mask); ADD_FAM(add_rt.rt_genmask); /* set up all of the flags and tables */ #define RD add_rt.add_rtm RD.rtm_msglen = l; RD.rtm_version = RTM_VERSION; RD.rtm_type = RTM_ADD; RD.rtm_flags = flags; RD.rtm_addrs = rtm_addrs; RD.rtm_inits = RTF_GATEWAY; RD.rtm_pid = pid = getpid(); RD.rtm_seq = ++SEQ; if( (sockfd = socket(PF_ROUTE, SOCK_RAW, 0)) < 0){ ERR("set_droute: FREEBSD cannot open socket %d"); } /* send it to the kernel */ i = write(sockfd, (char *)&add_rt, l); syslog(LOG_ERR, "errno = %d ", errno); } else{ /* get a buffer for the data */ ERR("get_droute returned ok %d "); } return(GOOD); } Thank you nathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 14:40: 0 2000 Delivered-To: freebsd-net@freebsd.org Received: from ns3.khmere.com (216-59-86-175.usa2.flashcom.net [216.59.86.175]) by builder.freebsd.org (Postfix) with ESMTP id 1DCB750F6 for ; Mon, 14 Feb 2000 14:33:02 -0800 (PST) Received: from getrelevant.com (IDENT:nathan@newwerk.getrelevant.com [63.211.149.44]) by ns3.khmere.com (8.9.3/8.8.7) with ESMTP id OAA01986; Mon, 14 Feb 2000 14:33:16 -0800 (PST) Message-ID: <38A882A2.30A31434@getrelevant.com> Date: Mon, 14 Feb 2000 14:33:06 -0800 From: Nathan Organization: Getrelevant X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13_SIS i686) X-Accept-Language: en MIME-Version: 1.0 To: darcy@ok-connect.com, "freebsd-net@FreeBSD.ORG" Subject: Re: HELP ! programing routes ?? References: R01YxYj Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org darcy@ok-connect.com wrote: > ----- ORIGINAL INTERNET MAIL FOLLOWS 02/14/2000 02:21 PM PST ----- > From: darcy@ok-connect.com > To: nboeger > > Well why not just exec("route add default xxx.xxx.xxx.xxx"); > > At 02:07 PM 2/14/00 -0800, you wrote: > >Sorry if this is a repeat ! > > > > > >I have a question, I need to write a small program that sets the default > > > >gw. It is written in C and I have looked at several way to do it. One > >way is using ioctl but that way seems a little "old" and not very well > >documented. Here is a simple snippet of my code, now when I run it I get > > > >an error "error 22" invalid arg. Does anyone have experience with this > >and can point out what I am doing wrong ? I did have it to where it > >would work but the kernel never added my netmask to the routing table. > >So the route would kinda "hang" their and not do anything. I did tell it > > > >that it was being sent but..... also the flags never where set proper on > > > >the route (when doing route -dvn flush ) > > > > > >Any help would be great ! (oh if this looks familiar, I learned this > >from reading both ruote.c and netstat.c. ) > > > >struct rt_data_msg{ > > struct rt_msghdr add_rtm; > > union{ > > struct sockaddr sa; > > struct sockaddr_in sin; > > struct sockaddr_dl sdl; > > }rt_dst, rt_gate, rt_mask; > >}; > > > >int set_droute(char *gw){ > > > > int sockfd, i, err = 0; > > int flags = 0, r_addrs = 0; > > u_long inits; > > char t_gw[32]; > > register int l; > > struct rt_data_msg add_rt; > > pid_t pid; > > > > /* check to see if we have a gateway address or quit */ > > if(!gw){ > > ERR("set_droute: FREEBSD no route sent ! %d"); > > return(BAD); > > } > > else{ > > /* convet this address if not valid quit */ > > if((inet_aton(gw, &so_gate.sin.sin_addr)) < 0){ > > ERR("set_droute: FREEBSD route not valid ! %d"); > > > > return(BAD); > > } > > } > > > > memset(&add_rt, 0, sizeof(struct rt_data_msg)); > > > > /* check to see if thier is an existing route or not make an > >entry from scratch */ > > if( (i = get_droute(t_gw)) == BAD){ > > > > /* make the address and netmasks */ > > > > if((inet_aton("0.0.0.0", &add_rt.rt_mask.sin.sin_addr)) > >< 0){ err++; } > > if((inet_aton("0.0.0.0", &add_rt.rt_dst.sin.sin_addr)) < > > > >0) { err++; } > > if((inet_aton(gw, &add_rt.rt_gate.sin.sin_addr)) < 0){ > >err++; } > > if(err > 0){ > > ERR("get_droute: FREEBSD cannot set mask or dst > >or gw invalid addresses %d"); > > return(BAD); > > } > > > > inits = RTV_EXPIRE; > > inits |= RTV_RPIPE; > > inits |= RTV_SPIPE; > > inits |= RTV_SSTHRESH; > > > > r_addrs = RTAX_DST; > > r_addrs |= RTAX_GATEWAY; > > r_addrs |= RTAX_NETMASK; > > > > flags = RTF_UP; > > flags |= RTF_GATEWAY; > > flags |= RTF_STATIC; > > flags |= RTF_PRCLONING; > > > > /* add thier size */ > >#define ADD_SIZE(w) l = ROUNDUP(w.sa.sa_len) > >#define ROUNDUP(a) ((a) > 0 ? (1 + (((a) - 1) | (sizeof(long) - 1))) > >: sizeof(long)); > > > > ADD_SIZE(add_rt.rt_dst); > > ADD_SIZE(add_rt.rt_gate); > > ADD_SIZE(add_rt.rt_mask); > > > > /* add their address family */ > >#define ADD_FAM(x) x.sin.sin_family = AF_INET; > > ADD_FAM(add_rt.rt_dst); > > ADD_FAM(add_rt.rt_gate); > > ADD_FAM(add_rt.rt_mask); > > ADD_FAM(add_rt.rt_genmask); > > > > /* set up all of the flags and tables */ > >#define RD add_rt.add_rtm > > RD.rtm_msglen = l; > > RD.rtm_version = RTM_VERSION; > > RD.rtm_type = RTM_ADD; > > RD.rtm_flags = flags; > > RD.rtm_addrs = rtm_addrs; > > RD.rtm_inits = RTF_GATEWAY; > > RD.rtm_pid = pid = getpid(); > > RD.rtm_seq = ++SEQ; > > > > if( (sockfd = socket(PF_ROUTE, SOCK_RAW, 0)) < 0){ > > ERR("set_droute: FREEBSD cannot open socket > >%d"); > > } > > /* send it to the kernel */ > > i = write(sockfd, (char *)&add_rt, l); > > syslog(LOG_ERR, "errno = %d ", errno); > > } > > else{ > > /* get a buffer for the data */ > > ERR("get_droute returned ok %d "); > > } > > > > return(GOOD); > >} > > > > > >Thank you > > > >nathan > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-net" in the body of the message > > > > Beacuse that would be a security leak and other reasons of the like. What I need to do is be able to set this from within my program with out calling popen or exec ..... Can you see any problems in the code ? thank you nathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 15: 9:43 2000 Delivered-To: freebsd-net@freebsd.org Received: from ns3.khmere.com (216-59-86-175.usa2.flashcom.net [216.59.86.175]) by builder.freebsd.org (Postfix) with ESMTP id 3C3C1541F for ; Mon, 14 Feb 2000 14:45:33 -0800 (PST) Received: from getrelevant.com (IDENT:nathan@newwerk.getrelevant.com [63.211.149.44]) by ns3.khmere.com (8.9.3/8.8.7) with ESMTP id OAA02007; Mon, 14 Feb 2000 14:45:48 -0800 (PST) Message-ID: <38A88592.8F1B94E7@getrelevant.com> Date: Mon, 14 Feb 2000 14:45:38 -0800 From: Nathan Organization: Getrelevant X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13_SIS i686) X-Accept-Language: en MIME-Version: 1.0 To: rbg@pmr.com, "freebsd-net@FreeBSD.ORG" Subject: Re: HELP ! programing routes ?? References: R01YxZF Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org rbg@pmr.com wrote: > ----- ORIGINAL INTERNET MAIL FOLLOWS 02/14/2000 02:26 PM PST ----- > From: rbg@pmr.com > To: nboeger > > Nath.. > > I don't see were l is getting set to the size you're > writing to the socket... > > ----- Original Message ----- > From: "Nathan" > To: > Sent: Monday, February 14, 2000 4:07 PM > Subject: HELP ! programing routes ?? > > > Sorry if this is a repeat ! > > > > > > I have a question, I need to write a small program that sets the default > > > > gw. It is written in C and I have looked at several way to do it. One > > way is using ioctl but that way seems a little "old" and not very well > > documented. Here is a simple snippet of my code, now when I run it I get > > > > an error "error 22" invalid arg. Does anyone have experience with this > > and can point out what I am doing wrong ? I did have it to where it > > would work but the kernel never added my netmask to the routing table. > > So the route would kinda "hang" their and not do anything. I did tell it > > > > that it was being sent but..... also the flags never where set proper on > > > > the route (when doing route -dvn flush ) > > > > > > Any help would be great ! (oh if this looks familiar, I learned this > > from reading both ruote.c and netstat.c. ) > > > > struct rt_data_msg{ > > struct rt_msghdr add_rtm; > > union{ > > struct sockaddr sa; > > struct sockaddr_in sin; > > struct sockaddr_dl sdl; > > }rt_dst, rt_gate, rt_mask; > > }; > > > > int set_droute(char *gw){ > > > > int sockfd, i, err = 0; > > int flags = 0, r_addrs = 0; > > u_long inits; > > char t_gw[32]; > > register int l; > > struct rt_data_msg add_rt; > > pid_t pid; > > > > /* check to see if we have a gateway address or quit */ > > if(!gw){ > > ERR("set_droute: FREEBSD no route sent ! %d"); > > return(BAD); > > } > > else{ > > /* convet this address if not valid quit */ > > if((inet_aton(gw, &so_gate.sin.sin_addr)) < 0){ > > ERR("set_droute: FREEBSD route not valid ! %d"); > > > > return(BAD); > > } > > } > > > > memset(&add_rt, 0, sizeof(struct rt_data_msg)); > > > > /* check to see if thier is an existing route or not make an > > entry from scratch */ > > if( (i = get_droute(t_gw)) == BAD){ > > > > /* make the address and netmasks */ > > > > if((inet_aton("0.0.0.0", &add_rt.rt_mask.sin.sin_addr)) > > < 0){ err++; } > > if((inet_aton("0.0.0.0", &add_rt.rt_dst.sin.sin_addr)) < > > > > 0) { err++; } > > if((inet_aton(gw, &add_rt.rt_gate.sin.sin_addr)) < 0){ > > err++; } > > if(err > 0){ > > ERR("get_droute: FREEBSD cannot set mask or dst > > or gw invalid addresses %d"); > > return(BAD); > > } > > > > inits = RTV_EXPIRE; > > inits |= RTV_RPIPE; > > inits |= RTV_SPIPE; > > inits |= RTV_SSTHRESH; > > > > r_addrs = RTAX_DST; > > r_addrs |= RTAX_GATEWAY; > > r_addrs |= RTAX_NETMASK; > > > > flags = RTF_UP; > > flags |= RTF_GATEWAY; > > flags |= RTF_STATIC; > > flags |= RTF_PRCLONING; > > > > /* add thier size */ > > #define ADD_SIZE(w) l = ROUNDUP(w.sa.sa_len) > > #define ROUNDUP(a) ((a) > 0 ? (1 + (((a) - 1) | (sizeof(long) - 1))) > > : sizeof(long)); > > > > ADD_SIZE(add_rt.rt_dst); > > ADD_SIZE(add_rt.rt_gate); > > ADD_SIZE(add_rt.rt_mask); > > > > /* add their address family */ > > #define ADD_FAM(x) x.sin.sin_family = AF_INET; > > ADD_FAM(add_rt.rt_dst); > > ADD_FAM(add_rt.rt_gate); > > ADD_FAM(add_rt.rt_mask); > > ADD_FAM(add_rt.rt_genmask); > > > > /* set up all of the flags and tables */ > > #define RD add_rt.add_rtm > > RD.rtm_msglen = l; > > RD.rtm_version = RTM_VERSION; > > RD.rtm_type = RTM_ADD; > > RD.rtm_flags = flags; > > RD.rtm_addrs = rtm_addrs; > > RD.rtm_inits = RTF_GATEWAY; > > RD.rtm_pid = pid = getpid(); > > RD.rtm_seq = ++SEQ; > > > > if( (sockfd = socket(PF_ROUTE, SOCK_RAW, 0)) < 0){ > > ERR("set_droute: FREEBSD cannot open socket > > %d"); > > } > > /* send it to the kernel */ > > i = write(sockfd, (char *)&add_rt, l); > > syslog(LOG_ERR, "errno = %d ", errno); > > } > > else{ > > /* get a buffer for the data */ > > ERR("get_droute returned ok %d "); > > } > > > > return(GOOD); > > } > > > > > > Thank you > > > > nathan > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > Good point ! this is an older copy, but the size I have fixed that and it receives a size of 128,. Now the problem I think is that the sizeof the struct rt_msghdr is 92, now that would be followed by my 3 sockaddr_in structs which are 16 each so total is 140 ? now the size of 128 is the size that the actual route.c sends and the difference is that they make a struct with a rt_msghdr, and a char buf of 512 and then he formats that without the popen numbers and only writes the fist 128. Now what I need to know if that is the case then what exactly needs to follow the rt_msghdr the doc's that I have found say that it needs in order: sockaddr dst /* destination rt_msghdr == 92 + this == 108*/ sockaddr gtw /* gateway current 108 + 16 == 124*/ sockaddr ntmsl /* net mask current 124 + 16 == 140 ? */ so does it really need the first destination or is that implied when you send the netmask ? or is their a location that is inside the struct rt_msghdr that you need to fill-in besides the obvious ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 17:27: 3 2000 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (dustdevil.waterspout.com [208.13.60.151]) by builder.freebsd.org (Postfix) with ESMTP id 26D3B3FB0; Mon, 14 Feb 2000 17:24:15 -0800 (PST) Received: by dustdevil.waterspout.com (Postfix, from userid 1000) id 5EE364B; Mon, 14 Feb 2000 20:24:34 -0500 (EST) Date: Mon, 14 Feb 2000 20:24:34 -0500 From: "C. Stephen Gunn" To: Garrett Wollman Cc: "C. Stephen Gunn" , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs Message-ID: <20000214202434.A16731@dustdevil.waterspout.com> References: <200002031847.NAA62013@khavrinen.lcs.mit.edu> <20000214002142.A12511@dustdevil.waterspout.com> <200002141625.LAA65769@khavrinen.lcs.mit.edu> <20000214125527.A14822@dustdevil.waterspout.com> <200002141935.OAA66996@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200002141935.OAA66996@khavrinen.lcs.mit.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Feb 14, 2000 at 02:35:39PM -0500, Garrett Wollman wrote: > Um, no. The point of running the VLAN code is to usefully interpret > frames with VLAN tags on them. As the designer of the code in > question, I think I can say that with some certainty. I'm not trying to question the intent of the code in FreeBSD. I was commenting on the special case of tagged/non-tagged frames on the same wire at the same time, and how that case is currently handled. My observation is that a bridge forwards packets based on rules (or VLAN tags) at layer-2. I don't see a difference if this happens on a physical wire, or inside the kernel drivers/protocol stacks. I have several goals (related to VLANs and FreeBSD) and starting an argument is definitely not one of them. Its not my intent to question your expertise, either as the code's architect, or in general. I'm working towards solid features in FreeBSD that I can use to simplify my production network environment. > > I believe it appropriate to make the lower protocol layers on FreeBSD > > comply with the specification for a bridge. > > I do not, unless bridging is actually configured. I see an administrative advantage to having your configuration be similar on all bridges or hosts that understand tagged frames. That's the motivation for my comments. Its entirely possible that I've missed something incredibly important here. Do you have some technical or philosopical reason to deviate from the advise of the published standard? - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc. Email: csg@waterspout.com 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 14 18: 3:22 2000 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (dustdevil.waterspout.com [208.13.60.151]) by builder.freebsd.org (Postfix) with ESMTP id 855D13DB9; Mon, 14 Feb 2000 18:03:20 -0800 (PST) Received: by dustdevil.waterspout.com (Postfix, from userid 1000) id 755434B; Mon, 14 Feb 2000 21:03:40 -0500 (EST) Date: Mon, 14 Feb 2000 21:03:40 -0500 From: "C. Stephen Gunn" To: wollman@freebsd.org Cc: freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs Message-ID: <20000214210340.B16731@dustdevil.waterspout.com> References: <200002031847.NAA62013@khavrinen.lcs.mit.edu> <20000214002142.A12511@dustdevil.waterspout.com> <200002141625.LAA65769@khavrinen.lcs.mit.edu> <20000214125527.A14822@dustdevil.waterspout.com> <200002141935.OAA66996@khavrinen.lcs.mit.edu> <20000214202434.A16731@dustdevil.waterspout.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20000214202434.A16731@dustdevil.waterspout.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I see an administrative advantage to having your configuration be > similar on all bridges or hosts that understand tagged frames. > That's the motivation for my comments. I also, after re-reading your message several times, and talking it over with Matthew Dodd, realized that I'm somewhat confused on the configuration/default-port-vlan issue. I do know this: I hate Cisco & their documentation.... - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc. Email: csg@waterspout.com 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 15 2:34: 2 2000 Delivered-To: freebsd-net@freebsd.org Received: from valis.olywa.net (valis.olywa.net [216.173.192.2]) by builder.freebsd.org (Postfix) with ESMTP id C4A943FA1; Tue, 15 Feb 2000 02:30:50 -0800 (PST) Received: from [216.173.212.205] by valis.olywa.net (Post.Office MTA v3.5.3 release 223 ID# 0-56662U5000L500S0V35) with ESMTP id net; Tue, 15 Feb 2000 02:30:46 -0800 User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630) Date: Tue, 15 Feb 2000 02:31:08 -0800 Subject: Re: kern/16318: Fix for wrong interface when adding new routes From: William Carrel To: , , , Message-ID: 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 This patch is applicable for both FreeBSD-stable AND FreeBSD-current, as well as OpenBSD and NetBSD. It has no noticeable ill-effects on the machines of nearly a dozen FreeBSD users that have been testing the patch for me. Nor does it have ill effects on the OpenBSD and NetBSD machines I have access to. It fixes some brain-dead behavior of the kernel routing table on all these operating systems. It causes the routing table to check itself for the ifa to assign to new routes before asking the interfaces. There are occasions (such as Ethernet point to point links) where the interfaces' idea of where a packet should go could disagree with the routing tables user made static entries. This leads to some very bizarre behavior for things like the default gateway if they get their packets routed to the wrong interface. The patch is available here: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=16318 I just thought I'd post this around again to draw attention to my open PR with code included, and mention that I've had successful testing reports on -current. -- William Carrel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 15 8:22: 1 2000 Delivered-To: freebsd-net@freebsd.org Received: from cd.mbn.or.jp (cd.mbn.or.jp [202.217.0.53]) by builder.freebsd.org (Postfix) with ESMTP id A283F4EB5 for ; Tue, 15 Feb 2000 08:20:01 -0800 (PST) Received: from gateway (cse6-32.kokubunji.mbn.or.jp [210.144.135.194]) by cd.mbn.or.jp (8.9.1/cd.mbn.or.jp-2.0) with SMTP id BAA18035 for ; Wed, 16 Feb 2000 01:20:25 +0900 (JST) Message-ID: <001401bf77d0$5bba4460$064ca8c0@gateway> From: "Masahiro Ariga" To: Subject: Is semaphore workable during socket transfer Date: Wed, 16 Feb 2000 01:13:49 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My name is Masahiro Ariga. I have a trouble with Inter Process Comunication(specifically,semaphore). Would anyone help me ? Our system is Server-Client model.Server receives commands from Client, and sends data to Client. Server receives commands from Client in parent process,and data transfer is done in child process forked from parent process. Server uses socket functions,like socket(),select() etc. It was working fine. Then there occured the need to hand the received command over to child process from parent process. So I am determined to use semaphore for communication between parent and child process. I added "option SYSVSEM" line in config file and re-made the kernel and compiled program. When I run the program there occured the errors that were never happend before. Errors are, "select:Invalid argument." and little later "/kernel:pid 185(vs_lk),uid 0:exited on signal 1" vs_lk is program's name. And never transfer data. Isn't it possible to use semaphore while using socket or select functions? How should I avoid errors ? Please enlighten me. Masahiro Ariga mariga@cd.mbn.or.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 15 10:33: 5 2000 Delivered-To: freebsd-net@freebsd.org Received: from www.geocrawler.com (sourceforge.net [198.186.203.33]) by builder.freebsd.org (Postfix) with ESMTP id 464A549DB for ; Tue, 15 Feb 2000 10:31:46 -0800 (PST) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id KAA04192; Tue, 15 Feb 2000 10:32:14 -0800 Date: Tue, 15 Feb 2000 10:32:14 -0800 Message-Id: <200002151832.KAA04192@www.geocrawler.com> To: freebsd-net@freebsd.org Subject: portforwarding From: "Martijn de Munnik" Reply-To: "Martijn de Munnik" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message was sent from Geocrawler.com by "Martijn de Munnik" Be sure to reply to that address. I've been using linux with ipchains for this for a while but I want to switch to FreeBSD. We got a gateway to the internet with a privat network behind it everything is working fine but i'm not able to do portforwarding (or whatever it's called). I want to forward all incomming connections to 194.109.56.89 (172.16.70.1 on the inside) port 25 to 172.16.70.51 port 25 (this are just example ipnumbers)... So I did the following ipfw add allow tcp from 172.16.70.1 to 172.16.70.1 25 ipfw add fwd 172.16.70.51,25 from any to 194.109.56.89 but it doesn't seem to work BTW a rule that is later declared: ipfw add allow all from any to any Can anyone tell me what is wrong??? Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 15 13:51:12 2000 Delivered-To: freebsd-net@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 2BD665CF3; Tue, 15 Feb 2000 12:12:36 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id MAA04092; Tue, 15 Feb 2000 12:12:11 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id MAA14862; Tue, 15 Feb 2000 12:12:10 -0800 Received: from softweyr.com (dyn2.utah.xylan.com [198.206.184.238]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id MAA26470; Tue, 15 Feb 2000 12:12:08 -0800 (PST) Message-ID: <38A9B4A0.73A8105D@softweyr.com> Date: Tue, 15 Feb 2000 13:18:40 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "C. Stephen Gunn" Cc: wollman@freebsd.org, freebsd-net@freebsd.org Subject: Re: 802.1Q VLANs References: <200002031847.NAA62013@khavrinen.lcs.mit.edu> <20000214002142.A12511@dustdevil.waterspout.com> <200002141625.LAA65769@khavrinen.lcs.mit.edu> <20000214125527.A14822@dustdevil.waterspout.com> <200002141935.OAA66996@khavrinen.lcs.mit.edu> <20000214202434.A16731@dustdevil.waterspout.com> <20000214210340.B16731@dustdevil.waterspout.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "C. Stephen Gunn" wrote: > > > I see an administrative advantage to having your configuration be > > similar on all bridges or hosts that understand tagged frames. > > That's the motivation for my comments. > > I also, after re-reading your message several times, and talking > it over with Matthew Dodd, realized that I'm somewhat confused on > the configuration/default-port-vlan issue. > > I do know this: I hate Cisco & their documentation.... I have a book written here at Xylan that explains VLAN and switching topics at a high level quite nicely. I don't have any printed copies lying around, but I have the book in PDF format and can email it to you if you like. It's a 3.7 MB PDf file; I can split it if your mailer will choke on that me. Let me know if you want it. -- "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 15 14: 3:30 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-94.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.222]) by builder.freebsd.org (Postfix) with ESMTP id B62A34B90 for ; Tue, 15 Feb 2000 13:37:44 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA27797; Tue, 15 Feb 2000 21:18:17 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00412; Tue, 15 Feb 2000 08:14:21 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002150814.IAA00412@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Fisch, Eric" Cc: Brian Somers , freebsd-net@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: PPP Gateway Routing Problem In-Reply-To: Message from "Fisch, Eric" of "Mon, 14 Feb 2000 12:16:02 EST." <8389C74A65EFD111B03800805FA7658F06D71F6A@USDALEXC01> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Feb 2000 08:14:21 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Now my problem is that some service is preventing my ppp from timing out > properly. When the system boots, it connects to the ISP (I don't know why). > The ppp.conf file is set to timeout at 10 minutes, but it never does. I > have to pick up the phone receiver to disrupt traffic and force a > disconnect. Interestingly, it does NOT reconnect until I manually force an > out-bound packet (ftp, telent, ping, etc.), and when it does connect, it > stays connected until I pick up the receiver again. The hunt goes on... You need to enable tcp/ip logging to determine what's keeping the line up. I think ppp really needs to be able to dis-assemble DNS traffic.... Hmmm > Thanks for all your suggestions, > Eric -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 15 15:30:30 2000 Delivered-To: freebsd-net@freebsd.org Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14]) by builder.freebsd.org (Postfix) with ESMTP id 5A30C5909 for ; Tue, 15 Feb 2000 14:48:07 -0800 (PST) Received: from TIGGER (p3E9ECFA6.dip.t-dialin.net [62.158.207.166]) by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id OAA18718 for ; Tue, 15 Feb 2000 14:45:40 -0800 (PST) Message-Id: <4.2.0.58.20000215233615.02334c30@tim> X-Sender: dermot@tim X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 15 Feb 2000 23:48:39 +0100 To: freebsd-net@freebsd.org From: Dermot McNally Subject: NAT issues with ppp 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 Folks, No sooner am I up and running with PPPoE than I hit a snag. When running ppp in -nat mode, I get What I Expect when connecting over a conventional external ISDN TA, but not using PPPoE. Here's my configuration: ed0 is connected to the DSL "Modem", has no IP address, but the interface is brought up at boot time. Internet access over PPPoE works. xl0 is connected to my local network. The FreeBSD box is configured as a gateway, and works as an Internet gateway from all boxes on my local network when using ISDN. When connecting over PPPoE, here are the symptoms: Gateway box: Can use any Internet services, everything works. Internal boxes (Windows and FreeBSD/alpha): Can do DNS lookups, pings and traceroutes. Can send mail to an external SMTP server. Telnet works, but starting pine in a Telnet session makes the session freeze (not sure how this could be...). Seems to be able to do passive FTP, can't do active. Can't browse Web with Netscape, nor use fetch to grab the contents of a URL. The Gateway box, as mentioned, can do all of these things. My question - is there any reason why the NAT functionality of ppp should work differently when the connection is using PPPoE and not a serial port? There doesn't appear to be anything in my configuration that could cause this. FWIW, here are tcpdump outputs from tun0, for a "fetch http://www.freebsd.org/", both from the gateway box and from an internal FreeBSD/alpha box: Gateway: 23:31:32.971235 62.158.207.171.1162 > 204.216.27.21.http: S 4244921612:4244921612(0) win 17520 (DF) (ttl 64, id 28445) 23:31:33.345163 204.216.27.21.http > 62.158.207.171.1162: S 870726063:870726063(0) ack 4244921613 win 17400 (DF) (ttl 46, id 566) 23:31:33.345293 62.158.207.171.1162 > 204.216.27.21.http: FP 1:127(126) ack 1 win 17520 (DF) (ttl 64, id 28447) 23:31:33.676529 204.216.27.21.http > 62.158.207.171.1162: . 1:1(0) ack 128 win 17274 (DF) (ttl 46, id 588) 23:31:33.702500 204.216.27.21.http > 62.158.207.171.1162: . 1:1451(1450) ack 128 win 17400 (DF) (ttl 46, id 589) 23:31:33.702625 62.158.207.171.1162 > 204.216.27.21.http: . 128:128(0) ack 1451 win 16070 (DF) (ttl 64, id 28467) 23:31:33.718568 204.216.27.21.http > 62.158.207.171.1162: . 1451:2901(1450) ack 128 win 17400 (DF) (ttl 46, id 590) 23:31:33.718659 62.158.207.171.1162 > 204.216.27.21.http: R 4244921740:4244921740(0) win 0 (ttl 64, id 28473) 23:31:34.063055 204.216.27.21.http > 62.158.207.171.1162: R 870727514:870727514(0) win 0 (ttl 46, id 607) Internal: 23:32:19.257112 192.168.0.1.1040 > 204.216.27.21.http: S 2290649560:2290649560(0) win 16384 (DF) (ttl 63, id 11973) 23:32:19.550951 204.216.27.21.http > 192.168.0.1.1040: S 887263498:887263498(0) ack 2290649561 win 17520 (DF) (ttl 46, id 5591) 23:32:19.551425 192.168.0.1.1040 > 204.216.27.21.http: FP 1:128(127) ack 1 win 17520 (DF) (ttl 63, id 11974) 23:32:19.846814 204.216.27.21.http > 192.168.0.1.1040: . 1:1(0) ack 129 win 17393 (DF) (ttl 46, id 5606) Any ideas? Thanks, Dermot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 15 18:24:46 2000 Delivered-To: freebsd-net@freebsd.org Received: from ns1.via-net-works.net.ar (ns1.via-net-works.net.ar [200.10.100.10]) by builder.freebsd.org (Postfix) with ESMTP id 12BCF40C9 for ; Tue, 15 Feb 2000 18:15:02 -0800 (PST) Received: (from fpscha@localhost) by ns1.via-net-works.net.ar (8.9.3/8.9.3) id XAA12580 for net@freebsd.org; Tue, 15 Feb 2000 23:11:09 -0300 (GMT) From: Fernando Schapachnik Message-Id: <200002160211.XAA12580@ns1.via-net-works.net.ar> Subject: Routing question To: net@freebsd.org Date: Tue, 15 Feb 2000 23:11:09 -0300 (GMT) Reply-To: Fernando Schapachnik X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello: I want to use a FreeBSD box as a router and I need to have static routes that become inactive (or dissapear) when the interface they point to goes down, but come to life again when the interface goes up (kind of what CISCO does). Is there a way to acomplish this without some nasty script monitoring the interface? Thanks and regards, Fernando P. Schapachnik Administración de la red VIA NET.WORKS ARGENTINA S.A. fernando@via-net-works.net.ar (54-11) 4323-3333 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 16 0:58:56 2000 Delivered-To: freebsd-net@freebsd.org Received: from digital.its-sby.edu (digital.its-sby.edu [202.154.63.10]) by builder.freebsd.org (Postfix) with ESMTP id 6069C43E7 for ; Wed, 16 Feb 2000 00:58:45 -0800 (PST) Received: from ns2.its-sby.edu (ns2.its-sby.edu [202.154.63.3]) by digital.its-sby.edu (8.9.3/8.9.3) with ESMTP id QAA02073 for ; Wed, 16 Feb 2000 16:02:52 +0700 (JAVT) (envelope-from roy@ns2.its-sby.edu) Received: from localhost (roy@localhost) by ns2.its-sby.edu (8.9.3/8.9.3) with ESMTP id QAA13223 for ; Wed, 16 Feb 2000 16:18:45 +0700 (JAVT) (envelope-from roy@ns2.its-sby.edu) Date: Wed, 16 Feb 2000 16:18:45 +0700 (JAVT) From: "Royyana M. Ijtihadie" To: net@freebsd.org Subject: fxp0 : device timeout 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 dear netter.. i sometime get a message like this /kernel : fxp0 : device timeout what's the meaning of this ? how to resolve this problem.. thanks alot.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 16 1: 0: 0 2000 Delivered-To: freebsd-net@freebsd.org Received: from digital.its-sby.edu (digital.its-sby.edu [202.154.63.10]) by builder.freebsd.org (Postfix) with ESMTP id B1DE240C5 for ; Wed, 16 Feb 2000 00:59:54 -0800 (PST) Received: from ns2.its-sby.edu (ns2.its-sby.edu [202.154.63.3]) by digital.its-sby.edu (8.9.3/8.9.3) with ESMTP id QAA02082 for ; Wed, 16 Feb 2000 16:03:54 +0700 (JAVT) (envelope-from roy@ns2.its-sby.edu) Received: from localhost (roy@localhost) by ns2.its-sby.edu (8.9.3/8.9.3) with ESMTP id QAA13238 for ; Wed, 16 Feb 2000 16:20:01 +0700 (JAVT) (envelope-from roy@ns2.its-sby.edu) Date: Wed, 16 Feb 2000 16:20:01 +0700 (JAVT) From: "Royyana M. Ijtihadie" To: freebsd-net@freebsd.org Subject: fxp0 : device timeout (fwd) 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 dear netter.. i sometime get a message like this /kernel : fxp0 : device timeout what's the meaning of this ? how to resolve this problem.. thanks alot.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 16 3:28: 7 2000 Delivered-To: freebsd-net@freebsd.org Received: from mta04.onebox.com (mta04.onebox.com [216.33.158.211]) by builder.freebsd.org (Postfix) with ESMTP id 4042C43FF for ; Wed, 16 Feb 2000 03:28:05 -0800 (PST) Received: from onebox.com ([216.33.158.154]) by mta04.onebox.com (InterMail vM.4.01.02.17 201-229-119) with SMTP id <20000216112837.SEWN28348.mta04.onebox.com@onebox.com> for ; Wed, 16 Feb 2000 03:28:37 -0800 From: "Chutima S." To: freebsd-net@FreeBSD.ORG Subject: Is there proxy for SMTP and POP3. Date: Wed, 16 Feb 2000 11:28:37 GMT Message-Id: <20000216112837.SEWN28348.mta04.onebox.com@onebox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear all, I'm setting proxy-machine for my Private-Network. There is Mail server (SMTP and POP) outside(Internet Network). I'm looking for proxy for SMTP and POP3 for use with FreeBSD-3.4. Where should I look for it? Thanks, -- Chutima Subsirin chutima_s@zdnetonebox.com - email ___________________________________________________________________ To get your own FREE ZDNet onebox - FREE voicemail, email, and fax, all in one place - sign up today at http://www.zdnetonebox.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 16 3:34:58 2000 Delivered-To: freebsd-net@freebsd.org Received: from pr.infosec.ru (pr.infosec.ru [194.135.141.98]) by builder.freebsd.org (Postfix) with ESMTP id 9C22B444C for ; Wed, 16 Feb 2000 03:34:55 -0800 (PST) Received: from blaze (200.0.0.51 [200.0.0.51]) by pr.infosec.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id D5XL43PZ; Wed, 16 Feb 2000 14:35:24 +0300 Date: Wed, 16 Feb 2000 14:35:45 +0300 (MSK) From: Andrey Sverdlichenko X-Sender: blaze@blaze To: freebsd-net@FreeBSD.ORG Subject: Re: Is there proxy for SMTP and POP3. In-Reply-To: <20000216112837.SEWN28348.mta04.onebox.com@onebox.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 Wed, 16 Feb 2000, Chutima S. wrote: > I'm setting proxy-machine for my Private-Network. There is Mail > server (SMTP and POP) outside(Internet Network). > I'm looking for proxy for SMTP and POP3 for use with FreeBSD-3.4. > > Where should I look for it? /usr/ports/security/fwtk -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d- s+:- a-- C++ UB++$ P+ L+ E- W+ N++ o? K? w-- O- M- V? PS+ PE+ Y+ PGP+ t 5+ X R tv b++(+++) DI? D++ G e++ h! r- y ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 16 9:12:29 2000 Delivered-To: freebsd-net@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 13F4C37B50D for ; Wed, 16 Feb 2000 09:12:28 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by builder.freebsd.org (Postfix) with ESMTP id 25C5B132D6 for ; Wed, 16 Feb 2000 09:11:51 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA76472; Wed, 16 Feb 2000 12:12:02 -0500 (EST) (envelope-from wollman) Date: Wed, 16 Feb 2000 12:12:02 -0500 (EST) From: Garrett Wollman Message-Id: <200002161712.MAA76472@khavrinen.lcs.mit.edu> To: Wes Peters Cc: freebsd-net@freebsd.org Subject: Re: 802.1Q VLANs In-Reply-To: <38A9B4A0.73A8105D@softweyr.com> References: <200002031847.NAA62013@khavrinen.lcs.mit.edu> <20000214002142.A12511@dustdevil.waterspout.com> <200002141625.LAA65769@khavrinen.lcs.mit.edu> <20000214125527.A14822@dustdevil.waterspout.com> <200002141935.OAA66996@khavrinen.lcs.mit.edu> <20000214202434.A16731@dustdevil.waterspout.com> <20000214210340.B16731@dustdevil.waterspout.com> <38A9B4A0.73A8105D@softweyr.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > I have a book written here at Xylan that explains VLAN and switching > topics at a high level quite nicely. The trouble is that every vendor means something different by `VLAN'. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 16 11:38:33 2000 Delivered-To: freebsd-net@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id E22E837B5C6 for ; Wed, 16 Feb 2000 11:38:31 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by builder.freebsd.org (Postfix) with ESMTP id D6D92132E0 for ; Wed, 16 Feb 2000 11:37:46 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA78246; Wed, 16 Feb 2000 14:38:19 -0500 (EST) (envelope-from wollman) Date: Wed, 16 Feb 2000 14:38:19 -0500 (EST) From: Garrett Wollman Message-Id: <200002161938.OAA78246@khavrinen.lcs.mit.edu> To: net@freebsd.org Subject: Synchronizing two (or more) machines over the network Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone have a good method for keeping two machines absolutely identical-but-for-a-few-symlinks that works reliably and securely over the network? I have looked at rdist6, but it doesn't understand file flags. (NFS is out of the running, since it is neither reliable nor secure.) Are there any other options that people have found to their liking? -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 16 13: 3:58 2000 Delivered-To: freebsd-net@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 46A6337B5C0 for ; Wed, 16 Feb 2000 13:03:57 -0800 (PST) (envelope-from vova@express.ru) Received: from lanturn.express.ru (lanturn.kmost.express.ru [212.24.37.109]) by builder.freebsd.org (Postfix) with ESMTP id 03E01132E8 for ; Wed, 16 Feb 2000 13:03:18 -0800 (PST) Received: from vova (helo=localhost) by lanturn.express.ru with local-esmtp (Exim 3.11 #1) id 12LBcQ-000MYD-00; Thu, 17 Feb 2000 00:04:18 +0300 Date: Thu, 17 Feb 2000 00:04:18 +0300 (MSK) From: "Vladimir B. Grebenschikov" X-Sender: vova@lanturn.kmost.express.ru To: Garrett Wollman Cc: net@freebsd.org Subject: Re: Synchronizing two (or more) machines over the network In-Reply-To: <200002161938.OAA78246@khavrinen.lcs.mit.edu> 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, 16 Feb 2000, Garrett Wollman wrote: > Does anyone have a good method for keeping two machines absolutely > identical-but-for-a-few-symlinks that works reliably and securely over > the network? I have looked at rdist6, but it doesn't understand file > flags. (NFS is out of the running, since it is neither reliable nor > secure.) Are there any other options that people have found to their > liking? Do you look at coda FS ? > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 16 17:30:18 2000 Delivered-To: freebsd-net@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 27E1737B5C5 for ; Wed, 16 Feb 2000 17:30:15 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from awfulhak.org (dynamic-26.max2-du-ws.dialnetwork.pavilion.co.uk [212.74.8.154]) by builder.freebsd.org (Postfix) with ESMTP id C72D3132DE for ; Wed, 16 Feb 2000 17:29:31 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA31137; Thu, 17 Feb 2000 01:26:42 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA01707; Thu, 17 Feb 2000 00:51:49 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002170051.AAA01707@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dermot McNally Cc: freebsd-net@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: NAT issues with ppp In-Reply-To: Message from Dermot McNally of "Tue, 15 Feb 2000 23:48:39 +0100." <4.2.0.58.20000215233615.02334c30@tim> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Feb 2000 00:51:49 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does this happen with the latest version from my web site ? There was a problem with NAT translations not adjusting the packet length a short while ago, resulting in bad breakage everytime the size of the IP number in things such as the PORT command was adjusted. If it still happens with the latest verison, can you also try decreasing your network MTU to 1492 (or maybe even 1400 for kicks). This would stop IP fragmentation - it shouldn't make a difference, but, well.... > Folks, > > No sooner am I up and running with PPPoE than I hit a snag. When running > ppp in -nat mode, I get What I Expect when connecting over a conventional > external ISDN TA, but not using PPPoE. Here's my configuration: > > ed0 is connected to the DSL "Modem", has no IP address, but the interface > is brought up at boot time. Internet access over PPPoE works. > > xl0 is connected to my local network. The FreeBSD box is configured as a > gateway, and works as an Internet gateway from all boxes on my local > network when using ISDN. When connecting over PPPoE, here are the symptoms: > > Gateway box: Can use any Internet services, everything works. > > Internal boxes (Windows and FreeBSD/alpha): Can do DNS lookups, pings and > traceroutes. Can send mail to an external SMTP server. Telnet works, but > starting pine in a Telnet session makes the session freeze (not sure how > this could be...). Seems to be able to do passive FTP, can't do active. > Can't browse Web with Netscape, nor use fetch to grab the contents of a > URL. The Gateway box, as mentioned, can do all of these things. > > My question - is there any reason why the NAT functionality of ppp should > work differently when the connection is using PPPoE and not a serial port? > There doesn't appear to be anything in my configuration that could cause > this. FWIW, here are tcpdump outputs from tun0, for a "fetch > http://www.freebsd.org/", both from the gateway box and from an internal > FreeBSD/alpha box: > > Gateway: > > 23:31:32.971235 62.158.207.171.1162 > 204.216.27.21.http: S > 4244921612:4244921612(0) win 17520 (DF) (ttl 64, id 28445) > 23:31:33.345163 204.216.27.21.http > 62.158.207.171.1162: S > 870726063:870726063(0) ack 4244921613 win 17400 (DF) (ttl 46, id > 566) > 23:31:33.345293 62.158.207.171.1162 > 204.216.27.21.http: FP 1:127(126) ack > 1 win 17520 (DF) (ttl 64, id 28447) > 23:31:33.676529 204.216.27.21.http > 62.158.207.171.1162: . 1:1(0) ack 128 > win 17274 (DF) (ttl 46, id 588) > 23:31:33.702500 204.216.27.21.http > 62.158.207.171.1162: . 1:1451(1450) > ack 128 win 17400 (DF) (ttl 46, id 589) > 23:31:33.702625 62.158.207.171.1162 > 204.216.27.21.http: . 128:128(0) ack > 1451 win 16070 (DF) (ttl 64, id 28467) > 23:31:33.718568 204.216.27.21.http > 62.158.207.171.1162: . 1451:2901(1450) > ack 128 win 17400 (DF) (ttl 46, id 590) > 23:31:33.718659 62.158.207.171.1162 > 204.216.27.21.http: R > 4244921740:4244921740(0) win 0 (ttl 64, id 28473) > 23:31:34.063055 204.216.27.21.http > 62.158.207.171.1162: R > 870727514:870727514(0) win 0 (ttl 46, id 607) > > Internal: > > 23:32:19.257112 192.168.0.1.1040 > 204.216.27.21.http: S > 2290649560:2290649560(0) win 16384 (DF) (ttl 63, id 11973) > 23:32:19.550951 204.216.27.21.http > 192.168.0.1.1040: S > 887263498:887263498(0) ack 2290649561 win 17520 (DF) (ttl 46, id > 5591) > 23:32:19.551425 192.168.0.1.1040 > 204.216.27.21.http: FP 1:128(127) ack 1 > win 17520 (DF) (ttl 63, id 11974) > 23:32:19.846814 204.216.27.21.http > 192.168.0.1.1040: . 1:1(0) ack 129 win > 17393 (DF) (ttl 46, id 5606) > > Any ideas? > > Thanks, > Dermot -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 16 17:44:19 2000 Delivered-To: freebsd-net@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id E358337B922 for ; Wed, 16 Feb 2000 17:44:16 -0800 (PST) (envelope-from wes@softweyr.com) Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 655EC132E4 for ; Wed, 16 Feb 2000 17:43:28 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id RAA26245; Wed, 16 Feb 2000 17:43:30 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id RAA02489; Wed, 16 Feb 2000 17:43:30 -0800 Received: from softweyr.com (dyn2.utah.xylan.com [198.206.184.238]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id RAA18054; Wed, 16 Feb 2000 17:43:26 -0800 (PST) Message-ID: <38AB53C9.B5BCF78F@softweyr.com> Date: Wed, 16 Feb 2000 18:50:01 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Garrett Wollman Cc: freebsd-net@freebsd.org Subject: Re: 802.1Q VLANs References: <200002031847.NAA62013@khavrinen.lcs.mit.edu> <20000214002142.A12511@dustdevil.waterspout.com> <200002141625.LAA65769@khavrinen.lcs.mit.edu> <20000214125527.A14822@dustdevil.waterspout.com> <200002141935.OAA66996@khavrinen.lcs.mit.edu> <20000214202434.A16731@dustdevil.waterspout.com> <20000214210340.B16731@dustdevil.waterspout.com> <38A9B4A0.73A8105D@softweyr.com> <200002161712.MAA76472@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 Garrett Wollman wrote: > > < said: > > > I have a book written here at Xylan that explains VLAN and switching > > topics at a high level quite nicely. > > The trouble is that every vendor means something different by `VLAN'. But at least one of them took the time to explain what they mean. ;^) -- "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 Wed Feb 16 18:45:36 2000 Delivered-To: freebsd-net@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id EDA3B37B5E4 for ; Wed, 16 Feb 2000 18:45:33 -0800 (PST) (envelope-from csg@waterspout.com) Received: from dustdevil.waterspout.com (dustdevil.waterspout.com [208.13.60.151]) by builder.freebsd.org (Postfix) with ESMTP id 75359132ED for ; Wed, 16 Feb 2000 18:44:54 -0800 (PST) Received: by dustdevil.waterspout.com (Postfix, from userid 1000) id 42D5A9D; Wed, 16 Feb 2000 21:45:32 -0500 (EST) Date: Wed, 16 Feb 2000 21:45:32 -0500 From: "C. Stephen Gunn" To: Wes Peters Cc: freebsd-net@freebsd.org Subject: Re: L2tp thoughts an implementations. Message-ID: <20000216214532.B25547@dustdevil.waterspout.com> References: <38A31B2F.434FBA74@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <38A31B2F.434FBA74@softweyr.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > FWIW, I'd like to see a solid implementation of 802.1q, too. Including the > important but always overlooked stuff like per-VLAN arp tables, in case you > have a Sun sitting on two VLANs using the same MAC address on both, and > per-VLAN routing tables so you can have different VLANs with their own > unique internet connections. Just FYI - Just like Suns, FreeBSD boxen running our current VLAN implementation will appear on all VLANs with the MAC address of the parent ethernet device. I've not noticed any problems with the ARP code, aside from my switch forwarding an occasional stray untagged packet to the parent device. I get a printf() about someone using my IP address (0.0.0.0). I'm a little confused on you comment about per-VLAN routing tables. VLANs operate at layer-2, and routing is a layer 3 decision, right? Can you please explain where this knowledge would be important? - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc. Email: csg@waterspout.com 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 16 19: 3:15 2000 Delivered-To: freebsd-net@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 3663C37B638 for ; Wed, 16 Feb 2000 19:03:13 -0800 (PST) (envelope-from csg@waterspout.com) Received: from dustdevil.waterspout.com (dustdevil.waterspout.com [208.13.60.151]) by builder.freebsd.org (Postfix) with ESMTP id 9D7BA132E3 for ; Wed, 16 Feb 2000 19:02:33 -0800 (PST) Received: by dustdevil.waterspout.com (Postfix, from userid 1000) id 674BF9D; Wed, 16 Feb 2000 22:03:17 -0500 (EST) Date: Wed, 16 Feb 2000 22:03:17 -0500 From: "C. Stephen Gunn" To: Garrett Wollman Cc: freebsd-net@freebsd.org Subject: Re: Synchronizing two (or more) machines over the network Message-ID: <20000216220317.C25547@dustdevil.waterspout.com> References: <200002161938.OAA78246@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200002161938.OAA78246@khavrinen.lcs.mit.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Feb 16, 2000 at 02:38:19PM -0500, Garrett Wollman wrote: > Does anyone have a good method for keeping two machines absolutely > identical-but-for-a-few-symlinks that works reliably and securely over > the network? I have looked at rdist6, but it doesn't understand file > flags. (NFS is out of the running, since it is neither reliable nor > secure.) Are there any other options that people have found to their > liking? I've been whining for quite some time that rdist should use /usr/bin/install to do its dirty work. This would fix flags flags, owner, group, and other "lacking" remote install options of note in rdist. Rdist shouldn't know how to "install" files when install(1) already knows how to do it better. At the very least it should be abstracted into a library that install and other programs can use. We use rdist extensively at Purdue to do software distributions, and flags/owner/group support have been aggrivating me for quite some time now. Perhaps I'll fix it. - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc. Email: csg@waterspout.com 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 17 0:11:53 2000 Delivered-To: freebsd-net@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id BF6DC37B672 for ; Thu, 17 Feb 2000 00:11:51 -0800 (PST) (envelope-from dermo@mcnally.de) Received: from shell20.ba.best.com (shell20.ba.best.com [206.184.139.152]) by builder.freebsd.org (Postfix) with ESMTP id 37EED132F9 for ; Thu, 17 Feb 2000 00:11:10 -0800 (PST) Received: from localhost (dermo@localhost) by shell20.ba.best.com (8.9.3/8.9.2/best.sh) with ESMTP id AAA26427; Thu, 17 Feb 2000 00:11:43 -0800 (PST) X-Authentication-Warning: shell20.ba.best.com: dermo owned process doing -bs Date: Thu, 17 Feb 2000 00:11:43 -0800 (PST) From: Dermot McNally X-Sender: dermo@shell20.ba.best.com To: Brian Somers Cc: Dermot McNally , freebsd-net@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: NAT issues with ppp In-Reply-To: <200002170051.AAA01707@hak.lan.Awfulhak.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, 17 Feb 2000, Brian Somers wrote: > Does this happen with the latest version from my web site ? There Good question - it certainly happens with -current of a day or so ago. If what's on your site is newer, I'll certainly give it a try. > was a problem with NAT translations not adjusting the packet length a > short while ago, resulting in bad breakage everytime the size of the > IP number in things such as the PORT command was adjusted. > > If it still happens with the latest verison, can you also try > decreasing your network MTU to 1492 (or maybe even 1400 for kicks). I'm currently using 1490. If nothing else helps, I'll try 1400. > This would stop IP fragmentation - it shouldn't make a difference, > but, well.... I know, when you eliminate the merely improbably, you have to investigate the impossible too... Thanks, Dermot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 17 1:41: 1 2000 Delivered-To: freebsd-net@freebsd.org Received: from shell20.ba.best.com (shell20.ba.best.com [206.184.139.152]) by hub.freebsd.org (Postfix) with ESMTP id 71B4D37B696 for ; Thu, 17 Feb 2000 01:40:59 -0800 (PST) (envelope-from dermo@mcnally.de) Received: from localhost (dermo@localhost) by shell20.ba.best.com (8.9.3/8.9.2/best.sh) with ESMTP id BAA08092; Thu, 17 Feb 2000 01:40:52 -0800 (PST) X-Authentication-Warning: shell20.ba.best.com: dermo owned process doing -bs Date: Thu, 17 Feb 2000 01:40:52 -0800 (PST) From: Dermot McNally X-Sender: dermo@shell20.ba.best.com To: Brian Somers Cc: Dermot McNally , freebsd-net@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: NAT issues with ppp In-Reply-To: <200002170051.AAA01707@hak.lan.Awfulhak.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, 17 Feb 2000, Brian Somers wrote: > If it still happens with the latest verison, can you also try > decreasing your network MTU to 1492 (or maybe even 1400 for kicks). > This would stop IP fragmentation - it shouldn't make a difference, > but, well.... I've just realised that you're talking about my inside MTU - I haven't even touched that yet. I'll try it. Cheers, Dermot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 17 6:58:59 2000 Delivered-To: freebsd-net@freebsd.org Received: from vidle.i.cz (vidle.i.cz [193.179.36.138]) by hub.freebsd.org (Postfix) with ESMTP id 115EF37B734 for ; Thu, 17 Feb 2000 06:58:57 -0800 (PST) (envelope-from mm@i.cz) Received: from ns.i.cz (brana.i.cz [193.179.36.134]) by vidle.i.cz (Postfix) with ESMTP id 0DB5A30701 for ; Thu, 17 Feb 2000 15:58:56 +0100 (CET) Received: from woody.i.cz (woody.i.cz [192.168.18.29]) by ns.i.cz (Postfix) with ESMTP id CC38036415 for ; Thu, 17 Feb 2000 15:58:54 +0100 (CET) Content-Length: 882 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200002161938.OAA78246@khavrinen.lcs.mit.edu> Date: Thu, 17 Feb 2000 15:58:54 +0100 (MET) Reply-To: mm@i.cz From: Martin Machacek To: net@freebsd.org Subject: RE: Synchronizing two (or more) machines over the network Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 16-Feb-00 Garrett Wollman wrote: > Does anyone have a good method for keeping two machines absolutely > identical-but-for-a-few-symlinks that works reliably and securely over > the network? I have looked at rdist6, but it doesn't understand file > flags. (NFS is out of the running, since it is neither reliable nor > secure.) Are there any other options that people have found to their > liking? I'm using rsync over ssh together with mtree. I first build completely image of target filesystem on the master machine (incorporating all target machine specific modifications) then rsync it to the target and finally run mtree to fix ownership and permissions. The whole process is driven by relatively primitive shell script. Works fine for a network of cca. 40 nameservers, mailservers and firewalls running FreeBSD 2.2.8 and 3.3. Martin --- [PGP KeyID F3F409C4] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 17 7:17:35 2000 Delivered-To: freebsd-net@freebsd.org Received: from hydrant.intranova.net (hydrant.intranova.net [209.201.95.10]) by hub.freebsd.org (Postfix) with SMTP id 2B4F837B6BD for ; Thu, 17 Feb 2000 07:17:31 -0800 (PST) (envelope-from oogali@intranova.net) Received: (qmail 91888 invoked from network); 17 Feb 2000 15:16:24 -0000 Received: from localhost (oogali@127.0.0.1) by hydrant.intranova.net with SMTP; 17 Feb 2000 15:16:24 -0000 Date: Thu, 17 Feb 2000 10:16:23 -0500 (EST) From: Omachonu Ogali To: Martijn de Munnik Cc: freebsd-net@freebsd.org Subject: Re: portforwarding In-Reply-To: <200002151832.KAA04192@www.geocrawler.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 ipfw add fwd 172.16.70.51,25 tcp from any to 194.109.56.89 25 If that doesn't work check to see if you enabled IPFIREWALL_FORWARD in the kernel. On Tue, 15 Feb 2000, Martijn de Munnik wrote: > This message was sent from Geocrawler.com by "Martijn de Munnik" > Be sure to reply to that address. > > I've been using linux with ipchains for this for > a while but I want to switch to FreeBSD. We got a > gateway to the internet with a privat network > behind it everything is working fine but i'm not > able to do portforwarding (or whatever it's > called). I want to forward all incomming > connections to 194.109.56.89 (172.16.70.1 on the > inside) port 25 to 172.16.70.51 port 25 (this are > just example ipnumbers)... > So I did the following > > ipfw add allow tcp from 172.16.70.1 to > 172.16.70.1 25 > ipfw add fwd 172.16.70.51,25 from any to > 194.109.56.89 > > but it doesn't seem to work > BTW > a rule that is later declared: > ipfw add allow all from any to any > > Can anyone tell me what is wrong??? > > Geocrawler.com - The Knowledge Archive > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 17 7:58:26 2000 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 A99CD37B78A for ; Thu, 17 Feb 2000 07:58:22 -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 KAA82324; Thu, 17 Feb 2000 10:58:06 -0500 (EST) (envelope-from wollman) Date: Thu, 17 Feb 2000 10:58:06 -0500 (EST) From: Garrett Wollman Message-Id: <200002171558.KAA82324@khavrinen.lcs.mit.edu> To: "C. Stephen Gunn" Cc: Wes Peters , freebsd-net@FreeBSD.ORG Subject: Re: L2tp thoughts an implementations. In-Reply-To: <20000216214532.B25547@dustdevil.waterspout.com> References: <38A31B2F.434FBA74@softweyr.com> <20000216214532.B25547@dustdevil.waterspout.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Just FYI - Just like Suns, FreeBSD boxen running our current VLAN > implementation will appear on all VLANs with the MAC address of > the parent ethernet device. As they should, and as does every other piece of VLAN-capable hardware I've ever seen (including routers from Cisco, Extreme, Cabletron, Nortel, and probably others). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 17 14:11:28 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.nerv.nu (cx639627-c.irvn1.occa.home.com [24.0.209.134]) by hub.freebsd.org (Postfix) with ESMTP id 1E61C37B84D for ; Thu, 17 Feb 2000 14:11:23 -0800 (PST) (envelope-from nugundam@nerv.nu) Received: (from nugundam@localhost) by greenwood3.nerv.nu (8.9.3/8.9.3) id OAA27081; Sun, 13 Feb 2000 14:31:09 -0800 (PST) (envelope-from nugundam) Date: Sun, 13 Feb 2000 14:31:09 -0800 From: "Joseph T. Lee" To: Marco Rodrigues Cc: freebsd-net@FreeBSD.ORG Subject: Re: natd redirect_port Message-ID: <20000213143109.A27031@greenwood3.nerv.nu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Marco Rodrigues on Sun, Feb 13, 2000 at 03:39:56PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Feb 13, 2000 at 03:39:56PM -0500, Marco Rodrigues wrote: > Has anyone ever got the redirect_port switch to work with natd? It seems > i've tried everything and I can't never get it to work. -redirect_port tcp > externalip:telnet internalip:telnet should pass all requests to port 23 on > the computer with both nics to a internal box at port 23 correct? I've also From the manpage: -redirect_port proto targetIP:targetPORT[-targetPORT] [aliasIP:]alias- PORT[-aliasPORT] [remoteIP[:remotePORT[-remotePORT]]] [snip] tcp inside1:telnet 6666 means that incoming tcp packets destined for port 6666 on this machine will be sent to the telnet port on the inside1 machine. tcp inside2:2300-2399 3300-3399 will redirect incoming connections on ports 3300-3399 to host inside2, ports 2300-2399. The mapping is 1:1 meaning port 3300 maps to 2300, 3301 maps to 2301, etc. You have it reversed. Try -redirect_port tcp internal:telnet telnet. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 2000 >> www.anime-expo.org/ > # FreeBSD: The Power to Serve >> www.freebsd.org > # The Ultimate Online Speed-Shop >> www.racesearch.com / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 17 19:51:21 2000 Delivered-To: freebsd-net@freebsd.org Received: from mrout2.yahoo.com (mrout2.yahoo.com [208.48.125.152]) by hub.freebsd.org (Postfix) with ESMTP id 6D99437B598 for ; Thu, 17 Feb 2000 19:51:13 -0800 (PST) (envelope-from jayanth@yahoo-inc.com) Received: from yahoo-inc.com (milk.yahoo.com [206.251.16.37]) by mrout2.yahoo.com (8.10.0.Beta6/8.10.0.Beta6/y.out) with ESMTP id e1I3owK58204 for ; Thu, 17 Feb 2000 19:50:58 -0800 (PST) Message-ID: <38ACC1A2.A830B26C@yahoo-inc.com> Date: Thu, 17 Feb 2000 19:50:58 -0800 From: jayanth X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 To: fbsdnet Subject: tcpsendspace and tcprecvspace issue ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There seems to be a certain condition where tcp advertises the wrong window size when the tcpsendspace and tcprecvspace value are set to a value = 65536(>65000 ) Assume rfc1323 is off. Scenario: Turn keepalive on and open a connection. Send some data and let the connection be idle. let the keepalive timer expire at the server end. tcp now advertises a window size of 164 instead of the original window size. I went through the code and found that in tcp_input.c in tcp_mss() the following code bumps the value from 65536 to 65700 tcp_mss() --------- #ifdef RTV_RPIPE if ((bufsize = rt->rt_rmx.rmx_recvpipe) == 0) #endif bufsize = so->so_rcv.sb_hiwat; if (bufsize > mss) { bufsize = roundup(bufsize, mss); ^^^^^^^^^^^^^^^^^^^^^^^^^^^ if (bufsize > sb_max) bufsize = sb_max; (void)sbreserve(&so->so_rcv, bufsize); If the keepalive timer expires the tcp_respond() uses the sbspace(so->so_rcv) to determine the window size. tcp_respond() ------------ ti->ti_win = htons((u_short) (win >> tp->rcv_scale)); else ti->ti_win = htons((u_short)win); ti->ti_win is cast to a unsigned short resulting in the wrap around 65700 - 65336 = 164 which is the advertised window size.. The problem occurs if the roundup result is greater than 65536. Is this a bug ? The fix is either not do a roundup() if rfc1323 is off or not to allow this value to exceed 65535 if rfc1323 is off. Hope I am making sense. cheers jayanth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 18 8:13:46 2000 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 1E07737B9AF for ; Fri, 18 Feb 2000 08:13:44 -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 LAA86410; Fri, 18 Feb 2000 11:13:32 -0500 (EST) (envelope-from wollman) Date: Fri, 18 Feb 2000 11:13:32 -0500 (EST) From: Garrett Wollman Message-Id: <200002181613.LAA86410@khavrinen.lcs.mit.edu> To: jayanth Cc: fbsdnet Subject: tcpsendspace and tcprecvspace issue ? In-Reply-To: <38ACC1A2.A830B26C@yahoo-inc.com> References: <38ACC1A2.A830B26C@yahoo-inc.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > The fix is either not do a roundup() if rfc1323 is off > or not to allow this value to exceed 65535 if rfc1323 is off. I believe the latter is a correct fix. If window scaling is disabled, then the maximum permissible TCP window size is 65535 octets. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 18 8:52: 6 2000 Delivered-To: freebsd-net@freebsd.org Received: from zirafe.carrier.kiev.ua (sivka.carrier.kiev.ua [193.193.193.101]) by hub.freebsd.org (Postfix) with ESMTP id ACBC837B9D7 for ; Fri, 18 Feb 2000 08:51:59 -0800 (PST) (envelope-from samj@itcj.kiev.ua) Received: from mails.itci.kiev.ua (gw1.itci.kiev.ua [62.244.54.196]) by zirafe.carrier.kiev.ua (8.Who.Cares/Kilkenny_is_better) with ESMTP id STY55188 for ; Fri, 18 Feb 2000 18:51:49 +0200 (EET) (envelope-from samj@itcj.kiev.ua) Received: from primsrv (primsrv.itci.kiev.ua [62.244.54.220]) by mails.itci.kiev.ua (8.8.8/8.8.8) with ESMTP id SAA12935 for ; Fri, 18 Feb 2000 18:51:06 +0200 (EET) (envelope-from samj@itcj.kiev.ua) Message-Id: <200002181651.SAA12935@mails.itci.kiev.ua> From: "Yuriy" To: Subject: mgetty is fixing the name cuaa wrong Date: Fri, 18 Feb 2000 18:51:45 +0200 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am multiport kard with 8 coms. I'm configured PPP on cuaa1, cuaa2, cuaa4 ... cuaaa, cuaab. All of them had worked fine. But one day I'd seen mgetty is fixed cuaaa and cuaab as cuaa10 and cuaa11. What's happen ? How can I recover cuaaa and cuaab ? Thanks in advance. _______ Yuriy Samartsev, Firm ITC Ltd, http://www.itci.net. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message