Date: Wed, 16 May 2001 14:09:20 -0400 From: Vivek Khera <khera@kcilink.com> To: Gregory Neil Shapiro <gshapiro@FreeBSD.ORG> Cc: stable@FreeBSD.ORG Subject: Re: dual fxp ethernet, one doesn't "work" Message-ID: <15106.49744.612179.206448@onceler.kciLink.com> In-Reply-To: <15106.49405.953545.516995@horsey.gshapiro.net> References: <15105.44534.131385.573668@onceler.kciLink.com> <x78zjx9oww.fsf@onceler.kciLink.com> <20010516104821.A19893@nexus.root.com> <15106.49405.953545.516995@horsey.gshapiro.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "GNS" == Gregory Neil Shapiro <gshapiro@FreeBSD.ORG> writes: VK> [m02]% ifconfig -a VK> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 VK> media: autoselect (100baseTX) status: active VK> fxp1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 VK> media: autoselect (10baseT/UTP) status: active GNS> The new fxp driver works fine at 100baseTX and has problems at 10baseT. GNS> When you swapped cables, you changed the speed each was running at (I GNS> assume they are connected to different equipment, one of which supports GNS> 100baseTX, one doesn't). Hmmm.. I also put both of them on 10baseT/UTP and had the same result: the 192.168.100 net did not work, and the 192.168.200 did... Curiously, I have another machine with just one fxp0 on it, and it runs fine on the same 10baseT hub. 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?15106.49744.612179.206448>