Sounds more like it could be a bug in the nic driver. I would report it to the FreeBSD people.
TimH > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Leo Clark > Sent: Thursday, November 01, 2001 8:23 AM > To: [EMAIL PROTECTED] > Subject: [EUG-LUG:3582] Paralyzed NIC > > > > Something very odd hapened to my DSL firewall FreeBSD 4.4 machine last > night. I had a friend over working on his new machine and we were > uploading a couple movies over samba. All of a sudden, the transfer > failed and the server no longer responded to anything on the local > subnet. I got on the console on the machine and it was still > workign fine > in the outside nic. ICQ, AIM and all that stuff was fine. I checked > sockstat, tried taking samba down and back up, brough the > interface up and > down, but no luck. It was even responding to pings from the internal > network. > > This is the wierd part, I launched ethereal and started > sniffing on that > card. It was receiving data! The windows boxes who were all > on dhcp were > getting very confused and useing their default IP addresses and doing > browser stuff. But the box was getting all of that, and I > could see it! > > It's like it refused to use the card even though it was > working. So I got > desperate, as I had been without connectivity for almost 15min, and > rebooted it. It was fine after the reboot. Curious. > > As I went to bed I started another large samba transfer. > Went I got up, > the same problem had come up. So I left it, and thats the way it sits > right now. > > Does anyone have any ideas as to what could be wrong? > Somethign to look > for? > > I'm running FreeBSD 4.4 Release, with 2 3cr990-tx-97's (txp0, > and txp1), > on a dual p2-450. I'm running samba version 2.0.10 (pretty > sure I got it > from the ports tree). > > Could samba be doing this? > > Thanks, > > --------------<<<((((((0))))))>>>-------------- > Leo Clark > [EMAIL PROTECTED] >
