Realtek8139 problem under SuSE 9.2

Hi,
after installing network cards REALTEK 8139 on two PCs under
SuSE 9.2 with the OS detecting both adapters correctly I
cannot even connect one PC to the other by *ping* command.
I use fixed local IP addresses, hardware connection directly
(without switch resp. hub),
Pinging in either direction from WinXP partition to WinXP
partition on the same machines does not cause any problems.
Is there anything known about driver problems ?
May somebody help me ?
Thanks so far,
atreyu.

atreyu wrote:
> Hi,
> after installing network cards REALTEK 8139 on two PCs under
> SuSE 9.2 with the OS detecting both adapters correctly I
> cannot even connect one PC to the other by *ping* command.
> I use fixed local IP addresses, hardware connection directly
> (without switch resp. hub),
> Pinging in either direction from WinXP partition to WinXP
> partition on the same machines does not cause any problems.
> Is there anything known about driver problems ?
> May somebody help me ?
> Thanks so far,
> atreyu.

There should be no problem with the 8139 driver.

Check if the lights at the backside of the cards are blinking while
pinging. If so, make sure the firewall is temporarily disabled and try
again.

If these steps do not help, post output of "/sbin/ifconfig" and "lspci
-v" of both systems.

Eric

atreyu wrote:
> Hi,
> after installing network cards REALTEK 8139 on two PCs under
> SuSE 9.2 with the OS detecting both adapters correctly I
> cannot even connect one PC to the other by *ping* command.
> I use fixed local IP addresses, hardware connection directly
> (without switch resp. hub),
> Pinging in either direction from WinXP partition to WinXP
> partition on the same machines does not cause any problems.
> Is there anything known about driver problems ?
> May somebody help me ?
> Thanks so far,
> atreyu.

Do the link LEDs on the cards light up?

To connect two computers directly, you need
a cross-over cable where the transmit pair
wires of computer A are wired to receive pair
of computer B and vice versa.

Please check also that the fixed local addresses
are in the same subnet, and not the very first
or very last addresses in the subnet (the first
address used to be the network address and the
last address is the local broadcast address).

This implies also that the subnet masks are
identical.

--

Tauno Voipio
tauno voipio (at) iki fi

atreyu wrote:

> Hi,
> after installing network cards REALTEK 8139 on two PCs under
> SuSE 9.2 with the OS detecting both adapters correctly I
> cannot even connect one PC to the other by *ping* command.
> I use fixed local IP addresses, hardware connection directly
> (without switch resp. hub),
> Pinging in either direction from WinXP partition to WinXP
> partition on the same machines does not cause any problems.
> Is there anything known about driver problems ?
> May somebody help me ?
> Thanks so far,
> atreyu.

Is shorewall running? If so :-
#:shorewall stop


--
Regards,
Peter.
http://www.pelicom.net.nz

atreyu wisely suggested:

