Better pull out the Ethernet book. Hubs cannot do full duplex. If they
tried to transmit and receive simultaneously on the same port (full
duplex) a collision would occur and they would have to step
back. Switches can do full duplex, hubs are half duplex only. Always
have been, always will be.
- rick warner
On Sat, 25 Nov 2000, Statux wrote:
> Um.. hubs do full duplex. Cat5 (and the like) cabling uses two wires for 1
> connection (one for TX and one for RX). Coax cable is only half.
>
> On Fri, 24 Nov 2000, Rick Warner wrote:
>
> >
> > This one seems to have a big problem. Not only is it flipping on speed,
> > but it has negotiated full duplex. Since a hub cannot do full-dup ....
> >
> > - rick warner
> >
> > On Fri, 24 Nov 2000, Jack Bowling wrote:
> >
> > > Hub that works is a 3Com HomeConnect 10Mbps 5-Port Hub model 3C19260.
> > >
> > > Now....stick the following hub which is a Linksys Etherfast 10/100
> > > Auto-Sensing 5-Port Workgroup Hub model EFAH05W in the circuit (this hub
> > > came with two matching Linksys cards as given above) and run the
> > > tulip-diag and here is what we get:
> > >
> > > tulip-diag.c:v2.03 7/31/2000 Donald Becker ([EMAIL PROTECTED])
> > > http://www.scyld.com/diag/index.html
> > > Index #1: Found a Lite-On PNIC-II adapter at 0x9000.
> > > Port selection is 10mpbs-serial, full-duplex.
> > > Transmit started, Receive started, full-duplex.
> > > The Rx process state is 'Waiting for packets'.
> > > The Tx process state is 'Idle'.
> > > The transmit threshold is 72.
> > > The NWay status register is 000020ce.
> > > The current PNIC-II MAC address is 00:a0:cc:36:dd:1d (a000a000
> > > 36cc1ddd).
> > > The current PNIC-II WOL address is 00:a0:cc:36:dd:1d.
> > > Internal autonegotiation state is 'Ability detect'.
> > > Use '-a' or '-aa' to show device registers,
> > > '-e' to show EEPROM contents, -ee for parsed contents,
> > > or '-m' or '-mm' to show MII management registers.
> > >
> > > Note the NWay register seems to be in a different state, and probably
> > > more importantly the autonegotiation is stuck in "Ability Detect" mode
> > > instead of "Negotiation Complete". As I write, the Port 2 indicator
> > > light on the Linksys hub is cycling between 10 and 100...apparently the
> > > hub cannot
> > > autonegotiate with its own matching card. One would be tempted to
> > > blame the hub rather than the card since the card works fine with the
> > > 3Com hub.
> > >
> >
> >
> >
> > _______________________________________________
> > Redhat-list mailing list
> > [EMAIL PROTECTED]
> > https://listman.redhat.com/mailman/listinfo/redhat-list
> >
>
> --
> -Statux
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
