Date: 11 Oct 1997 14:04:50 GMT From: peter@netplex.com.au (Peter Wemm) To: freebsd-current@freebsd.org Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? Message-ID: <876578689.767862@haywire.dialix.com.au> References: <Pine.BSF.3.96.971002140726.24987F-100000@shell.uniserve.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <5652.875828050@critter.freebsd.dk>,
phk@critter.freebsd.dk (Poul-Henning Kamp) writes:
> In message <Pine.BSF.3.96.971002140726.24987F-100000@shell.uniserve.com>, Tom w
> rites:
>>
>>On Thu, 2 Oct 1997, Poul-Henning Kamp wrote:
>>
>>> In message <9023.875816283@verdi.nethelp.no>, sthaug@nethelp.no writes:
>>> >> On the other hand, the only quad cards I know of are based
>>> >> on the DEC chip; I'll be trying out the Znyx quad card (I think) soon.
>>> >
>>> >We have the ZNYX 4-port 10 Mbps card, and the SMC 2-port 100 Mbps card
>>> >in a FreeBSD machine here. They work very well for us.
>>>
>>> I have a machine with 4 of the ZNYX boards (16 ports total) doing the
>>> "collapsed backbone" thing. Works like a charm, and in difference
>>> from a cisco that would cost 10 times as much, you can run tcpdump
>>> and trafshow on it :-)
>>
>> I would have liked to have been able to use a solution like that.
>>However, currently ethernet interfaces that do not have carrier/link
>>active, still show us UP. I wish that loss of carrier/link would force
>>the interface into a DOWN state automatically. I realize this would
>>require some driver changes.
>
> Well, go for it :-)
The de driver already does this, but in a different way:
peter@spinner[8:59pm]~-102> ifconfig de0
de0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 202.12.86.3 netmask 0xffffffe0 broadcast 202.12.86.31
ether 00:e0:29:06:48:ee
media: autoselect (10baseT/UTP) status: active
[yank cable]
peter@spinner[9:39pm]~-103> ifconfig de0
de0: flags=8c43<UP,BROADCAST,RUNNING,OACTIVE,SIMPLEX,MULTICAST> mtu 1500
inet 202.12.86.3 netmask 0xffffffe0 broadcast 202.12.86.31
ether 00:e0:29:06:48:ee
media: autoselect
[plug back in]
peter@spinner[9:39pm]~-104> ifconfig de0
de0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 202.12.86.3 netmask 0xffffffe0 broadcast 202.12.86.31
ether 00:e0:29:06:48:ee
media: autoselect (10baseT/UTP) status: active
peter@spinner[9:39pm]~-105>
Or, if you have the media hardwired, you get this:
peter@spinner[9:41pm]/home/peter-100# ifconfig de0 media 10baseT/UTP
peter@spinner[9:41pm]/home/peter-101# ifconfig de0
de0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 202.12.86.3 netmask 0xffffffe0 broadcast 202.12.86.31
ether 00:e0:29:06:48:ee
media: 10baseT/UTP status: active
[yank cable]
peter@spinner[9:41pm]/home/peter-102# ifconfig de0
de0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 202.12.86.3 netmask 0xffffffe0 broadcast 202.12.86.31
ether 00:e0:29:06:48:ee
media: 10baseT/UTP status: no carrier
^^^^^^^^^^^^^
However, the driver seems to have a bug here.. Once the cable is plugged
back in, the 'no carrier' status doesn't go away. :-> Not even after
using the interface again...
Cheers,
-Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?876578689.767862>