Date: Fri, 31 Aug 2007 22:48:35 +0200 From: Tobias Ernst <tobi@casino.uni-stuttgart.de> To: freebsd-questions@freebsd.org Cc: nvass@teledomenet.gr Subject: Re: strange arp problem with bge nics Message-ID: <46D87EA3.7070703@casino.uni-stuttgart.de> In-Reply-To: <200708312243.01122.nvass@teledomenet.gr> References: <46D83451.2030808@casino.uni-stuttgart.de> <46D86411.1020603@casino.uni-stuttgart.de> <200708312230.55235.nvass@teledomenet.gr> <200708312243.01122.nvass@teledomenet.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
Nikos Vassiliadis schrieb: > On Friday 31 August 2007 22:30, I correctly wrote: >> Did you try without forcing a link speed(check ifconfig -m) > s/without // > > anything useful in dmesg? No, nothing at all in dmesg. 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? If the NIC were not properly negotiated, it would not even see the broadcasts of the Windows machine, I would think. It must be something with ARP and TCP/IP in connection with that particular river, I suppose. 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. Regards Tobias -- Universität Stuttgart|Fakultät für Architektur und Stadtplanung|casinoIT 70174 Stuttgart Geschwister-Scholl-Straße 24D T +49 (0)711 121-4228 F +49 (0)711 121-4276 E office@casino.uni-stuttgart.de I http://www.casino.uni-stuttgart.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46D87EA3.7070703>