From owner-freebsd-stable Wed Feb 3 08:04:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00511 for freebsd-stable-outgoing; Wed, 3 Feb 1999 08:04:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from horse.supranet.net (horse.supranet.net [205.164.160.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00503 for ; Wed, 3 Feb 1999 08:04:49 -0800 (PST) (envelope-from gavinb@supranet.net) Received: from rat (rat.supranet.net [205.164.160.15]) by horse.supranet.net (8.9.1/8.9.1) with SMTP id KAA06276 for ; Wed, 3 Feb 1999 10:04:47 -0600 (CST) Message-Id: <4.1.19990203100744.00b33d50@mail.supranet.net> X-Sender: gavinb@mail.supranet.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 03 Feb 1999 10:07:59 -0600 To: freebsd-stable@FreeBSD.ORG From: Benjamin Gavin Subject: Re: 3Com 3C509B Oddities Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Just to let everyone know... I have replaced the 3c509 with an Intel Pro/100. The crd came up fine, and I am not having any network trouble with it. It must be a problem with the 3C509s... This can't be too good, since these cards are _very_ widely used, both in our organization, and I am sure in many others... Ben At 09:57 AM 2/3/99 -0600, you wrote: >Hi, > Just to clear everything up... > >1) I am not having a problem with conflicting IPs, I am fully aware that >sharing IPs doesn't work. > >2) I am also using internal, non-routable IPs running through a firewall >(IPFW 3.0-STABLE) running NAT. The Internal network is running 10MBit >switched using an HP 24-port switch (that may be where the floating MAC >Addresses are coming from...) > >3) It is an ISA _3C509_ that is giving me trouble, not the 905. > > I am still having some very interesting problems. I will state them >here, then probably throw another ethernet card in the machine to see if >they are limited to just that card/OS combination, or to the OS itself. >Here are the problems I am having... > >1) I am able to flood ping out from the machine to the firewall. >2) I am able to flood ping from the firewall to the machine. >3) I am unable to FTP to anywhere from the machine and maintain a decent >datastream, this includes passive and active mode transfers. The >connection starts, then stalls itself, never to be retrieved again. Even >'ifconfig ep0 up' doesn't do the trick. >4) I am able to FTP from the machine (file /kernel.GENERIC) >5) I am able to telnet to/from the machine just fine > > I don't have the time to test every network service, but I think this is >some highly non-standard behavior that we are seeing here. The interesting >thing is this... The firewall is also using two 3C509s and it is running >an earlier version of 3.0-STABLE, possibly about 2-3 weeks old, maybe as >much as a month. What has changed since then??? Anyone? > >Ben Gavin > >At 09:09 AM 2/3/99 +1100, you wrote: >>> I had a 3C509B in a 2.2.8 machine for a while with no problems... I haven't >>> had it in a 3.0 machine yet - I'm using a DEC Tulip card in it right now. >>> Maybe 3.0 broke something? >>> >> >>Nope. I have been using a 905B since 3.0-R and now 3.0-Stable with no >>problems at all: >> >>>xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 11 on >>pci0.17.0 >>>xl0: Ethernet address: 00:10:5a:a9:84:33 >>>xl0: autoneg complete, link status good (full-duplex, 100Mbps) >> >>The messages the original poster was getting about ether addresses moving >>probably means that several machines are attempting to use the same IP address >>and they are fighting over it. This explains why it works periodically - when >>this machine has 'control' it receives packets, but as soon as one of the >other >>machines attempts to use the net, it 'steals' the ARP entries and this machine >>stops. It would also explain the failing ftps: when another machine >steals the >>IP address, the in-progress TCP session will get a RST because the new machine >>has no knowledge of the open session, causing the FTP server to drop the >>connection even when this machine steals back the IP address. >> >>Sharing IPs is A Bad Thing. >> >> >> >> >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-stable" in the body of the message > >/--------------------------------------------------------------------------/ > Benjamin Gavin - Senior Consultant > > *********** NO SPAM!! ************ > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message /--------------------------------------------------------------------------/ Benjamin Gavin - Senior Consultant *********** NO SPAM!! ************ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message