From owner-freebsd-net Sun Oct 10 0:49:39 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 5EA5315104 for ; Sun, 10 Oct 1999 00:49:32 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 70641 invoked by uid 1001); 10 Oct 1999 07:49:31 +0000 (GMT) To: julian@whistle.com 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 From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 9 Oct 1999 14:06:54 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 10 Oct 1999 09:49:31 +0200 Message-ID: <70639.939541771@verdi.nethelp.no> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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. If I had one inside net and one outside net connected to the same switch, and *no* VLAN or segmentation on the switch (due to some kind of switch misconfiguration), I certainly would like FreeBSD to tell me about this misconfiguration - for instance by a suitable ARP error messge. (This is not just theoretical. I've seen organizations buy an expensive firewall, only to connect both the inside and outside nets to the same hub!) 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 Sun Oct 10 4:24:36 1999 Delivered-To: freebsd-net@freebsd.org Received: from monsoon.mail.pipex.net (monsoon.mail.pipex.net [158.43.128.69]) by hub.freebsd.org (Postfix) with SMTP id 106EA15500 for ; Sun, 10 Oct 1999 04:23:55 -0700 (PDT) (envelope-from mik.thwaite@dial.pipex.com) Received: (qmail 16750 invoked from network); 10 Oct 1999 11:23:54 -0000 Received: from userk117.uk.uudial.com (HELO mik) (194.69.100.201) by smtp.dial.pipex.com with SMTP; 10 Oct 1999 11:23:54 -0000 Message-ID: <002601bf1311$483d1e40$4a741cac@SUNDERLAND> From: "Mik Thwaite" To: , Subject: Was : Installing two NICs Date: Sun, 10 Oct 1999 05:35:44 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for the advice, I now have it up and running as a gateway after 3 or 4 kernel rebuilds to get it as right as possible. Turns out the port and irq settings were different to the ones being probed. Cheers, Mik To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 10 6:37: 6 1999 Delivered-To: freebsd-net@freebsd.org Received: from nvision.netvision.com.br (nvision.netvision.com.br [200.215.94.35]) by hub.freebsd.org (Postfix) with ESMTP id C979615044 for ; Sun, 10 Oct 1999 06:36:28 -0700 (PDT) (envelope-from andre@netvision.com.br) Received: from nv12.netvision.com.br ([200.215.95.197]) by nvision.netvision.com.br (Netscape Mail Server v2.02) with SMTP id AAA20429 for ; Sun, 10 Oct 1999 11:35:10 -0200 From: andre@netvision.com.br (Andre Luiz dos Santos) To: freebsd-net@FreeBSD.ORG Subject: Divert Sockets Date: Fri, 8 Oct 1999 10:35:06 -0400 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99100810404704.04076@nv12.netvision.com.br> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. Is there anyway to me know the source MAC address of a packet divert'ed to a divert socket? Like in BPF, where you've the headers of the ethernet packet. If this is not possible, there are anyway to me block an IP packet by their MAC address? Sorry my poor english. Thanks any help! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 10 17:23: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 A66EC1527B for ; Sun, 10 Oct 1999 17:23:56 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id RAA11188; Sun, 10 Oct 1999 17:23:21 -0700 (PDT) From: Archie Cobbs Message-Id: <199910110023.RAA11188@bubba.whistle.com> Subject: Re: arp errors on machines with two interfaces In-Reply-To: <199910090121.VAA68534@khavrinen.lcs.mit.edu> from Garrett Wollman at "Oct 8, 1999 09:21:53 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Sun, 10 Oct 1999 17:23:21 -0700 (PDT) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Garrett Wollman writes: > > 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. Garret, I'd be interested in seeing what references you have that say having two NICs on the same wire (with NON-overlapping net ranges) is somehow broken or illegal or technically incorrect. I had always assumed this was perfectly legal, just like running AppleTalk and TCP/IP on the same wire is perfectly legal. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 10 17:28:28 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 2496D14EDD for ; Sun, 10 Oct 1999 17:28:27 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id RAA11266; Sun, 10 Oct 1999 17:28:21 -0700 (PDT) From: Archie Cobbs Message-Id: <199910110028.RAA11266@bubba.whistle.com> Subject: Re: Divert Sockets In-Reply-To: <99100810404704.04076@nv12.netvision.com.br> from Andre Luiz dos Santos at "Oct 8, 1999 10:35:06 am" To: andre@netvision.com.br (Andre Luiz dos Santos) Date: Sun, 10 Oct 1999 17:28:21 -0700 (PDT) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andre Luiz dos Santos writes: > Is there anyway to me know the source MAC address of a packet divert'ed to a > divert socket? Like in BPF, where you've the headers of the ethernet packet. No. Divert works at the IP layer is not specific to Ethernet, and so doesn't provide any way to get the Ethernet header.. it's already long gone by the time divert sees it anyway. > If this is not possible, there are anyway to me block an IP packet by their > MAC address? Not without a custom kernel hack AFAIK. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 10 17:58:39 1999 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-84.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.84]) by hub.freebsd.org (Postfix) with ESMTP id 0F625155C1 for ; Sun, 10 Oct 1999 17:58:28 -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 BAA00297; Mon, 11 Oct 1999 01:54:52 +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 BAA01324; Mon, 11 Oct 1999 01:46:19 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910110046.BAA01324@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Ernie Elu Cc: freebsd-net@FreeBSD.ORG Subject: Re: Modem race with Multilink PPP In-reply-to: Your message of "Sun, 10 Oct 1999 09:23:04 +1000." <199910092323.JAA18223@spooky.eis.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Oct 1999 01:46:16 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a known problem (well, to me anyway). Ppp will attempt to bind() a local domain socket when MP is established. If bind() fails, it'll try to connect(), otherwise it'll try to listen(). If two processes are doing this at the same time, one bind() succeeds, but the connect() of the failed process happens before the servers listen() and fails :-( You can stagger the connects by changing the last line of your config to link 1 set mode ddial link 2 set mode interactive and then in ppp.linkup: link * set mode ddial Now if someone could tell me how to defeat the above race.... > 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 -- 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 10 18:54:30 1999 Delivered-To: freebsd-net@freebsd.org Received: from mullian.ee.mu.OZ.AU (mullian.ee.mu.OZ.AU [128.250.80.1]) by hub.freebsd.org (Postfix) with ESMTP id 526EB14D8E for ; Sun, 10 Oct 1999 18:54:17 -0700 (PDT) (envelope-from m.summerfield@ee.mu.oz.au) Received: from m-summerfield.ee.mu.oz.au (m-summerfield.ee.mu.OZ.AU [128.250.79.188]) by mullian.ee.mu.OZ.AU (8.9.1a/8.9.1) with SMTP id LAA19461; Mon, 11 Oct 1999 11:53:55 +1000 (EST) Message-Id: <199910110153.LAA19461@mullian.ee.mu.OZ.AU> X-Sender: summer@mullian.ee.mu.oz.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Mon, 11 Oct 1999 11:55:34 +1000 To: Archie Cobbs , wollman@khavrinen.lcs.mit.edu (Garrett Wollman) From: Mark Summerfield Subject: Re: arp errors on machines with two interfaces Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <199910110023.RAA11188@bubba.whistle.com> References: <199910090121.VAA68534@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 17:23 10/10/99 -0700, Archie Cobbs wrote: >Garret, I'd be interested in seeing what references you have that >say having two NICs on the same wire (with NON-overlapping net ranges) >is somehow broken or illegal or technically incorrect. > >I had always assumed this was perfectly legal, just like running >AppleTalk and TCP/IP on the same wire is perfectly legal. AppleTalk and TCP/IP are different protocols -- there's no possibility (in a properly functioning system) that an Ethernet broadcast packet carrying an AppleTalk packet will get passed to the IP stack for processing. However, if you have two interfaces in the same wire, then broadcast packets carrying IP datagrams will be received on both interfaces, and thus passed to the IP stack twice. And in many cases there is no way to determine at that point which interface the broadcast "should" have been received on. This could be resolved by adding appropriate additional information to the IP header. But that information is not provided for, because it is not part of the protocol design. Ipso facto, we conclude that this is not an intended use of IP, since necessary support is not part of the protocol. It's a question of where, when and how multiplexing is done, both between and within protocol suites. You can (presumably) do wacky things like running IP over AppleTalk over Ethernet on the same wire as plain old IP over Ethernet, and there's no problem -- because the multiplexing between the two IP interfaces is resolved by the encapsulation of one in AppleTalk packets. Which perhaps suggests a possible solution for the original question. It might be possible, by using a different encapsulation, to avoid binding an IP address to the second interface altogether -- that should stop it from delivering broadcast packets to the IP stack. How's that PPPoE code coming along?! ;-) Mark ---- Dr. Mark Summerfield Australian Photonics Cooperative Research Centre Photonics Research Laboratory Dept. of Electrical and Electronic Engineering The University of Melbourne Parkville, 3052 AUSTRALIA Phone: +61 3 9344 7419 Fax: +61 3 9344 6678 Email: m.summerfield@ieee.org WWW: http://www.ee.mu.oz.au/staff/summer/index.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 10 20: 6:56 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id E68BF14D35 for ; Sun, 10 Oct 1999 20:06:52 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11aVnV-00072g-00; Sun, 10 Oct 1999 21:06:49 -0600 Message-ID: <380121FF.CB92828A@softweyr.com> Date: Sun, 10 Oct 1999 17:32:15 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mohit Aron Cc: freebsd-net@FreeBSD.ORG, justin@apple.com, Alan Cox , wollman@khavrinen.lcs.mit.edu Subject: Re: arp errors on machines with two interfaces References: <199910091650.LAA08261@cs.rice.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mohit Aron 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. Get a switch that supports Layer 3 VLANs, then the broadcasts from the 192.168 network will not show up on the 128.42 network and vice versa. > 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. Normally you would want to be warned about such things, they are usually a sign of a network misconfiguration. Perhaps a sysctl to turn off these arp warnings would meet your needs? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 10 21:35: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 E5F9114E57 for ; Sun, 10 Oct 1999 21:35:11 -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 VAA81760; Sun, 10 Oct 1999 21:30:35 -0700 (PDT) Date: Sun, 10 Oct 1999 21:30:35 -0700 (PDT) From: Julian Elischer To: Mark Summerfield Cc: Archie Cobbs , Garrett Wollman , freebsd-net@FreeBSD.ORG Subject: Re: arp errors on machines with two interfaces In-Reply-To: <199910110153.LAA19461@mullian.ee.mu.OZ.AU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 11 Oct 1999, Mark Summerfield wrote: > > binding an IP address to the second interface altogether -- that should > stop it from delivering broadcast packets to the IP stack. How's that > PPPoE code coming along?! ;-) NEarly all of the pppoe node itself is completed I'm just adding finishin gtouches.. after that we need to kook the ppp daemon intoo it which is a separate task.. in the meanwhile I will have code that can be tested (but not go into ppp sometime tonight if I don't get sucked into a reallyinteresting TV show tonight. 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 11 8:56: 5 1999 Delivered-To: freebsd-net@freebsd.org Received: from intrepid.cameron.edu (intrepid.cameron.edu [164.58.112.171]) by hub.freebsd.org (Postfix) with ESMTP id AB6F3154EB for ; Mon, 11 Oct 1999 08:55:59 -0700 (PDT) (envelope-from jbeley@intrepid.cameron.edu) Received: (from jbeley@localhost) by intrepid.cameron.edu (8.9.3/8.9.3/Debian/GNU) id KAA05692 for freebsd-net@freebsd.org; Mon, 11 Oct 1999 10:55:55 -0500 Date: Mon, 11 Oct 1999 10:55:55 -0500 From: Jeff Beley To: freebsd-net@freebsd.org Subject: NAT on a bridge Message-ID: <19991011105555.A5341@jeffb> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre3i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a FreeBSD bridge between my router and my network and was wondering if I can do network address translation(transparent proxy) on my bridge. --Jeff -- we embrace technology, we learn from it, we use it, and we exploit it. technology is a very powerful tool, as is knowledge, but some people go beyond these boundaries, testing limits, finding new ways and ideas... we call these people hackers. PGP Key ID 0xF0DE9044 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 11 11:48:31 1999 Delivered-To: freebsd-net@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 4A6211565C for ; Mon, 11 Oct 1999 11:47:17 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpx22.lx.ehu.es [158.227.99.22]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id UAA00860 for ; Mon, 11 Oct 1999 20:47:13 +0200 (MET DST) Message-ID: <380230AB.BF7A96C5@we.lc.ehu.es> Date: Mon, 11 Oct 1999 20:47:07 +0200 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dept. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.6 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: freebsd-net@FreeBSD.org Subject: problem with multicast routing, PPP, and shared subnets Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I am doing some experiments with IP multicast. In particular, I am interested in "multicast@home", i.e., bringing IP multicast services to home PCs connected to our LAN with PPP. I set up a FreeBSD (3.3-RELEASE) PPP server, which has MROUTING configured and runs mrouted. The addresses assigned to the PPP clients belong to our LAN's IP subnet, and routing is solved with proxy ARP. When any PPP client adds (or deletes) itself to a multicast group, the membership information is sent through the "tun" interface to the server/router. However, a "netstat -g" shows that these group memberships are associated to the VIF 0 (ethernet) rather than to the VIF 1 (tun), as they would be: Virtual Interface Table Vif Thresh Rate Local-Address Remote-Address Pkts-In Pkts-Out 0 1 0 157.228.6.111 0 0 1 1 0 192.168.6.111 0 0 Multicast Forwarding Cache Origin Group Packets In-Vif Out-Vifs:Ttls 157.228.6.224 224.2.230.125 0 0 <---- BAD 157.228.6.224 224.2.127.254 0 0 <---- BAD (The server's ethernet interface IP address is 157.228.6.111. The PPP client I am using in this example has the IP address 157.228.6.224; the local address of the "tun" point-to-point interface is 192.168.6.111.) Obviously, that multicast forwarding table is wrong, and the consequence is that multicast forwarding does not work. I think that this problem is related to the IP subnet sharing I mentioned above, so that I reconfigured the PPP server in order to use a different subnet: then, MC forwarding worked fine. But I do not want to use another IP subnet for the PPP clients. Anyway, I think that multicast forwarding _should_ work even with the LAN and the PPP clients sharing the same subnet. I read the mrouted(8) man page and I tried a "phyint tun0 netmask 32" to no avail... Am I doing anything wrong? If the cause is a bug I will fill a PR. BTW, I have another problem: mrouted detects the multicast-capable interfaces at startup, and it does not notice when other interfaces go up or down. This behavior is not appropriate for PPP connections, because the "tun" devices go up when a connection is opened (the ppp process is started), and down when it is closed (ppp terminates). I could send a SIGHUP to mrouted whenever a PPP connection is established, but this would flush the multicast forwarding cache. Please accept my apologies for this long message. Saludos, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.ORG Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Keyboard not present -- Press F1 to resume" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 11 17:18:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 34DBE14A2C for ; Mon, 11 Oct 1999 17:18:37 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id UAA13277; Mon, 11 Oct 1999 20:18:01 -0400 (EDT) Message-ID: <19991011201800.A11154@netmonger.net> Date: Mon, 11 Oct 1999 20:18:01 -0400 From: Christopher Masto To: Brian Somers , Ernie Elu Cc: freebsd-net@FreeBSD.ORG Subject: Re: Modem race with Multilink PPP Mail-Followup-To: Brian Somers , Ernie Elu , freebsd-net@FreeBSD.ORG References: <199910092323.JAA18223@spooky.eis.net.au> <199910110046.BAA01324@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=envbJBWh7q8WU6mo X-Mailer: Mutt 0.91.1i In-Reply-To: <199910110046.BAA01324@hak.lan.Awfulhak.org>; from Brian Somers on Mon, Oct 11, 1999 at 01:46:16AM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii On Mon, Oct 11, 1999 at 01:46:16AM +0100, Brian Somers wrote: > This is a known problem (well, to me anyway). > > Ppp will attempt to bind() a local domain socket when MP is > established. If bind() fails, it'll try to connect(), otherwise > it'll try to listen(). If two processes are doing this at the same > time, one bind() succeeds, but the connect() of the failed process > happens before the servers listen() and fails :-( IDKWITA, but from experimentation, the connect() should block for a while and succeed shortly after the other process calls listen(). -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="sock_race.pl" #!/usr/local/bin/perl -w use IO::Socket; use strict; fork ? &parent : &child; sub parent { print "P $$: parent\n"; my $proto = getprotobyname('tcp'); my $s = new IO::Socket; $s->socket(AF_INET, SOCK_STREAM, $proto) or die "P $$: socket: $!"; $s->bind(pack_sockaddr_in(7890, INADDR_ANY)) or die "P $$: bind: $!"; print "P $$: waiting..\n"; sleep 5; print "P $$: listening.\n"; $s->listen(5); print "P $$: waiting..\n"; sleep 30; print "P $$: done\n"; } sub child { print "C $$: child\n"; sleep 1; print "C $$: connecting..\n"; my $c = new IO::Socket::INET(Proto => "tcp", PeerAddr => "localhost:7890") or die "C $$: connect: $!"; print "C $$: done.\n"; } --envbJBWh7q8WU6mo-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 11 23:18:31 1999 Delivered-To: freebsd-net@freebsd.org Received: from jason.argos.org (a1-3a123.neo.rr.com [24.93.180.123]) by hub.freebsd.org (Postfix) with ESMTP id 6D0A714E6A for ; Mon, 11 Oct 1999 23:18:29 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA15661; Tue, 12 Oct 1999 02:17:44 -0400 Date: Tue, 12 Oct 1999 02:17:44 -0400 (EDT) From: Mike Nowlin To: Mark Summerfield Cc: Archie Cobbs , Garrett Wollman , freebsd-net@FreeBSD.ORG Subject: Re: arp errors on machines with two interfaces In-Reply-To: <199910110153.LAA19461@mullian.ee.mu.OZ.AU> 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 > At 17:23 10/10/99 -0700, Archie Cobbs wrote: > >Garret, I'd be interested in seeing what references you have that > >say having two NICs on the same wire (with NON-overlapping net ranges) > >is somehow broken or illegal or technically incorrect. > > > >I had always assumed this was perfectly legal, just like running > >AppleTalk and TCP/IP on the same wire is perfectly legal. > I ran into this problem (actually, I'm still dealing with it) a few years ago when we got a dedicated Internet line at work... When the network was first set up, we used 192.168.2.0/24 addresses for everything. With the new IP block from the ISP, we then had 208.132.36.128/25, which I started working into the network... Due to some problems with our application software (hard-coded IP addresses that would have cost $1000's to change), we couldn't switch about 50% of the equipment to the new IP block... Turns out that some of the machines had two IP addresses assigned to them, and some of those ended up getting a second ethernet card - one for 192, one for 208. Aside from a few headaches caused by having to manually do the routing tables on all the machines, everything was OK until we started putting some WAN routing equipment in that used RIP with routing info that changed every time one of our remote LANs connected -- life suddenly got complicated. The routing tables would suddenly clear out, then build back up again, then empty out again. Sometimes they would build up correct info, sometimes not... An address/netmask combination basically refers to the addresses that a certain machine can talk directly to in a single hop. When you start mixing different combinations on a shared ethernet, RIP (and probably other routing protocols) get really confused -- they hear two different broadcasts that are essentially contradicting themseleves. Your results will vary depending on what version/release of the protocol you're running on -- our DEC UNIX boxes ended up setting the ethernet cards to something like 192.168.2.4/0, which made them completely lose track of the 208 address, and the default gateway, and the Linux boxes did something similar. The FreeBSD boxes started reporting messages like: arp: 208.132.36.174 moved from 00:00:c0:0b:01:81 to 00:40:05:1e:df:19 on ed1 arp: 208.132.36.174 moved from 00:40:05:1e:df:19 to 00:00:c0:0b:01:81 on ed1 arplookup 192.168.2.15 failed: host is not on local network (just happened to have that saved).... I finally figured out a way to make everything work, as long as our ISP line didn't go down - the DNS box started throwing fits if that happened..... With the installation of some new systems (Y2K fixes), I had the opportunity to fix a lot of these problems.... I "worked" a couple 40- and 24-port HP intelligent switches into the purchase orders, along with some new wiring. Between the VLAN capability of the switches and the extra wiring, we've fixed about 95% of the problems. Things are pretty much back to normal as far as the standards go, and none of the 192 (or the new 10.x.0.0/16 addresses) can hear the 208 machines, and RIP is now working fine. The only reason it's working now is that there are logically three ethernets - 208, 192, and 10 (which goes to another router to break it down into 10.0.0.0/24 chunks). Long winded, I know -- but you wanted an example... --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 11 23:53: 6 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 D60A614A2F for ; Mon, 11 Oct 1999 23:53:02 -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 HAA88948; Tue, 12 Oct 1999 07:52:46 +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 HAA00670; Tue, 12 Oct 1999 07:20:47 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910120620.HAA00670@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Masto , freebsd-net@FreeBSD.ORG Cc: Brian Somers , Ernie Elu Subject: Re: Modem race with Multilink PPP - what does POSIX say ? In-reply-to: Your message of "Mon, 11 Oct 1999 20:18:01 EDT." <19991011201800.A11154@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Oct 1999 07:20:47 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Mon, Oct 11, 1999 at 01:46:16AM +0100, Brian Somers wrote: > > This is a known problem (well, to me anyway). > > > > Ppp will attempt to bind() a local domain socket when MP is > > established. If bind() fails, it'll try to connect(), otherwise > > it'll try to listen(). If two processes are doing this at the same > > time, one bind() succeeds, but the connect() of the failed process > > happens before the servers listen() and fails :-( > > IDKWITA, but from experimentation, the connect() should block for a > while and succeed shortly after the other process calls listen(). > -- > Christopher Masto Senior Network Monkey NetMonger Communications > chris@netmonger.net info@netmonger.net http://www.netmonger.net > > Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ [.....] All very well, but in ppp(8)s case, this means that I need a new datalink state in between lcp and open so that I can go off and deal with more urgent things.... This is non-trivial and a PITA. It's also pretty cruddy and unreliable IMHO. The real way forward would be to have a different errno coming back from connect() - something like EAGAIN rather ECONREFUSED when the socket is bound but not listening. This would be a double bonus because I'd then be able to identify stale local domain sockets. Anybody know what POSIX says on along these lines ? Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 1:21: 6 1999 Delivered-To: freebsd-net@freebsd.org Received: from hotmail.com (f295.hotmail.com [207.82.251.186]) by hub.freebsd.org (Postfix) with SMTP id B8CC415ABB for ; Tue, 12 Oct 1999 01:21:02 -0700 (PDT) (envelope-from hmoghadam@hotmail.com) Received: (qmail 25557 invoked by uid 0); 12 Oct 1999 08:21:01 -0000 Message-ID: <19991012082101.25555.qmail@hotmail.com> Received: from 195.200.226.109 by www.hotmail.com with HTTP; Tue, 12 Oct 1999 01:21:01 PDT X-Originating-IP: [195.200.226.109] From: "Hamid Moghadam" To: freebsd-net@freebsd.org Subject: 3C509B support ? Date: Tue, 12 Oct 1999 01:21:01 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all Does anyone know weather 3.2R supports 3Com 3C509B 16 bit ethernet card or not and is it a FBSD friendly card ? Thanks a lot - HM ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.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 12 2:23:50 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpham.uni-mb.si (alpham.uni-mb.si [164.8.1.101]) by hub.freebsd.org (Postfix) with ESMTP id D375E14F57 for ; Tue, 12 Oct 1999 02:23:46 -0700 (PDT) (envelope-from vrtin@uni-mb.si) Received: from gea.uni-mb.si by alpham.uni-mb.si (PMDF V5.1-12 #7554) with ESMTP id <01JH1N5SHJ6M0035VQ@alpham.uni-mb.si> for freebsd-net@freebsd.org; Tue, 12 Oct 1999 11:23:44 MET Received: from localhost (david@localhost) by gea.uni-mb.si (8.9.3/8.9.3/19990328) with SMTP id LAA00491 for ; Tue, 12 Oct 1999 11:23:44 +0200 (CEST) Date: Tue, 12 Oct 1999 11:23:42 +0200 (CEST) From: David Vrtin Subject: UCD-SNMP: kvm_read(*, 2, 0xbfbfb1e8, 96) = 0: kvm_read: Bad address To: freebsd-net@freebsd.org Reply-To: David Vrtin Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-No-Archive: Yes Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello I have 3.3-STABLE FreeBSD (cvsup 5. oct 1999 12:00) and UCD-SNMP version 4.0.1. After "# snmpwalk -v 1 localhost ro-blahblehblih" is in snmpd.log: UCD-SNMP version 4.0.1 Reconfiguring daemon kvm_read(*, 2, 0xbfbfb1e8, 96) = 0: kvm_read: Bad address TCP_Count_Connections - inpcb: Bad address Bad address?? Anything else is ok. My snmpd.conf is: syslocation University of Maribor, Faculty of EE and CS, Slovenia syscontact e-mail: admin@um.ieee.si com2sec public localhost ro-blahblehblih com2sec private localhost rw-tralalilalal group public any public group private any private view all included .1 80 access public "" any noauth 0 all none none access private "" any noauth 0 all all none Any idea? Best regards, David -- David Vrtin (system manager) # tel: +386 62 220-7129 University of Maribor, Faculty of EE and CS # fax: +386 62 211-178 Smetanova 17, SI-2000 Maribor, Slovenia # www.uni-mb.si/~david/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 2:56:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from hotmail.com (f39.hotmail.com [207.82.250.50]) by hub.freebsd.org (Postfix) with SMTP id 5D2C214C9B for ; Tue, 12 Oct 1999 02:56:53 -0700 (PDT) (envelope-from hmoghadam@hotmail.com) Received: (qmail 43537 invoked by uid 0); 12 Oct 1999 09:56:52 -0000 Message-ID: <19991012095652.43536.qmail@hotmail.com> Received: from 195.200.226.109 by www.hotmail.com with HTTP; Tue, 12 Oct 1999 02:56:51 PDT X-Originating-IP: [195.200.226.109] From: "Hamid Moghadam" To: freebsd-net@freebsd.org Subject: Re: 3C509B support ? Date: Tue, 12 Oct 1999 02:56:51 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have just read 3.2 release notes, it said that it is buggy ! I didn't understand that the card is buggy or the driver. >From: "D.M.P." >To: Hamid Moghadam >Subject: Re: 3C509B support ? >Date: Tue, 12 Oct 1999 02:48:50 -0700 > >Hamid Moghadam wrote: > > > > Does anyone know weather 3.2R supports 3Com 3C509B 16 bit ethernet card >or > > not and is it a FBSD friendly card ? > >Yes, using the ep driver. It works very well. In fact, the firewall >box sitting right next to me (the through which this email was sent) >uses a pair of 3c509 cards. Make sure you read the man page first, >there's some important info you need to know. > >-- >"Nothing is more noble, nothing more venerable than fidelity. Truth >and faithfulness are the most sacred excellences and endowments of >the human mind." -- Cicero > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.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 12 4:54:17 1999 Delivered-To: freebsd-net@freebsd.org Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6]) by hub.freebsd.org (Postfix) with ESMTP id 50E4A14C38 for ; Tue, 12 Oct 1999 04:54:13 -0700 (PDT) (envelope-from kazu@iijlab.net) Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8]) by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id UAA02820 for ; Tue, 12 Oct 1999 20:54:11 +0900 (JST) Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id UAA11725 for ; Tue, 12 Oct 1999 20:54:11 +0900 (JST) Received: from localhost (mine.iij.ad.jp [192.168.10.205]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id UAA16232 for ; Tue, 12 Oct 1999 20:54:11 +0900 (JST) To: net@FreeBSD.ORG Subject: KAME stable package 19991012 From: core@kame.net X-Mailer: Mew version 1.95b1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991012205302F.kazu@iijlab.net> Date: Tue, 12 Oct 1999 20:53:02 +0900 X-Dispatcher: imput version 991007(IM132) Lines: 17 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As usual, KAME Project has released "stable" packages of IPv6/IPsec network code for FreeBSD 2.2.8/3.2, NetBSD 1.4.1, and BSD/OS 3.1. These packages have been tested by the TAHI team(http://www.tahi.org). They are free of charge but absolutely no warranty. They are avaiable from the following web site: http://www.kame.net/ NOTE: IF YOU GAIN ACCESS TO THIS WEB PAGE OVER IPv6, THE TURTLE WILL DANCE. To know the changes from the previous stable package, please refer to the CHANGELOG file. --KAME Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 6: 3:25 1999 Delivered-To: freebsd-net@freebsd.org Received: from online.no (pilt-s.online.no [148.122.208.18]) by hub.freebsd.org (Postfix) with ESMTP id B0BE814CB9 for ; Tue, 12 Oct 1999 06:03:23 -0700 (PDT) (envelope-from osl@nextel.no) Received: from gspot (gspot.nextel.no [148.122.201.51]) by online.no (8.9.3/8.9.1) with SMTP id PAA20510 for ; Tue, 12 Oct 1999 15:03:22 +0200 (MET DST) From: =?iso-8859-1?Q?Olaf_S_L=F8ken?= To: Subject: subscribe freebsd-net Date: Tue, 12 Oct 1999 14:09:14 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 7: 2: 9 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 88DE614E94 for ; Tue, 12 Oct 1999 07:02:05 -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 KAA90595; Tue, 12 Oct 1999 10:01:59 -0400 (EDT) (envelope-from wollman) Date: Tue, 12 Oct 1999 10:01:59 -0400 (EDT) From: Garrett Wollman Message-Id: <199910121401.KAA90595@khavrinen.lcs.mit.edu> To: David Vrtin Cc: freebsd-net@FreeBSD.ORG Subject: UCD-SNMP: kvm_read(*, 2, 0xbfbfb1e8, 96) = 0: kvm_read: Bad address In-Reply-To: References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Hello > I have 3.3-STABLE FreeBSD (cvsup 5. oct 1999 12:00) and UCD-SNMP version 4.0.1. > After "# snmpwalk -v 1 localhost ro-blahblehblih" is in snmpd.log: > UCD-SNMP version 4.0.1 > Reconfiguring daemon > kvm_read(*, 2, 0xbfbfb1e8, 96) = 0: kvm_read: Bad address > TCP_Count_Connections - inpcb: Bad address > Bad address?? That indicates that the SNMP agent doesn't know how to correctly extract TCP connection information from the kernel. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 7:35: 6 1999 Delivered-To: freebsd-net@freebsd.org Received: from etek.chalmers.se (quarl0.etek.chalmers.se [129.16.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 27C1C15752 for ; Tue, 12 Oct 1999 07:34:52 -0700 (PDT) (envelope-from em8jaci@etek.chalmers.se) Received: from jaci.rotary.studenthem.gu.se (nat.studenthem.gu.se [193.10.163.20]) by etek.chalmers.se (8.8.8/8.8.8) with ESMTP id QAA13694 for ; Tue, 12 Oct 1999 16:34:11 +0200 (MET DST) X-Authentication-Warning: quarl0.etek.chalmers.se: Host nat.studenthem.gu.se [193.10.163.20] claimed to be jaci.rotary.studenthem.gu.se Date: Tue, 12 Oct 1999 16:28:45 +0200 From: Jacopo Pecci X-Mailer: The Bat! (v1.36) S/N 6B091D52 / Educational Reply-To: Jacopo Pecci X-Priority: 3 (Normal) Message-ID: <8686.991012@etek.chalmers.se> To: net@freebsd.org Subject: delayed ACKs 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 According to what I have studied, delayed ACKs can be sent: (1)every 200 ms (2)when I have data to send (piggyback packet) (3)every second packet so I don't understand why in the example below, there are ACKs that acknowledge up to 7 segments. (in the example I have just sent 50 segments of 1460 bytes from the client to the server) 15:58:26.565899 172.20.1.15.1034 > 172.20.2.15.1111: S 1085244744:1085244744(0) win 16384 (DF) 15:58:26.566236 172.20.2.15.1111 > 172.20.1.15.1034: S 242000411:242000411(0) ack 1085244745 win 17520 (DF) 15:58:26.566438 172.20.1.15.1034 > 172.20.2.15.1111: . ack 1 win 17520 (DF) 15:58:26.662625 172.20.1.15.1034 > 172.20.2.15.1111: . 1:1461(1460) ack 1 win 17520 (DF) 15:58:26.781386 172.20.2.15.1111 > 172.20.1.15.1034: . ack 1461 win 17520 (DF) ^^^^^^^ 15:58:26.782287 172.20.1.15.1034 > 172.20.2.15.1111: . 1461:2921(1460) ack 1 win 17520 (DF) 15:58:26.783086 172.20.1.15.1034 > 172.20.2.15.1111: . 2921:4381(1460) ack 1 win 17520 (DF) 15:58:26.784675 172.20.2.15.1111 > 172.20.1.15.1034: . ack 4381 win 17520 (DF) ^^^^^^^^^ 15:58:26.785521 172.20.1.15.1034 > 172.20.2.15.1111: . 4381:5841(1460) ack 1 win 17520 (DF) 15:58:26.786299 172.20.1.15.1034 > 172.20.2.15.1111: . 5841:7301(1460) ack 1 win 17520 (DF) 15:58:26.787074 172.20.1.15.1034 > 172.20.2.15.1111: . 7301:8761(1460) ack 1 win 17520 (DF) 15:58:26.788639 172.20.2.15.1111 > 172.20.1.15.1034: . ack 7301 win 17520 (DF) ^^^^^^^^^^^ 15:58:26.789477 172.20.1.15.1034 > 172.20.2.15.1111: . 8761:10221(1460) ack 1 win 17520 (DF) 15:58:26.790255 172.20.1.15.1034 > 172.20.2.15.1111: . 10221:11681(1460) ack 1 win 17520 (DF) 15:58:26.791029 172.20.1.15.1034 > 172.20.2.15.1111: . 11681:13141(1460) ack 1 win 17520 (DF) 15:58:26.792614 172.20.2.15.1111 > 172.20.1.15.1034: . ack 10221 win 17520 (DF) ....... ^^^^^^^^^^^ according with point (3) each ACK acknowledges 2 packets but later.... 15:58:26.793455 172.20.1.15.1034 > 172.20.2.15.1111: . 13141:14601(1460) ack 1 win 17520 (DF) 15:58:26.794232 172.20.1.15.1034 > 172.20.2.15.1111: . 14601:16061(1460) ack 1 win 17520 (DF) 15:58:26.795007 172.20.1.15.1034 > 172.20.2.15.1111: . 16061:17521(1460) ack 1 win 17520 (DF) 15:58:26.796695 172.20.2.15.1111 > 172.20.1.15.1034: . ack 13141 win 17520 (DF) 15:58:26.796750 172.20.2.15.1111 > 172.20.1.15.1034: . ack 16061 win 17520 (DF) ^^^^^^^^^^^ 15:58:26.797580 172.20.1.15.1034 > 172.20.2.15.1111: . 17521:18981(1460) ack 1 win 17520 (DF) 15:58:26.798349 172.20.1.15.1034 > 172.20.2.15.1111: . 18981:20441(1460) ack 1 win 17520 (DF) 15:58:26.799119 172.20.1.15.1034 > 172.20.2.15.1111: . 20441:21901(1460) ack 1 win 17520 (DF) 15:58:26.800083 172.20.1.15.1034 > 172.20.2.15.1111: . 21901:23361(1460) ack 1 win 17520 (DF) 15:58:26.801295 172.20.1.15.1034 > 172.20.2.15.1111: . 23361:24821(1460) ack 1 win 17520 (DF) 15:58:26.802540 172.20.1.15.1034 > 172.20.2.15.1111: . 24821:26281(1460) ack 1 win 17520 (DF) 15:58:26.865477 172.20.2.15.1111 > 172.20.1.15.1034: . ack 26281 win 10372 (DF) ^^^^^^^^^^ 15:58:26.866343 172.20.1.15.1034 > 172.20.2.15.1111: . 26281:27741(1460) ack 1 win 17520 (DF) 15:58:26.867117 172.20.1.15.1034 > 172.20.2.15.1111: . 27741:29201(1460) ack 1 win 17520 (DF) 15:58:26.867886 172.20.1.15.1034 > 172.20.2.15.1111: . 29201:30661(1460) ack 1 win 17520 (DF) 15:58:26.868837 172.20.1.15.1034 > 172.20.2.15.1111: . 30661:32121(1460) ack 1 win 17520 (DF) 15:58:26.870080 172.20.1.15.1034 > 172.20.2.15.1111: P 32121:33581(1460) ack 1 win 17520 (DF) 15:58:26.871290 172.20.1.15.1034 > 172.20.2.15.1111: . 33581:35041(1460) ack 1 win 17520 (DF) 15:58:26.872534 172.20.1.15.1034 > 172.20.2.15.1111: . 35041:36501(1460) ack 1 win 17520 (DF) 15:58:26.928674 172.20.2.15.1111 > 172.20.1.15.1034: . ack 36501 win 3224 (DF) ^^^^^^^^^^^^ 15:58:26.928732 172.20.2.15.1111 > 172.20.1.15.1034: . ack 36501 win 6296 (DF) ... it acknowledges first 16061 and then 26281 (7 segments) thanks /jaci To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 7:48: 8 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 96C1915772 for ; Tue, 12 Oct 1999 07:48:03 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11b3De-0006Yk-00; Tue, 12 Oct 1999 08:48:03 -0600 Message-ID: <38034A21.B908DBAC@softweyr.com> Date: Tue, 12 Oct 1999 08:48:01 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Hamid Moghadam Cc: freebsd-net@FreeBSD.ORG Subject: Re: 3C509B support ? References: <19991012095652.43536.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hamid Moghadam wrote: > > I have just read 3.2 release notes, it said that it is buggy ! > I didn't understand that the card is buggy or the driver. Yes. 3.3 supports the 905, 905B, and 905C. Despite the 3Com advertising campaign, they're not the best cards in the world, but should work adequately. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 8: 9:36 1999 Delivered-To: freebsd-net@freebsd.org Received: from entic.net (shell.entic.net [209.157.122.66]) by hub.freebsd.org (Postfix) with SMTP id 602221585E for ; Tue, 12 Oct 1999 08:09:33 -0700 (PDT) (envelope-from aj@entic.net) Received: (qmail 24100 invoked by uid 1000); 12 Oct 1999 15:07:40 -0000 Date: Tue, 12 Oct 1999 08:07:39 -0700 (PDT) From: Anil Jangity To: Hamid Moghadam Cc: freebsd-net@freebsd.org Subject: Re: 3C509B support ? In-Reply-To: <19991012082101.25555.qmail@hotmail.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 Hamid: Next time do some research on the freebsd web site before posting such questions: ftp.freebsd.org/pub/FreeBSD/releases/i386/3.2-RELEASE/RELNOTES.TXT. Look at section 2 (Supported Configurations). I don't think that FTP worked for me, so you can take a look at the 2.2.8 RELNOTES. If its in there it will work in 3.2 as well. But just to answer you question yes 3.2 does support the 5x9s. On Tue, 12 Oct 1999, Hamid Moghadam wrote: |Hi all | |Does anyone know weather 3.2R supports 3Com 3C509B 16 bit ethernet card or |not and is it a FBSD friendly card ? | | |Thanks a lot |- HM | |______________________________________________________ |Get Your Private, Free Email at http://www.hotmail.com | | |To Unsubscribe: send mail to majordomo@FreeBSD.org |with "unsubscribe freebsd-net" in the body of the message | Kind regards, Anil Jangity aj@entic.net "Work like you don't need money, love like you've never been hurt, and dance like no one's watching." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 8:27:54 1999 Delivered-To: freebsd-net@freebsd.org Received: from guppy.pond.net (guppy.pond.net [205.240.25.2]) by hub.freebsd.org (Postfix) with ESMTP id 2E99014E35 for ; Tue, 12 Oct 1999 08:27:37 -0700 (PDT) (envelope-from gryph@mindless.com) Received: from mindless.com (snapuser2-89.pacificcrest.net [216.36.34.89]) by guppy.pond.net (8.9.3/8.9.3) with ESMTP id IAA15368; Tue, 12 Oct 1999 08:21:32 -0700 (PDT) Message-ID: <38035366.DC8E4910@mindless.com> Date: Tue, 12 Oct 1999 08:27:34 -0700 From: "D.M.P." Organization: dmp@aracnet.com X-Mailer: Mozilla 4.6 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Hamid Moghadam Cc: freebsd-net@FreeBSD.ORG Subject: Re: 3C509B support ? References: <19991012095652.43536.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hamid Moghadam wrote: > > I have just read 3.2 release notes, it said that it is buggy ! > I didn't understand that the card is buggy or the driver. In the dozen or or so FreeBSD boxes I've built using 3c509's, I haven't had any problems with the driver or the card. > >Hamid Moghadam wrote: > > > > > > Does anyone know weather 3.2R supports 3Com 3C509B 16 bit ethernet card or > > > not and is it a FBSD friendly card ? > > > >Yes, using the ep driver. It works very well. In fact, the firewall > >box sitting right next to me (the through which this email was sent) > >uses a pair of 3c509 cards. Make sure you read the man page first, > >there's some important info you need to know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 8:51:29 1999 Delivered-To: freebsd-net@freebsd.org Received: from thelab.hub.org (nat203.183.mpoweredpc.net [142.177.203.183]) by hub.freebsd.org (Postfix) with ESMTP id 5B4A714E35 for ; Tue, 12 Oct 1999 08:51:24 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id MAA92811; Tue, 12 Oct 1999 12:48:41 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 12 Oct 1999 12:48:37 -0300 (ADT) From: The Hermit Hacker To: "D.M.P." Cc: Hamid Moghadam , freebsd-net@FreeBSD.ORG Subject: Re: 3C509B support ? In-Reply-To: <38035366.DC8E4910@mindless.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm running 3.3-STABLE on a box at the office, with the following card detected: xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x24 int a irq 9 on pci0.20.0 xl0: Ethernet address: 00:10:4b:69:5c:64 xl0: autoneg complete, link status good (half-duplex, 10Mbps) And have the following messages popping up fairly frequently: xl0: command never completed! xl0: command never completed! xl0: command never completed! xl0: command never completed! I haven' tworried too much abuot them, since it hasn't noticeably affected performance, I don't think...anyone want to comment on these, since the thread is going? On Tue, 12 Oct 1999, D.M.P. wrote: > Hamid Moghadam wrote: > > > > I have just read 3.2 release notes, it said that it is buggy ! > > I didn't understand that the card is buggy or the driver. > > In the dozen or or so FreeBSD boxes I've built using 3c509's, I > haven't had any problems with the driver or the card. > > > >Hamid Moghadam wrote: > > > > > > > > Does anyone know weather 3.2R supports 3Com 3C509B 16 bit ethernet card or > > > > not and is it a FBSD friendly card ? > > > > > >Yes, using the ep driver. It works very well. In fact, the firewall > > >box sitting right next to me (the through which this email was sent) > > >uses a pair of 3c509 cards. Make sure you read the man page first, > > >there's some important info you need to know. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 8:52:49 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 91421151B5; Tue, 12 Oct 1999 08:52:42 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id KAA16014; Tue, 12 Oct 1999 10:52:38 -0500 (CDT) From: Mohit Aron Message-Id: <199910121552.KAA16014@cs.rice.edu> Subject: paper on fine-grained OS timers To: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org, tech-net@netbsd.org Date: Tue, 12 Oct 1999 10:52:38 -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 Hi, I'd like to tell the BSD community about my paper entitled "Soft timers: efficient microsecond software timer support for network processing" that's going to appear in SOSP 1999. The abstract for the paper is attached below. The gzip'd postcript for the paper can be downloaded from: http://www.cs.rice.edu/~aron/papers/soft-timers.ps.gz Thanks, - Mohit Abstract: This paper proposes and evaluates soft timers, a new operating system facility that allows the efficient scheduling of software events at a granularity down to tens of microseconds. Soft timers can be used to avoid interrupts and reduce context switches associated with network processing without sacrificing low communication delays. More specifically, soft timers enable transport protocols like TCP to efficiently perform rate-based clocking of packet transmissions. Experiments show that rate-based clocking can improve HTTP response time over connections with high bandwidth-delay products by up to 89% and that soft timers allow a server to employ rate-based clocking with little CPU overhead (2--6%) at high aggregate bandwidths. Soft timers can also be used to perform network polling, which eliminates network interrupts and increases the memory access locality of the network subsystem without sacrificing delay. Experiments show that this technique can improve the throughput of a Web server by up to 25%. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 9:33: 8 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 9BB5414C98 for ; Tue, 12 Oct 1999 09:33:01 -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 SAA18460 for ; Tue, 12 Oct 1999 18:32:57 +0200 (MET DST) Received: (from livensw@localhost) by btmq9s.rc.bel.alcatel.be (8.8.8+Sun/8.8.8) id SAA05660 for freebsd-net@freebsd.org; Tue, 12 Oct 1999 18:33:49 +0200 (MET DST) Date: Tue, 12 Oct 1999 18:33:49 +0200 From: Wim Livens To: freebsd-net@freebsd.org Subject: Why copying data is needed for forwarding IP packets ? Message-ID: <19991012183349.D7794@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 In Stevens' volume II book, the following is mentioned: "Two operations dominate the time required to process packets: copying data end computing checksums." (section 8.7, p. 234). What is meant exactly by copying data here ? Am I correct in saying that to forward a packet received on one interface and send it out on another interface, the packet is stored in host memory by the first interface card, then some fields are modified, and then the second interface card reads the packet from host memory and send it out on the wire (maybe using some buffering on the card) ? Or is the data copied from host memory to host memory somewhere ? Does the same hold for multicast ? Thanks for any clarification, -- 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 Tue Oct 12 11: 9: 3 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 33A90152DF for ; Tue, 12 Oct 1999 11:09:00 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id NAA19953; Tue, 12 Oct 1999 13:08:52 -0500 (CDT) From: Mohit Aron Message-Id: <199910121808.NAA19953@cs.rice.edu> Subject: Re: delayed ACKs To: m8jaci@etek.chalmers.se, freebsd-net@freebsd.org Date: Tue, 12 Oct 1999 13:08:51 -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 > According to what I have studied, delayed ACKs can be sent: > (1)every 200 ms > (2)when I have data to send (piggyback packet) > (3)every second packet > so I don't understand why in the example below, there are ACKs that > acknowledge up to 7 segments. (in the example I have just sent 50 > segments of 1460 bytes from the client to the server) Yes, I've seen that. An ACK is sent when the receiver process actually picks up the data from the socket buffers. Now it is possible that the time taken between: pkt reception -> pkt processing -> receiving process getting scheduled -> receiving process reading data from socket is greater than the packet inter-arrival time. This does indeed happen on high b/w networks and since pkt processing is given higher priority, you'll often see ACKs acknowledging large number of packets. Check out the section on "big ACKs" in the appendix of the paper that I recently posted on this list - its available from http://www.cs.rice.edu/~aron/papers/soft-timers.ps.gz. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 13:13: 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 2BB07153AA for ; Tue, 12 Oct 1999 13:13:00 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id PAA23666; Tue, 12 Oct 1999 15:12:52 -0500 (CDT) From: Mohit Aron Message-Id: <199910122012.PAA23666@cs.rice.edu> Subject: Re: Search a symbol in the source tree To: zzhang@cs.binghamton.edu, freebsd-net@freebsd.org Date: Tue, 12 Oct 1999 15:12:52 -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 > Can anyone suggest me a way of searching symbols in the entire /usr/src > tree? I normally use grep */*. But grep does not work recursively, right? > Something like a small shell script may do this. Thanks a lot. Rather than using something equivalent to a recursive grep (which is slow), I prefer to use etags. This gives me the flexibility of searching for symbols from within emacs where emacs directly takes me to the section of code that defines the symbol. To use, first create a TAGS file with the following command: find /usr/src/sys/ -name \*.[ch] -print | etags - This'll create a TAGS file in the current directory for the kernel source. Then from within emacs, commands such as: M-x find-tag (also bound to M-.) are available to search for symbols in the TAGS file. To do a general regexp search on the code for anything whatsoever, you can use: M-x tags-search - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 13:21: 8 1999 Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 716B214BD8; Tue, 12 Oct 1999 13:21:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 62ECF1CD411; Tue, 12 Oct 1999 13:21:07 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Tue, 12 Oct 1999 13:21:07 -0700 (PDT) From: Kris Kennaway To: Garrett Wollman Cc: David Vrtin , freebsd-net@FreeBSD.ORG Subject: Re: UCD-SNMP: kvm_read(*, 2, 0xbfbfb1e8, 96) = 0: kvm_read: Bad address In-Reply-To: <199910121401.KAA90595@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 12 Oct 1999, Garrett Wollman wrote: > > Reconfiguring daemon > > kvm_read(*, 2, 0xbfbfb1e8, 96) = 0: kvm_read: Bad address > > TCP_Count_Connections - inpcb: Bad address > > > Bad address?? > > That indicates that the SNMP agent doesn't know how to correctly > extract TCP connection information from the kernel. the ucd-snmp port is notoriously fragile - it seems to break regularly every few months with some kernel change or other. But, it should work on 3.3 according to bento.freebsd.org - have you recompiled it since upgrading? Kris ---- XOR for AES -- join the campaign! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 14:42:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from grmls01.nebs.com (grmls01.nebs.com [161.211.200.240]) by hub.freebsd.org (Postfix) with ESMTP id BA27614DFD for ; Tue, 12 Oct 1999 14:42:02 -0700 (PDT) (envelope-from ph3414a@nebs.com) Received: from [208.0.183.22] by grmls01.nebs.com (Netscape Messaging Server 3.6) with SMTP id AAA47B7 for ; Tue, 12 Oct 1999 17:36:30 -0400 Date: Tue, 12 Oct 1999 17:18:25 -0500 From: Patrick Hooper Reply-To: phooper@nebs.com Subject: NFS error To: freebsd-net@freebsd.org Message-ID: X-Authenticated: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am running the following: FreeBSD tom2k1.nebs.com 3.2-RELEASE FreeBSD 3.2-RELEASE #0: Tue Aug 17 11:27:02 CDT 1999 root@mecca2k.my.domain:/usr/src/sys/compile/MECCA2K i386 I am getting the following message in /var/log/messages: Oct 11 02:00:01 tom2k1 /kernel: nfs send error 32 for server todbs01:/mom/landin g/eps/EPSUNCOMPRESS Oct 11 02:00:01 tom2k1 /kernel: nfs send error 32 for server todbs01:/mom/data/s tage_ps/dp96 Oct 11 02:00:01 tom2k1 /kernel: nfs send error 32 for server todbs01:/mom/data/s tage_ps/dp96 Oct 12 02:00:01 tom2k1 /kernel: nfs send error 32 for server todbs01:/mom/landin g/eps/EPSUNCOMPRESS Oct 12 02:00:01 tom2k1 /kernel: nfs send error 32 for server todbs01:/mom/landin g/eps/EPSUNCOMPRESS Oct 12 02:00:01 tom2k1 /kernel: nfs send error 32 for server todbs01:/mom/data/s tage_ps/dp96 Oct 12 02:00:01 tom2k1 /kernel: nfs send error 32 for server todbs01:/mom/data/s tage_ps/dp96 Oct 12 13:41:14 tom2k1 su: amgraf to root on /dev/ttyp0 Oct 12 13:41:21 tom2k1 /kernel: nfs send error 32 for server todbs01:/mom/landin g/eps/EPSUNCOMPRESS Oct 12 13:41:21 tom2k1 /kernel: nfs send error 32 for server todbs01:/mom/landin g/eps/EPSUNCOMPRESS Any ideas? I searched the archives to no avail. Oddly enough the mount works and I can do an "ls" and get results. This is a TCP mount against a Solaris 2.5.1 E3000. Thank you in advance. ================================================================== Patrick Hooper Senior PrePress Engineer? New England Business Service, Inc. Peterborough, NH ... /_ _\ <| ^ |> "Just might get some sleep ... tonight" \ ^ / |-| ================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 15: 5:28 1999 Delivered-To: freebsd-net@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 9B50415383 for ; Tue, 12 Oct 1999 15:05:19 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id AAA27779; Wed, 13 Oct 1999 00:05:03 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 42113D24F; Wed, 13 Oct 1999 00:05:02 +0200 (CEST) Message-ID: <19991013000502.A8186@enst.fr> Date: Wed, 13 Oct 1999 00:05:02 +0200 From: Pierre Beyssac To: Wim Livens , freebsd-net@FreeBSD.ORG Subject: Re: Why copying data is needed for forwarding IP packets ? References: <19991012183349.D7794@rc.bel.alcatel.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19991012183349.D7794@rc.bel.alcatel.be>; from Wim Livens on Tue, Oct 12, 1999 at 06:33:49PM +0200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 12, 1999 at 06:33:49PM +0200, Wim Livens wrote: > In Stevens' volume II book, the following is mentioned: > > "Two operations dominate the time required to process packets: copying > data end computing checksums." (section 8.7, p. 234). > > What is meant exactly by copying data here ? Copying data from user space to kernel space, or the opposite, or copying data inside the kernel. Generally the latter is avoided as much as possible due to its high cost. > modified, and then the second interface card reads the packet from > host memory and send it out on the wire (maybe using some buffering on > the card) ? Or is the data copied from host memory to host memory > somewhere ? AFAICT, there's no copy in that case. > Does the same hold for multicast ? Not always. The forwarding code copies datagrams sometimes (when they are to be forwarded to more than one interface). Have a look at sys/netinet/ip_mroute.c:X_ip_mforward() and section 14.3 of Stevens... -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 15: 8:14 1999 Delivered-To: freebsd-net@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 8DD0714C1B for ; Tue, 12 Oct 1999 15:07:59 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id AAA28006; Wed, 13 Oct 1999 00:07:55 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 49132D24F; Wed, 13 Oct 1999 00:07:55 +0200 (CEST) Message-ID: <19991013000755.B8186@enst.fr> Date: Wed, 13 Oct 1999 00:07:55 +0200 From: Pierre Beyssac To: The Hermit Hacker , "D.M.P." Cc: Hamid Moghadam , freebsd-net@FreeBSD.ORG Subject: Re: 3C509B support ? References: <38035366.DC8E4910@mindless.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from The Hermit Hacker on Tue, Oct 12, 1999 at 12:48:37PM -0300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 12, 1999 at 12:48:37PM -0300, The Hermit Hacker wrote: > And have the following messages popping up fairly frequently: > > xl0: command never completed! > xl0: command never completed! I'm running -current and I see similar messages with Brian's new driver (not with the previous driver AFAIR): xl1: watchdog timeout My card is a 3c905B too. xl1: <3Com 3c905B-TX Fast Etherlink XL> irq 11 at device 17.0 on pci0 xl1: Ethernet address: 00:c0:4f:67:0b:82 -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 12 23: 0:50 1999 Delivered-To: freebsd-net@freebsd.org Received: from jason.argos.org (a1-3a123.neo.rr.com [24.93.180.123]) by hub.freebsd.org (Postfix) with ESMTP id 4C29314C3A; Tue, 12 Oct 1999 23:00:47 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA01868; Wed, 13 Oct 1999 02:00:46 -0400 Date: Wed, 13 Oct 1999 02:00:46 -0400 (EDT) From: Mike Nowlin To: Kris Kennaway Cc: Garrett Wollman , David Vrtin , freebsd-net@FreeBSD.ORG Subject: Re: UCD-SNMP: kvm_read(*, 2, 0xbfbfb1e8, 96) = 0: kvm_read: Bad address 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 > the ucd-snmp port is notoriously fragile - it seems to break regularly > every few months with some kernel change or other. But, it should work on > 3.3 according to bento.freebsd.org - have you recompiled it since > upgrading? That is the fix (at least, for the 10 or so machines I upgraded recently) -- recompile ucd-snmp, and it should work again... mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 13 0: 9:59 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.bsb.nutecnet.com.br (mail.bsb.nutecnet.com.br [200.252.253.5]) by hub.freebsd.org (Postfix) with ESMTP id 9696114C0F; Wed, 13 Oct 1999 00:09:46 -0700 (PDT) (envelope-from visi0n@aux-tech.org) Received: from variola.chinatown.org (dl7073-bsb.bsb.nutecnet.com.br [200.252.208.73]) by mail.bsb.nutecnet.com.br (8.8.5/SCA-6.6) with SMTP id FAA29412; Wed, 13 Oct 1999 05:08:12 -0300 (BRA) Date: Tue, 12 Oct 1999 04:11:59 +0000 ( ) From: visi0n X-Sender: visi0n@variola.chinatown.org To: freebsd-net@FreeBSD.ORG Cc: freebsd-hackers@freebsd.org Subject: Isa Ether Devices (ne2000) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Im studying the network part of the kernel and trying to found where's the function which do the interruption in the ne2000 isa card when a packet is in the "wire", and what function of the kernel initialize the ne2000 isa card. Thanx =============================================================================== visi0n AUX Technologies www.aux-tech.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 13 0:14:37 1999 Delivered-To: freebsd-net@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 8BDF814E79; Wed, 13 Oct 1999 00:14:27 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA21463; Wed, 13 Oct 1999 16:44:07 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 13 Oct 1999 16:44:07 +0930 (CST) From: "Daniel O'Connor" To: visi0n Subject: RE: Isa Ether Devices (ne2000) Cc: freebsd-hackers@freebsd.org, freebsd-net@FreeBSD.ORG Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 12-Oct-99 visi0n wrote: > Hi, Im studying the network part of the kernel and trying to found > where's the function which do the interruption in the ne2000 isa card when > a packet is in the "wire", and what function of the kernel initialize the > ne2000 isa card. Look in /usr/src/sys/i386/isa/if_ed.c You might want to look at something less complex like the fxp driver (/usr/src/sys/pci/if_fxp.c). It has less cruft about PCMCIA and other junk. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 13 8:55:51 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpham.uni-mb.si (alpham.uni-mb.si [164.8.1.101]) by hub.freebsd.org (Postfix) with ESMTP id 4057815530 for ; Wed, 13 Oct 1999 08:55:44 -0700 (PDT) (envelope-from vrtin@uni-mb.si) Received: from gea.uni-mb.si by alpham.uni-mb.si (PMDF V5.1-12 #7554) with ESMTP id <01JH3F4ZVRLU00465J@alpham.uni-mb.si> for freebsd-net@FreeBSD.ORG; Wed, 13 Oct 1999 17:55:37 MET Received: from localhost (david@localhost) by gea.uni-mb.si (8.9.3/8.9.3/19990328) with SMTP id RAA09669; Wed, 13 Oct 1999 17:55:36 +0200 (CEST) Date: Wed, 13 Oct 1999 17:55:32 +0200 (CEST) From: David Vrtin Subject: Re: UCD-SNMP: kvm_read(*, 2, 0xbfbfb1e8, 96) = 0: kvm_read: Bad address In-reply-to: To: Kris Kennaway Cc: Garrett Wollman , freebsd-net@FreeBSD.ORG Reply-To: David Vrtin Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-No-Archive: Yes Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 12 Oct 1999, Kris Kennaway wrote: > > > Reconfiguring daemon > > > kvm_read(*, 2, 0xbfbfb1e8, 96) = 0: kvm_read: Bad address > > > TCP_Count_Connections - inpcb: Bad address > > > Bad address?? > > That indicates that the SNMP agent doesn't know how to correctly > > extract TCP connection information from the kernel. > the ucd-snmp port is notoriously fragile - it seems to break regularly > every few months with some kernel change or other. But, it should work on > 3.3 according to bento.freebsd.org - have you recompiled it since > upgrading? Yes, I have. Snmpd works OK, I get only this strange error in snmpd.log file. Best regards, David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 13 15:30:46 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 AFBEE1543F for ; Wed, 13 Oct 1999 15:30:29 -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 QAA01979; Wed, 13 Oct 1999 16:00:06 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 13 Oct 1999 16:00:05 -0500 (CDT) From: Chris Dillon To: Pierre Beyssac Cc: The Hermit Hacker , "D.M.P." , Hamid Moghadam , freebsd-net@FreeBSD.ORG Subject: Re: 3C509B support ? In-Reply-To: <19991013000755.B8186@enst.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 13 Oct 1999, Pierre Beyssac wrote: > On Tue, Oct 12, 1999 at 12:48:37PM -0300, The Hermit Hacker wrote: > > And have the following messages popping up fairly frequently: > > > > xl0: command never completed! > > xl0: command never completed! > > I'm running -current and I see similar messages with Brian's new > driver (not with the previous driver AFAIR): > > xl1: watchdog timeout > > My card is a 3c905B too. > > xl1: <3Com 3c905B-TX Fast Etherlink XL> irq 11 at device 17.0 on pci0 > xl1: Ethernet address: 00:c0:4f:67:0b:82 You folks are confusing the 509B with the 905B. The original poster asked about the 509B. 3COM has a wonderful model numbering system, don't they? Someone will buy another 3COM NIC around here only over my dead body, but I do use one 3C509B (a.k.a. EtherLink III) in a FreeBSD 3.1-STABLE box and it has been working just fine. -- 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 Wed Oct 13 23: 5:56 1999 Delivered-To: freebsd-net@freebsd.org Received: from hotmail.com (f302.hotmail.com [207.82.251.215]) by hub.freebsd.org (Postfix) with SMTP id C49B314FDA for ; Wed, 13 Oct 1999 23:05:54 -0700 (PDT) (envelope-from hmoghadam@hotmail.com) Received: (qmail 46044 invoked by uid 0); 14 Oct 1999 06:05:54 -0000 Message-ID: <19991014060554.46043.qmail@hotmail.com> Received: from 195.200.226.109 by www.hotmail.com with HTTP; Wed, 13 Oct 1999 23:05:52 PDT X-Originating-IP: [195.200.226.109] From: "Hamid Moghadam" To: cdillon@wolves.k12.mo.us, beyssac@enst.fr Cc: scrappy@hub.org, gryph@mindless.com, freebsd-net@FreeBSD.ORG Subject: Re: 3C509B support ? Date: Wed, 13 Oct 1999 23:05:52 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, Chris told the actual thing happened ! I asked about 3C509B not 3C905B ! Anyhow, I have just installed three of them (3C509B) in one box running 3.2R working as fw, bandwidth limiter, nat and router, and everything is working properly. Thanks for your comments. Cheers - HM >From: Chris Dillon >To: Pierre Beyssac >CC: The Hermit Hacker , "D.M.P." , > Hamid Moghadam , freebsd-net@FreeBSD.ORG >Subject: Re: 3C509B support ? >Date: Wed, 13 Oct 1999 16:00:05 -0500 (CDT) > >On Wed, 13 Oct 1999, Pierre Beyssac wrote: > > > On Tue, Oct 12, 1999 at 12:48:37PM -0300, The Hermit Hacker wrote: > > > And have the following messages popping up fairly frequently: > > > > > > xl0: command never completed! > > > xl0: command never completed! > > > > I'm running -current and I see similar messages with Brian's new > > driver (not with the previous driver AFAIR): > > > > xl1: watchdog timeout > > > > My card is a 3c905B too. > > > > xl1: <3Com 3c905B-TX Fast Etherlink XL> irq 11 at device 17.0 on pci0 > > xl1: Ethernet address: 00:c0:4f:67:0b:82 > >You folks are confusing the 509B with the 905B. The original poster >asked about the 509B. 3COM has a wonderful model numbering system, >don't they? Someone will buy another 3COM NIC around here only over >my dead body, but I do use one 3C509B (a.k.a. EtherLink III) in a >FreeBSD 3.1-STABLE box and it has been working just fine. > > >-- 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." > > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 14 4:36:30 1999 Delivered-To: freebsd-net@freebsd.org Received: from eembox.ee.ncku.edu.tw (eembox.ee.ncku.edu.tw [140.116.72.15]) by hub.freebsd.org (Postfix) with ESMTP id 97FE014CCC for ; Thu, 14 Oct 1999 04:36:03 -0700 (PDT) (envelope-from ckwen@eembox.ee.ncku.edu.tw) Received: (from ckwen@localhost) by eembox.ee.ncku.edu.tw (8.9.1a/8.9.1) id TAA12728 for freebsd-net@freebsd.org; Thu, 14 Oct 1999 19:31:00 +0800 (CST) From: ckwen Message-Id: <199910141131.TAA12728@eembox.ee.ncku.edu.tw> Subject: can two fast ethernet cards work in a freebsd box ? To: freebsd-net@freebsd.org Date: Thu, 14 Oct 1999 19:30:59 +0800 (CST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I install two Dlink DFE-530TX on my freebsd 3.3 box. They can be detected by kernel without problems. It happens when I connect them with two cat.5 lines to a 100 Mb hub. During booting sequence, the kernel reports that the link status of the first interface is full-duplex 100 Mbps but the second interface is half-duplex 10 Mbps. I expect that the two links should be full-duplex 100 Mbps. Can anyone help me out ? Regards, Cheng-Kang Wen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 14 7: 4:44 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id ACEA914C32 for ; Thu, 14 Oct 1999 07:04:36 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11blUb-0000gL-00; Thu, 14 Oct 1999 08:04:29 -0600 Message-ID: <3805E2EF.798C9448@softweyr.com> Date: Thu, 14 Oct 1999 08:04:31 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: ckwen Cc: freebsd-net@FreeBSD.ORG Subject: Re: can two fast ethernet cards work in a freebsd box ? References: <199910141131.TAA12728@eembox.ee.ncku.edu.tw> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ckwen wrote: > > I install two Dlink DFE-530TX on my freebsd 3.3 box. > They can be detected by kernel without problems. > It happens when I connect them with two cat.5 lines to a > 100 Mb hub. During booting sequence, the kernel reports > that the link status of the first interface is full-duplex 100 Mbps > but the second interface is half-duplex 10 Mbps. I expect that > the two links should be full-duplex 100 Mbps. > Can anyone help me out ? Your autonegotiation is failing. If you're certain it is plugged into a 100 Mb hub, try adding "mediaopt 100baseTX" to the ifconfig parameters. If you're plugging both into the same hub, don't be surprised if you get other error messages too. There is no real reason to place two network interfaces on the same physical network. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 14 9:37:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from sugar.pharlap.com (sugar.pharlap.com [192.107.36.1]) by hub.freebsd.org (Postfix) with ESMTP id EDC4714BD7 for ; Thu, 14 Oct 1999 09:36:54 -0700 (PDT) (envelope-from clark@pharlap.com) Received: from clark ([192.107.36.171]) by sugar.pharlap.com (Post.Office MTA v3.5.2 release 221 ID# 0-56365U200L2S100V35) with SMTP id com; Thu, 14 Oct 1999 12:36:44 -0400 From: clark@pharlap.com (Clark Jarvis) Date: Thu, 14 Oct 1999 12:40:52 -0400 To: Mohit Aron , freebsd-net@freebsd.org In-Reply-To: <199910122012.PAA23666@cs.rice.edu> Subject: Re: Search a symbol in the source tree X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v1.61 b62 Message-ID: <19991014163644223.AAA270@sugar.pharlap.com@clark> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In <199910122012.PAA23666@cs.rice.edu>, on 10/12/99 at 03:12 PM, Mohit Aron said: >> Can anyone suggest me a way of searching symbols in the entire /usr/src >> tree? I normally use grep */*. But grep does not work recursively, right? >> Something like a small shell script may do this. Thanks a lot. >Rather than using something equivalent to a recursive grep (which is >slow), I prefer to use etags. This gives me the flexibility of searching >for symbols from within emacs where emacs directly takes me to the >section of code that defines the symbol. [tags creation code deleted] I use a combination of tags and an unzipped tar file of the source tree, providing your text editor can handle large files and binary characters with some success. Just load up the tar file and search. Inside the tar file, the filespec for each file is stored in a block at the beginning of each file, so it only takes a little reverse searching to figure out where the file lives in the source tree. Tags are great, but they don't find where/how symbols are used, just where they are defined. And realizing that this is an old, ingrained behavior - etags may be able to do more than I'm aware of. -- Clark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 14 10:34: 6 1999 Delivered-To: freebsd-net@freebsd.org Received: from totally.morphed.com (totally.morphed.com [207.66.106.134]) by hub.freebsd.org (Postfix) with ESMTP id 4E7A515393; Thu, 14 Oct 1999 10:33:48 -0700 (PDT) (envelope-from root@totally.morphed.com) Received: from localhost (root@localhost) by totally.morphed.com (8.9.3/8.9.2) with ESMTP id LAA76918; Thu, 14 Oct 1999 11:33:47 -0600 (MDT) (envelope-from root@totally.morphed.com) Date: Thu, 14 Oct 1999 11:33:47 -0600 (MDT) From: "Jason L. Schwab" To: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: arplookup.... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey, I run a 3.3-STABLE box on a T3 network, and I own 64 ips out of a c class those 64 ips are between XXX.XXX.XXX.134 tho XXX.XXX.XXX.198 and There i dont own or use 207.66.106.1 .. but i'm always getting these messages. Altho I do have firewall rules that use 207.66.106.0/24, could that be the problem? Please help! arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network arplookup 207.66.106.1 failed: host is not on local network To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 14 11: 3:49 1999 Delivered-To: freebsd-net@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id B41FE1514D; Thu, 14 Oct 1999 11:03:34 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id LAA36450; Thu, 14 Oct 1999 11:03:29 -0700 (PDT) Date: Thu, 14 Oct 1999 11:03:29 -0700 (PDT) From: David Wolfskill Message-Id: <199910141803.LAA36450@pau-amma.whistle.com> To: freebsd-net@FreeBSD.org, freebsd-questions@FreeBSD.org, root@totally.morphed.com Subject: Re: arplookup.... In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Date: Thu, 14 Oct 1999 11:33:47 -0600 (MDT) >From: "Jason L. Schwab" >I run a 3.3-STABLE box on a T3 network, and I own 64 ips out of a c class >those 64 ips are between XXX.XXX.XXX.134 tho XXX.XXX.XXX.198 and There i >dont own or use 207.66.106.1 .. but i'm always getting these messages. >Altho I do have firewall rules that use 207.66.106.0/24, could that be the >problem? Please help! >arplookup 207.66.106.1 failed: host is not on local network >... Yes. Tell the machine the truth about the network it's on -- specify an appropriate netmask for the actual circumstances. If you tell it /24, that means that 207.66.106.1 is on the local network. In your case, it would seem that /26 would be a better choice (though you might be able to use (e.g.) /27 or /28, if you subnet your /26). Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 14 11:10:46 1999 Delivered-To: freebsd-net@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 24AC714C1E for ; Thu, 14 Oct 1999 11:10:43 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (ind.alcatel.com 2.3 [OUT])) id LAA15963; Thu, 14 Oct 1999 11:09:36 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id LAA15229; Thu, 14 Oct 1999 11:09:36 -0700 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA12453; Thu, 14 Oct 99 11:09:12 PDT Message-Id: <38061C5C.75B89CA3@softweyr.com> Date: Thu, 14 Oct 1999 12:09:32 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Clark Jarvis Cc: Mohit Aron , freebsd-net@FreeBSD.ORG Subject: Re: Search a symbol in the source tree References: <19991014163644223.AAA270@sugar.pharlap.com@clark> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Clark Jarvis wrote: > > In <199910122012.PAA23666@cs.rice.edu>, on 10/12/99 > at 03:12 PM, Mohit Aron said: > > >> Can anyone suggest me a way of searching symbols in the entire /usr/src > >> tree? I normally use grep */*. But grep does not work recursively, right? > >> Something like a small shell script may do this. Thanks a lot. > > >Rather than using something equivalent to a recursive grep (which is > >slow), I prefer to use etags. This gives me the flexibility of searching > >for symbols from within emacs where emacs directly takes me to the > >section of code that defines the symbol. > > [tags creation code deleted] > > I use a combination of tags and an unzipped tar file of the source tree, > providing your text editor can handle large files and binary characters > with some success. Just load up the tar file and search. Inside the tar > file, the filespec for each file is stored in a block at the beginning of > each file, so it only takes a little reverse searching to figure out where > the file lives in the source tree. > > Tags are great, but they don't find where/how symbols are used, just where > they are defined. And realizing that this is an old, ingrained behavior - > etags may be able to do more than I'm aware of. 'tags-search' will exhaustively search all the tagged files for the symbol. On popular symbols, this can take a while, but it will certainly find all the references. Handily enough, the search string is a regexp. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 14 13:32:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from earth.wnm.net (earth.wnm.net [208.246.240.243]) by hub.freebsd.org (Postfix) with ESMTP id D412F1521A; Thu, 14 Oct 1999 13:32:24 -0700 (PDT) (envelope-from alex@wnm.net) Received: from localhost (alex@localhost) by earth.wnm.net (8.8.8/8.8.8) with ESMTP id PAA18291; Thu, 14 Oct 1999 15:32:14 -0500 (CDT) Date: Thu, 14 Oct 1999 15:32:14 -0500 (CDT) From: Alex Charalabidis To: David Wolfskill Cc: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, root@totally.morphed.com Subject: Re: arplookup.... In-Reply-To: <199910141803.LAA36450@pau-amma.whistle.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 Thu, 14 Oct 1999, David Wolfskill wrote: > >Date: Thu, 14 Oct 1999 11:33:47 -0600 (MDT) > >From: "Jason L. Schwab" > > >I run a 3.3-STABLE box on a T3 network, and I own 64 ips out of a c class > >those 64 ips are between XXX.XXX.XXX.134 tho XXX.XXX.XXX.198 and There i > >dont own or use 207.66.106.1 .. but i'm always getting these messages. > >Altho I do have firewall rules that use 207.66.106.0/24, could that be the > >problem? Please help! > > >arplookup 207.66.106.1 failed: host is not on local network > >... > > Yes. Tell the machine the truth about the network it's on -- specify an > appropriate netmask for the actual circumstances. > > If you tell it /24, that means that 207.66.106.1 is on the local > network. In your case, it would seem that /26 would be a better choice > (though you might be able to use (e.g.) /27 or /28, if you subnet your /26). > This is an arbitrary block of 65 addresses within a /24, not a properly subnetted class c. I suggest the class c be subnetted in a consistent manner and you get a real /26 like 207.66.106.128-191. -ac -- Alex Charalabidis WebNet Memphis (901) 432-6000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 14 16:46:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from totally.morphed.com (totally.morphed.com [207.66.106.134]) by hub.freebsd.org (Postfix) with ESMTP id 1A5F214ED7; Thu, 14 Oct 1999 16:46:17 -0700 (PDT) (envelope-from root@totally.morphed.com) Received: from localhost (root@localhost) by totally.morphed.com (8.9.3/8.9.2) with ESMTP id RAA99892; Thu, 14 Oct 1999 17:46:12 -0600 (MDT) (envelope-from root@totally.morphed.com) Date: Thu, 14 Oct 1999 17:46:12 -0600 (MDT) From: "Jason L. Schwab" To: David Wolfskill Cc: freebsd-net@FreeBSD.org, freebsd-questions@FreeBSD.org Subject: Re: arplookup.... In-Reply-To: <199910141803.LAA36450@pau-amma.whistle.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 How would i set the approiate netmask? On Thu, 14 Oct 1999, David Wolfskill wrote: > >Date: Thu, 14 Oct 1999 11:33:47 -0600 (MDT) > >From: "Jason L. Schwab" > > >I run a 3.3-STABLE box on a T3 network, and I own 64 ips out of a c class > >those 64 ips are between XXX.XXX.XXX.134 tho XXX.XXX.XXX.198 and There i > >dont own or use 207.66.106.1 .. but i'm always getting these messages. > >Altho I do have firewall rules that use 207.66.106.0/24, could that be the > >problem? Please help! > > >arplookup 207.66.106.1 failed: host is not on local network > >... > > Yes. Tell the machine the truth about the network it's on -- specify an > appropriate netmask for the actual circumstances. > > If you tell it /24, that means that 207.66.106.1 is on the local > network. In your case, it would seem that /26 would be a better choice > (though you might be able to use (e.g.) /27 or /28, if you subnet your /26). > > Cheers, > david > -- > David Wolfskill dhw@whistle.com UNIX System Administrator > voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 14 18:15:31 1999 Delivered-To: freebsd-net@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id DDF1C14E59; Thu, 14 Oct 1999 18:15:19 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id SAA38517; Thu, 14 Oct 1999 18:15:18 -0700 (PDT) Date: Thu, 14 Oct 1999 18:15:18 -0700 (PDT) From: David Wolfskill Message-Id: <199910150115.SAA38517@pau-amma.whistle.com> To: dhw@whistle.com, root@totally.morphed.com Subject: Re: arplookup.... Cc: freebsd-net@FreeBSD.org, freebsd-questions@FreeBSD.org In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Date: Thu, 14 Oct 1999 17:46:12 -0600 (MDT) >From: "Jason L. Schwab" >How would i set the approiate netmask? Generally (in FreeBSD), in /etc/rc.conf or /etc/rc.conf.local. For example: ifconfig_de0="inet 172.16.8.11 netmask 255.255.255.0" In your case (as someone else pointed out), you're going to need to figure out what subnet(s) you really want to use. First, you said: >> >Date: Thu, 14 Oct 1999 11:33:47 -0600 (MDT) >> >From: "Jason L. Schwab" >> >I run a 3.3-STABLE box on a T3 network, and I own 64 ips out of a c class >> >those 64 ips are between XXX.XXX.XXX.134 tho XXX.XXX.XXX.198... Now, .134 - .198 is 65 addresses, not 64. And neither 134 nor 198 is on a reasonable subnet boundary. Here: dec hex bin 128 80 1000 0000 129 81 1000 0001 ... 134 86 1000 0110 135 87 1000 0111 136 88 1000 1000 ... 191 bf 1011 1111 192 c0 1100 0000 193 c1 1100 0001 ... 197 c5 1100 0101 198 c6 1100 0110 199 c7 1100 0111 200 c8 1100 1000 Ideally, you could arrange to swap IP addresses around, so you could get .128 - .191; that's a nice, clean netmask of 255.255.255.192, with 62 usable host addresses. Alternatively, if you really have (and are stuck with) .134 - .198, you could split it up as: .134 - .135 Wasted .136 - .143 *.136/29; mask of 255.255.255.248 (6 usable host addresses) .144 - .159 *.144/28; mask of 255.255.255.240 (14 usable host addresses) .160 - .191 *.160/27; mask of 255.255.255.224 (30 usable host addresses) .192 - .195 *.192/30; mask of 255.255.255.252 (2 usable host addresses) .196 - .197 Wasted .198 Wasted (Recall that for each subnet, the "all 0s" host address denotes the (sub)net, and the "all 1s" host address denotes the broadcast address.) The above mess (except for the wasted addresses) could possibly be useful, but it's a bit of a stretch. Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 14 21:17:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from sttlpop5.sttl.uswest.net (sttlpop5.sttl.uswest.net [206.81.192.5]) by hub.freebsd.org (Postfix) with SMTP id 2AE7F14BDE for ; Thu, 14 Oct 1999 21:17:08 -0700 (PDT) (envelope-from nchong@uswest.net) Received: (qmail 20867 invoked by alias); 15 Oct 1999 04:17:08 -0000 Delivered-To: fixup-freebsd-net@freebsd.org@fixme Received: (qmail 20849 invoked by uid 0); 15 Oct 1999 04:17:07 -0000 Received: from ddslppp190.sttl.uswest.net (HELO gchunghome) (216.160.75.190) by sttlpop5.sttl.uswest.net with SMTP; 15 Oct 1999 04:17:07 -0000 From: "N. C. Hong" To: "'Mohit Aron'" , , Subject: RE: Search a symbol in the source tree Date: Thu, 14 Oct 1999 21:20:52 -0700 Message-ID: <000f01bf16c4$ab747380$0200000a@gchunghome> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <199910122012.PAA23666@cs.rice.edu> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org $ find /usr/src -name "*.c" -print -exec grep "" {} \; | more -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Mohit Aron Sent: Tuesday, October 12, 1999 1:13 PM To: zzhang@cs.binghamton.edu; freebsd-net@freebsd.org Subject: Re: Search a symbol in the source tree > Can anyone suggest me a way of searching symbols in the entire /usr/src > tree? I normally use grep */*. But grep does not work recursively, right? > Something like a small shell script may do this. Thanks a lot. Rather than using something equivalent to a recursive grep (which is slow), I prefer to use etags. This gives me the flexibility of searching for symbols from within emacs where emacs directly takes me to the section of code that defines the symbol. To use, first create a TAGS file with the following command: find /usr/src/sys/ -name \*.[ch] -print | etags - This'll create a TAGS file in the current directory for the kernel source. Then from within emacs, commands such as: M-x find-tag (also bound to M-.) are available to search for symbols in the TAGS file. To do a general regexp search on the code for anything whatsoever, you can use: M-x tags-search - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 14 21:26:48 1999 Delivered-To: freebsd-net@freebsd.org Received: from eembox.ee.ncku.edu.tw (eembox.ee.ncku.edu.tw [140.116.72.15]) by hub.freebsd.org (Postfix) with ESMTP id 9A36014BDE for ; Thu, 14 Oct 1999 21:26:41 -0700 (PDT) (envelope-from ckwen@eembox.ee.ncku.edu.tw) Received: (from ckwen@localhost) by eembox.ee.ncku.edu.tw (8.9.1a/8.9.1) id KAA15619 for freebsd-net@freebsd.org; Fri, 15 Oct 1999 10:21:41 +0800 (CST) From: ckwen Message-Id: <199910150221.KAA15619@eembox.ee.ncku.edu.tw> Subject: Re: can two fast ethernet cards work in a freebsd box ? To: freebsd-net@freebsd.org Date: Fri, 15 Oct 1999 10:21:40 +0800 (CST) In-Reply-To: <3805E2EF.798C9448@softweyr.com> from "Wes Peters" at Oct 14, 99 08:04:31 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry for not describing the situation clearly. > > > > I install two Dlink DFE-530TX on my freebsd 3.3 box. > > They can be detected by kernel without problems. > > It happens when I connect them with two cat.5 lines to a > > 100 Mb hub. During booting sequence, the kernel reports ^^^^^^^^^^^ connected to two seperated 100 Mb hubs. > > that the link status of the first interface is full-duplex 100 Mbps > > but the second interface is half-duplex 10 Mbps. I expect that > > the two links should be full-duplex 100 Mbps. > > Can anyone help me out ? > Both of 100 Mb LED indicators of the two hubs light when freebsd machine is powered on. The 100 Mb LED of the hub which the second interface connected to goes off after kernel reports that the second interface is 10 Mbps half-duplex. Cheng-Kang Wen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 14 22:30:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id E40B414BDC for ; Thu, 14 Oct 1999 22:30:38 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11bzwp-0005Ag-00; Thu, 14 Oct 1999 23:30:36 -0600 Message-ID: <3806BBFA.7E5E4658@softweyr.com> Date: Thu, 14 Oct 1999 23:30:34 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: ckwen Cc: freebsd-net@FreeBSD.ORG Subject: Re: can two fast ethernet cards work in a freebsd box ? References: <199910150221.KAA15619@eembox.ee.ncku.edu.tw> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ckwen wrote: > > Sorry for not describing the situation clearly. > > > > > > > I install two Dlink DFE-530TX on my freebsd 3.3 box. > > > They can be detected by kernel without problems. > > > It happens when I connect them with two cat.5 lines to a > > > 100 Mb hub. During booting sequence, the kernel reports > ^^^^^^^^^^^ > connected to two seperated 100 Mb hubs. > > > > that the link status of the first interface is full-duplex 100 Mbps > > > but the second interface is half-duplex 10 Mbps. I expect that > > > the two links should be full-duplex 100 Mbps. > > > Can anyone help me out ? > > > > Both of 100 Mb LED indicators of the two hubs light when freebsd > machine is powered on. The 100 Mb LED of the hub which the second > interface connected to goes off after kernel reports that the > second interface is 10 Mbps half-duplex. Autonegotiation is failing between your card and this hub. Specify "mediaopt 100baseTX" as part of the ifconfig options, as in: ifconfig_vr0="inet 192.168.42.1 netmask 0xffffff00 mediaopt 100baseTX" in /etc/rc.conf. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 15 3:36:56 1999 Delivered-To: freebsd-net@freebsd.org Received: from vidle.i.cz (vidle.i.cz [193.179.36.138]) by hub.freebsd.org (Postfix) with ESMTP id BE12714FE1 for ; Fri, 15 Oct 1999 03:36:53 -0700 (PDT) (envelope-from mm@i.cz) Received: from ns.i.cz (brana.i.cz [193.179.36.134]) by vidle.i.cz (Postfix) with ESMTP id 45F5930706 for ; Fri, 15 Oct 1999 12:36:53 +0200 (CEST) Received: from woody.i.cz (woody.i.cz [192.168.18.29]) by ns.i.cz (Postfix) with ESMTP id 7C8C636415 for ; Fri, 15 Oct 1999 12:36:52 +0200 (CEST) Content-Length: 532 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3806BBFA.7E5E4658@softweyr.com> Date: Fri, 15 Oct 1999 12:36:52 +0200 (MET DST) Reply-To: mm@i.cz From: Martin Machacek To: freebsd-net@FreeBSD.ORG Subject: Re: can two fast ethernet cards work in a freebsd box ? Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15-Oct-99 Wes Peters wrote: > Autonegotiation is failing between your card and this hub. Specify > "mediaopt 100baseTX" as part of the ifconfig options, as in: > > ifconfig_vr0="inet 192.168.42.1 netmask 0xffffff00 mediaopt 100baseTX" I thought it should be: ifconfig_vr0="inet 192.168.42.1 netmask 0xffffff00 media 100baseTX" ^^^^^ At least my (FreeBSD 3.2) vr(4) manpage says that mediaopt could be full-duplex of half-duplex. Martin --- [PGP KeyID F3F409C4] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 15 12:52:30 1999 Delivered-To: freebsd-net@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 02A5A151F0 for ; Fri, 15 Oct 1999 12:52:28 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (ind.alcatel.com 2.3 [OUT])) id MAA02870; Fri, 15 Oct 1999 12:52:20 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id MAA22214; Fri, 15 Oct 1999 12:52:20 -0700 Received: from softweyr.com (dyn8.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA20519; Fri, 15 Oct 99 12:52:14 PDT Message-Id: <380785EE.9F9DD5F3@softweyr.com> Date: Fri, 15 Oct 1999 13:52:14 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: mm@i.cz Cc: freebsd-net@FreeBSD.ORG Subject: Re: can two fast ethernet cards work in a freebsd box ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin Machacek wrote: > > On 15-Oct-99 Wes Peters wrote: > > Autonegotiation is failing between your card and this hub. Specify > > "mediaopt 100baseTX" as part of the ifconfig options, as in: > > > > ifconfig_vr0="inet 192.168.42.1 netmask 0xffffff00 mediaopt 100baseTX" > > I thought it should be: > > ifconfig_vr0="inet 192.168.42.1 netmask 0xffffff00 media 100baseTX" > ^^^^^ > At least my (FreeBSD 3.2) vr(4) manpage says that mediaopt could be full-duplex > of half-duplex. Oh, whoops, you're right. Sorry, autonegotiation never fails on my switches; if it does, I have to fix it. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 16 4:10:15 1999 Delivered-To: freebsd-net@freebsd.org Received: from eembox.ee.ncku.edu.tw (eembox.ee.ncku.edu.tw [140.116.72.15]) by hub.freebsd.org (Postfix) with ESMTP id 4DE5C14CAE for ; Sat, 16 Oct 1999 04:10:06 -0700 (PDT) (envelope-from ckwen@eembox.ee.ncku.edu.tw) Received: (from ckwen@localhost) by eembox.ee.ncku.edu.tw (8.9.1a/8.9.1) id TAA26753 for freebsd-net@freebsd.org; Sat, 16 Oct 1999 19:04:59 +0800 (CST) From: ckwen Message-Id: <199910161104.TAA26753@eembox.ee.ncku.edu.tw> Subject: Re: can two fast ethernet cards work in a freebsd box ? To: freebsd-net@freebsd.org Date: Sat, 16 Oct 1999 19:04:58 +0800 (CST) In-Reply-To: <3806BBFA.7E5E4658@softweyr.com> from "Wes Peters" at Oct 14, 99 11:30:34 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks to Wes Peters and Martin Machacek. Now the hub's 100 Mbps LED goes on again after the execution of ifconfig command. The parameters I set in ifconfig are "media 100baseTX mediaopt full-duplex." Neither of them can be omitted. I'll observe for some days to see if the link becomes unstable or not after I force it to work with 100baseTX/full-duplex mode. Cheng-Kang Wen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 16 9:12:43 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 54B3614CCB; Sat, 16 Oct 1999 09:12:37 -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 MAA14154; Sat, 16 Oct 1999 12:12:36 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA69254; Sat, 16 Oct 1999 12:12:06 -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: Sat, 16 Oct 1999 12:12:06 -0400 (EDT) To: freebsd-alpha@freebsd.org Cc: freebsd-net@freebsd.org Subject: diskless booting: netboot loader problem X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14344.39286.675388.510743@grasshopper.cs.duke.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been converting my net over from using bootp on a Digital UNIX server to using isc-dhcpd2. I'm having some trouble booting FreeBSD/alpha boxes because of what might be a bug in the netboot loader. (or it might just be my lack of experience w/dhcp, maybe somebody can tell me..). The problem seems to be that a DHCP server will reply to the netboot loader's DHCPDISCOVER by sending the reply to its fixed address, not broadcasting the reply. So the client never sees the reply. More details: My dhcpd.conf looks like this: deny unknown-clients ; allow bootp; subnet 152.3.XXX.0 netmask 255.255.255.0 { group { use-host-decl-names on ; # key to netbooting Digital Unix clients always-reply-rfc1048 on ; filename "/freebsd/diskless.alpha/boot/netboot"; option root-path "152.3.YYY.WWW:/freebsd/diskless.alpha/" ; host client { hardware ethernet 08:00:2b:86:6e:e0 ; fixed-address 152.3.YYY.XXX ; } } This works well for the initial load of the netboot loader from "/freebsd/diskless.alpha/boot/netboot" via the SRM console. I see a BOOTREQUEST from 08:00:2b:86:6e:e0 via fxp0 (non-rfc1048) BOOTREPLY for 152.3.YYY.XXX to client (08:00:2b:86:6e:e0) via fxp0 However, when the netboot loader is loaded, it tries to find out what its address is & where its root path, etc lies. It proceeds to send a DHPDISCOVER. The problem is that the dhcp server is sending a DHCPOFFER to 152.3.YYY.XXX, it is NOT broadcasting it. So the poor client never sees it. Eg, a tcpdump looks like this: tcpdump: listening on fxp0 11:36:19.302956 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x37b23a44 secs:3 [|bootp] 11:36:26.303848 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x37b23a44 secs:10 [|bootp] 11:36:26.305769 dhcpserver.cs.duke.edu.bootps > 255.255.255.255.bootpc: xid:0x37b23a44 secs:10 Y:client.cs.duke.edu S:dhcpserver.cs.duke.edu [|bootp] [tos 0x10] 11:36:26.331609 arp who-has dhcpserver.cs.duke.edu tell client.cs.duke.edu 11:36:26.331653 arp reply dhcpserver.cs.duke.edu is-at 0:a0:c9:9a:b2:f4 11:36:26.336821 client.cs.duke.edu.14079 > dhcpserver.cs.duke.edu.tftp: 45 RRQ "/freebsd/diskless.alpha/" [|tftp] 11:36:26.693814 dhcpserver.cs.duke.edu.3630 > client.cs.duke.edu.14079: udp 516 <....> 11:36:36.332410 0.0.0.0.bootpc > 255.255.255.255.bootps: secs:6 [|bootp] 11:36:36.334891 dhcpserver.cs.duke.edu.bootps > client.cs.duke.edu.bootpc: secs:6 Y:client.cs.duke.edu S:dhcpserver.cs.duke.edu [|bootp] [tos 0x10] 11:36:41.122377 0.0.0.0.bootpc > 255.255.255.255.bootps: secs:41 [|bootp] 11:36:41.124853 dhcpserver.cs.duke.edu.bootps > client.cs.duke.edu.bootpc: secs:41 Y:client.cs.duke.edu S:dhcpserver.cs.duke.edu [|bootp] [tos 0x10] 11:36:50.396375 rarp who-is 8:0:2b:86:6e:e0 tell 8:0:2b:86:6e:e0 11:36:52.216760 rarp who-is 8:0:2b:86:6e:e0 tell 8:0:2b:86:6e:e0 If I comment out #define SUPPORT_DHCP in lib/libstand/bootp.c, the netboot loader sends a bootp request (not dhcp) and all is well. Can I work around this by some clever dhcpd.conf option, or is the netboot loader broken. Thanks, 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 Sat Oct 16 10:21:19 1999 Delivered-To: freebsd-net@freebsd.org Received: from dingo.cdrom.com (castles550.castles.com [208.214.165.114]) by hub.freebsd.org (Postfix) with ESMTP id 3C33815105; Sat, 16 Oct 1999 10:21:12 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA06314; Sat, 16 Oct 1999 10:13:15 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910161713.KAA06314@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org, freebsd-net@freebsd.org Subject: Re: diskless booting: netboot loader problem In-reply-to: Your message of "Sat, 16 Oct 1999 12:12:06 EDT." <14344.39286.675388.510743@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Oct 1999 10:13:15 -0700 From: Mike Smith Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > If I comment out #define SUPPORT_DHCP in lib/libstand/bootp.c, the > netboot loader sends a bootp request (not dhcp) and all is well. > > Can I work around this by some clever dhcpd.conf option, or is the > netboot loader broken. The patches I posted some time back for the loader's netboot code eliminated its DHCP support for the simple reason that it was a grotty hack (and didn't work when I tried it). I'd be interested to know if the patched code I posted works in your environment, but the answer to your question is that the loader's current DHCP support is broken, yes. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 16 10:38:24 1999 Delivered-To: freebsd-net@freebsd.org Received: from thelab.hub.org (nat203.183.mpoweredpc.net [142.177.203.183]) by hub.freebsd.org (Postfix) with ESMTP id C64E314BEB; Sat, 16 Oct 1999 10:38:19 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id OAA32016; Sat, 16 Oct 1999 14:38:25 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sat, 16 Oct 1999 14:38:25 -0300 (ADT) From: The Hermit Hacker To: freebsd-net@freebsd.org Cc: freebsd-stable@freebsd.org Subject: xl0: command never completed! 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 Morning all... On a 3.3-STABLE machine, being used as a Squid server, I'm getting a pretty continuous stream of teh following message to /var/log/messages: Oct 16 14:21:01 demeter /kernel: xl0: command never completed! Not including the "last message repeated # times" messages, I've got 68 of them in the last 9hrs or so... dmesg reports the card as being: xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x24 int a irq 9 on pci0.20.0 xl0: Ethernet address: 00:10:4b:69:5c:64 xl0: autoneg complete, link status good (half-duplex, 10Mbps) Which I've always found to be a pretty reliable card in the past... Possible bug in our driver? Harmless error? I'm more worried about performance of the machine then anything, since its the first production FreeBSD machine I've been able to railroad through at work, and other then that, she's operating such that its pissing some ppl off...they expected it to crash and burn ages ago *grin* Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 16 11: 5:57 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 9D14A14D80 for ; Sat, 16 Oct 1999 11:05:54 -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 LAA32444 for ; Sat, 16 Oct 1999 11:05:49 -0700 (PDT) Date: Sat, 16 Oct 1999 11:05:49 -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 I am now at the stage of testing, I have an offer of a test machine with both ISDN, and DSL with PPPOE which I will be using to test. reports in a day or so hopefully. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 16 11:35:12 1999 Delivered-To: freebsd-net@freebsd.org Received: from totally.morphed.com (totally.morphed.com [207.66.106.134]) by hub.freebsd.org (Postfix) with ESMTP id A5DA7154EF; Sat, 16 Oct 1999 11:35:05 -0700 (PDT) (envelope-from skalir@totally.morphed.com) Received: from localhost (skalir@localhost) by totally.morphed.com (8.9.3/8.9.2) with ESMTP id MAA49054; Sat, 16 Oct 1999 12:35:04 -0600 (MDT) (envelope-from skalir@totally.morphed.com) Date: Sat, 16 Oct 1999 12:35:04 -0600 (MDT) From: "Jason L. Schwab" To: freebsd-questions@freebsd.org, freebsd-net@freebsd.org Subject: good, reliable, awesome colocation.. where? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Poeple, I am looking for a good place to colo my system(s) at. I need all of this: Atleast Dual T3+ backbone connection to the internet, a full c class (255 ips(with reserse control)) My systems on average pull about 30K/sec contantly and I just want a damn good uplink that can let me pull more than my current colo place which has too many dialups on only four t1's... i can only pull like 40K/sec on average, I would like to pull around 200 or 300K/sec (K=kilobyte) so let me know, if any one has suggestions, thankx. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 16 12: 1:38 1999 Delivered-To: freebsd-net@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 47ED814D2E; Sat, 16 Oct 1999 12:01:31 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id PAA07375; Sat, 16 Oct 1999 15:01:30 -0400 (EDT) Date: Sat, 16 Oct 1999 15:01:30 -0400 (EDT) From: Bosko Milekic To: The Hermit Hacker Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: xl0: command never completed! 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 Sat, 16 Oct 1999, The Hermit Hacker wrote: !> !>Morning all... !> !> On a 3.3-STABLE machine, being used as a Squid server, I'm getting !>a pretty continuous stream of teh following message to /var/log/messages: !> !>Oct 16 14:21:01 demeter /kernel: xl0: command never completed! !> !> Not including the "last message repeated # times" messages, I've !>got 68 of them in the last 9hrs or so... !> It appears that the xl_wait() function loops XL_TIMEOUT times if it cannot confirm that XL_STAT_CMDBUSY has been unset. If the 'command busy' bit is still set after this, that is, if the 'for' loop has gone around XL_TIMEOUT times, then that message is printed. Although I'm not near certain, you _may_ want to try incresing XL_TIMEOUT (see if_xlreg.h) and seeing what you get. Regards, Bosko. -- Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 16 12:29: 7 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 2D60914EC0 for ; Sat, 16 Oct 1999 12:29:05 -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.3) with ESMTP id OAA81590; Sat, 16 Oct 1999 14:28:57 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Sat, 16 Oct 1999 14:28:56 -0500 (CDT) From: Chris Dillon To: ckwen Cc: freebsd-net@FreeBSD.ORG Subject: Re: can two fast ethernet cards work in a freebsd box ? In-Reply-To: <199910161104.TAA26753@eembox.ee.ncku.edu.tw> 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, 16 Oct 1999, ckwen wrote: > > Thanks to Wes Peters and Martin Machacek. > Now the hub's 100 Mbps LED goes on again after the execution > of ifconfig command. The parameters I set in ifconfig are > "media 100baseTX mediaopt full-duplex." > Neither of them can be omitted. If this really is a HUB as you have been saying all this time, and not a SWITCH, you don't want to be using full-duplex. > I'll observe for some days to see if the link becomes unstable or > not after I force it to work with 100baseTX/full-duplex mode. > > > Cheng-Kang Wen > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > -- 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 16 16: 4:11 1999 Delivered-To: freebsd-net@freebsd.org Received: from gw.caamora.com.au (jonath5.lnk.telstra.net [139.130.41.237]) by hub.freebsd.org (Postfix) with ESMTP id 47CD014D35 for ; Sat, 16 Oct 1999 16:03:59 -0700 (PDT) (envelope-from jon@gw.caamora.com.au) Received: (from jon@localhost) by gw.caamora.com.au (8.8.8/8.8.8) id JAA23951; Sun, 17 Oct 1999 09:03:24 +1000 (EST) (envelope-from jon) Message-ID: <19991017090323.A23931@caamora.com.au> Date: Sun, 17 Oct 1999 09:03:23 +1000 From: jonathan michaels To: Chris Dillon , ckwen Cc: freebsd-net@FreeBSD.ORG Subject: Re: can two fast ethernet cards work in a freebsd box ? Mail-Followup-To: Chris Dillon , ckwen , freebsd-net@FreeBSD.ORG References: <199910161104.TAA26753@eembox.ee.ncku.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Chris Dillon on Sat, Oct 16, 1999 at 02:28:56PM -0500 X-Operating-System: FreeBSD gw.caamora.com.au 2.2.7-RELEASE i386 X-Mood: i'm alive, if it counts Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Oct 16, 1999 at 02:28:56PM -0500, Chris Dillon wrote: > On Sat, 16 Oct 1999, ckwen wrote: > > > > > Thanks to Wes Peters and Martin Machacek. > > Now the hub's 100 Mbps LED goes on again after the execution > > of ifconfig command. The parameters I set in ifconfig are > > "media 100baseTX mediaopt full-duplex." > > Neither of them can be omitted. > > If this really is a HUB as you have been saying all this time, and not > a SWITCH, you don't want to be using full-duplex. ummm, this may be a silly question, if so would you (or anybody else) be so kind as to reply off list as to why and what the difference would be in this regard i've just recently gotten a couple of 100basetx nics for my three pci based computers and have started to save fro a 100basetx hub, i was then told that a swithch would be better, especially if i had lots of collisions. since mving into a new house (700 meters fron teh end of off and directly down teh middle of off teh middle of one off teh main runways of sydeny international airport. previously ultra reliable equipment has becme more than a bit quirky. i see "scanning lines" in teh tv and hear "radar chatter" on my fm tuners output and my previously quiet as a mouse power amplifier now hums and when i get my hifi and computer gear checked out it works flawlessly. but, when it come home it starts to play up. i'm hoping a switch will help in this (rf as well as audiable) noisy environment. or, am i grasping at straws ? i understand that thier isn't much i can do to "fix" this probelm or the causes, but, i'm hoping i can minimise the fallout so to speak, iff possible. regards and thanks in advance jonathan -- =============================================================================== Jonathan Michaels PO Box 144, Rosebery, NSW 1445 Australia =========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 16 21:30:38 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 7E7AD14C07 for ; Sat, 16 Oct 1999 21:30:34 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11chxo-0001mo-00; Sat, 16 Oct 1999 22:30:32 -0600 Message-ID: <380941F1.17A49348@softweyr.com> Date: Sat, 16 Oct 1999 21:26:41 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: ckwen Cc: freebsd-net@FreeBSD.ORG Subject: Re: can two fast ethernet cards work in a freebsd box ? References: <199910161104.TAA26753@eembox.ee.ncku.edu.tw> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ckwen wrote: > > Thanks to Wes Peters and Martin Machacek. > Now the hub's 100 Mbps LED goes on again after the execution > of ifconfig command. The parameters I set in ifconfig are > "media 100baseTX mediaopt full-duplex." > Neither of them can be omitted. > I'll observe for some days to see if the link becomes unstable or > not after I force it to work with 100baseTX/full-duplex mode. If you're plugging it into a hub rather than a switch and using full duplex, you're extremely lucky it's working at all. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 16 21:30:57 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id D2DA3150D5 for ; Sat, 16 Oct 1999 21:30:41 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11chxq-0001nD-00; Sat, 16 Oct 1999 22:30:35 -0600 Message-ID: <38094456.B210ECEC@softweyr.com> Date: Sat, 16 Oct 1999 21:36:54 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: jonathan michaels Cc: Chris Dillon , ckwen , freebsd-net@FreeBSD.ORG Subject: Re: can two fast ethernet cards work in a freebsd box ? References: <199910161104.TAA26753@eembox.ee.ncku.edu.tw> <19991017090323.A23931@caamora.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org jonathan michaels wrote: > > On Sat, Oct 16, 1999 at 02:28:56PM -0500, Chris Dillon wrote: > > On Sat, 16 Oct 1999, ckwen wrote: > > > > > > > > Thanks to Wes Peters and Martin Machacek. > > > Now the hub's 100 Mbps LED goes on again after the execution > > > of ifconfig command. The parameters I set in ifconfig are > > > "media 100baseTX mediaopt full-duplex." > > > Neither of them can be omitted. > > > > If this really is a HUB as you have been saying all this time, and not > > a SWITCH, you don't want to be using full-duplex. > > ummm, this may be a silly question, if so would you (or > anybody else) be so kind as to reply off list as to why and > what the difference would be in this regard Full duplex can only be used on a network where there are only two transmitters. Since hubs are a shared resource, connecting multiple transmitters together, you can only use half-duplex. Switches do not have this problem, because each switch port is a single network. As long as you plug only one NIC into each switch port, you can run that one NIC at full duplex. > i've just recently gotten a couple of 100basetx nics for my > three pci based computers and have started to save fro a > 100basetx hub, i was then told that a swithch would be better, > especially if i had lots of collisions. Yes, every machine plugged into a hub is in a shared collision domain. In a switched environment, the collision domain consists of the switch and the host, so there are NO collisions. Even an inexpensive layer 2 switch provides these benefits. > since mving into a new house (700 meters fron teh end of off > and directly down teh middle of off teh middle of one off teh > main runways of sydeny international airport. previously ultra > reliable equipment has becme more than a bit quirky. It may. A switch will regenerate each of the packets, whereas a hub only retransmits them and often will induce small timing errors itself. Unfortunately, even inexpensive switches aren't all that inexpensive. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 16 23:16:20 1999 Delivered-To: freebsd-net@freebsd.org Received: from gw.caamora.com.au (jonath5.lnk.telstra.net [139.130.41.237]) by hub.freebsd.org (Postfix) with ESMTP id 223A414CB6 for ; Sat, 16 Oct 1999 23:16:13 -0700 (PDT) (envelope-from jon@gw.caamora.com.au) Received: (from jon@localhost) by gw.caamora.com.au (8.8.8/8.8.8) id QAA24380; Sun, 17 Oct 1999 16:15:55 +1000 (EST) (envelope-from jon) Message-ID: <19991017161555.A24189@caamora.com.au> Date: Sun, 17 Oct 1999 16:15:55 +1000 From: jonathan michaels To: Wes Peters Cc: Chris Dillon , ckwen , freebsd-net@FreeBSD.ORG Subject: Re: can two fast ethernet cards work in a freebsd box ? Mail-Followup-To: Wes Peters , Chris Dillon , ckwen , freebsd-net@FreeBSD.ORG References: <199910161104.TAA26753@eembox.ee.ncku.edu.tw> <19991017090323.A23931@caamora.com.au> <38094456.B210ECEC@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <38094456.B210ECEC@softweyr.com>; from Wes Peters on Sat, Oct 16, 1999 at 09:36:54PM -0600 X-Operating-System: FreeBSD gw.caamora.com.au 2.2.7-RELEASE i386 X-Mood: i'm alive, if it counts Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org wes, dmp, chris, ckwen On Sat, Oct 16, 1999 at 09:36:54PM -0600, Wes Peters wrote: > jonathan michaels wrote: > > > > On Sat, Oct 16, 1999 at 02:28:56PM -0500, Chris Dillon wrote: > > > On Sat, 16 Oct 1999, ckwen wrote: > > > > Thanks to Wes Peters and Martin Machacek. > > > > Now the hub's 100 Mbps LED goes on again after the execution > > > > of ifconfig command. The parameters I set in ifconfig are > > > > "media 100baseTX mediaopt full-duplex." > > > > Neither of them can be omitted. > > > If this really is a HUB as you have been saying all this time, and not > > > a SWITCH, you don't want to be using full-duplex. > > ummm, this may be a silly question, if so would you (or > > anybody else) be so kind as to reply off list as to why and > > what the difference would be in this regard thanks guys, your responces private and mailinglist are muchly apreciated. i now have a clear understanding of what i need to do to to get a good (maybe not perfect) 100 mbit environment that will be built with 3 pci based pentiums (a 90 mhz, a 133 mhz and a 180 mhz ppro) that will be a development platform to build x11 based applications for use by disabled people in an intranetworked office. i apreciate your time and effort. keep you all posted and maybe the odd question in the future, freebsd is a good workhorse os. warm regards and best wishes. jonathan -- =============================================================================== Jonathan Michaels PO Box 144, Rosebery, NSW 1445 Australia =========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 16 23:36:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from gw.caamora.com.au (jonath5.lnk.telstra.net [139.130.41.237]) by hub.freebsd.org (Postfix) with ESMTP id 5F01814F21 for ; Sat, 16 Oct 1999 23:36:49 -0700 (PDT) (envelope-from jon@gw.caamora.com.au) Received: (from jon@localhost) by gw.caamora.com.au (8.8.8/8.8.8) id QAA24405; Sun, 17 Oct 1999 16:36:40 +1000 (EST) (envelope-from jon) Message-ID: <19991017163640.B24189@caamora.com.au> Date: Sun, 17 Oct 1999 16:36:40 +1000 From: jonathan michaels To: Wes Peters Cc: Chris Dillon , ckwen , freebsd-net@FreeBSD.ORG Subject: ethernet switch type and freebsd (Re: can two fast ethernet cards work in a freebsd box ?) Mail-Followup-To: Wes Peters , Chris Dillon , ckwen , freebsd-net@FreeBSD.ORG References: <199910161104.TAA26753@eembox.ee.ncku.edu.tw> <19991017090323.A23931@caamora.com.au> <38094456.B210ECEC@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <38094456.B210ECEC@softweyr.com>; from Wes Peters on Sat, Oct 16, 1999 at 09:36:54PM -0600 X-Operating-System: FreeBSD gw.caamora.com.au 2.2.7-RELEASE i386 X-Mood: i'm alive, if it counts Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Oct 16, 1999 at 09:36:54PM -0600, Wes Peters wrote: > jonathan michaels wrote: > > especially if i had lots of collisions. > > Yes, every machine plugged into a hub is in a shared collision domain. > In a switched environment, the collision domain consists of the switch > and the host, so there are NO collisions. Even an inexpensive layer 2 > switch provides these benefits. i've heard a reasonable amount of chatter, when its been raised, about switch "layer N". specifically, is thier support in freebsd fro different switch 'layers', i realise that i should "look in the code", but i'm afraid i wouldn't know what to look for. if this 'layering' is in freebsd, how effective is it and does one need to follow a specific type of layering protocol (rfc blahblah and or blabberblabber, etc). > > reliable equipment has becme more than a bit quirky. > > Unfortunately, even inexpensive switches aren't all that inexpensive. yes, more expensive than even a good hub. but, certainly much cheaper than moving house as one chappie suggested (not sarcastically) and my favoured resolution .. grin, sort off. warm regards & best wishes. jonathan -- =============================================================================== Jonathan Michaels PO Box 144, Rosebery, NSW 1445 Australia =========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message