second LAN-Port does not work

Hi,

on my Epia-pd6000 Mainboard on which Suse 9.1 runs, works the second LAN
eth1 not. Under Windows 98 works both LAN ports without problems.

I have the following konfig:

eth0 has the IP 192.168.0.6
eth1 has the IP 192.168.0.5

PC (192.168.0.1) -- Switch (Linksys WRT54GS) -- eth0 (EPIA PC) eth1 --
Satreceiver Dreambox (192.168.0.2)


From the PC, which hangs on the switch, I can ping eth0 and eth1.


If I put the switch on lan1, I can ping neither eth0 nor eth1.

I have for test with yast eth0 deleted however eth1 did not work.

eth0 and eth1 are in the same subnet because I have in the switch no
free port.

someone has an idea?


# route
Kernel IP Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.0.191 0.0.0.0 UG 0 0 0 eth0


Here is the dmesg Output:

via-rhine.c:v1.10-LK1.1.19-2.5 July-12-2003 Written by Donald Becker
http://www.scyld.com/network/via-rhine.html

eth0: VIA VT6105 Rhine-III (rev 8b)at 0xd000, 00:40:63:da:d4:f7, IRQ 12.
eth0: MII PHY found at address 1, status 0x7869 advertising 05e1 Link 45e1
eth1: VIA VT6102 Rhine-II (rev 74) at 0xe800, 00:40:63:da:d5:66, IRQ 11.
eth1: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 41e1.

eth1: Setting full-duplex based on MII #1 link partner capability of 41e1.
SFW2-INext-ACC-TCP IN=eth0 OUT=
MAC=00:40:63:da:d4:f7:00:0e:a6:87:a0:3e:08:00 SRC=192.168.0.1
DST=192.168.0.5 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=32963 DF PROTO=TCP
SPT=32919 DPT=22 WINDOW=5840 RES=0x00 SYN URGP=0 OPT
(020405B40402080A004039110000000001030300)

thanks
Ralf

Ralf Kleemann wrote:
> Hi,
>
> on my Epia-pd6000 Mainboard on which Suse 9.1 runs, works the second LAN
> eth1 not. Under Windows 98 works both LAN ports without problems.
>
> I have the following konfig:
>
> eth0 has the IP 192.168.0.6
> eth1 has the IP 192.168.0.5
>
> PC (192.168.0.1) -- Switch (Linksys WRT54GS) -- eth0 (EPIA PC) eth1 --
> Satreceiver Dreambox (192.168.0.2)
>
>
> From the PC, which hangs on the switch, I can ping eth0 and eth1.
>
>
> If I put the switch on lan1, I can ping neither eth0 nor eth1.
>
> I have for test with yast eth0 deleted however eth1 did not work.
>
> eth0 and eth1 are in the same subnet because I have in the switch no
> free port.
>
> someone has an idea?


Yes - you're confusing routing by having two interfaces in
the same local network. Don't.

What would you like to do with the two interfaces?

Please note that the speed of a LAN does not increase any
by connecting two interfaces in parallel between a switch
and a computer (called host in IP-speak).

HTH

--

Tauno Voipio
tauno voipio (at) iki fi

Tauno Voipio schrieb:
> Ralf Kleemann wrote:

>> someone has an idea?
>
>
> Yes - you're confusing routing by having two interfaces in
> the same local network. Don't.

I have changed the subnet of eth1:

eth0 has the IP 192.168.0.6
eth1 have I changed to IP 192.168.1.5
the Dreambox Ip have I changed to 192.168.1.2

Now works eth1, but I will eth0 and eth1 in the same subnet.

Is there a possibility (e.g. iptables) that are both interfaces in the
same subnet?

> What would you like to do with the two interfaces?

I will use the two interfaces as a kind of switch.

> Please note that the speed of a LAN does not increase any
> by connecting two interfaces in parallel between a switch
> and a computer (called host in IP-speak).

I don't need the the full speed, the dreambox can anyway no more than
30MBit.

Thanks
Ralf

