Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Feb 1999 08:05:20 -0800
From:      "Justin Wolf" <jjwolf@bleeding.com>
To:        <freebsd-stable@FreeBSD.ORG>, "Benjamin Gavin" <gavinb@supranet.net>
Subject:   Re: 3Com 3C509B Oddities
Message-ID:  <002f01be4ec5$e793cea0$06c3fe90@cisco.com>

next in thread | raw e-mail | index | archive | help
Just to make sure it's nothing obvious - is your subnet set correctly and
there aren't any other machines sharing the same IP, right?  What about
routers?  Just checking...

-Justin

----- Original Message -----
From: Benjamin Gavin <gavinb@supranet.net>
To: <freebsd-stable@FreeBSD.ORG>
Sent: Tuesday, February 02, 1999 7:16 AM
Subject: 3Com 3C509B Oddities


>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
>


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?002f01be4ec5$e793cea0$06c3fe90>