Yes, Vidiot's theory makes sense. However, there is a slim
possibility that some switches on the hub are set wrong? Perhaps
the 'cascade' button or something similar to that effect is set
wrong on the hub itself. Bear in mind, a crossover cable IIRC is
necessary between two hubs, and the 'cascade' button has to be in
a particular state for that sort of connection. I'm babbling,
so I'll just say this:
play around with the switches (if any present) on the hub. <g>
HTH,
L.G.
On Thu, 23 Nov 2000, Jack Bowling wrote:
> Pardon the obvious hardware slant of this post but it IS using two
> versions of RH!!
>
> Here is one for the gurus. Have a 3-box linux LAN at home. It works
> with one hub perfectly but not with another with the same network
> settings. A big clue that it must have something to do with the cabling
> or internal wiring of the hub is that when monitoring a ping from one
> machine to another in realtime (usernet in gnome....real cool) with the
> "bad" hub, I can see transmit out on the eth0 but incoming is on the
> loopback!!!! And "ifconfig -a" confirms only transmit and no receive on
> the NIC. With the good hub, everything is in and out on eth0. Using
> straight-through cables from NIC to hub. Not critical since I do have a
> working hub, but would be nice to know if this can be fixed in case I
> have to use another hub of a different design.
>
> Jack Bowling
> Prince George, BC
> mailto:[EMAIL PROTECTED]
>
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
-- Generated Signature --
Carson's Observation on Footwear:
If the shoe fits, buy the other one
too.
-- End Sig --
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
