Date: Tue, 2 Feb 1999 08:26:36 -0800 From: "Justin Wolf" <jjwolf@bleeding.com> To: <freebsd-stable@FreeBSD.ORG>, "Tanguy de Courson" <tanguy@itninc.net> Subject: Re: 3Com 3C509B Oddities Message-ID: <003c01be4ec8$e0481a40$06c3fe90@cisco.com>
next in thread | raw e-mail | index | archive | help
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? -Justin ----- Original Message ----- From: Tanguy de Courson <tanguy@itninc.net> To: <freebsd-stable@FreeBSD.ORG> Sent: Tuesday, February 02, 1999 8:27 AM Subject: Re: 3Com 3C509B Oddities >you know i ran into the same problem. i tried to install 3.0-RELEASE with >this card and it dowloaded all of 5 packets and then just stopped. > >i then installed 2.2.2 from an old cd and tried to cvsup and it kept >connecting to the cvsup server then timeing out. the card that was in the >machine before was an old ISA PNP card and for some reason FreeBSD would >not pick up the card no matter what i did. but it was working fine before. > does FreeBSD have a problem with the 3com 3C509B cards? > > > >At 09:16 AM 02/02/1999 -0600, you wrote: >>Hi all, >> I ran into an interesting problem yesterday when running >>3.0-19990201-STABLE installation. While trying to perform a FTP install, >>my card seemed unable to respond to ip traffic. The card was set up in PNP >>mode (0x300, IRQ 10 detected in dmesg). The card seemed to setup >>correctly, assigned 192.168.0.32 as an IP, then tried to pass some ip >>traffic through it. I ended up with about 95% of the packets dropped, but >>the link light remained on, and some of the packets were getting through at >>their normal speed (0.6 ms). >> After fighting with it for a while, I went in with the 3Com config >>program, hard assigned these values into the card, diabled PNP, and >>restarted. This led to yet another interesting behavior, in this case the >>card seemed unable to talk through the firewall, the ping times were fine, >>but the ftp wouldn't work, in either active of passive mode. I have at >>least ten other machines behind the firewall and they were all working just >>fine. >> Finally I gave up and switched it over to public IPs, after which time it >>worked fine (public IP's are on a standard hub, private IPs are on a >>switch). Anyone have an explanation here? I can't figure it out. >> I also noticed that there were a number of kernel messages where IPs were >>switching between numerous MAC addresses (don't have the exact numbers, but >>I also noticed the same thing happening on the firewall). For example: >> >>On 3.0-STABLE box: >>... /kernel: 192.168.0.1 moved from 00:...:8f to 00:...:8e >>... /kernel: 192.168.0.1 moved from 00:...:8e to 00:...:8c >>... /kernel: 192.168.0.1 moved from 00:...:8c to 00:...:8f >> >>On Firewall (3.0-STABLE): >>... /kernel: 192.168.0.32 moved from 00:...:4b to 00:...:4d >> >>Anyone got any ideas? The firewall server is running 3.0 CVSup'ed probably >>2 weeks ago. >> >>Thanks, >>Ben >> >>/------------------------------------------------------------------------- -/ >> Benjamin Gavin - Senior Consultant >> >> *********** NO SPAM!! ************ >> >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-stable" in the body of the message >> >----------------------------------------------------------- >Tanguy 'Ripper' de Courson - Internet Programmer ('Perl') at ITN >myneid - fool 'o fools, gnome 'o gnomes >"schalin666: Okay. I guess I should allow a human's right to a higher >education, so long as it doesn't ruin my pornography income" > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003c01be4ec8$e0481a40$06c3fe90>