[Soekris] impossible to link eth1, eth2, eth3 but eth0 is well working
Bryan Irvine
sparctacus at gmail.com
Sat Dec 6 06:24:03 UTC 2008
Top-posting because there's a lot here.
Try assigning different ip ranges to the other interfaces and re-test.
Bryan
-
On Fri, Dec 5, 2008 at 8:39 AM, stef <stef at aerosim.fr> wrote:
> Hi,
> I just receive on dec 2nd, my new "very expensive box" net5501-70 from
> soekris USA.
> I boot the net5501 with a 4 Go CF card and voyage-linux 0.5.2 OS
> installed in.
> My computer based on linux Ubuntu 8.04.1.is linked to the net5501.
> BIOS v 133
>
> The OS is working good and I made some tests in order to use it as a
> router.
> But it's impossible to communicate with eth1 eth2 eth3. eth0 is well
> working.
>
>
> -------------------------------------------------------------------
> >> first test : work well
> [ home PC] ---- eth0 [ net5501]
> 192.168.10.1 192.168.10.50
>
> soekris:/etc# ping -I eth0 192.168.10.1
> PING 192.168.10.1 (192.168.10.1) from 192.168.10.50 eth0: 56(84) bytes
> of data.
> 64 bytes from 192.168.10.1: icmp_seq=1 ttl=64 time=0.250 ms
> 64 bytes from 192.168.10.1: icmp_seq=2 ttl=64 time=0.174 ms
>
> stef at home:~$ ping 192.168.10.50
> PING 192.168.10.50 (192.168.10.50) 56(84) bytes of data.
> 64 bytes from 192.168.10.50: icmp_seq=1 ttl=64 time=0.242 ms
> 64 bytes from 192.168.10.50: icmp_seq=2 ttl=64 time=0.238 ms
> 64 bytes from 192.168.10.50: icmp_seq=3 ttl=64 time=0.238 ms
> >>>>>>>>>>>>>>>>>>>> OK good
>
> -------------------------------------------------------------------
> >> second test :
> [ home PC] ---- eth1 [ net5501]
> 192.168.10.1 192.168.10.51
>
> soekris:/etc# ping -I eth1 192.168.10.1
> PING 192.168.10.1 (192.168.10.1) from 192.168.10.50 eth1: 56(84) bytes
> of data.
> From 192.168.10.50 icmp_seq=2 Destination Host Unreachable
> From 192.168.10.50 icmp_seq=3 Destination Host Unreachable
> >>>>>>>>>>>>>>> no ping answer from the box net5501 !!!
>
> stef at home:~$ ping 192.168.10.51
> PING 192.168.10.51 (192.168.10.51) 56(84) bytes of data.
> From 192.168.10.1 icmp_seq=2 Destination Host Unreachable
> From 192.168.10.1 icmp_seq=3 Destination Host Unreachable
> >>>>>>>>>>>>>>> no ping answer from my PC !!!
>
> soekris:/etc# ping 192.168.10.51
> PING 192.168.10.51 (192.168.10.51) 56(84) bytes of data.
> 64 bytes from 192.168.10.51: icmp_seq=1 ttl=64 time=0.191 ms
> 64 bytes from 192.168.10.51: icmp_seq=2 ttl=64 time=0.143 ms
> >>>>>>>>>>>>>>> only loopback ping on net5501 working
>
> >> third test : >>>>>>>>>>>>>>>>>>>>> no ping answer !!!
> [ home PC] ---- eth2 [ net5501] .... and same for eth3
>
> -------------------------------------------------------------------
> here are some tests result on my soekris
>
> soekris:/# netstat -i -e
> Kernel Interface table
> eth0 Link encap:Ethernet HWaddr 00:00:24:CB:51:EC
> inet addr:192.168.10.50 Bcast:192.168.10.255 Mask:255.255.255.0
> inet6 addr: fe80::200:24ff:fecb:51ec/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:29788 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3404 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:7980048 (7.6 MiB) TX bytes:257892 (251.8 KiB)
> Interrupt:11
>
> eth1 Link encap:Ethernet HWaddr 00:00:24:CB:51:ED
> inet addr:192.168.10.51 Bcast:192.168.10.255 Mask:255.255.255.0
> inet6 addr: fe80::200:24ff:fecb:51ed/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2590 errors:0 dropped:0 overruns:0 frame:0
> TX packets:468 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:171058 (167.0 KiB) TX bytes:44456 (43.4 KiB)
> Interrupt:5 Base address:0x2100
>
> eth2 Link encap:Ethernet HWaddr 00:00:24:CB:51:EE
> inet addr:192.168.10.52 Bcast:192.168.10.255 Mask:255.255.255.0
> inet6 addr: fe80::200:24ff:fecb:51ee/64 Scope:Link
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:4 errors:0 dropped:0 overruns:0 frame:0
> TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:362 (362.0 b) TX bytes:468 (468.0 b)
> Interrupt:9 Base address:0x6200
>
> eth3 Link encap:Ethernet HWaddr 00:00:24:CB:51:EF
> inet addr:192.168.10.53 Bcast:192.168.10.255 Mask:255.255.255.0
> UP BROADCAST MULTICAST MTU:1500 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:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:12 Base address:0x8300
>
> 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:46560 errors:0 dropped:0 overruns:0 frame:0
> TX packets:46560 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:5214270 (4.9 MiB) TX bytes:5214270 (4.9 MiB)
>
> soekris:/etc# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
> 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
> 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth3
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 192.168.10.9 0.0.0.0 UG 0 0 0 eth0
>
>
> dmesg result :
> ...
> via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker
> eth0: VIA Rhine III (Management Adapter) at 0xa0004000,
> 00:00:24:cb:51:ec, IRQ 11.
> eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 45e1.
> eth1: VIA Rhine III (Management Adapter) at 0xa0004100,
> 00:00:24:cb:51:ed, IRQ 5.
> eth1: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000.
> eth2: VIA Rhine III (Management Adapter) at 0xa0004200,
> 00:00:24:cb:51:ee, IRQ 9.
> eth2: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000.
> eth3: VIA Rhine III (Management Adapter) at 0xa0004300,
> 00:00:24:cb:51:ef, IRQ 12.
> eth3: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000.
> ...
>
>
> soekris:/etc# iptables -L
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source destination
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source destination
>
> -------------------------------------------------------------------
>
> I try several ethernet cables for the second test but still impossible
> to communicate by eth1 eth2 eth3.
> No problems found in : iptables, route, dmesg, ifconfig.
> Where is the bug ?
>
> Only eth0 is perfectly working. So perfectly thah I had upgraded the OS
> with apt-get command when linked to Internet by eth0, no link problem.
>
> Would you help me in configuring eth1 2 3,
> I think it's a material problem !!! but not really sure ...
>
> Thanks
> _______________________________________________
> Soekris-tech mailing list
> Soekris-tech at lists.soekris.com
> http://lists.soekris.com/mailman/listinfo/soekris-tech
>
More information about the Soekris-tech
mailing list