host can't attach to small network

I've got a small ethernet network consisting of two hosts and a linksys
router. These all connect to a 5-port linksys hub, where the router
attaches to "uplink". I have Windows running on one host, and Suse Linux
7.6 on the other. This setup has worked fine for a long time. Then I
tried adding a third host, with Suse 8.0, onto the hub. Used Yast to
configure the nic. Appears to load module and configure the ip just
fine as below(manually configured with a private ip).


But this interface does not function at all. I cannot ping any host on
the hub or be pinged from any other host on the hub. Furthermore, the
indicator light on the hub where this host is attached blinks steadily
with a frequency of about 8 sec. I've tried different cables on
different points on the hub to no avail. Also, the blinking is the same
even when it is the only host connected to the hub.

Network:

router: 192.168.1.1
Suse 7.6 host: 192.168.1.2
Windows host: 192.168.1.5
Suse 8.0 host: 192.168.1.10 *

* default route set to 192.168.1.1

As far as I can see this should work, I don't know what I'm missing. I
don't know what to do with this.

Thanks,

George



eth0 Link encap:Ethernet HWaddr 10:F0:10:F0:10:F0
inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:28 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0xa000 Memory:eb041000-eb041038

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1344 (1.3 Kb) TX bytes:1344 (1.3 Kb)

On Sun, 14 Sep 2003, George Bell <(E-Mail Removed)> wrote:
> I've got a small ethernet network consisting of two hosts and a linksys
> router. These all connect to a 5-port linksys hub, where the router
> attaches to "uplink". I have Windows running on one host, and Suse Linux
> 7.6 on the other. This setup has worked fine for a long time. Then I
> tried adding a third host, with Suse 8.0, onto the hub. Used Yast to
> configure the nic. Appears to load module and configure the ip just
> fine as below(manually configured with a private ip).
>
>
> But this interface does not function at all. I cannot ping any host on
> the hub or be pinged from any other host on the hub. Furthermore, the
> indicator light on the hub where this host is attached blinks steadily
> with a frequency of about 8 sec. I've tried different cables on
> different points on the hub to no avail. Also, the blinking is the same
> even when it is the only host connected to the hub.
>
> Network:
>
> router: 192.168.1.1
> Suse 7.6 host: 192.168.1.2
> Windows host: 192.168.1.5
> Suse 8.0 host: 192.168.1.10 *
>
> * default route set to 192.168.1.1
>
> As far as I can see this should work, I don't know what I'm missing. I
> don't know what to do with this.

Which nic mfr/model and which Linux module? What does 'lspci -v' show
related to the nic? If using rtl8139 module, try 8139too instead. It can
get confusing when a mfr uses several different chips for different
versions of same nic model number.

What is your hub speed (a hub only does half duplex at speed of slowest
nic, switch should be able to do full duplex at speed of peer)? You could
try 'mii-tool -A 10baseT-HD eth0' (or -F if -A does not work).

What is dhcp range of Linksys router (maybe it does not like you using
static IP within its dhcp range, or you set some IP or MAC filtering you
forgot about).

--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/

In article <(E-Mail Removed)>, George Bell wrote:
> This is a multi-part message in MIME format.

MIME and Usenet text groups do not mix. Please post your samples inline.

> But this interface does not function at all. I cannot ping any host on
> the hub or be pinged from any other host on the hub. Furthermore, the
> indicator light on the hub where this host is attached blinks steadily
> with a frequency of about 8 sec. I've tried different cables on

Sounds like a hardware problem. What does the hub's documentation say?

> eth0 Link encap:Ethernet HWaddr 10:F0:10:F0:10:F0
> inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:28 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Nothing transmitted nor received.

Is this a combo card? Maybe it thinks you want to use the BNC. You
didn't say what kind of card it is. Look for a diagnostic utility for
it. The manufacturer may provide a DOS-based one. Scyld.com might have
one for Linux.

"man mii-tool" might lead to some more clues too.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

David Efflandt wrote:

> On Sun, 14 Sep 2003, George Bell <(E-Mail Removed)> wrote:
>
>>I've got a small ethernet network consisting of two hosts and a linksys
>>router. These all connect to a 5-port linksys hub, where the router
>>attaches to "uplink". I have Windows running on one host, and Suse Linux
>>7.6 on the other. This setup has worked fine for a long time. Then I
>>tried adding a third host, with Suse 8.0, onto the hub. Used Yast to
>>configure the nic. Appears to load module and configure the ip just
>>fine as below(manually configured with a private ip).
>>
>>
>>But this interface does not function at all. I cannot ping any host on
>>the hub or be pinged from any other host on the hub. Furthermore, the
>>indicator light on the hub where this host is attached blinks steadily
>>with a frequency of about 8 sec. I've tried different cables on
>>different points on the hub to no avail. Also, the blinking is the same
>>even when it is the only host connected to the hub.
>>
>>Network:
>>
>>router: 192.168.1.1
>>Suse 7.6 host: 192.168.1.2
>>Windows host: 192.168.1.5
>>Suse 8.0 host: 192.168.1.10 *
>>
>>* default route set to 192.168.1.1
>>
>>As far as I can see this should work, I don't know what I'm missing. I
>>don't know what to do with this.
>>
>
> Which nic mfr/model and which Linux module? What does 'lspci -v' show
> related to the nic? If using rtl8139 module, try 8139too instead. It can
> get confusing when a mfr uses several different chips for different
> versions of same nic model number.


Yes, that was it - a driver problem. Large thanks for helping me out of
my mental block. I had tried with two nics - an Allied Telesyn
ATS-AT-2700 FTX/ST-001 with the amd 79c970 chip and another the
IBM-22P4901 Ethernet Pro 100 Dual Port Server Adapter with Intel
82557/8/9 chip. The lights on the hub appeared normal for the former
and blinked as described for the latter, but neither worked. Then I
swapped in an Allied Telesyn AT-2700TX ( with AMD 79c970 chip also ) and
it worked with that one. I can't figure how Suse can load modules for
adapaters that don't work.

George

George Bell <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> Content-Type: text/plain; charset=us-ascii; format=flowed
> Content-Transfer-Encoding: 7bit
>
> I've got a small ethernet network consisting of two hosts and a
> linksys router. These all connect to a 5-port linksys hub, where the
> router attaches to "uplink". I have Windows running on one host, and
> Suse Linux 7.6 on the other.

Be careful about using the uplink port on the hub. They are often
defaulting to crossover (they sometimes have a push button switch to
uncross the uplink port). The uplink is generally intended for daisy
chaining another hub or switch. Try connecting the router to one of the
normal ports on the hub.

Rgds Llanzlan.

<SNIP>

George Bell <(E-Mail Removed)> writes:

[...]

>But this interface does not function at all. I cannot ping any host on
>the hub or be pinged from any other host on the hub. Furthermore, the
>indicator light on the hub where this host is attached blinks steadily
>with a frequency of about 8 sec. I've tried different cables on
>different points on the hub to no avail. Also, the blinking is the same
>even when it is the only host connected to the hub.

[...]

If that is really a hub and not a switch, try the "mii-tool" from
http://www.scyld.com and check the NIC's settings. It's possible
that the card is setup for 100MBit whereas the rest of your network
is running on 10MBit, or vice versa. Otherwise, check the driver loaded
or try a different NIC.


Michael
--
Michael Buchenrieder * (E-Mail Removed) * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.