I recently installed a pair of LinkSys Fast 10/100 cards. One in a Linux PC
(RH 5.1 -- kernel compiled with tulip.c v90) and the other in a Windows 95
box.
I can ping localhost, loopback, and the local IP address on each PC. But I
can't ping either machine from the other. I had this working for a short
time, but it stopped working when I rebooted Linux (just once, to test my
boot scripts).
I'm using the IP addresses in all cases, so name resolution shouldn't be a
factor. I have a 4-port hub (LinkSys) and I can clearly see from watching
the LED's that data is making it from the Windows PC to the hub. When I
ping the Windows PC from Linux, I don't see as much activity as when Windows
tries to ping the other way. Sometimes I don't see a noticeable "blip" for
10 or 15 seconds, but I do occasionally see something. There are only two
PC's
on the hub which is not uplinked, so I doubt there is a congestion/collision
problem.
I have the routing set up as explained below.
Linux IP address: 192.168.0.3
Here are my Linux network configuration commands:
ifconfig eth0 192.168.0.3 netmask 255.255.255.0 up
ifconfig lo 127.0.0.0
route add -net 192.168.0.0 netmask 255.255.255.0 eth0
route add -host 127.0.0.1 lo # i think this is it. I can't look
right now -- loopback works for me though
# windows seems to be working
Windows (static) IP address: 192.168.0.2
Windows netmask 255.255.255.0
One more thing that might be important: shortly after running the ifconfig
for eth0, I get a "transmitter stopped" message on the console. When I look
in /var/log/messages I see something about "switching to half-duplex". I
already know I can't use full duplex with a simple hub, but how the heck do
I keep it from doing that (full duplex) in the first place? And is that my
overall problem?
I read the NET-3-HOWTO. I read man pages for ifconfig, route, ping, etc. I
went to LinkSys.com, read all of their HOWTOs and FAQs and got the latest
tulip.c driver. I checked DejaNews with every possible permutation of
keywords I could think of! Is there some other archive source I should be
checking (aside from man pages and HOWTOs)?
Oh, I also tried cycling the power to the hub in case it was paritioning the
"LAN". I thought it might have interpreted the Linux PCs initial attempt at
full duplex as an error condition worthy of paritioning. It didn't help
though.
I'd be grateful if anyone could help me on this. I've be trying for two
days now. Any ideas, especially stupid ones, are appreciated (since it's
probably a stupid mistake on my part that caused all this).
Thanks!!
Robert Glover -- [EMAIL PROTECTED]
-----------------------------------------------
This document contains text or data which, if
read, could convey an opinion -- an opinion
that may differ from that of the company.
-----------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
