Date: Sat, 1 Sep 2007 03:47:59 +0300 From: Nikos Vassiliadis <nvass@teledomenet.gr> To: Tobias Ernst <tobi@casino.uni-stuttgart.de>, nvass@teledomenet.gr Cc: freebsd-questions@freebsd.org Subject: Re: strange arp problem with bge nics Message-ID: <1262ce9de9ed8ac240d21624fd6b5eb0@mail.teledomenet.gr> In-Reply-To: <46D87EA3.7070703@casino.uni-stuttgart.de> References: <46D87EA3.7070703@casino.uni-stuttgart.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 31 Aug 2007 22:48:35 +0200, Tobias Ernst <tobi@casino.uni-stuttgart.de> wrote: > I don't think this is an auto negotiation issue. How can a Windows > machine that is connected to the same switch as my two FreeBSD machines > and does not even talk to them explicitly influence the autonegotation > of the FreeBSD NIC? I didn't say that a Windows machine can influence adversely a FreeBSD machine. My question was about the NIC's link status. It's crystal clear now that your links are up. But: (Symptom is that the NIC reports the link as up (PCS synched) but no traffic can be exchanged.) This message is from revision 1.71 of the bge driver. In short I would really try what's recommended there. > > It must be something with ARP and TCP/IP in connection with that > particular river, I suppose. hm, there's nothing bge-specific in TCP/IP nor ARP. > > The cards properly negotiate whatever the particular switch (tried > several, 100 and 1000) supports and I also tried setting various fixed > rates and duplex settings when using a cross link cable. This does not > change anything. > > The interface is live and running, it just does not properly perform ARP > up to the point when I either put the interface in promiscuous mode for > a while or send some Windows broadcasts. hm, what happens if you disable ARP? ifconfig intX -arp and use static ARP? I'd go the driver-fiddling way myself. HTH Nikos
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1262ce9de9ed8ac240d21624fd6b5eb0>