From owner-freebsd-net Sun Oct 3 3:47:17 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 0D4921554D for ; Sun, 3 Oct 1999 03:45:51 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 92428 invoked from network); 3 Oct 1999 10:45:42 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.182]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 3 Oct 1999 10:45:42 -0000 Message-ID: <37F73424.3578DBB@pipeline.ch> Date: Sun, 03 Oct 1999 12:47:00 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: net@FreeBSD.ORG, louie@uu.net Subject: Re: PPPoE testers please. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian Elischer wrote: > > More questions.. > > Should a FreeBSd box running PPPoE be able to run multiple PPPoE sessions? > (i.e. each with a different Session_ID) Yes. FreeBSD schould be running on the PPPoE gateway/server too! ;-) > Can there be multiple sessions to the same AC requesting the same > Service, from the same host? I don't know. > What about differnt services? > (what ARE the possible services?) One PPPoE to the ISP/Online Service and one to your Corp. LAN... etc. > Might multiple ISPs offer ppp session services on the same cable, > competing with each other? Yes. PPPoE is not only used for Cable but also for xDSL in some places. For example Deutsche Telekom does PPPoE over ADSL (which works as an bridge and uses then ATM) for their T-Offline online service. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 3 7: 0:56 1999 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-5.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.5]) by hub.freebsd.org (Postfix) with ESMTP id 196EF14E58 for ; Sun, 3 Oct 1999 07:00:52 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id PAA00960; Sun, 3 Oct 1999 15:00:49 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA63729; Sun, 3 Oct 1999 13:28:05 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910031228.NAA63729@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Louis A. Mamakos" Cc: spork , freebsd-net@FreeBSD.ORG Subject: Re: PPPoE In-reply-to: Your message of "Fri, 01 Oct 1999 19:10:40 EDT." <199910012310.TAA09717@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Oct 1999 13:28:02 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [.....] > We did a proof-of-concept implemention starting with the user-mode PPP > daemon and using BPF to put frames on and off the wire, with no kernel > changes. This happened to be done on a BSDI system, but that's really > not at all significant. [.....] Were any modifications needed to get it to build on BSDi ? I'd be happy to roll them back into the sources. As it happens, I've got PPPoE on my todo list. I've had various hardware problems lately, so things have been a bit slow :-( > louie > (aka louie@UU.NET) -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 3 13: 1:46 1999 Delivered-To: freebsd-net@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 48EAC14BB8 for ; Sun, 3 Oct 1999 13:01:43 -0700 (PDT) (envelope-from spork@super-g.com) Received: by super-g.com (Postfix, from userid 1000) id B7A14B917; Sun, 3 Oct 1999 16:01:42 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id 954C8B916; Sun, 3 Oct 1999 16:01:42 -0400 (EDT) Date: Sun, 3 Oct 1999 16:01:42 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Julian Elischer Cc: "Louis A. Mamakos" , freebsd-net@FreeBSD.ORG Subject: Re: PPPoE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is from a company that sells win/mac/linux PPPoE implementations to ISP's (I came here after browsing the linux source on Sympatico's website). Seems like a decent list of links: http://www.nts.com/library/tlpppoe.html There's a bit of info from sympatico at: http://www.hse.sympatico.ca/en/community/download.htm Charles On Fri, 1 Oct 1999, Julian Elischer wrote: > > > On Fri, 1 Oct 1999, Louis A. Mamakos wrote: > > > > It seems more and more ADSL providers in the US are moving from bridged > > > IP over ethernet to PPP over Ethernet as they dump whatever clunky > > > solutions they started with and move to the RedBack "subscriber management > > > system". The idea it seems is to simulate the familiar dialup connection. > > > This lets you hand out dynamic addresses, dump idle users, discourage > > > servers, track usage, hamper NAT, and (the relevant part) discourage > > > people from connecting with anything but "supported" OS's. > > > > Uh, as one of the folks responsible for driving PPPoE development, I can > > assure that the last part of your remark wasn't one of the goals we had. > > It was, in fact, time-to-market given the existing bridged-ethernet > > capable hardware out there. It was also to support simultanous connections > > to different service providers, and with different levels of service. Think > > low-end, consumer user vs. work-at-home teleworkers. Why shouldn't they > > be able to use the same ADSL pipe to support concurrent access to both > > e.g., AOL for the kids (that you're paying for yourself) AND > > higher-performance > > access that your employer is paying for. > > > > > Is there anyone actively working on PPPoE for FreeBSD? I don't like the > > > whole concept of wrapping so many frames inside each other, but it would > > > be a shame if a bunch of folks with FBSD gateways for their home nets had > > > to move to Win98 and its' ICS (Internet Connection Sharing). Blech. > > > > > > Could user/kernel ppp be modified? How does this work anyhow? Is there > > > an ethernet frame type for PPPoE? How close do you have to get to the > > > ethernet driver to send PPPoE frames? Can any existing PPP implementations > > > easily handle a few megabits/sec on older hardware? > > > > We did a proof-of-concept implemention starting with the user-mode PPP > > daemon and using BPF to put frames on and off the wire, with no kernel > > changes. This happened to be done on a BSDI system, but that's really > > not at all significant. > > > > I observed once before that the Whistle netgraph stuff is an ideal > > sort of solution for this type of problem where you're really concerned > > about performance, and don't want to context switch into a user process > > for each packet. > > I hope to start work on a netgraph/PPPoE module in the next day or so.. > do you have any suggested reading? > > > > > louie > > (aka louie@UU.NET) > > > > > > > > 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 From owner-freebsd-net Sun Oct 3 13: 8:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 1689814D5E for ; Sun, 3 Oct 1999 13:08:14 -0700 (PDT) (envelope-from spork@super-g.com) Received: by super-g.com (Postfix, from userid 1000) id 53188B916; Sun, 3 Oct 1999 16:08:14 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id 3EF18B914; Sun, 3 Oct 1999 16:08:14 -0400 (EDT) Date: Sun, 3 Oct 1999 16:08:14 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Julian Elischer Cc: net@freebsd.org, louie@uu.net Subject: Re: PPPoE testers please. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is anyone aware of a PPPoE server? Software, that is, not a RedBack box... Also, here's a link to patches for linux kernel-ppp that may be interesting to someone... Charles On Sat, 2 Oct 1999, Julian Elischer wrote: > > I have PPPoE code mapped out but I will need someone to test with at some > stage. Is there anyone that has such a setup that can be used for testing? > > Also, Is ther anyone out there that knows what the normal kinds of > "service name" might look like? > for that matter, What is a likely example of an AC-Name? > > I ask this because if I knew that these values were less than 15 or 31 > bytes in length I might take a different approach to that I would need if > they can be 256 bytes on length. (I'm presently assuming the latter). > > julian > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 3 14:25:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id D706014C28 for ; Sun, 3 Oct 1999 14:25:53 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id OAA22366; Sun, 3 Oct 1999 14:25:50 -0700 (PDT) Date: Sun, 3 Oct 1999 14:25:50 -0700 (PDT) From: Julian Elischer To: spork Cc: net@freebsd.org, louie@uu.net Subject: Re: PPPoE testers please. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org er, you left off the link :-) On Sun, 3 Oct 1999, spork wrote: > Is anyone aware of a PPPoE server? Software, that is, not a RedBack > box... > > Also, here's a link to patches for linux kernel-ppp that may be > interesting to someone... > > Charles > > On Sat, 2 Oct 1999, Julian Elischer wrote: > > > > > I have PPPoE code mapped out but I will need someone to test with at some > > stage. Is there anyone that has such a setup that can be used for testing? > > > > Also, Is ther anyone out there that knows what the normal kinds of > > "service name" might look like? > > for that matter, What is a likely example of an AC-Name? > > > > I ask this because if I knew that these values were less than 15 or 31 > > bytes in length I might take a different approach to that I would need if > > they can be 256 bytes on length. (I'm presently assuming the latter). > > > > julian > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 3 15:14:24 1999 Delivered-To: freebsd-net@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 7AC3F14C15 for ; Sun, 3 Oct 1999 15:14:22 -0700 (PDT) (envelope-from spork@super-g.com) Received: by super-g.com (Postfix, from userid 1000) id 66852B916; Sun, 3 Oct 1999 18:14:21 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id 525CDB914; Sun, 3 Oct 1999 18:14:21 -0400 (EDT) Date: Sun, 3 Oct 1999 18:14:21 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Julian Elischer Cc: net@freebsd.org, louie@uu.net Subject: Re: PPPoE testers please. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ooops... Here you go: http://math.uwaterloo.ca/~mostrows Charles On Sun, 3 Oct 1999, Julian Elischer wrote: > er, you left off the link :-) > > > On Sun, 3 Oct 1999, spork wrote: > > > Is anyone aware of a PPPoE server? Software, that is, not a RedBack > > box... > > > > Also, here's a link to patches for linux kernel-ppp that may be > > interesting to someone... > > > > Charles > > > > On Sat, 2 Oct 1999, Julian Elischer wrote: > > > > > > > > I have PPPoE code mapped out but I will need someone to test with at some > > > stage. Is there anyone that has such a setup that can be used for testing? > > > > > > Also, Is ther anyone out there that knows what the normal kinds of > > > "service name" might look like? > > > for that matter, What is a likely example of an AC-Name? > > > > > > I ask this because if I knew that these values were less than 15 or 31 > > > bytes in length I might take a different approach to that I would need if > > > they can be 256 bytes on length. (I'm presently assuming the latter). > > > > > > julian > > > > > > > > > > > > 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 From owner-freebsd-net Sun Oct 3 17: 2:47 1999 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-51.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.51]) by hub.freebsd.org (Postfix) with ESMTP id 4A3D6151CA for ; Sun, 3 Oct 1999 17:02:35 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA00488; Mon, 4 Oct 1999 01:02:13 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA28249; Sun, 3 Oct 1999 23:46:45 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910032246.XAA28249@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer Cc: net@FreeBSD.org, louie@uu.net Subject: Re: PPPoE testers please. In-reply-to: Your message of "Sat, 02 Oct 1999 21:40:59 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Oct 1999 23:46:44 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > More questions.. > > Should a FreeBSd box running PPPoE be able to run multiple PPPoE sessions? > (i.e. each with a different Session_ID) I would think so. > Can there be multiple sessions to the same AC requesting the same > Service, from the same host? I would think so here too. > What about differnt services? > (what ARE the possible services?) > Might multiple ISPs offer ppp session services on the same cable, > competing with each other? And again. Disclaimer: I know nothing for sure ! :-] > Julian -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 4 8:57:20 1999 Delivered-To: freebsd-net@freebsd.org Received: from homer.web-ex.com (homer.web-ex.com [209.54.66.254]) by hub.freebsd.org (Postfix) with ESMTP id BD29A14F06 for ; Mon, 4 Oct 1999 08:57:12 -0700 (PDT) (envelope-from jim@web-ex.com) Received: from localhost (jim@localhost) by homer.web-ex.com (8.9.3/8.9.3) with ESMTP id LAA30241 for ; Mon, 4 Oct 1999 11:57:15 -0400 (EDT) (envelope-from jim@web-ex.com) X-Authentication-Warning: homer.web-ex.com: jim owned process doing -bs Date: Mon, 4 Oct 1999 11:57:15 -0400 (EDT) From: Jim Cassata To: FreeBSD Net Subject: Re: PPPoE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I'd like to, but it doesn't have a 'killer app' so it's been suggested by > someone that they'd rather we didn't. > > If other people found uses for it, that would make it easier, but as there > is not a single other peroson that has found a use for it other than us, > I really don't have clearance to add it. (clearance from freebsd people > that is, Whistle couldn't care....) > I apologize for not being up on this thread, but we may have a "killer app" could someone please explain exactly what Netgraph is? Jim Cassata 516.421.6000 jim@web-ex.com Web Express 20 Broadhollow Road Suite 3011 Melville, NY 11747 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 4 15:12:59 1999 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 5AA561529E for ; Mon, 4 Oct 1999 15:12:58 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id PAA60631; Mon, 4 Oct 1999 15:12:19 -0700 (PDT) From: Archie Cobbs Message-Id: <199910042212.PAA60631@bubba.whistle.com> Subject: Re: PPPoE In-Reply-To: from Jim Cassata at "Oct 4, 1999 11:57:15 am" To: jim@web-ex.com (Jim Cassata) Date: Mon, 4 Oct 1999 15:12:19 -0700 (PDT) Cc: freebsd-net@FreeBSD.ORG (FreeBSD Net) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jim Cassata writes: > > I'd like to, but it doesn't have a 'killer app' so it's been suggested by > > someone that they'd rather we didn't. > > > > If other people found uses for it, that would make it easier, but as there > > is not a single other peroson that has found a use for it other than us, > > I really don't have clearance to add it. (clearance from freebsd people > > that is, Whistle couldn't care....) > > I apologize for not being up on this thread, but we may have a "killer > app" could someone please explain exactly what Netgraph is? See ftp://ftp.whistle.com/pub/archie/netgraph/index.html for a description. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 4 15:24:23 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 330891529E for ; Mon, 4 Oct 1999 15:24:22 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id PAA58534 for ; Mon, 4 Oct 1999 15:24:21 -0700 (PDT) Date: Mon, 4 Oct 1999 15:24:20 -0700 (PDT) From: Julian Elischer To: net@freebsd.org Subject: PPPoE question (repeat) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does ANYONE have any ideas of the expected formats of the AC-Name and Service-Name fields? I'm trying to figure out if it's possible to 'bind' a listenning socket ahead of time (not really, but the analagy works) to a service, so that it gets all teh PADI requests to that service, or whether I'd have to bind using a regexp pattern (e.g. ".+@whistle.com"). Obviously that would require some sort of pattern matching code in the kernel. (We already have similar in the CAM code for QUIRK matching). I don't know however how extensive this needs to be. I can imagine that "*@my-isp.net" might be sufficient. The alternative is to pass ALL PADI service requests to a userland agent that interprets the packets and decides whether or not to offer a service to the requesting client machine. I'd rather have the option of some pre-processing in the kernel so that the the server daemons can be simpler in the case where a server is only selecting simple services to respond to. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 4 21:54:49 1999 Delivered-To: freebsd-net@freebsd.org Received: from ns1.portal2.com (ns1.portal2.com [203.85.226.193]) by hub.freebsd.org (Postfix) with SMTP id 3BBA5152A3 for ; Mon, 4 Oct 1999 21:53:54 -0700 (PDT) (envelope-from yusufg@yusufg.portal2.com) Received: (qmail 36587 invoked from network); 5 Oct 1999 04:52:42 -0000 Received: from yusufg.portal2.com (qmailr@203.85.226.249) by ns1.portal2.com with SMTP; 5 Oct 1999 04:52:42 -0000 Received: (qmail 11295 invoked by uid 500); 5 Oct 1999 04:53:50 -0000 Date: 5 Oct 1999 04:53:50 -0000 Message-ID: <19991005045350.11294.qmail@yusufg.portal2.com> From: Yusuf Goolamabbas To: freebsd-questions@freebsd.org, freebsd-net@freebsd.org Subject: Trying to achieve zen with natd Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a FreeBSD 3.3-stable box with 2 NIC cards each bound to static IP's and different ISP WAN interfaces (fxp0 and fxp1) fxp0 is connected to a /25 network fxp1 is connected to a /26 network Default router is fxp1 I would like to configure this box to act as a NATD box. Set the right kernel config and recompile the kernel /etc/rc.conf gateway_enable="YES" firewall_enable="YES" firewall_type="open" natd_enable = "YES" natd_interface = "fxp1" #Assuming this will take the public interface natd_flags = "-u" I did the following in /etc/rc.local ifconfig fxp1 alias 192.168.0.1 netmask 255.255.255.0 Setup a Windows box with IP 192.168.0.2 and gateway 192.168.0.1 I can ping the gateway box, however I can't seem to get out to either the /25 network or the /26 network What am I missing ?? Thanks, Yusuf -- Yusuf Goolamabbas yusufg@outblaze.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 5 2:13:57 1999 Delivered-To: freebsd-net@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 206AC14FE2 for ; Tue, 5 Oct 1999 02:13:15 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.198.208]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA57D; Tue, 5 Oct 1999 11:12:01 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id KAA98234; Tue, 5 Oct 1999 10:18:46 +0200 (CEST) (envelope-from asmodai) Date: Tue, 5 Oct 1999 10:18:46 +0200 From: Jeroen Ruigrok/Asmodai To: dodi maryanto Cc: freebsd-net@freebsd.org Subject: Re: sniffit Message-ID: <19991005101846.F98066@daemon.ninth-circle.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On [19990924 10:47], dodi maryanto (dodi@pau-router.itb.ac.id) wrote: >I use 2.2.8 Release and try to use sniffit. >When I do force sniffit to use ed0, it always give me a core dump. >But when I force to use xl0 in same PC , output is okay. >Buggy on ed0 ? And probably solved in 3.x or CURRENT. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Things do not change, we change. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 5 6:16: 5 1999 Delivered-To: freebsd-net@freebsd.org Received: from spike.snickers.org (snickers.org [216.126.90.2]) by hub.freebsd.org (Postfix) with ESMTP id C69B514CFD for ; Tue, 5 Oct 1999 06:15:19 -0700 (PDT) (envelope-from josh@spike.snickers.org) Received: (from josh@localhost) by spike.snickers.org (8.9.3/8.9.3) id JAA93510; Tue, 5 Oct 1999 09:25:59 -0400 (EDT) Date: Tue, 5 Oct 1999 09:25:58 -0400 From: Josh Tiefenbach To: Julian Elischer Cc: net@FreeBSD.ORG Subject: Re: PPPoE question (repeat) Message-ID: <19991005092558.A93411@snickers.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Organization: Hah Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Oct 04, 1999 at 03:24:20PM -0700, Julian Elischer wrote: > > Does ANYONE have any ideas of the expected formats of the AC-Name and > Service-Name fields? This is obviously not universal, but my ISP uses something like: 123455678554-sms2-toronto for the AC-Name. I havent actually seen them reply to a PADI with a non-null Service-Name tag yet tho. josh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 5 9:57:21 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 57745151FE for ; Tue, 5 Oct 1999 09:56:47 -0700 (PDT) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA82980; Tue, 5 Oct 1999 09:56:13 -0700 (PDT) Date: Tue, 5 Oct 1999 09:56:08 -0700 (PDT) From: Julian Elischer X-Sender: julian@home.elischer.org To: Josh Tiefenbach Cc: net@FreeBSD.ORG Subject: Re: PPPoE question (repeat) In-Reply-To: <19991005092558.A93411@snickers.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org what are you using for pppoe? On Tue, 5 Oct 1999, Josh Tiefenbach wrote: > On Mon, Oct 04, 1999 at 03:24:20PM -0700, Julian Elischer wrote: > > > > Does ANYONE have any ideas of the expected formats of the AC-Name and > > Service-Name fields? > > This is obviously not universal, but my ISP uses something like: > > 123455678554-sms2-toronto > > for the AC-Name. I havent actually seen them reply to a PADI with a > non-null Service-Name tag yet tho. > > josh > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 5 10:26:21 1999 Delivered-To: freebsd-net@freebsd.org Received: from spike.snickers.org (snickers.org [216.126.90.2]) by hub.freebsd.org (Postfix) with ESMTP id F136A155EF for ; Tue, 5 Oct 1999 10:26:09 -0700 (PDT) (envelope-from josh@spike.snickers.org) Received: (from josh@localhost) by spike.snickers.org (8.9.3/8.9.3) id NAA99581; Tue, 5 Oct 1999 13:36:41 -0400 (EDT) Date: Tue, 5 Oct 1999 13:36:40 -0400 From: Josh Tiefenbach To: Julian Elischer Cc: Josh Tiefenbach , net@FreeBSD.ORG Subject: Re: PPPoE question (repeat) Message-ID: <19991005133640.B97981@snickers.org> References: <19991005092558.A93411@snickers.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Organization: Hah Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 05, 1999 at 09:56:08AM -0700, Julian Elischer wrote: > what are you using for pppoe? Errr. Right now, nothing. :) I saw these values as I was attempting to teach ppp(8) to speak pppoe. I pretty much followed the RFC in sending the PADI - I'd fire off a packet with a zero-length Service-Name tag, and in the PADO, I'd see a zero length Service-Name tag in the reply (2 actually, IIRC), and the aforementioned AC-Name tag. My ISP also distributed some source code for Linux users to use. Other than it being rather ugly and inefficient, it did the same thing - sending a PADI with a zero-length Service-Name tag. If you'd like, when I get home, I'll try to set things up to sniff the connection while running the windows software provided, and see if I can find out anything more. josh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 5 11:33:21 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 8E0251531D for ; Tue, 5 Oct 1999 11:33:12 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id LAA87597; Tue, 5 Oct 1999 11:30:22 -0700 (PDT) Date: Tue, 5 Oct 1999 11:30:21 -0700 (PDT) From: Julian Elischer To: Josh Tiefenbach Cc: net@FreeBSD.ORG Subject: Re: PPPoE question (repeat) In-Reply-To: <19991005133640.B97981@snickers.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org can you send the linux source? I have looked at 2 linux versions already, but not one supplied by a supplier. I am about 70% through coding. julian On Tue, 5 Oct 1999, Josh Tiefenbach wrote: > On Tue, Oct 05, 1999 at 09:56:08AM -0700, Julian Elischer wrote: > > what are you using for pppoe? > > Errr. Right now, nothing. :) > > I saw these values as I was attempting to teach ppp(8) to speak pppoe. I > pretty much followed the RFC in sending the PADI - I'd fire off a packet with > a zero-length Service-Name tag, and in the PADO, I'd see a zero length > Service-Name tag in the reply (2 actually, IIRC), and the aforementioned AC-Name > tag. > > My ISP also distributed some source code for Linux users to use. Other than it > being rather ugly and inefficient, it did the same thing - sending a PADI with > a zero-length Service-Name tag. > > If you'd like, when I get home, I'll try to set things up to sniff > the connection while running the windows software provided, and see if > I can find out anything more. > > josh > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 6 5: 0: 9 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 6D6B515287 for ; Wed, 6 Oct 1999 05:00:06 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id EAA15959 for ; Wed, 6 Oct 1999 04:59:57 -0700 (PDT) Date: Wed, 6 Oct 1999 04:59:57 -0700 (PDT) From: Julian Elischer To: net@freebsd.org Subject: PPPoE report. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org got most of the encapsulator etc. done yesterday however spent about 10 hours rebuilding my machine from spares afte rI lost a disk and then apparently a motherboard (while relacing the disk). A POX on people who design PCs where you have to remove the motherboard to be able to get to teh screws holding in the disk. You then run the risk of breaking something else. No idea what happenned but after I put it all back together teh MB couldn't find teh OTHER (WD) disk. (but the disk was OK). ANYHOW after that rant, I need sleep, but I'll be back on PPPoE tomorrow as I'm back on the air. Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 6 10:18:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from george.arc.nasa.gov (george.arc.nasa.gov [128.102.194.142]) by hub.freebsd.org (Postfix) with ESMTP id 8C6E415759 for ; Wed, 6 Oct 1999 10:18:18 -0700 (PDT) (envelope-from lamaster@nren.nasa.gov) Received: from localhost by george.arc.nasa.gov (8.9.3/8.9.3) with SMTP id KAA13960 for ; Wed, 6 Oct 1999 10:16:52 -0700 (PDT) X-Authentication-Warning: george.arc.nasa.gov: lamaster owned process doing -bs Date: Wed, 6 Oct 1999 10:16:51 -0700 (PDT) From: Hugh LaMaster X-Sender: lamaster@george.arc.nasa.gov To: "FreeBSD-Net (FreeBSD.Org)" Subject: Re: Tulip drivers for BSD. In-Reply-To: <37EB1C97.64915398@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 24 Sep 1999, Wes Peters wrote: > > Can any one tell me the sites for "Well Documented" Tulip drivers for BSD. > > I did search a lot but failed. > > man de > > They're included in the system; you don't have to go fetch them from some > website somewhere. Yes, and, when last I looked at it, the Tulip cards were the most efficient available when it comes to multicast, and, very good wrt high-bandwidth CPU efficiency. Unfortunately, over the last year, most companies shipping NICs have stopped marking on the packages what chipset they use, and some have switched chipsets within the same product line. At this point, I have no idea how to tell which current product lines use the Tulip chipset. Is anyone keeping a current list? Is the Tulip chipset still in production/widespread use? What are FreeBSD'ers recommending these days wrt multicast and CPU efficiency (and, which is currently supported)? -- Hugh LaMaster, M/S 233-21, Email: lamaster@nren.nasa.gov NASA Ames Research Center Or: lamaster@nas.nasa.gov Moffett Field, CA 94035-1000 Or: lamaster@george.arc.nasa.gov Phone: 650/604-1056 Disc: Unofficial, personal *opinion*. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 6 11:27:38 1999 Delivered-To: freebsd-net@freebsd.org Received: from smyk.apk.net (smyk.apk.net [207.54.158.17]) by hub.freebsd.org (Postfix) with ESMTP id 8026214D5B for ; Wed, 6 Oct 1999 11:26:51 -0700 (PDT) (envelope-from stuart@apk.net) Received: from junior.apk.net (stuart@junior.apk.net [207.54.158.20]) by smyk.apk.net (8.9.3/8.9.3/apk.990812+rchk1.22+bspm1.13.1.5) with ESMTP id OAA12235; Wed, 6 Oct 1999 14:15:12 -0400 (EDT) Received: from localhost (stuart@localhost) by junior.apk.net (8.9.3/8.9.3) with ESMTP id OAA29329; Wed, 6 Oct 1999 14:15:09 -0400 (EDT) Date: Wed, 6 Oct 1999 14:15:09 -0400 (EDT) From: Stuart Krivis To: Hugh LaMaster Cc: "FreeBSD-Net (FreeBSD.Org)" Subject: Re: Tulip drivers for BSD. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 6 Oct 1999, Hugh LaMaster wrote: > NICs have stopped marking on the packages what chipset > they use, and some have switched chipsets within the > same product line. At this point, I have no idea how > to tell which current product lines use the Tulip chipset. > Is anyone keeping a current list? Is the Tulip chipset > still in production/widespread use? I have several recent Kingston KNE100 cards with an Intel version of the Tulip. It seems to work quite well. > > What are FreeBSD'ers recommending these days wrt multicast > and CPU efficiency (and, which is currently supported)? I hear a lot about the Intel Pro100 cards. In fact, people seem to like them over the Tulip cards. I keep wondering whatever happened to 3Com cards. They used to be the best choice because they worked with everything. -- Stuart Krivis stuart@krivis.com Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 6 12:13:23 1999 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 64B751575D for ; Wed, 6 Oct 1999 12:12:02 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id PAA56427; Wed, 6 Oct 1999 15:12:00 -0400 (EDT) (envelope-from wollman) Date: Wed, 6 Oct 1999 15:12:00 -0400 (EDT) From: Garrett Wollman Message-Id: <199910061912.PAA56427@khavrinen.lcs.mit.edu> To: Hugh LaMaster Cc: "FreeBSD-Net (FreeBSD.Org)" Subject: Re: Tulip drivers for BSD. In-Reply-To: References: <37EB1C97.64915398@softweyr.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Is anyone keeping a current list? Is the Tulip chipset > still in production/widespread use? It is still in production, but the sale of Digital Semiconductor to Intel has cast long shadows over the product. Most vendors could see the writing on the wall and switched to another manufacturer's silicon. (Many of these are similar to the 21143, but have inferior bus interfaces and require their own drivers.) The best chip to buy at this point is probably the Intel 82558. It has an excellent bus interface (better than the 21143's) and a clean and efficient driver in FreeBSD. Unfortunately, it does not have a perfect multicast filter -- but then, I've never seen nor heard of a non-DEC product which did. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 6 13: 3: 7 1999 Delivered-To: freebsd-net@freebsd.org Received: from kit.isi.edu (kit.isi.edu [128.9.160.207]) by hub.freebsd.org (Postfix) with ESMTP id B7D3015744 for ; Wed, 6 Oct 1999 13:02:43 -0700 (PDT) (envelope-from eddy@kit.isi.edu) Received: (from eddy@localhost) by kit.isi.edu (8.9.2/8.8.7) id MAA06992; Wed, 6 Oct 1999 12:52:35 -0700 (PDT) (envelope-from eddy) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 6 Oct 1999 12:52:35 -0700 (PDT) From: eddy@isi.edu To: Garrett Wollman Cc: Hugh LaMaster , "FreeBSD-Net (FreeBSD.Org)" Subject: Re: Tulip drivers for BSD. In-Reply-To: <199910061912.PAA56427@khavrinen.lcs.mit.edu> References: <37EB1C97.64915398@softweyr.com> <199910061912.PAA56427@khavrinen.lcs.mit.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14331.43011.715630.511708@kit.isi.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Garrett Wollman states: > < said: > > The best chip to buy at this point is probably the Intel 82558. does anyone know if there any quad cards based on this chipset? (or any supported chipset other than the tulip)? - rusty To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 6 19:44:21 1999 Delivered-To: freebsd-net@freebsd.org Received: from cc.weber.edu (cc.weber.edu [137.190.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 2855C14F43 for ; Wed, 6 Oct 1999 19:43:56 -0700 (PDT) (envelope-from jlewis@cc.weber.edu) Received: from offcampus.weber.edu ([137.190.3.226]) by cc.WEBER.EDU (PMDF V5.1-12 #7039) with SMTP id <01JGTSZ748SW8Y7PXQ@cc.WEBER.EDU> for freebsd-net@freebsd.org; Wed, 6 Oct 1999 20:43:54 MST Date: Wed, 06 Oct 1999 20:43:47 -0600 (Mountain Daylight Time) From: Jason Lewis Subject: ppp To: freebsd-net@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-X-Sender: jlewis9@gwmta1.weber.edu Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org How can one route public IP's over ppp without IP Masquerading? I tried enabling forwarding, but it didnot work. Do I need to use pppd instead of ppp? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 7 3:25:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id D563414C25 for ; Thu, 7 Oct 1999 03:25:40 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id LAA70684; Thu, 7 Oct 1999 11:25:38 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA04197; Thu, 7 Oct 1999 11:26:28 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910071026.LAA04197@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Jason Lewis Cc: freebsd-net@FreeBSD.ORG Subject: Re: ppp In-reply-to: Your message of "Wed, 06 Oct 1999 20:43:47 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Oct 1999 11:26:28 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > How can one route public IP's over ppp without IP Masquerading? I tried > enabling forwarding, but it didnot work. Do I need to use pppd instead of > ppp? I'd advise using tcpdump (or enabling ppps tcp/ip logging) at each point of the packets journey to discover what's not forwarding it... Ppp is functionally the same as pppd in this respect. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 6:57:18 1999 Delivered-To: freebsd-net@freebsd.org Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110]) by hub.freebsd.org (Postfix) with ESMTP id 6F80714D9D for ; Fri, 8 Oct 1999 06:56:51 -0700 (PDT) (envelope-from jacopo.pecci@erv.ericsson.se) Received: from ervgwy.eritel.se (ervgwy.erv.ericsson.se [192.71.49.65]) by penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.3) with SMTP id PAA18568 for ; Fri, 8 Oct 1999 15:56:50 +0200 (MET DST) Received: by ervgwy.eritel.se (4.1/SMI-4.1) id AA13063; Fri, 8 Oct 99 15:56:50 +0200 Received: from puh.erv.ericsson.se(193.234.208.14) by ervgwy.eritel.se via smap (V1.3) id sma013058; Fri Oct 8 15:56:26 1999 Received: from simba.eritel.se by puh (SMI-8.6/SMI-SVR4) id PAA16826; Fri, 8 Oct 1999 15:56:24 +0200 Received: from erv.ericsson.se (localhost [127.0.0.1]) by simba.eritel.se (8.8.8+Sun/8.8.8) with ESMTP id PAA10284 for ; Fri, 8 Oct 1999 15:56:23 +0200 (MET DST) Message-Id: <37FDF806.1D2FD356@erv.ericsson.se> Date: Fri, 08 Oct 1999 15:56:22 +0200 From: Jacopo Pecci X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.6 sun4m) X-Accept-Language: en Mime-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: how to drop few packets Content-Type: multipart/alternative; boundary="------------C7D122A554FFE22DF9E7AA2B" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------C7D122A554FFE22DF9E7AA2B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have just implemented the new reno algorithm but I would like to have a sort of feedback to see if it is working. I have built up a small network with 3 PCs, one of them act as a router and has NISTnet emulator to emulate some channels. Do you have any idea how I could check if my implementation is right or wrong? I should find the way to drop few packets in the same window (is there any traffic generator like SOCK that allows me to drop some packets?). -- -------------------------------------------------------- Jacopo Pecci Ericsson Mobile Data Design phone: +46 (0)31 703 6920 -------------------------------------------------------- --------------C7D122A554FFE22DF9E7AA2B Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit I have just implemented the new reno algorithm but I would like to have a sort of feedback to see if it is working.
I have built up a small network with 3 PCs, one of them act as a router and has NISTnet emulator to emulate some channels.
Do you have any idea how I could check if my implementation is right or wrong? I should find the way to drop few packets in the same window (is there any traffic generator like SOCK that allows me to drop some packets?). 
-- 
--------------------------------------------------------
Jacopo Pecci 
Ericsson Mobile Data Design
phone: +46 (0)31 703 6920
--------------------------------------------------------
  --------------C7D122A554FFE22DF9E7AA2B-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 7: 9:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from btm4r4.alcatel.be (btm4r4.alcatel.be [195.207.101.110]) by hub.freebsd.org (Postfix) with ESMTP id 0A5C714E25 for ; Fri, 8 Oct 1999 07:09:09 -0700 (PDT) (envelope-from livensw@rc.bel.alcatel.be) Received: from btmq9s.rc.bel.alcatel.be (btmq9s.rc.bel.alcatel.be [138.203.65.182]) by btm4r4.alcatel.be (8.9.1a/8.9.1) with ESMTP id QAA12759 for ; Fri, 8 Oct 1999 16:09:08 +0200 (MET DST) Received: (from livensw@localhost) by btmq9s.rc.bel.alcatel.be (8.8.8+Sun/8.8.8) id QAA04309 for freebsd-net@freebsd.org; Fri, 8 Oct 1999 16:09:56 +0200 (MET DST) Date: Fri, 8 Oct 1999 16:09:55 +0200 From: Wim Livens To: freebsd-net@freebsd.org Subject: IP_TOS on raw socket Message-ID: <19991008160955.A1671@rc.bel.alcatel.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've noticed that the IP_TOS socket option doesn't work on raw sockets. There is no error returned and the TOS is stored in the protocol control block but when the packet headers are constructed, a hardcoded zero is put (instead of inp->inp_ip_tos). Is there any specific reason for this or is this a bug ? (I don't want to use IP_HDRINCL). Here an extract from netinet/raw_ip.c: int rip_output(m, so, dst) ... ip->ip_tos = 0; ip->ip_off = 0; ip->ip_p = inp->inp_ip_p; ip->ip_len = m->m_pkthdr.len; ip->ip_src = inp->inp_laddr; ip->ip_dst.s_addr = dst; ip->ip_ttl = MAXTTL; Clearly, the same holds for the ttl. BTW, the linux implementation does allow to set the tos on raw sockets. Thanks for any comments, -- Wim Livens. Alcatel - Corporate Research Center wim.livens@alcatel.be Fr. Wellesplein 1 livensw@rc.bel.alcatel.be B-2018 Antwerpen Tel: +32 3 240 7570 Belgium. Fax: +32 3 240 9932 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 7:16: 7 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 6CD8D150CE for ; Fri, 8 Oct 1999 07:16:03 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id QAA18526; Fri, 8 Oct 1999 16:17:50 +0100 From: Luigi Rizzo Message-Id: <199910081517.QAA18526@labinfo.iet.unipi.it> Subject: Re: how to drop few packets To: jacopo.pecci@erv.ericsson.se (Jacopo Pecci) Date: Fri, 8 Oct 1999 16:17:49 +0100 (MET) Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <37FDF806.1D2FD356@erv.ericsson.se> from "Jacopo Pecci" at Oct 8, 99 03:56:03 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1390 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have just implemented the new reno algorithm but I would like to have > a sort of feedback to see if it is working. > I have built up a small network with 3 PCs, one of them act as a router > and has NISTnet emulator to emulate some channels. since you are using freebsd, why don't you just use dummynet which is part of recent FreeBSD distributions to simulate the lossy/congested channel ? > Do you have any idea how I could check if my implementation is right or > wrong? I should find the way to drop few packets in the same window (is > there any traffic generator like SOCK that allows me to drop some > packets?). To simulate what you want you could first try with a small queue size (because TCP is bursty), then you could even do minor modifications to dummynet to set some histeresys on the queue -- drop once above the high water mark, and keep dropping until the queue goes below low water. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) http://www.iet.unipi.it/~luigi/ngc99/ ==== First International Workshop on Networked Group Communication ==== -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 9:12:48 1999 Delivered-To: freebsd-net@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 37C2114FC2 for ; Fri, 8 Oct 1999 09:12:41 -0700 (PDT) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.9.3/8.9.3) id JAA71227; Fri, 8 Oct 1999 09:12:18 -0700 (PDT) Message-Id: <199910081612.JAA71227@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.0 09/18/1999 To: Wim Livens Cc: freebsd-net@FreeBSD.ORG Subject: Re: IP_TOS on raw socket In-Reply-To: Your message of "Fri, 08 Oct 1999 16:09:55 +0200." <19991008160955.A1671@rc.bel.alcatel.be> From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-167196902P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 08 Oct 1999 09:12:18 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --==_Exmh_-167196902P Content-Type: text/plain; charset=us-ascii If memory serves me right, Wim Livens wrote: > I've noticed that the IP_TOS socket option doesn't work on raw > sockets. There is no error returned and the TOS is stored in the > protocol control block but when the packet headers are constructed, a > hardcoded zero is put (instead of inp->inp_ip_tos). > > Is there any specific reason for this or is this a bug ? I don't know the answer to this question, but it does seem a little odd. TCP/IP Illustrated Volume 2 [1] has no comment on this issue (p. 1056): The TOS is set to 0 and the TTL to 255....[this] differs from UDP and TCP where the process had the capabillity of setting the IP_TTL and IP_TOS socket options. While I was looking through rip_output I noticed something else odd...it seems that if the user process tries to send a larger-than-MTU raw packet, rip_output seems to generate an error, rather than allow a fragment to be generated. This sounds like an attempt at better security, but I'm curious about this also. I used IP_HDRINCL when I needed to tweak the TOS and TTL bytes for raw packets (mostly because some older OSs didn't allow one to actually set them via setsockopt) so you might keep that in mind if portability is an issue. However, see cautions documented on p. 657 of UNIX Network Programming (second edition), Volume 1 about byte-ordering of fields in the IP packet. Bruce. [1] RIP WRS --==_Exmh_-167196902P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: RhV1Rni9kgq76vyHrTF3bbxd+73khube iQA/AwUBN/4X4tjKMXFboFLDEQJO5gCg2qqAPfb0RMn+MkkUYRjVx1UV+wQAoNcv 4ZhIcsoqikNahtoU1iWIn2PM =8dem -----END PGP SIGNATURE----- --==_Exmh_-167196902P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 13:51:57 1999 Delivered-To: freebsd-net@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 79FC514D29; Fri, 8 Oct 1999 13:51:34 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id PAA25028; Fri, 8 Oct 1999 15:51:29 -0500 (CDT) From: Mohit Aron Message-Id: <199910082051.PAA25028@cs.rice.edu> Subject: sbappend() is not scalable To: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Date: Fri, 8 Oct 1999 15:51:29 -0500 (CDT) Cc: tech-net@netbsd.org X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I recently did some experiments with TCP over a high b/w-delay path and found a scalability problem in sbappend(). The experimental setup consisted of a 100Mbps network with a round-trip delay of 100ms. Under this situation, FreeBSD's TCP version is incapable of attaining more than 65 Mbps on a 300MHz Pentium II - even without slow-start. I tracked down the problem to sbappend() - the routine that appends user data into the socket buffers for network transmission. Every time a TCP ACK acknowledges some data, space is created in the socket buffer that permits more data to be appended. Unfortunately, the implementation does not maintain a pointer to the end of the list of mbufs in the socket buffer. Thus each time any data is added, the whole list of mbufs is traversed to reach the very end where the data is added. Since the b/w-delay product is large, there can be about 600 mbufs in the socket buffer waiting to be acknowledged. Thus upon every ACK, about 600 mbufs are traversed causing the TCP sender to run out of CPU. The problem is not limited only to high b/w networks - it is also present in long latency paths (satellite links). Thus a server transferring a large file over a satellite link can spend lot of CPU due to the above problem. Hope the problem shall be fixed in future releases, - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 14:29:59 1999 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 32D6814F9B for ; Fri, 8 Oct 1999 14:29:56 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id RAA67391; Fri, 8 Oct 1999 17:29:54 -0400 (EDT) (envelope-from wollman) Date: Fri, 8 Oct 1999 17:29:54 -0400 (EDT) From: Garrett Wollman Message-Id: <199910082129.RAA67391@khavrinen.lcs.mit.edu> To: Mohit Aron Cc: freebsd-net@FreeBSD.ORG Subject: sbappend() is not scalable In-Reply-To: <199910082051.PAA25028@cs.rice.edu> References: <199910082051.PAA25028@cs.rice.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > can be about 600 mbufs in the socket buffer waiting to be acknowledged. Thus > upon every ACK, about 600 mbufs are traversed causing the TCP sender to run > out of CPU. This is a well-known feature of the 4BSD socket layer. The right fix is to get rid of the socket layer, but this requires a substantial effort that none of the people who know how to do it have been able to put in. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 14:34: 0 1999 Delivered-To: freebsd-net@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 2559E14C14 for ; Fri, 8 Oct 1999 14:33:52 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id QAA26223; Fri, 8 Oct 1999 16:33:51 -0500 (CDT) From: Mohit Aron Message-Id: <199910082133.QAA26223@cs.rice.edu> Subject: Re: sbappend() is not scalable To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 8 Oct 1999 16:33:51 -0500 (CDT) Cc: freebsd-net@freebsd.org In-Reply-To: <199910082129.RAA67391@khavrinen.lcs.mit.edu> from "Garrett Wollman" at Oct 8, 99 05:29:54 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > This is a well-known feature of the 4BSD socket layer. The right fix > is to get rid of the socket layer, but this requires a substantial > effort that none of the people who know how to do it have been able to > put in. > It may not require such a massive effort. I fixed it for my experiments just by maintaining an extra pointer to the tail of the list of mbufs. My solution however isn't general enough in that I haven't patched other parts of the socket/mbuf code to know about this pointer. However, I don't think it should require overhauling the whole system. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 14:46:31 1999 Delivered-To: freebsd-net@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8F0E614EE6 for ; Fri, 8 Oct 1999 14:46:28 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id RAA01636; Fri, 8 Oct 1999 17:46:13 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA19829; Fri, 8 Oct 1999 17:45:43 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 8 Oct 1999 17:45:43 -0400 (EDT) To: Mohit Aron Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), freebsd-net@FreeBSD.ORG Subject: Re: sbappend() is not scalable In-Reply-To: <199910082133.QAA26223@cs.rice.edu> References: <199910082129.RAA67391@khavrinen.lcs.mit.edu> <199910082133.QAA26223@cs.rice.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14334.25691.85379.323929@grasshopper.cs.duke.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mohit Aron writes: > > > > > This is a well-known feature of the 4BSD socket layer. The right fix > > is to get rid of the socket layer, but this requires a substantial > > effort that none of the people who know how to do it have been able to > > put in. > > > > > It may not require such a massive effort. I fixed it for my experiments just > by maintaining an extra pointer to the tail of the list of mbufs. My solution > however isn't general enough in that I haven't patched other parts of the > socket/mbuf code to know about this pointer. However, I don't think it should > require overhauling the whole system. For what it is worth, sbappend() is also responsible for a non-trivial amount of cpu wastage when running TCP on low-latency, high-bandwidth networks such gigabit ethernet & myrinet. I don't have the exact data in front of me, but I seem to remember that, next to bcopy & in_cksumdata, it is the function where the most cpu is being spent when transmitting at in the range of 500-1100Mb/s. This is according to iprobe on FreeBSD/alpha. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 17: 0:14 1999 Delivered-To: freebsd-net@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 91EE915445; Fri, 8 Oct 1999 17:00:08 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id TAA28762; Fri, 8 Oct 1999 19:00:07 -0500 (CDT) From: Mohit Aron Message-Id: <199910090000.TAA28762@cs.rice.edu> Subject: arp errors on machines with two interfaces To: freebsd-bugs@freebsd.org Date: Fri, 8 Oct 1999 19:00:06 -0500 (CDT) Cc: freebsd-net@freebsd.org, alc@cs.rice.edu (Alan Cox) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, whenever I have a FreeBSD machine containing two interfaces connected to switched 100Mbps Ethernet, I keep getting arp errors of the form: arp: 128.42.1.30 is on fxp0 but got reply from 08:00:20:87:90:92 on fxp1 Here's an output of 'uname -a' on my machine: FreeBSD idli.cs.rice.edu 3.3-RELEASE FreeBSD 3.3-RELEASE #7: Fri Oct 8 17:31:12 CDT 1999 aron@idli.cs.rice.edu:/usr/users/aron/FreeBSD-3.3-src/sys/compile/IDLI i386 I managed to find the source of these error reports. The steps below outline what happens. 1) The FreeBSD machine in question is idli.cs.rice.edu and has two network interfaces fxp0 and fxp1. The routing tables are set such that all packets to machine cs.rice.edu (128.42.1.30) are routed through interface fxp0. 2) Any communication between idli.cs.rice.edu and cs.rice.edu results in cs.rice.edu's address to be stored in the arp cache of idli.cs.rice.edu. Lets assume that this has happened. 3) Assume now that someone on cs.rice.edu does a login to a 3rd machine foo.cs.rice.edu. cs.rice.edu sends an arp broadcast on the network asking for foo.cs.rice.edu's ethernet address. This broadcast is received on both the interfaces of idli.cs.rice.edu. 4) Upon getting arp packets from cs.rice.edu, idli.cs.rice.edu gets a chance to refresh the address of cs.rice.edu in its arp cache (although idli.cs.rice.edu won't reply to the arp query). The processing for the arp packet received on interface fxp0 happens without any problem. 5) However, the processing for the arp packet received on interface fxp1 raises an arp error. This is because the routing table entry indicates that arp packets from cs.rice.edu should arrive on interface fxp0. This raises the arp errors that keep flooding the message log. The code in question is in sys/netinet/if_ether.c in the function in_arpinput(). Is there a better way to fix the problem other than simply turning the error report off ? - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 18:21:57 1999 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 9D4C014C15 for ; Fri, 8 Oct 1999 18:21:55 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA68534; Fri, 8 Oct 1999 21:21:53 -0400 (EDT) (envelope-from wollman) Date: Fri, 8 Oct 1999 21:21:53 -0400 (EDT) From: Garrett Wollman Message-Id: <199910090121.VAA68534@khavrinen.lcs.mit.edu> To: Mohit Aron Cc: freebsd-net@FreeBSD.ORG Subject: arp errors on machines with two interfaces In-Reply-To: <199910090000.TAA28762@cs.rice.edu> References: <199910090000.TAA28762@cs.rice.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Is there a better way to fix the problem other than simply turning the > error report off ? Yes, don't put two network interfaces on one (logical) wire. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 21:16:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id B73F115870 for ; Fri, 8 Oct 1999 21:16:14 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id XAA01282; Fri, 8 Oct 1999 23:16:12 -0500 (CDT) From: Mohit Aron Message-Id: <199910090416.XAA01282@cs.rice.edu> Subject: Re: arp errors on machines with two interfaces To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 8 Oct 1999 23:16:12 -0500 (CDT) Cc: freebsd-net@freebsd.org, alc@cs.rice.edu (Alan Cox) In-Reply-To: <199910090121.VAA68534@khavrinen.lcs.mit.edu> from "Garrett Wollman" at Oct 8, 99 09:21:53 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Yes, don't put two network interfaces on one (logical) wire. > Brilliant! All machines in our dept are connected by switched 100Mbps Ethernet - so your suggestion implies that I either don't put two network interfaces on the machine or don't connect both to the network. The first would mean I cannot saturate the machine anymore in my experiments, and I'll leave the second to more imaginative minds than mine. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 22:45:35 1999 Delivered-To: freebsd-net@freebsd.org Received: from at.dotat.com (zed.dotat.com [203.2.134.254]) by hub.freebsd.org (Postfix) with ESMTP id 8EA471586A for ; Fri, 8 Oct 1999 22:45:27 -0700 (PDT) (envelope-from hart@at.dotat.com) Received: from at.dotat.com (localhost.dotat.com [127.0.0.1]) by at.dotat.com (8.8.8/8.8.8) with ESMTP id PAA20008; Sat, 9 Oct 1999 15:15:14 +0930 (CST) Message-Id: <199910090545.PAA20008@at.dotat.com> To: Mohit Aron Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), freebsd-net@FreeBSD.ORG, alc@cs.rice.edu (Alan Cox) Subject: Re: arp errors on machines with two interfaces In-reply-to: Your message of "Fri, 08 Oct 1999 23:16:12 EST." <199910090416.XAA01282@cs.rice.edu> Date: Sat, 09 Oct 1999 15:15:14 +0930 From: Leigh Hart Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Mohit, Mohit Aron wrote: > > > Yes, don't put two network interfaces on one (logical) wire. > > Brilliant! All machines in our dept are connected by switched > 100Mbps Ethernet - so your suggestion implies that I either > don't put two network interfaces on the machine or don't > connect both to the network. > > The first would mean I cannot saturate the machine anymore in > my experiments, and I'll leave the second to more imaginative > minds than mine. If you require more than 100Mbps of aggregate bandwidth to the network, use FastEtherchannel or use two different (logical) subnets via two different VLANs on your switch. Cheers Leigh -- | "By the time they had diminished | Leigh Hart, hart@dotat.com | | from 50 to 8, the other dwarves | CCNA: http://www.cisco.com | | began to suspect 'Hungry' ..." | PO Box 3057 Newton SA 5074 | | -- Gary Larson, "The Far Side" | http://www.dotat.com/hart/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 8 22:53:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E02314F45 for ; Fri, 8 Oct 1999 22:53:53 -0700 (PDT) (envelope-from justin@walker3.apple.com) Received: from mailgate2.apple.com ([17.129.100.225]) by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id WAA13876 for ; Fri, 8 Oct 1999 22:53:52 -0700 (PDT) Received: from scv1.apple.com (scv1.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 2.0.15) with ESMTP id for ; Fri, 08 Oct 1999 22:53:52 -0700 Received: from walker3.apple.com (walkeridsl1.apple.com [17.219.158.66]) by scv1.apple.com (8.9.3/8.9.3) with ESMTP id WAA17924 for ; Fri, 8 Oct 1999 22:53:46 -0700 (PDT) Received: (from justin@localhost) by walker3.apple.com (8.9.1/8.9.1) id WAA00756 for freebsd-net@FreeBSD.ORG; Fri, 8 Oct 1999 22:53:41 -0700 (PDT) Message-Id: <199910090553.WAA00756@walker3.apple.com> To: freebsd-net@freebsd.org Subject: Re: arp errors on machines with two interfaces In-Reply-To: "Your message of Fri, 08 Oct 1999 23:16:12 EST."<199910090416.XAA01282@cs.rice.edu> Date: Fri, 8 Oct 1999 22:53:39 -0700 From: "Justin C. Walker" Reply-To: justin@apple.com X-Mailer: by Apple MailViewer (2.105.dev) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: Leigh Hart > Date: 1999-10-08 22:45:42 -0700 > To: Mohit Aron > Subject: Re: arp errors on machines with two interfaces > Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), > freebsd-net@FreeBSD.ORG,alc@cs.rice.edu (Alan Cox) > In-reply-to: "Your message of Fri, 08 Oct 1999 23:16:12 > EST."<199910090416.XAA01282@cs.rice.edu> > Delivered-to: freebsd-net@freebsd.org > X-Loop: FreeBSD.org > > Hi Mohit, > > Mohit Aron wrote: > > > > > Yes, don't put two network interfaces on one (logical) wire. > > > > Brilliant! All machines in our dept are connected by switched > > 100Mbps Ethernet - so your suggestion implies that I either > > don't put two network interfaces on the machine or don't > > connect both to the network. > > > > The first would mean I cannot saturate the machine anymore in > > my experiments, and I'll leave the second to more imaginative > > minds than mine. Garrett is correct, and sarcasm doesn't help. You can't have more than one interface on a given wire, with the same subnet address, using IP. Them's the protocol rules. There are ways around this, but I don't know if FreeBSD supports them (check the archives). One involves "bonding" multiple interfaces as a single "uber channel" to the switch. It requires support in the switch, of course. The bonding lets you load balance across multiple interfaces (which look like a single interface, with a single IP address [or, more acurately, subnet], to the outside whirled). Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking | When crypto is outlawed, Apple Computer, Inc. | Only outlaws will have crypto. 2 Infinite Loop | Cupertino, CA 95014 | *-------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 8: 5: 6 1999 Delivered-To: freebsd-net@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 6606A14E5E for ; Sat, 9 Oct 1999 08:05:03 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id KAA07190; Sat, 9 Oct 1999 10:04:50 -0500 (CDT) From: Mohit Aron Message-Id: <199910091504.KAA07190@cs.rice.edu> Subject: Re: arp errors on machines with two interfaces To: hart@dotat.com (Leigh Hart) Date: Sat, 9 Oct 1999 10:04:50 -0500 (CDT) Cc: wollman@khavrinen.lcs.mit.edu, freebsd-net@freebsd.org, alc@cs.rice.edu In-Reply-To: <199910090545.PAA20008@at.dotat.com> from "Leigh Hart" at Oct 9, 99 03:15:14 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > If you require more than 100Mbps of aggregate bandwidth to the > network, use FastEtherchannel or use two different (logical) > subnets via two different VLANs on your switch. > Well, since this is switched Ethernet, I can still get 200 Mbps on it even though it is the same "logical" wire. That is, I can have different clients connecting simultaneously to both interfaces without interfering with each other's data. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 9:50:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 7E84114BF3 for ; Sat, 9 Oct 1999 09:50:52 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id LAA08261; Sat, 9 Oct 1999 11:50:51 -0500 (CDT) From: Mohit Aron Message-Id: <199910091650.LAA08261@cs.rice.edu> Subject: Re: arp errors on machines with two interfaces To: freebsd-net@freebsd.org, justin@apple.com Date: Sat, 9 Oct 1999 11:50:51 -0500 (CDT) Cc: alc@cs.rice.edu (Alan Cox), wollman@khavrinen.lcs.mit.edu X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Garrett is correct, and sarcasm doesn't help. You can't have more > than one interface on a given wire, with the same subnet address, > using IP. Them's the protocol rules. > Actually I am using different subnet addresses on the two interfaces. One is 128.42.3.77 and the other is 192.168.3.77. There are other machines in the dept running Solaris and other OS's that are connected in similar fashions. However, the Ethernet is switched and any broadcast by anyone is going to be seen by all interfaces connected to it. > There are ways around this, but I don't know if FreeBSD supports > them (check the archives). One involves "bonding" multiple > interfaces as a single "uber channel" to the switch. It requires > support in the switch, of course. The bonding lets you load balance > across multiple interfaces (which look like a single interface, with > a single IP address [or, more acurately, subnet], to the outside > whirled). I don't have control over the hardware. But here's a possibility - wouldn't it be better if this error message generation in FreeBSD is turned off if the packet is an arp broadcast ? Like I showed in my earlier mail, the problem only happens due to arp broadcasts. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 13:52:22 1999 Delivered-To: freebsd-net@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id DA97014C26 for ; Sat, 9 Oct 1999 13:52:11 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 63644 invoked by uid 1001); 9 Oct 1999 20:52:08 +0000 (GMT) To: aron@cs.rice.edu Cc: freebsd-net@freebsd.org, justin@apple.com, alc@cs.rice.edu, wollman@khavrinen.lcs.mit.edu Subject: Re: arp errors on machines with two interfaces From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 9 Oct 1999 11:50:51 -0500 (CDT)" References: <199910091650.LAA08261@cs.rice.edu> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 09 Oct 1999 22:52:08 +0200 Message-ID: <63642.939502328@verdi.nethelp.no> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Garrett is correct, and sarcasm doesn't help. You can't have more > > than one interface on a given wire, with the same subnet address, > > using IP. Them's the protocol rules. > > Actually I am using different subnet addresses on the two interfaces. One is > 128.42.3.77 and the other is 192.168.3.77. There are other machines in the > dept running Solaris and other OS's that are connected in similar fashions. > However, the Ethernet is switched and any broadcast by anyone is going to be > seen by all interfaces connected to it. What you are doing is not supported by the standard TCP/IP model of communication. The fact that it (partly) works for you should be regarded as incidental. Try to think of it in terms of a traditional coax-based Ethernet, and having two NICs on one host connected to the same physical Ethernet cable. Would you expect this to work? (You shouldn't.) > I don't have control over the hardware. But here's a possibility - wouldn't > it be better if this error message generation in FreeBSD is turned off if > the packet is an arp broadcast ? Like I showed in my earlier mail, the > problem only happens due to arp broadcasts. No, the problem happens due to the fact that you are connecting two Ethernet NICs to the same segment. This is not supported. Why should the error message be turned off just to please you, when you're using an unsupported configuration? Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 14: 3: 5 1999 Delivered-To: freebsd-net@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id DA6C314C26 for ; Sat, 9 Oct 1999 14:03:01 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id QAA11299; Sat, 9 Oct 1999 16:02:57 -0500 (CDT) From: Mohit Aron Message-Id: <199910092102.QAA11299@cs.rice.edu> Subject: Re: arp errors on machines with two interfaces To: sthaug@nethelp.no Date: Sat, 9 Oct 1999 16:02:57 -0500 (CDT) Cc: freebsd-net@freebsd.org, justin@apple.com, alc@cs.rice.edu, wollman@khavrinen.lcs.mit.edu In-Reply-To: <63642.939502328@verdi.nethelp.no> from "sthaug@nethelp.no" at Oct 9, 99 10:52:08 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Try to think of it in terms of a traditional coax-based Ethernet, and > having two NICs on one host connected to the same physical Ethernet > cable. Would you expect this to work? (You shouldn't.) > Well with the traditional Ethernet, it didn't make much sense to connect multiple interfaces to the same wire - you don't expect both interfaces together to deliver any more than 10Mbps. However, with switched Ethernet, both interfaces can deliver the full b/w. So why not get the advantages of getting this higher b/w as well as full one on one connectivity between hosts connected to the Ethernet ? - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 14:10:14 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 143E4154CB for ; Sat, 9 Oct 1999 14:10:07 -0700 (PDT) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id OAA51006; Sat, 9 Oct 1999 14:07:03 -0700 (PDT) Date: Sat, 9 Oct 1999 14:06:54 -0700 (PDT) From: Julian Elischer X-Sender: julian@home.elischer.org To: sthaug@nethelp.no Cc: aron@cs.rice.edu, freebsd-net@FreeBSD.ORG, justin@apple.com, alc@cs.rice.edu, wollman@khavrinen.lcs.mit.edu Subject: Re: arp errors on machines with two interfaces In-Reply-To: <63642.939502328@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 9 Oct 1999 sthaug@nethelp.no wrote: > > > Garrett is correct, and sarcasm doesn't help. You can't have more > > > than one interface on a given wire, with the same subnet address, > > > using IP. Them's the protocol rules. > > > > Actually I am using different subnet addresses on the two interfaces. One is > > 128.42.3.77 and the other is 192.168.3.77. There are other machines in the > > dept running Solaris and other OS's that are connected in similar fashions. > > However, the Ethernet is switched and any broadcast by anyone is going to be > > seen by all interfaces connected to it. Why are you doing this? Why not just assign the two addresses to the same NIC? (though I guess with a switch you may be able to get twice the throughput with two NICs..) He does have a point however.. ARP packets that are not for the networks that are on teh receiving NIC could probably be safely discarded without effecting the way that the system supports the spec. I think it's vague on this point, and we SEE that other people do similar. I would actually thinkmthat it would be a security imporovement. I don't think we should accept cofiguration or routing information from machines that are not on the right network. If I had one net inside a firewall and one outside, I don't want to recieve ARP packets from the outside that are influencing my internal routint (arp) table. > > What you are doing is not supported by the standard TCP/IP model of > communication. The fact that it (partly) works for you should be > regarded as incidental. > > Try to think of it in terms of a traditional coax-based Ethernet, and > having two NICs on one host connected to the same physical Ethernet > cable. Would you expect this to work? (You shouldn't.) > > > I don't have control over the hardware. But here's a possibility - wouldn't > > it be better if this error message generation in FreeBSD is turned off if > > the packet is an arp broadcast ? Like I showed in my earlier mail, the > > problem only happens due to arp broadcasts. > > No, the problem happens due to the fact that you are connecting two > Ethernet NICs to the same segment. This is not supported. Why should the > error message be turned off just to please you, when you're using an > unsupported configuration? This is not that unsupported.. High availability hosts do this all the time, and need to. My suggestion is that we check incoming arp packets to discard packets that resolve addresses that are not in a netrange on the interface into which they came. I think this is a good idea anyway for security reasons and we can dispense with the check against ALL local networks. It might even be faster. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 14:14:41 1999 Delivered-To: freebsd-net@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 06DBC150D0 for ; Sat, 9 Oct 1999 14:14:38 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id QAA11499; Sat, 9 Oct 1999 16:14:34 -0500 (CDT) From: Mohit Aron Message-Id: <199910092114.QAA11499@cs.rice.edu> Subject: Re: arp errors on machines with two interfaces To: julian@whistle.com (Julian Elischer) Date: Sat, 9 Oct 1999 16:14:33 -0500 (CDT) Cc: sthaug@nethelp.no, freebsd-net@freebsd.org, justin@apple.com, alc@cs.rice.edu, wollman@khavrinen.lcs.mit.edu In-Reply-To: from "Julian Elischer" at Oct 9, 99 02:06:54 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Why are you doing this? > Why not just assign the two addresses to the same > NIC? (though I guess with a switch you may be able to get twice the > throughput with two NICs..) > Actually I do have aliases on each of the interfaces but as you guessed, the two interfaces are there to get more throughput. The machine has a 500 MHz Pentium III processor (actually 4 of them, but I'm just using one for now). Its not possible to saturate the machine with just one 100Mbps interface. I need to have multiple interfaces. > He does have a point however.. ARP packets that are not for the networks > that are on teh receiving NIC could probably be safely discarded without > effecting the way that the system supports the spec. I think it's vague on > this point, and we SEE that other people do similar. I would actually > thinkmthat it would be a security imporovement. > I don't think we should accept cofiguration or routing information from > machines that are not on the right network. > > If I had one net inside a firewall and one outside, I don't want to > recieve ARP packets from the outside that are influencing my internal > routint (arp) table. > > This is not that unsupported.. High availability hosts do this all the > time, and need to. > > My suggestion is that we check incoming arp packets to discard > packets that resolve addresses that are not in a netrange on the interface > into which they came. > > I think this is a good idea anyway for security reasons and we can > dispense with the check against ALL local networks. It might even be > faster. > Thanks for clarifying the specs and supporting my suggestion. I do really need this configuration and all high end server systems that I know use it too. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 14:21:21 1999 Delivered-To: freebsd-net@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 9673A154B2 for ; Sat, 9 Oct 1999 14:21:07 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 64934 invoked by uid 1001); 9 Oct 1999 21:21:00 +0000 (GMT) To: aron@cs.rice.edu Cc: freebsd-net@freebsd.org, justin@apple.com, alc@cs.rice.edu, wollman@khavrinen.lcs.mit.edu Subject: Re: arp errors on machines with two interfaces From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 9 Oct 1999 16:02:57 -0500 (CDT)" References: <199910092102.QAA11299@cs.rice.edu> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 09 Oct 1999 23:20:59 +0200 Message-ID: <64932.939504059@verdi.nethelp.no> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Try to think of it in terms of a traditional coax-based Ethernet, and > > having two NICs on one host connected to the same physical Ethernet > > cable. Would you expect this to work? (You shouldn't.) > > > Well with the traditional Ethernet, it didn't make much sense to connect > multiple interfaces to the same wire - you don't expect both interfaces > together to deliver any more than 10Mbps. However, with switched Ethernet, > both interfaces can deliver the full b/w. So why not get the advantages of > getting this higher b/w as well as full one on one connectivity between > hosts connected to the Ethernet ? - Because getting the advantage of this higher bandwidth requires special support (e.g. Fast Etherchannel or other forms of load balancing/bundling) that FreeBSD doesn't currently have in the standard configuration. It would require considerably more than just removing one error message to support this properly. - Because the error message is a valuable piece of information which tells you the system has detected something that "shouldn't happen", and which most people would indeed consider an error. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 14:37:33 1999 Delivered-To: freebsd-net@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id B1B3214D75 for ; Sat, 9 Oct 1999 14:37:12 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id QAA11776; Sat, 9 Oct 1999 16:37:00 -0500 (CDT) From: Mohit Aron Message-Id: <199910092137.QAA11776@cs.rice.edu> Subject: Re: arp errors on machines with two interfaces To: sthaug@nethelp.no, freebsd-net@freebsd.org, justin@apple.com, alc@cs.rice.edu, wollman@khavrinen.lcs.mit.edu Date: Sat, 9 Oct 1999 16:37:00 -0500 (CDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > - Because getting the advantage of this higher bandwidth requires special > support (e.g. Fast Etherchannel or other forms of load balancing/bundling) > that FreeBSD doesn't currently have in the standard configuration. It > would require considerably more than just removing one error message to > support this properly. > What you're suggesting requires the following: 1) Support in the switch for load-balancing incoming packets to the multiple interfaces on the host (each having the same IP address). 2) OS support for allowing same IP address to be present on multiple interfaces. Why go for the above costly solution when the same effect can simply be achieved by connecting multiple interfaces with different IP addresses with the vanilla OS ? Also as Julian remarked, many high-end servers already use the configuration that I'm using. I'm not aware of any specs that conflict with this configuration either. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 16:17:52 1999 Delivered-To: freebsd-net@freebsd.org Received: from spooky.eis.net.au (spooky.eis.net.au [203.12.171.2]) by hub.freebsd.org (Postfix) with ESMTP id D891B14F79 for ; Sat, 9 Oct 1999 16:17:44 -0700 (PDT) (envelope-from ernie@spooky.eis.net.au) Received: (from ernie@localhost) by spooky.eis.net.au (8.9.3/8.8.3) id JAA18223 for freebsd-net@freebsd.org; Sun, 10 Oct 1999 09:23:05 +1000 (EST) From: Ernie Elu Message-Id: <199910092323.JAA18223@spooky.eis.net.au> Subject: Modem race with Multilink PPP To: freebsd-net@freebsd.org Date: Sun, 10 Oct 1999 09:23:04 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a problem dialing into a 3Com/USR Total control rack using two modems and multilink PPP. When the FreeBSD 3.2-RELEASE system is rebooted both the modems try dialing at once and establish ppp sessions at virtually the same second according to the radius logs, but it does not becom a multilink session. When I force the lines to hang up the next time they dial in multilink PPP works fine. I suspect the fact that they dial in at exactly the same time after a reboot is the source of the problem. Is there a way of making the modems dial say 30 seconds apart? Here is my ppp.conf minus the correct passwords. It's using a Stallion Easyio 8 port board hence the funny device names. - Ernie. default: set log phase chat physical connect set device /dev/cue0 /dev/cue1 set speed 57600 set phone "555-555-555" deny lqr set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT" set login set authname name set authkey "password" set timeout 0 set ifaddr 10.0.0.1/0 10.0.0.2/0 0.0.0.0 0.0.0.0 add default HISADDR set mrru 1500 clone 1,2 link deflink remove link 1,2 set mode ddial To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 17:59:48 1999 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 600AB14E75 for ; Sat, 9 Oct 1999 17:59:46 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id UAA75663; Sat, 9 Oct 1999 20:59:44 -0400 (EDT) (envelope-from wollman) Date: Sat, 9 Oct 1999 20:59:44 -0400 (EDT) From: Garrett Wollman Message-Id: <199910100059.UAA75663@khavrinen.lcs.mit.edu> To: Mohit Aron Cc: freebsd-net@freebsd.org Subject: Re: arp errors on machines with two interfaces In-Reply-To: <199910091650.LAA08261@cs.rice.edu> References: <199910091650.LAA08261@cs.rice.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Actually I am using different subnet addresses on the two interfaces. One is > 128.42.3.77 and the other is 192.168.3.77. There are other machines in the dept > running Solaris and other OS's that are connected in similar fashions. > However, the Ethernet is switched and any broadcast by anyone is going to be > seen by all interfaces connected to it. Aha! Then your switch is broken -- or it's an early generation of the ``vlan'' switches which really didn't support VLANs. You're lucky you're not trying to do multicast over this mess... -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 Sat Oct 9 19:30:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id BF8BD14D46 for ; Sat, 9 Oct 1999 19:30:25 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.2) with ESMTP id VAA72971; Sat, 9 Oct 1999 21:30:18 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Sat, 9 Oct 1999 21:30:17 -0500 (CDT) From: Chris Dillon To: Mohit Aron Cc: sthaug@nethelp.no, freebsd-net@FreeBSD.ORG, justin@apple.com, alc@cs.rice.edu, wollman@khavrinen.lcs.mit.edu Subject: Re: arp errors on machines with two interfaces In-Reply-To: <199910092137.QAA11776@cs.rice.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 9 Oct 1999, Mohit Aron wrote: > > > - Because getting the advantage of this higher bandwidth requires special > > support (e.g. Fast Etherchannel or other forms of load balancing/bundling) > > that FreeBSD doesn't currently have in the standard configuration. It > > would require considerably more than just removing one error message to > > support this properly. > > > > > > What you're suggesting requires the following: > 1) Support in the switch for load-balancing incoming packets to the > multiple interfaces on the host (each having the same IP address). That is assuming you need the extra _incoming_ bandwidth, and not just outgoing. I use load-balanced links on our (cough) NT servers without having to set up anything at the switch. The NIC drivers assign the same MAC address to both (actually, up to 4) NICs. Data can be sent out any of the NICs and the switch will send the data to its proper location, that being the nature of the switch. Seeing the same MAC address on 4 ports, the switch sends incoming data to all four ports. I'm assuming for performance reasons that the NIC drivers ignore incoming data from all but one NIC. This happens to be done with a Intel dual 10/100, with the Compaq drivers (its a Compaq server), which appear to be just slightly modified Intel drivers. The drivers support manual failover, automatic failover, Fast EtherChannel, and "load-balancing without switch support" (which I am using). > 2) OS support for allowing same IP address to be present on multiple > interfaces. Or more precisely, the same MAC address. > Why go for the above costly solution when the same effect can simply be > achieved by connecting multiple interfaces with different IP addresses with the > vanilla OS ? Also as Julian remarked, many high-end servers already use the > configuration that I'm using. I'm not aware of any specs that conflict with > this configuration either. The solution would only be costly in terms of taking the time to actually implement it for FreeBSD. I would actually find it simpler, from an administrative standpoint, to assign one IP address balanced across multiple NICs than to assign multiple IPs to multiple NICs. One IP address also allows for greater bandwidth to a single host for a single transaction whereas the multiple-IP scheme doesn't (for example, you're connected at 4*100, and the other machine is on a gigabit link, and you're FTPing a file over). A question I have is, is this possible with all the different NICs that FreeBSD supports, or just a few different ones (due to hardware limitations)? -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 22:25:52 1999 Delivered-To: freebsd-net@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 9F08014D7F for ; Sat, 9 Oct 1999 22:24:38 -0700 (PDT) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 11aBUL-0002ML-00; Sun, 10 Oct 1999 01:25:41 -0400 To: Mohit Aron Cc: freebsd-net@freebsd.org From: "Gary Palmer" Subject: Re: arp errors on machines with two interfaces In-reply-to: Your message of "Sat, 09 Oct 1999 11:50:51 CDT." <199910091650.LAA08261@cs.rice.edu> Date: Sun, 10 Oct 1999 01:25:38 -0400 Message-ID: <9072.939533138@noop.colo.erols.net> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mohit Aron wrote in message ID <199910091650.LAA08261@cs.rice.edu>: > I don't have control over the hardware. But here's a possibility - > wouldn't it be better if this error message generation in FreeBSD is > turned off if the packet is an arp broadcast ? Like I showed in my > earlier mail, the problem only happens due to arp broadcasts. Turning it off for ARP broadcasts would defeat the purpose of the message, which is to alert the user to a broken network layout, or someone attempting to steal your traffic. I'd much rather you fix your network layout (e.g. by putting the RFC1918 network on a seperate VLAN on the switch) rather than trying to change FreeBSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 22:37:49 1999 Delivered-To: freebsd-net@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id E71A91501E for ; Sat, 9 Oct 1999 22:37:47 -0700 (PDT) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 11aBh4-0002Np-00; Sun, 10 Oct 1999 01:38:50 -0400 To: Garrett Wollman Cc: Mohit Aron , freebsd-net@freebsd.org From: "Gary Palmer" Subject: Re: arp errors on machines with two interfaces In-reply-to: Your message of "Sat, 09 Oct 1999 20:59:44 EDT." <199910100059.UAA75663@khavrinen.lcs.mit.edu> Date: Sun, 10 Oct 1999 01:38:50 -0400 Message-ID: <9164.939533930@noop.colo.erols.net> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Garrett Wollman wrote in message ID <199910100059.UAA75663@khavrinen.lcs.mit.edu>: > > However, the Ethernet is switched and any broadcast by anyone is going to > > be seen by all interfaces connected to it. > Aha! Then your switch is broken -- or it's an early generation of the > ``vlan'' switches which really didn't support VLANs. I don't think he's vlanning the switch at all, just using it as a way of improving the per-connection speed. Its still a flat LAN. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 9 23:26: 8 1999 Delivered-To: freebsd-net@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 9E38615204 for ; Sat, 9 Oct 1999 23:25:37 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id BAA16409; Sun, 10 Oct 1999 01:25:35 -0500 (CDT) From: Mohit Aron Message-Id: <199910100625.BAA16409@cs.rice.edu> Subject: Re: arp errors on machines with two interfaces To: gjp@in-addr.com (Gary Palmer) Date: Sun, 10 Oct 1999 01:25:34 -0500 (CDT) Cc: wollman@khavrinen.lcs.mit.edu, freebsd-net@freebsd.org In-Reply-To: <9164.939533930@noop.colo.erols.net> from "Gary Palmer" at Oct 10, 99 01:38:50 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I don't think he's vlanning the switch at all, just using it as a way > of improving the per-connection speed. Its still a flat LAN. > You're right. I'll see if I can get my sysadmins to create separate VLANs for the multiple interfaces. Surprisingly though, other than this arp error message, I don't experience any other problem with the current configuration. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message