>OK, first things first. txqueuelen sets the size of the transmit queue,
>not the speed of the interface. Hardcoding the speed of the interface is
>a bit tricky. If you are using modules for the NIC drivers, some drivers
>take an option which sets speed of the interface. Is there a speed status
>light on the NICs? If so, what does that say? It still sounds like a
>speed mismatch; have you tried rebooting or restarting networking after
>connecting to the dual-speed hubs? That would force negotiation.
>
>- rick warner
I've never seen a 10/100 hub not negotiate speed when the cable is
connected. The hub should hve a link light and if it is a 10/100 hub,
a speed indicator for the port. Of course, it may be a real cheapy and
not have the indicators. If it has the lights, check them.
The lights were a hugh plus at a show I was recently at. During all of
the connecting of 10 and 100 equipment to the swtiches and hubs, we lost
a hub, i.e., a port died and its lights went out for a port. We had to
replace it and did so with 10/100 switches (which are preferred over hubs).
Brought the hib back and it was determined that not only was the one port
dead, the other ports were acting weird as well.
So, if you have 10/100 NICs and a 10 only hub, the NICs should connect
to the hub at 10baseT.
I just don't trust the hub.
MB
--
e-mail: [EMAIL PROTECTED]
Bart: Hey, why is it destroying other toys? Lisa: They must have
programmed it to eliminate the competition. Bart: You mean like
Microsoft? Lisa: Exactly. [The Simpsons - 12/18/99]
Visit - URL:http://www.vidiot.com/ (Your link to Star Trek and UPN)
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list