Date: Fri, 26 Sep 1997 18:43:16 +0930 From: Mike Smith <mike@smith.net.au> To: Terry Lambert <tlambert@primenet.com> Cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) Message-ID: <199709260913.SAA00775@word.smith.net.au> In-Reply-To: Your message of "Fri, 26 Sep 1997 08:20:19 GMT." <199709260820.BAA18077@usr04.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card > > (fxp0 interface). Sometimes (about 3-4 times per week) I'm getting > > troubles with IP. 127.0.0.1 pings ok, and my fxp0's address as well, > > but no other computer can see me, and I can't see any others. > > 127.0.0.1 is the loopback address. You aren't ifconfig'ing the card > to actually have that address, are you? (I have removed the term "peanut" from the following response. Feel free to reinsert it at an appropriate point to achieve the original tone.) No. He's reporting the "fxp driver dies occasionally" problem that's been seen off and on for the last few months. Pinging the loopback address is a simple confidence test in at least a little of the network code. See the section in the above paragraph where he uses English well enough to make it clear that 127.0.0.1 is *not* the address attachd to fxp0. > The 127.0.0.1 is not normally something that has anything at all to > do with the card driver. Instead, it is internally looped back; it > is a simulated interface. I don't see how shoving the interface > into promiscuous mode would help. Putting the fxp driver into promiscuous mode involves poking at bits of the interface hardware. This appears to fix whatever it is that's going wrong. If this problem hasn't already been dealt with in the -current/-stable drivers, I hope DG is looking at it. mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709260913.SAA00775>