On Fri, 9 Apr 1999, Bernd Ernesti wrote:

> On Fri Apr  9 18:05:00 1999, Paul H. Anderson wrote:
>
> Please show us the ifconfig de0 output.

This is typical of the machines I have, although atypical in the sense
that this particular machine has two interfaces (it is a gateway between
two private networks).

(de0 is plugged into a hub)
de0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:00:f8:06:83:b8
        media: Ethernet 100baseTX
        status: active
        inet 192.168.128.2 netmask 0xfffff800 broadcast 192.168.135.255
(de0 is a 10/100 full duplex capable switch)
de1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:00:f8:08:aa:fd
        media: Ethernet 100baseTX
        status: active
        inet 192.168.2.206 netmask 0xffffff00 broadcast 192.168.2.255


> Do you have an switch which supports full-duplex, if yes then and try to use
> 'media 100baseTX mediaopt full-duplex' and not autoselect.

I have one alpha plugged into both a switch and also a hub.  The hub side
is what seems to be causing the performance problems.  When I use a simple
crossover cable between two alphas (i.e. no hub or switch involved), I get
the same behaviour.

> I have problems with the autoselect mode on my 164LX, see port-alpha/6807:
> http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=6807

I have a similar problem with my de0 that is plugged into my 10/100 
switch.  However, the only way I've been able to get the link light back
on is to unplug and reinsert the cable.

Paul


+------------------------------------------------------+
| Paul Anderson           Public Data Queries, Inc.    |
| pha@pdq.com             734-213-4964(W) 994-3734(H)  |
+------------------------------------------------------+