From owner-freebsd-net Sun Sep 27 10:53:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21206 for freebsd-net-outgoing; Sun, 27 Sep 1998 10:53:21 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21194 for ; Sun, 27 Sep 1998 10:53:16 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id NAA04318; Sun, 27 Sep 1998 13:52:46 -0400 (EDT) (envelope-from wollman) Date: Sun, 27 Sep 1998 13:52:46 -0400 (EDT) From: Garrett Wollman Message-Id: <199809271752.NAA04318@khavrinen.lcs.mit.edu> To: "Allen Smith" Cc: ark@eltex.ru, luigi@labinfo.iet.unipi.it, kev@lab321.ru, mike@smith.net.au, net@FreeBSD.ORG Subject: Re: Packet/traffic shapper ? In-Reply-To: <9809260207.ZM14494@beatrice.rutgers.edu> References: <199809210951.NAA32644@paranoid.eltex.spb.ru> <9809260207.ZM14494@beatrice.rutgers.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Not to get back into the debate regarding ALTQ's "ugliness", the > primary thing I was looking at ALTQ for was the RED (Random Early > Detection) capability of ALTQ, so that I can get the lower-priority > TCP streams to drop back their bandwidth when they're getting too > much. I once did a RED implementation for FreeBSD, mostly aping the sample code in the original RED paper. It's not all that hard, but does involve a lot of fiddling to deal with all the code that thinks it knows how interfaces should operate better than you do. One of the particular difficulties -- if you want RED to work like it's supposed to -- is to squash the internal queueing that a lot of network interface drivers do. I didn't solve that problem (``left as an exercise...''), but it should be obvious that for correct operation, it's essential for RED to be able to determine the actual instantaneous length of the queue. -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 Sun Sep 27 12:00:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29228 for freebsd-net-outgoing; Sun, 27 Sep 1998 12:00:24 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29214 for ; Sun, 27 Sep 1998 12:00:11 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id CAA13841; Mon, 28 Sep 1998 02:57:37 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199809271857.CAA13841@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Allen Smith" cc: ark@eltex.ru, luigi@labinfo.iet.unipi.it, kev@lab321.ru, mike@smith.net.au, net@FreeBSD.ORG Subject: Re: Packet/traffic shapper ? In-reply-to: Your message of "Sat, 26 Sep 1998 02:07:58 -0400." <9809260207.ZM14494@beatrice.rutgers.edu> Date: Mon, 28 Sep 1998 02:57:37 +0800 From: Peter Wemm Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Allen Smith" wrote: > On Sep 21, 5:52am, ark@eltex.ru (possibly) wrote: > > > ALTQ is damn ugly. I'd prefer to see something like dummynet interacting > > with IPFilter instead of ipfw. > > Not to get back into the debate regarding ALTQ's "ugliness", the > primary thing I was looking at ALTQ for was the RED (Random Early > Detection) capability of ALTQ, so that I can get the lower-priority > TCP streams to drop back their bandwidth when they're getting too > much. I've never seen the ALTQ code or implementation, so I'm commenting in ignorance.. Having got that out of the way, it was explained to me the importance of being able to apply different 'shaping' procedures to different IP protocols. ie: RED (I was told 'Random Early Drop') for tcp, and some other rate limit function for udp. I'd really love to see an implementation that does this, if they don't already. > -Allen Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 27 18:15:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24474 for freebsd-net-outgoing; Sun, 27 Sep 1998 18:15:29 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from millennium.stealth.net (millennium.stealth.net [206.252.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24394; Sun, 27 Sep 1998 18:14:52 -0700 (PDT) (envelope-from digital@millennium.stealth.net) Received: from localhost (digital@localhost) by millennium.stealth.net (8.8.7/8.7.3) with SMTP id VAA24465; Sun, 27 Sep 1998 21:14:38 -0400 (EDT) Date: Sun, 27 Sep 1998 21:14:37 -0400 (EDT) From: Shrihari Pandit To: FreeBSD Question cc: FreeBSD Net Subject: rtfree messages In-Reply-To: <006801bde208$b8e51ac0$52099584@pc-kichoi.cst.cnes.fr> 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 have started getting the following rtfree messages in the /var/log/messages.. thousands per day. Sep 28 01:00:28 machine /kernel: rtfree: 0xf26afa00 not Sep 28 01:00:28 machine /kernel: freed (neg refs) Sep 28 01:00:28 machine /kernel: rtfree: 0xf26afa00 not freed (neg refs) Sep 28 01:00:31 machine last message repeated 4052 times This machine is running FreeBSD 2.2.7. GateD is also running. What is the meaning of this message? Thank you, Shrihari. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 27 19:32:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08442 for freebsd-net-outgoing; Sun, 27 Sep 1998 19:32:23 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08342; Sun, 27 Sep 1998 19:31:56 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id TAA01769; Sun, 27 Sep 1998 19:32:13 -0700 (PDT) Message-Id: <199809280232.TAA01769@implode.root.com> To: Shrihari Pandit cc: FreeBSD Question , FreeBSD Net Subject: Re: rtfree messages In-reply-to: Your message of "Sun, 27 Sep 1998 21:14:37 EDT." From: David Greenman Reply-To: dg@root.com Date: Sun, 27 Sep 1998 19:32:13 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >We have started getting the following rtfree messages in the >/var/log/messages.. thousands per day. > >Sep 28 01:00:28 machine /kernel: rtfree: 0xf26afa00 not >Sep 28 01:00:28 machine /kernel: freed (neg refs) >Sep 28 01:00:28 machine /kernel: rtfree: 0xf26afa00 not freed (neg refs) >Sep 28 01:00:31 machine last message repeated 4052 times > >This machine is running FreeBSD 2.2.7. GateD is also running. > >What is the meaning of this message? It could be a bug with freeing a route too many times. It might also be casued by a memory error. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 27 22:17:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01743 for freebsd-net-outgoing; Sun, 27 Sep 1998 22:17:52 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01730 for ; Sun, 27 Sep 1998 22:17:45 -0700 (PDT) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id BAA04032; Mon, 28 Sep 1998 01:16:21 -0400 (EDT) From: "Allen Smith" Message-Id: <9809280116.ZM4030@beatrice.rutgers.edu> Date: Mon, 28 Sep 1998 01:16:21 -0400 In-Reply-To: Luigi Rizzo "Re: Packet/traffic shapper ?" (Sep 26, 2:50am) References: <199809260502.HAA13908@labinfo.iet.unipi.it> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Luigi Rizzo Subject: Re: Packet/traffic shapper ? Cc: ark@eltex.ru, kev@lab321.ru, mike@smith.net.au, net@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sep 26, 2:50am, Luigi Rizzo (possibly) wrote: > > > To get the idea, the most difficult part is the ipfw code to pass > > > RED parameters to the kernel! > > > > Nice... although given other capabilities that IpFilter has (including > > ones that I've patched into it, such as making ICMP messages look like > > they're coming from the supposed destination machine - allowing for > > what will look to other machines like a bridge, but is actually > > looking at higher-level information than just the MAC address), it'd > > be nicer if somebody adapted it and dummynet to work together. > > you just look like the right "somebody" ! Umm... I'm not very good at C. > seriously, i think it would be a fairly easy task to adapt ipfilter > to work with dummynet, as it was for ipfw, and i will be happy to help > you if you want to work a little bit on the adaptation (the main > obstacle for me would be to learn and understand the ipfilter code, you > seem to know it somehow having patched it). Well... the patches in question are not very difficult, due to how it's set up. (It's essentially a matter of adding one flag to mbufs in m_flags, a slight modification to ip_icmp.c, and a few alterations onto the ipfilter interpretation code (which isn't documented very well... sigh).) > All i had to do to support dummynet in ipfw > was to add a new return code to the ipfw call so that i > could decide to pass accepted packets to a pipe. > > Once you have done that, you just need to process the return code from > > (*fr_checkp)(...) > > in the same exact way it is done for > > (*ip_fw_chk_ptr)(...) > > e.g. in ip_input.c (look at the -stable code, since this is not in > -current yet). > > Actually, if we manage to make the kernel interfaces for ipfw and > ipfilter the same (they seem to be already 99% compatible) the > integration will come for free. The kernel interface for ipfilter is somewhat limited by the need to retain compatibility with multiple operating systems - solaris seems to be a particularly tough one, judging from the messages to the ipfilter mailing list. > So essentially, can you look at how hard would it be to add support for > multiple return codes to ipfilter ? Then when the dummynet code will be > in -current (hopefully soon) you will be able to use it. Well... I'll try to take a look at it, but I can't make any guarantees about how soon. There's also the problem that currently 3.0 doesn't run ipfilter... Darren is waiting for it to stabilize before working on ipfilter, which will probably be only at 3.1.1 or so from what he's said. -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 27 22:40:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04186 for freebsd-net-outgoing; Sun, 27 Sep 1998 22:40:28 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA04170 for ; Sun, 27 Sep 1998 22:40:19 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id EAA03142; Mon, 28 Sep 1998 04:38:15 +0100 From: Luigi Rizzo Message-Id: <199809280338.EAA03142@labinfo.iet.unipi.it> Subject: Re: Packet/traffic shapper ? To: easmith@beatrice.rutgers.edu (Allen Smith) Date: Mon, 28 Sep 1998 04:38:15 +0100 (MET) Cc: ark@eltex.ru, kev@lab321.ru, mike@smith.net.au, net@FreeBSD.ORG In-Reply-To: <9809280116.ZM4030@beatrice.rutgers.edu> from "Allen Smith" at Sep 28, 98 01:16:02 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > you just look like the right "somebody" ! > > Umm... I'm not very good at C. you have to learn at some point :) > The kernel interface for ipfilter is somewhat limited by the need to > retain compatibility with multiple operating systems - solaris seems > to be a particularly tough one, judging from the messages to the > ipfilter mailing list. ok, but we can always add a stub to adapt interfaces. > Well... I'll try to take a look at it, but I can't make any guarantees > about how soon. There's also the problem that currently 3.0 doesn't > run ipfilter... Darren is waiting for it to stabilize before working > on ipfilter, which will probably be only at 3.1.1 or so from what he's > said. ok, so the thing seems to be out of question by now... i will try to install a -current snap later this week. let me know if you do some progress or you need help, anytime cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 28 22:05:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11093 for freebsd-net-outgoing; Mon, 28 Sep 1998 22:05:56 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from msf1.swe.ids.dps.casa.es (h025016.nexo.es [195.235.25.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11062 for ; Mon, 28 Sep 1998 22:05:37 -0700 (PDT) (envelope-from jlfreniche@acm.org) Received: from hpswe.swe.ids.dps.casa.es (hpswe.swe.ids.dps.casa.es [172.16.50.100]) by msf1.swe.ids.dps.casa.es (8.8.8/8.8.8) with ESMTP id SAA00281 for ; Mon, 28 Sep 1998 18:16:01 +0200 (CEST) (envelope-from jlfreniche@acm.org) Received: from hpswe.swe.ids.dps.casa.es (localhost [127.0.0.1]) by hpswe.swe.ids.dps.casa.es with SMTP (8.7.6/8.7.3) id PAA08060 for ; Mon, 28 Sep 1998 15:57:18 +0200 (METDST) Message-ID: <360F95BD.464F@acm.org> Date: Mon, 28 Sep 1998 15:57:17 +0200 From: "Juan L. Freniche" X-Mailer: Mozilla 3.01Gold (X11; I; HP-UX B.10.20 9000/879) MIME-Version: 1.0 To: FreeBSD Net Subject: ZNYX and writing/reading LL frames Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, We are going to setup an experimental bench composed by 4 PCs with FreeBSD 2.2.7 (future upgrade to 3.x can be considered), in this way: Network A +-----------+ +-------------+ +-------------+ | | | | | | | | | | | | +------+ +------+ +------+ +------+ | ES-1 | | IS-1 | | IS-2 | | ES-2 | +------+ +------+ +------+ +------+ | | | | | | | | | | | | +-----------+ +-------------+ +-------------+ Network B where ES-x means End System, IS means Intermediate System. Each ES will be fitted with two Ethernet 10/100 Mbps FDX 1-port PCI card, model 345. Also, each IS will be fitted with two Ethernet 10/100 Mbps FDX 4-port card, model 346. Standard protocols (INET) will not be used. Can anybody confirm/respond/clarify the following questions: 1 Any hint in configuring FreeBSD? 2 Are the mentioned ZNYX cards supported? Otherwise we will have to move to Linux, something that I don't want. 3 How to program the interface in promiscuous mode? 4 How to select 10 Mbps or 100 Mbps or normal Ethernet or Full Duplex? 5 How to write link-layer frames? The application will write the complete frame, including the first 14 bytes. 6 How to read, in an exclusive way, link-layer frames? By exclusive I mean that the application will receive the frame and that, given the non-standard header (in particular, the EtherType), that frame must not be passed to the network stack. Thanks in advance. -- Juan L. Freniche To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 28 22:06:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11104 for freebsd-net-outgoing; Mon, 28 Sep 1998 22:06:00 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from msf1.swe.ids.dps.casa.es (h025016.nexo.es [195.235.25.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11070 for ; Mon, 28 Sep 1998 22:05:43 -0700 (PDT) (envelope-from jlfreniche@acm.org) Received: from hpswe.swe.ids.dps.casa.es (hpswe.swe.ids.dps.casa.es [172.16.50.100]) by msf1.swe.ids.dps.casa.es (8.8.8/8.8.8) with ESMTP id SAA00265 for ; Mon, 28 Sep 1998 18:05:17 +0200 (CEST) (envelope-from jlfreniche@acm.org) Received: from hpswe.swe.ids.dps.casa.es (localhost [127.0.0.1]) by hpswe.swe.ids.dps.casa.es with SMTP (8.7.6/8.7.3) id SAA15386 for ; Mon, 28 Sep 1998 18:02:45 +0200 (METDST) Message-ID: <360FB325.2FD1@acm.org> Date: Mon, 28 Sep 1998 18:02:45 +0200 From: "Juan L. Freniche" X-Mailer: Mozilla 3.01Gold (X11; I; HP-UX B.10.20 9000/879) MIME-Version: 1.0 To: FreeBSD Net Subject: Invalid ACKs in SYN-SENT and T/TCP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We have two FreeBSD 2.2.7 boxes connected through Ethernet, both with T/TCP enabled. We have noted the following behaviour: 1 Assume A started several normal TCP connections to B. Client connections in A use local ports selected in the command line when the client is launched. After a while, leave only one such connection in Established. 2 Unplug the Ethernet cable from Box A and reboot Box A. Reason to unplug is to avoid that the RST sent by A reach the connection in B. 3 Launch again several connections from A to B, but using a different local port than the old still-established socket in B. Finish them now normally. The reason of the above is to build, in A, a TAO cache for B. 4 Launch a connection from A to B but using the same local port than the old still-established socket in B. If tcpdump is used for tracing, we will see: - A sends a SYN to B. This new connection is in SYN-SENT in A. - B responds with an ACK, probabilistic invalid because it is the old still-established socket who is responding. - A does not respond with a RST, instead the SYN is retransmitted after the retransmission timeout. - B again responds with an ACK, invalid. - and so on, until the SYN retransmissions are exhausted. RFC 793 (TCP) states in page 66 that a RST must be send if an invalid ACK is received in SYN-SENT (as the received ACK has not the RST bit). Instead, A is ignoring such invalid ACKs, and then retransmitting the SYN. Nothing is said about this in the T/TCP RFCs 1379 and 1644 (at least, I could'nt find this case). I consulted the Stevens book, vol 3, the figure that is identical to the source code (file /usr/src/sys/netinet/tcp_input.c): case TCPS_SYN_SENT: if ((taop = tcp_gettaocache(inp)) == NULL) { taop = &tao_noncached; bzero(taop, sizeof(*taop)); } if ((tiflags & TH_ACK) && (SEQ_LEQ(ti->ti_ack, tp->iss) || SEQ_GT(ti->ti_ack, tp->snd_max))) { /* * If we have a cached CCsent for the remote host, * hence we haven't just crashed and restarted, * do not send a RST. This may be a retransmission * from the other side after our earlier ACK was lost. * Our new SYN, when it arrives, will serve as the * needed ACK. */ if (taop->tao_ccsent != 0) goto drop; else goto dropwithreset; This explain why A didn't sent RSTs when receiving invalid ACKs: A has a valid TAO cache for B, so the invalid ACK is ignored. My question is: is this behaviour what it was intended? The comment in the code covers one case, but aborting connections and loosing its RST is not so unlikely. Should A come back to RFC 793? -- Juan L. Freniche To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 30 06:11:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28408 for freebsd-net-outgoing; Wed, 30 Sep 1998 06:11:05 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28403 for ; Wed, 30 Sep 1998 06:11:02 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id PAA02793 for ; Wed, 30 Sep 1998 15:15:50 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id PAA23543 for ; Wed, 30 Sep 1998 15:27:25 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id PAA21212; Wed, 30 Sep 1998 15:18:59 +0200 (CEST) Message-ID: <19980930151859.05182@deepo.prosa.dk> Date: Wed, 30 Sep 1998 15:18:59 +0200 From: Philippe Regnauld To: freebsd-net@FreeBSD.ORG Subject: 2.2.7 + natd + "No buffer space" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Setup: 2.2.7 with natd running, two NICs: - outside is a RealTek el-cheapo PCI NIC (NE2000), ed1 - inside is 3Com 3C509, ep0 Twice in two days, the insied NIC has jammed with "no buffer space". I can solve this by doing ifconfig ep0 down, ifconfig ep0 up, but there has to be something else ? I've looked in the mailing lists, and I can see quite a few people've had the same problem, but no solutions. Is there some parameter I can bump in the kernel ? Also, I've only seen this behavior on 3Com NICs. My old SMC and DEC 21140 cards have never acted up like this (which really makes me hate 3Com more and more, but that's another story). -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 30 07:58:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15105 for freebsd-net-outgoing; Wed, 30 Sep 1998 07:58:12 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from at.dotat.com (zed.dotat.com [203.38.154.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15083; Wed, 30 Sep 1998 07:58:04 -0700 (PDT) (envelope-from hart@at.dotat.com) Received: from at.dotat.com (localhost.dotat.com [127.0.0.1]) by at.dotat.com (8.8.7/8.8.5) with ESMTP id AAA15771; Thu, 1 Oct 1998 00:29:33 +0930 (CST) Message-Id: <199809301459.AAA15771@at.dotat.com> To: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: 802.1Q VLAN support Reply-to: hart@dotat.com Date: Thu, 01 Oct 1998 00:29:32 +0930 From: Leigh Hart Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm developing some single board computer applications that require 802.1Q vlan support (of the simplest kind) and in trawling through these list archives I found mention of if_vlan.c ...: /* * ... * ... * ... * * $Id: if_vlan.c,v 1.3 1998/08/23 03:07:10 wollman Exp $ */ /* * if_vlan.c - pseudo-device driver for IEEE 802.1Q virtual LANs. * Might be extended some day to also handle IEEE 802.1p priority * tagging. This is sort of sneaky in the implementation, since * we need to pretend to be enough of an Ethernet implementation * to make arp work. The way we do this is by telling everyone * that we are an Ethernet, and then catch the packets that * ether_output() left on our output queue queue when it calls * if_start(), rewrite them for use by the real outgoing interface, * and ask it to send them. */ This is about all I can find in the kernel-current source tree that relates to 802.1Q - there's little or no documentation I can find that tells me how to start using this code...(god help me if it's there and I havn't looked hard enough :[) Any pointers to /dev/obvious gratefully accepted... PS - my work with 802.1Q has found that, despite the current draft spec suggesting that each vendor should decide on their own what to do about the problem of having a larger frame size due to the extra 4 byte VLAN header, most vendors have opted to support an increas by four bytes in the frame size... It should be noted that if FreeBSD is going to support this in any sensible manner, it should start including an option for changing ETHER_MAX_LEN in the kernel, either real time or at compile time... Cheers Leigh -- | "By the time they had diminished | Leigh Hart, | | from 50 to 8, the other dwarves | Dotat Communications Pty Ltd | | began to suspect 'Hungry' ..." | GPO Box 487 Adelaide SA 5001 | | -- Gary Larson, "The Far Side" | http://www.dotat.com/hart/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 30 09:24:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26704 for freebsd-net-outgoing; Wed, 30 Sep 1998 09:24:02 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26662 for ; Wed, 30 Sep 1998 09:23:57 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA16321; Wed, 30 Sep 1998 12:23:11 -0400 (EDT) (envelope-from wollman) Date: Wed, 30 Sep 1998 12:23:11 -0400 (EDT) From: Garrett Wollman Message-Id: <199809301623.MAA16321@khavrinen.lcs.mit.edu> To: hart@dotat.com Cc: freebsd-net@FreeBSD.ORG Subject: 802.1Q VLAN support In-Reply-To: <199809301459.AAA15771@at.dotat.com> References: <199809301459.AAA15771@at.dotat.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: [One list only, please!] > I'm developing some single board computer applications that require > 802.1Q vlan support (of the simplest kind) and in trawling through > these list archives I found mention of if_vlan.c ...: > This is about all I can find in the kernel-current source tree that > relates to 802.1Q - there's little or no documentation I can find > that tells me how to start using this code...(god help me if it's > there and I havn't looked hard enough :[) I don't even know whether it works at this point, because my 1Q switch was an eval unit that I had to send back (and my PO for the real thing has been held up by management). The way you configure these things is by using the SIOCSIFGENERIC-based ioctl interface defined in . I wrote a little hack which configures them, but I believe the function should really be a part of ifconfig, which is why it's not there in the source tree. Beyond that, UTSL. There is at present no support for multicast or promiscuous mode, both of which would need to be fixed in order for this code to be really useful. (The particular application I had in mind doesn't require those functions.) > It should be noted that if FreeBSD is going to support this in > any sensible manner, it should start including an option for > changing ETHER_MAX_LEN in the kernel, either real time or at > compile time... Not all hardware and drivers are capable of supporting larger packets. The correct thing is, for those drivers which are able, to so indicate by setting their ifi_hdrlen to sizeof(struct ether_vlan_header) rather than sizeof(struct ether_header). You will note the following code in vlan_config: if (p->if_data.ifi_hdrlen == sizeof(struct ether_vlan_header)) ifv->ifv_if.if_mtu = p->if_mtu; else ifv->ifv_if.if_mtu = p->if_data.ifi_mtu - EVL_ENCAPLEN; I had originally contemplated implementing this functionality with subinterfaces (a la Slowaris), but expediency quickly won out, so I did the thing which avoided any painful work or interface changes. -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 Sep 30 15:35:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12685 for freebsd-net-outgoing; Wed, 30 Sep 1998 15:35:34 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12640 for ; Wed, 30 Sep 1998 15:35:15 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from grjottunagard.ifi.uio.no (2602@grjottunagard.ifi.uio.no [129.240.64.131]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id AAA05937; Thu, 1 Oct 1998 00:34:54 +0200 (MET DST) Received: (from dag-erli@localhost) by grjottunagard.ifi.uio.no ; Thu, 1 Oct 1998 00:34:54 +0200 (MET DST) Mime-Version: 1.0 To: Philippe Regnauld Cc: freebsd-net@FreeBSD.ORG Subject: Re: 2.2.7 + natd + "No buffer space" References: <19980930151859.05182@deepo.prosa.dk> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 01 Oct 1998 00:34:53 +0200 In-Reply-To: Philippe Regnauld's message of "Wed, 30 Sep 1998 15:18:59 +0200" Message-ID: Lines: 16 X-Mailer: Gnus v5.6.44/Emacs 20.3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id PAA12648 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Philippe Regnauld writes: > - inside is 3Com 3C509, ep0 ^^^^^^^^^^ > Twice in two days, the insied NIC has jammed with "no buffer space". Known bug in the ep0 driver. When will people learn to check the archives? > I can solve this by doing ifconfig ep0 down, ifconfig ep0 up, but > there has to be something else ? ifconfig ep0 down is unnecessary, up is enough. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 30 18:01:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08831 for freebsd-net-outgoing; Wed, 30 Sep 1998 18:01:02 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08821; Wed, 30 Sep 1998 18:00:46 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA04638; Wed, 30 Sep 1998 18:05:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810010105.SAA04638@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hart@dotat.com cc: freebsd-net@FreeBSD.ORG, wollman@FreeBSD.ORG Subject: Re: 802.1Q VLAN support In-reply-to: Your message of "Thu, 01 Oct 1998 00:29:32 +0930." <199809301459.AAA15771@at.dotat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Sep 1998 18:05:10 -0700 From: Mike Smith Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I'm developing some single board computer applications that require > 802.1Q vlan support (of the simplest kind) and in trawling through > these list archives I found mention of if_vlan.c ...: > > /* > * ... > * ... > * ... > * > * $Id: if_vlan.c,v 1.3 1998/08/23 03:07:10 wollman Exp $ > */ > > /* > * if_vlan.c - pseudo-device driver for IEEE 802.1Q virtual LANs. > * Might be extended some day to also handle IEEE 802.1p priority > * tagging. This is sort of sneaky in the implementation, since > * we need to pretend to be enough of an Ethernet implementation > * to make arp work. The way we do this is by telling everyone > * that we are an Ethernet, and then catch the packets that > * ether_output() left on our output queue queue when it calls > * if_start(), rewrite them for use by the real outgoing interface, > * and ask it to send them. > */ > > This is about all I can find in the kernel-current source tree that > relates to 802.1Q - there's little or no documentation I can find > that tells me how to start using this code...(god help me if it's > there and I havn't looked hard enough :[) 'pseudo-device vlan X' will get it into the kernel. However it seems that there's a missing userland application required for the 'SIOC[GS]ETVLAN' ioctls. You ought to ask Garrett about this. > PS - my work with 802.1Q has found that, despite the current draft > spec suggesting that each vendor should decide on their own what > to do about the problem of having a larger frame size due to the > extra 4 byte VLAN header, most vendors have opted to support an > increas by four bytes in the frame size... > > It should be noted that if FreeBSD is going to support this in > any sensible manner, it should start including an option for > changing ETHER_MAX_LEN in the kernel, either real time or at > compile time... Ick. How does this impact hardware with frame size limitations? You'll need to differentiate between "how big a frame is allowed to be" and "how big we will normally make a frame". Diffs would be good. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 30 19:51:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24911 for freebsd-net-outgoing; Wed, 30 Sep 1998 19:51:36 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from at.dotat.com (zed.dotat.com [203.38.154.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24893 for ; Wed, 30 Sep 1998 19:51:31 -0700 (PDT) (envelope-from hart@at.dotat.com) Received: from at.dotat.com (localhost.dotat.com [127.0.0.1]) by at.dotat.com (8.8.7/8.8.5) with ESMTP id MAA17381; Thu, 1 Oct 1998 12:22:46 +0930 (CST) Message-Id: <199810010252.MAA17381@at.dotat.com> To: Mike Smith cc: freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLAN support In-reply-to: Your message of "Wed, 30 Sep 1998 18:05:10 MST." <199810010105.SAA04638@dingo.cdrom.com> Date: Thu, 01 Oct 1998 12:22:44 +0930 From: Leigh Hart Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Mike [:p] Mike Smith wrote: > > > I'm developing some single board computer applications that require > > 802.1Q vlan support (of the simplest kind) and in trawling through > > these list archives I found mention of if_vlan.c ...: > > 'pseudo-device vlan X' Ooer - Thanks :) > will get it into the kernel. However it seems that there's a missing > userland application required for the 'SIOC[GS]ETVLAN' ioctls. I can work that bit out easy enough once the code is in the kernel! > > PS - my work with 802.1Q has found that, despite the current draft > > spec suggesting that each vendor should decide on their own what > > to do about the problem of having a larger frame size due to the > > extra 4 byte VLAN header, most vendors have opted to support an > > increas by four bytes in the frame size... > > > > It should be noted that if FreeBSD is going to support this in > > any sensible manner, it should start including an option for > > changing ETHER_MAX_LEN in the kernel, either real time or at > > compile time... > > Ick. How does this impact hardware with frame size limitations? Some hardware can't physically cope with larger frame sizes, so you don't use that hardware - I've found SMC, NE2000 and some WD cards (ie: the ed driver set) have no problems supporting the larger frames (just by tweaking the value in the system includes and rebuilding the kernel, then using ifconfig to set a larger mtu) - but I havn't tried any others yet... Normally, if you try and set the MTU of an interface above 1500 using ifconfig, the ioctl (set mtu): will fail with "Invalid argument". The SIOCSIFMTU ioctl call which ifconfig uses eventually ends up in one place or another inside the driver code which does something not unlike this: /* * Set the interface MTU. */ if (ifr->ifr_mtu > ETHERMTU) { error = EINVAL; } else { ifp->if_mtu = ifr->ifr_mtu; } So regardless of hardware, it enforces ETHERMTU as the maximum possible MTU on any interface of any type. If you change ETHERMTU to reflect the fact you want an extra four bytes in the frame, certainly the SMC and NE2k's work - you can (a) set the MTU to 1504 using ifconfig, and (b) large packets do make it across the wire (eg: ping -s 2000 desthost splits into 1504 and 496 byte packets). > You'll need to differentiate between "how big a frame is allowed to be" > and "how big we will normally make a frame". The real problem with the draft dot1q standard is that they don't address this issue - they leave it up to the vendor to choose between growing the frame size by four bytes for the VLAN header and forcing a lower MTU for the network - to date, no switch vendors have chosen to do the latter because it isn't possible, practically, to force everyone to change their MTU before using this vendor's switch - would you do that?? The only other option is to fragment the frames across the trunk port (vlan tagged port) but *ouch* that hurts the throughput... > Diffs would be good. 8) Miffs are better ;] Cheers Leigh -- | "By the time they had diminished | Leigh Hart, | | from 50 to 8, the other dwarves | Dotat Communications Pty Ltd | | began to suspect 'Hungry' ..." | GPO Box 487 Adelaide SA 5001 | | -- Gary Larson, "The Far Side" | http://www.dotat.com/hart/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 30 20:06:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26266 for freebsd-net-outgoing; Wed, 30 Sep 1998 20:06:19 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from at.dotat.com (zed.dotat.com [203.38.154.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26249 for ; Wed, 30 Sep 1998 20:06:04 -0700 (PDT) (envelope-from hart@at.dotat.com) Received: from at.dotat.com (localhost.dotat.com [127.0.0.1]) by at.dotat.com (8.8.7/8.8.5) with ESMTP id MAA17458 for ; Thu, 1 Oct 1998 12:37:47 +0930 (CST) Message-Id: <199810010307.MAA17458@at.dotat.com> To: freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLAN support In-reply-to: Your message of "Wed, 30 Sep 1998 12:23:11 -0400." <199809301623.MAA16321@khavrinen.lcs.mit.edu> Date: Thu, 01 Oct 1998 12:37:46 +0930 From: Leigh Hart Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Garrett, Garrett Wollman wrote: ... [on if_vlan.c] ... > Not all hardware and drivers are capable of supporting larger packets. > The correct thing is, for those drivers which are able, to so indicate > by setting their ifi_hdrlen to sizeof(struct ether_vlan_header) rather > than sizeof(struct ether_header). You will note the following code > in vlan_config: > > if (p->if_data.ifi_hdrlen == sizeof(struct ether_vlan_header)) > ifv->ifv_if.if_mtu = p->if_mtu; > else > ifv->ifv_if.if_mtu = p->if_data.ifi_mtu - EVL_ENCAPLEN; Is this changing the MTU of the physical interface? > I had originally contemplated implementing this functionality with > subinterfaces (a la Slowaris), but expediency quickly won out, so I > did the thing which avoided any painful work or interface changes. So how does each VLAN appear on the FreeBSD box under your model? Cheers Leigh -- | "By the time they had diminished | Leigh Hart, | | from 50 to 8, the other dwarves | Dotat Communications Pty Ltd | | began to suspect 'Hungry' ..." | GPO Box 487 Adelaide SA 5001 | | -- Gary Larson, "The Far Side" | http://www.dotat.com/hart/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 30 21:41:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09559 for freebsd-net-outgoing; Wed, 30 Sep 1998 21:41:21 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09551 for ; Wed, 30 Sep 1998 21:41:13 -0700 (PDT) (envelope-from kazu@iijlab.net) Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8]) by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id NAA18077 for ; Thu, 1 Oct 1998 13:40:55 +0900 (JST) Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id NAA17520 for ; Thu, 1 Oct 1998 13:40:54 +0900 (JST) Received: from localhost (mine.iij.ad.jp [192.168.4.209]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id NAA11253 for ; Thu, 1 Oct 1998 13:40:54 +0900 (JST) To: freebsd-net@FreeBSD.ORG Subject: KAME 980930 stable release Mime-Version: 1.0 From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981001134057Y.kazu@iijlab.net> Date: Thu, 01 Oct 1998 13:40:57 +0900 X-Dispatcher: imput version 980923(IM101) Lines: 76 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We are happy to inform you the stable release of KAME 980930. The kits are available from: http://www.kame.net/ Summary of the differences from the previous release is enclosed below. Enjoy! --Kazu, KAME Project ---from here Here is summary of differences between KAME stable 980731 and 980930. <> - Added our home-brew NAT code, called "SuMiRe". (FreeBSD/BSDI only) NOTE: Since it lacks documentations at this moment, we don't recommend you to try this right now. <> - Supported router alert option to some extent. - Supported multicast listener discovery to some extent(host side). - Improved the management code for information obtained from router advertisements. - rtsold: router solicitation daemon, for interface management on endhosts. - Router renumbering support is ongoing. (is not working right now). - Number of multicast groups per socket is now unlimited; it was limited to 20 in the previous stable release. - Added a new mechanism to manage prefixes advertised by router advertisements for mobile stations. - IPv6 version of multicast kludge; unicast addresses can be safely deleted from an interface even if there is a multicast group on the interface. - More conformance to Neighbor Discovery specification, especially about processing router advertisements(see CHANGELOG). - IPV6_{ADD,DROP}_MEMBERSHIP is renamed to IPV6_{JOIN,LEAVE}_MEMBERSHIP. NOTE: latest revision of bsd-api-new-02, called "02a", renamed this again into IPV6_{JOIN,LEAVE}_GROUP. This kit uses definition based on "old 02". - ICMP Redirects to on-link destinations, that is, not to better routers. - ICMP error rate limitation. <> - "struct sockaddr_in6" was changed again to conform to draft-ietf-ipngwg-bsd-api-new-02 spec. sin6_ifindex member was removed, and struct members were reordered. NOTE: ALL THE USERLAND TOOLS MUST BE RECOMPILED. - Some library functions, inet6_option_XXX, are newly implemented, which are defined in RFC 2292(advanced sockets API). <> - "racoon" IKE daemon is now working in limited situations. - Proper source IPv4 address will be used for outer IPv4 header of IPv4 IPsec tunnel. Now you can configure VPN network with KAME routers. - Key management code is improved. <> - EPRT/EPSV support for ftp/ftpd. (rfc2428) - getnodeby{addr,name} has renamed to getipnodeby{addr,name} to conform to draft-ietf-ipngwg-bsd-api-new-02 spec. - Bunch of updates/additions in IPv6-ready ports collection (FreeBSD kit only). - Some of IPv6 enable patches are now distributed separately from FreeBSD ports directory, so that BSDI/NetBSD users can enjoy those patches. Please check ftp://ftp.kame.net/pub/kame/misc/. <> - For BSDI, ATM driver based on ALTQ kit has been merged into the kernel. ATM userland tools must be grabbed from ALTQ kit. visit ftp://ftp.csl.sony.co.jp/pub/kjc/. - Synchronized some of the kernel source code among three operating systems we support (FreeBSD/BSDI/NetBSD), to ease maintainance. ---to here To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 1 02:29:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17628 for freebsd-net-outgoing; Thu, 1 Oct 1998 02:29:55 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from msf1.swe.ids.dps.casa.es (h024124.nexo.es [195.235.24.124]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17619 for ; Thu, 1 Oct 1998 02:29:37 -0700 (PDT) (envelope-from jlfreniche@acm.org) Received: from hpswe.swe.ids.dps.casa.es (hpswe.swe.ids.dps.casa.es [172.16.50.100]) by msf1.swe.ids.dps.casa.es (8.8.8/8.8.8) with ESMTP id JAA04531 for ; Thu, 1 Oct 1998 09:35:52 +0200 (CEST) (envelope-from jlfreniche@acm.org) Received: from hpswe.swe.ids.dps.casa.es (localhost [127.0.0.1]) by hpswe.swe.ids.dps.casa.es with SMTP (8.7.6/8.7.3) id JAA19355 for ; Thu, 1 Oct 1998 09:33:00 +0200 (METDST) Message-ID: <3613302B.449D@acm.org> Date: Thu, 01 Oct 1998 09:32:59 +0200 From: "Juan L. Freniche" X-Mailer: Mozilla 3.01Gold (X11; I; HP-UX B.10.20 9000/879) MIME-Version: 1.0 To: FreeBSD Net Subject: Invalid ACKs in SYN-SENT and T/TCP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Recently I sent this message to freebsd-net and got no response. May be that the message never arrived so I try again: We have two FreeBSD 2.2.7 boxes connected through Ethernet, both with T/TCP enabled. We have noted the following behaviour: 1 Assume A started several normal TCP connections to B. Client connections in A use local ports selected in the command line when the client is launched. After a while, leave only one such connection in Established. 2 Unplug the Ethernet cable from Box A and reboot Box A. Reason to unplug is to avoid that the RSTs sent by A reach the connection in B. 3 Launch again several connections from A to B, but using a different local port than the old still-established socket in B. Finish them now normally. The reason of the above is to build, in A, a TAO cache for B. 4 Launch a connection from A to B but using the same local port than the old still-established socket in B. If tcpdump is used for tracing, we will see: - A sends a SYN to B. This new connection is in SYN-SENT in A. - B responds with an ACK, probabilistic invalid because it is the old still-established socket who is responding. - A does not respond with a RST, instead the SYN is retransmitted after the retransmission timeout. - B again responds with an ACK, invalid. - and so on, until the SYN retransmissions are exhausted. RFC 793 (TCP) states in page 66 that a RST must be send if an invalid ACK is received in SYN-SENT (as the received ACK has not the RST bit). Instead, A is ignoring such invalid ACKs, and then retransmitting the SYN. Nothing is said about this in the T/TCP RFCs 1379 and 1644 (at least, I could'nt find this case). I consulted the Stevens book, vol 3, the figure that is identical to the source code (file /usr/src/sys/netinet/tcp_input.c): case TCPS_SYN_SENT: if ((taop = tcp_gettaocache(inp)) == NULL) { taop = &tao_noncached; bzero(taop, sizeof(*taop)); } if ((tiflags & TH_ACK) && (SEQ_LEQ(ti->ti_ack, tp->iss) || SEQ_GT(ti->ti_ack, tp->snd_max))) { /* * If we have a cached CCsent for the remote host, * hence we haven't just crashed and restarted, * do not send a RST. This may be a retransmission * from the other side after our earlier ACK was lost. * Our new SYN, when it arrives, will serve as the * needed ACK. */ if (taop->tao_ccsent != 0) goto drop; else goto dropwithreset; This explain why A didn't sent RSTs when receiving invalid ACKs: A has a valid TAO cache for B, so the invalid ACK is ignored. My question is: is this behaviour what it was intended? The comment in the code covers one case, but aborting connections and loosing its RST is not so unlikely. Should A come back to RFC 793? -- Juan L. Freniche To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 1 02:29:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17645 for freebsd-net-outgoing; Thu, 1 Oct 1998 02:29:57 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from msf1.swe.ids.dps.casa.es (h024124.nexo.es [195.235.24.124]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17611 for ; Thu, 1 Oct 1998 02:29:17 -0700 (PDT) (envelope-from jlfreniche@acm.org) Received: from hpswe.swe.ids.dps.casa.es (hpswe.swe.ids.dps.casa.es [172.16.50.100]) by msf1.swe.ids.dps.casa.es (8.8.8/8.8.8) with ESMTP id JAA04448 for ; Thu, 1 Oct 1998 09:31:43 +0200 (CEST) (envelope-from jlfreniche@acm.org) Received: from hpswe.swe.ids.dps.casa.es (localhost [127.0.0.1]) by hpswe.swe.ids.dps.casa.es with SMTP (8.7.6/8.7.3) id JAA19131 for ; Thu, 1 Oct 1998 09:28:50 +0200 (METDST) Message-ID: <36132F32.2D81@acm.org> Date: Thu, 01 Oct 1998 09:28:50 +0200 From: "Juan L. Freniche" X-Mailer: Mozilla 3.01Gold (X11; I; HP-UX B.10.20 9000/879) MIME-Version: 1.0 To: FreeBSD Net Subject: ZNYX and writing/reading LL frames Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Recently I sent the following message to freebsd-net and received no response. May be that the message never arrived, so I try again with a second version (several of the questions included in the first version are now solved): We are going to setup an experimental bench composed by 4 PCs with FreeBSD 2.2.7 (future upgrade to 3.x can be considered), in this way: Network A +-----------+ +-------------+ +-------------+ | | | | | | | | | | | | +------+ +------+ +------+ +------+ | ES-1 | | IS-1 | | IS-2 | | ES-2 | +------+ +------+ +------+ +------+ | | | | | | | | | | | | +-----------+ +-------------+ +-------------+ Network B where ES-x means End System, IS means Intermediate System. Each ES will be fitted with two Ethernet 10/100 Mbps FDX 1-port PCI card, model 345. Also, each IS will be fitted with two Ethernet 10/100 Mbps FDX 4-port card, model 346. Can anybody confirm/respond/clarify the following questions: 1 Any hint in configuring FreeBSD? ---> there was really no problem. 2 Are the mentioned ZNYX cards supported? Otherwise we will have to move to Linux, something that I don't want. ---> yes, uses the device de. 3 How to program (in C) the interface in promiscuous mode? ---> Still Open 4 How to select 10 Mbps or 100 Mbps or normal Ethernet or Full Duplex? ---> ifconfig media works for 10 and 100 Mbps. However, ifconfig mediaopt full-duplex does not work. Is it supported? 5 How to write link-layer frames? The application will write the complete frame, including the first 14 bytes. ---> Still Open 6 How to read, in an exclusive way, link-layer frames? By exclusive I mean that the application will receive the frame and that, given the non-standard header (in particular, the EtherType), that frame must not be passed to the network stack. ---> Still Open Thanks in advance. Standard protocols (INET) will not be used. -- Juan L. Freniche To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 1 03:01:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21619 for freebsd-net-outgoing; Thu, 1 Oct 1998 03:01:21 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21591 for ; Thu, 1 Oct 1998 03:01:07 -0700 (PDT) (envelope-from flumiani@infotech.it) From: flumiani@infotech.it Received: from infotech.ud.nettuno.it (infotech.ud.nettuno.it [193.207.87.2]) by bologna.nettuno.it (8.8.6/8.8.6/NETTuno 3.1) with SMTP id MAA14491 for ; Thu, 1 Oct 1998 12:00:42 +0200 (MDT) Received: from webserver [192.168.1.4] by posta.infotech [192.168.1.2] with SMTP (MDaemon.v2.7.SP4.R) for ; Thu, 01 Oct 1998 10:32:20 +0200 Message-Id: <3.0.6.32.19981001103149.007b7450@pop> X-Sender: flumiani@pop X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Thu, 01 Oct 1998 10:31:49 +0200 To: freebsd-net@FreeBSD.ORG Subject: sendmail ups the line? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MDaemon-Deliver-To: freebsd-net@FreeBSD.ORG X-Return-Path: flumiani@infotech.it Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello everybody! I use a FredBSD box as a gateway to connect a LAN to Internet. To do this, i followed the PPP Primer. WHAT HAPPENS: If the PPP is working in the background (command ppp -auto -alias ips_connect_script) everytime an e-mail client as Eudora Light (also Elm on the same FreeBSD system) sends a message to local address (the same for non local addresses) makes the sendmail do a DNS request to identify the IP of the client's box. Becouse DNS is not on the LAN but on the internet, ppp dials out. Well, this is what i suppose :) Every other client i tested: ftp, telnet, pop3 and http doesn't act like that, both using local and remote clients on the LAN. If the ppp daemon doesn't listen in background sending mail from every email client works fine. I tryed to avoid this action programming sendmail.cf but nothing. Next my LAN, FreeBSD box configuration. Can someone help me? CONFIGURATIONS The LAN has 192.168.0.x IPs. (for now just 2 PCs) /etc/hosts 127.0.0.1 localhost.sts-cast.it localhost 192.168.0.1 caronte.sts-cast.it caronte 192.168.0.1 caronte.sts-cast.it. 192.168.0.5 24h.sts-cast.it 24h /etc/host.conf hosts bind /etc/resolv.conf domain sts-cast.it nameserver 193.43.2.1 <-- This is the nameserver of my IPS dns.nettuno.it PPP.CONF AND SENDMAIL.CF Ask if you need it :) Thanks! Federico Flumiani -- Il mio email: flumiani@infotech.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 1 07:04:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21910 for freebsd-net-outgoing; Thu, 1 Oct 1998 07:04:41 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from at.dotat.com (zed.dotat.com [203.38.154.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21859 for ; Thu, 1 Oct 1998 07:04:33 -0700 (PDT) (envelope-from hart@at.dotat.com) Received: from at.dotat.com (localhost.dotat.com [127.0.0.1]) by at.dotat.com (8.8.7/8.8.5) with ESMTP id XAA19276; Thu, 1 Oct 1998 23:36:09 +0930 (CST) Message-Id: <199810011406.XAA19276@at.dotat.com> To: "Juan L. Freniche" cc: FreeBSD Net Subject: Re: ZNYX and writing/reading LL frames In-reply-to: Your message of "Thu, 01 Oct 1998 09:28:50 +0200." <36132F32.2D81@acm.org> Date: Thu, 01 Oct 1998 23:36:09 +0930 From: Leigh Hart Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Juan, Funny, I started asking some of these questions of myself just yesterday ;] Most of your answers lie within man... I have no idea what you're trying to do with that wierd'n'wonderful network diagram, however, onto your questions: "Juan L. Freniche" wrote: > > 3 How to program (in C) the interface in promiscuous mode? > ---> Still Open man bpf and see below. > 5 How to write link-layer frames? The application will write the > complete frame, including the first 14 bytes. > ---> Still Open man bpf - you can open /dev/bpf0 - ioctl a few times to setup which interface you want to attach the filter to, use ioctl to set the interface to promiscuous mode and optionally use ioctl again to set the read operation to one-packet-at-a-time mode, rather than allowing the bpf to buffer as many frames into your read call as it can manage (using BIOCIMMEDIATE) - this makes life a little simpler, that's all. Then you can write frames to your hearts content. There is one caveat - in 2.2.5 (at least, not sure about -current) when you write an ethernet frame out via the bpf file descriptor, the kernel re-writes the source MAC address in your packet to that of the interface which is being used to send the packet. This is designed to prevent spoof attacks I presume, but its a pain in the neck if you're writing a bridge application in userland :) I'll be generating a small diff for the hack I made to fix this sooner or later ;] (see if_ethersubr.c in ether_output, at or about case AF_UNSPEC:, where memcpy is used to set eh->ether_shost) Will allow you to write link-layer frames to the device. > 6 How to read, in an exclusive way, link-layer frames? By exclusive I > mean that the application will receive the frame and that, given the > non-standard header (in particular, the EtherType), that frame must > not be passed to the network stack. > ---> Still Open You can read packets using the above bpf stuff, but note that your buffer will contain not just the packet, but also an extra bpf_hdr which has a few other details about the packet - use the following to bypass the header and get straight into the meat of the ethernet frame: frame_ptr = buffer+((struct bpf_hdr *)buffer)->bh_hdrlen; (don't use sizeof(struct bpf_hdr) to get the length of the bpf_hdr, read /usr/include/net/bpf.h for the reasons why...) As for stopping the packets from reaching the higher level protocols, I don't believe you can do this exclusively without frobbing the kernel. Cheers Leigh -- | "By the time they had diminished | Leigh Hart, | | from 50 to 8, the other dwarves | Dotat Communications Pty Ltd | | began to suspect 'Hungry' ..." | GPO Box 487 Adelaide SA 5001 | | -- Gary Larson, "The Far Side" | http://www.dotat.com/hart/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 1 11:53:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11558 for freebsd-net-outgoing; Thu, 1 Oct 1998 11:53:11 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from oldyeller.comtest.com (comtest.hits.net [206.127.244.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11530 for ; Thu, 1 Oct 1998 11:52:56 -0700 (PDT) (envelope-from randal@comtest.com) Received: from graphics.comtest.com (graphics.comtest.com [206.127.245.194]) by oldyeller.comtest.com (8.8.8/8.8.8) with SMTP id IAA11827; Thu, 1 Oct 1998 08:41:18 -1000 (HST) (envelope-from randal@comtest.com) Message-Id: <199810011841.IAA11827@oldyeller.comtest.com> From: "Randal S. Masutani" Organization: ComTest Technologies, Inc. To: "Juan L. Freniche" Date: Thu, 1 Oct 1998 08:56:00 -1000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Invalid ACKs in SYN-SENT and T/TCP Reply-to: randal@comtest.com CC: freebsd-net@FreeBSD.ORG In-reply-to: <3613302B.449D@acm.org> X-mailer: Pegasus Mail for Windows (v3.01b) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1 Oct 98, at 9:32, Juan L. Freniche wrote: > My question is: is this behaviour what it was intended? The comment in > the code covers one case, but aborting connections and loosing its RST > is not so unlikely. Should A come back to RFC 793? I have seen this exact behavior myself and I often wondered why it didn't RST the connection? I always had to kill the open connection on the other computer before I could continue. I haven't reviewed the RFCs, so unfortunately I don't have any answers. Randal Masutani ------------------------------------------------------------------------- ComTest Technologies, Inc. 3049 Ualena St., Suite 1005 Honolulu, Hawaii 96819 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 1 12:48:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19920 for freebsd-net-outgoing; Thu, 1 Oct 1998 12:48:43 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from enterprise.sl.ru ([212.5.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19910 for ; Thu, 1 Oct 1998 12:48:36 -0700 (PDT) (envelope-from tarkhil@sl.ru) Received: from enterprise.sl.ru (tarkhil@localhost.enterprise.sl.ru [127.0.0.1] (may be forged)) by enterprise.sl.ru (8.8.8/8.8.8) with ESMTP id XAA07327 for ; Thu, 1 Oct 1998 23:46:30 +0400 (MSD) (envelope-from tarkhil@enterprise.sl.ru) Message-Id: <199810011946.XAA07327@enterprise.sl.ru> To: freebsd-net@FreeBSD.ORG Subject: Sorry, test Date: Thu, 01 Oct 1998 23:46:29 +0400 From: "Alexander B. Povolotsky" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! I _do_ know this is The Wrong Thing, but I've just set up this server and I'm not sure if it works... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 1 13:43:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00311 for freebsd-net-outgoing; Thu, 1 Oct 1998 13:43:58 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA00289; Thu, 1 Oct 1998 13:43:30 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id TAA11715; Thu, 1 Oct 1998 19:43:26 +0100 From: Luigi Rizzo Message-Id: <199810011843.TAA11715@labinfo.iet.unipi.it> Subject: dummynet for 3.0 available To: current@FreeBSD.ORG Date: Thu, 1 Oct 1998 19:43:26 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have what i think is a working version of my dummynet code and associated stuff for 3.0. Diffs against 3.0-980925 are at http://www.iet.unipi.it/~luigi/ip_dummynet/dn-3.0-981001.diffs testers welcome, but i don't think this will go on the 3.0-RELEASE CD other than as an "experimental" patchfile (still, it will be nice to have bugs sorted out!) luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 1 14:29:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08532 for freebsd-net-outgoing; Thu, 1 Oct 1998 14:29:52 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from us.net (laurel.us.net [198.240.72.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08526 for ; Thu, 1 Oct 1998 14:29:51 -0700 (PDT) (envelope-from dgs@us.net) Received: (from dgs@localhost) by us.net (8.8.8/8.8.8) id RAA15429; Thu, 1 Oct 1998 17:29:22 -0400 (EDT) X-Provider: US Net - Advanced Internet Services - 301-361-USNET - info@us.net Where Business Connects! (tm) -- http://www.us.net/ From: David Stoddard Message-Id: <199810012129.RAA15429@us.net> Subject: Re: Sorry, test To: tarkhil@sl.ru (Alexander B. Povolotsky) Date: Thu, 1 Oct 1998 17:29:19 -0400 (EDT) Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <199810011946.XAA07327@enterprise.sl.ru> from "Alexander B. Povolotsky" at Oct 1, 98 11:46:29 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alexander B. Povolotsky writes: > Hello! > > I _do_ know this is The Wrong Thing, but I've just set up this server and > I'm not sure if it works... Use bounce@us.net to do this instead ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 1 15:39:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19804 for freebsd-net-outgoing; Thu, 1 Oct 1998 15:39:10 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19781 for ; Thu, 1 Oct 1998 15:38:55 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id PAA25983; Thu, 1 Oct 1998 15:37:21 -0700 (PDT) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id PAA29735; Thu, 1 Oct 1998 15:36:50 -0700 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id QAA04823; Thu, 1 Oct 1998 16:36:49 -0600 Message-ID: <36140401.36C4B897@softweyr.com> Date: Thu, 01 Oct 1998 16:36:49 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: flumiani@infotech.it CC: freebsd-net@FreeBSD.ORG Subject: Re: sendmail ups the line? References: <3.0.6.32.19981001103149.007b7450@pop> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org flumiani@infotech.it wrote: > I use a FredBSD box as a gateway to connect a LAN to Internet. To do this, > i followed the PPP Primer. > > WHAT HAPPENS: > If the PPP is working in the background (command ppp -auto -alias > ips_connect_script) everytime an e-mail client as Eudora Light (also Elm on > the same FreeBSD system) sends a message to local address (the same for non > local addresses) makes the sendmail do a DNS request to identify the IP of > the client's box. Becouse DNS is not on the LAN but on the internet, ppp > dials out. > > I tryed to avoid this action programming sendmail.cf but nothing. Next my > LAN, FreeBSD box configuration. Can someone help me? Setup a cache-only nameserver on your FreeBSD machine, and make it the "resolver" for your FreeBSD machine and all of your clients. Setup your ISP nameserver as a forwarder for this nameserver. Another, perhaps better option, is to become a secondary for your own domain; this is how I operate. The comments in /etc/namedb/named.boot will be helpful in setting up a secondary nameserver. This way, whenever you make a DNS query that has already been answered before (and hasn't timed out) it will be answered from your local DNS cache. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@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 Oct 1 16:33:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25468 for freebsd-net-outgoing; Thu, 1 Oct 1998 16:33:47 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA25463 for ; Thu, 1 Oct 1998 16:33:44 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id QAA26472; Thu, 1 Oct 1998 16:32:45 -0700 (PDT) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA01041; Thu, 1 Oct 1998 16:32:44 -0700 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id RAA05456; Thu, 1 Oct 1998 17:32:43 -0600 Message-ID: <3614111B.730F432@softweyr.com> Date: Thu, 01 Oct 1998 17:32:43 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: "Juan L. Freniche" , FreeBSD Net Subject: Re: ZNYX and writing/reading LL frames References: <36132F32.2D81@acm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Juan L. Freniche wrote: > > > 5 How to write link-layer frames? The application will write the > complete frame, including the first 14 bytes. > ---> Still Open > > 6 How to read, in an exclusive way, link-layer frames? By exclusive I > mean that the application will receive the frame and that, given the > non-standard header (in particular, the EtherType), that frame must > not be passed to the network stack. > ---> Still Open You can read and write raw network frames using the bpf (Berkeley Packet Filter) device as outlined in another response. There are a few caveats, though. The bpf device is a shared-read device; if you don't want your custom frames getting handed up the network stack, you'd better use an EtherType that is not recognized by the networking code. You will probably want to look into the read-filtering capabilities to cut down on the number of read packets your code has to process. If you pick an unused EtherType and stick with it, it should be simple to filter out your packets from any others on the system, and to guarantee they will not be mistaken for IP (or IPX, or XNS, etc) packets. I'm working on a program that does something much like this right now. If you like, once I've got it tested (probably tomorrow or Monday) I can send you the source so you can see how the bpf related code works. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@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 Oct 1 17:02:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28756 for freebsd-net-outgoing; Thu, 1 Oct 1998 17:02:03 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from arcadia.a2000.nl (arcadia.a2000.nl [62.108.1.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28669 for ; Thu, 1 Oct 1998 17:01:58 -0700 (PDT) (envelope-from lamminen@cable.a2000.nl) Received: from cable.a2000.nl ([24.132.4.90]) by arcadia.a2000.nl (Netscape Mail Server v2.02) with ESMTP id AAA7982 for ; Fri, 2 Oct 1998 02:01:39 +0200 Message-ID: <361417F1.115469ED@cable.a2000.nl> Date: Fri, 02 Oct 1998 02:01:54 +0200 From: LITE solutions Organization: L amminen I nformation T echnology E ngineering X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en,nl MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: extremely slow and strange connection with cable modem and 3c509 Content-Type: multipart/mixed; boundary="------------E35FAAA441DBFD061DE5CE6B" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------E35FAAA441DBFD061DE5CE6B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi ! I hope anyone can help me out with this one. I have an ethernet link to a cable modem with a 3com 3c509 card. Under (blasted) windoze NT 4.0 workstation service pack 3 all works really fine. i get speeds up to 150 k / second tops and 30 k / second average. i installed FreeBSD version 2.2.6 (and a little later 2.2.7, but now back to 2.2.6 again due to shared-with-friend CDROM reasons) configured the network exactly like the NT configuration, but connection speeds are EXTREMELY slow, just starting at about 300 b/s (yes BYTE / second) rapidly dropping down to 100, 60, 20, STALLED (with netscape communicator 4.04 port). ping doesn't work at all, all packages are lost, and traceroute gives hop times of over 1900 ms. I bought the crab (TCP/IP network administration) book from O'Reilly's, after digging through Greg Lehey's really comprehensive Complete FreeBSD. I tried hard to figure out what is wrong, but i kind sort it out. I would really like to jumpstart with the net so i can learn the marvelous world of UNIX at much greater speed. If anyone can help me with this i would really jump in the air with joy:) If more configuration stuff is needed to give a solutions, i would be more than happy to provide this. thnx Lasse --------------E35FAAA441DBFD061DE5CE6B Content-Type: text/x-vcard; charset=us-ascii; name="lite.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for LITE solutions Content-Disposition: attachment; filename="lite.vcf" begin:vcard n:Lamminen;Lasse x-mozilla-html:TRUE org:LITE solutions adr: version:2.1 email;internet:lamminen@cable.a2000.nl fn:Lamminen, Lasse end:vcard --------------E35FAAA441DBFD061DE5CE6B-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 1 21:27:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25592 for freebsd-net-outgoing; Thu, 1 Oct 1998 21:27:07 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ha1.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25578 for ; Thu, 1 Oct 1998 21:27:05 -0700 (PDT) (envelope-from sw@home.com) Received: from home.com ([24.1.110.249]) by ha1.rdc1.sfba.home.com (Netscape Mail Server v2.02) with ESMTP id AAA23827; Thu, 1 Oct 1998 21:23:38 -0700 Message-ID: <36145574.ED1C7EB4@home.com> Date: Thu, 01 Oct 1998 21:24:20 -0700 From: Sanjay Waghray Reply-To: sw@home.com Organization: Sanjay Waghray X-Mailer: Mozilla 4.05 [en]C-AtHome0404 (WinNT; U) MIME-Version: 1.0 To: LITE solutions CC: freebsd-net@FreeBSD.ORG Subject: Re: extremely slow and strange connection with cable modem and 3c509 References: <361417F1.115469ED@cable.a2000.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What cable modem do you have? I have a cable modem set up with a 2.2.7 box and have been running fine for a long time now! In fact, I first installed 2.2.5 on this box via ftp from ftp.freebsd.org over the cable connection. I routinely get transfer rates (ftp from well connected sites) of 300-600 kbps. Until recently I'd been running on a 3C509 card; I have a Bay Networks LANCity modem. Please email me if you have any questions. Sanjay LITE solutions wrote: > > Hi ! > > I hope anyone can help me out with this one. > > I have an ethernet link to a cable modem with a 3com 3c509 card. > Under (blasted) windoze NT 4.0 workstation service pack 3 all works > really fine. > i get speeds up to 150 k / second tops and 30 k / second average. > > i installed FreeBSD version 2.2.6 (and a little later 2.2.7, but now > back to 2.2.6 again due to shared-with-friend CDROM reasons) > configured the network exactly like the NT configuration, but connection > speeds are EXTREMELY slow, just starting at about 300 b/s (yes BYTE / > second) rapidly dropping down to 100, 60, 20, STALLED (with netscape > communicator 4.04 port). > ping doesn't work at all, all packages are lost, and traceroute gives > hop times of over 1900 ms. > I bought the crab (TCP/IP network administration) book from O'Reilly's, > after digging through Greg Lehey's really comprehensive Complete > FreeBSD. I tried hard to figure out what is wrong, but i kind sort it > out. I would really like to jumpstart with the net so i can learn the > marvelous world of UNIX at much greater speed. > > If anyone can help me with this i would really jump in the air with > joy:) > > If more configuration stuff is needed to give a solutions, i would be > more than happy to provide this. > > thnx Lasse > > ------------------------------------------------------------------------ > > Lamminen, Lasse > LITE solutions > > Lamminen, Lasse > LITE solutions > HTML Mail > version:2.1 > Additional Information: > Last Name Lamminen > First Name Lasse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 2 07:45:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08252 for freebsd-net-outgoing; Fri, 2 Oct 1998 07:45:58 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from lodgenet.com (cline.lodgenet.com [204.124.122.251]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08246 for ; Fri, 2 Oct 1998 07:45:55 -0700 (PDT) (envelope-from lee.mckenna@lodgenet.com) Received: from chaplin.lodgenet.com (chaplin.lodgenet.com [10.0.104.215]) by lodgenet.com (8.7.5/8.7.3) with SMTP id JAA00451 for ; Fri, 2 Oct 1998 09:45:28 -0500 Received: by chaplin.lodgenet.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52) id <01BDEDE9.852ACEE0@chaplin.lodgenet.com>; Fri, 2 Oct 1998 09:46:25 -0500 Message-ID: From: "McKenna, Lee" To: "'sw@home.com'" , "'LITE solutions'" Cc: "'freebsd-net@FreeBSD.ORG'" Subject: RE: extremely slow and strange connection with cable modem and 3c509 Date: Fri, 2 Oct 1998 09:46:23 -0500 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52 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 2.2.7 with a Dec "tulip" ethernet card, and a Bay Networks LANCity cable modem. I installed 2.2.7 across the net using ftp option, and it flew -- peak transfer rates of 120KB/s (KiloBytes!). It continues to perform well. This doesnt really offer you much help, hearing about another success story :) Maybe barking up the wrong tree, but perhaps your problem is related to an MTU size issue? Although, with my configuration, it worked "out of the box" with no tweaking of the ifconfig parameters... Try a different brand/model of enet card if you can...big hammer approach, but it quickly helps narrow the list of suspects... --Lee McKenna lee.mckenna@lodgenet.com -----Original Message----- From: Sanjay Waghray [mailto:sw@home.com] Sent: Thursday, October 01, 1998 11:24 PM To: LITE solutions Cc: freebsd-net@FreeBSD.ORG Subject: Re: extremely slow and strange connection with cable modem and 3c509 What cable modem do you have? I have a cable modem set up with a 2.2.7 box and have been running fine for a long time now! In fact, I first installed 2.2.5 on this box via ftp from ftp.freebsd.org over the cable connection. I routinely get transfer rates (ftp from well connected sites) of 300-600 kbps. Until recently I'd been running on a 3C509 card; I have a Bay Networks LANCity modem. Please email me if you have any questions. Sanjay LITE solutions wrote: > > Hi ! > > I hope anyone can help me out with this one. > > I have an ethernet link to a cable modem with a 3com 3c509 card. > Under (blasted) windoze NT 4.0 workstation service pack 3 all works > really fine. > i get speeds up to 150 k / second tops and 30 k / second average. > > i installed FreeBSD version 2.2.6 (and a little later 2.2.7, but now > back to 2.2.6 again due to shared-with-friend CDROM reasons) > configured the network exactly like the NT configuration, but connection > speeds are EXTREMELY slow, just starting at about 300 b/s (yes BYTE / > second) rapidly dropping down to 100, 60, 20, STALLED (with netscape > communicator 4.04 port). > ping doesn't work at all, all packages are lost, and traceroute gives > hop times of over 1900 ms. > I bought the crab (TCP/IP network administration) book from O'Reilly's, > after digging through Greg Lehey's really comprehensive Complete > FreeBSD. I tried hard to figure out what is wrong, but i kind sort it > out. I would really like to jumpstart with the net so i can learn the > marvelous world of UNIX at much greater speed. > > If anyone can help me with this i would really jump in the air with > joy:) > > If more configuration stuff is needed to give a solutions, i would be > more than happy to provide this. > > thnx Lasse > > ------------------------------------------------------------------------ > > Lamminen, Lasse > LITE solutions > > Lamminen, Lasse > LITE solutions > HTML Mail > version:2.1 > Additional Information: > Last Name Lamminen > First Name Lasse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 3 00:04:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08514 for freebsd-net-outgoing; Sat, 3 Oct 1998 00:04:45 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from dt041n6f.san.rr.com (dt041n6f.san.rr.com [204.210.28.111]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08507 for ; Sat, 3 Oct 1998 00:04:43 -0700 (PDT) (envelope-from gvb@tns.net) Received: from gvb ([192.168.0.3]) by dt041n6f.san.rr.com (8.9.1a/Rectum? It almost killed em!) with SMTP id AAA19849 for ; Sat, 3 Oct 1998 00:04:18 -0700 (PDT) Message-Id: <4.1.19981003000534.009434b0@mail.tns.net> X-Sender: gvb@mail.tns.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 03 Oct 1998 00:07:37 -0700 To: freebsd-net@FreeBSD.ORG From: GVB Subject: simple port forwarding.. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Question, A NAT machine with two network cards, one for the internet, one for the internal LAN running on the 192.168. network. How do I setup port forwarding on the server so that things like quickcams can be used in stuff like VDOPhone or Netmeeting. I tryed ssh tunneling but it didnt seem to work correctly. From what I could tell certian softwares use different ports for this kind of thing. Any help is appriciated as always. GVB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 3 10:04:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25786 for freebsd-net-outgoing; Sat, 3 Oct 1998 10:04:07 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from sundance.KKS.net (sundance.KKS.net [212.62.128.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25778 for ; Sat, 3 Oct 1998 10:04:02 -0700 (PDT) (envelope-from andy@mail.kks.net) Received: from atechnet4.kks.net (cm-33.rot.KKS.net [212.62.129.33]) by sundance.KKS.net (8.8.8/8.8.8/19980312) with SMTP id TAA12586 for ; Sat, 3 Oct 1998 19:03:37 +0200 Message-Id: <199810031703.TAA12586@sundance.KKS.net> X-Sender: rozmanal@164.8.8.5 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 03 Oct 1998 16:44:16 +0100 To: freebsd-net@FreeBSD.ORG From: Aleksander Rozman - Andy Subject: Internet problem Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi ! I am new to this list (and to FreeBSD) and I need little help. Recently I got cable modem to get internet access over cable TV. I have more than one computer so I decided to create a FreeBSD server to give access to all of my computer and also to be able to have http server. But here I have one problem. I can make server (AC1) have contact with Inet through cable modem, I can also access AC1 from my other computers (AC2, AC4), but I cannot access Internet from AC2, or AC4. ********************************************************** ** FreeBSD Server Ethernet 1 (212.62.129.33) ** -----> Internet (cable ** Ethernet 2 (192.168.44.1) ---- modem network) ____________________________________________________| | | AC2 AC4 192.168.44.2 192.169.44.4 AC2/4 have both set gateway to 192.168.44.1 (second eth card on AC1), and AC1 has default gateway that shows to my ISP server (cable modem connects all users into one big network). I don't know how to set that everytime I send reuqest for internet AC1 should give my LAN access to it. I know that my description is little weird, but I hope you will understand it and help me. Andy ************************************************************************** * Aleksander Rozman - Andy * Member of: E2:EA, E2F, SAABer, Trekkie, * * aleksander.rozman@uni-mb.si * X-Phile, Heller's angel, True's screamer,* * andy@quixotic.org * True's Trooper, Questie, Legacy, PO5. * * Maribor, Slovenia (Europe) ******************************************** * ICQ-UIC: 4911125 * http://quixotic.org/~andy/ * * PGP key available * http://tferi4.uni-mb.si/~rozmanal/ * ************************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 3 17:37:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27307 for freebsd-net-outgoing; Sat, 3 Oct 1998 17:37:02 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27285 for ; Sat, 3 Oct 1998 17:37:00 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id UAA13095 for ; Sat, 3 Oct 1998 20:27:12 -0400 (EDT) Date: Sat, 3 Oct 1998 20:38:31 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: freebsd-net@FreeBSD.ORG Subject: Re: Is PPP now being used by all 3 *BSD's? 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 ACK! I posted this to -hackers on accident it should of gone here. I got off my ass and am writing an article for Dameon News on creating a dial on demand ppp router for small ofices and lans and had "FreeBSD" strewn throughout but decided I would rather use "*BSD" instead to show a more united front and attempt to include everyone. But I didnt know if all 3 are using the brian's ppp work? I assume so but I wanted to know for sure. Anyone? Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." -Wes Peters ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.7 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message