Ralf Kleemann wrote:
> Tauno Voipio schrieb:
>
>> Ralf Kleemann wrote:
>
>
>>> someone has an idea?
>>
>>
>>
>> Yes - you're confusing routing by having two interfaces in
>> the same local network. Don't.
>
>
> I have changed the subnet of eth1:
>
> eth0 has the IP 192.168.0.6
> eth1 have I changed to IP 192.168.1.5
> the Dreambox Ip have I changed to 192.168.1.2
>
> Now works eth1, but I will eth0 and eth1 in the same subnet.
>
> Is there a possibility (e.g. iptables) that are both interfaces in the
> same subnet?

Would you now tell what you're intending to do with the two nets?
Do you want to route between the networks?
Do you want to connect the computers together without a hub/switch?

There is a way to use several interfaces so that they
use a common IP address: bridging. There is a mini-HOWTO
in the Linux Documentation Project.

--

Tauno Voipio
tauno voipio (at) iki fi

Tauno Voipio schrieb:
> Ralf Kleemann wrote:
>
>> Tauno Voipio schrieb:
>>
>>> Ralf Kleemann wrote:
>>
>>
>>
>>>> someone has an idea?
>>>
>>>
>>>
>>>
>>> Yes - you're confusing routing by having two interfaces in
>>> the same local network. Don't.
>>
>>
>>
>> I have changed the subnet of eth1:
>>
>> eth0 has the IP 192.168.0.6
>> eth1 have I changed to IP 192.168.1.5
>> the Dreambox Ip have I changed to 192.168.1.2
>>
>> Now works eth1, but I will eth0 and eth1 in the same subnet.
>>
>> Is there a possibility (e.g. iptables) that are both interfaces in the
>> same subnet?
>
>
> Would you now tell what you're intending to do with the two nets?
> Do you want to connect the computers together without a hub/switch?
Yes

The EPIA-PC is also a Samba- and NFS-Server for the PC's and the
Dreambox. I want also copy Movies between the PC and the Dreambox.

Ralf

>>
>> Would you now tell what you're intending to do with the two nets?
>> Do you want to connect the computers together without a hub/switch?
>
> Yes
>
> The EPIA-PC is also a Samba- and NFS-Server for the PC's and the
> Dreambox. I want also copy Movies between the PC and the Dreambox.

Good.

Would you now please make an ASCII scetch / list of all the
computers, network connections and hubs/switches involved, so we
could make an intelligent suggestion.

Also, please list which boxes you do have control of,
and which cannot be changed.

--

Tauno Voipio
tauno voipio (at) iki fi

Tauno Voipio schrieb:
>>>
>>> Would you now tell what you're intending to do with the two nets?
>>> Do you want to connect the computers together without a hub/switch?
>>
>>
>> Yes
>>
>> The EPIA-PC is also a Samba- and NFS-Server for the PC's and the
>> Dreambox. I want also copy Movies between the PC and the Dreambox.
>
>
> Good.
>
> Would you now please make an ASCII scetch / list of all the
> computers, network connections and hubs/switches involved, so we
> could make an intelligent suggestion.
>
> Also, please list which boxes you do have control of,
> and which cannot be changed.

WLAN AP/Switch (Linksys WRT54G) IP 192.168.0.191 connected with the
DSL-Modem and one PC. This is in another House.

WLAN Connection

WLAN AP/Switch (Linksys WRT54GS) IP 192.168.0.190
SWITCH Port 1: PC with IP 192.168.0.1 with Windows and Suse 9.1
SWITCH Port 2: PC with IP 192.168.0.4 with Windows
SWITCH Port 3: EPIA PC with LAN0 IP 192.168.0.5
SWITCH Port 4: Reserved for a further Sat-Receiver with 192.168.0.3

EPIA PC LAN1 (IP 192.168.0.6, if necessary also 192.168.1.6) is
connected with the Dreambox (IP 192.168.0.2, if necessary also 192.168.1.2).

The Defaultgateway of all PC and the switch is 192.168.0.191

The PC in the another House does not have to connect to the Dreambox.

In principle can at all PC and switch (but in the another House with
difficulty) be changed.


Thanks Ralf

