RUT240 LAN interface bridge does not work after Firmware update to 07.06.19

Networking Solutions
1

Hi,

we updated a RUT240 to firmware 07.06.19.

Since then, the 2 devices on eth0 and eth1 cannot communicate with each other anymore.
It seems the bridge does not work correctly.

I tried removing and re-setting the bridge, even delete and setup the lan interface from scratch.

Below you find ping and ifconfig output:
10.11.63.10 is on eth0 and 10.11.63.100 is on eth1.
I want to point out that there is no packets logged on eth1 even though the ping went through.

Any suggestions?

Thanks
Torsten

root@SIS-BIE2:~# ping 10.11.63.10PING 10.11.63.10 (10.11.63.10): 56 data bytes64 bytes from 10.11.63.10: seq=0 ttl=64 time=0.728 ms64 bytes from 10.11.63.10: seq=1 ttl=64 time=0.747 ms64 bytes from 10.11.63.10: seq=2 ttl=64 time=0.807 ms64 bytes from 10.11.63.10: seq=3 ttl=64 time=0.735 ms^C— 10.11.63.10 ping statistics —4 packets transmitted, 4 packets received, 0% packet lossround-trip min/avg/max = 0.728/0.754/0.807 msroot@SIS-BIE2:~# ping 10.11.63.100PING 10.11.63.100 (10.11.63.100): 56 data bytes64 bytes from 10.11.63.100: seq=0 ttl=64 time=0.907 ms64 bytes from 10.11.63.100: seq=1 ttl=64 time=0.812 ms64 bytes from 10.11.63.100: seq=2 ttl=64 time=0.799 ms64 bytes from 10.11.63.100: seq=3 ttl=64 time=0.827 ms^C— 10.11.63.100 ping statistics —4 packets transmitted, 4 packets received, 0% packet lossround-trip min/avg/max = 0.799/0.836/0.907 msroot@SIS-BIE2:~# ipconfig-ash: ipconfig: not foundroot@SIS-BIE2:~# ifconfigbr-ifLan1 Link encap:Ethernet  HWaddr 00:1E:42:19:05:FCinet addr:10.11.63.1  Bcast:10.11.63.255  Mask:255.255.255.0inet6 addr: fe80::21e:42ff:fe19:5fc/64 Scope:LinkUP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1RX packets:87 errors:0 dropped:0 overruns:0 frame:0TX packets:107 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:8348 (8.1 KiB)  TX bytes:12227 (11.9 KiB)

eth0      Link encap:Ethernet  HWaddr 00:1E:42:19:05:FCUP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1RX packets:87 errors:0 dropped:0 overruns:0 frame:0TX packets:107 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:9566 (9.3 KiB)  TX bytes:12227 (11.9 KiB)Interrupt:5

eth1      Link encap:Ethernet  HWaddr 00:1E:42:19:05:FDUP BROADCAST MULTICAST  MTU:1500  Metric:1RX packets:0 errors:0 dropped:0 overruns:0 frame:0TX packets:0 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)Interrupt:4

lo        Link encap:Local Loopbackinet addr:127.0.0.1  Mask:255.0.0.0inet6 addr: ::1/128 Scope:HostUP LOOPBACK RUNNING  MTU:65536  Metric:1RX packets:25 errors:0 dropped:0 overruns:0 frame:0TX packets:25 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:2959 (2.8 KiB)  TX bytes:2959 (2.8 KiB)

qmimux0   Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00inet addr:10.142.149.115  P-t-P:10.142.149.115  Mask:255.255.255.255inet6 addr: fe80::df1d:b82a:bb6e:70c6/64 Scope:LinkUP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1RX packets:2012 errors:0 dropped:0 overruns:0 frame:0TX packets:2146 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:281438 (274.8 KiB)  TX bytes:669298 (653.6 KiB)

tun_c_enscloud Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00inet addr:10.1.7.226  P-t-P:10.1.7.226  Mask:255.255.255.240inet6 addr: fd:0:0:817e::2/64 Scope:Globalinet6 addr: fe80::75ab:8d71:4b0b:a133/64 Scope:LinkUP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1RX packets:1956 errors:0 dropped:0 overruns:0 frame:0TX packets:2078 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:500RX bytes:164593 (160.7 KiB)  TX bytes:474423 (463.3 KiB)

wwan0     Link encap:Ethernet  HWaddr 02:A2:B9:54:FE:C3inet6 addr: fe80::a2:b9ff:fe54:fec3/64 Scope:LinkUP BROADCAST RUNNING MULTICAST  MTU:4096  Metric:1RX packets:1773 errors:0 dropped:1773 overruns:0 frame:0TX packets:1675 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:272110 (265.7 KiB)  TX bytes:603448 (589.3 KiB)

root@SIS-BIE2:~#
3

Greetings,

Could you first please explain what you’re trying to achieve, or what setup you want to have?

Next, could you please login to the WebUI, head to Network → Firewall → General Settings, and disable "Software flow offloading" and click on Save & Apply?
image
Offloading can make bridge ports appear not to show software counters while traffic passes in hardware, so we’re just eliminating that possibility.

Regards,
M.

4

Hello,
"Software flow offloading" was already off, I tried with enabling but it did not make a difference.

my setup:

RUT240 (10.63.11.1)—”LAN port” — device1 (10.11.63.10)
±–”WAN port” —device2 (10.11.63.100)

bridge of eth0 and eth1 (LAN and WAN port) is set up.

I want IP communication between device 2 and device 1, all protocols (TCP, ICMP, UDP).

As you can see from the following screenshot:
RUT240 can ping both devices,
but device 2 (10.11.63.10) ping to 10.11.63.100 is lost.

image
image1068×721 36 KB

5

FYI, just to double-check I changed the IP of the RUT240 to another one of the same subnet, and results are the same.

Therefore, both device1 and device2 have the correct same subnet config, which should be as their communication was working previous to the RUT240 firmware update.

6

Hi, Torsten,

Apologies for the late reply. I’ve tried to reproduce this issue and was unable to do so, therefore, I believe that we should continue our communication on a different channel as I’d like to view the troubleshoot file for the configuration/logs. I’ve sent you a form to fill out, which you’ll receive to your e-mail address that the forum account is registered on. In the Ticket ID field, simply enter 16401.

Thank you,
M.

7

got your mail and will send you the troubleshoot file.

however, it was critical for us, so we send a technician and installed an external switch as workaround at this remote site.

8

This topic was automatically closed after 60 days. New replies are no longer allowed.