> Hi,
> after installing network cards REALTEK 8139 on two PCs under
> SuSE 9.2 with the OS detecting both adapters correctly I
> cannot even connect one PC to the other by *ping* command.
> I use fixed local IP addresses, hardware connection directly
> (without switch resp. hub),
> Pinging in either direction from WinXP partition to WinXP
> partition on the same machines does not cause any problems.
> Is there anything known about driver problems ?
> May somebody help me ?
> Thanks so far,
> atreyu.
Are you sure your network cards are up? $: ifconfig -a should give you
an output similar to this:
eth0 Link encap:Ethernet HWaddr 00:11:09:22:BE:81
inet addr:195.159.171.130 Bcast:195.159.171.191
Mask:255.255.255.192
inet6 addr: fe80::211:9ff:fe2a:9e81/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17420472 errors:0 dropped:0 overruns:0 frame:0
TX packets:12881572 errors:89 dropped:0 overruns:0
carrier:89
collisions:335050 txqueuelen:1000
RX bytes:403929301 (385.2 MiB) TX bytes:762245176 (726.9
MiB)
Interrupt:193 Base address:0xe600

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4868774 errors:0 dropped:0 overruns:0 frame:0
TX packets:4868774 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2060942120 (1.9 GiB) TX bytes:2060942120 (1.9 GiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
--
You need to look for "UP" "RUNNING" and that you have an IP address,
subnet mask and gateway that makes sense.
Can you ping the localhost?

regards,
Hans Poppe
*************
System failure is not an option.
It comes bundled with Windows.

Eric Teuber wrote:

> There should be no problem with the 8139 driver.
>
> Check if the lights at the backside of the cards are
> blinking while pinging. If so, make sure the firewall is
> temporarily disabled and try again.
>
> If these steps do not help, post output of
> "/sbin/ifconfig" and "lspci -v" of both systems.
>
> Eric

There are obviously no lights at the backside of the card.
The outputs are as follows:

# Output of <ifconfig> on PC 1

eth0 Link encap:Ethernet HWaddr 00:0E:2E:6C:AF:E5
inet addr:192.168.1.2 Bcast:192.168.1.255
Mask:255.255.255.0
inet6 addr: fe80::20e:2eff:fe6c:afe5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:1000
RX bytes:60 (60.0 b) TX bytes:1304 (1.2 Kb)
Interrupt:11 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

# Output of <ifconfig> on PC 0

eth0 Link encap:Ethernet HWaddr 00:0E:2E:6CB:A8
inet addr:192.168.1.3 Bcast:192.168.1.255
Mask:255.255.255.0
inet6 addr: fe80::20e:2eff:fe6c:dba8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:1000
RX bytes:844 (844.0 b) TX bytes:200 (200.0 b)
Interrupt:10 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:60 errors:0 dropped:0 overruns:0
frame:0
TX packets:60 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:3912 (3.8 Kb) TX bytes:3912 (3.8 Kb)

# Output of <lspci -v> concerning network device on PC 1:

0000:00:0b.0 Ethernet controller: Realtek Semiconductor Co.,
Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at 6200
Memory at e4000000 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2

# Output of <lspci -v> concerning network device on PC 0:

0000:00:0a.0 Ethernet controller: Realtek Semiconductor Co.,
Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at d400
Memory at ea000000 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2

Thanks so far,
atreyu.

Tauno Voipio wrote:


> Do the link LEDs on the cards light up?
>
> To connect two computers directly, you need
> a cross-over cable where the transmit pair
> wires of computer A are wired to receive pair
> of computer B and vice versa.
>
> Please check also that the fixed local addresses
> are in the same subnet, and not the very first
> or very last addresses in the subnet (the first
> address used to be the network address and the
> last address is the local broadcast address).
>
> This implies also that the subnet masks are
> identical.
>

There are no LEDs on the card, as far as I can see.

The hardware connection does work satisfyingly on the same
two PCs under WinXP.

There are no address conflicts with network or broadcast
address, and the subnet mask is identical on both sides.

Thank you for thiese hints,
atreyu.

Hans Poppe wrote:

> Are you sure your network cards are up? $: ifconfig -a
> should give you an output similar to this:
> eth0 Link encap:Ethernet HWaddr 00:11:09:22:BE:81
> inet addr:195.159.171.130 Bcast:195.159.171.191
> Mask:255.255.255.192
> inet6 addr: fe80::211:9ff:fe2a:9e81/64
> Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500
> Metric:1 RX packets:17420472 errors:0 dropped:0
> overruns:0 frame:0 TX packets:12881572 errors:89
> dropped:0 overruns:0
> carrier:89
> collisions:335050 txqueuelen:1000
> RX bytes:403929301 (385.2 MiB) TX
> bytes:762245176 (726.9
> MiB)
> Interrupt:193 Base address:0xe600
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:4868774 errors:0 dropped:0 overruns:0
> frame:0 TX packets:4868774 errors:0 dropped:0
> overruns:0 carrier:0 collisions:0 txqueuelen:0
> RX bytes:2060942120 (1.9 GiB) TX
> bytes:2060942120 (1.9 GiB)
>
> sit0 Link encap:IPv6-in-IPv4
> NOARP MTU:1480 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0
> frame:0 TX packets:0 errors:0 dropped:0
> overruns:0 carrier:0 collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

The cards are "UP", and the addresses should be correct.

Pinging the localhost (127.0.0.1) works fine.

Thank you for the hints,
atreyu.

Peter Lowrie wrote:

>> Is shorewall running? If so :-
> #:shorewall stop
>

It is not.

Thanks so far,
atreyu.

atreyu wrote:
> The outputs are as follows:
>
> # Output of <ifconfig> on PC 1
>
> eth0 Link encap:Ethernet HWaddr 00:0E:2E:6C:AF:E5
> inet addr:192.168.1.2 Bcast:192.168.1.255
> Mask:255.255.255.0
> inet6 addr: fe80::20e:2eff:fe6c:afe5/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1 errors:0 dropped:0 overruns:0 frame:0
> TX packets:15 errors:0 dropped:0 overruns:0
> carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:60 (60.0 b) TX bytes:1304 (1.2 Kb)
> Interrupt:11 Base address:0x6000
>
>
> # Output of <ifconfig> on PC 0
>
> eth0 Link encap:Ethernet HWaddr 00:0E:2E:6CB:A8
> inet addr:192.168.1.3 Bcast:192.168.1.255
> Mask:255.255.255.0
> inet6 addr: fe80::20e:2eff:fe6c:dba8/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:9 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3 errors:0 dropped:0 overruns:0
> carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:844 (844.0 b) TX bytes:200 (200.0 b)
> Interrupt:10 Base address:0x6000
>

Looks good! Check the following on both systems:

/etc/init.d/SuSEfirewall2_init status

If the firewall is used on either system shut it down by executing

/etc/init.d/SuSEfirewall2_init stop

and try again. If it is unused on both systems create a root shell
session on both systems and execute "tcpdump -v -i eth0" and let it run
(it wont come back). Later on you can kill it with CTRL-C.

Open another shell session on one system and ping the other one. Check
if there is any output in the tcpdump sessions and post the whole
scenario. Also post the following output of both systems "route -v".

Eric