Ralf Kleemann wrote:
> Tauno Voipio schrieb:
>
>>>>
>>>> Would you now tell what you're intending to do with the two nets?
>>>> Do you want to connect the computers together without a hub/switch?
>>>
>>>
>>>
>>> Yes
>>>
>>> The EPIA-PC is also a Samba- and NFS-Server for the PC's and the
>>> Dreambox. I want also copy Movies between the PC and the Dreambox.
>>
>>
>>
>> Good.
>>
>> Would you now please make an ASCII scetch / list of all the
>> computers, network connections and hubs/switches involved, so we
>> could make an intelligent suggestion.
>>
>> Also, please list which boxes you do have control of,
>> and which cannot be changed.
>
>
> WLAN AP/Switch (Linksys WRT54G) IP 192.168.0.191 connected with the
> DSL-Modem and one PC. This is in another House.
>
> WLAN Connection
>
> WLAN AP/Switch (Linksys WRT54GS) IP 192.168.0.190
> SWITCH Port 1: PC with IP 192.168.0.1 with Windows and Suse 9.1
> SWITCH Port 2: PC with IP 192.168.0.4 with Windows
> SWITCH Port 3: EPIA PC with LAN0 IP 192.168.0.5
> SWITCH Port 4: Reserved for a further Sat-Receiver with 192.168.0.3
>
> EPIA PC LAN1 (IP 192.168.0.6, if necessary also 192.168.1.6) is
> connected with the Dreambox (IP 192.168.0.2, if necessary also
> 192.168.1.2).
>
> The Defaultgateway of all PC and the switch is 192.168.0.191
>
> The PC in the another House does not have to connect to the Dreambox.
>
> In principle can at all PC and switch (but in the another House with
> difficulty) be changed.

Fine.

So, you'd like to extend the 4-port switch of the WLAN AP/Switch
with the Linux box (called EPIA).

I see some possibilities:

1. Make the extension at link layer, so the Dreambox will be a
member of the subnet in the AP. This is effected by bridging
eth0 and eth1 into one bridged interface (with one IP address).

2. Make the extension at IP layer, so the Dreambox and the corresponding
Ethernet interface will be a separate subnet (like what you did
with the 192.168.1.x subnet).

If directly routed, the WLAN subnet partipicants have to know
that the separate subnet (192.168.1.x) is behind the EPIA box.
If it's not possible to modify the routing tables of all WLAN
subnet participants, there are still solutions:

2.a) Make the EPIA box respond to the ARP requests for the Dreambox.
This is called Proxy ARP (Google for it).

2.b) Make the EPIA box act as a NAT router for the Dreambox subnet.

3. Split the 192.168.0.x subnet between the WLAN and the Dreambox
subnets. With the current address assignments, this is doable,
but somewhat complicated.

HTH

--

Tauno Voipio
tauno voipio (at) iki fi

Tauno Voipio schrieb:
> Ralf Kleemann wrote:
>
>> WLAN AP/Switch (Linksys WRT54GS) IP 192.168.0.190
>> SWITCH Port 1: PC with IP 192.168.0.1 with Windows and Suse 9.1
>> SWITCH Port 2: PC with IP 192.168.0.4 with Windows
>> SWITCH Port 3: EPIA PC with LAN0 IP 192.168.0.5
>> SWITCH Port 4: Reserved for a further Sat-Receiver with 192.168.0.3
>>
>> EPIA PC LAN1 (IP 192.168.0.6, if necessary also 192.168.1.6) is
>> connected with the Dreambox (IP 192.168.0.2, if necessary also
>> 192.168.1.2).
>>
>> The Defaultgateway of all PC and the switch is 192.168.0.191
>>
>
> Fine.
>
> So, you'd like to extend the 4-port switch of the WLAN AP/Switch
> with the Linux box (called EPIA).
>
> I see some possibilities:
>
> 1. Make the extension at link layer, so the Dreambox will be a
> member of the subnet in the AP. This is effected by bridging
> eth0 and eth1 into one bridged interface (with one IP address).

Means this, that I must compile the kernel of the EPIA-PC new?

And means this also, that the EPIA-PC passed all Packets from the
dreambox to the switch and the dreambox cannot access directly to the
EPIA-PC?


