From owner-freebsd-net Sun Nov 5 13:40:50 2000 Delivered-To: freebsd-net@freebsd.org Received: from tomts8-srv.bellnexxia.net (tomts8.bellnexxia.net [209.226.175.52]) by hub.freebsd.org (Postfix) with ESMTP id C270437B479 for ; Sun, 5 Nov 2000 13:40:48 -0800 (PST) Received: from johnny5 ([64.229.34.151]) by tomts8-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20001105214047.OKFY625.tomts8-srv.bellnexxia.net@johnny5>; Sun, 5 Nov 2000 16:40:47 -0500 Message-ID: <000801c04770$84014980$0100000a@johnny5> Reply-To: "John Telford" From: "John Telford" To: "Julian Elischer" Cc: References: <001501c0453e$c0d00100$0100000a@johnny5> <3A047E22.5C320AA1@elischer.org> Subject: Re: Tips, How-To on VPN ? Date: Sun, 5 Nov 2000 16:36:53 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > John Telford wrote: > > > > Hi, > > Am I on the right track here ? > > Here's the scenario: > > 2 locations with the same ISP, on the same public subnet. > > Each firewalled with a 4.1.1 box. > > > > Macs and PC's need access to Mac and NT servers in both directions. > > > > Is a vpn/pptp the way to go here ? > > Pointers to resources and tutorials would be greatly appreciated. > > Thanks in advance, John. > > > > > > you could use mpd-netgraph (in ports/net) with pptp > > julian > -- > with "unsubscribe freebsd-net" in the body of the message Thanks, I came across this: http://www.freebsddiary.org/pipsecd.html Anyone else used pipesecd, comments ? ,John. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 14: 4:48 2000 Delivered-To: freebsd-net@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id D4AE537B4CF for ; Sun, 5 Nov 2000 14:04:45 -0800 (PST) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id OAA24207 for ; Sun, 5 Nov 2000 14:02:44 -0800 (PST) Message-Id: <200011052202.OAA24207@implode.root.com> To: freebsd-net@freebsd.org Subject: tcp sendspace/recvspace From: David Greenman Reply-To: dg@root.com Date: Sun, 05 Nov 2000 14:02:44 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been messing around with the net.inet.tcp.sendspace and net.inet.tcp.recvspace parameters on ftp.freesoftware.com and have found that there is a significant performance improvement when increasing these to 32768 bytes. Apparantly there are enough systems out there with higher window maxes that it really does make a difference. By significant improvement, I mean about a average of a 20% increase in Mbps per user, and this was just the change over a 30 minute period with lots of connections still using the old 16K values. Any objections to increasing the defaults in FreeBSD to 32K? -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 14:12: 3 2000 Delivered-To: freebsd-net@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 03EB837B479 for ; Sun, 5 Nov 2000 14:12:01 -0800 (PST) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 459AB5E89; Sun, 5 Nov 2000 23:11:59 +0100 (CET) Date: Sun, 5 Nov 2000 23:11:59 +0100 (CET) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: David Greenman Cc: freebsd-net@freebsd.org Subject: Re: tcp sendspace/recvspace In-Reply-To: <200011052202.OAA24207@implode.root.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 > I've been messing around with the net.inet.tcp.sendspace and > net.inet.tcp.recvspace parameters on ftp.freesoftware.com and have found > that there is a significant performance improvement when increasing these > to 32768 bytes. Apparantly there are enough systems out there with higher > window maxes that it really does make a difference. By significant > improvement, I mean about a average of a 20% increase in Mbps per user, > and this was just the change over a 30 minute period with lots of connections > still using the old 16K values. > Any objections to increasing the defaults in FreeBSD to 32K? I actually wanted to suggest the same some time ago. Some time ago I was trying to find out why a certain Linux box can download at much higher speed over a satellite link than a FreeBSD box. Well, the default TCP window size in Linux is higher. Increasing it on FreeBSD, more than doubled the transfer speed. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 14:24:40 2000 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 49E8737B4CF for ; Sun, 5 Nov 2000 14:24:38 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eA5MOXv25962; Sun, 5 Nov 2000 14:24:33 -0800 (PST) Date: Sun, 5 Nov 2000 14:24:33 -0800 From: Alfred Perlstein To: David Greenman Cc: freebsd-net@FreeBSD.ORG Subject: Re: tcp sendspace/recvspace Message-ID: <20001105142433.K5112@fw.wintelcom.net> References: <200011052202.OAA24207@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200011052202.OAA24207@implode.root.com>; from dg@root.com on Sun, Nov 05, 2000 at 02:02:44PM -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * David Greenman [001105 14:05] wrote: > I've been messing around with the net.inet.tcp.sendspace and > net.inet.tcp.recvspace parameters on ftp.freesoftware.com and have found > that there is a significant performance improvement when increasing these > to 32768 bytes. Apparantly there are enough systems out there with higher > window maxes that it really does make a difference. By significant > improvement, I mean about a average of a 20% increase in Mbps per user, > and this was just the change over a 30 minute period with lots of connections > still using the old 16K values. > Any objections to increasing the defaults in FreeBSD to 32K? No objection, just a suggestion that perhaps it should be set when booting and determined by the amount of ram in the machine. Just setting it 32k would also work. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 14:29:20 2000 Delivered-To: freebsd-net@freebsd.org Received: from overlord.e-gerbil.net (e-gerbil.net [207.91.110.247]) by hub.freebsd.org (Postfix) with ESMTP id F30F537B479 for ; Sun, 5 Nov 2000 14:29:17 -0800 (PST) Received: by overlord.e-gerbil.net (Postfix, from userid 1001) id 74236E4EB9; Sun, 5 Nov 2000 17:29:14 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by overlord.e-gerbil.net (Postfix) with ESMTP id 60399E4EB8; Sun, 5 Nov 2000 17:29:14 -0500 (EST) Date: Sun, 5 Nov 2000 17:29:14 -0500 (EST) From: "Richard A. Steenbergen" To: David Greenman Cc: freebsd-net@freebsd.org Subject: Re: tcp sendspace/recvspace In-Reply-To: <200011052202.OAA24207@implode.root.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 Sun, 5 Nov 2000, David Greenman wrote: > I've been messing around with the net.inet.tcp.sendspace and > net.inet.tcp.recvspace parameters on ftp.freesoftware.com and have found > that there is a significant performance improvement when increasing these > to 32768 bytes. Apparantly there are enough systems out there with higher > window maxes that it really does make a difference. By significant > improvement, I mean about a average of a 20% increase in Mbps per user, > and this was just the change over a 30 minute period with lots of connections > still using the old 16K values. > Any objections to increasing the defaults in FreeBSD to 32K? One of the projects I've been working on in my spare time is an implimentation of auto-tuning the socket buffers based on feedback from the tcp congestion window. Remember that these numbers don't actually allocate any memory and there are no pools, but mearly set an allocation limit. Any situation where an artifically advertised TCP window based on a non-existant memory limitation is keeping the number of packets allowed in flight below what would be permitted by the cwnd is probably a bad thing for performance, at least on high latency high bandwidth connections. The only time you will see memory actually allocated in these buffers is during packet loss recovery, when data in flight is being buffered while awaiting a retransmission. It is relatively straight forward to instead set a fixed limit of amount of memory which can be allocated for this task on a system and per user basis, and then intelligently share this among the tcp connections in question. I believe this will be a much better system in the long run. BTW a blanket 32k in both directions, while not an outright bad idea, is not optimal and probably overly wasteful. In most cases you can achieve your increased thruput by setting the recv buffer higher without needing to make the sendbuf match, but the numbers you're looking for are probably closet to 65535 without rfc1323 window scaling or at least 256k with, in order to get optimal thruput. You can obviously see problems coming from this. Among other things its just plain stupid, not every connection needs the memory it just needs the potential for the memory for any given connection at any given time, and you open yourself to mbuf exhaustion and various forms of attacks by trying to achieve that with blanket numbers. But while sticking with the existing system, turning up the socket buffers in applications like ftp w/setsockopt() is not a bad idea. :P -- Richard A Steenbergen http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 14:59:34 2000 Delivered-To: freebsd-net@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id C5BC937B4C5 for ; Sun, 5 Nov 2000 14:59:31 -0800 (PST) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id OAA24410; Sun, 5 Nov 2000 14:57:28 -0800 (PST) Message-Id: <200011052257.OAA24410@implode.root.com> To: "Richard A. Steenbergen" Cc: freebsd-net@freebsd.org Subject: Re: tcp sendspace/recvspace In-reply-to: Your message of "Sun, 05 Nov 2000 17:29:14 EST." From: David Greenman Reply-To: dg@root.com Date: Sun, 05 Nov 2000 14:57:28 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >BTW a blanket 32k in both directions, while not an outright bad idea, is >not optimal and probably overly wasteful. In most cases you can achieve >your increased thruput by setting the recv buffer higher without needing >to make the sendbuf match, but the numbers you're looking for are probably >closet to 65535 without rfc1323 window scaling or at least 256k with, in >order to get optimal thruput. You can obviously see problems coming from >this. Among other things its just plain stupid, not every connection needs >the memory it just needs the potential for the memory for any given >connection at any given time, and you open yourself to mbuf exhaustion and >various forms of attacks by trying to achieve that with blanket numbers. Uh, the negotiated window maximum is the lower of the receiver's advertised window and the sender's congestion window, so both sides must cooperate for a larger window to be used. Since FreeBSD is used as both a client and server platform, I feel it is important to increase both recvspace and sendspace. Overall I like the idea of a dynamically scaling these, but I'm talking about the "right now" and not the "next year some time, maybe". I am concerned about the increased memory use in some applications, but memory is cheap these days and getting cheaper. Really the only issue I see is that some people may not be prepared to tune there kernel configs to allow for the increased network buffer use. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 15:11: 8 2000 Delivered-To: freebsd-net@freebsd.org Received: from overlord.e-gerbil.net (e-gerbil.net [207.91.110.247]) by hub.freebsd.org (Postfix) with ESMTP id 1E48237B4CF for ; Sun, 5 Nov 2000 15:11:06 -0800 (PST) Received: by overlord.e-gerbil.net (Postfix, from userid 1001) id DDFADE4EB9; Sun, 5 Nov 2000 18:11:02 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by overlord.e-gerbil.net (Postfix) with ESMTP id 8E3F4E4EB8; Sun, 5 Nov 2000 18:11:02 -0500 (EST) Date: Sun, 5 Nov 2000 18:11:02 -0500 (EST) From: "Richard A. Steenbergen" To: David Greenman Cc: freebsd-net@freebsd.org Subject: Re: tcp sendspace/recvspace In-Reply-To: <200011052257.OAA24410@implode.root.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 Sun, 5 Nov 2000, David Greenman wrote: > Uh, the negotiated window maximum is the lower of the receiver's advertised > window and the sender's congestion window, so both sides must cooperate for > a larger window to be used. Since FreeBSD is used as both a client and server > platform, I feel it is important to increase both recvspace and sendspace. Not really. Cooperation on both sides is not totally necessary, as the senders congestion window does not depend on the senders sendbuf. A larger sendbuf is only necessary in the face of packet loss recovery. Which is not to say that this isn't valuable and improves performance, but you'll still get your performance gain with only receiver side cooperation. The numbers you're looking for sendbuf wise are at least 2*cwnd. You should take a look at a paper on the subject from SIGCOMM 98, at http://www.psc.edu/networking/papers/auto_abstract.html and the implementation for NetBSD that they have done (as well as other interesting projects) at http://www.psc.edu/networking/research.html. I wouldn't recommend copying their implementation exactly, but they have interesting numbers and graphs on the subject. > Overall I like the idea of a dynamically scaling these, but I'm talking > about the "right now" and not the "next year some time, maybe". I am concerned > about the increased memory use in some applications, but memory is cheap > these days and getting cheaper. Really the only issue I see is that some > people may not be prepared to tune there kernel configs to allow for the > increased network buffer use. Memory isn't the issue, kernel memory is the issue, as well as behavior in the face of network outages. -- Richard A Steenbergen http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 16:59:53 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.rdc2.pa.home.com (ha2.rdc2.pa.home.com [24.12.106.195]) by hub.freebsd.org (Postfix) with ESMTP id 3AAD337B4CF for ; Sun, 5 Nov 2000 16:59:51 -0800 (PST) Received: from home.com ([24.40.47.120]) by mail.rdc2.pa.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001106005950.UZLT15714.mail.rdc2.pa.home.com@home.com> for ; Sun, 5 Nov 2000 16:59:50 -0800 Message-ID: <3A0602C0.B0D3FC58@home.com> Date: Sun, 05 Nov 2000 20:00:48 -0500 From: Peter Schwenk X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: Getting Lucent Orinoco Silver Card Working References: <3A039EFD.A45F01B8@softweyr.com> <20001104184309.A10492@peorth.iteration.net> <3A04B99A.4B3AA866@home.com> <3A04C8A3.51C9A034@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Don't worry, I still use FreeBSD for other, more important stuff. Lucent wrote the Linux Orinoco driver, so I figured it had the best chance of working well. Wes Peters wrote: > Peter Schwenk wrote: > > > > Being impatient, I decided to use Linux for the gateway box. Lucent has a driver > > based on a provided library which supports all of the card's functions. > > Clever. Instead of simply fixing the configuration, you broke the operating > system. > > -- > Where am I, and what am I doing in this handbasket? > > Wes Peters wes@softweyr.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 17:12:47 2000 Delivered-To: freebsd-net@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id DAAED37B4C5 for ; Sun, 5 Nov 2000 17:12:44 -0800 (PST) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id RAA24642; Sun, 5 Nov 2000 17:10:41 -0800 (PST) Message-Id: <200011060110.RAA24642@implode.root.com> To: "Richard A. Steenbergen" Cc: freebsd-net@freebsd.org Subject: Re: tcp sendspace/recvspace In-reply-to: Your message of "Sun, 05 Nov 2000 18:11:02 EST." From: David Greenman Reply-To: dg@root.com Date: Sun, 05 Nov 2000 17:10:40 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Sun, 5 Nov 2000, David Greenman wrote: > >> Uh, the negotiated window maximum is the lower of the receiver's advertised >> window and the sender's congestion window, so both sides must cooperate for >> a larger window to be used. Since FreeBSD is used as both a client and server >> platform, I feel it is important to increase both recvspace and sendspace. > >Not really. Cooperation on both sides is not totally necessary, as the >senders congestion window does not depend on the senders sendbuf. A larger >sendbuf is only necessary in the face of packet loss recovery. Which is >not to say that this isn't valuable and improves performance, but you'll >still get your performance gain with only receiver side cooperation. The >numbers you're looking for sendbuf wise are at least 2*cwnd. This just doesn't jive with my memory on this subject. The socket send queue is limited by tcp_sendspace. How can a server have packets in-flight that are outside of the scope of that? In other words, I don't see how an infinitely large receive window is going to get you anything if the server's tcp_sendspace restricts how much data can be buffered in the socket. Clearly you can't discard the data in the socket, moving the window forward, until the receiver's ack for it has been received, so how can you have more data in flight than is buffered in the socket? I guess I really just don't understand the point you're trying to make and I wonder if we're really talking about the same issue? >You should take a look at a paper on the subject from SIGCOMM 98, at >http://www.psc.edu/networking/papers/auto_abstract.html and the >implementation for NetBSD that they have done (as well as other >interesting projects) at http://www.psc.edu/networking/research.html. I >wouldn't recommend copying their implementation exactly, but they have >interesting numbers and graphs on the subject. It's been awhile, but I have read the above paper. I haven't looked at the implementation in NetBSD, however. I'm not arguing that it isn't a good idea - I did say that I liked the idea. >> Overall I like the idea of a dynamically scaling these, but I'm talking >> about the "right now" and not the "next year some time, maybe". I am concerned >> about the increased memory use in some applications, but memory is cheap >> these days and getting cheaper. Really the only issue I see is that some >> people may not be prepared to tune their kernel configs to allow for the >> increased network buffer use. > >Memory isn't the issue, kernel memory is the issue, as well as behavior in >the face of network outages. Huh? Isn't that what I said? By "memory use in some applications", I was talking about applications of FreeBSD, not application programs. I tried to make that clear in the sentence that followed regarding kernel tuning for increased network buffer usage. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 17:23: 2 2000 Delivered-To: freebsd-net@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 137E337B4E5 for ; Sun, 5 Nov 2000 17:22:57 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eA61O1308796; Sun, 5 Nov 2000 17:24:01 -0800 (PST) (envelope-from kris) Date: Sun, 5 Nov 2000 17:24:00 -0800 From: Kris Kennaway To: David Greenman Cc: freebsd-net@FreeBSD.ORG Subject: Re: tcp sendspace/recvspace Message-ID: <20001105172400.A8778@citusc17.usc.edu> References: <200011052202.OAA24207@implode.root.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011052202.OAA24207@implode.root.com>; from dg@root.com on Sun, Nov 05, 2000 at 02:02:44PM -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 05, 2000 at 02:02:44PM -0800, David Greenman wrote: > I've been messing around with the net.inet.tcp.sendspace and=20 > net.inet.tcp.recvspace parameters on ftp.freesoftware.com and have found > that there is a significant performance improvement when increasing these > to 32768 bytes. Apparantly there are enough systems out there with higher > window maxes that it really does make a difference. By significant=20 > improvement, I mean about a average of a 20% increase in Mbps per user, > and this was just the change over a 30 minute period with lots of connect= ions > still using the old 16K values. > Any objections to increasing the defaults in FreeBSD to 32K? Won't this impact the latency of multiple connections over a slow PPP link? Kris --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoGCC8ACgkQWry0BWjoQKVnywCgtho5cl8IN9GDSp4ZntINW4Gx /WUAoO1tiCGIaHRy65auWQMM6cmq0VZN =1a/M -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 17:36:20 2000 Delivered-To: freebsd-net@freebsd.org Received: from overlord.e-gerbil.net (e-gerbil.net [207.91.110.247]) by hub.freebsd.org (Postfix) with ESMTP id A602E37B4CF; Sun, 5 Nov 2000 17:36:17 -0800 (PST) Received: by overlord.e-gerbil.net (Postfix, from userid 1001) id 2CB9DE4EB9; Sun, 5 Nov 2000 20:36:14 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by overlord.e-gerbil.net (Postfix) with ESMTP id 18689E4EB8; Sun, 5 Nov 2000 20:36:14 -0500 (EST) Date: Sun, 5 Nov 2000 20:36:14 -0500 (EST) From: "Richard A. Steenbergen" To: Kris Kennaway Cc: David Greenman , freebsd-net@FreeBSD.ORG Subject: Re: tcp sendspace/recvspace In-Reply-To: <20001105172400.A8778@citusc17.usc.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 Sun, 5 Nov 2000, Kris Kennaway wrote: > On Sun, Nov 05, 2000 at 02:02:44PM -0800, David Greenman wrote: > > I've been messing around with the net.inet.tcp.sendspace and > > net.inet.tcp.recvspace parameters on ftp.freesoftware.com and have found > > that there is a significant performance improvement when increasing these > > to 32768 bytes. Apparantly there are enough systems out there with higher > > window maxes that it really does make a difference. By significant > > improvement, I mean about a average of a 20% increase in Mbps per user, > > and this was just the change over a 30 minute period with lots of connections > > still using the old 16K values. > > Any objections to increasing the defaults in FreeBSD to 32K? > > Won't this impact the latency of multiple connections over a slow PPP link? Thats what the congestion window is for. Any limitation of transmits based on the advertised memory limitation window is totally improper. -- Richard A Steenbergen http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 17:56:17 2000 Delivered-To: freebsd-net@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id CB85237B4C5 for ; Sun, 5 Nov 2000 17:56:14 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eA61vM208907; Sun, 5 Nov 2000 17:57:22 -0800 (PST) (envelope-from kris) Date: Sun, 5 Nov 2000 17:57:22 -0800 From: Kris Kennaway To: "Richard A. Steenbergen" Cc: David Greenman , freebsd-net@FreeBSD.ORG Subject: Re: tcp sendspace/recvspace Message-ID: <20001105175722.A8886@citusc17.usc.edu> References: <20001105172400.A8778@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ras@e-gerbil.net on Sun, Nov 05, 2000 at 08:36:14PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 05, 2000 at 08:36:14PM -0500, Richard A. Steenbergen wrote: > On Sun, 5 Nov 2000, Kris Kennaway wrote: >=20 > > On Sun, Nov 05, 2000 at 02:02:44PM -0800, David Greenman wrote: > > > I've been messing around with the net.inet.tcp.sendspace and=20 > > > net.inet.tcp.recvspace parameters on ftp.freesoftware.com and have fo= und > > > that there is a significant performance improvement when increasing t= hese > > > to 32768 bytes. Apparantly there are enough systems out there with hi= gher > > > window maxes that it really does make a difference. By significant=20 > > > improvement, I mean about a average of a 20% increase in Mbps per use= r, > > > and this was just the change over a 30 minute period with lots of con= nections > > > still using the old 16K values. > > > Any objections to increasing the defaults in FreeBSD to 32K? > >=20 > > Won't this impact the latency of multiple connections over a slow PPP l= ink? >=20 > Thats what the congestion window is for. Any limitation of transmits based > on the advertised memory limitation window is totally improper. Perhaps it was a bug, but I used to see e.g. FTP transfers which were running at full speed totally monopolizing my modem bandwidth (then a 14.4k), and other sessions not being able to receive their "fair share". Tweaking net.inet.tcp.recvspace to give only a second or two worth of data transfer reduced the latency to acceptable levels. Maybe this has been fixed by now - I haven't noticed it since I upgraded to a 56k modem. I'll try increasing my system to 32768 and see if it has any effect. Kris --zhXaljGHf11kAtnf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoGEAIACgkQWry0BWjoQKXcwQCgq/gqLgX+Ww9vFeIvniPG6Zwi ROoAoL+42nSzUBaCTnHWVpOTJb5lugyQ =CG2d -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 18: 1: 7 2000 Delivered-To: freebsd-net@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id 7691537B4D7 for ; Sun, 5 Nov 2000 18:01:04 -0800 (PST) Received: (qmail 40263 invoked by uid 1000); 6 Nov 2000 02:01:03 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Nov 2000 02:01:03 -0000 Date: Sun, 5 Nov 2000 20:01:03 -0600 (CST) From: Mike Silbersack To: Kris Kennaway Cc: "Richard A. Steenbergen" , David Greenman , freebsd-net@FreeBSD.ORG Subject: Re: tcp sendspace/recvspace In-Reply-To: <20001105175722.A8886@citusc17.usc.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 Sun, 5 Nov 2000, Kris Kennaway wrote: > Perhaps it was a bug, but I used to see e.g. FTP transfers which were > running at full speed totally monopolizing my modem bandwidth (then a > 14.4k), and other sessions not being able to receive their "fair > share". Tweaking net.inet.tcp.recvspace to give only a second or two > worth of data transfer reduced the latency to acceptable levels. > > Maybe this has been fixed by now - I haven't noticed it since I > upgraded to a 56k modem. I'll try increasing my system to 32768 > and see if it has any effect. > > Kris Isn't that more related to the length of the interface queue for PPP? I think Archie tweaked it (or was going to) when he changed how packets overflowing the queue are handled. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 18: 2: 8 2000 Delivered-To: freebsd-net@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id 81A6737B4CF for ; Sun, 5 Nov 2000 18:02:04 -0800 (PST) Received: (qmail 40273 invoked by uid 1000); 6 Nov 2000 02:02:03 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Nov 2000 02:02:03 -0000 Date: Sun, 5 Nov 2000 20:02:03 -0600 (CST) From: Mike Silbersack To: Kris Kennaway Cc: "Richard A. Steenbergen" , David Greenman , freebsd-net@FreeBSD.ORG Subject: Re: tcp sendspace/recvspace 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, 5 Nov 2000, Mike Silbersack wrote: > Isn't that more related to the length of the interface queue for PPP? I > think Archie tweaked it (or was going to) when he changed how packets > overflowing the queue are handled. > > Mike "Silby" Silbersack Ignore me, sending != recieving. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 18: 8: 7 2000 Delivered-To: freebsd-net@freebsd.org Received: from overlord.e-gerbil.net (e-gerbil.net [207.91.110.247]) by hub.freebsd.org (Postfix) with ESMTP id 2691237B4C5; Sun, 5 Nov 2000 18:08:04 -0800 (PST) Received: by overlord.e-gerbil.net (Postfix, from userid 1001) id 67241E4EB9; Sun, 5 Nov 2000 21:08:00 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by overlord.e-gerbil.net (Postfix) with ESMTP id 52EAEE4EB8; Sun, 5 Nov 2000 21:08:00 -0500 (EST) Date: Sun, 5 Nov 2000 21:08:00 -0500 (EST) From: "Richard A. Steenbergen" To: Kris Kennaway Cc: David Greenman , freebsd-net@FreeBSD.ORG Subject: Re: tcp sendspace/recvspace In-Reply-To: <20001105175722.A8886@citusc17.usc.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 Sun, 5 Nov 2000, Kris Kennaway wrote: > Perhaps it was a bug, but I used to see e.g. FTP transfers which were > running at full speed totally monopolizing my modem bandwidth (then a > 14.4k), and other sessions not being able to receive their "fair > share". Tweaking net.inet.tcp.recvspace to give only a second or two > worth of data transfer reduced the latency to acceptable levels. > > Maybe this has been fixed by now - I haven't noticed it since I > upgraded to a 56k modem. I'll try increasing my system to 32768 > and see if it has any effect. Interesting... Most likely thats just the effect of having a slow speed link which takes a long time to serialize data. Especially if you have large packets, they will monopolize the time on the link and make interactive sessions painfully sluggish. This is where WFQ comes in handy. Sounds like what you were doing was intentionally tuning down the performance to sub-optimal so that it wouldn't be lagged. Intelligent queueing seems like a better solution, but turning the socket buffer to 32768 should have no negative impact. -- Richard A Steenbergen http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 18:30:43 2000 Delivered-To: freebsd-net@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id C2B7637B479 for ; Sun, 5 Nov 2000 18:30:40 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eA62VgM09027; Sun, 5 Nov 2000 18:31:42 -0800 (PST) (envelope-from kris) Date: Sun, 5 Nov 2000 18:31:42 -0800 From: Kris Kennaway To: Mike Silbersack Cc: "Richard A. Steenbergen" , David Greenman , freebsd-net@FreeBSD.ORG Subject: Re: tcp sendspace/recvspace Message-ID: <20001105183142.A9009@citusc17.usc.edu> References: <20001105175722.A8886@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from silby@silby.com on Sun, Nov 05, 2000 at 08:01:03PM -0600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 05, 2000 at 08:01:03PM -0600, Mike Silbersack wrote: >=20 > On Sun, 5 Nov 2000, Kris Kennaway wrote: >=20 > > Perhaps it was a bug, but I used to see e.g. FTP transfers which were > > running at full speed totally monopolizing my modem bandwidth (then a > > 14.4k), and other sessions not being able to receive their "fair > > share". Tweaking net.inet.tcp.recvspace to give only a second or two > > worth of data transfer reduced the latency to acceptable levels. > >=20 > > Maybe this has been fixed by now - I haven't noticed it since I > > upgraded to a 56k modem. I'll try increasing my system to 32768 > > and see if it has any effect. > >=20 > > Kris >=20 > Isn't that more related to the length of the interface queue for PPP? I > think Archie tweaked it (or was going to) when he changed how packets > overflowing the queue are handled. Could well be. Kris --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoGGA0ACgkQWry0BWjoQKWtIwCgg+XfFf5WjLvtWwuXo41w3YiM 2sMAoIpY/FOth/GMoVOEWPdzEapPdYDg =cpBo -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 5 18:31:17 2000 Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 793FB37B479 for ; Sun, 5 Nov 2000 18:31:14 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13sc4d-0000Kk-00; Sun, 05 Nov 2000 19:31:51 -0700 Message-ID: <3A061817.E6EF7928@softweyr.com> Date: Sun, 05 Nov 2000 19:31:51 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Schwenk Cc: freebsd-net@freebsd.org Subject: Re: Getting Lucent Orinoco Silver Card Working References: <3A039EFD.A45F01B8@softweyr.com> <20001104184309.A10492@peorth.iteration.net> <3A04B99A.4B3AA866@home.com> <3A04C8A3.51C9A034@softweyr.com> <3A0602C0.B0D3FC58@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Schwenk wrote: > > Don't worry, I still use FreeBSD for other, more important stuff. Lucent wrote the > Linux Orinoco driver, so I figured it had the best chance of working well. Then you don't know vendor device-driver writers very well. I do, I used to be one. ;^) -- "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 Mon Nov 6 2:33:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from bart.esiee.fr (bart.esiee.fr [147.215.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 2CBA537B479 for ; Mon, 6 Nov 2000 02:33:49 -0800 (PST) Received: (from bonnetf@localhost) by bart.esiee.fr (8.11.1/8.11.1) id eA6AXb804873; Mon, 6 Nov 2000 11:33:38 +0100 (MET) From: Frank Bonnet Message-Id: <200011061033.eA6AXb804873@bart.esiee.fr> Subject: Re: tcp sendspace/recvspace To: blaz@amis.net Date: Mon, 06 Nov 2000 11:33:37 MET Cc: dg@root.com, freebsd-net@FreeBSD.ORG In-Reply-To: ; from "Blaz Zupan" at Nov 5, 2000 11:11 pm X-Mailer: Elm [revision: 212.5] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > I've been messing around with the net.inet.tcp.sendspace and > > net.inet.tcp.recvspace parameters on ftp.freesoftware.com and have found > > that there is a significant performance improvement when increasing these > > to 32768 bytes. Apparantly there are enough systems out there with higher > > window maxes that it really does make a difference. By significant > > improvement, I mean about a average of a 20% increase in Mbps per user, > > and this was just the change over a 30 minute period with lots of connections > > still using the old 16K values. > > Any objections to increasing the defaults in FreeBSD to 32K? > > I actually wanted to suggest the same some time ago. Some time ago I was > trying to find out why a certain Linux box can download at much higher speed > over a satellite link than a FreeBSD box. Well, the default TCP window size in > Linux is higher. Increasing it on FreeBSD, more than doubled the transfer > speed. I've applied THIS modification on our proxy/cache server running FreeBSD 4.1.1 and Squid, it seems performances are much better for web access and downloads ( sorry for my bad english ...) Any help from FreeBSD-Net gurus to "tune" a web proxy-cache machine would be very much appreciated , any web pointers too. The machine hasn't any ppp link only LAN access ( ethernet ) Thanks a lot -- Frank Bonnet Groupe ESIEE Paris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 6 13: 6:32 2000 Delivered-To: freebsd-net@freebsd.org Received: from virtual.sysadmin-inc.com (lists.sysadmin-inc.com [209.16.228.140]) by hub.freebsd.org (Postfix) with ESMTP id C332337B479 for ; Mon, 6 Nov 2000 13:06:24 -0800 (PST) Received: from 98wkst ([209.16.228.146]) by virtual.sysadmin-inc.com (8.9.1/8.9.1) with SMTP id QAA22396 for ; Mon, 6 Nov 2000 16:07:20 -0500 Reply-To: From: "Peter Brezny" To: Subject: mpd-netgraph giving page fault on exit Date: Mon, 6 Nov 2000 16:06:20 -0500 Message-ID: <001b01c04835$6a137320$92e410d1@sysadmininc.com> 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 CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When starting and stopping mpd on a 4.1 release box before any vpn connections have been made using the mpd.conf.sample's pptp conf, I have no problems. After a MS pptp connection has been made and then closed from the client end, typing q [enter] at the console running mpd causes the machine to lock up and auto reboot giving the message... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 etc. any advice is appreciated. Peter Brezny SysAdmin Services, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 6 14:52:51 2000 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 774EC37B479; Mon, 6 Nov 2000 14:52:34 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.0) with ESMTP id eA6MlsT02060; Mon, 6 Nov 2000 22:47:54 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eA6MmJT13763; Mon, 6 Nov 2000 22:48:19 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200011062248.eA6MmJT13763@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Richard A. Steenbergen" Cc: Kris Kennaway , David Greenman , freebsd-net@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: tcp sendspace/recvspace In-Reply-To: Message from "Richard A. Steenbergen" of "Sun, 05 Nov 2000 21:08:00 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Nov 2000 22:48:18 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sun, 5 Nov 2000, Kris Kennaway wrote: > > > Perhaps it was a bug, but I used to see e.g. FTP transfers which were > > running at full speed totally monopolizing my modem bandwidth (then a > > 14.4k), and other sessions not being able to receive their "fair > > share". Tweaking net.inet.tcp.recvspace to give only a second or two > > worth of data transfer reduced the latency to acceptable levels. > > > > Maybe this has been fixed by now - I haven't noticed it since I > > upgraded to a 56k modem. I'll try increasing my system to 32768 > > and see if it has any effect. > > Interesting... Most likely thats just the effect of having a slow speed > link which takes a long time to serialize data. Especially if you have > large packets, they will monopolize the time on the link and make > interactive sessions painfully sluggish. This is where WFQ comes in handy. > > Sounds like what you were doing was intentionally tuning down the > performance to sub-optimal so that it wouldn't be lagged. Intelligent > queueing seems like a better solution, but turning the socket buffer to > 32768 should have no negative impact. If fair queueing is used with ppp, ``set ifqueue 0'' is probably a good idea too - to stop ppp from getting in the way. > -- > Richard A Steenbergen http://www.e-gerbil.net/humble > PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) -- 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 Nov 6 14:53:43 2000 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 21E9837B479; Mon, 6 Nov 2000 14:53:30 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.0) with ESMTP id eA6MjiT02058; Mon, 6 Nov 2000 22:45:44 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eA6Mk9T13715; Mon, 6 Nov 2000 22:46:09 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200011062246.eA6Mk9T13715@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Kris Kennaway Cc: "Richard A. Steenbergen" , David Greenman , freebsd-net@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: tcp sendspace/recvspace In-Reply-To: Message from Kris Kennaway of "Sun, 05 Nov 2000 17:57:22 PST." <20001105175722.A8886@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Nov 2000 22:46:09 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sun, Nov 05, 2000 at 08:36:14PM -0500, Richard A. Steenbergen wrote: > > On Sun, 5 Nov 2000, Kris Kennaway wrote: > >=20 > > > On Sun, Nov 05, 2000 at 02:02:44PM -0800, David Greenman wrote: > > > > I've been messing around with the net.inet.tcp.sendspace and=20 > > > > net.inet.tcp.recvspace parameters on ftp.freesoftware.com and have fo= > und > > > > that there is a significant performance improvement when increasing t= > hese > > > > to 32768 bytes. Apparantly there are enough systems out there with hi= > gher > > > > window maxes that it really does make a difference. By significant=20 > > > > improvement, I mean about a average of a 20% increase in Mbps per use= > r, > > > > and this was just the change over a 30 minute period with lots of con= > nections > > > > still using the old 16K values. > > > > Any objections to increasing the defaults in FreeBSD to 32K? > > >=20 > > > Won't this impact the latency of multiple connections over a slow PPP l= > ink? > >=20 > > Thats what the congestion window is for. Any limitation of transmits based > > on the advertised memory limitation window is totally improper. > > Perhaps it was a bug, but I used to see e.g. FTP transfers which were > running at full speed totally monopolizing my modem bandwidth (then a > 14.4k), and other sessions not being able to receive their "fair > share". Tweaking net.inet.tcp.recvspace to give only a second or two > worth of data transfer reduced the latency to acceptable levels. > > Maybe this has been fixed by now - I haven't noticed it since I > upgraded to a 56k modem. I'll try increasing my system to 32768 > and see if it has any effect. Have a look at ppp's ``set urgent'' and ``set ifqueue'' commands. These will effect interactive performance over a (slow) link.... Setting tcp.sendspace to a low value would probably make these ppp values more sensitive. > Kris -- 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 Nov 6 20:43:47 2000 Delivered-To: freebsd-net@freebsd.org Received: from ebola.biohz.net (ebola.biohz.net [206.80.1.35]) by hub.freebsd.org (Postfix) with ESMTP id A735E37B4CF for ; Mon, 6 Nov 2000 20:43:44 -0800 (PST) Received: from flu (localhost [127.0.0.1]) by ebola.biohz.net (Postfix) with SMTP id 01A973A2C1; Mon, 6 Nov 2000 20:43:43 -0800 (PST) Message-ID: <00d801c04875$4f2b86c0$0402010a@biohz.net> From: "Renaud Waldura" To: "John Telford" Cc: References: <001501c0453e$c0d00100$0100000a@johnny5> <3A047E22.5C320AA1@elischer.org> <000801c04770$84014980$0100000a@johnny5> Subject: Re: Tips, How-To on VPN ? Date: Mon, 6 Nov 2000 20:43:43 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" 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 > Thanks, I came across this: http://www.freebsddiary.org/pipsecd.html > Anyone else used pipesecd, comments ? Yeah, it's all right -- basically a week-end hack by some French dude. I mean, it basically works, it's just that it's more a proof of concept than a rock solid VPN backbone; something to play with at home. I wouldn't use it to support any kind of "commercial" operations. But hey YMMV, give it a shot for yourself. --Renaud ----- Original Message ----- From: John Telford To: Julian Elischer Cc: Sent: Sunday, November 05, 2000 1:36 PM Subject: Re: Tips, How-To on VPN ? > > > John Telford wrote: > > > > > > Hi, > > > Am I on the right track here ? > > > Here's the scenario: > > > 2 locations with the same ISP, on the same public subnet. > > > Each firewalled with a 4.1.1 box. > > > > > > Macs and PC's need access to Mac and NT servers in both directions. > > > > > > Is a vpn/pptp the way to go here ? > > > Pointers to resources and tutorials would be greatly appreciated. > > > Thanks in advance, John. > > > > > > > > > > you could use mpd-netgraph (in ports/net) with pptp > > > > julian > > -- > > with "unsubscribe freebsd-net" in the body of the message > Thanks, I came across this: http://www.freebsddiary.org/pipsecd.html > Anyone else used pipesecd, comments ? > ,John. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 6 20:50:13 2000 Delivered-To: freebsd-net@freebsd.org Received: from ebola.biohz.net (ebola.biohz.net [206.80.1.35]) by hub.freebsd.org (Postfix) with ESMTP id 04E1F37B4C5 for ; Mon, 6 Nov 2000 20:50:11 -0800 (PST) Received: from flu (localhost [127.0.0.1]) by ebola.biohz.net (Postfix) with SMTP id 6DDAA3A2C1; Mon, 6 Nov 2000 20:50:10 -0800 (PST) Message-ID: <016601c04876$356ab3e0$0402010a@biohz.net> From: "Renaud Waldura" To: "Peter Schwenk" Cc: References: <3A039EFD.A45F01B8@softweyr.com> <20001104184309.A10492@peorth.iteration.net> Subject: Re: Getting Lucent Orinoco Silver Card Working Date: Mon, 6 Nov 2000 20:50:10 -0800 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've found that "(null)" ("(null)") is iomem conflicts. Please follow Same here. Watch out for those IRQ conflicts! I had to enter: machdep.pccard.pcic_irq=10 in /boot/loader.conf to get my PC card reader to work. dmesg now says: pcic0: at port 0x3e0-0x3e1 on isa0 pcic0: management irq 10 and PC cards are detected OK. I was going to do the same setup as yours, but got distracted onto other things... Let us know how you get it to work with FreeBSD. --Renaud ----- Original Message ----- From: Michael C . Wu To: Peter Schwenk Cc: Sent: Saturday, November 04, 2000 4:43 PM Subject: Re: Getting Lucent Orinoco Silver Card Working > On Sat, Nov 04, 2000 at 12:50:45AM -0500, Mike Goumans scribbled: > | On Fri, 3 Nov 2000, Wes Peters wrote: > | > Peter Schwenk wrote: > | > > I'm attempting to use a freebsd 4.1-R box as a base station. The box > | > > has another ethernet board hooked up to a cable modem. The box > | > > currently works as a home router to a wired network, but I'm hoping to > | > > replace the wires with Orinoco cards, which I've already purchased. The > | > > freebsd box has the ISA adapter from Lucent, which gets recognized by > | > > the kernel. When the card is inserted into the adapter, the pccard > | > > service complains about not having an entry in the database for card > | > > "(null)" ("(null)"). It's as if the orinoco card isn't advertising > | > > itself as any card at all. Does anyone know what might be going wrong? > | > Poke the card in your system, do a pccardc dumpcis, and edit the above entry > | > to match the two ID strings, probably something like "Orinoco/IEEE" at a > | Orinoco cards still have the same cis tuples as the older Lucent badged > | ones. Only the sticker is different. The fact that the card is coming up > | null null though would leave me to beleive that the cis information cannot > | be read properly. I would try using pccardc power to shutdown and > | reactivate the card, and see if you can use dumcis to read the tuples > | properly, and if it still doesnt i would say not based on experience but > | just assumption, first try the card in a windows box and see if the driver > | takes on it. if it doesnt there may be hardware issues. And then next try > | to force the driver on the card with pccardc enabler but there seems to be > | an error in handling the iosize for assigning ports to the card. instead > | of assigning a range of ports, it just assigns one indivbidual port when > | it needs 64. YMMV though. its a simple fix though but I dont have it on > | me. Its in the pccardc code but it didnt work until i forced it to. > > I've found that "(null)" ("(null)") is iomem conflicts. Please follow > http://www.geocrawler.com/lists/3/FreeBSD/163/0/3788553/ :) > > -- > +------------------------------------------------------------------+ > | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | > | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | > +------------------------------------------------------------------+ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 6 20:50:59 2000 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 9029F37B479 for ; Mon, 6 Nov 2000 20:50:55 -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) with ESMTP id NAA27520; Tue, 7 Nov 2000 13:50:46 +0900 (JST) To: John Telford , freebsd-net@freebsd.org In-reply-to: nick's message of Fri, 03 Nov 2000 08:51:59 MST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: Tips, How-To on VPN ? From: itojun@iijlab.net Date: Tue, 07 Nov 2000 13:50:46 +0900 Message-ID: <27518.973572646@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Hi, >> Am I on the right track here ? >> Here's the scenario: >> 2 locations with the same ISP, on the same public subnet. >> Each firewalled with a 4.1.1 box. >> Macs and PC's need access to Mac and NT servers in both directions. >> Is a vpn/pptp the way to go here ? i'm not sure what is your goal here, but if you are trying to do IPsec, http://www.netbsd.org/Documentation/network/ipsec/ might be useful. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 6 21:14:23 2000 Delivered-To: freebsd-net@freebsd.org Received: from tomts6-srv.bellnexxia.net (smtp.bellnexxia.net [209.226.175.26]) by hub.freebsd.org (Postfix) with ESMTP id 3E73037B4CF for ; Mon, 6 Nov 2000 21:14:20 -0800 (PST) Received: from johnny5 ([64.229.46.74]) by tomts6-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20001107051418.BPPV10530.tomts6-srv.bellnexxia.net@johnny5>; Tue, 7 Nov 2000 00:14:18 -0500 Message-ID: <001201c04879$08dae5e0$0100000a@johnny5> Reply-To: "John Telford" From: "John Telford" To: "Renaud Waldura" Cc: References: <001501c0453e$c0d00100$0100000a@johnny5> <3A047E22.5C320AA1@elischer.org> <000801c04770$84014980$0100000a@johnny5> <00d801c04875$4f2b86c0$0402010a@biohz.net> Subject: Re: Tips, How-To on VPN ? Date: Tue, 7 Nov 2000 00:10:24 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What would you use then ? I look at the freebsddiary article because it describes pretty much what I would like to do ""Our goal is to make it appear to the machines on either LAN that it is one seamless network. Additionally we want any data that is transferred between the two networks to be secure (encrypted). We do that by setting up a secure tunnel."" I want the FBSD boxes to do all the work and users consider it a slow LAN connection without having to do anything on the client systems. Regards, John. ----- Original Message ----- From: "Renaud Waldura" To: "John Telford" Cc: Sent: Monday, November 06, 2000 11:43 PM Subject: Re: Tips, How-To on VPN ? > > Thanks, I came across this: http://www.freebsddiary.org/pipsecd.html > > Anyone else used pipesecd, comments ? > > Yeah, it's all right -- basically a week-end hack by some French dude. I > mean, it basically works, it's just that it's more a proof of concept than a > rock solid VPN backbone; something to play with at home. I wouldn't use it > to support any kind of "commercial" operations. > > But hey YMMV, give it a shot for yourself. > > --Renaud > > > > > ----- Original Message ----- > From: John Telford > To: Julian Elischer > Cc: > Sent: Sunday, November 05, 2000 1:36 PM > Subject: Re: Tips, How-To on VPN ? > > > > > > John Telford wrote: > > > > > > > > Hi, > > > > Am I on the right track here ? > > > > Here's the scenario: > > > > 2 locations with the same ISP, on the same public subnet. > > > > Each firewalled with a 4.1.1 box. > > > > > > > > Macs and PC's need access to Mac and NT servers in both directions. > > > > > > > > Is a vpn/pptp the way to go here ? > > > > Pointers to resources and tutorials would be greatly appreciated. > > > > Thanks in advance, John. > > > > > > > > > > > > > > you could use mpd-netgraph (in ports/net) with pptp > > > > > > julian > > > -- > > > with "unsubscribe freebsd-net" in the body of the message > > Thanks, I came across this: http://www.freebsddiary.org/pipsecd.html > > Anyone else used pipesecd, comments ? > > ,John. > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 6 21:16:40 2000 Delivered-To: freebsd-net@freebsd.org Received: from tomts6-srv.bellnexxia.net (smtp.bellnexxia.net [209.226.175.26]) by hub.freebsd.org (Postfix) with ESMTP id 5956D37B479 for ; Mon, 6 Nov 2000 21:16:38 -0800 (PST) Received: from johnny5 ([64.229.46.74]) by tomts6-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20001107051637.BQWJ10530.tomts6-srv.bellnexxia.net@johnny5>; Tue, 7 Nov 2000 00:16:37 -0500 Message-ID: <001701c04879$5bb93140$0100000a@johnny5> Reply-To: "John Telford" From: "John Telford" To: , References: <27518.973572646@coconut.itojun.org> Subject: Re: Tips, How-To on VPN ? Date: Tue, 7 Nov 2000 00:12:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ----- Original Message ----- From: To: "John Telford" ; Sent: Monday, November 06, 2000 11:50 PM Subject: Re: Tips, How-To on VPN ? > > >> Hi, > >> Am I on the right track here ? > >> Here's the scenario: > >> 2 locations with the same ISP, on the same public subnet. > >> Each firewalled with a 4.1.1 box. > >> Macs and PC's need access to Mac and NT servers in both directions. > >> Is a vpn/pptp the way to go here ? > > i'm not sure what is your goal here, but if you are trying to do IPsec, > http://www.netbsd.org/Documentation/network/ipsec/ might be useful. > > itojun > Thanks, I look at the freebsddiary article because it describes pretty much what I would like to do ""Our goal is to make it appear to the machines on either LAN that it is one seamless network. Additionally we want any data that is transferred between the two networks to be secure (encrypted). We do that by setting up a secure tunnel."" I want the FBSD boxes to do all the work and users consider it a slow LAN connection without having to do anything on the client systems. Regards, John. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 6 23:22:33 2000 Delivered-To: freebsd-net@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 7155A37B4C5; Mon, 6 Nov 2000 23:22:25 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id A5F7F5730D; Tue, 7 Nov 2000 01:22:26 -0600 (CST) Date: Tue, 7 Nov 2000 01:22:26 -0600 From: "Michael C . Wu" To: Andrew Sporner Cc: freebsd-net@freebsd.org, "'freebsd-hackers@freebsd.org'" Subject: Re: High-availability failover software available. Message-ID: <20001107012226.A61671@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , Andrew Sporner , freebsd-net@freebsd.org, "'freebsd-hackers@freebsd.org'" References: <8D18C4F9CBA1D311900F00A0C990C97F67CB44@neimail.networkengines.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8D18C4F9CBA1D311900F00A0C990C97F67CB44@neimail.networkengines.com Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >; from andy.sporner@networkengines.com on Mon, Nov 06, 2000 at 05:59:57PM -0500 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 [Moving to -net, please remove -hackers cc when replying] On Mon, Nov 06, 2000 at 05:59:57PM -0500, Andrew Sporner scribbled: | Hi, | | Please allow me to introduce myself. I am Andrew Sporner and I have Hi, :) | a H/A Failover system that happens to work with BSD. I would like to | contribute | this to the FreeBSD project or at a minimum make it available to those who | What it includes is: | - Multi-path heartbeat based node failure detection. How do you determine that a machine/service is "failing"? Have you considered that the distributed nodes might be very far away from each other, even across the globe? Lag time can lead to daemon falsely thinking that a node is down. Example: condition, Cross pacific link being slow Node A,B in Lake Tahoe, USA. Node C,D in Maldive Islands, South Pacific Node C and D have gigabit LAN between each other, and so does A and B Lake Tahoe Pacific Ocean Maldive Islands (A+B) <-------connected via T1-------> (C+D) Upon lag and/or service requests to (C+D) in India, while the T1 is slow, (C+D) should take over. Upon service request in America, B is down, C+D still alive, A is under high load, no matter how light the load of C+D, the service request should be routed to A. bla bla bla..... (I want to buy houses in these two places one day... 8-P ) Reading your code, I don't think broadcasting over all interfaces is a good idea. A safer way would be requiring two physical interfaces on all nodes, building two seperate physical networks. The nodes communicate information on one network, and do the actual "work" on the other, more powerful, network. The daemons on the nodes should broadcast over these two interfaces. In addition, a comparison between the connectivity of the two physical networks can provide lots of valuable info. There is another bad thing about broadcasting over all interfaces, several types of attacks can be made: A. spoofing node packets, making controlling daemon believe some machinese are down. B. network internal information acquired by people that shouldn't have them. A great thing to do with this code would be using kqueue. | - Application failover. | - Applications can be assigned to two or many nodes in the | cluster. If the current node that the application runs on | fails, the next successor picks up the application. I think there should be a daemon that "routes" service queries, say a http request, to different nodes as the requests come in. | - Drag&Drop administration interface (X-11 tcl/tk based I think this should also include a console-type controller. Real-life work involves admining remotely, and GUI apps are not that great remotely. | The current state is alpha and is being tested by several people now. Beta | The current source is located at http://www.sporner.com/bsdclusters Please document what you have done, so we can learn more about the engineering thinking behind your implementation. | Please let me know what I should do... Will this be BSDL or will it be another license? Also, please include man pages. | Andy Sporner | PS. I am not sure how many of you were at BSDCon 2000, but that was some | very good talks--especially the BIO talk. I think we missed a great chance to talk to each other, since my research interest is the same field as your project. Or we may have met, I'm the Chinese guy that had the shortest hair. P.S. Please keep lines shorter than 80 characters. :) -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 7 6:51: 5 2000 Delivered-To: freebsd-net@freebsd.org Received: from neimail.networkengines.com (unknown [64.55.6.7]) by hub.freebsd.org (Postfix) with ESMTP id E238537B4C5; Tue, 7 Nov 2000 06:50:55 -0800 (PST) Received: by neimail.networkengines.com with Internet Mail Service (5.5.2650.21) id ; Tue, 7 Nov 2000 09:48:08 -0500 Message-ID: <8D18C4F9CBA1D311900F00A0C990C97F67CB4A@neimail.networkengines.com> From: Andrew Sporner To: "'Michael C . Wu'" , Andrew Sporner Cc: freebsd-net@freebsd.org, "'freebsd-hackers@freebsd.org'" Subject: RE: High-availability failover software available. Date: Tue, 7 Nov 2000 09:48:07 -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 Hi! > | a H/A Failover system that happens to work with BSD. I > would like to > | contribute > | this to the FreeBSD project or at a minimum make it > available to those who > | What it includes is: > | - Multi-path heartbeat based node failure detection. > > How do you determine that a machine/service is "failing"? > Have you considered that the distributed nodes might be very far > away from each other, even across the globe? Lag time can > lead to daemon falsely thinking that a node is down. This is for local area clusters. This is really foundation work for another project I have in mind, involving process swapping. I needed a way of finding when a node died to do some garbage collection. As it turned out, it didn't take much to make it work for doing application failover. So I thought, "Well since there doesn't appear to be anything free this way--why not!? and so here it is." In short I am not trying to solve geographical failover because it isn't really germaine to my goal. But, if the architecture lends itself to it, there is no reason not to include it. Any takers? But to answer your question. A heart beat message is sent on the broadcast address of the networks that the machine lives on. Currently it will use all of them. I think a necessary feature would be to allow for a subset of interfaces. :-) But I wanted to solve the bigger problems first. When a peer node recieves the packet, it updates a timestamp for it's peer interface. Periodically these are checked and if one of the links is out of bounds, it is marked offline. When the last live interface is marked offline, the node is marked offline and then the recovery procedure starts. There may be a need to start recovery if only one interface fails, but again this is outside the mission I have embarked on. Mainly because the architecture I am pursing requires that the heartbeat lans (which will also be used to transfer pages between machines) be private and not used for user applications. In this way I get link recovery through redundancy and the cluster software knows how to handle it--where an application might (actually probably) won't know how to handle it. But to stop a potential argument--let's leave it strictly the case of keeping these particular lans private. > > Reading your code, I don't think broadcasting over all > interfaces is a good idea. A safer way would be requiring two > physical interfaces on all nodes, building two seperate physical > networks. The nodes communicate information on one network, and > do the actual "work" on the other, more powerful, network. The > daemons on the nodes should broadcast over these two interfaces. > In addition, a comparison between the connectivity of the two physical > networks can provide lots of valuable info. I agree! I am answering this email serially and am reading as I reply and it looks like we are in sync. I will in the next few releases privide a delete option on the GUI to take away an autodiscovered interface. I think the autodiscovery is important, but it should be allowed to be updated. The interface will remain in the configuration (so it doesn't get autodiscovered again! :-)) but marked with a special flag so it isn't used. An upcoming feature is the ability to drag a lan interface over to the right of the GUI to monitor LAN perforamce. I also plan to have several metrics tied to each resource and by right-clicking on the guages that are there you can change them. Right now The applications or nodes can be monitored and it is only CPU, MEMORY and one other--been too long since I saw it. At one point I even thougth about putting TOP functionality in the GUI so that by expanding a node, one can also see the processes and drag a process over to the right side to monitor it. > A great thing to do with this code would be using kqueue. Can you give me more specifics? or better--would you be willing to try it and give me the patch? > > I think there should be a daemon that "routes" service queries, say > a http request, to different nodes as the requests come in. Like a load balancer? :-) I had one once and unfortunately two things. First it won't scale (reverse proxy) and second some people I worked on this for would have a fit. I went to a great mini-tutorial at BSDcon about IP filter. Guido mentioned something about having a kernel filter rule that calls a kernel address for each packet. A good way to do this would be to put a router inside the kernel and then leverage the IP filter. > > | - Drag&Drop administration interface (X-11 tcl/tk based > > I think this should also include a console-type controller. > Real-life work involves admining remotely, and GUI apps are not > that great remotely. :-) OK, next release! :-) > > | The current state is alpha and is being tested by several > people now. Beta > | The current source is located at http://www.sporner.com/bsdclusters > > Please document what you have done, so we can learn more about > the engineering thinking behind your implementation. In progress, maybe some of my answers here would help. I also have heavily commented the cluster.c code. But I will write a document detailing how and why in the near future. > Will this be BSDL or will it be another license? Also, please > include man pages. Yes, and yes :-) > I think we missed a great chance to talk to each other, since my > research interest is the same field as your project. Or we may have > met, I'm the Chinese guy that had the shortest hair. > > P.S. Please keep lines shorter than 80 characters. :) Ahhh! A terminal guy :-) I will try to, but since I kind of whored myself to microsoft for email it is hard to think about this :-) Thanks for all of your feedback! Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 7 12:48:22 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id D96DB37B479 for ; Tue, 7 Nov 2000 12:48:19 -0800 (PST) Received: (qmail 11748 invoked by uid 0); 7 Nov 2000 20:48:18 -0000 Received: from p3e9e03d9.dip.t-dialin.net (HELO forge.local) (62.158.3.217) by mail.gmx.net (mail06) with SMTP; 7 Nov 2000 20:48:18 -0000 Received: from thomas by forge.local with local (Exim 3.12 #1 (Debian)) id 13tFeo-0000YX-00 for ; Tue, 07 Nov 2000 21:47:50 +0100 Date: Tue, 7 Nov 2000 21:47:50 +0100 To: freebsd-net@freebsd.org Subject: setting source address for UDP packets Message-ID: <20001107214749.A2125@forge.local> Mail-Followup-To: tmoestl@gmx.net, freebsd-net@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i From: Thomas Moestl Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, is there any way to set the source address of an UDP (over IPv4) packet without using bind() or changing the socket state, ala the IN6_PKTINFO ancillary data to sendmsg? Background: in a multithreaded server, I want to answer with the source address the query went to. This will work normally, but if the packet leaves through another interface than that it arrived on, it will off course get a different source address. There are some routing situations where such things can happen. I cannot use bind(), because the socket is shared by other threads. I could of course lock the socket in some way, but since the send()-call can block, this is suboptimal. Any ideas? Thanks in advance, Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 7 13:56:35 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 6B92737B479 for ; Tue, 7 Nov 2000 13:56:33 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA87433; Tue, 7 Nov 2000 16:56:23 -0500 (EST) (envelope-from wollman) Date: Tue, 7 Nov 2000 16:56:23 -0500 (EST) From: Garrett Wollman Message-Id: <200011072156.QAA87433@khavrinen.lcs.mit.edu> To: Thomas Moestl Cc: freebsd-net@FreeBSD.ORG Subject: setting source address for UDP packets In-Reply-To: <20001107214749.A2125@forge.local> References: <20001107214749.A2125@forge.local> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > is there any way to set the source address of an UDP (over IPv4) packet > without using bind() or changing the socket state, No. This is a long-standing bug. It shouldn't be too hard to fix if you're up to a bit of kernel hacking. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 7 14: 2:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 13E8837B479 for ; Tue, 7 Nov 2000 14:02:39 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.9.3/8.9.3) id OAA03771; Tue, 7 Nov 2000 14:02:24 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200011072202.OAA03771@iguana.aciri.org> Subject: Re: setting source address for UDP packets In-Reply-To: <200011072156.QAA87433@khavrinen.lcs.mit.edu> from Garrett Wollman at "Nov 7, 2000 4:56:23 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Tue, 7 Nov 2000 14:02:24 -0800 (PST) Cc: tmoestl@gmx.net, freebsd-net@FreeBSD.ORG, rizzo@aciri.org (Luigi Rizzo) 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 > > is there any way to set the source address of an UDP (over IPv4) packet > > without using bind() or changing the socket state, > > No. This is a long-standing bug. It shouldn't be too hard to fix if > you're up to a bit of kernel hacking. you mean by adding a sendto_from() system call where you also pass the address for the source ? Or [really dirty hack here] an extended sendto() where the sockaddr really points to an array of two addresses (with "tolen" set accordingly) ? cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 7 14:13:51 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 94E0937B479 for ; Tue, 7 Nov 2000 14:13:48 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id RAA87555; Tue, 7 Nov 2000 17:13:46 -0500 (EST) (envelope-from wollman) Date: Tue, 7 Nov 2000 17:13:46 -0500 (EST) From: Garrett Wollman Message-Id: <200011072213.RAA87555@khavrinen.lcs.mit.edu> To: Luigi Rizzo Cc: tmoestl@gmx.net, freebsd-net@FreeBSD.ORG Subject: Re: setting source address for UDP packets In-Reply-To: <200011072202.OAA03771@iguana.aciri.org> References: <200011072156.QAA87433@khavrinen.lcs.mit.edu> <200011072202.OAA03771@iguana.aciri.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > you mean by adding a sendto_from() system call where you also pass > the address for the source ? > Or [really dirty hack here] an extended sendto() where the sockaddr > really points to an array of two addresses (with "tolen" set > accordingly) ? No, I mean by adding a control-data interpreter to accept IP_RECVDSTADDR control messages and set the `from' address accordingly. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 7 14:35: 8 2000 Delivered-To: freebsd-net@freebsd.org Received: from overlord.e-gerbil.net (e-gerbil.net [207.91.110.247]) by hub.freebsd.org (Postfix) with ESMTP id 7878337B479 for ; Tue, 7 Nov 2000 14:35:05 -0800 (PST) Received: by overlord.e-gerbil.net (Postfix, from userid 1001) id 6A99DE4EB9; Tue, 7 Nov 2000 17:34:53 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by overlord.e-gerbil.net (Postfix) with ESMTP id 56A57E4EB8; Tue, 7 Nov 2000 17:34:53 -0500 (EST) Date: Tue, 7 Nov 2000 17:34:53 -0500 (EST) From: "Richard A. Steenbergen" To: David Greenman Cc: freebsd-net@freebsd.org Subject: Re: tcp sendspace/recvspace In-Reply-To: <200011052257.OAA24410@implode.root.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 Sun, 5 Nov 2000, David Greenman wrote: > Overall I like the idea of a dynamically scaling these, but I'm talking > about the "right now" and not the "next year some time, maybe". I am concerned Its nowhere near so far away. Infact if you're interested, here's the current holdup. The auto-tuned socket buffer size is designed to take feedback from the cwnd, to determine what the socket "wants". But in a low memory situation, the socket may not always be able to get what it wants. In order to determine how much it "gets", one should be fair and consider the demands of all other sockets. The PSC implementation does this by periodically (on slowtimo) scanning through all tcp sockets, and calculating a fair value per socket. http://www.psc.edu/publications/tech_reports/fairshare/fairshare.html http://www.psc.edu/networking/papers/sigcomm98/sld018.htm http://www.psc.edu/networking/papers/sigcomm98/sld016.htm This obviously has performance and locking implications, and probably isn't the easiest way to do things. The method that I'm considering most heavily now is eliminating the slowtimo called scan, seperating the demands for memory into "easy" to fill aka we can give it everything it wants, and "hard" to fill, and then calculating ratios of available / requested to determine how much the sockets can get... In order for this to be effective it would need to be driven down to sbappend() and done on a per packet basis though. I'm really not happy with any solution so far. -- Richard A Steenbergen http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 7 15:33:27 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 0E7D937B4C5 for ; Tue, 7 Nov 2000 15:33:24 -0800 (PST) Received: (qmail 20415 invoked by uid 0); 7 Nov 2000 23:33:22 -0000 Received: from p3e9e0465.dip.t-dialin.net (HELO forge.local) (62.158.4.101) by mail.gmx.net (mail06) with SMTP; 7 Nov 2000 23:33:22 -0000 Received: from thomas by forge.local with local (Exim 3.12 #1 (Debian)) id 13tIEY-0001Qk-00 for ; Wed, 08 Nov 2000 00:32:54 +0100 Date: Wed, 8 Nov 2000 00:32:54 +0100 From: Thomas Moestl To: freebsd-net@FreeBSD.ORG Subject: Re: setting source address for UDP packets Message-ID: <20001108003253.A5469@forge.local> Mail-Followup-To: Thomas Moestl , freebsd-net@FreeBSD.ORG References: <20001107214749.A2125@forge.local> <200011072156.QAA87433@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011072156.QAA87433@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Tue, Nov 07, 2000 at 04:56:23PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > is there any way to set the source address of an UDP (over IPv4) packet > > without using bind() or changing the socket state, > > No. This is a long-standing bug. It shouldn't be too hard to fix if > you're up to a bit of kernel hacking. I'll give it a try. Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 7 16:23:17 2000 Delivered-To: freebsd-net@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id B5CFB37B4CF for ; Tue, 7 Nov 2000 16:23:14 -0800 (PST) Received: from randy by rip.psg.com with local (Exim 3.16 #1) id 13tJ1E-0000FY-00; Tue, 07 Nov 2000 16:23:12 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Richard A. Steenbergen" Cc: freebsd-net@freebsd.org, Vern Paxson Subject: Re: tcp sendspace/recvspace References: <200011052257.OAA24410@implode.root.com> X-Mailer: VM 6.80 under Emacs 19.34.1 Message-Id: Date: Tue, 07 Nov 2000 16:23:12 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org vern said i was welcome to copy this to the list To: Randy Bush Cc: Allison Mankin , Scott Bradner Subject: Re: tcp sendspace/recvspace Date: Mon, 06 Nov 2000 00:40:29 PST From: Vern Paxson I hope they do indeed pursue autotuning, I think it's a nifty solution to the general problem of finding the right window size. One effect I've noticed locally is that cranking the window size to a value like 32 KB can (1) help a lot with getting nearer to 100 Mbps performance on a fast LAN, but (2) can lead to throughput *degradation*, apparently due to the Ethernet capture effect. So I hope they assess the performance implications of the increase carefully, in a number of different operating regimes. Vern To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 7 18:24:32 2000 Delivered-To: freebsd-net@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 3A9D337B4C5 for ; Tue, 7 Nov 2000 18:24:29 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.0/8.11.0) with ESMTP id eA82OHG61786; Tue, 7 Nov 2000 21:24:17 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200011080224.eA82OHG61786@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Thomas Moestl Cc: freebsd-net@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: setting source address for UDP packets References: <20001107214749.A2125@forge.local> <200011072156.QAA87433@khavrinen.lcs.mit.edu> <20001108003253.A5469@forge.local> In-reply-to: Your message of "Wed, 08 Nov 2000 00:32:54 +0100." <20001108003253.A5469@forge.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Nov 2000 21:24:17 -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Take a look at the code for the NTP daemon. Simply, it creates and bind()'s a socket for each interface address associated with a multi-homed host (original application) or "alias" address. It then remembers what socket a query arrived on, and replies using the same socket to ensure the source address of the reply matches what the query was sent to. This is required to make the NTP protocol work. Yes, it's sort of a crock, but for typical hosts with only a few network interfaces/addresses, is probably workable. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 7 20:39:12 2000 Delivered-To: freebsd-net@freebsd.org Received: from tomts7-srv.bellnexxia.net (tomts7.bellnexxia.net [209.226.175.40]) by hub.freebsd.org (Postfix) with ESMTP id 511ED37B479; Tue, 7 Nov 2000 20:39:02 -0800 (PST) Received: from johnny5 ([64.229.55.24]) by tomts7-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20001108043852.NMGR20301.tomts7-srv.bellnexxia.net@johnny5>; Tue, 7 Nov 2000 23:38:52 -0500 Message-ID: <000e01c0493d$403d8460$0100000a@johnny5> Reply-To: "John Telford" From: "John Telford" To: , , References: <20001103215005.3885737B479@hub.freebsd.org> Subject: Re: Help with natd redirect address Please ???? Date: Tue, 7 Nov 2000 23:34:58 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for the tips, here's what happened: Lukasz Dudek suggested I recompile without the IPFILTER options and I also changed rc.conf so that the NIC's were initialized first. See below for my new settings. This got the redirect working fine at my office on a DSL connection but when I took the box on-site it just wouldn't work with the other ISP's numbers. It's a wireless ISP, but that shouldn't matter according to the ISP. My initial plan was that since we really just wanted our other site on the same ISP to have access to the inside servers and not public traffic I was going to get them setup on a quick (yeah right) redirect then move them to a VPN solution after I gathered some information on it, see my post at net@freebsd.org "Re: Tips, How-To on VPN ?" So I set up a VPN tunnel using pipsec and its working fine. I didn't get to research it as much as I wanted and will have scrounge some test boxes to try it with ipsec but the users are happy they can move files across at 1mbs rather than 56k modems. Regards, John. P.S. to the E man at the Big O the -u didn't help at tempo either, oh well just hope Dave doesn't want to access the Mac server from home anytime soon. Here's my configs that redirect worked with on the DSL: TEMfw3# more rc.conf network_interfaces="auto" # List of network interfaces (or "auto"). ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration. ifconfig_fxp0="inet 216.208.171.XXX netmask 255.255.255.224" ifconfig_fxp1="inet 10.150.0.241 netmask 255.255.255.0" # named_enable="YES" # Run named, the DNS server (or NO). defaultrouter="216.208.171.XXX" sendmail_enable="NO" gateway_enable="YES" sshd_enable="YES" inetd_enable="YES" ############################################################## ### Network configuration sub-section ###################### ############################################################## ### Basic network and firewall/security options: ### hostname="TEMfw3" # Set this! firewall_enable="YES" # Set to YES to enable firewall functionality firewall_type="OPEN" # Firewall type (see /etc/rc.firewall) firewall_quiet="NO" # Set to YES to suppress rule display firewall_logging="YES" natd_enable="YES" # Enable natd (if firewall_enable == YES). natd_interface="fxp0" # Public interface or IPaddress to use. natd_flags="-f /etc/natd.conf" # TEMfw3# TEMfw3# more natd.conf redirect_address 10.150.0.143 216.208.171.XXX TEMfw3# kernel settings: # options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets options IPSTEALTH #support for stealth forwarding options TCPDEBUG # options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN options TCP_RESTRICT_RST #restrict emission of TCP RST options "ICMP_BANDLIM" options DUMMYNET options BRIDGE TEMfw3# eot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 7 20:49:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from tomts7-srv.bellnexxia.net (tomts7.bellnexxia.net [209.226.175.40]) by hub.freebsd.org (Postfix) with ESMTP id 18C7F37B479 for ; Tue, 7 Nov 2000 20:49:39 -0800 (PST) Received: from johnny5 ([64.229.55.24]) by tomts7-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20001108044938.NPFC20301.tomts7-srv.bellnexxia.net@johnny5>; Tue, 7 Nov 2000 23:49:38 -0500 Message-ID: <002301c0493e$c10da1f0$0100000a@johnny5> Reply-To: "John Telford" From: "John Telford" To: References: <001501c0453e$c0d00100$0100000a@johnny5> Subject: Re: Tips, How-To on VPN ? Date: Tue, 7 Nov 2000 23:45:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As usual I ran out of time, see my post "Help with natd redirect address Please ????". I was trying to get a simple redirect to work while I played with the suggestions but redirect wouldn't go. I went through the http://www.freebsddiary.org/pipsecd.html and the instructions worked just fine. Thanks Phil ! If anyone has any other tips/suggestions let me know. Regards, John Original Text: Hi, Am I on the right track here ? Here's the scenario: 2 locations with the same ISP, on the same public subnet. Each firewalled with a 4.1.1 box. Macs and PC's need access to Mac and NT servers in both directions. Is a vpn/pptp the way to go here ? Pointers to resources and tutorials would be greatly appreciated. Thanks in advance, John. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Nov 8 1:26:58 2000 Delivered-To: freebsd-net@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id EA38037B479 for ; Wed, 8 Nov 2000 01:26:55 -0800 (PST) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.1/8.11.0) id eA89QhC81521; Wed, 8 Nov 2000 10:26:43 +0100 (CET) (envelope-from asmodai) Date: Wed, 8 Nov 2000 10:26:43 +0100 From: Jeroen Ruigrok van der Werven To: Alfred Perlstein Cc: David Greenman , freebsd-net@FreeBSD.ORG Subject: Re: tcp sendspace/recvspace Message-ID: <20001108102643.C80971@lucifer.bart.nl> References: <200011052202.OAA24207@implode.root.com> <20001105142433.K5112@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001105142433.K5112@fw.wintelcom.net>; from bright@wintelcom.net on Sun, Nov 05, 2000 at 02:24:33PM -0800 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20001105 23:25], Alfred Perlstein (bright@wintelcom.net) wrote: >* David Greenman [001105 14:05] wrote: >> I've been messing around with the net.inet.tcp.sendspace and >> net.inet.tcp.recvspace parameters on ftp.freesoftware.com and have found >> that there is a significant performance improvement when increasing these >> to 32768 bytes. [snip] >> Any objections to increasing the defaults in FreeBSD to 32K? > >No objection, just a suggestion that perhaps it should be set when >booting and determined by the amount of ram in the machine. Just >setting it 32k would also work. :) That's what we got /etc/sysctl.conf for maybe? We could hardwire it, or do a more configurable way of putting it in /etc/sysctl.conf. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Knowledge is power... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Nov 8 3: 1:56 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id CC2FE37B479 for ; Wed, 8 Nov 2000 03:01:52 -0800 (PST) Received: from victoria-137.budapest.interware.hu ([195.70.63.137] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13tSzC-0000jW-00; Wed, 08 Nov 2000 12:01:46 +0100 Message-ID: <3A093283.48BE41D8@elischer.org> Date: Wed, 08 Nov 2000 03:01:23 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Luigi Rizzo Cc: Garrett Wollman , tmoestl@gmx.net, freebsd-net@FreeBSD.ORG Subject: Re: setting source address for UDP packets References: <200011072202.OAA03771@iguana.aciri.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luigi Rizzo wrote: > > > > is there any way to set the source address of an UDP (over IPv4) packet > > > without using bind() or changing the socket state, > > > > No. This is a long-standing bug. It shouldn't be too hard to fix if > > you're up to a bit of kernel hacking. > > you mean by adding a sendto_from() system call where you also pass > the address for the source ? > Or [really dirty hack here] an extended sendto() where the sockaddr > really points to an array of two addresses (with "tolen" set well you could use divert sockets to send UDP packets (bleah) > accordingly) ? > > cheers > luigi > ----------------------------------+----------------------------------------- > Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) > http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 > Phone: (510) 666 2927 > ----------------------------------+----------------------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Nov 8 4: 7:30 2000 Delivered-To: freebsd-net@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A085537B479; Wed, 8 Nov 2000 04:07:24 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id NAA58160; Wed, 8 Nov 2000 13:07:21 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "John Telford" Cc: , , Subject: Re: Help with natd redirect address Please ???? References: <20001103215005.3885737B479@hub.freebsd.org> <000e01c0493d$403d8460$0100000a@johnny5> From: Dag-Erling Smorgrav Date: 08 Nov 2000 13:07:21 +0100 In-Reply-To: "John Telford"'s message of "Tue, 7 Nov 2000 23:34:58 -0500" Message-ID: Lines: 10 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "John Telford" writes: > Lukasz Dudek suggested I recompile without the IPFILTER options and I also > changed rc.conf so that the NIC's were initialized first. The order in which variables are assigned in rc.conf has absolutely no significance. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Nov 8 8:20:49 2000 Delivered-To: freebsd-net@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id CC8C937B479 for ; Wed, 8 Nov 2000 08:20:45 -0800 (PST) Received: (from uucp@localhost) by light.imasy.or.jp (8.11.0+3.3W/3.7W-light) with UUCP id eA8GKet22486; Thu, 9 Nov 2000 01:20:40 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:ecCPC0FUwagl3ML28N7AyQPJ53ai180FL9FhfRytb2stHucRurwKWHv99fu+3HTl@peace.mahoroba.org [2001:200:301:0:200:f8ff:fe05:3eae]) by mail.mahoroba.org (8.11.1/8.11.1/chaos) with ESMTP/inet6 id eA8GErn10392; Thu, 9 Nov 2000 01:14:53 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Thu, 09 Nov 2000 01:14:52 +0900 (JST) Message-Id: <20001109.011452.59467043.ume@mahoroba.org> To: j.telford@sympatico.ca Cc: freebsd-net@freebsd.org, itojun@iijlab.net Subject: Re: Tips, How-To on VPN ? From: Hajimu UMEMOTO In-Reply-To: <001701c04879$5bb93140$0100000a@johnny5> References: <27518.973572646@coconut.itojun.org> <001701c04879$5bb93140$0100000a@johnny5> X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> On Tue, 7 Nov 2000 00:12:43 -0500 >>>>> "John Telford" said: > i'm not sure what is your goal here, but if you are trying to do IPsec, > http://www.netbsd.org/Documentation/network/ipsec/ might be useful. j.telford> I want the FBSD boxes to do all the work and users consider it a slow LAN j.telford> connection without having to do anything on the client systems. j.telford> Regards, John. Though the URL Itojun mentioned is for NetBSD, FreeBSD has almost same IPSec facility, too. Both NetBSD's and FreeBSD's are from KAME. There are few documents about IPSec for FreeBSD than for NetBSD. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Nov 8 9:30:21 2000 Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 03A6437B479 for ; Wed, 8 Nov 2000 09:30:20 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13tZ1j-0000II-00; Wed, 08 Nov 2000 10:28:47 -0700 Message-ID: <3A098D4F.C5635D0C@softweyr.com> Date: Wed, 08 Nov 2000 10:28:47 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Garrett Wollman Cc: Thomas Moestl , freebsd-net@FreeBSD.ORG Subject: Re: setting source address for UDP packets References: <20001107214749.A2125@forge.local> <200011072156.QAA87433@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: > > > is there any way to set the source address of an UDP (over IPv4) packet > > without using bind() or changing the socket state, > > No. This is a long-standing bug. It shouldn't be too hard to fix if > you're up to a bit of kernel hacking. sendfrom(2), anyone? -- "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 Nov 8 10: 4:20 2000 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id D75EF37B479 for ; Wed, 8 Nov 2000 10:04:14 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id eA8I40o39160; Wed, 8 Nov 2000 20:04:00 +0200 (EET) (envelope-from ru) Date: Wed, 8 Nov 2000 20:03:59 +0200 From: Ruslan Ermilov To: net@FreeBSD.org Cc: Charles Mott , Ari Suutari Subject: libalias: Incremental Update of Internet Checksum Message-ID: <20001108200359.A38693@sunbay.com> Mail-Followup-To: net@FreeBSD.org, Charles Mott , Ari Suutari Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi! The DifferentialChecksum() function in libalias(3) is used to efficiently recompute the checksum for altered packets. Unfortunately, the implementation suffers from the problem described in RFC 1624. I have implemented the replacement for it, using the final formula [4] from the RFC. The attached C program demonstrates the problem as well as the new implementation. Comments? -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=Makefile PROG= inc_cksum NOMAN= YES CFLAGS+=${BDECFLAGS} .include --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="inc_cksum.c" #include #include void DifferentialChecksum(u_short *, u_short *, u_short *, int); void DifferentialChecksum_RFC1624(u_short *, u_short *, u_short *, int); void DifferentialChecksum(u_short *cksum, u_short *new, u_short *old, int n) { int i; int accumulate; accumulate = *cksum; for (i=0; i> 16) + (accumulate & 0xffff); accumulate += accumulate >> 16; *cksum = (u_short) ~accumulate; } else { accumulate = (accumulate >> 16) + (accumulate & 0xffff); accumulate += accumulate >> 16; *cksum = (u_short) accumulate; } } /* * Incremental Update of Internet Checksum with [Eqn. 4] from RFC 1624. */ void DifferentialChecksum_RFC1624(u_short *cksum, u_short *new, u_short *old, int n) { int i; int accumulate; /* should be `signed' */ accumulate = *cksum; for (i = 0; i < n; i++) { accumulate -= *new++; accumulate -= (u_short)~*old++; } accumulate = (accumulate >> 16) + (accumulate & 0xffff); accumulate += accumulate >> 16; *cksum = (u_short) accumulate; } int main(void) { u_short old, new, oldcksum, newcksum1, newcksum2; old = 0x5555; for (new = 0x0;; new++) { for (oldcksum = 0x0;; oldcksum++) { newcksum1 = newcksum2 = oldcksum; DifferentialChecksum(&newcksum1, &new, &old, 1); DifferentialChecksum_RFC1624(&newcksum2, &new, &old, 1); if (newcksum1 != newcksum2) printf("old=%#hx new=%#hx oldcksum=%#hx " "newcksum1=%#hx newcksum2=%#hx\n", old, new, oldcksum, newcksum1, newcksum2); if (oldcksum == 0xffff) break; } if (new == 0xffff) break; } return (0); } --Dxnq1zWXvFF0Q93v-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Nov 8 10:19: 9 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 5DF2737B4C5 for ; Wed, 8 Nov 2000 10:19:06 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA95466; Wed, 8 Nov 2000 13:18:55 -0500 (EST) (envelope-from wollman) Date: Wed, 8 Nov 2000 13:18:55 -0500 (EST) From: Garrett Wollman Message-Id: <200011081818.NAA95466@khavrinen.lcs.mit.edu> To: Wes Peters Cc: freebsd-net@FreeBSD.ORG Subject: Re: setting source address for UDP packets In-Reply-To: <3A098D4F.C5635D0C@softweyr.com> References: <20001107214749.A2125@forge.local> <200011072156.QAA87433@khavrinen.lcs.mit.edu> <3A098D4F.C5635D0C@softweyr.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > sendfrom(2), anyone? No! The correct solution is the one I described in my previous mail. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 6:37:29 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.chiaro.com (us.chiaro.com [63.88.196.33]) by hub.freebsd.org (Postfix) with ESMTP id B755737B479 for ; Thu, 9 Nov 2000 06:37:26 -0800 (PST) Received: from chiaro.com (PLAWTHERS [128.101.236.150]) by mail.chiaro.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id WR33KN0J; Thu, 9 Nov 2000 08:37:24 -0600 Message-ID: <3A0AB6A2.517AC64F@chiaro.com> Date: Thu, 09 Nov 2000 08:37:22 -0600 From: Peter Lawthers Organization: Chiaro Networks X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: ANVL Test Suites Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone ever run the ANVL test suites (http://www.hammer.com/p_datacom.htm) on FreeBSD? I would be interested in hearing what the results were. I apologize if this question has been asked before, but I couldn't find a FAQ or anything like that for this list. Is there an online archive anywhere? Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 9:38:40 2000 Delivered-To: freebsd-net@freebsd.org Received: from aifhs8.alcatel.fr (aifhs8.alcatel.fr [212.208.74.153]) by hub.freebsd.org (Postfix) with ESMTP id 04A6F37B479 for ; Thu, 9 Nov 2000 09:38:36 -0800 (PST) Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs8.alcatel.fr (ALCANET/SMTP2) with SMTP id SAA07801 for ; Thu, 9 Nov 2000 18:38:30 +0100 (MET) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id C1256992.0060DD45 ; Thu, 9 Nov 2000 18:38:01 +0100 X-Lotus-FromDomain: ALCATEL From: Thierry.Herbelot@alcatel.fr To: net@freebsd.org Message-ID: Date: Thu, 9 Nov 2000 18:30:56 +0100 Subject: 16 NICs on a Compaq PC ? Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I'm trying to build a low-cost Ethernet router with a Compaq Deskpro EP-6450 and 4 4-port NIC from DLINK (DFE-570-TX model) I'm using the dc driver for a 4.1.1-Release. the performance is very disappointing (the throughput is on the order of 200 kpbs for a direct 100Mbps ful-duplex Ethernet link) I've got messages "dc0 : TX underrun -- increasing TX threshold" (lots of them ..) I've also seen that all dc ports get mapped to the same irq (nr 11), and when I try to change this setting, the machine stops booting (I have to try with WinNT) 1st Q : is there a performance hit with all ports tied to the single irq11 ? (my gut feeling would be "of course", I'd like to be sure) 2nd Q : has someone built a similar configuration ? 3rd Q : do I need to dump all the Compaqs to buy other, more standard machines ? TfH PS1 : PS2 : sinppet of the dmesg : .... dc0: port 0x4000-0x407f mem 0x40c00000-0x40c003ff irq 11 at device 4.0 on pci2 dc0: Ethernet address: 00:80:c8:f8:4c:4d miibus0: on dc0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc1: port00x4080-0x40ff mem 0x40d00000-0x40d003ff irq 11 at device 5.0 on pci2 dc1: Ethernet address: 00:80:c8:f8:4c:4e mii\M-bus1: on dc1 ukphy1: on miibus1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc2: port 0x4400-0x447f mem 0x40e00000-0x40e003ff irq 11 at device 6.0 on pci2 dc2: Ethernet address: 00:80:c8:f8:4c:4f miibus2: on dc2 ukphy2: on miibus2 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc3: port 0x4480-0x44ff mem 0x40f00000-0x40f003ff irq .... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 10:52:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 342B137B479 for ; Thu, 9 Nov 2000 10:52:40 -0800 (PST) Received: (qmail 19330 invoked by uid 0); 9 Nov 2000 18:52:34 -0000 Received: from pc19e96b1.dip.t-dialin.net (HELO forge.local) (193.158.150.177) by mail.gmx.net (mail05) with SMTP; 9 Nov 2000 18:52:34 -0000 Received: from thomas by forge.local with local (Exim 3.12 #1 (Debian)) id 13twnl-0000Fz-00 for ; Thu, 09 Nov 2000 19:51:57 +0100 Date: Thu, 9 Nov 2000 19:51:57 +0100 From: Thomas Moestl To: freebsd-net@FreeBSD.ORG Subject: Re: setting source address for UDP packets Message-ID: <20001109195156.A951@forge.local> Mail-Followup-To: Thomas Moestl , freebsd-net@FreeBSD.ORG References: <20001107214749.A2125@forge.local> <200011072156.QAA87433@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011072156.QAA87433@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Tue, Nov 07, 2000 at 04:56:23PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Nov 07, 2000 at 04:56:23PM -0500, Garrett Wollman wrote: > > is there any way to set the source address of an UDP (over IPv4) packet > > without using bind() or changing the socket state, > > No. This is a long-standing bug. It shouldn't be too hard to fix if > you're up to a bit of kernel hacking. As followup to my recent post, here is my first version of a patch to make UDP sendmsg() honor the IP_RECVDSTADDR ancillary data. Please comment! This is tested on a -stable box and works fine. Unfortunately, I had no chance for testing this on a -current box (I am right now building one, but my network connection is slow). There does not seem to have changed very much in that particular code, however. The patch applies to only udp_output in netinet/udp_usrreq.c For assigning the source address temporarily, in_pcbbind() is used if the socket was not bound before, otherwise we assign the parameters and rehash. Analog to the in_pcbconnect() handling, we lock with splnet() temporarily while the opration is in progress. After we are done, we rebind using the old parameters. Part of the ancillary data handling is taken from in6_output.c, so I assume that it is correct (tolerable ?) to change m_len and m_data of an mbuf. If it is not, please correct me! This change might break programs that pass ancillary data of unknown type. If this is a problem, we could silently ignore the options as we did before. Apropos: on certain error conditions, namely after a failing M_PREPEND, in_pcbdisconnect() was not called even if a temporary in_pcbconnect() was issued before. Was that correct? I have changed this for now. As you can see, I tried to keep this simple even with the patch and changed some more in the procedure for that, too. Please correct me in case of errors, bad style or general failure to do The Right Thing. I am not an experienced kernel hacker after all. In particular, I do not know whether the fmbuf construct is good, or if we rather should duplicate that portion of code. Thanks for your patience, Thomas --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="recvdstaddr-current.diff" *** netinet/udp_usrreq.c.old Thu Nov 9 19:05:13 2000 --- netinet/udp_usrreq.c Thu Nov 9 19:23:54 2000 *************** *** 642,680 **** { register struct udpiphdr *ui; register int len = m->m_pkthdr.len; struct in_addr laddr; struct sockaddr_in *sin; ! int s = 0, error = 0; ! ! if (control) ! m_freem(control); /* XXX */ ! if (len + sizeof(struct udpiphdr) > IP_MAXPACKET) { error = EMSGSIZE; goto release; } if (addr) { sin = (struct sockaddr_in *)addr; prison_remote_ip(p, 0, &sin->sin_addr.s_addr); ! laddr = inp->inp_laddr; if (inp->inp_faddr.s_addr != INADDR_ANY) { error = EISCONN; ! goto release; } /* * Must block input while temporarily connected. */ ! s = splnet(); error = in_pcbconnect(inp, addr, p); ! if (error) { ! splx(s); ! goto release; ! } } else { if (inp->inp_faddr.s_addr == INADDR_ANY) { error = ENOTCONN; ! goto release; } } /* --- 642,741 ---- { register struct udpiphdr *ui; register int len = m->m_pkthdr.len; + register struct cmsghdr *cm = 0; struct in_addr laddr; struct sockaddr_in *sin; ! struct sockaddr_in src; ! int s = 0, error = 0, bound = 0, addrset = 0, fmbuf = 0; ! if (len + sizeof(struct udpiphdr) > IP_MAXPACKET) { error = EMSGSIZE; + if (control) + m_freem(control); goto release; } + if (control) { + /* + * XXX: Currently, we assume all the optional information is stored + * in a single mbuf. + */ + if (control->m_next) + error = EINVAL; + else { + for (; control->m_len; control->m_data += ALIGN(cm->cmsg_len), + control->m_len -= ALIGN(cm->cmsg_len)) { + cm = mtod(control, struct cmsghdr *); + if (cm->cmsg_len == 0 || cm->cmsg_len > control->m_len) { + error = EINVAL; + break; + } + if (cm->cmsg_level != IPPROTO_IP) + continue; + + switch(cm->cmsg_type) { + case IP_RECVDSTADDR: + if (cm->cmsg_len != CMSG_LEN(sizeof(struct in_addr))) { + error = EINVAL; + break; + } + laddr = inp->inp_laddr; + bzero(&src, sizeof(src)); + src.sin_family = AF_INET; + src.sin_port = inp->inp_lport; + src.sin_addr = *(struct in_addr *)CMSG_DATA(cm); + bound = 1; + s = splnet(); + if (inp->inp_laddr.s_addr == INADDR_ANY && inp->inp_lport == 0) { + /* This will check the address */ + error = in_pcbbind(inp, (struct sockaddr *)&src, p); + } else { + if (prison_ip(p, 0, &src.sin_addr.s_addr)) { + error = EINVAL; + break; + } + if (ifa_ifwithaddr((struct sockaddr *)&src) == 0) { + error = EADDRNOTAVAIL; + break; + } + inp->inp_laddr = src.sin_addr; + in_pcbrehash(inp); + } + break; + default: + error = ENOPROTOOPT; + } + if (error) + break; + } + } + m_freem(control); /* XXX */ + if (error) + goto unbind; + } + if (addr) { sin = (struct sockaddr_in *)addr; prison_remote_ip(p, 0, &sin->sin_addr.s_addr); ! if (!bound) ! laddr = inp->inp_laddr; if (inp->inp_faddr.s_addr != INADDR_ANY) { error = EISCONN; ! goto unbind; } /* * Must block input while temporarily connected. */ ! addrset=1; ! if (!bound) ! s = splnet(); error = in_pcbconnect(inp, addr, p); ! if (error) ! goto unbind; } else { if (inp->inp_faddr.s_addr == INADDR_ANY) { error = ENOTCONN; ! goto unbind; } } /* *************** *** 684,692 **** M_PREPEND(m, sizeof(struct udpiphdr), M_DONTWAIT); if (m == 0) { error = ENOBUFS; ! if (addr) ! splx(s); ! goto release; } /* --- 745,752 ---- M_PREPEND(m, sizeof(struct udpiphdr), M_DONTWAIT); if (m == 0) { error = ENOBUFS; ! /* XXX we did _not_ disconnect here before. Was that correct? Then back out! */ ! goto disconnect; } /* *************** *** 721,739 **** #ifdef IPSEC ipsec_setsocket(m, inp->inp_socket); #endif /*IPSEC*/ error = ip_output(m, inp->inp_options, &inp->inp_route, (inp->inp_socket->so_options & (SO_DONTROUTE | SO_BROADCAST)), inp->inp_moptions); ! if (addr) { in_pcbdisconnect(inp); inp->inp_laddr = laddr; /* XXX rehash? */ - splx(s); } ! return (error); ! release: ! m_freem(m); return (error); } --- 781,807 ---- #ifdef IPSEC ipsec_setsocket(m, inp->inp_socket); #endif /*IPSEC*/ + fmbuf = 1; error = ip_output(m, inp->inp_options, &inp->inp_route, (inp->inp_socket->so_options & (SO_DONTROUTE | SO_BROADCAST)), inp->inp_moptions); ! disconnect: ! if (addrset) { in_pcbdisconnect(inp); inp->inp_laddr = laddr; /* XXX rehash? */ } ! unbind: ! if (bound) { ! /* restore old state */ ! inp->inp_laddr = laddr; ! in_pcbrehash(inp); ! } ! if (addrset || bound) ! splx(s); release: ! if (!fmbuf) ! m_freem(m); return (error); } --EVF5PPMfhYS0aIcm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 12: 3: 9 2000 Delivered-To: freebsd-net@freebsd.org Received: from orthanc.ab.ca (207-167-15-66.dsl.worldgate.ca [207.167.15.66]) by hub.freebsd.org (Postfix) with ESMTP id BC1A037B479 for ; Thu, 9 Nov 2000 12:03:06 -0800 (PST) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.11.0/8.11.0.Beta3) with ESMTP id eA9K35N30738 for ; Thu, 9 Nov 2000 13:03:05 -0700 (MST) Message-Id: <200011092003.eA9K35N30738@orthanc.ab.ca> To: freebsd-net@freebsd.org Subject: Canadian dealers for Alteon Gig-E NICs Organization: The Frobozz Magic Homing Pigeon Company Date: Thu, 09 Nov 2000 13:03:05 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can any of you point me at a Canadian company that sells Alteon ACEnic Gigabit Ethernet cards? Thanks. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 12:57:42 2000 Delivered-To: freebsd-net@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id A309437B4C5 for ; Thu, 9 Nov 2000 12:57:39 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA32963; Thu, 9 Nov 2000 13:57:34 -0700 (MST) (envelope-from ken) Date: Thu, 9 Nov 2000 13:57:34 -0700 From: "Kenneth D. Merry" To: Lyndon Nerenberg Cc: freebsd-net@FreeBSD.ORG Subject: Re: Canadian dealers for Alteon Gig-E NICs Message-ID: <20001109135734.A32915@panzer.kdm.org> References: <200011092003.eA9K35N30738@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200011092003.eA9K35N30738@orthanc.ab.ca>; from lyndon@orthanc.ab.ca on Thu, Nov 09, 2000 at 01:03:05PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 09, 2000 at 13:03:05 -0700, Lyndon Nerenberg wrote: > Can any of you point me at a Canadian company that sells > Alteon ACEnic Gigabit Ethernet cards? Thanks. I would suggest getting the Netgear or 3Com boards instead. They're Alteon OEM boards, and are generally a fair bit cheaper than the price you'll get from Alteon. The Netgear GA620 boards have 512K SRAM on board, the 3Com 3c985B has 1MB SRAM on board. Netgear has a copper version out (GA620T), but I don't see a copper version of 3Com's OEM board, which would likely have 1MB SRAM. So if you want a Alteon board with a cat-5 interface, you'll probably have to go directly to Alteon. AFAIK, you can't buy Alteon-branded boards from anyone but Alteon. You'll have to call them up and talk to a salesperson. If you want fiber, a Netgear or 3Com board will do the trick. 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 Thu Nov 9 13:43:15 2000 Delivered-To: freebsd-net@freebsd.org Received: from orthanc.ab.ca (207-167-15-66.dsl.worldgate.ca [207.167.15.66]) by hub.freebsd.org (Postfix) with ESMTP id 4306B37B4CF for ; Thu, 9 Nov 2000 13:43:13 -0800 (PST) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.11.0/8.11.0.Beta3) with ESMTP id eA9Lh3N31248; Thu, 9 Nov 2000 14:43:03 -0700 (MST) Message-Id: <200011092143.eA9Lh3N31248@orthanc.ab.ca> To: "Kenneth D. Merry" Cc: freebsd-net@FreeBSD.ORG Subject: Re: Canadian dealers for Alteon Gig-E NICs In-reply-to: Your message of "Thu, 09 Nov 2000 13:57:34 MST." <20001109135734.A32915@panzer.kdm.org> Date: Thu, 09 Nov 2000 14:43:03 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Kenneth" == Kenneth D Merry writes: Kenneth> I would suggest getting the Netgear or 3Com boards Kenneth> instead. They're Alteon OEM boards, and are generally a Kenneth> fair bit cheaper than the price you'll get from Alteon. So I'm finding out. Kenneth> So if you want a Alteon board with a cat-5 interface, Kenneth> you'll probably have to go directly to Alteon. AFAIK, Kenneth> you can't buy Alteon-branded boards from anyone but Kenneth> Alteon. You'll have to call them up and talk to a Kenneth> salesperson. I did finally manage to find someone at Alteon who pointed me at a Canadian reseller. Dynavar in Calgary is saying things like CAN$1200+ for an Alteon SX card (512K). The 3C985B-SX (1MB), from the same supplier, is CAN$739. Go figure. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 14: 1:45 2000 Delivered-To: freebsd-net@freebsd.org Received: from greencreek.kappaisle.com (24.65.73.235.on.wave.home.com [24.65.73.235]) by hub.freebsd.org (Postfix) with ESMTP id 1994937B4C5; Thu, 9 Nov 2000 14:01:42 -0800 (PST) Received: from localhost (mikey@localhost) by greencreek.kappaisle.com (8.9.3/8.9.3) with ESMTP id RAA49641; Thu, 9 Nov 2000 17:18:25 -0500 (EST) (envelope-from mikey@kappaisle.com) Date: Thu, 9 Nov 2000 17:18:25 -0500 (EST) From: Mike To: freebsd-questions@freebsd.org Cc: freebsd-net@freebsd.org Subject: VPN over PPPoE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, Has anyone ever successfully configured VPN (using IPSec protocol) over PPPoE connection? I have 1 VPN configured over 2 locations with T1 connections without any problem (using the KAME IPSec on FreeBSD 4.1.1). However, when I tried the same configuration with the 3rd location running DSL, it seems the IPSec packets can't reach out via tun0 device. I've searched through the FAQ and mailing lists, and seen people suggest "pipsecd" for VPN over PPPoE. However, I do prefer using KAME IPSec for this type of implementation, and hope that someone can point me to some lights. Thank you all! Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 14: 6:22 2000 Delivered-To: freebsd-net@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id BCECC37B479 for ; Thu, 9 Nov 2000 14:06:15 -0800 (PST) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id AAA64858 for ; Fri, 10 Nov 2000 00:06:10 +0200 (EET) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id AAA00573 for ; Fri, 10 Nov 2000 00:06:05 +0200 (EET) (envelope-from petro@She.wertep.com) Date: Fri, 10 Nov 2000 00:06:05 +0200 (EET) From: petro To: FreeBSD-net@FreeBSD.ORG Subject: D-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 Hello! I have D-Link for ISA slot with such characteristics (DE-220P, DLT-2518) I don't know exactly what they mean... I would like to know what I must add ti kernel.. What is the name for the interface on such cards??? Excuse for such question... Thank you very much... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 14:13: 3 2000 Delivered-To: freebsd-net@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 9831637B4C5 for ; Thu, 9 Nov 2000 14:12:53 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA33613; Thu, 9 Nov 2000 15:12:35 -0700 (MST) (envelope-from ken) Date: Thu, 9 Nov 2000 15:12:35 -0700 From: "Kenneth D. Merry" To: Lyndon Nerenberg Cc: freebsd-net@FreeBSD.ORG Subject: Re: Canadian dealers for Alteon Gig-E NICs Message-ID: <20001109151234.A33585@panzer.kdm.org> References: <20001109135734.A32915@panzer.kdm.org> <200011092143.eA9Lh3N31248@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200011092143.eA9Lh3N31248@orthanc.ab.ca>; from lyndon@orthanc.ab.ca on Thu, Nov 09, 2000 at 02:43:03PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 09, 2000 at 14:43:03 -0700, Lyndon Nerenberg wrote: > >>>>> "Kenneth" == Kenneth D Merry writes: > > Kenneth> I would suggest getting the Netgear or 3Com boards > Kenneth> instead. They're Alteon OEM boards, and are generally a > Kenneth> fair bit cheaper than the price you'll get from Alteon. > > So I'm finding out. > > Kenneth> So if you want a Alteon board with a cat-5 interface, > Kenneth> you'll probably have to go directly to Alteon. AFAIK, > Kenneth> you can't buy Alteon-branded boards from anyone but > Kenneth> Alteon. You'll have to call them up and talk to a > Kenneth> salesperson. > > I did finally manage to find someone at Alteon who pointed me at a > Canadian reseller. Dynavar in Calgary is saying things like CAN$1200+ > for an Alteon SX card (512K). The 3C985B-SX (1MB), from the same supplier, > is CAN$739. > > Go figure. The pricing is probably designed so that Alteon isn't underselling their OEMs. The solution is to do what they want, and buy from their OEMs. :) 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 Thu Nov 9 14:25:48 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 3F14F37B479; Thu, 9 Nov 2000 14:25:41 -0800 (PST) Received: from casablanca-42.budapest.interware.hu ([195.70.53.42] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13u08I-00015o-00; Thu, 09 Nov 2000 23:25:23 +0100 Message-ID: <3A0B2436.EEC5188D@elischer.org> Date: Thu, 09 Nov 2000 14:24:54 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Cc: freebsd-questions@freebsd.org, freebsd-net@freebsd.org Subject: Re: VPN over PPPoE References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike wrote: > > Hi all, > > Has anyone ever successfully configured VPN (using IPSec protocol) over > PPPoE connection? I have 1 VPN configured over 2 locations with T1 > connections without any problem (using the KAME IPSec on FreeBSD > 4.1.1). However, when I tried the same configuration with the 3rd > location running DSL, it seems the IPSec packets can't reach out via tun0 > device. how are the T1 lines connected? more details on the pppoe connection might be good too.. do you used the netgraph pppoe or the user-land pppoe front-end? ppp over pppoe uses a slightly reduced MTU that may have something to do with it, but I doubt it.. have you tried ipsec over ppp with a dialup connection (if you have one)? maybe it's the ppp program having an argument with ipsec? (One for Brian really..) (I presume the pppoe connection is otherwise working ok).. > > I've searched through the FAQ and mailing lists, and seen people suggest > "pipsecd" for VPN over PPPoE. However, I do prefer using KAME IPSec for > this type of implementation, and hope that someone can point me to some > lights. > > Thank you all! > > Mike > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 14:46:55 2000 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 468F937B4CF; Thu, 9 Nov 2000 14:46:39 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eA9Mgfi22167; Thu, 9 Nov 2000 22:42:41 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eA9MhCB00794; Thu, 9 Nov 2000 22:43:12 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200011092243.eA9MhCB00794@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Julian Elischer Cc: Mike , freebsd-questions@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: VPN over PPPoE In-Reply-To: Message from Julian Elischer of "Thu, 09 Nov 2000 14:24:54 PST." <3A0B2436.EEC5188D@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Nov 2000 22:43:12 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Mike wrote: > > > > Hi all, > > > > Has anyone ever successfully configured VPN (using IPSec protocol) over > > PPPoE connection? I have 1 VPN configured over 2 locations with T1 > > connections without any problem (using the KAME IPSec on FreeBSD > > 4.1.1). However, when I tried the same configuration with the 3rd > > location running DSL, it seems the IPSec packets can't reach out via tun0 > > device. > > how are the T1 lines connected? > more details on the pppoe connection might be good too.. > do you used the netgraph pppoe or the user-land pppoe front-end? > > ppp over pppoe uses a slightly reduced MTU > that may have something to do with it, but I doubt it.. > > have you tried ipsec over ppp with a dialup connection (if you have > one)? > maybe it's the ppp program having an argument with ipsec? > (One for Brian really..) > (I presume the pppoe connection is otherwise working ok).. At the moment there *may* be problems with IPSEC if you've got ``nat deny_incoming yes'' in your config. If this is the case, Ruslan is about to commit a fix (I've reviewed it and given the ok w/ some ppp patches). If not, there's no known problems with ppp & IPSEC. > > I've searched through the FAQ and mailing lists, and seen people suggest > > "pipsecd" for VPN over PPPoE. However, I do prefer using KAME IPSec for > > this type of implementation, and hope that someone can point me to some > > lights. > > > > Thank you all! > > > > Mike > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000 > ---> X_.---._/ presently in: Budapest -- 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 Thu Nov 9 14:49:17 2000 Delivered-To: freebsd-net@freebsd.org Received: from greencreek.kappaisle.com (24.65.73.235.on.wave.home.com [24.65.73.235]) by hub.freebsd.org (Postfix) with ESMTP id 5B67337B4C5; Thu, 9 Nov 2000 14:49:08 -0800 (PST) Received: from localhost (mikey@localhost) by greencreek.kappaisle.com (8.9.3/8.9.3) with ESMTP id SAA49737; Thu, 9 Nov 2000 18:05:34 -0500 (EST) (envelope-from mikey@kappaisle.com) Date: Thu, 9 Nov 2000 18:05:34 -0500 (EST) From: Mike To: Julian Elischer Cc: freebsd-questions@freebsd.org, freebsd-net@freebsd.org Subject: Re: VPN over PPPoE In-Reply-To: <3A0B2436.EEC5188D@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian, I'm pretty sure that we can safely leave the T1 lines out of the equation since both T1s go to the same ISP from different locations. I suspect the problem is on the PPPoE (running Netgraph PPPoE) side because none of the IPSec packets actually go out from the tun0 device when I sniff the network. The PPPoE alone works fine and dandy, and I have set the MTU to 1492 for tun0 and both the internal and external NICs. The ADSL connection is through Bell Nexxia. I don't know if this gives you enough information about my setup, but if you'd like to know more details, I can draw the network diagram between the T1 site and the ADSL site. Thank you for your help. Mike On Thu, 9 Nov 2000, Julian Elischer wrote: > how are the T1 lines connected? > more details on the pppoe connection might be good too.. > do you used the netgraph pppoe or the user-land pppoe front-end? > > ppp over pppoe uses a slightly reduced MTU > that may have something to do with it, but I doubt it.. > > have you tried ipsec over ppp with a dialup connection (if you have > one)? > maybe it's the ppp program having an argument with ipsec? > (One for Brian really..) > (I presume the pppoe connection is otherwise working ok).. > > > -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000 > ---> X_.---._/ presently in: Budapest > v > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 15:32:47 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id A892A37B479 for ; Thu, 9 Nov 2000 15:32:44 -0800 (PST) Received: from casablanca-42.budapest.interware.hu ([195.70.53.42] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13u1BM-00062F-00; Fri, 10 Nov 2000 00:32:37 +0100 Message-ID: <3A0B33FB.5A79F70F@elischer.org> Date: Thu, 09 Nov 2000 15:32:11 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Cc: freebsd-net@freebsd.org Subject: Re: VPN over PPPoE References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike wrote: > > Julian, > > I'm pretty sure that we can safely leave the T1 lines out of the > equation since both T1s go to the same ISP from different locations. > I suspect the problem is on the PPPoE (running Netgraph PPPoE) side > because none of the IPSec packets actually go out from the tun0 device > when I sniff the network. > > The PPPoE alone works fine and dandy, and I have set the MTU to 1492 for > tun0 and both the internal and external NICs. The ADSL connection is > through Bell Nexxia. > > I don't know if this gives you enough information about my setup, but if > you'd like to know more details, I can draw the network diagram > between the T1 site and the ADSL site. > > Thank you for your help. > > Mike I was just wondering if the T1s are connected to a freebsd box or not.. :-) I think we should wait for the commit brian mentioned.. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 15:45:11 2000 Delivered-To: freebsd-net@freebsd.org Received: from greencreek.kappaisle.com (24.65.73.235.on.wave.home.com [24.65.73.235]) by hub.freebsd.org (Postfix) with ESMTP id E450C37B479 for ; Thu, 9 Nov 2000 15:45:06 -0800 (PST) Received: from localhost (mikey@localhost) by greencreek.kappaisle.com (8.9.3/8.9.3) with ESMTP id TAA49989; Thu, 9 Nov 2000 19:01:48 -0500 (EST) (envelope-from mikey@kappaisle.com) Date: Thu, 9 Nov 2000 19:01:48 -0500 (EST) From: Mike To: Julian Elischer Cc: freebsd-net@freebsd.org Subject: Re: VPN over PPPoE In-Reply-To: <3A0B33FB.5A79F70F@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Julian and all, Guess we all just have to wait for the patch ^_^ Thank you very much for your generous help. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 15:47: 7 2000 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 7FD9637B479 for ; Thu, 9 Nov 2000 15:47:02 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eA9Nj4i22421; Thu, 9 Nov 2000 23:45:04 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eA9NjXB01411; Thu, 9 Nov 2000 23:45:33 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200011092345.eA9NjXB01411@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Julian Elischer Cc: Mike , freebsd-net@FreeBSD.org, brian@Awfulhak.org Subject: Re: VPN over PPPoE In-Reply-To: Message from Julian Elischer of "Thu, 09 Nov 2000 15:32:11 PST." <3A0B33FB.5A79F70F@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Nov 2000 23:45:33 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Mike wrote: > > > > Julian, > > > > I'm pretty sure that we can safely leave the T1 lines out of the > > equation since both T1s go to the same ISP from different locations. > > I suspect the problem is on the PPPoE (running Netgraph PPPoE) side > > because none of the IPSec packets actually go out from the tun0 device > > when I sniff the network. > > > > The PPPoE alone works fine and dandy, and I have set the MTU to 1492 for > > tun0 and both the internal and external NICs. The ADSL connection is > > through Bell Nexxia. > > > > I don't know if this gives you enough information about my setup, but if > > you'd like to know more details, I can draw the network diagram > > between the T1 site and the ADSL site. > > > > Thank you for your help. > > > > Mike > > I was just wondering if the T1s are connected to a freebsd box or not.. > :-) > I think we should wait for the commit brian mentioned.. Or try toggling ``nat deny_incoming yes'' :-) > -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000 > ---> X_.---._/ presently in: Budapest > v -- 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 Thu Nov 9 21:49:16 2000 Delivered-To: freebsd-net@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id C11F837B479 for ; Thu, 9 Nov 2000 21:49:13 -0800 (PST) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G3S0024ZO60HG@falla.videotron.net> for freebsd-net@freebsd.org; Fri, 10 Nov 2000 00:49:12 -0500 (EST) Date: Fri, 10 Nov 2000 00:54:09 -0500 (EST) From: Bosko Milekic Subject: M_RDONLY: review & comment X-Sender: bmilekic@jehovah.technokratis.com To: freebsd-net@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, It's been about 4 months since this was last discussed... The updated and merged diff adding M_RDONLY flag for mbufs is now available here: http://people.freebsd.org/~bmilekic/mb_rdonly.diff Please review and comment. It does the following: * Adds M_RDONLY flag for mbufs, which basically means "don't tamper with my data region." A macro, M_WRITABLE() is provided which will evaluate true if: (a) mbuf does not have M_RDONLY bit set in its flags ...and... (b) either: (i) mbuf is "regular" mbuf with no ext_buf (i.e. no M_EXT) or (ii) mbuf is M_EXT and reference count is not above 1. Hopefully this will replace all the scattered "is this mbuf writable" checks, at least eventually. * m_pulldown() ; replaced "sharedcluster" variable with one called "writable." This code is still somewhat flawed. Checkout the comment in the diff for a good explanation on how it works and what still needs to be done. But, a decent start on using M_WRITABLE() to determine "writability." * Added m_ext.ext_type which holds either EXT_CLUSTER, EXT_SFBUF, ... better than checking whether there is an installed ext_free to determine whether ext_buf is cluster. * Made sendfile(2)'s sf_bufs explicitly make their buffers M_RDONLY to the mbuf system. If M_WRITABLE() is used on an mbuf with an sf_buf for an ext_buf, then it will never evaluate "writable," but always "read-only." * Small tiny tiny fix in netinet/ip_fil.c, diff is self-explanatory. * netinet6/ipsec.c should probably eventually be checked out (see diff for exact spot where) to be made to use M_WRITABLE as an approach to determining whether to make a copy or not... wasn't 100% sure on what to do with it immediately. I think that's it. It's really not that much and the diff is a mere 10K. Reviews and comments welcomed, I'd like to commit this soon and get the PR closed, unless anyone has objections. dwmalone, anything to add? (I modified the behavior in m_pulldown() just a bit w.r.t. the original patch, so feel free to glance at that). Cheers, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 9 22:55:50 2000 Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 72FFF37B479 for ; Thu, 9 Nov 2000 22:55:46 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13u86y-0000U1-00; Thu, 09 Nov 2000 23:56:32 -0700 Message-ID: <3A0B9C20.F137736D@softweyr.com> Date: Thu, 09 Nov 2000 23:56:32 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: Lyndon Nerenberg , freebsd-net@FreeBSD.ORG Subject: Re: Canadian dealers for Alteon Gig-E NICs References: <20001109135734.A32915@panzer.kdm.org> <200011092143.eA9Lh3N31248@orthanc.ab.ca> <20001109151234.A33585@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote: > > On Thu, Nov 09, 2000 at 14:43:03 -0700, Lyndon Nerenberg wrote: > > >>>>> "Kenneth" == Kenneth D Merry writes: > > > > Kenneth> I would suggest getting the Netgear or 3Com boards > > Kenneth> instead. They're Alteon OEM boards, and are generally a > > Kenneth> fair bit cheaper than the price you'll get from Alteon. > > > > So I'm finding out. > > > > Kenneth> So if you want a Alteon board with a cat-5 interface, > > Kenneth> you'll probably have to go directly to Alteon. AFAIK, > > Kenneth> you can't buy Alteon-branded boards from anyone but > > Kenneth> Alteon. You'll have to call them up and talk to a > > Kenneth> salesperson. > > > > I did finally manage to find someone at Alteon who pointed me at a > > Canadian reseller. Dynavar in Calgary is saying things like CAN$1200+ > > for an Alteon SX card (512K). The 3C985B-SX (1MB), from the same supplier, > > is CAN$739. > > > > Go figure. > > The pricing is probably designed so that Alteon isn't underselling their > OEMs. The solution is to do what they want, and buy from their OEMs. :) NetGear GA620T, CDN $529.99 at www.microwarehouse.ca. Searching google for "NetGear GA620T Canada" turned up mostly references to FreeBSD. ;^) -- "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 Nov 9 22:58:57 2000 Delivered-To: freebsd-net@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id B7C3E37B479 for ; Thu, 9 Nov 2000 22:58:54 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA36958; Thu, 9 Nov 2000 23:58:43 -0700 (MST) (envelope-from ken) Date: Thu, 9 Nov 2000 23:58:43 -0700 From: "Kenneth D. Merry" To: Wes Peters Cc: Lyndon Nerenberg , freebsd-net@FreeBSD.ORG Subject: Re: Canadian dealers for Alteon Gig-E NICs Message-ID: <20001109235843.A36934@panzer.kdm.org> References: <20001109135734.A32915@panzer.kdm.org> <200011092143.eA9Lh3N31248@orthanc.ab.ca> <20001109151234.A33585@panzer.kdm.org> <3A0B9C20.F137736D@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A0B9C20.F137736D@softweyr.com>; from wes@softweyr.com on Thu, Nov 09, 2000 at 11:56:32PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 09, 2000 at 23:56:32 -0700, Wes Peters wrote: > "Kenneth D. Merry" wrote: > > On Thu, Nov 09, 2000 at 14:43:03 -0700, Lyndon Nerenberg wrote: > > > I did finally manage to find someone at Alteon who pointed me at a > > > Canadian reseller. Dynavar in Calgary is saying things like CAN$1200+ > > > for an Alteon SX card (512K). The 3C985B-SX (1MB), from the same supplier, > > > is CAN$739. > > > > > > Go figure. > > > > The pricing is probably designed so that Alteon isn't underselling their > > OEMs. The solution is to do what they want, and buy from their OEMs. :) > > NetGear GA620T, CDN $529.99 at www.microwarehouse.ca. The Netgear boards only have 512K SRAM, thus the reason for the lower price. > Searching google for "NetGear GA620T Canada" turned up mostly references to > FreeBSD. ;^) :) 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 Thu Nov 9 23:21:17 2000 Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id B9F4637B4D7 for ; Thu, 9 Nov 2000 23:21:13 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13u8Vl-0000Vm-00; Fri, 10 Nov 2000 00:22:09 -0700 Message-ID: <3A0BA221.F094A400@softweyr.com> Date: Fri, 10 Nov 2000 00:22:09 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: Lyndon Nerenberg , freebsd-net@FreeBSD.ORG Subject: Re: Canadian dealers for Alteon Gig-E NICs References: <20001109135734.A32915@panzer.kdm.org> <200011092143.eA9Lh3N31248@orthanc.ab.ca> <20001109151234.A33585@panzer.kdm.org> <3A0B9C20.F137736D@softweyr.com> <20001109235843.A36934@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote: > > On Thu, Nov 09, 2000 at 23:56:32 -0700, Wes Peters wrote: > > > > NetGear GA620T, CDN $529.99 at www.microwarehouse.ca. > > The Netgear boards only have 512K SRAM, thus the reason for the lower price. Unless you have a fast machine with a 64bit or 66Mhz PCI slot, the 620T will give you all the performance you can get out of an average PC. Not the extreme of performance, but well worth the price. > > Searching google for "NetGear GA620T Canada" turned up mostly references to > > FreeBSD. ;^) > > :) -- "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 Nov 9 23:56: 2 2000 Delivered-To: freebsd-net@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id AB62B37B4CF for ; Thu, 9 Nov 2000 23:55:59 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA37245; Fri, 10 Nov 2000 00:55:50 -0700 (MST) (envelope-from ken) Date: Fri, 10 Nov 2000 00:55:50 -0700 From: "Kenneth D. Merry" To: Wes Peters Cc: Lyndon Nerenberg , freebsd-net@FreeBSD.ORG Subject: Re: Canadian dealers for Alteon Gig-E NICs Message-ID: <20001110005550.A37221@panzer.kdm.org> References: <20001109135734.A32915@panzer.kdm.org> <200011092143.eA9Lh3N31248@orthanc.ab.ca> <20001109151234.A33585@panzer.kdm.org> <3A0B9C20.F137736D@softweyr.com> <20001109235843.A36934@panzer.kdm.org> <3A0BA221.F094A400@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A0BA221.F094A400@softweyr.com>; from wes@softweyr.com on Fri, Nov 10, 2000 at 12:22:09AM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Nov 10, 2000 at 00:22:09 -0700, Wes Peters wrote: > "Kenneth D. Merry" wrote: > > > > On Thu, Nov 09, 2000 at 23:56:32 -0700, Wes Peters wrote: > > > > > > NetGear GA620T, CDN $529.99 at www.microwarehouse.ca. > > > > The Netgear boards only have 512K SRAM, thus the reason for the lower price. > > Unless you have a fast machine with a 64bit or 66Mhz PCI slot, the 620T will > give you all the performance you can get out of an average PC. Not the > extreme of performance, but well worth the price. The extra memory is worth another 20-30Mbps of performance, IIRC. Even on a PC with 32 bit 33MHz PCI. You're right, though, the performance you'll get from the 512K boards is well worth the price. 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 Fri Nov 10 0:43:47 2000 Delivered-To: freebsd-net@freebsd.org Received: from aifhs8.alcatel.fr (aifhs8.alcatel.fr [212.208.74.153]) by hub.freebsd.org (Postfix) with ESMTP id 77D7837B4C5 for ; Fri, 10 Nov 2000 00:43:42 -0800 (PST) Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs8.alcatel.fr (ALCANET/SMTP2) with SMTP id JAA13572 for ; Fri, 10 Nov 2000 09:43:39 +0100 (MET) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id C1256993.002FEA90 ; Fri, 10 Nov 2000 09:43:22 +0100 X-Lotus-FromDomain: ALCATEL From: Thierry.Herbelot@alcatel.fr To: freebsd-net@freebsd.org Message-ID: Date: Fri, 10 Nov 2000 09:26:36 +0100 Subject: 16 NICs on a Compaq PC ? Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I'm trying to build a low-cost Ethernet router with a Compaq Deskpro EP-6450 and 4 4-port NIC from DLINK (DFE-570-TX model) I'm using the dc driver for a 4.1.1-Release. the performance is very disappointing (the throughput is on the order of 200 kpbs for a direct 100Mbps ful-duplex Ethernet link) I've got messages "dc0 : TX underrun -- increasing TX threshold" (lots of them ..) I've also seen that all dc ports get mapped to the same irq (nr 11), and when I try to change this setting, the machine stops booting (I have to try with WinNT) 1st Q : is there a performance hit with all ports tied to the single irq11 ? (my gut feeling would be "of course", I'd like to be sure) 2nd Q : has someone built a similar configuration ? 3rd Q : do I need to dump all the Compaqs to buy other, more standard machines ? TfH PS1 : PS2 : sinppet of the dmesg : .... dc0: port 0x4000-0x407f mem 0x40c00000-0x40c003ff irq 11 at device 4.0 on pci2 dc0: Ethernet address: 00:80:c8:f8:4c:4d miibus0: on dc0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc1: port00x4080-0x40ff mem 0x40d00000-0x40d003ff irq 11 at device 5.0 on pci2 dc1: Ethernet address: 00:80:c8:f8:4c:4e mii\M-bus1: on dc1 ukphy1: on miibus1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc2: port 0x4400-0x447f mem 0x40e00000-0x40e003ff irq 11 at device 6.0 on pci2 dc2: Ethernet address: 00:80:c8:f8:4c:4f miibus2: on dc2 ukphy2: on miibus2 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc3: port 0x4480-0x44ff mem 0x40f00000-0x40f003ff irq .... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 10 1:29:23 2000 Delivered-To: freebsd-net@freebsd.org Received: from smtp.huawei.com (unknown [202.96.135.132]) by hub.freebsd.org (Postfix) with ESMTP id 9421A37B4C5 for ; Fri, 10 Nov 2000 01:29:15 -0800 (PST) Received: from w07542 ([10.105.34.27]) by smtp.huawei.com (Netscape Messaging Server 4.15) with SMTP id G3SXVD03.714 for ; Fri, 10 Nov 2000 17:18:49 +0800 Message-ID: <000e01c04af8$91352d20$1b22690a@huawei.com.cn> From: "wu haijun" To: Subject: A question for PPPoE 's MTU: Date: Fri, 10 Nov 2000 17:28:20 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C04B3B.9EEC16C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C04B3B.9EEC16C0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 VGhlIE1UVSBvZiBQUFBvRSBpcyAxNDkyIEJ5dGVzLiBCdXQgaWYgdGhlIFBQUG9FIFNlcnZlciBy ZWNlaXZlcyBJUCAgcGFja2V0cyBmcm9tIHRoZSBXQU4gYW5kIHRoZSBwYWNrZXRzJ3MgIHdpbGwg YmUgYWx3YXlzIDE1MTQgQnl0ZXMsc28gdGhlIFNlcnZlciBtdXN0IGZyYWdtZW50IHRoZSBQYWNr ZXRzIHRvIGZpdCBpbiB0aGUgUFBQb0UgcGFja2V0cyAsYW5kIHRoaXMgd2lsbCBkZWdyYWRlIHRo ZSBwZXJmb3JtYW5jZSBvZiB0aGUgU2VydmVyLg0K ------=_NextPart_000_000B_01C04B3B.9EEC16C0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8 Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5UaGUgTVRVJm5ic3A7b2Yg UFBQb0UgaXMgMTQ5MiBCeXRlcy4gQnV0Jm5ic3A7aWYgdGhlIFBQUG9FIA0KU2VydmVyIHJlY2Vp dmVzIElQJm5ic3A7IHBhY2tldHMgZnJvbSB0aGUgV0FOIGFuZCB0aGUgcGFja2V0cydzICB3aWxs IGJlIGFsd2F5cyANCjE1MTQgQnl0ZXMsc28gdGhlIFNlcnZlciBtdXN0IGZyYWdtZW50IHRoZSBQ YWNrZXRzJm5ic3A7dG8gZml0IGluIHRoZSBQUFBvRSANCnBhY2tldHMgLGFuZCB0aGlzIHdpbGwg ZGVncmFkZSB0aGUgcGVyZm9ybWFuY2Ugb2YgdGhlIA0KU2VydmVyLjwvRk9OVD48L0RJVj48L0JP RFk+PC9IVE1MPg0K ------=_NextPart_000_000B_01C04B3B.9EEC16C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 10 1:50:58 2000 Delivered-To: freebsd-net@freebsd.org Received: from smtp.huawei.com (unknown [202.96.135.132]) by hub.freebsd.org (Postfix) with ESMTP id 56ED837B479 for ; Fri, 10 Nov 2000 01:50:49 -0800 (PST) Received: from w07542 ([10.105.34.27]) by smtp.huawei.com (Netscape Messaging Server 4.15) with SMTP id G3SYVN00.90V for ; Fri, 10 Nov 2000 17:40:35 +0800 Message-ID: <001f01c04afb$9b6e07a0$1b22690a@huawei.com.cn> From: "wu haijun" To: Subject: A question for PPPoE 's MTU: Date: Fri, 10 Nov 2000 17:50:06 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01C04B3E.A96FB5E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_001C_01C04B3E.A96FB5E0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGk6DQoNClRoZSBNVFUgb2YgUFBQb0UgaXMgMTQ5MiBCeXRlcy4gQnV0IGlmIHRoZSBQUFBvRSBT ZXJ2ZXIgcmVjZWl2ZXMgSVAgIHBhY2tldHMgZnJvbSB0aGUgV0FOIGFuZCB0aGUgcGFja2V0cydz IHdpbGwgYmUgYWx3YXlzIDE1MTQgQnl0ZXMsc28gdGhlIFNlcnZlciBtdXN0IGZyYWdtZW50IHRo ZSBQYWNrZXRzIHRvIGZpdCBpbiB0aGUgUFBQb0UgcGFja2V0cyAsYW5kIHRoaXMgd2lsbCBkZWdy YWRlIHRoZSBwZXJmb3JtYW5jZSBvZiB0aGUgU2VydmVyLg0KV2h5IG5vdCBzdWdnZXN0IHRoYXQg UFBQb0UgaGVhZGVyIGRpZG4ndCBiZSBpbmNsdWRlZCBpbiB0aGUgTVRVIGNhbGN1bGF0aW9uLGp1 c3QgbGlrZSBWTEFOIGVuY2Fwc3VsYXRpb24/IA0KDQpSZWdhcmRzDQoNCld1IEhhaWp1bg0KSHVh d2VpIFRlY2guIENvcnAuIExURCAgaW4gQ0hJTkENClNlbmlvciBGaXJtd2FyZSBFbmdpbmVlcg0K DQoNCg== ------=_NextPart_000_001C_01C04B3E.A96FB5E0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8 Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj4NCjxESVY+PEZPTlQgc2l6 ZT0yPkhpOjwvRk9OVD48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9 Mj5UaGUgTVRVJm5ic3A7b2YgUFBQb0UgaXMgMTQ5MiBCeXRlcy4gQnV0Jm5ic3A7aWYgdGhlIFBQ UG9FIA0KU2VydmVyIHJlY2VpdmVzIElQJm5ic3A7IHBhY2tldHMgZnJvbSB0aGUgV0FOIGFuZCB0 aGUgcGFja2V0cydzIHdpbGwgYmUgYWx3YXlzIA0KMTUxNCBCeXRlcyxzbyB0aGUgU2VydmVyIG11 c3QgZnJhZ21lbnQgdGhlIFBhY2tldHMmbmJzcDt0byBmaXQgaW4gdGhlIFBQUG9FIA0KcGFja2V0 cyAsYW5kIHRoaXMgd2lsbCBkZWdyYWRlIHRoZSBwZXJmb3JtYW5jZSBvZiB0aGUgU2VydmVyLjwv Rk9OVD48L0RJVj4NCjxESVY+V2h5IG5vdCBzdWdnZXN0IHRoYXQgUFBQb0UgaGVhZGVyIGRpZG4n dCBiZSBpbmNsdWRlZCBpbiB0aGUgTVRVIA0KY2FsY3VsYXRpb24sanVzdCBsaWtlIFZMQU4gZW5j YXBzdWxhdGlvbj8gPC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5SZWdhcmRzPC9ESVY+ DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5XdSBIYWlqdW48L0RJVj4NCjxESVY+SHVhd2VpIFRl Y2guIENvcnAuIExURCZuYnNwOyZuYnNwO2luIENISU5BPC9ESVY+DQo8RElWPlNlbmlvciBGaXJt d2FyZSBFbmdpbmVlcjxCUj48QlI+PC9ESVY+PC9GT05UPjwvRElWPjwvQk9EWT48L0hUTUw+DQo= ------=_NextPart_000_001C_01C04B3E.A96FB5E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 10 7: 7:44 2000 Delivered-To: freebsd-net@freebsd.org Received: from css-1.cs.iastate.edu (css-1.cs.iastate.edu [129.186.3.24]) by hub.freebsd.org (Postfix) with ESMTP id D12E037B479 for ; Fri, 10 Nov 2000 07:07:41 -0800 (PST) Received: from popeye.cs.iastate.edu (ghelmer@popeye.cs.iastate.edu [129.186.3.4]) by css-1.cs.iastate.edu (8.9.0/8.9.0) with ESMTP id JAA16241 for ; Fri, 10 Nov 2000 09:07:41 -0600 (CST) Received: from localhost (ghelmer@localhost) by popeye.cs.iastate.edu (8.9.0/8.9.0) with ESMTP id JAA10092 for ; Fri, 10 Nov 2000 09:07:39 -0600 (CST) X-Authentication-Warning: popeye.cs.iastate.edu: ghelmer owned process doing -bs Date: Fri, 10 Nov 2000 09:07:39 -0600 (CST) From: Guy Helmer To: net@freebsd.org Subject: "arp: XX is on xx0 but got reply from YY on yy0" message 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'm working with a situation where a machine will have two interfaces on the same Ethernet segment. One interface does not have an IP address and is in promiscuous mode to listen to the segment; the other interface has an IP address and is running normally. The kernel logs a lot of "arp: XX is on xx0 but got reply from YY on yy0" messages. Questions also appear on the FreeBSD lists asking about this message when people have multiple interfaces in different IP subnets on the same wire. From reading the source in for in_arpinput() in /sys/netinet/if_ether.c, it appears that the kernel just logs this message and harmlessly tosses the packet. If this *is* harmless, would it be OK to make the log message conditional on a sysctl toggle? Guy Guy Helmer, Ph.D. Candidate, Iowa State University Dept. of Computer Science Research Assistant, Dept. of Computer Science --- ghelmer@cs.iastate.edu http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 10 7:22:28 2000 Delivered-To: freebsd-net@freebsd.org Received: from apollo.ocsny.com (apollo.ocsny.com [204.107.76.2]) by hub.freebsd.org (Postfix) with ESMTP id 91CAE37B479 for ; Fri, 10 Nov 2000 07:22:26 -0800 (PST) Received: from upan.org (thoth.upan.org [204.107.76.16]) by apollo.ocsny.com (8.9.2/8.9.3) with ESMTP id KAA61968; Fri, 10 Nov 2000 10:22:35 -0500 (EST) Message-ID: <3A0C1163.82FDA989@upan.org> Date: Fri, 10 Nov 2000 10:16:51 -0500 From: Mikel Reply-To: mikel@upan.org X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en,it MIME-Version: 1.0 To: Guy Helmer Cc: net@FreeBSD.ORG Subject: Re: "arp: XX is on xx0 but got reply from YY on yy0" message References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org could you maybe send a copy (or a mock copy) of your rc.conf files? Guy Helmer wrote: > I'm working with a situation where a machine will have two interfaces on > the same Ethernet segment. One interface does not have an IP address and > is in promiscuous mode to listen to the segment; the other interface has > an IP address and is running normally. The kernel logs a lot of "arp: XX > is on xx0 but got reply from YY on yy0" messages. > > Questions also appear on the FreeBSD lists asking about this message when > people have multiple interfaces in different IP subnets on the same wire. > > >From reading the source in for in_arpinput() in > /sys/netinet/if_ether.c, it appears that the kernel just logs this message > and harmlessly tosses the packet. If this *is* harmless, would it be OK > to make the log message conditional on a sysctl toggle? > > Guy > > Guy Helmer, Ph.D. Candidate, Iowa State University Dept. of Computer Science > Research Assistant, Dept. of Computer Science --- ghelmer@cs.iastate.edu > http://www.cs.iastate.edu/~ghelmer > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 10 7:23:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from bdc.orlando.tradeweb.net (ns.tradeweb.net [206.228.208.10]) by hub.freebsd.org (Postfix) with ESMTP id 4BC8437B479 for ; Fri, 10 Nov 2000 07:23:22 -0800 (PST) Received: by bdc.orlando.tradeweb.net with Internet Mail Service (5.5.2650.21) id ; Fri, 10 Nov 2000 10:47:48 -0500 Message-ID: <71E79DA61328D311B4D10020AFF78E4218D953@bdc.orlando.tradeweb.net> From: John Congdon To: "'freebsd-net@freebsd.org'" Subject: MPD question Date: Fri, 10 Nov 2000 10:47:46 -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 using mpd to do dial-in PPP. It works GREAT except when I disconnect, the server does not drop the connection. When I redial it just rings. Here is a snippet of mpd. Starts to close, says waiting for ring... but continues as if it is still open. [usr] device: DOWN event in state CLOSING [usr] device is now in state DOWN [usr] link: DOWN event [usr] LCP: Down event [usr] LCP: state change Stopped --> Starting [usr] LCP: phase shift ESTABLISH --> DEAD [usr] LCP: LayerStart [usr] device: OPEN event in state DOWN [usr] pausing 7 seconds before open [usr] device is now in state DOWN [usr] device: OPEN event in state DOWN [usr] device is now in state DOWN [dialin] closing link "usr"... [usr] link: CLOSE event [usr] LCP: Close event [usr] LCP: state change Starting --> Initial [usr] LCP: LayerFinish [usr] device: CLOSE event in state DOWN [usr] device is now in state DOWN mpd: empty auth name [usr] chat: Waiting for ring... [dialin] opening link "usr"... [usr] link: OPEN event [usr] LCP: Open event [usr] LCP: state change Initial --> Starting [usr] LCP: LayerStart [usr] device: OPEN event in state DOWN [usr] pausing 3 seconds before open [usr] device is now in state DOWN Thank you for any help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 10 9:39:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail2.netvision.com.br (nv37.netvision.com.br [200.215.94.37]) by hub.freebsd.org (Postfix) with ESMTP id F04AE37B479 for ; Fri, 10 Nov 2000 09:39:45 -0800 (PST) Received: from nv12.netvision.com.br (nv12.netvision.com.br [200.247.217.134]) by mail2.netvision.com.br (Postfix) with SMTP id 2E204177E for ; Fri, 10 Nov 2000 15:39:17 -0200 (BST) From: =?iso-8859-1?q?Andr=E9=20Luiz=20dos=20Santos?= Reply-To: andre@netvision.com.br Date: Fri, 10 Nov 2000 15:40:40 +0000 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" To: 'freebsd-net@freebsd.org' Subject: BreezeNet Wireless MIME-Version: 1.0 Message-Id: <00111015404002.16098@nv12.netvision.com.br> Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi... Does anybody knows where can I find FreeBSD drivers for the BreezeNet=20 PRO.11 Series SA-PCD Wireless LAN Adapter? Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 10 10:44:32 2000 Delivered-To: freebsd-net@freebsd.org Received: from herbelot.dyndns.org (s014.dhcp212-24.cybercable.fr [212.198.24.14]) by hub.freebsd.org (Postfix) with ESMTP id BFAD537B479 for ; Fri, 10 Nov 2000 10:44:28 -0800 (PST) Received: from cybercable.fr (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id TAA42963 for ; Fri, 10 Nov 2000 19:44:27 +0100 (CET) (envelope-from herbelot@cybercable.fr) Message-ID: <3A0C420A.F9446B74@cybercable.fr> Date: Fri, 10 Nov 2000 19:44:26 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-net@FreeBSD.ORG Subject: Re: 16 NICs on a Compaq PC ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org for reference only : the problem came from using 4 4-port boards in a single machine (seems that the 4th PCI slot does not like the DFE-570TX) I have a good performance with just 3 NICs for a total of 12 Ethernet ports per machine. TfH Thierry.Herbelot@alcatel.fr wrote: > > Hello, > > I'm trying to build a low-cost Ethernet router with a Compaq Deskpro > EP-6450 and 4 4-port NIC from DLINK (DFE-570-TX model) > > I'm using the dc driver for a 4.1.1-Release. > > the performance is very disappointing (the throughput is on the order of > 200 kpbs for a direct 100Mbps ful-duplex Ethernet link) > > I've got messages "dc0 : TX underrun -- increasing TX threshold" (lots of them ..) > > I've also seen that all dc ports get mapped to the same irq (nr 11), and when > I try to change this setting, the machine stops booting (I have to try with WinNT) > > 1st Q : is there a performance hit with all ports tied to the single irq11 ? (my gut feeling > would be "of course", I'd like to be sure) > 2nd Q : has someone built a similar configuration ? > 3rd Q : do I need to dump all the Compaqs to buy other, more standard machines ? > > TfH > PS1 : > PS2 : sinppet of the dmesg : > .... > dc0: port 0x4000-0x407f mem 0x40c00000-0x40c003ff irq > 11 at device 4.0 on pci2 > dc0: Ethernet address: 00:80:c8:f8:4c:4d > miibus0: on dc0 > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > dc1: port00x4080-0x40ff mem 0x40d00000-0x40d003ff irq > 11 at device 5.0 on pci2 > dc1: Ethernet address: 00:80:c8:f8:4c:4e > mii\M-bus1: on dc1 > ukphy1: on miibus1 > ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > dc2: port 0x4400-0x447f mem 0x40e00000-0x40e003ff irq > 11 at device 6.0 on pci2 > dc2: Ethernet address: 00:80:c8:f8:4c:4f > miibus2: on dc2 > ukphy2: on miibus2 > ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > dc3: port 0x4480-0x44ff mem 0x40f00000-0x40f003ff irq > .... -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 10 13:14:36 2000 Delivered-To: freebsd-net@freebsd.org Received: from skeezix.n0qds.org (skeezix.n0qds.org [204.246.69.106]) by hub.freebsd.org (Postfix) with ESMTP id 3B91337B4C5 for ; Fri, 10 Nov 2000 13:14:32 -0800 (PST) Received: by skeezix.n0qds.org (Postfix, from userid 501) id 1868E14DC; Fri, 10 Nov 2000 15:14:21 -0600 (CST) Date: Fri, 10 Nov 2000 15:14:21 -0600 From: Greg Putrich To: dg@root.com Cc: freebsd-net@freebsd.org Subject: Re: Intel(R) PRO/XX Adapters .. Message-ID: <20001110151421.I20916@skeezix.n0qds.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 According to the source (if_wx.c), it's for the Intel 82452 chip. The PRO/1000 (F&T) uses the 82543GC. I have a PRO/1000 F and it's not being detected by FreeBSD-RELEASE 4.1.1. Also have some form of PRO/100 and that works fine (used by fxp driver). Hopefully soon these PRO/1000's will work... hoping it's a case where I forgot something simple. >>Morning all ... >> >> Just picked up a Netfinity 7100 to act as a proxy server, running >>FreeBSD 4.x, and hit a rut in the road I wasn't expecting ... my Intel >>EtherExpress card isn't supported by the hardware itself :( >> >> I have a choice of 4 cards that I can run, and am curious as to >>whether any of them will be supported, and if anyone has any caveats about >>any, before I order them ... >> >>PILA8470 - Intel(R) PRO/100+ Server Adapter >>PILA8472 - Intel(R) PRO/100+ Dual Port Server Adapter >>PWLA8490 - Intel(R) PRO/1000 Gigabit Server Adapter >>PILA8480 - Intel(R) PRO/100 Intelligent Server Adapter > > Actually, all of the above should work - are you saying that you've tried >and they don't work? The Pro/1000 should work with the wx driver and the >others should work with the fxp driver. > >-DG > David Greenman -- -------------------------------------------------------------------------- Greg Putrich - Internet: gregp@n0qds.org [sk] "I will not be pushed, filed, stamped, indexed, briefed, debriefed, or numbered. My life is my own." - No. 6 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 10 14:12:37 2000 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id C5AA537B479 for ; Fri, 10 Nov 2000 14:12:16 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eAAMAji28823; Fri, 10 Nov 2000 22:10:45 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eAAMAj062544; Fri, 10 Nov 2000 22:10:45 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200011102210.eAAMAj062544@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "wu haijun" Cc: freebsd-net@freebsd.org, brian@Awfulhak.org Subject: Re: A question for PPPoE 's MTU: In-Reply-To: Message from "wu haijun" of "Fri, 10 Nov 2000 17:50:06 +0800." <001f01c04afb$9b6e07a0$1b22690a@huawei.com.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 10 Nov 2000 22:10:45 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org haggai.wu@huawei.com said: > Hi: > = > The MTU=A0of PPPoE is 1492 Bytes. But=A0if the PPPoE Server receives > IP=A0 packets from the WAN and the packets's will be always 1514 > Bytes,so the Server must fragment the Packets=A0to fit in the PPPoE > packets ,and this will degrade the performance of the Server. > = > Why not suggest that PPPoE header didn't be included in the MTU > calculation, just like VLAN encapsulation? The 1492 MTU limit is imposed because the PPPoE header is 8 bytes = big. The total header + data cannot exceed 1500 - the maximum = ethernet payload. > Regards > = > Wu Haijun > Huawei Tech. Corp. LTD=A0=A0in CHINA > Senior Firmware Engineer -- = 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 Nov 10 15:32:15 2000 Delivered-To: freebsd-net@freebsd.org Received: from mario.zyan.com (mario.zyan.com [209.250.96.140]) by hub.freebsd.org (Postfix) with ESMTP id 9046237B479 for ; Fri, 10 Nov 2000 15:32:13 -0800 (PST) Received: from dopey.weyrich.com (orville@node-64-249-12-250.dslspeed.zyan.com [64.249.12.250]) by mario.zyan.com (8.9.3/8.9.3) with ESMTP id PAA75943 for ; Fri, 10 Nov 2000 15:32:12 -0800 (PST) (envelope-from orville@weyrich.com) Received: from localhost (orville@localhost) by dopey.weyrich.com (8.9.3/8.6.9) with ESMTP id QAA13523 for ; Fri, 10 Nov 2000 16:43:10 -0700 Date: Fri, 10 Nov 2000 16:43:10 -0700 (MST) From: "Orville R. Weyrich.Jr" Cc: freebsd-net@FreeBSD.ORG Subject: Free list browser. In-Reply-To: <200011102210.eAAMAj062544@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 Does anyone know of a tool for browsing the free list of a FreeBSD (or OpenBSD) file system to view what is in the list of free blocks (ideally, reporting the disk coordinates as well)? Thanks orville. ------------------------------------------------------------------- Orville R. Weyrich, Jr. Weyrich Computer Consulting mailto:orville@weyrich.com KD7HJV http://www.weyrich.com ------------------------------------------------------------------- Visit our online collection of book reviews: http://www.weyrich.com/book_reviews/ Ask about our world wide web services! ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 10 21:10:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from hetnet.nl (net047s.hetnet.nl [194.151.104.151]) by hub.freebsd.org (Postfix) with ESMTP id 1FA8737B479 for ; Fri, 10 Nov 2000 21:10:23 -0800 (PST) Received: from alias ([63.201.230.193]) by hetnet.nl with Microsoft SMTPSVC(5.5.1877.537.53); Sat, 11 Nov 2000 06:10:19 +0100 Message-ID: <003301c04b9d$2cde51d0$0a00a8c0@alias> From: "Wilbert de Graaf" To: "wu haijun" Cc: References: <001f01c04afb$9b6e07a0$1b22690a@huawei.com.cn> Subject: Re: A question for PPPoE 's MTU: Date: Fri, 10 Nov 2000 21:06:38 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Wu, I remember this problem when we implemented an IP aggregator behind our terminal servers. We configured our servers to respond with packet telling the client to start over again and use smaller, not fragmented, ip packets. This definitely improved performance. I think this is rfc879 (The TCP Maximum Segment Size) related. I don't remember how we did it but I believe just setting the MTU on that interface to 1492 in your case, and set don't fragment. - Wilbert ----- Original Message ----- From: wu haijun To: freebsd-net@freebsd.org Sent: Friday, November 10, 2000 1:50 AM Subject: A question for PPPoE 's MTU: Hi: The MTU of PPPoE is 1492 Bytes. But if the PPPoE Server receives IP packets from the WAN and the packets's will be always 1514 Bytes,so the Server must fragment the Packets to fit in the PPPoE packets ,and this will degrade the performance of the Server. Why not suggest that PPPoE header didn't be included in the MTU calculation,just like VLAN encapsulation? Regards Wu Haijun Huawei Tech. Corp. LTD in CHINA Senior Firmware Engineer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Nov 11 0:46: 9 2000 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 81DD337B479 for ; Sat, 11 Nov 2000 00:46:05 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id eAB8jkL62156; Sat, 11 Nov 2000 10:45:46 +0200 (EET) (envelope-from ru) Date: Sat, 11 Nov 2000 10:45:46 +0200 From: Ruslan Ermilov To: Wilbert de Graaf Cc: wu haijun , freebsd-net@FreeBSD.ORG Subject: Re: A question for PPPoE 's MTU: Message-ID: <20001111104546.B61961@sunbay.com> Mail-Followup-To: Wilbert de Graaf , wu haijun , freebsd-net@FreeBSD.ORG References: <001f01c04afb$9b6e07a0$1b22690a@huawei.com.cn> <003301c04b9d$2cde51d0$0a00a8c0@alias> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <003301c04b9d$2cde51d0$0a00a8c0@alias>; from wilbertdg@hetnet.nl on Fri, Nov 10, 2000 at 09:06:38PM -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Nov 10, 2000 at 09:06:38PM -0800, Wilbert de Graaf wrote: > > Hi Wu, > > I remember this problem when we implemented an IP aggregator behind our > terminal servers. We configured our servers to respond with packet telling > the client to start over again and use smaller, not fragmented, ip packets. > This definitely improved performance. I think this is rfc879 (The TCP > Maximum Segment Size) related. > I don't remember how we did it but I believe just setting the MTU on that > interface to 1492 in your case, and set don't fragment. > You may also try ports/net/tcpmssd for that purpose. -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Nov 11 3: 0:48 2000 Delivered-To: freebsd-net@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id DDD9237B479 for ; Sat, 11 Nov 2000 03:00:45 -0800 (PST) Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #20) id 13uYOn-0001vr-00; Sat, 11 Nov 2000 12:00:41 +0100 Received: from a6ca9.pppool.de ([213.6.108.169] helo=elischer.org) by mx2.freenet.de with esmtp (Exim 3.16 #26) id 13uYOm-0006HR-00; Sat, 11 Nov 2000 12:00:41 +0100 Message-ID: <3A0D26BD.E34BF23A@elischer.org> Date: Sat, 11 Nov 2000 03:00:13 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Wilbert de Graaf Cc: wu haijun , freebsd-net@freebsd.org Subject: Re: A question for PPPoE 's MTU: References: <001f01c04afb$9b6e07a0$1b22690a@huawei.com.cn> <003301c04b9d$2cde51d0$0a00a8c0@alias> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilbert de Graaf wrote: > > Hi Wu, > > I remember this problem when we implemented an IP aggregator behind our > terminal servers. We configured our servers to respond with packet telling > the client to start over again and use smaller, not fragmented, ip packets. > This definitely improved performance. I think this is rfc879 (The TCP > Maximum Segment Size) related. > I don't remember how we did it but I believe just setting the MTU on that > interface to 1492 in your case, and set don't fragment. I once wrote a module that intercepted all tcp setup packets passing through the system and rewrote them to say that the windows and MTUs should be lower. > > - Wilbert > > ----- Original Message ----- > From: wu haijun > To: freebsd-net@freebsd.org > Sent: Friday, November 10, 2000 1:50 AM > Subject: A question for PPPoE 's MTU: > > Hi: > > The MTU of PPPoE is 1492 Bytes. But if the PPPoE Server receives IP packets > from the WAN and the packets's will be always 1514 Bytes,so the Server must > fragment the Packets to fit in the PPPoE packets ,and this will degrade the > performance of the Server. > Why not suggest that PPPoE header didn't be included in the MTU > calculation,just like VLAN encapsulation? > > Regards > > Wu Haijun > Huawei Tech. Corp. LTD in CHINA > Senior Firmware Engineer > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Nov 11 18:30:54 2000 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 454E137B479 for ; Sat, 11 Nov 2000 18:30:52 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id SAA88870; Sat, 11 Nov 2000 18:30:48 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.11.0/8.11.0) id eAC2Ues13896; Sat, 11 Nov 2000 18:30:40 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200011120230.eAC2Ues13896@curve.dellroad.org> Subject: Re: MPD question In-Reply-To: <71E79DA61328D311B4D10020AFF78E4218D953@bdc.orlando.tradeweb.net> "from John Congdon at Nov 10, 2000 10:47:46 am" To: John Congdon Date: Sat, 11 Nov 2000 18:30:40 -0800 (PST) Cc: "'freebsd-net@freebsd.org'" X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Congdon writes: > I am using mpd to do dial-in PPP. It works GREAT except when I disconnect, > the server does not drop the connection. When I redial it just rings. > > Here is a snippet of mpd. Starts to close, says waiting for ring... but > continues as if it is still open. Looking at the log trace I think it's a problem with mpd in answer mode.. try configuring the link with no dial-on-demand and no idle timeout... some permutation of those parameters might fix it. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Nov 11 22:35:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from sentry.granch.com (sentry.granch.com [212.109.197.55]) by hub.freebsd.org (Postfix) with ESMTP id E184D37B4C5 for ; Sat, 11 Nov 2000 22:35:49 -0800 (PST) Received: from sentry.granch.ru (IDENT:shelton@localhost [127.0.0.1]) by sentry.granch.com (8.9.3/8.9.3) with ESMTP id MAA45608 for ; Sun, 12 Nov 2000 12:32:58 +0600 (NOVT) Message-ID: <3A0E399A.DF69446D@sentry.granch.ru> Date: Sun, 12 Nov 2000 12:32:58 +0600 From: "Rashid N. Achilov" Reply-To: achilov@granch.ru Organization: Granch Ltd. X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Traceroute and UDP port 33434 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 encountered a strange problem - when I deny UDP port 33434, traceroute refuses to trace...Can the traceroute use the UDP port 33434? -- With Best Regards. Rashid N. Achilov (RNA1-RIPE), Brainbench ID: 28514 Granch Ltd. system administrator, e-mail: achilov@granch.ru tel/fax (383-2) 24-2363 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Nov 11 23: 9:50 2000 Delivered-To: freebsd-net@freebsd.org Received: from overlord.e-gerbil.net (e-gerbil.net [207.91.110.247]) by hub.freebsd.org (Postfix) with ESMTP id AEA0437B479 for ; Sat, 11 Nov 2000 23:09:47 -0800 (PST) Received: by overlord.e-gerbil.net (Postfix, from userid 1001) id EB00AE4F0C; Sun, 12 Nov 2000 02:09:27 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by overlord.e-gerbil.net (Postfix) with ESMTP id D4310E4F0B; Sun, 12 Nov 2000 02:09:27 -0500 (EST) Date: Sun, 12 Nov 2000 02:09:27 -0500 (EST) From: "Richard A. Steenbergen" To: achilov@granch.ru Cc: freebsd-net@freebsd.org Subject: Re: Traceroute and UDP port 33434 In-Reply-To: <3A0E399A.DF69446D@sentry.granch.ru> 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, 12 Nov 2000, Rashid N. Achilov wrote: > I have encountered a strange problem - when I deny UDP port 33434, > traceroute refuses to trace...Can the traceroute use the UDP port 33434? The default unix traceroute uses UDP probes destined to supposidly "unused" ports. This probe starts at 33434 (32768+666 :P) and increments once with each probe. The default behavior is 3 probes per hop (per TTL increment), with a maximium of 30 hops, which means the standard unix traceroute will target UDP ports 33434-33524. The traceroute program knows there is another hop when it receives a TTL Exceed, and knows it has reached the end of the trace when it receives a Dest Unreachable for those ports. If something is listening on those ports, the traceroute will fail. With FreeBSD traceroute, the parameter you're looking for to change this default base is "-p ". HTH -- Richard A Steenbergen http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message