From owner-freebsd-net Sun Oct 14 10:50: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 81F1D37B405 for ; Sun, 14 Oct 2001 10:50:05 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 11BC716B36 for ; Sun, 14 Oct 2001 19:50:03 +0200 (CEST) Received: from IBM-HIRXKN66F0W.Go2France.com [66.64.14.18] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id A35B649A0084; Sun, 14 Oct 2001 20:03:07 +0200 Message-Id: <5.1.0.14.0.20011014124637.05a7a828@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 14 Oct 2001 12:49:19 -0500 To: freebsd-net@freebsd.org From: Len Conrad Subject: load-balancing to multiple T1's Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Is anybody using netgraph and multilink ppp (recommended by PHK) to load-balance outgoing traffic over multiple (4 or more) T1's? stable? efficient enough to push the T1's towards practial limits? thanks Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 14 20:37:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 39D7D37B406 for ; Sun, 14 Oct 2001 20:37:39 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id f9F3bX834547 for ; Sun, 14 Oct 2001 20:37:34 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 14 Oct 2001 20:37:33 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: net@freebsd.org Subject: PXE boot vs. DHCP Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've been setting up a 4.4-RELEASE system for net booting and diskless operation with pxeboot, and I've run into a minor but annoying problem. It seems that if you boot with PXE you can't use dhclient. pxeboot configures the relevant network interface (let's call it fxp0), NFS-mounts the root filesystem, boots the kernel, etc., and begins to enter multi-user mode. The rc.network script then runs dhclient, which tries to configure fxp0 (again). It apparently starts out by unconfiguring fxp0's IP address, because NFS immediately hangs with a "host unreachable" error. At that point I have to walk over and press the reset button. If I disable DHCP on fxp0 in /etc/rc.conf, the system boots fine and leaves me with a working, configured interface. But lots of other useful stuff that DHCP would give me is missing: e.g., the host name, the DNS server, and so forth. It would be nice if I could netboot the machine and then grab all that other information with DHCP. I'm aware that /etc/rc.diskless* allow me to put host-specific configuration files into /config//etc. But I'd much prefer to keep all that information together in the dhcpd.conf file. Any ideas on how to solve this problem? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 14 20:54:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 8FA6037B406 for ; Sun, 14 Oct 2001 20:54:46 -0700 (PDT) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f9F3sjH11286 for ; Sun, 14 Oct 2001 20:54:45 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sun, 14 Oct 2001 20:54:45 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: freebsd-net@freebsd.org Subject: (resend/redo) of BRIDGE patches Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org can somebody help test these? It compiles well, etc... but I haven't quite got the setup at the moment to really do this as I'd have to tear down a current infrastructure that's in the middle of some long term tests. Can sombody try these and make it does what it's supposed to? They should... =================================================================== RCS file: /home/ncvs/src/sys/net/bridge.c,v retrieving revision 1.40 diff -u -r1.40 bridge.c --- net/bridge.c 2001/10/12 18:04:44 1.40 +++ net/bridge.c 2001/10/15 03:53:38 @@ -556,16 +556,16 @@ * for outgoing packets from ether_output(). */ BDG_STAT(ifp, BDG_IN); - switch ((int)dst) { - case (int)BDG_BCAST: - case (int)BDG_MCAST: - case (int)BDG_LOCAL: - case (int)BDG_UNKNOWN: - case (int)BDG_DROP: + switch ((uintptr_t)dst) { + case (uintptr_t) BDG_BCAST: + case (uintptr_t) BDG_MCAST: + case (uintptr_t) BDG_LOCAL: + case (uintptr_t) BDG_UNKNOWN: + case (uintptr_t) BDG_DROP: BDG_STAT(ifp, dst); break ; default : - if (dst == ifp || dropit ) + if (dst == ifp || dropit) BDG_STAT(ifp, BDG_DROP); else BDG_STAT(ifp, BDG_FORWARD); @@ -649,7 +649,7 @@ ifp = dst ; once = 1 ; } - if ( (u_int)(ifp) <= (u_int)BDG_FORWARD ) + if (ifp <= BDG_FORWARD) panic("bdg_forward: bad dst"); /* Index: net/bridge.h =================================================================== RCS file: /home/ncvs/src/sys/net/bridge.h,v retrieving revision 1.8 diff -u -r1.8 bridge.h --- net/bridge.h 2001/10/05 05:45:26 1.8 +++ net/bridge.h 2001/10/15 03:53:38 @@ -92,8 +92,9 @@ *((unsigned int *)(a)) == 0xffffffff && \ ((unsigned short *)(a))[2] == 0xffff ) #else -#warning... must complete these for the alpha etc. -#define BDG_MATCH(a,b) (!bcmp(a, b, ETHER_ADDR_LEN) ) +/* Unaligned access versions. */ +#define BDG_MATCH(a,b) (!bcmp(a, b, ETHER_ADDR_LEN) ) +#define IS_ETHER_BROADCAST(a) (!bcmp(a, "\377\377\377\377\377\377", 6)) #endif /* * The following constants are not legal ifnet pointers, and are used @@ -127,7 +128,7 @@ } ; -#define BDG_STAT(ifp, type) bdg_stats.s[ifp->if_index].p_in[(int)type]++ +#define BDG_STAT(ifp, type) bdg_stats.s[ifp->if_index].p_in[(long)type]++ #ifdef _KERNEL typedef struct ifnet *bridge_in_t(struct ifnet *, struct ether_header *); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 0:33:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from web11208.mail.yahoo.com (web11208.mail.yahoo.com [216.136.131.190]) by hub.freebsd.org (Postfix) with SMTP id 266AD37B407 for ; Mon, 15 Oct 2001 00:33:53 -0700 (PDT) Message-ID: <20011015073353.31894.qmail@web11208.mail.yahoo.com> Received: from [164.164.56.2] by web11208.mail.yahoo.com via HTTP; Mon, 15 Oct 2001 00:33:53 PDT Date: Mon, 15 Oct 2001 00:33:53 -0700 (PDT) From: deepika kakrania Subject: mrouted 3.8(how to find multicast members??) To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, I am using mrouted (release 3.8) code on my system. In the code I find that for non-member interfaces of a multicast group, threshold TTL is set to 0. Like this. prun_add_ttls(gt) struct gtable *gt; { struct uvif *v; vifi_t vifi; for (vifi = 0, v = uvifs; vifi < numvifs; ++vifi, ++v) { if (VIFM_ISSET(vifi, gt->gt_grpmems)) gt->gt_ttls[vifi] = v->uv_threshold; else gt->gt_ttls[vifi] = 0; } } But the definition of threshhold TTL says that a incoming multicast packets will be forwarded out of an interface only if it has the TTL value >= threshold TTL of that interface. Am I right? Then doesn't multicast packet get forwarded out of all those interfaces which have TTL threshold of 0, which actually are not members for that multicast group? Can anyone help me out. Thanks & regards, Deepika  __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 1:10: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from admin4.dircon.net (admin4.dircon.net [195.157.2.156]) by hub.freebsd.org (Postfix) with ESMTP id E438F37B40F for ; Mon, 15 Oct 2001 01:09:59 -0700 (PDT) Received: (from tdcmb2@localhost) by admin4.dircon.net (8.11.1/8.11.1) id f9F89cT12504; Mon, 15 Oct 2001 09:09:38 +0100 (BST) (envelope-from tdcmb2) Date: Mon, 15 Oct 2001 09:09:38 +0100 From: Mark Blackman To: John Polstra Cc: net@freebsd.org, le@cs.unc.edu Subject: Re: Connect(2) problem Message-ID: <20011015090938.A12490@admin4.dircon.net> References: <200110101546.f9AFkcd86407@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200110101546.f9AFkcd86407@vashon.polstra.com>; from jdp@polstra.com on Wed, Oct 10, 2001 at 08:46:38AM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This actually sounds like a problem I hit once where the default settings actually restrict the number of ports. net.inet.ip.portrange.lowfirst: 1023 net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.first: 1024 net.inet.ip.portrange.last: 5000 net.inet.ip.portrange.hifirst: 49152 net.inet.ip.portrange.hilast: 65535 specifically, portrange.first and portrange.last are set a bit low for some applications. By default you only get 5000-1024 ports (3976). set net.inet.ip.portrange.last=16384 or higher to get more ports. - Mark On Wed, Oct 10, 2001 at 08:46:38AM -0700, John Polstra wrote: > In article , > Nguyen-Tuong Long Le wrote: > > > > I have a software that simulates web clients and servers to create > > network congestion (for the purpose of doing research in network > > congestion). In our experiment, a client opens an HTTP connection > > to a server, fetches a number of objects, and then closes the > > connection. A problem I seem to have right now is that a client > > machine cannot simulate more than 3000 connections. When my client > > machine simulates more than 3000 connections, it's able to open > > a socket but then connect(2) fails with errno 35 (Resource > > temporarily unavailable). Another interesting notice is that the > > connect(2) system call blocks for a few miliseconds before it > > fails although fcntl(2) was used to make the socket non-blocking. > > The OS version I am using is FreeBSD 4.3-release. > > In addition to the suggestion from Alex Rousskov, adding these lines > to "/boot/loader.conf" may help: > > kern.ipc.maxsockets="8192" > kern.ipc.nmbclusters="32768" > > John > -- > John Polstra > John D. Polstra & Co., Inc. Seattle, Washington USA > "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 5:36:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailman.thenap.com (mailman.thenap.com [209.190.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 8BCE237B406 for ; Mon, 15 Oct 2001 05:36:49 -0700 (PDT) Received: by MAILMAN with Internet Mail Service (5.5.2653.19) id <42VNJD5B>; Mon, 15 Oct 2001 08:40:53 -0400 Message-ID: From: "Drew J. Weaver" To: "'freebsd-net@freebsd.org'" Subject: DNS causing problems with sendmail? Date: Mon, 15 Oct 2001 08:40:46 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C15576.9C5395F0" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C15576.9C5395F0 Content-Type: text/plain Hi, I've had this problem for a few days now, we have a small dial-up ISP and when users dial into one of our cities they get a 209.xxx.xxx.xxx IP and our mail server responds normally, we have another modem pool in that city that consists of 206.xxx.xxx.xxx IP addresses, if a user gets a 206.xxx.xxx.xxx IP address and they attempt to check mail it takes a good 2-3 minutes before the sendmail connection starts, which is an obvious problem because of the timeouts on email clients (and.. 2-3 minutes is just bad). I've been kinda asking around on comp.mail.sendmail about this issue and they are telling me it is a DNS problem. Well, I know that my mail server can reverse the IP addresses because if I am logged in and issue a host command with the IP after it the server is able to produce the proper reverse name. Another user thought it was because I have no Forward dns (a record) for what the IPs are reversed to, but the fact is I've NEVER had any A records or anything for my modem pools. I also have another server running the same version of sendmail, and if I dial into this city and get a 206.xxx.xxx.xxx IP and telnet to port 25 on that server it comes up instantly. So this appears to be an issue only effecting one daemon on one server. The afflicted server also runs a POP daemon that isn't having any problems of this type. Does anyone have a clue on this? I'm awfully confused at this point. Thanks, -Drew ------_=_NextPart_001_01C15576.9C5395F0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

Hi, I've had this problem = for a few days now, we have a small dial-up ISP and when users dial into = one of our cities they get a 209.xxx.xxx.xxx IP and our mail server responds = normally, we have another modem pool in that city that consists of 206.xxx.xxx.xxx = IP addresses, if a user gets a 206.xxx.xxx.xxx IP address and they attempt = to check mail it takes a good 2-3 minutes before the sendmail connection starts, which is an obvious problem because of the timeouts = on email clients (and.. 2-3 minutes is just bad). I've been kinda asking around on comp.mail.sendmail about = this issue and they are telling me it is a DNS problem. Well, I know that my mail = server can reverse the IP addresses because if I am logged in and issue a host = command with the IP after it the server is able to produce the proper reverse = name. Another user thought it was because I have no Forward dns (a record) for what the IPs are reversed = to, but the fact is I've NEVER had any A records or = anything for my modem pools. I also have another server running the same version = of sendmail, and if I dial into this city and get a 206.xxx.xxx.xxx IP and telnet to port 25 on that server it comes up = instantly. So this appears to be an issue only effecting one daemon on one server. = The afflicted server also runs a POP daemon that isn't having any problems = of this type.

 

Does anyone have a clue on = this? I'm awfully confused at this point.

 

Thanks,

-Drew

 

------_=_NextPart_001_01C15576.9C5395F0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 8:34:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from cx175057-a.ocnsd1.sdca.home.com (cx175057-a.ocnsd1.sdca.home.com [24.4.86.45]) by hub.freebsd.org (Postfix) with ESMTP id 5ADA937B40C for ; Mon, 15 Oct 2001 08:34:27 -0700 (PDT) Received: from brian (cx175057-b.ocnsd1.sdca.home.com [24.4.87.106]) by cx175057-a.ocnsd1.sdca.home.com (8.11.6/8.11.3) with SMTP id f9FFYIY08995; Mon, 15 Oct 2001 08:34:24 -0700 (PDT) (envelope-from bri@sonicboom.org) Message-ID: <007701c1558e$585a1460$3324200a@sonicboom.org> From: "Brian" To: "Drew J. Weaver" , "'freebsd-net@freebsd.org'" References: Subject: Re: DNS causing problems with sendmail? Date: Mon, 15 Oct 2001 08:30:18 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0070_01C15553.9F600080" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0070_01C15553.9F600080 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable After the 2 or 3 minute delay, does it work? Looked in /var/log/maillog = for reject causes? Are all the hosts you want to allow to send = specified in /etc/mail/relay-domains? If you want to try to see if dns = is the cause, specify a few of the non working hosts in /etc/hosts. = Personally as an isp customer, if forward and reverse dns is not setup, = I'd be looking for a new isp. Some sites will not allow you to connect = in this situation. TCP wrappers often includes this entry. # Prevent those with no reverse DNS from connecting. ALL : PARANOID : RFC931 20 : deny Bri ----- Original Message -----=20 From: Drew J. Weaver=20 To: 'freebsd-net@freebsd.org'=20 Sent: Monday, October 15, 2001 5:40 AM Subject: DNS causing problems with sendmail? Hi, I've had this problem for a few days now, we have a small dial-up = ISP and when users dial into one of our cities they get a = 209.xxx.xxx.xxx IP and our mail server responds normally, we have = another modem pool in that city that consists of 206.xxx.xxx.xxx IP = addresses, if a user gets a 206.xxx.xxx.xxx IP address and they attempt = to check mail it takes a good 2-3 minutes before the sendmail connection = starts, which is an obvious problem because of the timeouts on email = clients (and.. 2-3 minutes is just bad). I've been kinda asking around = on comp.mail.sendmail about this issue and they are telling me it is a = DNS problem. Well, I know that my mail server can reverse the IP = addresses because if I am logged in and issue a host command with the IP = after it the server is able to produce the proper reverse name. Another = user thought it was because I have no Forward dns (a record) for what = the IPs are reversed to, but the fact is I've NEVER had any A records or = anything for my modem pools. I also have another server running the same = version of sendmail, and if I dial into this city and get a = 206.xxx.xxx.xxx IP and telnet to port 25 on that server it comes up = instantly. So this appears to be an issue only effecting one daemon on = one server. The afflicted server also runs a POP daemon that isn't = having any problems of this type. =20 Does anyone have a clue on this? I'm awfully confused at this point. =20 Thanks, -Drew =20 ------=_NextPart_000_0070_01C15553.9F600080 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
After the 2 or 3 minute delay, does it = work? =20 Looked in /var/log/maillog for reject causes?  Are all the hosts = you want=20 to allow to send specified in /etc/mail/relay-domains?  If you want = to try=20 to see if dns is the cause, specify a few of the non working hosts in=20 /etc/hosts.  Personally as an isp customer, if forward and reverse = dns is=20 not setup, I'd be looking for a new isp.  Some sites will not allow = you to=20 connect in this situation.  TCP wrappers often includes this=20 entry.
 
# Prevent those with no reverse DNS = from=20 connecting.
ALL : PARANOID : RFC931 20 : deny
Bri
----- Original Message -----
From:=20 Drew J.=20 Weaver
Sent: Monday, October 15, 2001 = 5:40=20 AM
Subject: DNS causing problems = with=20 sendmail?

Hi, I've had this = problem for a=20 few days now, we have a small dial-up ISP and when users dial into one = of our=20 cities they get a 209.xxx.xxx.xxx IP and our mail server responds = normally, we=20 have another modem pool in that city that consists of 206.xxx.xxx.xxx = IP=20 addresses, if a user gets a 206.xxx.xxx.xxx IP address and they = attempt to=20 check mail it takes a good 2-3 minutes before the sendmail connection starts, which is an obvious = problem=20 because of the timeouts on email clients (and.. 2-3 minutes is just = bad). I've=20 been kinda asking around on comp.mail.sendmail about this issue and they are = telling=20 me it is a DNS problem. Well, I know that my mail server can reverse = the IP=20 addresses because if I am logged in and issue a host command with the = IP after=20 it the server is able to produce the proper reverse name. Another user = thought=20 it was because I have no Forward dns (a = record) for=20 what the IPs are reversed to, but the fact = is I've=20 NEVER had any A records or anything for my = modem=20 pools. I also have another server running the same version of sendmail, and if I dial into this city and get a = 206.xxx.xxx.xxx IP and telnet to port 25 on that server it comes up = instantly.=20 So this appears to be an issue only effecting one daemon on one = server. The=20 afflicted server also runs a POP daemon that isn't having any problems = of this=20 type.

 

Does anyone have a clue = on this?=20 I'm awfully confused at this point.

 

Thanks,

-Drew

 

------=_NextPart_000_0070_01C15553.9F600080-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 8:45:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from cessium.prosolve.com (gw.prosolve.com [63.225.188.140]) by hub.freebsd.org (Postfix) with ESMTP id 3D56F37B408 for ; Mon, 15 Oct 2001 08:45:44 -0700 (PDT) Received: from fs01.prosolve.com (fs01.prosolve.com [172.16.128.50]) by cessium.prosolve.com (8.11.4/8.11.4) with ESMTP id f9FEp5S15364; Mon, 15 Oct 2001 07:51:06 -0700 (PDT) Received: by fs01.prosolve.com with Internet Mail Service (5.5.2653.19) id <4XX5B5MT>; Mon, 15 Oct 2001 07:51:04 -0700 Message-ID: From: Sean Mathias To: "'Drew J. Weaver'" Cc: "'freebsd-net@FreeBSD.ORG'" Subject: RE: DNS causing problems with sendmail? Date: Mon, 15 Oct 2001 07:51:01 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C15588.CE86D2A0" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C15588.CE86D2A0 Content-Type: text/plain; charset="iso-8859-1" I have seen a similar timeout problem, though not with dial up. The problem was with the ident protocol talking to other mail servers. When I turned off this check, performance improved greatly. In the sendmail.cf file, I changed the ident timeout to zero to disable it. O Timeout.ident=0s Hope this helps, Sean Mathias Network & Security Consultant Prosolve http://www.prosolve.com v. (206) 306-2525 f. (206) 306-2526 -----Original Message----- From: Drew J. Weaver [mailto:drew.weaver@thenap.com] Sent: Monday, October 15, 2001 5:41 AM To: 'freebsd-net@freebsd.org' Subject: DNS causing problems with sendmail? Hi, I've had this problem for a few days now, we have a small dial-up ISP and when users dial into one of our cities they get a 209.xxx.xxx.xxx IP and our mail server responds normally, we have another modem pool in that city that consists of 206.xxx.xxx.xxx IP addresses, if a user gets a 206.xxx.xxx.xxx IP address and they attempt to check mail it takes a good 2-3 minutes before the sendmail connection starts, which is an obvious problem because of the timeouts on email clients (and.. 2-3 minutes is just bad). I've been kinda asking around on comp.mail.sendmail about this issue and they are telling me it is a DNS problem. Well, I know that my mail server can reverse the IP addresses because if I am logged in and issue a host command with the IP after it the server is able to produce the proper reverse name. Another user thought it was because I have no Forward dns (a record) for what the IPs are reversed to, but the fact is I've NEVER had any A records or anything for my modem pools. I also have another server running the same version of sendmail, and if I dial into this city and get a 206.xxx.xxx.xxx IP and telnet to port 25 on that server it comes up instantly. So this appears to be an issue only effecting one daemon on one server. The afflicted server also runs a POP daemon that isn't having any problems of this type. Does anyone have a clue on this? I'm awfully confused at this point. Thanks, -Drew ------_=_NextPart_001_01C15588.CE86D2A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have=20 seen a similar timeout problem, though not with dial up.  The = problem was=20 with the ident protocol talking to other mail servers.  When I = turned off=20 this check, performance improved greatly. 
 
In the=20 sendmail.cf file, I changed the ident timeout to zero to disable=20 it.
 
O=20 Timeout.ident=3D0s
 
Hope=20 this helps,
 

Sean Mathias
Network & Security Consultant
Prosolve
http://www.prosolve.com =
v. (206) 306-2525
f. (206)=20 306-2526

-----Original Message-----
From: Drew J. Weaver=20 [mailto:drew.weaver@thenap.com]
Sent: Monday, October 15, = 2001 5:41=20 AM
To: 'freebsd-net@freebsd.org'
Subject: DNS = causing=20 problems with sendmail?

Hi, I've had this = problem for a=20 few days now, we have a small dial-up ISP and when users dial into = one of our=20 cities they get a 209.xxx.xxx.xxx IP and our mail server responds = normally, we=20 have another modem pool in that city that consists of 206.xxx.xxx.xxx = IP=20 addresses, if a user gets a 206.xxx.xxx.xxx IP address and they = attempt to=20 check mail it takes a good 2-3 minutes before the sendmail connection starts, which is an obvious = problem=20 because of the timeouts on email clients (and.. 2-3 minutes is just = bad). I've=20 been kinda asking around on comp.mail.sendmail about this issue and they = are telling=20 me it is a DNS problem. Well, I know that my mail server can reverse = the IP=20 addresses because if I am logged in and issue a host command with the = IP after=20 it the server is able to produce the proper reverse name. Another = user thought=20 it was because I have no Forward dns (a = record) for=20 what the IPs are reversed to, but the = fact is I've=20 NEVER had any A records or anything for my = modem=20 pools. I also have another server running the same version of sendmail, and if I dial into this city and get = a=20 206.xxx.xxx.xxx IP and telnet to port 25 on that server it comes up = instantly.=20 So this appears to be an issue only effecting one daemon on one = server. The=20 afflicted server also runs a POP daemon that isn't having any = problems of this=20 type.

 

Does anyone have a clue = on this?=20 I'm awfully confused at this point.

 

Thanks,

-Drew

 

------_=_NextPart_001_01C15588.CE86D2A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 8:49:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailman.thenap.com (mailman.thenap.com [209.190.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 4A20E37B410 for ; Mon, 15 Oct 2001 08:49:40 -0700 (PDT) Received: by MAILMAN with Internet Mail Service (5.5.2653.19) id <42VNJD79>; Mon, 15 Oct 2001 11:53:54 -0400 Message-ID: From: "Drew J. Weaver" To: 'Brian' Cc: "'freebsd-net@freebsd.org'" Subject: RE: DNS causing problems with sendmail? Date: Mon, 15 Oct 2001 11:53:48 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C15591.9414BB10" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C15591.9414BB10 Content-Type: text/plain After 2 or 3 minutes it does work, the weird thing is that it was working No problem for 2 years and then suddenly it stopped working. Yes, our modem pool IP addresses all have PTR records, just not forward DNS (we aren't that stupid). When I specify a few of the non working hosts in /etc/hosts it works fine then. One of the IP addresses in question is 206.222.10.7, if you do a host 206.222.10.7 it does reverse. So I guess my question is, what the dilly-o? -----Original Message----- From: Brian [mailto:bri@sonicboom.org] Sent: Monday, October 15, 2001 11:30 AM To: Drew J. Weaver; 'freebsd-net@freebsd.org' Subject: Re: DNS causing problems with sendmail? After the 2 or 3 minute delay, does it work? Looked in /var/log/maillog for reject causes? Are all the hosts you want to allow to send specified in /etc/mail/relay-domains? If you want to try to see if dns is the cause, specify a few of the non working hosts in /etc/hosts. Personally as an isp customer, if forward and reverse dns is not setup, I'd be looking for a new isp. Some sites will not allow you to connect in this situation. TCP wrappers often includes this entry. # Prevent those with no reverse DNS from connecting. ALL : PARANOID : RFC931 20 : deny Bri ----- Original Message ----- From: Drew J. Weaver To: 'freebsd-net@freebsd.org' Sent: Monday, October 15, 2001 5:40 AM Subject: DNS causing problems with sendmail? Hi, I've had this problem for a few days now, we have a small dial-up ISP and when users dial into one of our cities they get a 209.xxx.xxx.xxx IP and our mail server responds normally, we have another modem pool in that city that consists of 206.xxx.xxx.xxx IP addresses, if a user gets a 206.xxx.xxx.xxx IP address and they attempt to check mail it takes a good 2-3 minutes before the sendmail connection starts, which is an obvious problem because of the timeouts on email clients (and.. 2-3 minutes is just bad). I've been kinda asking around on comp.mail.sendmail about this issue and they are telling me it is a DNS problem. Well, I know that my mail server can reverse the IP addresses because if I am logged in and issue a host command with the IP after it the server is able to produce the proper reverse name. Another user thought it was because I have no Forward dns (a record) for what the IPs are reversed to, but the fact is I've NEVER had any A records or anything for my modem pools. I also have another server running the same version of sendmail, and if I dial into this city and get a 206.xxx.xxx.xxx IP and telnet to port 25 on that server it comes up instantly. So this appears to be an issue only effecting one daemon on one server. The afflicted server also runs a POP daemon that isn't having any problems of this type. Does anyone have a clue on this? I'm awfully confused at this point. Thanks, -Drew ------_=_NextPart_001_01C15591.9414BB10 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

After 2 or 3 minutes it does work, = the weird thing is that it was working No problem for 2 years and then = suddenly it stopped working. Yes, our modem pool IP addresses all have PTR records, = just not forward DNS (we aren't that stupid). When I specify a few of the = non working hosts in /etc/hosts it works fine then. One of the IP addresses in = question is 206.222.10.7, if you do a host 206.222.10.7 it does reverse. So I guess = my question is, what the dilly-o?

 

=

-----Original = Message-----
From: Brian [mailto:bri@sonicboom.org]
Sent: = Monday, October 15, = 2001 11:30 AM
To: Drew J. Weaver; 'freebsd-net@freebsd.org'
Subject: Re: DNS causing = problems with sendmail?

 

After the 2 or 3 minute = delay, does it work?  Looked in /var/log/maillog for reject causes?  Are = all the hosts you want to allow to send specified in = /etc/mail/relay-domains?  If you want to try to see if dns is the cause, specify a few of the non = working hosts in /etc/hosts.  Personally as an isp customer, if forward and = reverse dns is not setup, I'd be looking for a new isp.  Some sites will not = allow you to connect in this situation.  TCP wrappers often includes this = entry.

 

# Prevent those with no = reverse DNS from connecting.
ALL : PARANOID : RFC931 20 : deny

Bri

----- Original Message = -----

Sent: Monday, October 15, = 2001 5:40 AM

Subject: DNS causing problems with sendmail?

 

Hi, = I've had this problem for a few days now, we have a small dial-up ISP and when users = dial into one of our cities they get a 209.xxx.xxx.xxx IP and our mail = server responds normally, we have another modem pool in that city that = consists of 206.xxx.xxx.xxx IP addresses, if a user gets a 206.xxx.xxx.xxx IP = address and they attempt to check mail it takes a good 2-3 minutes before the = sendmail connection starts, which is an obvious problem because of the timeouts = on email clients (and.. 2-3 minutes is just bad). I've been kinda asking around = on comp.mail.sendmail about this issue and they are telling me it is a DNS problem. Well, I know that my mail server can reverse the IP addresses = because if I am logged in and issue a host command with the IP after it the = server is able to produce the proper reverse name. Another user thought it was = because I have no Forward dns (a record) for what the IPs are reversed to, but = the fact is I've NEVER had any A records or anything for my modem pools. I also = have another server running the same version of sendmail, and if I dial into = this city and get a 206.xxx.xxx.xxx IP and telnet to port 25 on that server = it comes up instantly. So this appears to be an issue only effecting one daemon = on one server. The afflicted server also runs a POP daemon that isn't having = any problems of this type.

 

Does = anyone have a clue on this? I'm awfully confused at this = point.

 

Thanks,

-Drew

 

------_=_NextPart_001_01C15591.9414BB10-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 8:54: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id EB80D37B40A; Mon, 15 Oct 2001 08:54:03 -0700 (PDT) Received: from bell.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 15 Oct 2001 16:53:59 +0100 (BST) To: Garrett Wollman Cc: net@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: Puzzled over sosend's handling of pre-prepared mbufs... In-Reply-To: Your message of "Thu, 27 Aug 1998 21:42:01 EDT." <199808280142.VAA11467@khavrinen.lcs.mit.edu> Date: Mon, 15 Oct 2001 16:53:58 +0100 From: Ian Dowse Message-ID: <200110151653.aa00863@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [a rather delayed response to this posting] In message <199808280142.VAA11467@khavrinen.lcs.mit.edu>, Garrett Wollman write s: >In looking over mbuf handling for TCP some more, I noticed a puzzling >omission. When sosend() is handed an mbuf chain rather than a uio, it >makes no effort to check whether the chain would actually fit within >the socket buffer limits. It simply calls pru_send() with the mbuf >chain, which -- in TCP's case -- just passes it to sbappend() also >without making any sort of check. The only client of this interface, >NFS, also makes no attempt to check the socket buffer capacity. > >Is this reasonable? I would rather see NFS obey the same buffering >model as everything else; that will make life much easier when the >underlying buffer mechanism changes. In this case, that would mean >that the process making the NFS request would get blocked rather than >``overrun'' the buffer. (I put ``overrun'' in quotation marks since >there is no physical limit on socket buffer lengths, just a >logical/administrative one.) I just came across this problem with a -current test box. When using ipfw to block an active TCP NFS mount, the NFS client ran the system out of mbufs by continuously retransmitting requests. It may be a current-specific bug that causes so many retransmits, but ignoring the socket buffer limit is a bad thing. The patch below makes the obvious change to sosend() so that it enforces the normal socket limit in the uio == NULL case also. Can anyone see any potential problems with this? I guess it is possible that NFS might need to reserve more socket space than it does currently - there is code in nfs_connect() that calls soreserve, but it is based on the vfs.nfs.bufpackets sysctl so tuning is easy. Ian Index: uipc_socket.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/sys/kern/uipc_socket.c,v retrieving revision 1.102 diff -u -r1.102 uipc_socket.c --- uipc_socket.c 9 Oct 2001 21:40:30 -0000 1.102 +++ uipc_socket.c 15 Oct 2001 14:34:16 -0000 @@ -528,7 +528,7 @@ if ((atomic && resid > so->so_snd.sb_hiwat) || clen > so->so_snd.sb_hiwat) snderr(EMSGSIZE); - if (space < resid + clen && uio && + if (space < resid + clen && (atomic || space < so->so_snd.sb_lowat || space < clen)) { if (so->so_state & SS_NBIO) snderr(EWOULDBLOCK); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 9:36:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 0D0F337B40D for ; Mon, 15 Oct 2001 09:36:54 -0700 (PDT) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id 51DF31E028; Mon, 15 Oct 2001 12:36:53 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id MAA12805; Mon, 15 Oct 2001 12:36:52 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id JAA16632; Mon, 15 Oct 2001 09:36:52 -0700 (PDT) Message-Id: <200110151636.JAA16632@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: deepika_77@yahoo.com Subject: Re: mrouted 3.8(how to find multicast members??) Cc: freebsd-net@freebsd.org Date: Mon, 15 Oct 2001 09:36:52 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > But the definition of threshhold TTL says that a >incoming multicast packets will be forwarded out of an >interface only if it has the TTL value >= threshold >TTL of that interface. Am I right? No. Zero is special, and means do not forward. If you have the kernel source, check out the ip_mdq() function in /sys/netinet/ip_mroute.c; the check is: if ((rt->mfc_ttls[vifi] > 0) && (ip->ip_ttl > rt->mfc_ttls[vifi])) { (the threshold > 0 and the TTL > the threshold -- note, >, not >=.) Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 12:18:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from sonic.kks.net (sonic.kks.net [213.161.0.18]) by hub.freebsd.org (Postfix) with ESMTP id CDCCD37B40B for ; Mon, 15 Oct 2001 12:18:06 -0700 (PDT) Received: from voyager.kksonline.com (5-51.ro.cable.kks.net [213.161.5.51]) by sonic.kks.net (Postfix) with ESMTP id E86C91E for ; Mon, 15 Oct 2001 21:18:14 +0200 (CEST) Message-Id: <5.0.2.1.0.20011015172745.02893dc8@sundance.kks.net> X-Sender: arozman@sundance.kks.net X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 15 Oct 2001 17:34:20 +0200 To: freebsd-net@freebsd.org From: Aleksander Rozman - Andy Subject: Re: VLAN speed In-Reply-To: <20011010143648.O51024@elvis.mu.org> References: <200110100519.WAA03152@windsor.research.att.com> <200110100519.WAA03152@windsor.research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 10.10.2001, you wrote: >On Tue, Oct 09, 2001 at 10:19:09PM -0700, Bill Fenner wrote: > > > (ifSpeed says "For a sub-layer which has no concept of bandwidth, this > > object should be zero." I'd argue that this describes VLAN interfaces.) > >not that the vendor is always right or anything, but at least one >implementation (juniper) behaves this way: > > interfaces.ifTable.ifEntry.ifDescr.9 = fxp1.0 > interfaces.ifTable.ifEntry.ifType.9 = ethernetCsmacd(6) > interfaces.ifTable.ifEntry.ifSpeed.9 = Gauge: 100000000 > > interfaces.ifTable.ifEntry.ifDescr.36 = ge-2/0/0.401 > interfaces.ifTable.ifEntry.ifType.36 = ethernetCsmacd(6) > interfaces.ifTable.ifEntry.ifSpeed.36 = Gauge: 1000000000 > >crisco only creates entries in the ifTable for physical interfaces in >their routers (or at least for the ones that I have access to that use >.1q or isl). cisco msfc2 reports gigabit for vlans, but that doesn't count. > >just a reference point. I would argue that vlans are definitely "a >sub-layer which has no concept of bandwidth" too. Yes and HP has special OIDs for VLANs. If I remember correct VLANs are not even in ifTable, since they are not interfaces, I am not 100% sure about this, but if they are in ifTable they have special type defined... It seems that every company has it's own way of dealing with VLANs... As for sub-layer thing, I wouldn't argue with you that VLAN is sub-layer, but I think it has a little concet of bandwidth... Andy >-- >- bill fumerola / fumerola@yahoo-inc.com / billf@FreeBSD.org / billf@mu.org >- my anger management counselor can beat up your self-affirmation therapist > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-net" in the body of the message ************************************************************************** * Aleksander Rozman - Andy * Fandoms: E2:EA, SAABer, Trekkie, Earthie * * andy@kksonline.com * Sentinel, BH 90210, True's Trooper, * * andy@atechnet.dhs.org * Heller's Angel, Questie, Legacy, PO5, * * Maribor, Slovenia (Europe) * Profiler, Buffy (Slayerete), Pretender * * ICQ-UIC: 4911125 ********************************************* * PGP key available * http://www.atechnet.dhs.org/~andy/ * ************************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 12:34:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 5379F37B409 for ; Mon, 15 Oct 2001 12:34:16 -0700 (PDT) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id 076701E059; Mon, 15 Oct 2001 15:34:12 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id PAA18690; Mon, 15 Oct 2001 15:34:10 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id MAA20835; Mon, 15 Oct 2001 12:34:09 -0700 (PDT) Message-Id: <200110151934.MAA20835@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: andy@kksonline.com Subject: Re: VLAN speed Cc: freebsd-net@freebsd.org References: <200110100519.WAA03152@windsor.research.att.com> <5.0.2.1.0.20011015172745.02893dc8@sundance.kks.net> Date: Mon, 15 Oct 2001 12:34:09 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >If I remember correct VLANs are not >even in ifTable, since they are not interfaces Why not? My reading of RFC 2863's section 3.1 says that although the VLAN multiplexing was not explicitly considered, it fits the ifStack model perfectly, and satisfies the requirements for defining a layer (notably, having multiplexing which means that the lower layer's counters are insufficient to represent what's going on). >if they are in ifTable they have special type defined... Yes, ifType l2vlan(135). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 16: 0:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 0FD9537B405 for ; Mon, 15 Oct 2001 16:00:18 -0700 (PDT) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id PAA48049; Mon, 15 Oct 2001 15:49:19 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.3/8.11.3) id f9FMnJJ33076; Mon, 15 Oct 2001 15:49:19 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200110152249.f9FMnJJ33076@arch20m.dellroad.org> Subject: Re: strange results with increased net.inet.ip.intr_queue_maxlen In-Reply-To: <5.1.0.14.0.20011012121150.072325d0@marble.sentex.ca> "from Mike Tancsa at Oct 12, 2001 12:13:59 pm" To: Mike Tancsa Date: Mon, 15 Oct 2001 15:49:19 -0700 (PDT) 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Mike Tancsa writes: > >If the forwarding path is maxed out, then it is the application layer's > >responsibility to back off (think TCP). > > Is it better for the networking layer to deal with this (potentially > introducing some latency) as opposed to letting the application ? Oops, can substitute "transport" for "application".. But no, the network should just do "best effort".. that is, unless you are a telco type in which case, go back to your X.25 :-) This is a religious issue to some degree, but in practice the war is over and the Internet won (vs. the telco way of doing things). There is probably a good paper somewhere outlining the "best effort" philosophy but I don't know what it is. Another way to look at it is intelligence in the leaf nodes rather than in the network. This is one of the central idea of the Internet dating back to a long time ago. I guess the other big idea is packets instead of dedicated circuits (which hog resources). > >Pinging is an excellent way to determine latency. > > I guess then its only at the "worst case" where I would see the added > latency as I dont see any difference by adjusting the queue size. Yes, you wouldn't notice a difference except when the queue is full all the time (the "worst case"). -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 Mon Oct 15 16:27:36 2001 Delivered-To: freebsd-net@freebsd.org Received: from tomts20-srv.bellnexxia.net (tomts20.bellnexxia.net [209.226.175.74]) by hub.freebsd.org (Postfix) with ESMTP id 6F18737B410 for ; Mon, 15 Oct 2001 16:27:33 -0700 (PDT) Received: from xena.gsicomp.on.ca ([65.93.39.114]) by tomts20-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20011015232732.SSTY14703.tomts20-srv.bellnexxia.net@xena.gsicomp.on.ca> for ; Mon, 15 Oct 2001 19:27:32 -0400 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.1) with SMTP id f9FNJJW14781 for ; Mon, 15 Oct 2001 19:19:19 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <01cc01c155d1$2547e8c0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: Subject: Strange situation with NAT and sendmail Date: Mon, 15 Oct 2001 19:28:49 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've got two networks -- A (10.0.0.0/24) and B (192.168.0.0/24), both behind NAT gateways. The problem I'm having is that I cannot connect to the mail server on network A (10.0.0.2) from any machine behind the NAT gateway on network B. However, any system on network B can successfully ping the gateway of Network A, as well as connect to the two HTTP servers running on the same host as the mail server (10.0.0.2). The mail server is running, since I can connect to it from the NAT box on network A (via internal address) and via public port-forwarded address from the NAT box on network B. Why can't I connect to it from behind the network B's NAT gateway, when I can connect fine to other services running on the same machine? -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 16:54:19 2001 Delivered-To: freebsd-net@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 024AA37B410 for ; Mon, 15 Oct 2001 16:54:16 -0700 (PDT) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id f9FNs5O23397; Mon, 15 Oct 2001 16:54:05 -0700 (PDT) Message-ID: <3BCB771C.7040306@isi.edu> Date: Mon, 15 Oct 2001 16:54:04 -0700 From: Lars Eggert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.4) Gecko/20010924 X-Accept-Language: en, de MIME-Version: 1.0 To: Matthew Emmerton Cc: freebsd-net@freebsd.org Subject: Re: Strange situation with NAT and sendmail References: <01cc01c155d1$2547e8c0$1200a8c0@gsicomp.on.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Matthew Emmerton wrote: > I've got two networks -- A (10.0.0.0/24) and B (192.168.0.0/24), both > behind NAT gateways. > > The problem I'm having is that I cannot connect to the mail server on > network A (10.0.0.2) from any machine behind the NAT gateway on network B. > However, any system on network B can successfully ping the gateway of > Network A, as well as connect to the two HTTP servers running on the same > host as the mail server (10.0.0.2). The mail server is running, since I can > connect to it from the NAT box on network A (via internal address) and via > public port-forwarded address from the NAT box on network B. > > Why can't I connect to it from behind the network B's NAT gateway, when I > can connect fine to other services running on the same machine? Of course you know that NATs are evil. :-) You can't run servers behind NAT boxes, generally. Or more precisely: You can only run one instance of a few popular services on one machine behind a NAT box *and* the NAT box has to be set up to know where the traffic for that port should go to. Some services (those carrying network info in the payload) don't work at all with NATs unless the NAT box mucks with the payload data. The only one I know of that most NATs support is FTP - maybe sendmail puts network info into the payload, too? Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 17:51:45 2001 Delivered-To: freebsd-net@freebsd.org Received: from tomts10-srv.bellnexxia.net (tomts10.bellnexxia.net [209.226.175.54]) by hub.freebsd.org (Postfix) with ESMTP id 5CB4A37B409 for ; Mon, 15 Oct 2001 17:51:41 -0700 (PDT) Received: from xena.gsicomp.on.ca ([65.93.39.114]) by tomts10-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20011016005140.XSWL4321.tomts10-srv.bellnexxia.net@xena.gsicomp.on.ca>; Mon, 15 Oct 2001 20:51:40 -0400 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.1) with SMTP id f9G0hIW15111; Mon, 15 Oct 2001 20:43:18 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <030701c155dc$e152f180$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Graham Dunn" Cc: References: <01cc01c155d1$2547e8c0$1200a8c0@gsicomp.on.ca> <20011015200352.A29974@inscriber.com> Subject: Re: Strange situation with NAT and sendmail [ FIXED ] Date: Mon, 15 Oct 2001 20:52:49 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > On Mon, Oct 15, 2001 at 07:28:49PM -0400, Matthew Emmerton wrote: > > I've got two networks -- A (10.0.0.0/24) and B (192.168.0.0/24), both > > behind NAT gateways. > > > > The problem I'm having is that I cannot connect to the mail server on > > network A (10.0.0.2) from any machine behind the NAT gateway on network B. > > However, any system on network B can successfully ping the gateway of > > Network A, as well as connect to the two HTTP servers running on the same > > host as the mail server (10.0.0.2). The mail server is running, since I can > > connect to it from the NAT box on network A (via internal address) and via > > public port-forwarded address from the NAT box on network B. > > > > Why can't I connect to it from behind the network B's NAT gateway, when I > > can connect fine to other services running on the same machine? > > My first guess would be to see if you're really "unable" to connect to > sendmail. Check the configuration on sendmail to see if it's set up to > do reverse lookups. It may be trying to resolve the IP you're connecting > from. Try connecting and then let it sit until you see a time out (and > running tcpdump on the box you're trying tp connect from will tell you > if any packets are coming back). I forgot to mention, the mail server on network A is running on *cough* NT *cough*. It is in the process of being replaced by a FreeBSD system with sendmail, but not until the new year. I did a tcpdump on the NAT box on network A - it never records any incoming packets destined for port 25 whatsoever. However, it does record incoming packets for port 81 (the administration web server for the mail server.) Therein lies the answer. It would appear that the ISP providing me residential broadband has now started filtering outbound access to port 25 - you can only send via their mail server. This is why I can't connect to the mail server on the remote network, but everything else works fine. Sorry for the false alarm! -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 17:53: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 1075837B401 for ; Mon, 15 Oct 2001 17:53:00 -0700 (PDT) Received: from chimp.simianscience.com (cage.simianscience.com [64.7.134.1]) by smtp1.sentex.ca (8.11.6/8.11.6) with SMTP id f9G0quV60386; Mon, 15 Oct 2001 20:52:56 -0400 (EDT) (envelope-from mike@sentex.net) From: Mike Tancsa To: archie@dellroad.org (Archie Cobbs) Cc: freebsd-net@FreeBSD.ORG Subject: Re: strange results with increased net.inet.ip.intr_queue_maxlen (solved) Date: Mon, 15 Oct 2001 20:52:55 -0400 Message-ID: References: <5.1.0.14.0.20011012121150.072325d0@marble.sentex.ca> In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 15 Oct 2001 23:00:27 +0000 (UTC), in sentex.lists.freebsd.net you wrote: >Mike Tancsa writes: >> >If the forwarding path is maxed out, then it is the application = layer's >> >responsibility to back off (think TCP). >>=20 >> Is it better for the networking layer to deal with this (potentially=20 >> introducing some latency) as opposed to letting the application ? > >Oops, can substitute "transport" for "application".. > >But no, the network should just do "best effort".. that is, unless >you are a telco type in which case, go back to your X.25 :-) This >is a religious issue to some degree, but in practice the war is over >and the Internet won (vs. the telco way of doing things). > >There is probably a good paper somewhere outlining the "best effort" >philosophy but I don't know what it is. Another way to look at it >is intelligence in the leaf nodes rather than in the network. This >is one of the central idea of the Internet dating back to a long >time ago. I guess the other big idea is packets instead of dedicated >circuits (which hog resources). Thanks for the info. Lugi Rizzo was kind enough to figure out what has been going on. I increased the queue size to 512 on both my OC-3 equipped machine (via the en device) as well as my pure FastE (via fxp) machines = and the problems have gone away. As to why this solved the problem Lugi = wrote, -------------- oh, did you see drops go to 0 when the queue size is 256 ? I missed this. Then it means another thing, you are receiving a very large burst of packet from the interface, larger than ipintrq, and this is why they get dropped. In fact, processing is done like this: in the interrupt driver, while you have packets you fetch them from the device and queue them in ipintrq. Once you are done with this (which could take very long and drain a lot of packets if either packets come in very fast, or the device queue is long and interrupts come late), you go up and process packets in ipintrq. Now, I am not 100% sure but the "en" device seems to have 512 slots in the receive queue, hence the problem... Normally, using fastforwarding would help because bypasses ipintrq and calls directly ip_input(), except that "en" calls atm_intr() which does not know anything about fastforwarding. I think the above should explain the problem, and then you can probably either set ipq_maxlen to a large enough value (like 512) or slightly modify the "en" driver to limit the burst of packets it produces to some more reasonable amount. Not my area though, you should contact the author of the device driver to see if this is possible. ----------------------------- ---Mike Mike Tancsa (mdtancsa@sentex.net) =09 Sentex Communications Corp, =09 Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers=20 could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 18:37:48 2001 Delivered-To: freebsd-net@freebsd.org Received: from mercury.is.co.za (mercury.is.co.za [196.4.160.222]) by hub.freebsd.org (Postfix) with ESMTP id BFD6E37B405 for ; Mon, 15 Oct 2001 18:37:44 -0700 (PDT) Received: from c1-pta-74.dial-up.net (c1-pta-74.dial-up.net [196.34.158.74]) by mercury.is.co.za (Postfix) with ESMTP id 3DCC83EC0; Tue, 16 Oct 2001 03:37:19 +0200 (SAST) Date: Tue, 16 Oct 2001 03:39:18 +0200 (SAST) From: The Psychotic Viper X-X-Sender: To: Matthew Emmerton Cc: Subject: Re: Strange situation with NAT and sendmail In-Reply-To: <01cc01c155d1$2547e8c0$1200a8c0@gsicomp.on.ca> Message-ID: <20011016032047.Q1152-100000@lucifer.fuzion.ath.cx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, On Mon, 15 Oct 2001, Matthew Emmerton wrote: > The problem I'm having is that I cannot connect to the mail server on > network A (10.0.0.2) from any machine behind the NAT gateway on network B. The mailserver is BEHIND the NAT box on network A? If so does your NAT do any form of forwarding? If its no to the second one you would either need to set up some forwarding rule, because you wouldnt have direct access from an external network (public or private class) to a machine behind a NAT gateway that is on a private network class. > However, any system on network B can successfully ping the gateway of > Network A, as well as connect to the two HTTP servers running on the same > host as the mail server (10.0.0.2). The mail server is running, since I can > connect to it from the NAT box on network A (via internal address) and via > public port-forwarded address from the NAT box on network B. The reason you can ping the gateway of the other network is because NAT is doing its job and translating ur ping request to send to the external net and back to sending the reply to you. So NAT is working and port-fwding is workin fine so safe to assume thats not the problem. > Why can't I connect to it from behind the network B's NAT gateway, when I > can connect fine to other services running on the same machine? Question though....are u possibly trying to connect to say 192.168.0.10 (for example) directly from your 10.0.0.10 box? For example : user@10.0.0.10# ping 192.168.0.10? If so that wouldnt pass throught ur NAT system on to the outside interface, due to the fact that unless set to route to the external device it would try to find that IP address on your local network , which in this case is 10.0.0.x (and no route is possibly set for 192.168.0.x at all thus sending the packets to effectivly nowhere). Hope you understood that, now for a "workaround" set up a forwarding rule on your network A system to foward to the system and port you want to connect to (maybe 25 in this case?) and connect to the NAT boxes IP and that port, it should work the way you want just on a different port. If I am unclear on anything or need help doing it just mail me off list and I am more than happy to help (would give me something to due to prevent insomnia aggrevated boredom). Seriously hope I helped, PsyV To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 18:52: 1 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 2115A37B40B for ; Mon, 15 Oct 2001 18:51:58 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f9G1ptH34482; Mon, 15 Oct 2001 21:51:55 -0400 (EDT) (envelope-from wollman) Date: Mon, 15 Oct 2001 21:51:55 -0400 (EDT) From: Garrett Wollman Message-Id: <200110160151.f9G1ptH34482@khavrinen.lcs.mit.edu> To: Mike Tancsa Cc: archie@dellroad.org (Archie Cobbs), freebsd-net@FreeBSD.ORG Subject: Re: strange results with increased net.inet.ip.intr_queue_maxlen (solved) In-Reply-To: References: <5.1.0.14.0.20011012121150.072325d0@marble.sentex.ca> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [Quoting Archie Cobbs, I think:] >> There is probably a good paper somewhere outlining the "best effort" >> philosophy but I don't know what it is. That would be ``End-to-End Arguments in System Design'' by Jerry Saltzer, Dave Reed, and Dave Clark, one of the most influential papers ever written on the topic of network protocol architecture. See for more details. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 20:45: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 53F8437B40D for ; Mon, 15 Oct 2001 20:45:03 -0700 (PDT) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id UAA49524; Mon, 15 Oct 2001 20:44:25 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.3/8.11.3) id f9G3iOd33944; Mon, 15 Oct 2001 20:44:24 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200110160344.f9G3iOd33944@arch20m.dellroad.org> Subject: Re: strange results with increased net.inet.ip.intr_queue_maxlen (solved) In-Reply-To: "from Mike Tancsa at Oct 15, 2001 08:52:55 pm" To: Mike Tancsa Date: Mon, 15 Oct 2001 20:44:24 -0700 (PDT) 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Mike Tancsa writes: > >> Is it better for the networking layer to deal with this (potentially > >> introducing some latency) as opposed to letting the application ? > > > >But no, the network should just do "best effort".. that is, unless > >you are a telco type in which case, go back to your X.25 :-) This > >is a religious issue to some degree, but in practice the war is over > >and the Internet won (vs. the telco way of doing things). > > Thanks for the info. Lugi Rizzo was kind enough to figure out what has > been going on. I increased the queue size to 512 on both my OC-3 equipped > machine (via the en device) as well as my pure FastE (via fxp) machines and > the problems have gone away. As to why this solved the problem Lugi wrote, > > -------------- > oh, did you see drops go to 0 when the queue size is 256 ? I missed > this. Then it means another thing, you are receiving a very large > burst of packet from the interface, larger than ipintrq, and this > is why they get dropped. This makes sense.. and that's is exactly what queues are for: absorbing bursts. If you have big bursts then you'll need big queues.. in general this is the only reason to have them. -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 Mon Oct 15 20:52:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 3A83937B413 for ; Mon, 15 Oct 2001 20:52:39 -0700 (PDT) Received: (from root@localhost) by cage.simianscience.com (8.11.6/8.11.6) id f9G3qcZ52973; Mon, 15 Oct 2001 23:52:38 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp.sentex.net (fcage [192.168.0.2]) by cage.simianscience.com (8.11.6/8.11.6av) with ESMTP id f9G3qY652965; Mon, 15 Oct 2001 23:52:34 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20011015234704.02bd7980@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 15 Oct 2001 23:52:32 -0400 To: Archie Cobbs From: Mike Tancsa Subject: Re: strange results with increased net.inet.ip.intr_queue_maxlen (solved) Cc: freebsd-net@freebsd.org In-Reply-To: <200110160344.f9G3iOd33944@arch20m.dellroad.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 08:44 PM 10/15/2001 -0700, Archie Cobbs wrote: >This makes sense.. and that's is exactly what queues are for: >absorbing bursts. If you have big bursts then you'll need big >queues.. in general this is the only reason to have them. The only mystery I didnt solve in the end was what was generating the bursts. The only commonality is that The machines in question are all running bgpd and zebra with a full view in the kernel. The bursts would happen once every 10min. But I am not aware of any timers that would run at that long an interval. I think I will ask over on the zebra list to see if this interval rings a bell with anyone. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 15 21:15:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id CB50637B40B for ; Mon, 15 Oct 2001 21:15:13 -0700 (PDT) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id VAA49671; Mon, 15 Oct 2001 21:02:59 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.3/8.11.3) id f9G42v634057; Mon, 15 Oct 2001 21:02:57 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200110160402.f9G42v634057@arch20m.dellroad.org> Subject: Re: strange results with increased net.inet.ip.intr_queue_maxlen (solved) In-Reply-To: <5.1.0.14.0.20011015234704.02bd7980@192.168.0.12> "from Mike Tancsa at Oct 15, 2001 11:52:32 pm" To: Mike Tancsa Date: Mon, 15 Oct 2001 21:02:57 -0700 (PDT) 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Mike Tancsa writes: > At 08:44 PM 10/15/2001 -0700, Archie Cobbs wrote: > >This makes sense.. and that's is exactly what queues are for: > >absorbing bursts. If you have big bursts then you'll need big > >queues.. in general this is the only reason to have them. > > The only mystery I didnt solve in the end was what was generating the > bursts. The only commonality is that > > The machines in question are all running bgpd and zebra with a full view in > the kernel. > > The bursts would happen once every 10min. But I am not aware of any timers > that would run at that long an interval. I think I will ask over on the > zebra list to see if this interval rings a bell with anyone. Could possibly be ARP related, if something is caching packets while an ARP entry is being resolved. For a semi-related issue, see PR #25517: http://www.freebsd.org/cgi/query-pr.cgi?pr=25517 -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 Tue Oct 16 11:16: 2 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 82A7537B40C; Tue, 16 Oct 2001 11:15:58 -0700 (PDT) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id CC46B4CE33; Tue, 16 Oct 2001 14:15:57 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id OAA11938; Tue, 16 Oct 2001 14:15:57 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id LAA07546; Tue, 16 Oct 2001 11:15:56 -0700 (PDT) Message-Id: <200110161815.LAA07546@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: jerry_murdock@yahoo.com Subject: Re: Squid Inside a Jail Fails - DNS Errors Cc: freebsd-questions@freebsd.org, freebsd-net@freebsd.org Date: Tue, 16 Oct 2001 11:15:56 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Can you try telling squid to bind to the jail IP address with the 'udp_outgoing_address' option? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 16 14: 4:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from fepZ.post.tele.dk (fepz.post.tele.dk [195.41.46.133]) by hub.freebsd.org (Postfix) with ESMTP id 6A4C437B405 for ; Tue, 16 Oct 2001 14:04:11 -0700 (PDT) Received: from arnold.neland.dk ([62.243.124.200]) by fepZ.post.tele.dk (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP id <20011016210407.PJMG2863.fepZ.post.tele.dk@arnold.neland.dk>; Tue, 16 Oct 2001 23:04:07 +0200 Received: from gina ([192.168.5.109]) by arnold.neland.dk (8.11.6/8.11.6) with SMTP id f9GL4cq01386; Tue, 16 Oct 2001 23:04:39 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <005c01c15686$13eead60$6d05a8c0@neland.dk> From: "Leif Neland" To: "Matthew Emmerton" , "Graham Dunn" Cc: References: <01cc01c155d1$2547e8c0$1200a8c0@gsicomp.on.ca> <20011015200352.A29974@inscriber.com> <030701c155dc$e152f180$1200a8c0@gsicomp.on.ca> Subject: Re: Strange situation with NAT and sendmail [ FIXED ] Date: Tue, 16 Oct 2001 23:03:58 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > I did a tcpdump on the NAT box on network A - it never records any incoming > packets destined for port 25 whatsoever. However, it does record incoming > packets for port 81 (the administration web server for the mail server.) > > Therein lies the answer. It would appear that the ISP providing me > residential broadband has now started filtering outbound access to port 25 - > you can only send via their mail server. This is why I can't connect to the > mail server on the remote network, but everything else works fine. Do you mean access to your port 25 from the outside is blocked? In that case, just put your ISP's mailservers as secondary MX, then you will get your mail from that server. It is done to avoid dumb people creating open relays, because they can't configure their mailservers properly. If you mean access from your network to port 25 outside, that is done to have control of YOU not spamming. Just your ISP's mailserver as smarthost. In general, it is done in the best interest of the rest of the internet. If you can not live with that, perhaps you can get full access for a fee... Or perhaps not, if your connection is classified as residential, then you shouldn't have need for that, they believe... Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 16 19:43:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from web14602.mail.yahoo.com (web14602.mail.yahoo.com [216.136.224.82]) by hub.freebsd.org (Postfix) with SMTP id 8181837B401 for ; Tue, 16 Oct 2001 19:43:45 -0700 (PDT) Message-ID: <20011017024343.7341.qmail@web14602.mail.yahoo.com> Received: from [66.156.10.164] by web14602.mail.yahoo.com via HTTP; Tue, 16 Oct 2001 19:43:43 PDT Date: Tue, 16 Oct 2001 19:43:43 -0700 (PDT) From: Jerry Murdock Subject: Re: Squid Inside a Jail Fails - DNS Errors To: Bill Fenner Cc: freebsd-questions@freebsd.org, freebsd-net@freebsd.org In-Reply-To: <200110161815.LAA07546@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --- Bill Fenner wrote: > > Can you try telling squid to bind to the jail IP address with the > 'udp_outgoing_address' option? > > Bill That did it. Hadn't tried it as the docs in squid.conf imply it's only used for ICP requests. Many thanks, Jerry __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 16 22: 0: 8 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 86EC737B408 for ; Tue, 16 Oct 2001 22:00:05 -0700 (PDT) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id VAA56900; Tue, 16 Oct 2001 21:48:51 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.3/8.11.3) id f9H4mof68845; Tue, 16 Oct 2001 21:48:50 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200110170448.f9H4mof68845@arch20m.dellroad.org> Subject: Re: load-balancing to multiple T1's In-Reply-To: <5.1.0.14.0.20011014124637.05a7a828@mail.Go2France.com> "from Len Conrad at Oct 14, 2001 12:49:19 pm" To: Len Conrad Date: Tue, 16 Oct 2001 21:48:50 -0700 (PDT) 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Len Conrad writes: > Is anybody using netgraph and multilink ppp (recommended by PHK) to > load-balance outgoing traffic over multiple (4 or more) T1's? stable? > efficient enough to push the T1's towards practial limits? Should work no problem. If you have FreeBSD on both ends, you might also consider a leaner approach using ng_one2many(4) and ng_iface(4)... e.g. +--------+ | ng0 | +--------+ || inet || || one +----------+ | one2many | +----------+ many0/ many1| \many2 / | \ [T1a] [T1b] [T1c] -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 17 1: 4:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from agayev.rt.net.tr (agayev.rt.net.tr [212.65.128.82]) by hub.freebsd.org (Postfix) with SMTP id B07C037B409 for ; Wed, 17 Oct 2001 01:04:10 -0700 (PDT) Received: (qmail 79641 invoked by uid 1000); 17 Oct 2001 11:04:33 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Oct 2001 11:04:33 -0000 Date: Wed, 17 Oct 2001 11:04:33 +0000 (GMT) From: Ismail YENIGUL To: Subject: CSELT TB and TS on FreeBSD help! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org hi i am trying to install an Tunnel Broker and Tunnel Server on a single FreeBSD 4.4-STABLE box. but i am a bit confused. i have also an IPv6 enabled Cisco router. currently i install CSELT Tunnel Broker web interface. i works very well. but i do not know how to configure same FreeBSD box as a Tunnel Server. After Configuring to Tunnel Server , what should i do to forward all packages that comes from clients to IPv6 Cisco Router ? Best regards If you know what you are doing, you would be bored ! Ismail YENIGUL RT.NET To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 17 6:17:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from web20005.mail.yahoo.com (web20005.mail.yahoo.com [216.136.225.68]) by hub.freebsd.org (Postfix) with SMTP id D24DC37B40A for ; Wed, 17 Oct 2001 06:17:55 -0700 (PDT) Message-ID: <20011017131755.12965.qmail@web20005.mail.yahoo.com> Received: from [193.123.204.66] by web20005.mail.yahoo.com via HTTP; Wed, 17 Oct 2001 14:17:55 BST Date: Wed, 17 Oct 2001 14:17:55 +0100 (BST) From: =?iso-8859-1?q?Gavin=20Kenny?= Subject: TCP Flavour To: net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, What flavour of TCP is standard in the FreeBSD stack, is it Reno or New Reno, Vegas, Tahoe any others? many thanks Gavin p.s. can you cc me as I am not subscribed to this list. ____________________________________________________________ Nokia Game is on again. Go to http://uk.yahoo.com/nokiagame/ and join the new all media adventure before November 3rd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 17 8:33:36 2001 Delivered-To: freebsd-net@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id CAD7F37B403; Wed, 17 Oct 2001 08:33:28 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f9HFXKB32064; Wed, 17 Oct 2001 11:33:20 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 17 Oct 2001 11:33:20 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jerry Murdock Cc: Bill Fenner , freebsd-questions@freebsd.org, freebsd-net@freebsd.org Subject: Re: Squid Inside a Jail Fails - DNS Errors In-Reply-To: <20011017024343.7341.qmail@web14602.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 16 Oct 2001, Jerry Murdock wrote: > --- Bill Fenner wrote: > > > > Can you try telling squid to bind to the jail IP address with the > > 'udp_outgoing_address' option? > > > > Bill > > That did it. Hadn't tried it as the docs in squid.conf imply it's only > used for ICP requests. Hmm. So it sounds like there's a bug in the jail UDP code, perhaps relating to not catching all relevant instance of INADDR_ANY. Would be fascinating to see an appropriately scoped truss/ktrace output covering activities on the fd associated with the socket in question, resulting in EINVAL. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 17 9:59:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from c527597-a.cstvl1.sfba.home.com (c527597-a.cstvl1.sfba.home.com [24.176.204.87]) by hub.freebsd.org (Postfix) with ESMTP id 0E19C37B40A for ; Wed, 17 Oct 2001 09:59:25 -0700 (PDT) Received: (from bmah@localhost) by c527597-a.cstvl1.sfba.home.com (8.11.6/8.11.6) id f9HGxNs04904; Wed, 17 Oct 2001 09:59:23 -0700 (PDT) (envelope-from bmah) Message-Id: <200110171659.f9HGxNs04904@c527597-a.cstvl1.sfba.home.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: =?iso-8859-1?q?Gavin=20Kenny?= Cc: net@FreeBSD.ORG Subject: Re: TCP Flavour In-Reply-To: <20011017131755.12965.qmail@web20005.mail.yahoo.com> References: <20011017131755.12965.qmail@web20005.mail.yahoo.com> Comments: In-reply-to =?iso-8859-1?q?Gavin=20Kenny?= message dated "Wed, 17 Oct 2001 14:17:55 +0100." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-411949674P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Wed, 17 Oct 2001 09:59:23 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --==_Exmh_-411949674P Content-Type: text/plain; charset=us-ascii If memory serves me right, =?iso-8859-1?q?Gavin=20Kenny?= wrote: > What flavour of TCP is standard in the FreeBSD stack, > is it Reno or New Reno, Vegas, Tahoe any others? You didn't say what version of FreeBSD you were concerned with, but 4.3-RELEASE and later versions all use NewReno. Bruce. --==_Exmh_-411949674P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7zbjq2MoxcVugUsMRAuYvAJ4hfyxiYQvLnuOhPnxFzc/bLqJe9gCg5/53 aFgLdglsxk5vd9i4MvE01RY= =NCMt -----END PGP SIGNATURE----- --==_Exmh_-411949674P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 17 10:43:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id C61AA37B407; Wed, 17 Oct 2001 10:43:52 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f9HHhpR55404; Wed, 17 Oct 2001 13:43:51 -0400 (EDT) (envelope-from wollman) Date: Wed, 17 Oct 2001 13:43:51 -0400 (EDT) From: Garrett Wollman Message-Id: <200110171743.f9HHhpR55404@khavrinen.lcs.mit.edu> To: bmah@FreeBSD.ORG Cc: =?iso-8859-1?q?Gavin=20Kenny?= , net@FreeBSD.ORG Subject: Re: TCP Flavour In-Reply-To: <200110171659.f9HGxNs04904@c527597-a.cstvl1.sfba.home.com> References: <20011017131755.12965.qmail@web20005.mail.yahoo.com> <200110171659.f9HGxNs04904@c527597-a.cstvl1.sfba.home.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > If memory serves me right, =?iso-8859-1?q?Gavin=20Kenny?= wrote: >> What flavour of TCP is standard in the FreeBSD stack, >> is it Reno or New Reno, Vegas, Tahoe any others? > You didn't say what version of FreeBSD you were concerned with, but > 4.3-RELEASE and later versions all use NewReno. Well, um, yes and no. FreeBSD includes the ``NewReno'' algorithm, but it is probably not appropriate to characterize FreeBSD's TCP stack in that way. I would say that FreeBSD implementes the FreeBSD flavor of TCP, which is a unique blend of ideas from many outside efforts, and is based originally on the 4.4BSD stack. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 17 10:50:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from c527597-a.cstvl1.sfba.home.com (c527597-a.cstvl1.sfba.home.com [24.176.204.87]) by hub.freebsd.org (Postfix) with ESMTP id A361D37B407; Wed, 17 Oct 2001 10:50:26 -0700 (PDT) Received: (from bmah@localhost) by c527597-a.cstvl1.sfba.home.com (8.11.6/8.11.6) id f9HHoJc05421; Wed, 17 Oct 2001 10:50:19 -0700 (PDT) (envelope-from bmah) Message-Id: <200110171750.f9HHoJc05421@c527597-a.cstvl1.sfba.home.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Garrett Wollman Cc: bmah@FreeBSD.ORG, =?iso-8859-1?q?Gavin=20Kenny?= , net@FreeBSD.ORG Subject: Re: TCP Flavour In-Reply-To: <200110171743.f9HHhpR55404@khavrinen.lcs.mit.edu> References: <20011017131755.12965.qmail@web20005.mail.yahoo.com> <200110171659.f9HGxNs04904@c527597-a.cstvl1.sfba.home.com> <200110171743.f9HHhpR55404@khavrinen.lcs.mit.edu> Comments: In-reply-to Garrett Wollman message dated "Wed, 17 Oct 2001 13:43:51 -0400." From: bmah@FreeBSD.ORG (Bruce A. Mah) Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-371035866P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Wed, 17 Oct 2001 10:50:19 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --==_Exmh_-371035866P Content-Type: text/plain; charset=us-ascii If memory serves me right, Garrett Wollman wrote: > < said: > > > If memory serves me right, =?iso-8859-1?q?Gavin=20Kenny?= wrote: > > >> What flavour of TCP is standard in the FreeBSD stack, > >> is it Reno or New Reno, Vegas, Tahoe any others? > > > You didn't say what version of FreeBSD you were concerned with, but > > 4.3-RELEASE and later versions all use NewReno. > > Well, um, yes and no. FreeBSD includes the ``NewReno'' algorithm, but > it is probably not appropriate to characterize FreeBSD's TCP stack in > that way. I would say that FreeBSD implementes the FreeBSD flavor of > TCP, which is a unique blend of ideas from many outside efforts, and > is based originally on the 4.4BSD stack. OK, that's a fair characterization. There's more to TCP than the congestion control and retransmission algorithms...other things such as initial sequence number generation (RFC 1948 or some variant thereof), timestamps (RFC 1323), etc. Bruce. --==_Exmh_-371035866P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7zcTb2MoxcVugUsMRAtnvAKDqa0xfkdPQE3gPDtxieYWUKm0FAACePED1 QLOvO6cddqhlQI7jtUsNG00= =zTsV -----END PGP SIGNATURE----- --==_Exmh_-371035866P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 17 13:40: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217]) by hub.freebsd.org (Postfix) with ESMTP id 35ADA37B405 for ; Wed, 17 Oct 2001 13:40:01 -0700 (PDT) Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87]) by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f9HKeTQ22613 for ; Wed, 17 Oct 2001 15:40:29 -0500 (CDT) Received: from daebh001.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 17 Oct 2001 15:40:00 -0500 Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966); Wed, 17 Oct 2001 15:40:13 -0500 content-class: urn:content-classes:message Subject: Tools Date: Wed, 17 Oct 2001 16:39:35 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: X-MS-Has-Attach: X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 X-MS-TNEF-Correlator: Thread-Topic: Tools Thread-Index: AcFXTOiYaEkeIl80RyChE+lP1dTEUA== From: "Gopal Ram (NRC/Boston)" To: X-OriginalArrivalTime: 17 Oct 2001 20:40:13.0638 (UTC) FILETIME=[EBFB8E60:01C1574B] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I am looking for free tools for FreeBSD which can simulate more than one IPStack and feed packets as if it is coming from real network. Thanks and Regards Ramg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 2:30:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 98FA937B403 for ; Thu, 18 Oct 2001 02:29:53 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [fec0::1:12]) by Awfulhak.org (8.11.6/8.11.6) with ESMTP id f9I9TYT07356; Thu, 18 Oct 2001 10:29:50 +0100 (BST) (envelope-from brian@freebsd-services.com) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.6/8.11.6) with ESMTP id f9I9TSb73055; Thu, 18 Oct 2001 10:29:28 +0100 (BST) (envelope-from brian@freebsd-services.com) Message-Id: <200110180929.f9I9TSb73055@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: chuakk@lycos.com Cc: jinmei@isl.rdc.toshiba.co.jp, itojun@iijlab.net, users@ipv6.org, freebsd-net@FreeBSD.ORG, brian@freebsd-services.com Subject: Re: IPv6 over (IPv4 over user-PPP over ISDN) using FreeBSD In-Reply-To: Message from "kim chua" of "Thu, 18 Oct 2001 11:43:08 +0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Oct 2001 10:29:28 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Try using the -current version of ppp. It supports IPv6 natively. You need to use ``iface add'' to assign non-link-level addresses. For example, I've got this in my laptop's config: iface add 2001:6f8:602:1::12 # global iface add fec0::1:12 fec0::1:1 # site-local > Hi, > > I've been testing IPv6 over IPv4 over User-PPP over ISDN on Freebsd 4.3-stable. > > I've managed to establish the PPP/ISDN connection between a machine acting as a server and the other as a client (using Xyzel TA). Both the machine can ping to one another. > > But the problem arises when I try to establish a tunnel(ipv6 o ipv4) using gif via the PPP/ISDN connection which uses tun interface. > > Here's what I did: > > Assuming the server has 10.0.0.1 and client has 10.0.0.2 address on their tun interfaces. > > ##server side## > > ifconfig gif0 up > ifconfig gif0 IPv6src-add IPv6dst-add > gifconfig gif0 10.0.0.1 10.0.0.2 > > ##client side## > > ifconfig gif0 up > ifconfig gif0 Ipv6src-add IPv6dst-add > gifconfig gif0 10.0.0.2 10.0.0.1 > > At this stage, I should be able to ping6 -I gif0 ff02::1 to verify that the gif tunnel is establish. However, it didn't on tun interface. > > As far as I know, it worked when i tried tunnelling on physical interfaces like xl0 or xl1 with valid IPv4 addresses. > > > Anyone got any ideas? > > btw, anyone knows about or tried PPPv6 ?? > > > thanks in advance, > > Kim Chua > Multimedia Super Corridor (MSC) > Cyberjaya > Malaysia -- Brian http://www.freebsd-services.com/ 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 Oct 18 3: 5:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 5DF4937B405; Thu, 18 Oct 2001 03:05:02 -0700 (PDT) Received: from v-ger.we.lc.ehu.es (v-ger [158.227.6.51]) by polaris.we.lc.ehu.es (8.11.6/8.11.6) with ESMTP id f9IA4uX20109; Thu, 18 Oct 2001 12:04:56 +0200 (MET DST) Received: (from jose@localhost) by v-ger.we.lc.ehu.es (8.11.6/8.11.6) id f9I9xTR01422; Thu, 18 Oct 2001 11:59:29 +0200 (CEST) (envelope-from jose) Date: Thu, 18 Oct 2001 11:59:29 +0200 From: "Jose M. Alcaide" To: Beech Rintoul Cc: current@FreeBSD.org, net@FreeBSD.org Subject: Re: arp: is using my IP address 0.0.0.0! ??!?!? Message-ID: <20011018115929.C921@v-ger.we.lc.ehu.es> References: <20011018065526.F3D4DC8@nebula.anchoragerescue.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011018065526.F3D4DC8@nebula.anchoragerescue.org>; from akbeech@anchoragerescue.org on Wed, Oct 17, 2001 at 10:55:25PM -0800 X-Operating-System: FreeBSD 4.4-RELEASE Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Oct 17, 2001 at 10:55:25PM -0800, Beech Rintoul wrote: > On Wed, 17 Oct 2001, Jose M. Alcaide wrote: > > After rebuilding the kernel two days ago (Oct 15), I am getting lots of > > messages like these: > > > > arp: 00:30:65:de:99:32 is using my IP address 0.0.0.0! > > arp: 00:0a:27:b0:a7:06 is using my IP address 0.0.0.0! > > arp: 00:30:65:d1:2f:cc is using my IP address 0.0.0.0! > > arp: 00:30:65:e9:57:5e is using my IP address 0.0.0.0! > > > > and so on. > > > > Neither ifconfig(8) nor arp(8) show anything unusual. > > > > I'm having the exact same problem. I connect to a large subnet /12 and I'm > getting flooded with these. This just started about a week ago. I'm also not > using DHCP. Any way of blocking this short of turning off all kernel messages? I found something interesting: these messages are caused by ARP requests carrying 0.0.0.0 as the sender IP address. All of them come from Apple Macintosh (over 40 different machines). I am not sure whether 0.0.0.0 is a legal sender IP address in an ARP request; 0.0.0.0 means "this" host, so that I think that it is a valid address when the machine doing the ARP request does not know its IP address yet (though this sounds stupid). Anyway, the fact is that -CURRENT can flood the console and /var/log/messages if there are many Macintosh sending these ARP requests in a LAN (as it is our case). I think that there is no reason to printf these messages, since 0.0.0.0 is a valid IP address meaning "this" host. -- ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 3:40:37 2001 Delivered-To: freebsd-net@freebsd.org Received: from smtp1.oskarmobil.cz (smtp1.oskarmobil.cz [217.77.161.133]) by hub.freebsd.org (Postfix) with ESMTP id 6EDE037B405; Thu, 18 Oct 2001 03:40:33 -0700 (PDT) Received: from wh01ex01.ceskymobil.cz (wh01ex01.oskarmobil.cz [172.20.116.17]) by smtp1.oskarmobil.cz (8.11.2/8.11.1) with ESMTP id f9IAafV87797; Thu, 18 Oct 2001 12:36:41 +0200 (CEST) (envelope-from Milon.Papezik@oskarmobil.cz) Received: by wh01ex01.oskarmobil.cz with Internet Mail Service (5.5.2653.19) id <40HA4ZNK>; Thu, 18 Oct 2001 12:38:02 +0200 Message-ID: From: Milon Papezik To: "'hackers@freebsd.org'" , "'net@freebsd.org'" Subject: netgraph one2many question Date: Thu, 18 Oct 2001 12:37:56 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-2" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, I would like to extend ng_one2many module to include automatic link failure datection, failover and FEC functionality. My question is: Are interface nodes able to send upstream notification that their state has changed or do I have to poll their status periodically as it is done in ng_fec module made kindly available by wpaul ? Thanks in advance, Milon -- milon.papezik@oskarmobil.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 4:20:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from web20008.mail.yahoo.com (web20008.mail.yahoo.com [216.136.225.71]) by hub.freebsd.org (Postfix) with SMTP id 6CDFA37B401 for ; Thu, 18 Oct 2001 04:20:11 -0700 (PDT) Message-ID: <20011018112010.69826.qmail@web20008.mail.yahoo.com> Received: from [193.123.204.66] by web20008.mail.yahoo.com via HTTP; Thu, 18 Oct 2001 12:20:10 BST Date: Thu, 18 Oct 2001 12:20:10 +0100 (BST) From: =?iso-8859-1?q?Gavin=20Kenny?= Subject: Re: TCP Flavour To: bmah@FreeBSD.ORG, Garrett Wollman Cc: bmah@FreeBSD.ORG, Gavin Kenny , net@FreeBSD.ORG In-Reply-To: <200110171750.f9HHoJc05421@c527597-a.cstvl1.sfba.home.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --- "Bruce A. Mah" wrote: > If memory serves me right, Garrett Wollman wrote: > > < Mah" said: > > > > > If memory serves me right, > =?iso-8859-1?q?Gavin=20Kenny?= wrote: > > > > >> What flavour of TCP is standard in the FreeBSD > stack, > > >> is it Reno or New Reno, Vegas, Tahoe any > others? > > > > > You didn't say what version of FreeBSD you were > concerned with, but > > > 4.3-RELEASE and later versions all use NewReno. > > > > Well, um, yes and no. FreeBSD includes the > ``NewReno'' algorithm, but > > it is probably not appropriate to characterize > FreeBSD's TCP stack in > > that way. I would say that FreeBSD implementes > the FreeBSD flavor of > > TCP, which is a unique blend of ideas from many > outside efforts, and > > is based originally on the 4.4BSD stack. > > OK, that's a fair characterization. There's more to > TCP than the > congestion control and retransmission > algorithms...other things such as > initial sequence number generation (RFC 1948 or some > variant thereof), > timestamps (RFC 1323), etc. > > Bruce. > Ah! OK. I was using 4.1 so I guess it uses plain Reno, I've been looking at Tranquility for space applications and comparing the two. Is there somewhere that documents all the differences between the different types, Reno, NewReno, Vegas, etc? Many thanks Gavin ____________________________________________________________ Nokia Game is on again. Go to http://uk.yahoo.com/nokiagame/ and join the new all media adventure before November 3rd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 7:39:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 70EAC37B407; Thu, 18 Oct 2001 07:39:20 -0700 (PDT) Received: from mindspring.com (dialup-209.247.141.141.Dial1.SanJose1.Level3.net [209.247.141.141]) by falcon.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f9IEcns04133; Thu, 18 Oct 2001 07:38:50 -0700 (PDT) Message-ID: <3BCEE9AD.6839DF3E@mindspring.com> Date: Thu, 18 Oct 2001 07:39:41 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jose M. Alcaide" Cc: Beech Rintoul , current@FreeBSD.org, net@FreeBSD.org Subject: Re: arp: is using my IP address 0.0.0.0! ??!?!? References: <20011018065526.F3D4DC8@nebula.anchoragerescue.org> <20011018115929.C921@v-ger.we.lc.ehu.es> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Jose M. Alcaide" wrote: > I found something interesting: these messages are caused by ARP requests > carrying 0.0.0.0 as the sender IP address. All of them come from Apple > Macintosh (over 40 different machines). I am not sure whether 0.0.0.0 is a > legal sender IP address in an ARP request; 0.0.0.0 means "this" host, so > that I think that it is a valid address when the machine doing the ARP > request does not know its IP address yet (though this sounds stupid). Most likely, these are ARPs for multicast for SLPv2 location of network resources, such as default gateway, etc., prior to stateless autoconfiguration. We discussed doing this on one of the IETF lists, as a side issue to IPv6 stateless autoconfiguration, which ends up giving you a routable address, in the context of permitting the reverse address to be set to a machine name outside your domain for a machine who got a routable stateless address from your domain. You may also want to look at the ZEROCONF working group list archives. > Anyway, the fact is that -CURRENT can flood the console and > /var/log/messages if there are many Macintosh sending these ARP requests > in a LAN (as it is our case). I think that there is no reason to printf > these messages, since 0.0.0.0 is a valid IP address meaning "this" host. Yes. This is basically a required use for a "whohas" for doing stateless autoconfiguration, both in IPv6 (routable) and IPv4 (in the presence of a NAT). The most recent DHCP and autoconfiguration RFC lets you ignore DHCP entirely, and it lets you have a DHCP server refuse an address to the host, with no recourse for the host to do the autoconfiguration (e.g. a properly configured DHCP server can make a conforming client not get an address at all). I don't think that, in that case, leaving the machine at 0.0.0.0 is a valid thing to do: the interface should probably be forced down instead. That said, it's probably a good idea to never ARP for 0.0.0.0, since a "who has" in that case is a really dumb idea, since, as weas pointed out, it's intended to mean "this host", in the absence of an IP address (i.e. 0.0.0.0 is not an IP address, it's a special value meaning "not an IP address"). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 7:40:24 2001 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 0118C37B407; Thu, 18 Oct 2001 07:40:04 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id f9IEdZN45805; Thu, 18 Oct 2001 17:39:35 +0300 (EEST) (envelope-from ru) Date: Thu, 18 Oct 2001 17:39:35 +0300 From: Ruslan Ermilov To: Darren Henderson Cc: stable@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: /kernel: arp_rtrequest: bad gateway value Message-ID: <20011018173935.A43019@sunbay.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from darren@bmv.state.me.us on Wed, Sep 26, 2001 at 01:08:40PM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Sep 26, 2001 at 01:08:40PM -0400, Darren Henderson wrote: > > Posted something similar the other day, but thought I would ask in a more > general way.... > > What causes this error? Looking at the archives and source it appears to be > related to aliases and if_inet.c > > What has changed between 4.3 and 4.4 that would account for this error > appearing under 4.4 but not appear under 4.3 on a system where the network > configuration has not changed? > > Everything appears to be working fine after the upgrade other then the > appearance of this message numerous times during the day with no apparent > pattern. > > Any thoughts appreciated. > There's the problem with routed(8). It issues a command similar to "route change ip ip" for each (but last) IP address of an interface if the route already exists and is different. This results in a changed route with AF_INET gateway, but route's IFA still points to Ethernet device and rt_ifa->ifa_rtrequest == arp_rtrequest. This results in this message as AF_INET != AF_LINK. The message is harmless. This is also reproduceable on a 4.1-RELEASE machine. How to repeat without routed(8): 1. Add IP address to your Ethernet interface: ifconfig rl0 192.168.1.1 alias 2. Create route for this address: ping -c1 192.168.1.1 3. Verify that the route was created with gateway of type AF_LINK: route -vn get 192.168.1.1 4. Change the route like routed(8) does: route change 192.168.1.1 192.168.1.1 5. Watch the dmesg(8) output then repeat "route get" command to see route's gateway changed to AF_INET: route -vn get 192.168.1.1 Cheers, -- 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 Thu Oct 18 7:48:36 2001 Delivered-To: freebsd-net@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 7E49F37B407; Thu, 18 Oct 2001 07:48:33 -0700 (PDT) Received: from mindspring.com (dialup-209.247.141.141.Dial1.SanJose1.Level3.net [209.247.141.141]) by pintail.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id HAA02475; Thu, 18 Oct 2001 07:48:09 -0700 (PDT) Message-ID: <3BCEEBDD.46121235@mindspring.com> Date: Thu, 18 Oct 2001 07:49:01 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jose M. Alcaide" , Beech Rintoul , current@FreeBSD.org, net@FreeBSD.org Subject: Re: arp: is using my IP address 0.0.0.0! ??!?!? References: <20011018065526.F3D4DC8@nebula.anchoragerescue.org> <20011018115929.C921@v-ger.we.lc.ehu.es> <3BCEE9AD.6839DF3E@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org To expand a little... > That said, it's probably a good idea to never ARP for 0.0.0.0, > since a "who has" in that case is a really dumb idea, since, > as weas pointed out, it's intended to mean "this host", in the > absence of an IP address (i.e. 0.0.0.0 is not an IP address, > it's a special value meaning "not an IP address"). It's probably also a good idea to make interfaces who have an IP of 0.0.0.0 _not_ respond to ARP requests for that address, and, just in case there are other idiots, we should also not give proxy ARP responses for that address, etiher. Ghah. I hate special cases... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 8:35:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 8767337B405 for ; Thu, 18 Oct 2001 08:35:47 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f9IFYRB65844; Thu, 18 Oct 2001 11:34:27 -0400 (EDT) (envelope-from wollman) Date: Thu, 18 Oct 2001 11:34:27 -0400 (EDT) From: Garrett Wollman Message-Id: <200110181534.f9IFYRB65844@khavrinen.lcs.mit.edu> To: =?iso-8859-1?q?Gavin=20Kenny?= Cc: net@FreeBSD.ORG Subject: Re: TCP Flavour In-Reply-To: <20011018112010.69826.qmail@web20008.mail.yahoo.com> References: <200110171750.f9HHoJc05421@c527597-a.cstvl1.sfba.home.com> <20011018112010.69826.qmail@web20008.mail.yahoo.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > Ah! OK. I was using 4.1 so I guess it uses plain Reno, No. > that documents all the differences between the > different types, Reno, NewReno, Vegas, etc? Not really, since those names are not particularly meaningful, and were mostly just invented by the researchers who were pushing their particular agendas. ``Vegas'' is Larry Peterson's version, ``NewReno'' is Janey Hoe's version, and so on. We can all agree that ``Reno'' is the version of TCP that was shipped in 4.3BSD-Reno, which was effectively an early beta of 4.4BSD but also the first official BSD release to contain the complete set of VJ congestion-control and -avoidance algorithms. If you look in the Stevens books, he had a completely different set of names. If there's a specific set of features which you need, we can tell you if FreeBSD implements them. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 9:54:44 2001 Delivered-To: freebsd-net@freebsd.org Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163]) by hub.freebsd.org (Postfix) with ESMTP id 2137B37B407 for ; Thu, 18 Oct 2001 09:54:35 -0700 (PDT) Received: from ukmail.uk.lucent.com (h135-86-160-50.lucent.com [135.86.160.50]) by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f9IGsXu06121 for ; Thu, 18 Oct 2001 12:54:33 -0400 (EDT) Received: from yahoo.com (mlgw010.uk.lucent.com [135.86.193.189]) by ukmail.uk.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id RAA19013; Thu, 18 Oct 2001 17:53:48 +0100 (BST) Message-ID: <3BCF091C.7AB601D8@yahoo.com> Date: Thu, 18 Oct 2001 17:53:48 +0100 From: Alexander Thorp Organization: Lucent Technologies X-Mailer: Mozilla 4.6C-CCK-MCD EMS-1.4 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: PPP problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I am unable to bring up PPP to my ISP. DNS works, but PING and all TCP-based protocols don't. I haven't tried any other UDP-based protocols. I have copied here ifconfig -a and netstat -rn output both before bringing the link up and while it is up. Lastly I have also copied the relevant lines from ppp.log. Does anybody have any idea what is going wrong and how I can fix it? Alex Thorp # cat /etc/ppp/ppp.conf default: set log local phase lcp ipcp debug set device /dev/cuaa1 set speed 115200 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATE1Q0 OK-AT-OK \\dATDT\\T TIMEOUT 40 CONNECT" freeserve: set phone "0123456789" set login set authname MYUSERNAME set authkey MYPASSWORD set timeout 180 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR enable dns # uname -a FreeBSD MYMACHINE.MYDOMAIN.CO.UK 4.4-RELEASE FreeBSD 4.4-RELEASE #0: Tue Sep 18 11:57:08 PDT 2001 murray@builder.FreeBSD.org:/usr/src/sys/compile/GENERIC i386 # ifconfig -a ep0: flags=8843 mtu 1500 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::260:97ff:fe16:71bf%ep0 prefixlen 64 scopeid 0x1 ether 00:60:97:16:71:bf media: Ethernet 10baseT/UTP lp0: flags=8810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 ppp0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 faith0: flags=8000 mtu 1500 # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire 127.0.0.1 127.0.0.1 UH 0 0 lo0 192.168.1 link#1 UC 1 0 ep0 192.168.1.5 0:60:8c:b9:82:ac UHLW 2 679 ep0 830 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%ep0/64 link#1 UC ep0 fe80::260:97ff:fe16:71bf%ep0 0:60:97:16:71:bf UHL lo0 fe80::%lo0/64 fe80::1%lo0 Uc lo0 fe80::1%lo0 link#3 UHL lo0 ff01::/32 ::1 U lo0 ff02::%ep0/32 link#1 UC ep0 ff02::%lo0/32 ::1 UC lo0 # ppp -background freeserve Working in background mode Using interface: tun0 Debug: ReadSystem: Checking freeserve (/etc/ppp/ppp.conf). Debug: wrote -1: cmd = Add, dst = 0, gateway = 200000a PPP enabled Phase: Parent: PPP enabled # ping www.freebsd.org PING freefall.freebsd.org (216.136.204.21): 56 data bytes ^C --- freefall.freebsd.org ping statistics --- 16 packets transmitted, 0 packets received, 100% packet loss # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 195.92.66.8 UGSc 1 26 tun0 127.0.0.1 127.0.0.1 UH 0 0 lo0 192.168.1 link#1 UC 1 0 ep0 192.168.1.5 0:60:8c:b9:82:ac UHLW 2 1578 ep0 643 195.92.66.8 62.136.215.63 UH 2 0 tun0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%ep0/64 link#1 UC ep0 fe80::260:97ff:fe16:71bf%ep0 0:60:97:16:71:bf UHL lo0 fe80::%lo0/64 fe80::1%lo0 Uc lo0 fe80::1%lo0 link#3 UHL lo0 fe80::%tun0/64 fe80::260:97ff:fe16:71bf%tun0 Uc tun0 fe80::260:97ff:fe16:71bf%tun0 link#7 UHL lo0 ff01::/32 ::1 U lo0 ff02::%ep0/32 link#1 UC ep0 ff02::%lo0/32 ::1 UC lo0 ff02::%tun0/32 fe80::260:97ff:fe16:71bf%tun0 UC tun0 # ifconfig -a ep0: flags=8843 mtu 1500 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::260:97ff:fe16:71bf%ep0 prefixlen 64 scopeid 0x1 ether 00:60:97:16:71:bf media: Ethernet 10baseT/UTP lp0: flags=8810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 ppp0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 faith0: flags=8000 mtu 1500 tun0: flags=8051 mtu 1500 inet6 fe80::260:97ff:fe16:71bf%tun0 prefixlen 64 scopeid 0x7 inet 62.136.215.63 --> 195.92.66.8 netmask 0xffffff00 Opened by PID 269 # cat ppp.log Oct 15 21:12:22 MYMACHINE ppp[268]: Phase: Using interface: tun0 Oct 15 21:12:23 MYMACHINE ppp[268]: Phase: deflink: Created in closed state Oct 15 21:12:23 MYMACHINE ppp[269]: Phase: PPP Started (background mode). Oct 15 21:12:23 MYMACHINE ppp[269]: Phase: bundle: Establish Oct 15 21:12:23 MYMACHINE ppp[269]: Phase: deflink: closed -> opening Oct 15 21:12:23 MYMACHINE ppp[269]: Phase: deflink: Connected! Oct 15 21:12:23 MYMACHINE ppp[269]: Phase: deflink: opening -> dial Oct 15 21:12:46 MYMACHINE ppp[269]: Phase: deflink: dial -> carrier Oct 15 21:12:47 MYMACHINE ppp[269]: Phase: deflink: /dev/cuaa1: CD detected Oct 15 21:12:47 MYMACHINE ppp[269]: Phase: deflink: carrier -> login Oct 15 21:12:47 MYMACHINE ppp[269]: Phase: deflink: login -> lcp Oct 15 21:12:50 MYMACHINE ppp[269]: Phase: bundle: Authenticate Oct 15 21:12:50 MYMACHINE ppp[269]: Phase: deflink: his = PAP, mine = none Oct 15 21:12:50 MYMACHINE ppp[269]: Phase: Pap Output: MYUSERNAME ******** Oct 15 21:12:50 MYMACHINE ppp[269]: Phase: Pap Input: SUCCESS () Oct 15 21:12:51 MYMACHINE ppp[269]: Phase: deflink: lcp -> open Oct 15 21:12:51 MYMACHINE ppp[269]: Phase: bundle: Network Oct 15 21:12:51 MYMACHINE ppp[268]: Phase: Parent: PPP enabled Oct 15 21:13:51 MYMACHINE ppp[269]: Phase: deflink: HDLC errors -> FCS: 2, ADDR: 0, COMD: 0, PROTO: 0 Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: Signal 15, terminate. Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: bundle: Terminate Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: open -> lcp Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: Disconnected! Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: lcp -> logout Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: logout -> hangup Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: Disconnected! Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: Connect time: 174 secs: 1538 octets in, 3311 octets out Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: : 45 packets in, 55 packets out Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: total 27 bytes/sec, peak 173 bytes/sec on Mon Oct 15 21:15:17 2001 Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: hangup -> closed Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: bundle: Dead Oct 15 21:15:18 MYMACHINE ppp[269]: Phase: PPP Terminated (normal). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 10: 1:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.fr.ipricot.com (imaps.fr.ipricot.com [195.154.74.8]) by hub.freebsd.org (Postfix) with ESMTP id 7CAA537B401 for ; Thu, 18 Oct 2001 10:00:56 -0700 (PDT) Received: from IPricot.com (ablangy.fr.ipricot.com [192.168.31.185]) by mail.fr.ipricot.com (8.11.4/8.11.3) with ESMTP id f9IH0os14581 for ; Thu, 18 Oct 2001 19:00:50 +0200 (CEST) (envelope-from Antoine.Blangy@IPricot.com) X-To: Message-ID: <3BCF0AD5.9D37E5F9@IPricot.com> Date: Thu, 18 Oct 2001 19:01:09 +0200 From: Antoine BLANGY Organization: IPricot X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: ICMP redirect Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I m currently working on ICMP redirect and i read in "TCP/IP Illustrated Vol 1 - The protocols", by W Richard Stevens, that 4.4BSD acting as a router checks if "the route being used for outgoing datagram must have been ..., and must not be the router's default route" (page 123). My questions are: - Why the route being used for outgoing datagram can't be the router's default route ? - Is it the same behavor on System V ? Thanks and regards, Antoine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 10: 7:51 2001 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 4B92537B407 for ; Thu, 18 Oct 2001 10:07:41 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.6/8.11.6) with ESMTP id f9IH7cT10981; Thu, 18 Oct 2001 18:07:39 +0100 (BST) (envelope-from brian@freebsd-services.com) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.6/8.11.6) with ESMTP id f9IH51b79512; Thu, 18 Oct 2001 18:05:01 +0100 (BST) (envelope-from brian@freebsd-services.com) Message-Id: <200110181705.f9IH51b79512@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Alexander Thorp Cc: freebsd-net@FreeBSD.ORG, brian@freebsd-services.com Subject: Re: PPP problem In-Reply-To: Message from Alexander Thorp of "Thu, 18 Oct 2001 17:53:48 BST." <3BCF091C.7AB601D8@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Oct 2001 18:05:01 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org You could try enabling tcp/ip and physical logging to see if data is being written as expected. I'd be surprised if this was a ppp problem - it doesn't look at the frame payload unless you're using NAT, filtering, or some of the more nasty log levels. Perhaps you've got some rogue firewall rules ? > I am unable to bring up PPP to my ISP. DNS works, but PING and all TCP-based > protocols don't. I haven't tried any other UDP-based protocols. I have copied > here ifconfig -a and netstat -rn output both before bringing the link up and > while it is up. Lastly I have also copied the relevant lines from ppp.log. > > Does anybody have any idea what is going wrong and how I can fix it? > > Alex Thorp > > # cat /etc/ppp/ppp.conf > > default: > set log local phase lcp ipcp debug > set device /dev/cuaa1 > set speed 115200 > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATE1Q0 OK-AT-OK > \\dATDT\\T TIMEOUT 40 CONNECT" > > freeserve: > set phone "0123456789" > set login > set authname MYUSERNAME > set authkey MYPASSWORD > set timeout 180 > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > add default HISADDR > enable dns > > # uname -a > FreeBSD MYMACHINE.MYDOMAIN.CO.UK 4.4-RELEASE FreeBSD 4.4-RELEASE #0: Tue Sep 18 > 11:57:08 PDT 2001 murray@builder.FreeBSD.org:/usr/src/sys/compile/GENERIC > i386 > > # ifconfig -a > ep0: flags=8843 mtu 1500 > inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::260:97ff:fe16:71bf%ep0 prefixlen 64 scopeid 0x1 > ether 00:60:97:16:71:bf > media: Ethernet 10baseT/UTP > > lp0: flags=8810 mtu 1500 > lo0: flags=8049 mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > inet 127.0.0.1 netmask 0xff000000 > ppp0: flags=8010 mtu 1500 > sl0: flags=c010 mtu 552 > faith0: flags=8000 mtu 1500 > > # netstat -rn > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > 127.0.0.1 127.0.0.1 UH 0 0 lo0 > 192.168.1 link#1 UC 1 0 ep0 > 192.168.1.5 0:60:8c:b9:82:ac UHLW 2 679 ep0 830 > > Internet6: > Destination Gateway Flags Netif > Expire > ::1 ::1 UH lo0 > fe80::%ep0/64 link#1 UC ep0 > fe80::260:97ff:fe16:71bf%ep0 0:60:97:16:71:bf UHL lo0 > fe80::%lo0/64 fe80::1%lo0 Uc lo0 > fe80::1%lo0 link#3 UHL lo0 > ff01::/32 ::1 U lo0 > ff02::%ep0/32 link#1 UC ep0 > ff02::%lo0/32 ::1 UC lo0 > > # ppp -background freeserve > Working in background mode > Using interface: tun0 > Debug: ReadSystem: Checking freeserve (/etc/ppp/ppp.conf). > Debug: wrote -1: cmd = Add, dst = 0, gateway = 200000a > PPP enabled > Phase: Parent: PPP enabled > > # ping www.freebsd.org > PING freefall.freebsd.org (216.136.204.21): 56 data bytes > ^C > --- freefall.freebsd.org ping statistics --- > 16 packets transmitted, 0 packets received, 100% packet loss > > # netstat -rn > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 195.92.66.8 UGSc 1 26 tun0 > 127.0.0.1 127.0.0.1 UH 0 0 lo0 > 192.168.1 link#1 UC 1 0 ep0 > 192.168.1.5 0:60:8c:b9:82:ac UHLW 2 1578 ep0 643 > 195.92.66.8 62.136.215.63 UH 2 0 tun0 > > Internet6: > Destination Gateway Flags Netif > Expire > ::1 ::1 UH lo0 > fe80::%ep0/64 link#1 UC ep0 > fe80::260:97ff:fe16:71bf%ep0 0:60:97:16:71:bf UHL lo0 > fe80::%lo0/64 fe80::1%lo0 Uc lo0 > fe80::1%lo0 link#3 UHL lo0 > fe80::%tun0/64 fe80::260:97ff:fe16:71bf%tun0 Uc tun0 > fe80::260:97ff:fe16:71bf%tun0 link#7 UHL lo0 > ff01::/32 ::1 U lo0 > ff02::%ep0/32 link#1 UC ep0 > ff02::%lo0/32 ::1 UC lo0 > ff02::%tun0/32 fe80::260:97ff:fe16:71bf%tun0 UC tun0 > # ifconfig -a > ep0: flags=8843 mtu 1500 > inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::260:97ff:fe16:71bf%ep0 prefixlen 64 scopeid 0x1 > ether 00:60:97:16:71:bf > media: Ethernet 10baseT/UTP > > lp0: flags=8810 mtu 1500 > lo0: flags=8049 mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > inet 127.0.0.1 netmask 0xff000000 > ppp0: flags=8010 mtu 1500 > sl0: flags=c010 mtu 552 > faith0: flags=8000 mtu 1500 > tun0: flags=8051 mtu 1500 > inet6 fe80::260:97ff:fe16:71bf%tun0 prefixlen 64 scopeid 0x7 > inet 62.136.215.63 --> 195.92.66.8 netmask 0xffffff00 > Opened by PID 269 > > # cat ppp.log > Oct 15 21:12:22 MYMACHINE ppp[268]: Phase: Using interface: tun0 > Oct 15 21:12:23 MYMACHINE ppp[268]: Phase: deflink: Created in closed state > Oct 15 21:12:23 MYMACHINE ppp[269]: Phase: PPP Started (background mode). > Oct 15 21:12:23 MYMACHINE ppp[269]: Phase: bundle: Establish > Oct 15 21:12:23 MYMACHINE ppp[269]: Phase: deflink: closed -> opening > Oct 15 21:12:23 MYMACHINE ppp[269]: Phase: deflink: Connected! > Oct 15 21:12:23 MYMACHINE ppp[269]: Phase: deflink: opening -> dial > Oct 15 21:12:46 MYMACHINE ppp[269]: Phase: deflink: dial -> carrier > Oct 15 21:12:47 MYMACHINE ppp[269]: Phase: deflink: /dev/cuaa1: CD detected > Oct 15 21:12:47 MYMACHINE ppp[269]: Phase: deflink: carrier -> login > Oct 15 21:12:47 MYMACHINE ppp[269]: Phase: deflink: login -> lcp > Oct 15 21:12:50 MYMACHINE ppp[269]: Phase: bundle: Authenticate > Oct 15 21:12:50 MYMACHINE ppp[269]: Phase: deflink: his = PAP, mine = none > Oct 15 21:12:50 MYMACHINE ppp[269]: Phase: Pap Output: MYUSERNAME ******** > Oct 15 21:12:50 MYMACHINE ppp[269]: Phase: Pap Input: SUCCESS () > Oct 15 21:12:51 MYMACHINE ppp[269]: Phase: deflink: lcp -> open > Oct 15 21:12:51 MYMACHINE ppp[269]: Phase: bundle: Network > Oct 15 21:12:51 MYMACHINE ppp[268]: Phase: Parent: PPP enabled > Oct 15 21:13:51 MYMACHINE ppp[269]: Phase: deflink: HDLC errors -> FCS: 2, ADDR: > 0, COMD: 0, PROTO: 0 > Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: Signal 15, terminate. > Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: bundle: Terminate > Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: open -> lcp > Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: Disconnected! > Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: lcp -> logout > Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: logout -> hangup > Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: Disconnected! > Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: Connect time: 174 secs: 1538 > octets in, 3311 octets out > Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: : 45 packets in, 55 packets > out > Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: total 27 bytes/sec, peak 173 > bytes/sec on Mon Oct 15 21:15:17 2001 > Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: deflink: hangup -> closed > Oct 15 21:15:17 MYMACHINE ppp[269]: Phase: bundle: Dead > Oct 15 21:15:18 MYMACHINE ppp[269]: Phase: PPP Terminated (normal). -- Brian http://www.freebsd-services.com/ 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 Oct 18 14:20:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailman.thenap.com (mailman.thenap.com [209.190.0.10]) by hub.freebsd.org (Postfix) with ESMTP id F22BB37B405 for ; Thu, 18 Oct 2001 14:20:07 -0700 (PDT) Received: by MAILMAN with Internet Mail Service (5.5.2653.19) id <42VNJFYH>; Thu, 18 Oct 2001 17:24:22 -0400 Message-ID: From: "Drew J. Weaver" To: "'bsdi-users@MAILINGLISTS.ORG'" Cc: "'freebsd-net@freebsd.org'" Subject: inetd on BSD urgent. Date: Thu, 18 Oct 2001 17:24:18 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1581B.3EB512A0" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1581B.3EB512A0 Content-Type: text/plain pop stream tcp nowait root /usr/libexec/tcpd /usr/local/lib/popper qpopper -c -C -R -F -S That is the command I am using in inetd.conf to call qpopper, it works on my 2 linux servers but for some reason inetd under bsd completely ignores everything after the qpopper is this standard? Is there a work around for this? ------_=_NextPart_001_01C1581B.3EB512A0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

pop     stream  tcp     nowait  = root    /usr/libexec/tcpd /usr/local/lib/popper qpopper -c -C -R -F -S

 

That is the command I am using in inetd.conf to call qpopper, it works on my 2 linux servers but for some reason inetd under = bsd completely ignores everything after the qpopper is this standard? Is there a work around = for this?

------_=_NextPart_001_01C1581B.3EB512A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 14:32:26 2001 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 4171F37B427 for ; Thu, 18 Oct 2001 14:32:19 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 06F2481D05; Thu, 18 Oct 2001 16:32:14 -0500 (CDT) Date: Thu, 18 Oct 2001 16:32:14 -0500 From: Alfred Perlstein To: "Drew J. Weaver" Cc: "'bsdi-users@MAILINGLISTS.ORG'" , "'freebsd-net@freebsd.org'" Subject: Re: inetd on BSD urgent. Message-ID: <20011018163213.C65676@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from drew.weaver@thenap.com on Thu, Oct 18, 2001 at 05:24:18PM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Drew J. Weaver [011018 16:20] wrote: > pop stream tcp nowait root /usr/libexec/tcpd > /usr/local/lib/popper qpopper -c -C -R -F -S > > That is the command I am using in inetd.conf to call qpopper, it works on my > 2 linux servers but for some reason inetd under bsd completely ignores > everything after the qpopper is this standard? Is there a work around for > this? isn't /usr/libexec/tcpd tcpwrappers? if it is just remove that, freebsd inetd has built in tcpwrapper support. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 14:33:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from webmail.chimesnet.com (mail001.level3.chc-chimes.com [63.211.16.2]) by hub.freebsd.org (Postfix) with ESMTP id 6EF9F37B401 for ; Thu, 18 Oct 2001 14:33:04 -0700 (PDT) Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by webmail.chimesnet.com (Postfix) with ESMTP id B86D8CAC502; Thu, 18 Oct 2001 17:33:03 -0400 (EDT) Received: by jade.chc-chimes.com (Postfix, from userid 1101) id 9F93E1C8D; Thu, 18 Oct 2001 17:32:56 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 91700385C; Thu, 18 Oct 2001 17:32:56 -0400 (EDT) Date: Thu, 18 Oct 2001 17:32:56 -0400 (EDT) From: Matt Ayres X-X-Sender: To: "Drew J. Weaver" Cc: "'bsdi-users@MAILINGLISTS.ORG'" , "'freebsd-net@freebsd.org'" Subject: Re: inetd on BSD urgent. In-Reply-To: Message-ID: <20011018173134.S56581-100000@jade.chc-chimes.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Look at your line again, note one is "popper" and one is "qpopper", you should change them to both be the same program name, perferably the one that is on your system. -- Matt Ayres On Thu, 18 Oct 2001, Drew J. Weaver wrote: > pop stream tcp nowait root /usr/libexec/tcpd > /usr/local/lib/popper qpopper -c -C -R -F -S > > That is the command I am using in inetd.conf to call qpopper, it works on my > 2 linux servers but for some reason inetd under bsd completely ignores > everything after the qpopper is this standard? Is there a work around for > this? > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 14:36: 1 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailman.thenap.com (mailman.thenap.com [209.190.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 3888737B403 for ; Thu, 18 Oct 2001 14:35:49 -0700 (PDT) Received: by MAILMAN with Internet Mail Service (5.5.2653.19) id <42VNJFY5>; Thu, 18 Oct 2001 17:40:12 -0400 Message-ID: From: "Drew J. Weaver" To: 'Matt Ayres' Cc: "'bsdi-users@MAILINGLISTS.ORG'" , "'freebsd-net@freebsd.org'" Subject: RE: inetd on BSD urgent. Date: Thu, 18 Oct 2001 17:40:03 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1581D.725CBA20" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1581D.725CBA20 Content-Type: text/plain Erm, popper qpopper is how you're supposed to call qpopper. -Drew -----Original Message----- From: Matt Ayres [mailto:mayres@chimesnet.com] Sent: Thursday, October 18, 2001 5:33 PM To: Drew J. Weaver Cc: 'bsdi-users@MAILINGLISTS.ORG'; 'freebsd-net@freebsd.org' Subject: Re: inetd on BSD urgent. Look at your line again, note one is "popper" and one is "qpopper", you should change them to both be the same program name, perferably the one that is on your system. -- Matt Ayres On Thu, 18 Oct 2001, Drew J. Weaver wrote: > pop stream tcp nowait root /usr/libexec/tcpd > /usr/local/lib/popper qpopper -c -C -R -F -S > > That is the command I am using in inetd.conf to call qpopper, it works on my > 2 linux servers but for some reason inetd under bsd completely ignores > everything after the qpopper is this standard? Is there a work around for > this? > ------_=_NextPart_001_01C1581D.725CBA20 Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: inetd on BSD urgent.

Erm, popper qpopper is how you're supposed to call = qpopper.

-Drew


-----Original Message-----
From: Matt Ayres [mailto:mayres@chimesnet.com] =
Sent: Thursday, October 18, 2001 5:33 PM
To: Drew J. Weaver
Cc: 'bsdi-users@MAILINGLISTS.ORG'; = 'freebsd-net@freebsd.org'
Subject: Re: inetd on BSD urgent.

Look at your line again, note one is = "popper" and one is "qpopper",
you should change them to both be the same program = name, perferably the one
that is on your system.

--
Matt Ayres


On Thu, 18 Oct 2001, Drew J. Weaver wrote:

> pop     stream  = tcp     nowait  root    = /usr/libexec/tcpd
> /usr/local/lib/popper qpopper -c -C -R -F = -S
>
> That is the command I am using in inetd.conf to = call qpopper, it works on my
> 2 linux servers but for some reason inetd under = bsd completely ignores
> everything after the qpopper is this standard? = Is there a work around for
> this?
>

------_=_NextPart_001_01C1581D.725CBA20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 14:36:25 2001 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id B4FBC37B403 for ; Thu, 18 Oct 2001 14:36:23 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id AA18681D05; Thu, 18 Oct 2001 16:36:23 -0500 (CDT) Date: Thu, 18 Oct 2001 16:36:23 -0500 From: Alfred Perlstein To: Matt Ayres Cc: "Drew J. Weaver" , "'bsdi-users@MAILINGLISTS.ORG'" , "'freebsd-net@freebsd.org'" Subject: Re: inetd on BSD urgent. Message-ID: <20011018163623.E65676@elvis.mu.org> References: <20011018173134.S56581-100000@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011018173134.S56581-100000@jade.chc-chimes.com>; from mayres@chimesnet.com on Thu, Oct 18, 2001 at 05:32:56PM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Matt Ayres [011018 16:33] wrote: > Look at your line again, note one is "popper" and one is "qpopper", > you should change them to both be the same program name, perferably the one > that is on your system. That shouldn't make a difference unless the program specifically examines argv[0] to determine what it was run as (like sendmail might). -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 14:43:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from pilchuck.reedmedia.net (pilchuck.reedmedia.net [63.145.197.178]) by hub.freebsd.org (Postfix) with ESMTP id 24E4D37B401 for ; Thu, 18 Oct 2001 14:43:10 -0700 (PDT) Received: from reed by pilchuck.reedmedia.net with local-esmtp (Exim 3.12 #1 (Debian)) id 15uKv9-0008St-00; Thu, 18 Oct 2001 14:41:43 -0700 Date: Thu, 18 Oct 2001 14:41:43 -0700 (PDT) From: "Jeremy C. Reed" To: "Drew J. Weaver" Cc: "'bsdi-users@MAILINGLISTS.ORG'" , "'freebsd-net@freebsd.org'" Subject: Re: inetd on BSD urgent. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 18 Oct 2001, Drew J. Weaver wrote: > pop stream tcp nowait root /usr/libexec/tcpd ^ ^ ^ ^ Make sure that service exists. ^ ^ This is the command to run ---------------- ^ Make sure it is the correct path. > /usr/local/lib/popper qpopper -c -C -R -F -S And this is the command (with its arguments) that tcpd will run (if it is okay with tcpd). As you can see, you should not have "qpopper" as an argument for popper. And make sure you have the correct path to popper. > That is the command I am using in inetd.conf to call qpopper, it works on my > 2 linux servers but for some reason inetd under bsd completely ignores > everything after the qpopper is this standard? Is there a work around for > this? I can see how this possible could work -- unless popper doesn't mind about invalid argument. Anyways, tcpd and inetd should complain (via log files) if there are problems. (Also, be sure to tell inetd with a HUP when you update its configs.) Good luck, Jeremy C. Reed BSD Resources -- http://bsd.reedmedia.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 14:43:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from smtp.clifftop.net (deepspace9.demon.co.uk [193.237.217.45]) by hub.freebsd.org (Postfix) with ESMTP id 906B237B403 for ; Thu, 18 Oct 2001 14:43:12 -0700 (PDT) Received: from workstation (machassociates-5.dsl.easynet.co.uk [217.204.162.181]) (authenticated bits=0) by smtp.clifftop.net (8.12.1/8.12.1) with ESMTP id f9ILgV70065163; Thu, 18 Oct 2001 22:42:32 +0100 (BST) From: "Danny Horne" To: "Drew J. Weaver" , Cc: "'freebsd-net@freebsd.org'" Subject: RE: inetd on BSD urgent. Date: Thu, 18 Oct 2001 22:43:24 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is how I'm calling Qpopper 4.0.3 in FreeBSD 4.4-STABLE - pop3 stream tcp nowait root /usr/sbin/popper -s -p 2 -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Drew J. Weaver Sent: Thursday 18 October 2001 10:24pm To: 'bsdi-users@MAILINGLISTS.ORG' Cc: 'freebsd-net@freebsd.org' Subject: inetd on BSD urgent. pop stream tcp nowait root /usr/libexec/tcpd /usr/local/lib/popper qpopper -c -C -R -F -S That is the command I am using in inetd.conf to call qpopper, it works on my 2 linux servers but for some reason inetd under bsd completely ignores everything after the qpopper is this standard? Is there a work around for this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 16:49: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 262F737B407 for ; Thu, 18 Oct 2001 16:49:03 -0700 (PDT) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id f9INn2O15585; Thu, 18 Oct 2001 16:49:02 -0700 (PDT) Message-ID: <3BCF6A6E.5000302@isi.edu> Date: Thu, 18 Oct 2001 16:49:02 -0700 From: Lars Eggert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.4) Gecko/20010924 X-Accept-Language: en, de MIME-Version: 1.0 To: net@freebsd.org, Yu-Shun Wang Subject: ARP & IP fragments Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, we're seeing a strange thing happening, related to ARP and IP fragments. In the tcpdump below, ifc is trying to send a large UDP message (~3x MTU) to dee. It does not have dee's MAC address in its ARP cache (happens both after an ARP timeout or an explicit ARP cache flush.) The ARP request/reply succeed, but then only the third IP fragment makes it out onto the wire: 16:36:27.550259 arp who-has dee.isi.edu tell ifc.isi.edu 16:36:27.550519 arp reply dee.isi.edu is-at 0:2:b3:2c:3:d9 16:36:27.550538 ifc.isi.edu > dee.isi.edu: (frag 11094:102@2960) (ttl 64, len 122) The IP protocol stats (netstat -s -p ip) go up correctly on ifc, "output datagrams fragmented" by 1 and "fragments created" by 3. The fragments never seem to make it into bpf or out on the wire though, and I see no other stats change or errors appear. This is with 4.4-RELEASE, but has happened (at least) since 4.2-RELEASE. Repeating this when an ARP entry for dee is present results in all three fragments to be sent: 16:36:54.255363 ifc.isi.edu.1309 > dee.isi.edu.1323: udp 3054 (frag 53580:1480@0+) (ttl 64, len 1500) 16:36:54.255369 ifc.isi.edu > dee.isi.edu: (frag 53580:1480@1480+) (ttl 64, len 1500) 16:36:54.255376 ifc.isi.edu > dee.isi.edu: (frag 53580:102@2960) (ttl 64, len 122) Any clues? Thanks, Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 17: 5:44 2001 Delivered-To: freebsd-net@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id F11B437B408 for ; Thu, 18 Oct 2001 17:05:40 -0700 (PDT) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id f9J05bO19221; Thu, 18 Oct 2001 17:05:37 -0700 (PDT) Message-ID: <3BCF6E50.9080904@isi.edu> Date: Thu, 18 Oct 2001 17:05:36 -0700 From: Lars Eggert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.4) Gecko/20010924 X-Accept-Language: en, de MIME-Version: 1.0 To: Lars Eggert Cc: net@freebsd.org, Yu-Shun Wang Subject: Re: ARP & IP fragments References: <3BCF6A6E.5000302@isi.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Lars Eggert wrote: > we're seeing a strange thing happening, related to ARP and IP fragments. It seems that Bill Paul saw the same thing back in 1998 (http://www.geocrawler.com/mail/msg.php3?msg_id=822366&list=165) but I couldn't find wheter this was ever resolved or not. Correction: > The IP protocol stats (netstat -s -p ip) go up correctly on ifc, "output > datagrams fragmented" by 1 and "fragments created" by 3. The fragments ^ first two > never seem to make it into bpf or out on the wire though, and I see no Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 17:27:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 7873E37B403 for ; Thu, 18 Oct 2001 17:27:56 -0700 (PDT) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id f9J0RrO25251; Thu, 18 Oct 2001 17:27:53 -0700 (PDT) Message-ID: <3BCF7389.9080104@isi.edu> Date: Thu, 18 Oct 2001 17:27:53 -0700 From: Lars Eggert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.4) Gecko/20010924 X-Accept-Language: en, de MIME-Version: 1.0 To: Lars Eggert Cc: net@freebsd.org, Yu-Shun Wang Subject: Re: ARP & IP fragments References: <3BCF6A6E.5000302@isi.edu> <3BCF6E50.9080904@isi.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Lars Eggert wrote: > we're seeing a strange thing happening, related to ARP and IP fragments. After a big of poking around, this is due to some code in arpresolve() and how struct llinfo_arp caches packets during lookup, see Stevens Vol. 2, page 699, the comment about lines 292-299. RFC 1122 also covers this. The structure that holds a packet while an ARP lookup for its destination is underway can only hold one packet. The problem is that if multiple packets arrive quickly for that destination, arpresolve() overwrites the cached packet with the last one it saw. For a fragment burst, this always causes the last fragment to be cached and eventually sent. Wouldn't it make more sense to do the ARP lookup before fragmentation, so that the unfragmented packet is cached? This should be OK according to RFC 1122, Section 2.3.2.2, which only specifies that the last of a set of packets to the same destination should be cached. Before fragmentation, there is only one packet... Also, according to the same section of RFC 1122, it should be OK to cache multiple packets here. Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 20:20: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 3DB5B37B403 for ; Thu, 18 Oct 2001 20:20:02 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f9J3Jx371649; Thu, 18 Oct 2001 23:19:59 -0400 (EDT) (envelope-from wollman) Date: Thu, 18 Oct 2001 23:19:59 -0400 (EDT) From: Garrett Wollman Message-Id: <200110190319.f9J3Jx371649@khavrinen.lcs.mit.edu> To: Lars Eggert Cc: net@FreeBSD.ORG, Yu-Shun Wang Subject: ARP & IP fragments In-Reply-To: <3BCF6A6E.5000302@isi.edu> References: <3BCF6A6E.5000302@isi.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > Hi, > we're seeing a strange thing happening, related to ARP and IP fragments. Not strange at all. The ARP cache only queues a single packet waiting for a reply, so the first few fragments you send get tossed. We could easily arrange it so that the first frag, rather than the last, gets sent, but it still wouldn't help you. Unfortunately, the FreeBSD codebase seems to be going in exactly the opposite direction of ILP, which would help. It might be an interesting exercise, and not terribly difficult, to restructure the network stack such that packets are queued before they are fragmented, and if the interface wants to fragment something it calls back up the stack to have it done. This would also allow smart network interfaces to provide hardware fragmentation assistance, which might be helpful on some media. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 20:27: 3 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 620D637B401 for ; Thu, 18 Oct 2001 20:27:01 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f9J3QEg58079; Thu, 18 Oct 2001 22:26:14 -0500 (CDT) (envelope-from jlemon) Date: Thu, 18 Oct 2001 22:26:14 -0500 (CDT) From: Jonathan Lemon Message-Id: <200110190326.f9J3QEg58079@prism.flugsvamp.com> To: wollman@khavrinen.lcs.mit.edu, net@freebsd.org Subject: Re: ARP & IP fragments X-Newsgroups: local.mail.freebsd-net In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In article you write: >calls back up the stack to have it done. This would also allow smart >network interfaces to provide hardware fragmentation assistance, which >might be helpful on some media. The code to support hardware fragmentation offload is already present in the codebase. However, I don't believe that any existing driver makes use of it at the moment. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 21: 8: 3 2001 Delivered-To: freebsd-net@freebsd.org Received: from w250.z064001178.sjc-ca.dsl.cnc.net (w250.z064001178.sjc-ca.dsl.cnc.net [64.1.178.250]) by hub.freebsd.org (Postfix) with SMTP id 5FAB437B401 for ; Thu, 18 Oct 2001 21:07:58 -0700 (PDT) Received: (qmail 848 invoked by uid 1000); 19 Oct 2001 04:08:19 -0000 Date: Thu, 18 Oct 2001 21:07:57 -0701 From: Jos Backus To: net@FreeBSD.ORG Subject: Re: cvs commit: ports/net/mpd-netgraph Makefile distinfo pkg-plist Message-ID: <20011018210757.B802@lizzy.bugworks.com> Reply-To: Jos Backus Mail-Followup-To: net@FreeBSD.ORG References: <200110190107.JAA04727@venus.cyber.mmu.edu.my> <200110190120.f9J1KtM75750@arch20m.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110190120.f9J1KtM75750@arch20m.dellroad.org> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org With the latest mpd-3.3 (which has MS-CHAPv2 support, yay!) I am seeing the following error(?): Oct 18 20:15:20 lizzy mpd: mpd: pid 6888, version 3.3 (root@lizzy.bugworks.com 2 0:00 18-Oct-2001) Oct 18 20:15:20 lizzy mpd: [ms-pptp] ppp node is "mpd6888-ms-pptp" Oct 18 20:15:20 lizzy mpd: [ms-pptp] using interface ng0 Oct 18 20:15:20 lizzy mpd: [ms-pptp] IFACE: Open event Oct 18 20:15:20 lizzy mpd: [ms-pptp] IPCP: Open event Oct 18 20:15:20 lizzy mpd: [ms-pptp] IPCP: state change Initial --> Starting Oct 18 20:15:20 lizzy mpd: [ms-pptp] IPCP: LayerStart Oct 18 20:15:20 lizzy mpd: [ms-pptp] bundle: OPEN event in state CLOSED Oct 18 20:15:20 lizzy mpd: [ms-pptp] opening link "work"... Oct 18 20:15:20 lizzy mpd: [work] link: OPEN event Oct 18 20:15:20 lizzy mpd: [work] LCP: Open event Oct 18 20:15:20 lizzy mpd: [work] LCP: state change Initial --> Starting Oct 18 20:15:20 lizzy mpd: [work] LCP: LayerStart Oct 18 20:15:20 lizzy mpd: [work] device: OPEN event in state DOWN Oct 18 20:15:20 lizzy mpd: pptp0: connecting to 207.46.125.13:1723 Oct 18 20:15:20 lizzy mpd: [work] device is now in state OPENING Oct 18 20:15:20 lizzy mpd: pptp0: connected to 207.46.125.13:1723 Oct 18 20:15:20 lizzy mpd: pptp0: attached to connection with 207.46.125.13:1723 Oct 18 20:15:20 lizzy mpd: pptp0-0: outgoing call connected at 14808325 bps Oct 18 20:15:20 lizzy mpd: [work] PPTP call successful # Error? Oct 18 20:15:20 lizzy mpd: [work] can't connect ksocket node: Operation now in p rogress Oct 18 20:15:20 lizzy mpd: pptp0-0: clearing call Oct 18 20:15:20 lizzy mpd: [work] device: DOWN event in state OPENING Oct 18 20:15:20 lizzy mpd: [work] device is now in state DOWN Oct 18 20:15:20 lizzy mpd: [work] link: DOWN event Oct 18 20:15:20 lizzy mpd: [work] LCP: Down event Oct 18 20:15:20 lizzy mpd: [work] device: OPEN event in state DOWN Oct 18 20:15:20 lizzy mpd: [work] pausing 7 seconds before open Oct 18 20:15:20 lizzy mpd: [work] device is now in state DOWN Oct 18 20:15:20 lizzy mpd: pptp0-0: peer call disconnected res=zero? err=none Oct 18 20:15:20 lizzy mpd: pptp0-0: killing channel Oct 18 20:15:20 lizzy mpd: pptp0: closing connection with 207.46.125.13:1723 Oct 18 20:15:20 lizzy mpd: pptp0: invalid length 16 for type 4 Oct 18 20:15:20 lizzy mpd: pptp0: killing connection with 207.46.125.13:1723 Oct 18 20:15:27 lizzy mpd: [work] device: OPEN event in state DOWN Oct 18 20:15:27 lizzy mpd: [work] pausing 1 seconds before open Oct 18 20:15:27 lizzy mpd: [work] device is now in state DOWN This is with Sundays' -current. lizzy:~jos# kldstat Id Refs Address Size Name 1 12 0xc0100000 29216c kernel 2 1 0xc0393000 42bb0 acpi.ko 3 1 0xc2b69000 4000 if_tap.ko 4 1 0xc2b6f000 5000 ng_socket.ko 5 8 0xc2b75000 11000 netgraph.ko 6 1 0xc2b8b000 5000 ng_ksocket.ko 7 1 0xc2b92000 4000 ng_iface.ko 8 1 0xc2b96000 8000 ng_ppp.ko 9 1 0xc2ba0000 5000 ng_bpf.ko 10 1 0xc2ba5000 5000 ng_vjc.ko 11 1 0xc2baa000 5000 ng_pptpgre.ko 12 1 0xc2baf000 4000 ng_mppc.ko Any idea what is going on? What could I be doing wrong? Thanks, -- Jos Backus _/ _/_/_/ Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ josb@cncdsl.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 18 23:48:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.kebne.se (mail.kebne.se [212.209.134.151]) by hub.freebsd.org (Postfix) with ESMTP id E106537B403; Thu, 18 Oct 2001 23:48:37 -0700 (PDT) Received: by mail.kebne.se with Internet Mail Service (5.5.2653.19) id ; Fri, 19 Oct 2001 08:48:40 +0200 Message-ID: <31A473DBB655D21180850008C71E251A031AB022@mail.kebne.se> From: Gunnar Olsson To: "Freebsd Hackers (E-mail)" , "Freebsd Net (E-mail)" Subject: TCP windowsize... Date: Fri, 19 Oct 2001 08:48:38 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Is there someone who can tell me how to set TCP windowsize? Best Regards, Gunnar ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gunnar Olsson Phone: +46 8 5062 5762 Xelerated Packet Devices AB Fax: +46 8 5455 3211 Regeringsgatan 67 Mobile: +46 73 3279765 SE-10386 Stockholm Web: http://www.xelerated.com Email: mailto:gunnar.olsson@xelerated.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 19 1:21:25 2001 Delivered-To: freebsd-net@freebsd.org Received: from yamato.ccrle.nec.de (yamato.ccrle.nec.de [195.37.70.1]) by hub.freebsd.org (Postfix) with ESMTP id EB7F637B407 for ; Fri, 19 Oct 2001 01:21:19 -0700 (PDT) Received: from citadel.mobility.ccrle.nec.de ([192.168.156.1]) by yamato.ccrle.nec.de (8.11.3/8.10.1) with ESMTP id f9J8N8f25964; Fri, 19 Oct 2001 10:23:08 +0200 (CEST) Received: by citadel.mobility.ccrle.nec.de (Postfix on SuSE eMail Server 2.0, from userid 30) id 6C325C25E; Fri, 19 Oct 2001 10:21:14 +0200 (CEST) To: Gunnar Olsson Subject: Re: TCP windowsize... Message-ID: <1003479674.3bcfe27a5cf9e@citadel.mobility.ccrle.nec.de> Date: Fri, 19 Oct 2001 10:21:14 +0200 (CEST) From: Martin.Stiemerling@ccrle.nec.de Cc: "Freebsd Net (E-mail)" References: <31A473DBB655D21180850008C71E251A031AB022@mail.kebne.se> In-Reply-To: <31A473DBB655D21180850008C71E251A031AB022@mail.kebne.se> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.3 X-Originating-IP: 192.168.102.83 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, look at tcp(4) of the man pages and the sysctl output: net.inet.tcp.sendspace net.inet.tcp.recvspace With sysctl -w you can set the parameters. Cheers Martin Zitiere Gunnar Olsson : > Hi, > Is there someone who can tell me how to set TCP windowsize? > > Best Regards, > Gunnar > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Gunnar Olsson Phone: +46 8 5062 5762 > Xelerated Packet Devices AB Fax: +46 8 5455 3211 > Regeringsgatan 67 Mobile: +46 73 3279765 > SE-10386 Stockholm > Web: http://www.xelerated.com > Email: mailto:gunnar.olsson@xelerated.com > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 19 2:13:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 2027F37B403; Fri, 19 Oct 2001 02:13:23 -0700 (PDT) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id LAA26862; Fri, 19 Oct 2001 11:12:48 +0200 (MET DST) Date: Fri, 19 Oct 2001 11:12:48 +0200 (CEST) From: Harti Brandt To: Terry Lambert Cc: "Jose M. Alcaide" , Beech Rintoul , , Subject: Re: arp: is using my IP address 0.0.0.0! ??!?!? In-Reply-To: <3BCEEBDD.46121235@mindspring.com> Message-ID: <20011019110116.Y1072-100000@beagle.fokus.gmd.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 18 Oct 2001, Terry Lambert wrote: TL>To expand a little... TL> TL>> That said, it's probably a good idea to never ARP for 0.0.0.0, TL>> since a "who has" in that case is a really dumb idea, since, TL>> as weas pointed out, it's intended to mean "this host", in the TL>> absence of an IP address (i.e. 0.0.0.0 is not an IP address, TL>> it's a special value meaning "not an IP address"). TL> TL>It's probably also a good idea to make interfaces who have an TL>IP of 0.0.0.0 _not_ respond to ARP requests for that address, TL>and, just in case there are other idiots, we should also not TL>give proxy ARP responses for that address, etiher. I have run tcpdump all night to find out what happens. The host receives an ARP request with a source address of 0.0.0.0: 18:33:51.222688 arp who-has hydra tell 0.0.0.0 0001 0800 0604 0001 0030 65c6 a174 0000 0000 0000 0000 0000 c1af 8755 5555 5555 5555 5555 5555 5555 5555 5555 5555 I think, this may happen if the host does not yet know it's IP address (DHCP maybe?). But FreeBSD-current for some unknown reason answers to this request: 18:33:51.222835 arp reply 0.0.0.0 is-at 0:60:97:a:99:f 0001 0800 0604 0002 0060 970a 990f 0000 0000 0030 65c6 a174 0000 0000 5555 5555 5555 5555 5555 5555 5555 5555 5555 and then prints: Oct 18 18:33:51 scotty /boot/kernel/kernel: arp: 00:30:65:c6:a1:74 is using my IP address 0.0.0.0! I think this is because I have an interface that is up and has NO IP address: lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 xl0: flags=8943 mtu 1500 inet 193.175.135.70 netmask 0xffffff00 broadcast 193.175.135.255 ether 00:60:97:0a:99:0f media: Ethernet 10baseT/UTP (10baseT/UTP ) hatm0: flags=841 mtu 9180 media: ATM UTP/155MBit status: active lane0: flags=8802 mtu 1516 ether 00:00:00:00:00:00 I think it is definitly wrong to assume that an interface with no IP address has IP address 0.0.0.0 harti TL>Ghah. I hate special cases... everything is a special case... harti TL> TL>-- Terry TL> TL>To Unsubscribe: send mail to majordomo@FreeBSD.org TL>with "unsubscribe freebsd-net" in the body of the message TL> -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fhg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 19 6: 2:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id B61F437B407; Fri, 19 Oct 2001 06:02:50 -0700 (PDT) Received: from v-ger.we.lc.ehu.es (v-ger [158.227.6.51]) by polaris.we.lc.ehu.es (8.11.6/8.11.6) with ESMTP id f9JD2lX26785; Fri, 19 Oct 2001 15:02:47 +0200 (MET DST) Received: (from jose@localhost) by v-ger.we.lc.ehu.es (8.11.6/8.11.6) id f9JCqkd01559; Fri, 19 Oct 2001 14:52:46 +0200 (CEST) (envelope-from jose) Date: Fri, 19 Oct 2001 14:52:46 +0200 From: "Jose M. Alcaide" To: Harti Brandt Cc: Terry Lambert , Beech Rintoul , current@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: arp: is using my IP address 0.0.0.0! ??!?!? Message-ID: <20011019145246.D327@v-ger.we.lc.ehu.es> References: <3BCEEBDD.46121235@mindspring.com> <20011019110116.Y1072-100000@beagle.fokus.gmd.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011019110116.Y1072-100000@beagle.fokus.gmd.de>; from brandt@fokus.gmd.de on Fri, Oct 19, 2001 at 11:12:48AM +0200 X-Operating-System: FreeBSD 4.4-RELEASE Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Oct 19, 2001 at 11:12:48AM +0200, Harti Brandt wrote: > I have run tcpdump all night to find out what happens. The host receives > an ARP request with a source address of 0.0.0.0: > > 18:33:51.222688 arp who-has hydra tell 0.0.0.0 > 0001 0800 0604 0001 0030 65c6 a174 0000 > 0000 0000 0000 0000 c1af 8755 5555 5555 > 5555 5555 5555 5555 5555 5555 5555 > > I think, this may happen if the host does not yet know it's IP address > (DHCP maybe?). > > But FreeBSD-current for some unknown reason answers to this request: > > 18:33:51.222835 arp reply 0.0.0.0 is-at 0:60:97:a:99:f > 0001 0800 0604 0002 0060 970a 990f 0000 > 0000 0030 65c6 a174 0000 0000 5555 5555 > 5555 5555 5555 5555 5555 5555 5555 > > and then prints: > > Oct 18 18:33:51 scotty /boot/kernel/kernel: arp: 00:30:65:c6:a1:74 is using my IP address 0.0.0.0! Same here. My -CURRENT system is replying to those ARP request which carry 0.0.0.0 as sender IP address: 14:43:33.706099 arp who-has 158.227.48.193 (ff:ff:ff:ff:ff:ff) tell 0.0.0.0 14:43:33.706152 arp reply 0.0.0.0 is-at 0:d0:b7:3e:a0:fb > I think this is because I have an interface that is up and has NO IP > address: I don't think so: # ifconfig -a fxp0: flags=8843 mtu 1500 inet 158.227.6.52 netmask 0xffffff00 broadcast 158.227.6.255 inet6 fe80::2d0:b7ff:fe3e:a0fb%fxp0 prefixlen 64 scopeid 0x1 inet6 fec0::9ee3:634 prefixlen 120 ether 00:d0:b7:3e:a0:fb media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 Something is broken in the ARP implementation of -CURRENT. --JMA -- ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 19 15:50:29 2001 Delivered-To: freebsd-net@freebsd.org Received: from atg.aciworldwide.com (h139-142-180-4.gtcust.grouptelecom.net [139.142.180.4]) by hub.freebsd.org (Postfix) with ESMTP id 8275F37B407 for ; Fri, 19 Oct 2001 15:50:27 -0700 (PDT) Received: from atg.aciworldwide.com (atg.aciworldwide.com [139.142.180.33]) by atg.aciworldwide.com (8.12.0/8.12.0) with ESMTP id f9JMoQ0H037736 for ; Fri, 19 Oct 2001 16:50:27 -0600 (MDT) Message-Id: <200110192250.f9JMoQ0H037736@atg.aciworldwide.com> To: freebsd-net@freebsd.org Subject: D-Link DGE-500T support X-URL: http://www.aciworldwide.com/ X-Notes-Item: Just say NO to Notes! Organization: ACI Worldwide - Advanced Technology Group Date: Fri, 19 Oct 2001 16:50:26 -0600 From: Lyndon Nerenberg Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Have any of you managed to get the DFE-500T running with the lge driver? lge(4) hints that this should work, but I don't see anything in the list archives to indicate that someone has actually used this NIC successfully. (Note: I'm talking about the NIC that talks over copper, not fibre.) --lyndon Lizzie Borden took an axe, And plunged it deep into the VAX; Don't you envy people who Do all the things YOU want to do? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 19 16: 5:53 2001 Delivered-To: freebsd-net@freebsd.org Received: from inje.iskon.hr (inje.iskon.hr [213.191.128.16]) by hub.freebsd.org (Postfix) with ESMTP id DEA9537B407; Fri, 19 Oct 2001 16:05:49 -0700 (PDT) Received: from tel.fer.hr (zg06-115.dialin.iskon.hr [213.191.148.116]) by mail.iskon.hr (8.11.4/8.11.4/Iskon 8.11.3-1) with ESMTP id f9JN5fR16234; Sat, 20 Oct 2001 01:05:43 +0200 (MEST) Message-ID: <3BD0B1D4.CFC32A4D@tel.fer.hr> Date: Sat, 20 Oct 2001 01:05:56 +0200 From: Marko Zec X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Cc: freebsd-net@freebsd.org Subject: fxp driver - receive interrupt bundling Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On http://fly.cc.fer.hr/~zec/index.html you can find a 4.4-RELEASE fxp driver source, with patches that incorporate receive interrupt bundling microcode, borrowed from the Intel's Linux e100 driver. Bundling interrupts for a couple of received Ethernet frames can significantly lower interrupt processing overhead, so if you have a really busy server or router or whatever this code can make a noticeable difference. On an 1200 MHz Athlon machine, the microcode saves around 10% of CPU utilization, with incoming traffic of 20k pps on a single interface. The code is tested on 82558 rev B0 hardware, I'd be glad to know how it works on other versions of Intel's fxp cards. Pls. send your comments, suggestions etc. to zec@tel.fer.hr Have fun! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 19 16:24:57 2001 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 177CB37B403 for ; Fri, 19 Oct 2001 16:24:42 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 4348314C2E; Sat, 20 Oct 2001 01:24:40 +0200 (CEST) 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: net@freebsd.org Subject: Small tweak to in_control() From: Dag-Erling Smorgrav Date: 20 Oct 2001 01:24:39 +0200 Message-ID: Lines: 22 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --=-=-= The attached patch makes sure that the address family on an in_ifaddr's netmask sockaddr is set to AF_INET. Apparently none of our kernel or userland code cares about this, but certain binaries from That Other OS, and possibly also applicatins ported from other OSes, expect the sockaddr returned by SIOCGIFNETMASK to have a valid address family. As far as I can determine, these changes are sufficient to ensure that ia_sockmask.sa_family is always AF_INET, but I'm not 100% certain, so I've added a KASSERT that checks this before returning from in_control(). I also don't know if similar changes are required in the IPv6 code. Comments? Objections? DES -- Dag-Erling Smorgrav - des@ofug.org --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=sockmask.diff Index: sys/netinet/in.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/in.c,v retrieving revision 1.59 diff -u -r1.59 in.c --- sys/netinet/in.c 1 Oct 2001 18:07:08 -0000 1.59 +++ sys/netinet/in.c 19 Oct 2001 23:15:31 -0000 @@ -198,7 +198,6 @@ struct in_aliasreq *ifra = (struct in_aliasreq *)data; struct sockaddr_in oldaddr; int error, hostIsNew, maskIsNew, s; - u_long i; switch (cmd) { case SIOCALIFADDR: @@ -286,6 +285,7 @@ ifa->ifa_dstaddr = (struct sockaddr *)&ia->ia_dstaddr; ifa->ifa_netmask = (struct sockaddr *)&ia->ia_sockmask; ia->ia_sockmask.sin_len = 8; + ia->ia_sockmask.sin_family = AF_INET; if (ifp->if_flags & IFF_BROADCAST) { ia->ia_broadaddr.sin_len = sizeof(ia->ia_addr); ia->ia_broadaddr.sin_family = AF_INET; @@ -362,8 +362,8 @@ (struct sockaddr_in *) &ifr->ifr_addr, 1)); case SIOCSIFNETMASK: - i = ifra->ifra_addr.sin_addr.s_addr; - ia->ia_subnetmask = ntohl(ia->ia_sockmask.sin_addr.s_addr = i); + ia->ia_sockmask.sin_addr = ifra->ifra_addr.sin_addr; + ia->ia_subnetmask = ntohl(ia->ia_sockmask.sin_addr.s_addr); break; case SIOCAIFADDR: @@ -381,6 +381,7 @@ if (ifra->ifra_mask.sin_len) { in_ifscrub(ifp, ia); ia->ia_sockmask = ifra->ifra_mask; + ia->ia_sockmask.sin_family = AF_INET; ia->ia_subnetmask = ntohl(ia->ia_sockmask.sin_addr.s_addr); maskIsNew = 1; @@ -439,6 +440,10 @@ return (EOPNOTSUPP); return ((*ifp->if_ioctl)(ifp, cmd, data)); } + + KASSERT(ia == NULL || ia->ia_sockmask.sin_family == AF_INET, + (__FUNCTION__ "(): ia_sockmask is not AF_INET")); + return (0); } --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 19 17:16:21 2001 Delivered-To: freebsd-net@freebsd.org Received: from root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id E3EEF37B401; Fri, 19 Oct 2001 17:16:17 -0700 (PDT) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id f9K0EFq89356; Fri, 19 Oct 2001 17:14:15 -0700 (PDT) (envelope-from dg) Date: Fri, 19 Oct 2001 17:14:15 -0700 From: David Greenman To: Marko Zec Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: fxp driver - receive interrupt bundling Message-ID: <20011019171415.B48897@nexus.root.com> References: <3BD0B1D4.CFC32A4D@tel.fer.hr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BD0B1D4.CFC32A4D@tel.fer.hr>; from zec@tel.fer.hr on Sat, Oct 20, 2001 at 01:05:56AM +0200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >On http://fly.cc.fer.hr/~zec/index.html you can find a 4.4-RELEASE fxp >driver source, with patches that incorporate receive interrupt bundling >microcode, borrowed from the Intel's Linux e100 driver. > >Bundling interrupts for a couple of received Ethernet frames can >significantly lower interrupt processing overhead, so if you have a >really busy server or router or whatever this code can make a noticeable >difference. On an 1200 MHz Athlon machine, the microcode saves around >10% of CPU utilization, with incoming traffic of 20k pps on a single >interface. > >The code is tested on 82558 rev B0 hardware, I'd be glad to know how it >works on other versions of Intel's fxp cards. > >Pls. send your comments, suggestions etc. to zec@tel.fer.hr > >Have fun! Nifty! -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 Fri Oct 19 17:50: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 4290C37B401 for ; Fri, 19 Oct 2001 17:49:59 -0700 (PDT) Received: from chimp.simianscience.com (cage.simianscience.com [64.7.134.1]) by smtp1.sentex.ca (8.11.6/8.11.6) with SMTP id f9K0nml20994; Fri, 19 Oct 2001 20:49:48 -0400 (EDT) (envelope-from mike@sentex.net) From: Mike Tancsa To: zec@tel.fer.hr (Marko Zec) Cc: freebsd-net@freebsd.org Subject: Re: fxp driver - receive interrupt bundling Date: Fri, 19 Oct 2001 20:49:48 -0400 Message-ID: References: In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 19 Oct 2001 23:06:16 +0000 (UTC), in sentex.lists.freebsd.hackers you wrote: >On http://fly.cc.fer.hr/~zec/index.html you can find a 4.4-RELEASE fxp >driver source, with patches that incorporate receive interrupt bundling >microcode, borrowed from the Intel's Linux e100 driver. > >Bundling interrupts for a couple of received Ethernet frames can >significantly lower interrupt processing overhead, so if you have a >really busy server or router or whatever this code can make a noticeable >difference. On an 1200 MHz Athlon machine, the microcode saves around >10% of CPU utilization, with incoming traffic of 20k pps on a single >interface. > >The code is tested on 82558 rev B0 hardware, I'd be glad to know how it >works on other versions of Intel's fxp cards. > >Pls. send your comments, suggestions etc. to zec@tel.fer.hr Hi, What values would you reccomend for a box with 4 fxp NICs in them ? Does it follow the the INT_DELAY should be lowered as you add more NICs ? ---Mike Mike Tancsa (mdtancsa@sentex.net) =09 Sentex Communications Corp, =09 Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers=20 could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 19 18:16:30 2001 Delivered-To: freebsd-net@freebsd.org Received: from inje.iskon.hr (inje.iskon.hr [213.191.128.16]) by hub.freebsd.org (Postfix) with ESMTP id 976E037B401 for ; Fri, 19 Oct 2001 18:16:25 -0700 (PDT) Received: from tel.fer.hr (zg03-106.dialin.iskon.hr [213.191.135.107]) by mail.iskon.hr (8.11.4/8.11.4/Iskon 8.11.3-1) with ESMTP id f9K1GER11679; Sat, 20 Oct 2001 03:16:14 +0200 (MEST) Message-ID: <3BD0D063.C084B21D@tel.fer.hr> Date: Sat, 20 Oct 2001 03:16:19 +0200 From: Marko Zec X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Tancsa Cc: freebsd-net@freebsd.org Subject: Re: fxp driver - receive interrupt bundling References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Mike Tancsa wrote: > > Hi, > What values would you reccomend for a box with 4 fxp NICs in them ? > Does it follow the the INT_DELAY should be lowered as you add more NICs ? > It doesn't matter how many fxp cards you have installed - if your box acts as a server than most probably you can leave INT_DELAY at default value (Intel proposes 0x600, but I think 0x400 would be more appropriate). If you use your multi-fxp-card BSD box as a router, than the microcode will impose additional delay *twice* (once in each direction), so in that case the default value of 0x600 might be too high for achieving full 100 megE throughput, because of TCP windowing scheme having to wait for ACK frames, which will be held in fxp receive buffers too long. On the other hand, setting INT_DELAY too low minimizes the benefits of bundling interrupts, as fewer received frames get "bundled" on a single interrupt. To summarize: if you are doing any routing (or bridging as I do), find the best value for INT_DELAY for your specific environment experimentally, it should be definitely smaller than or equal to 0x400. If you don't do packet forwarding between fxp interfaces, use the defaults. Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 19 18:20: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 83BB037B401 for ; Fri, 19 Oct 2001 18:20:01 -0700 (PDT) Received: (from root@localhost) by cage.simianscience.com (8.11.6/8.11.6) id f9K1K0K96595; Fri, 19 Oct 2001 21:20:00 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp.sentex.net (fcage [192.168.0.2]) by cage.simianscience.com (8.11.6/8.11.6av) with ESMTP id f9K1Ju696587; Fri, 19 Oct 2001 21:19:56 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20011019211817.05a05890@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 19 Oct 2001 21:19:54 -0400 To: Marko Zec From: Mike Tancsa Subject: Re: fxp driver - receive interrupt bundling Cc: freebsd-net@freebsd.org In-Reply-To: <3BD0D063.C084B21D@tel.fer.hr> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 03:16 AM 10/20/2001 +0200, Marko Zec wrote: >It doesn't matter how many fxp cards you have installed - if your box acts >as a >server than most probably you can leave INT_DELAY at default value (Intel >proposes 0x600, but I think 0x400 would be more appropriate). > >If you use your multi-fxp-card BSD box as a router, than the microcode will >impose additional delay *twice* (once in each direction), so in that case the >default value of 0x600 might be too high for achieving full 100 megE >throughput, because of TCP windowing scheme having to wait for ACK frames, >which will be held in fxp receive buffers too long. On the other hand, setting >INT_DELAY too low minimizes the benefits of bundling interrupts, as fewer >received frames get "bundled" on a single interrupt. > >To summarize: if you are doing any routing (or bridging as I do), find the >best >value for INT_DELAY for your specific environment experimentally, it should be >definitely smaller than or equal to 0x400. If you don't do packet forwarding >between fxp interfaces, use the defaults. Thanks! This is for a router pushing upwards of 20Mb/s with about 110K routes on 4 interfaces. I will try and experiment a bit on my test setup first to see what works best. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 19 18:41:35 2001 Delivered-To: freebsd-net@freebsd.org Received: from inje.iskon.hr (inje.iskon.hr [213.191.128.16]) by hub.freebsd.org (Postfix) with ESMTP id 15AC937B407 for ; Fri, 19 Oct 2001 18:41:31 -0700 (PDT) Received: from tel.fer.hr (zg06-007.dialin.iskon.hr [213.191.148.8]) by mail.iskon.hr (8.11.4/8.11.4/Iskon 8.11.3-1) with ESMTP id f9K1fSR16241; Sat, 20 Oct 2001 03:41:28 +0200 (MEST) Message-ID: <3BD0D653.EDC5EF8E@tel.fer.hr> Date: Sat, 20 Oct 2001 03:41:40 +0200 From: Marko Zec X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Tancsa Cc: freebsd-net@freebsd.org Subject: Re: fxp driver - receive interrupt bundling References: <5.1.0.14.0.20011019211817.05a05890@192.168.0.12> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Mike Tancsa wrote: > At 03:16 AM 10/20/2001 +0200, Marko Zec wrote: > >It doesn't matter how many fxp cards you have installed - if your box acts > >as a > >server than most probably you can leave INT_DELAY at default value (Intel > >proposes 0x600, but I think 0x400 would be more appropriate). > > > >If you use your multi-fxp-card BSD box as a router, than the microcode will > >impose additional delay *twice* (once in each direction), so in that case the > >default value of 0x600 might be too high for achieving full 100 megE > >throughput, because of TCP windowing scheme having to wait for ACK frames, > >which will be held in fxp receive buffers too long. On the other hand, setting > >INT_DELAY too low minimizes the benefits of bundling interrupts, as fewer > >received frames get "bundled" on a single interrupt. > > > >To summarize: if you are doing any routing (or bridging as I do), find the > >best > >value for INT_DELAY for your specific environment experimentally, it should be > >definitely smaller than or equal to 0x400. If you don't do packet forwarding > >between fxp interfaces, use the defaults. > > Thanks! This is for a router pushing upwards of 20Mb/s with about 110K > routes on 4 interfaces. I will try and experiment a bit on my test setup > first to see what works best. Nice - I'd be glad if you let us know the details after you complete the experiments. Probably you could try tweaking the BUNDLE_MAX as well, if it is supported by your fxp chipset - on my cards it is not, unfortunately. If you experience high traffic volumes, than having BUNDLE_MAX restricted to only 6 frames (default) can be somewhat unnecessary limitating. Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 20 0:28: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.nsu.ru (b.ns.ssc.nsu.ru [193.124.215.221]) by hub.freebsd.org (Postfix) with ESMTP id 4100A37B401; Sat, 20 Oct 2001 00:27:59 -0700 (PDT) Received: from iclub.nsu.ru ([193.124.222.66] ident=root) by mail.nsu.ru with esmtp (Exim 3.20 #1) id 15uqXh-00006Q-00; Sat, 20 Oct 2001 14:27:37 +0700 Received: (from fjoe@localhost) by iclub.nsu.ru (8.11.6/8.11.6) id f9K7RXI48565; Sat, 20 Oct 2001 14:27:33 +0700 (NSS) (envelope-from fjoe) Date: Sat, 20 Oct 2001 14:27:33 +0700 From: Max Khon To: "Jose M. Alcaide" Cc: Harti Brandt , Terry Lambert , Beech Rintoul , current@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: arp: is using my IP address 0.0.0.0! ??!?!? Message-ID: <20011020142733.A48164@iclub.nsu.ru> References: <3BCEEBDD.46121235@mindspring.com> <20011019110116.Y1072-100000@beagle.fokus.gmd.de> <20011019145246.D327@v-ger.we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011019145246.D327@v-ger.we.lc.ehu.es>; from jose@we.lc.ehu.es on Fri, Oct 19, 2001 at 02:52:46PM +0200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org hi, there! > Same here. My -CURRENT system is replying to those ARP request which carry > 0.0.0.0 as sender IP address: > > 14:43:33.706099 arp who-has 158.227.48.193 (ff:ff:ff:ff:ff:ff) tell 0.0.0.0 > 14:43:33.706152 arp reply 0.0.0.0 is-at 0:d0:b7:3e:a0:fb > > > I think this is because I have an interface that is up and has NO IP > > address: > > I don't think so: > > # ifconfig -a > fxp0: flags=8843 mtu 1500 > inet 158.227.6.52 netmask 0xffffff00 broadcast 158.227.6.255 > inet6 fe80::2d0:b7ff:fe3e:a0fb%fxp0 prefixlen 64 scopeid 0x1 > inet6 fec0::9ee3:634 prefixlen 120 > ether 00:d0:b7:3e:a0:fb > media: Ethernet autoselect (100baseTX ) > status: active > lo0: flags=8049 mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet 127.0.0.1 netmask 0xff000000 > > Something is broken in the ARP implementation of -CURRENT. please try this patch (provided by jlemon) Index: if_ether.c =================================================================== RCS file: /ncvs/src/sys/netinet/if_ether.c,v retrieving revision 1.85 diff -u -r1.85 if_ether.c --- if_ether.c 2001/10/17 18:07:05 1.85 +++ if_ether.c 2001/10/19 15:38:07 @@ -593,10 +593,12 @@ isaddr.s_addr == ia->ia_addr.sin_addr.s_addr) goto match; /* - * No match, use the first address on the receive interface + * No match, use the first inet address on the receive interface * as a dummy address for the rest of the function. */ - ifa = TAILQ_FIRST(&ifp->if_addrhead); + TAILQ_FOREACH(ifa, &ifp->if_addrhead, ifa_link) + if (ifa->ifa_addr && ifa->ifa_addr->sa_family == AF_INET) + break; if (ifa == NULL) { m_freem(m); return; /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 20 10:34:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from mta4.snfc21.pbi.net (mta4.snfc21.pbi.net [206.13.28.142]) by hub.freebsd.org (Postfix) with ESMTP id 8DCCB37B401 for ; Sat, 20 Oct 2001 10:34:14 -0700 (PDT) Received: from cv.org ([63.201.33.164]) by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0GLI00GLAM4NZM@mta4.snfc21.pbi.net> for freebsd-net@freebsd.org; Sat, 20 Oct 2001 10:33:59 -0700 (PDT) Date: Sat, 20 Oct 2001 10:35:51 -0700 From: Jason Kocol Subject: ppp, tun0, and 2 IP addresses To: freebsd-net@freebsd.org Message-id: <3BD1B5F7.DA998771@cv.org> MIME-version: 1.0 X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.12 i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I am running FreeBSD 4.4-STABLE, using ppp with a DSL router. I run ppp in ddial mode, using tun0 as the device. My DSL service provides me with a dynamic IP address. Whenever I get disconnected somehow (most likely by the ISP or switch I am connected to), and ppp reconnects, tun0 ends up binding to 2 different IP addresses - the one it was using prior to disconnecting and the new one. Has anyone ever experienced this problem and has a way to solve it? It happens to me regularly. Please let me know if you need any more information. Thanks in advance, -Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 20 10:45: 8 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id A223337B401 for ; Sat, 20 Oct 2001 10:45:02 -0700 (PDT) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id KAA82910; Sat, 20 Oct 2001 10:42:50 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.3/8.11.3) id f9KHgnU84534; Sat, 20 Oct 2001 10:42:49 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200110201742.f9KHgnU84534@arch20m.dellroad.org> Subject: Re: cvs commit: ports/net/mpd-netgraph Makefile distinfo pkg-plist In-Reply-To: <20011018210757.B802@lizzy.bugworks.com> "from Jos Backus at Oct 18, 2001 09:07:57 pm" To: Jos Backus Date: Sat, 20 Oct 2001 10:42:49 -0700 (PDT) Cc: 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Jos Backus writes: > With the latest mpd-3.3 (which has MS-CHAPv2 support, yay!) I am seeing the > following error(?): > > Oct 18 20:15:20 lizzy mpd: [work] PPTP call successful > Oct 18 20:15:20 lizzy mpd: [work] can't connect ksocket node: Operation now in progress Weird.. What version of FreeBSD is this? Does mpd-3.2 work OK on this same system? If mpd-3.2 does NOT work, then there may be some change in the way the socket code works that is causing this. FYI, this error is happening when mpd attempts to do a connect(2) on a (PF_INET, SOCK_RAW, IPPROTO_GRE) socket (which should normally always succeed immediately). -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 Oct 20 10:59:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from fepE.post.tele.dk (fepE.post.tele.dk [195.41.46.137]) by hub.freebsd.org (Postfix) with ESMTP id A404B37B401 for ; Sat, 20 Oct 2001 10:59:12 -0700 (PDT) Received: from arnold.neland.dk ([62.243.124.200]) by fepE.post.tele.dk (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP id <20011020175911.ESCQ13021.fepE.post.tele.dk@arnold.neland.dk>; Sat, 20 Oct 2001 19:59:11 +0200 Received: from gina ([192.168.5.109]) by arnold.neland.dk (8.11.6/8.11.6) with SMTP id f9KHxkq80369; Sat, 20 Oct 2001 19:59:46 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <005701c15990$eb5407c0$6d05a8c0@neland.dk> From: "Leif Neland" To: "Jason Kocol" , References: <3BD1B5F7.DA998771@cv.org> Subject: Re: ppp, tun0, and 2 IP addresses Date: Sat, 20 Oct 2001 19:59:09 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ----- Original Message ----- From: "Jason Kocol" To: Sent: Saturday, October 20, 2001 7:35 PM Subject: ppp, tun0, and 2 IP addresses > I am running FreeBSD 4.4-STABLE, using ppp with a DSL router. I run ppp > in ddial mode, using tun0 as the device. My DSL service provides me > with a dynamic IP address. > > Whenever I get disconnected somehow (most likely by the ISP or switch I > am connected to), and ppp reconnects, tun0 ends up binding to 2 > different IP addresses - the one it was using prior to disconnecting and > the new one. > > Has anyone ever experienced this problem and has a way to solve it? It > happens to me regularly. Please let me know if you need any more > information. > It is no problem. It is because processes running during the cutoff and reconnect does not have to bind to another IP. Are you having any trouble with it, other than confusion? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 20 11: 0: 8 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 0B87437B401; Sat, 20 Oct 2001 11:00:03 -0700 (PDT) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id KAA82982; Sat, 20 Oct 2001 10:51:08 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.3/8.11.3) id f9KHp1584570; Sat, 20 Oct 2001 10:51:01 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200110201751.f9KHp1584570@arch20m.dellroad.org> Subject: Re: netgraph one2many question In-Reply-To: "from Milon Papezik at Oct 18, 2001 12:37:56 pm" To: Milon Papezik Date: Sat, 20 Oct 2001 10:51:01 -0700 (PDT) Cc: "'hackers@freebsd.org'" , "'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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Milon Papezik writes: > I would like to extend ng_one2many module to include > automatic link failure datection, failover and FEC functionality. > > My question is: > Are interface nodes able to send upstream notification > that their state has changed or do I have to poll their status periodically > as it is done in ng_fec module made kindly available by wpaul ? They don't now, but I think you could add this in a reasonably unoffensive way. What you would do is add a new function pointer to struct ifnet, say "void (*if_report)(struct ifnet *, int status)" or something. When a device driver detected link going up/down, it could call this function (if non-NULL). Then if_ethersubr() would set this function pointer to point to some function if_ether_report(). When if_ether_report() is called, if ng_ether was loaded, it would call into ng_ether() to generate a control message that would be passed to the node connected to the "lower" hook. Then, ng_one2many could be modified to understand this control message and do the right thing according to its configuration. Or, something like that. Polling might be a quicker and easier though less precise way to do it for starters. -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 Oct 20 11:12:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from mta2.snfc21.pbi.net (mta2.snfc21.pbi.net [206.13.28.123]) by hub.freebsd.org (Postfix) with ESMTP id C747337B401 for ; Sat, 20 Oct 2001 11:12:56 -0700 (PDT) Received: from cv.org ([63.201.33.164]) by mta2.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0GLI003USNM43I@mta2.snfc21.pbi.net> for freebsd-net@freebsd.org; Sat, 20 Oct 2001 11:06:04 -0700 (PDT) Date: Sat, 20 Oct 2001 11:07:56 -0700 From: Jason Kocol Subject: Re: ppp, tun0, and 2 IP addresses To: Leif Neland , freebsd-net@freebsd.org Message-id: <3BD1BD7C.88C97C57@cv.org> MIME-version: 1.0 X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.12 i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en References: <3BD1B5F7.DA998771@cv.org> <005701c15990$eb5407c0$6d05a8c0@neland.dk> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Leif Neland wrote: > > I am running FreeBSD 4.4-STABLE, using ppp with a DSL router. I run > ppp > > in ddial mode, using tun0 as the device. My DSL service provides me > > with a dynamic IP address. > > > > Whenever I get disconnected somehow (most likely by the ISP or > switch I > > am connected to), and ppp reconnects, tun0 ends up binding to 2 > > different IP addresses - the one it was using prior to disconnecting > and > > the new one. > > > > Has anyone ever experienced this problem and has a way to solve it? > It > > happens to me regularly. Please let me know if you need any more > > information. > > > It is no problem. It is because processes running during the cutoff > and reconnect does not have to bind to another IP. > > Are you having any trouble with it, other than confusion? > > Leif Yes, I am having trouble with it because I also have a utility running that will update my IP address at dyndns.org if it changes (so I can have a constant URL to connect to my machine). The utility does not update the IP address when this happens because it still sees the old one bound to tun0 as well. Thus, I am unable to connect to this machine remotely until I reset everything manually. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 20 11:31:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from ns1.via-net-works.net.ar (ns1.via-net-works.net.ar [200.10.100.10]) by hub.freebsd.org (Postfix) with ESMTP id DE0E437B403 for ; Sat, 20 Oct 2001 11:31:43 -0700 (PDT) Received: from gont.gont.com.ar (ppp118-r5300-cap1.via-net-works.net.ar [200.16.146.17]) by ns1.via-net-works.net.ar (8.9.3/8.9.3) with ESMTP id PAA75583 for ; Sat, 20 Oct 2001 15:32:16 -0300 (ART) Message-Id: <4.3.2.7.2.20011020101858.00d984e0@mail.sitanium.com> X-Sender: ingroupcomar-fgont@mail.sitanium.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 20 Oct 2001 10:22:29 -0300 To: freebsd-net@freebsd.org From: Fernando Gont Subject: SYN flood and IP spoofing Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi! I've read some explanations about the SYN flood DoS attack. I understand that when the attacker fills the listening queue of the attacked host with incomplete connections, the attacked host will not reply to any SYN it receives after that. However, I don't understand why it will not even reply with an RST when it receives a SYN-ACK from other machine. For example, take a look at the famous Kevin Mitnick's attack. First, Mitnick SYN- floods "server". 14:18:22.516699 130.92.6.97.600 > server.login: S 1382726960:1382726960(0) win 4096 14:18:22.566069 130.92.6.97.601 > server.login: S 1382726961:1382726961(0) win 4096 [....and lots of other SYNs....] Then he spoofes server's IP address and try to connect to x-terminal. He sends a SYN from server to x-terminal. Then I think x-terminal sends a SYN/ACK back to server, BUT server IGNORES it (if not, this attack wouldn't have succeeded). And then Mitnick predicts the TCP sequence number, and sends an ACK, so that he's able to ESTABLISH the connection. 14:18:36.245045 server.login > x-terminal.shell: S 1382727010:1382727010(0) win 4096 14:18:36.755522 server.login > x-terminal.shell: . ack 2024384001 win 4096 My question is why didn't server send an RST in response to the SYN/ACK x-terminal sent to it? I understand that if a host has its listening queue full, it'll ignore the following SYNs, because it has "no resources" to keep sate information for a new connection. But, why doesn't it reply a SYN/ACK with a RST, if it DOES KNOW that that segment doesn't correspond to any current connection? Kind regards, Fernando Gont e-mail: fernando@gont.com.ar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 20 12: 3:36 2001 Delivered-To: freebsd-net@freebsd.org Received: from w250.z064001178.sjc-ca.dsl.cnc.net (w250.z064001178.sjc-ca.dsl.cnc.net [64.1.178.250]) by hub.freebsd.org (Postfix) with SMTP id E459937B403 for ; Sat, 20 Oct 2001 12:03:33 -0700 (PDT) Received: (qmail 21078 invoked by uid 1000); 20 Oct 2001 19:03:54 -0000 Date: Sat, 20 Oct 2001 12:03:32 -0700 From: Jos Backus To: Archie Cobbs Cc: net@FreeBSD.ORG Subject: Re: cvs commit: ports/net/mpd-netgraph Makefile distinfo pkg-plist Message-ID: <20011020120332.A3944@lizzy.bugworks.com> Reply-To: Jos Backus Mail-Followup-To: Archie Cobbs , net@FreeBSD.ORG References: <20011018210757.B802@lizzy.bugworks.com> <200110201742.f9KHgnU84534@arch20m.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110201742.f9KHgnU84534@arch20m.dellroad.org> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, Oct 20, 2001 at 10:42:49AM -0700, Archie Cobbs wrote: > Weird.. What version of FreeBSD is this? FreeBSD lizzy.bugworks.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Thu Oct 18 18:23:13 PDT 2001 jos@lizzy.bugworks.com:/usr/obj/usr/src/sys/LIZZY i386 > Does mpd-3.2 work OK on this same system? Nope, same error. Btw, while I was fiddling with this I also got my first panic since resuming tracking -current. Meanwhile I have turned crashdumps on so maybe next time I'll be able to provide some useful info. > If mpd-3.2 does NOT work, then there may be some change in the > way the socket code works that is causing this. > > FYI, this error is happening when mpd attempts to do a connect(2) > on a (PF_INET, SOCK_RAW, IPPROTO_GRE) socket (which should normally > always succeed immediately). Thanks. This smells like a -current problem. -- Jos Backus _/ _/_/_/ Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ josb@cncdsl.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 20 12:17:19 2001 Delivered-To: freebsd-net@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 6C58637B405 for ; Sat, 20 Oct 2001 12:17:15 -0700 (PDT) Received: (qmail 63978 invoked by uid 1000); 20 Oct 2001 19:17:12 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Oct 2001 19:17:12 -0000 Date: Sat, 20 Oct 2001 14:17:12 -0500 (CDT) From: Mike Silbersack To: Fernando Gont Cc: Subject: Re: SYN flood and IP spoofing In-Reply-To: <4.3.2.7.2.20011020101858.00d984e0@mail.sitanium.com> Message-ID: <20011020140704.R63640-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 20 Oct 2001, Fernando Gont wrote: > Hi! > > I've read some explanations about the SYN flood DoS attack. > I understand that when the attacker fills the listening queue of the > attacked host with incomplete connections, the attacked host will not > reply to any SYN it receives after that. That's an old explanation; basically any OS released in the last few years will throw old/random connections out of the queue when it fills up. What you actually describe here is more "spoofing" than a syn flood; a syn flood just involves blasting large numbers of syn packets at someone, with no intent of actually spoofing a connection. When Mitnick / anyone else did spoofing, it was through weaknesses in the algorithm used to generate initial sequence numbers, not through simple brute force. (I'm assuming that's how Mitnick did it; I'm not aware that he has revealed exactly how he did anything, and I doubt I'd trust him even if he did explain.) > However, I don't understand why it will not even reply with an RST > when it receives a SYN-ACK from other machine. In the general case of spoofing, you could ensure that a syn-ack does not elicit a rst by spoofing the IP of a nonexistant host. I've also read that older tcp stacks could be caused to stop emitting packets by filling their SYN queue; I'm not sure when that stopped applying. These days, spoofing really isn't a concern; those looking to find a way into a system wouldn't gain anything by spoofing and would instead look for a buffer overflow to exploit. Syn floods are alive and well, though. 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 Sat Oct 20 12:18:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id A4F2D37B405; Sat, 20 Oct 2001 12:18:25 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA80757; Sat, 20 Oct 2001 13:23:18 -0700 (PDT) Date: Sat, 20 Oct 2001 13:23:16 -0700 (PDT) From: Julian Elischer To: Archie Cobbs Cc: Milon Papezik , "'hackers@freebsd.org'" , "'net@freebsd.org'" Subject: Re: netgraph one2many question In-Reply-To: <200110201751.f9KHp1584570@arch20m.dellroad.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bill Paul has written a specific NETGRAPH FEC module... he has failover as well.. (it is only PART a netgraph module as it doesn;t use the netgraph hooks to talk to teh ethernet driver.. (strange)) I suggest you look for it in the archives or on http://www.freebsd.org/~wpaul/ On Sat, 20 Oct 2001, Archie Cobbs wrote: > Milon Papezik writes: > > I would like to extend ng_one2many module to include > > automatic link failure datection, failover and FEC functionality. > > > > My question is: > > Are interface nodes able to send upstream notification > > that their state has changed or do I have to poll their status periodically > > as it is done in ng_fec module made kindly available by wpaul ? > > They don't now, but I think you could add this in a reasonably > unoffensive way. > > What you would do is add a new function pointer to struct ifnet, > say "void (*if_report)(struct ifnet *, int status)" or something. > > When a device driver detected link going up/down, it could call > this function (if non-NULL). Then if_ethersubr() would set this > function pointer to point to some function if_ether_report(). > When if_ether_report() is called, if ng_ether was loaded, it > would call into ng_ether() to generate a control message that > would be passed to the node connected to the "lower" hook. > > Then, ng_one2many could be modified to understand this control > message and do the right thing according to its configuration. > > Or, something like that. Polling might be a quicker and easier > though less precise way to do it for starters. > > -Archie > > __________________________________________________________________________ > Archie Cobbs * Packet Design * http://www.packetdesign.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 20 13:55:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from hotmail.com (f89.pav2.hotmail.com [64.4.37.89]) by hub.freebsd.org (Postfix) with ESMTP id E128737B40A for ; Sat, 20 Oct 2001 13:55:45 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 20 Oct 2001 13:55:45 -0700 Received: from 204.178.20.14 by pv2fd.pav2.hotmail.msn.com with HTTP; Sat, 20 Oct 2001 20:55:45 GMT X-Originating-IP: [204.178.20.14] From: "murthy kn" To: net@freebsd.org Subject: Re: netgraph one2many question Date: Sun, 21 Oct 2001 02:25:45 +0530 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 20 Oct 2001 20:55:45.0844 (UTC) FILETIME=[96DC2740:01C159A9] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I am a newbie to netgraph and have started looking at the sources and manpages. 1.In the context of one2many, in the manpage example, I see that it puts the interfaces into promiscuous mode. My question is, instead of turning on the promiscuous mode, will it not work if we use the "ifconfig lladdr" to temporarily change the MAC address (hardware receive filter) of the cards to that of the master card (fxp0 in the manpage example). 2. Are the messages like "arp: something was on fxp0 got the reply from fxp1...." kind of messages harmful - can I turn it off if in any way. I get lot of such messages when I enable multiple cards connected on the same segment on a FreeBSD machine. 3. Is it possible to have multiple cards with the same IP address on a FreeBSD machine. Thanks for your time. Bye, murthy >From: Julian Elischer >To: Archie Cobbs >CC: Milon Papezik , "'hackers@freebsd.org'" >, "'net@freebsd.org'" >Subject: Re: netgraph one2many question >Date: Sat, 20 Oct 2001 13:23:16 -0700 (PDT) > >Bill Paul has written a specific NETGRAPH FEC module... > >he has failover as well.. > >(it is only PART a netgraph module as it doesn;t use the netgraph hooks to >talk to teh ethernet driver.. (strange)) > >I suggest you look for it in the archives or on >http://www.freebsd.org/~wpaul/ > >On Sat, 20 Oct 2001, Archie Cobbs wrote: > > > Milon Papezik writes: > > > I would like to extend ng_one2many module to include > > > automatic link failure datection, failover and FEC functionality. > > > > > > My question is: > > > Are interface nodes able to send upstream notification > > > that their state has changed or do I have to poll their status >periodically > > > as it is done in ng_fec module made kindly available by wpaul ? > > > > They don't now, but I think you could add this in a reasonably > > unoffensive way. > > > > What you would do is add a new function pointer to struct ifnet, > > say "void (*if_report)(struct ifnet *, int status)" or something. > > > > When a device driver detected link going up/down, it could call > > this function (if non-NULL). Then if_ethersubr() would set this > > function pointer to point to some function if_ether_report(). > > When if_ether_report() is called, if ng_ether was loaded, it > > would call into ng_ether() to generate a control message that > > would be passed to the node connected to the "lower" hook. > > > > Then, ng_one2many could be modified to understand this control > > message and do the right thing according to its configuration. > > > > Or, something like that. Polling might be a quicker and easier > > though less precise way to do it for starters. > > > > -Archie > > > > >__________________________________________________________________________ > > Archie Cobbs * Packet Design * >http://www.packetdesign.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-net" in the body of the message _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 20 14:25:25 2001 Delivered-To: freebsd-net@freebsd.org Received: from fepZ.post.tele.dk (fepz.post.tele.dk [195.41.46.133]) by hub.freebsd.org (Postfix) with ESMTP id DC5BB37B401 for ; Sat, 20 Oct 2001 14:25:20 -0700 (PDT) Received: from arnold.neland.dk ([62.243.124.200]) by fepZ.post.tele.dk (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP id <20011020212519.QVY2863.fepZ.post.tele.dk@arnold.neland.dk>; Sat, 20 Oct 2001 23:25:19 +0200 Received: from gina ([192.168.5.109]) by arnold.neland.dk (8.11.6/8.11.6) with SMTP id f9KLPnq16486; Sat, 20 Oct 2001 23:25:50 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <007501c159ad$b56fc5a0$6d05a8c0@neland.dk> From: "Leif Neland" To: "Jason Kocol" , References: <3BD1B5F7.DA998771@cv.org> <005701c15990$eb5407c0$6d05a8c0@neland.dk> <3BD1BD7C.88C97C57@cv.org> Subject: Re: ppp, tun0, and 2 IP addresses Date: Sat, 20 Oct 2001 23:25:14 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ----- Original Message ----- From: "Jason Kocol" To: "Leif Neland" ; Sent: Saturday, October 20, 2001 8:07 PM Subject: Re: ppp, tun0, and 2 IP addresses > Leif Neland wrote: > > > > I am running FreeBSD 4.4-STABLE, using ppp with a DSL router. I run > > ppp > > > in ddial mode, using tun0 as the device. My DSL service provides me > > > with a dynamic IP address. > > > > > > Whenever I get disconnected somehow (most likely by the ISP or > > switch I > > > am connected to), and ppp reconnects, tun0 ends up binding to 2 > > > different IP addresses - the one it was using prior to disconnecting > > and > > > the new one. > > > > > > Has anyone ever experienced this problem and has a way to solve it? > > It > > > happens to me regularly. Please let me know if you need any more > > > information. > > > > > It is no problem. It is because processes running during the cutoff > > and reconnect does not have to bind to another IP. > > > > Are you having any trouble with it, other than confusion? > > > > Leif > > Yes, I am having trouble with it because I also have a utility running > that will update my IP address at dyndns.org if it changes (so I can > have a constant URL to connect to my machine). The utility does not > update the IP address when this happens because it still sees the old > one bound to tun0 as well. Thus, I am unable to connect to this machine > remotely until I reset everything manually. > Quoted from man ppp: iface-alias Default: Enabled if -nat is specified. This option simply tells ppp to add new interface addresses to the interface rather than replacing them. The option can only be enabled if network address translation is enabled (``nat enable yes''). With this option enabled, ppp will pass traffic for old interface addresses through the NAT engine (see libalias(3)), resulting in the ability (in -auto mode) to properly connect the process that caused the PPP link to come up in the first place. Disabling NAT with ``nat enable no'' will also disable `iface-alias'. But anyway, is the trouble that your utility must know your "true" ip to tell dyndns, or just that it needs to know that the address has changed? If it is the latter, then run the utility in ppp.linkup and kill it in ppp.linkdown. I think you will get in trouble if you disable the behaviour of keeping the old addresses. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 20 18:48: 3 2001 Delivered-To: freebsd-net@freebsd.org Received: from cx175057-a.ocnsd1.sdca.home.com (cx175057-a.ocnsd1.sdca.home.com [24.4.86.45]) by hub.freebsd.org (Postfix) with ESMTP id 6765C37B401 for ; Sat, 20 Oct 2001 18:47:56 -0700 (PDT) Received: from localhost (bri@localhost) by cx175057-a.ocnsd1.sdca.home.com (8.11.6/8.11.3) with ESMTP id f9L1lsG28761 for ; Sat, 20 Oct 2001 18:47:55 -0700 (PDT) (envelope-from bri@sonicboom.org) Date: Sat, 20 Oct 2001 18:47:54 -0700 (PDT) From: Brian Whalen X-X-Sender: To: Subject: 3com 3cr990-tx 97 Message-ID: <20011020183813.D28542-100000@cx175057-a.ocnsd1.sdca.home.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I saw this card does ipsec on the nic, offloading it from the cpu. Any chance of bsd supporting this? I didn't see it on the hardware.txt file for 4.4. Brian "Sonic" Whalen Success = Preparation + Opportunity To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 20 20: 6:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from cobalt.hytekblue.com (adsl-208-191-100-26.dsl.stlsmo.swbell.net [208.191.100.26]) by hub.freebsd.org (Postfix) with ESMTP id B1BD237B401 for ; Sat, 20 Oct 2001 20:06:28 -0700 (PDT) Received: from hytekblue1 ([10.0.0.177]) by cobalt.hytekblue.com (8.9.3/8.9.3) with SMTP id WAA33006; Sat, 20 Oct 2001 22:05:52 -0500 (CDT) (envelope-from mgt@hytekblue.com) Message-ID: <200110202206550921.00165911@cobalt.hytekblue.com> In-Reply-To: <200110192250.f9JMoQ0H037736@atg.aciworldwide.com> References: <200110192250.f9JMoQ0H037736@atg.aciworldwide.com> X-Mailer: Calypso Version 2.40.35 Date: Sat, 20 Oct 2001 22:06:55 -0500 From: "Matthew" To: lyndon@atg.aciworldwide.com, freebsd-net@FreeBSD.ORG Subject: Re: D-Link DGE-500T support Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org well obvoiusly this is not the same but i was able to get the lge driver to= work with the dlink DGE-500SX. i get about 212mb a second through put on a= 32bit pci slot and closer to 600mb/s on a 64bit slot however the card= does not seam to be very stable on my motherboard in a 64bit slot. best= of luck with the dge-500t Matthew if its not broke i will fix it till it is :) *********** REPLY SEPARATOR *********** On 10/19/2001, at 5:50 PM, Lyndon Nerenberg wrote: >Have any of you managed to get the DFE-500T running with the >lge driver? lge(4) hints that this should work, but I don't see >anything in the list archives to indicate that someone has >actually used this NIC successfully. (Note: I'm talking about >the NIC that talks over copper, not fibre.) > > >--lyndon > >Lizzie Borden took an axe, >And plunged it deep into the VAX; >Don't you envy people who >Do all the things YOU want to do? > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 20 21:20:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from soso.eecs.umich.edu (soso.eecs.umich.edu [141.213.4.24]) by hub.freebsd.org (Postfix) with ESMTP id 128F237B406 for ; Sat, 20 Oct 2001 21:20:11 -0700 (PDT) Received: from localhost (binkertn@localhost) by soso.eecs.umich.edu (8.11.4/8.10.0) with ESMTP id f9L4Jep24874; Sun, 21 Oct 2001 00:19:42 -0400 (EDT) X-Authentication-Warning: soso.eecs.umich.edu: binkertn owned process doing -bs Date: Sun, 21 Oct 2001 00:19:38 -0400 (EDT) From: Nathan Binkert X-X-Sender: To: Matthew Cc: , Subject: Re: D-Link DGE-500T support In-Reply-To: <200110202206550921.00165911@cobalt.hytekblue.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The DGE-500T uses a different chip than the DGE-500SX. The 500T uses the nge driver, and the 500SX uses the lge driver. Nathan > well obvoiusly this is not the same but i was able to get the lge > driver to work with the dlink DGE-500SX. i get about 212mb a second > through put on a 32bit pci slot and closer to 600mb/s on a 64bit slot > however the card does not seam to be very stable on my motherboard in > a 64bit slot. best of luck with the dge-500t > Matthew > if its not broke i will fix it till it is :) > > > *********** REPLY SEPARATOR *********** > > On 10/19/2001, at 5:50 PM, Lyndon Nerenberg wrote: > > >Have any of you managed to get the DFE-500T running with the > >lge driver? lge(4) hints that this should work, but I don't see > >anything in the list archives to indicate that someone has > >actually used this NIC successfully. (Note: I'm talking about > >the NIC that talks over copper, not fibre.) > > > > > >--lyndon > > > >Lizzie Borden took an axe, > >And plunged it deep into the VAX; > >Don't you envy people who > >Do all the things YOU want to do? > > > >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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message