> 2. Make the extension at IP layer, so the Dreambox and the corresponding
> Ethernet interface will be a separate subnet (like what you did
> with the 192.168.1.x subnet).
>
> If directly routed, the WLAN subnet partipicants have to know
> that the separate subnet (192.168.1.x) is behind the EPIA box.
> If it's not possible to modify the routing tables of all WLAN
> subnet participants, there are still solutions:
>
> 2.a) Make the EPIA box respond to the ARP requests for the Dreambox.
> This is called Proxy ARP (Google for it).

Which advantage has this opposite to routing? is this faster?


> 2.b) Make the EPIA box act as a NAT router for the Dreambox subnet.

I have in the EPIA-PC with YAST IP-forwarding activated.

Are this route ok?

PC with the IP 192.168.0.1:
route add 192.168.1.0 mask 255.255.255.0 192.168.0.5

Dreambox with the IP 192.168.1.2:
route add 192.168.0.0 mask 255.255.255.0 192.168.1.6

Thanks Ralf

Ralf Kleemann wrote:
> Tauno Voipio schrieb:
>
>> Ralf Kleemann wrote:
>>
>>> WLAN AP/Switch (Linksys WRT54GS) IP 192.168.0.190
>>> SWITCH Port 1: PC with IP 192.168.0.1 with Windows and Suse 9.1
>>> SWITCH Port 2: PC with IP 192.168.0.4 with Windows
>>> SWITCH Port 3: EPIA PC with LAN0 IP 192.168.0.5
>>> SWITCH Port 4: Reserved for a further Sat-Receiver with 192.168.0.3
>>>
>>> EPIA PC LAN1 (IP 192.168.0.6, if necessary also 192.168.1.6) is
>>> connected with the Dreambox (IP 192.168.0.2, if necessary also
>>> 192.168.1.2).
>>>
>>> The Defaultgateway of all PC and the switch is 192.168.0.191
>>>
>>
>> Fine.
>>
>> So, you'd like to extend the 4-port switch of the WLAN AP/Switch
>> with the Linux box (called EPIA).
>>
>> I see some possibilities:
>>
>> 1. Make the extension at link layer, so the Dreambox will be a
>> member of the subnet in the AP. This is effected by bridging
>> eth0 and eth1 into one bridged interface (with one IP address).
>
>
> Means this, that I must compile the kernel of the EPIA-PC new?

Maybe. In many modern kernels the bridging is already available.
For details, start at <http://bridge.sourceforge.net/>.

> And means this also, that the EPIA-PC passed all Packets from the
> dreambox to the switch and the dreambox cannot access directly to the
> EPIA-PC?

No.

>> 2. Make the extension at IP layer, so the Dreambox and the corresponding
>> Ethernet interface will be a separate subnet (like what you did
>> with the 192.168.1.x subnet).
>>
>> If directly routed, the WLAN subnet partipicants have to know
>> that the separate subnet (192.168.1.x) is behind the EPIA box.
>> If it's not possible to modify the routing tables of all WLAN
>> subnet participants, there are still solutions:
>>
>> 2.a) Make the EPIA box respond to the ARP requests for the Dreambox.
>> This is called Proxy ARP (Google for it).
>
>
> Which advantage has this opposite to routing? is this faster?

You do not need to split the subnet nor create a new subnet with NAT.

>> 2.b) Make the EPIA box act as a NAT router for the Dreambox subnet.
>
>
> I have in the EPIA-PC with YAST IP-forwarding activated.
>
> Are this route ok?
>
> PC with the IP 192.168.0.1:
> route add 192.168.1.0 mask 255.255.255.0 192.168.0.5
>
> Dreambox with the IP 192.168.1.2:
> route add 192.168.0.0 mask 255.255.255.0 192.168.1.6

That's not enough: if the hosts outside of the EPIA and Dreambox
do not know that the Dreambox sits behind the EPIA, you need to
tell everybody (including the WLAN router) that the gateway to
the Dreambox subnet is the EPIA.

For NAT, you have to use iptables (or some of the front-ends for it)
to create the address translation/filtering.

For details, start at
<http://people.netfilter.org/rusty/unreliable-guides/>.

HTH

--

Tauno Voipio
tauno voipio (at) iki fi