Wired Wan Failover Issue

Your advice much appreciated. We have several remote (public ip) RUT240 units that have the same issue. We have configured Mobile Failover to a Wired WAN connection.

LAN IP is 192.168.0.1
WAN ip is set to 192.168.1.2

We have appropriate port forwarding rules set on the Wired Wan router

This works when it failsover - in directing WAN (source traffic) to the RUT240 routers LAN devices. Also working is WevbUI and SSH login from the WAN routers public IP address.

However, from RUT240:

ping traffic works to any public ip - eg 8.8.8.8.
but http traffic - eg wget google.com.au or any curl call to a public address fails this inlcudes any attempt to update the dyndns addresses.

below is the results from ifconfig show eth01 set to the WAN IP:

Firware 14.7 - please - before you say this firmware too old, and you cant support it. It is the most recent last GEN firmware, Many units we recieve are still loaded with even earlier firmware.
Remotely upgrading via public IP as suggested does not work for our configurations, eg: POST/GET API has changed for v7+, which requries integration changes to our server side software. This will be upgraded in due course, along with costly site visits ( ie 3000+km trips in Australia). Hovever, in the meantime, we would really appreciate if you can offer any advice like to resolve the issue if possible. But please, do advise if 14.7 has this as known bug which will prevent this from ever working correctly in 14.7. And we will give up attempting to make this work for now,

Perhaps do we need to configue a static route on the RUT240 for Wired WAN (192.168.1.2) to use 192.168.1.1 as gateway perhaps ?

br-lan Link encap:Ethernet HWaddr 00:1E:42:25:3B:B8
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21e:42ff:fe25:3bb8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15814 errors:0 dropped:0 overruns:0 frame:0
TX packets:47311 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2723915 (2.5 MiB) TX bytes:21524964 (20.5 MiB)

eth0 Link encap:Ethernet HWaddr 00:1E:42:25:3B:B8
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:284 errors:0 dropped:0 overruns:0 frame:0
TX packets:56032 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:74650 (72.9 KiB) TX bytes:23776237 (22.6 MiB)
Interrupt:5

eth1 Link encap:Ethernet HWaddr 00:1E:42:25:3B:B9
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21e:42ff:fe25:3bb9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:88226 errors:0 dropped:5765 overruns:0 frame:0
TX packets:8219 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:17379710 (16.5 MiB) TX bytes:2678761 (2.5 MiB)
Interrupt:4

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:65536 Metric:1
RX packets:4651 errors:0 dropped:0 overruns:0 frame:0
TX packets:4651 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:375207 (366.4 KiB) TX bytes:375207 (366.4 KiB)

wlan0 Link encap:Ethernet HWaddr 00:1E:42:25:3B:BA
inet6 addr: fe80::21e:42ff:fe25:3bba/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15530 errors:0 dropped:0 overruns:0 frame:0
TX packets:58707 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2870683 (2.7 MiB) TX bytes:25106050 (23.9 MiB)

wwan0 Link encap:Ethernet HWaddr 32:C3:55:D9:62:98
inet addr:101.168.6.169 Bcast:101.168.6.169 Mask:255.255.255.255
inet6 addr: fe80::30c3:55ff:fed9:6298/64 Scope:Link
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:11574 errors:0 dropped:0 overruns:0 frame:0
TX packets:7646 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:636417 (621.5 KiB) TX bytes:447592 (437.1 KiB)

Hello,

From the first glance, the issue looks like it could be related to the DNS servers. If the wired WAN interface is configured statically, make sure to include the DNS servers (e.g. 8.8.8.8 or 1.1.1.1), as well as the default gateway (since ICMP traffic passes, this is unlikely to be the cause).
Additionally, on the wired WAN interface there are over 5700 incoming packets dropped. Perhaps there are any additional rules configured on the RUT240 firewall?
Finally, could it be that the wired WAN interface uses an MTU lower than 1500? If so, it can be lowered in the WAN interface settings. ICMP packets by default are very small, and it could be that CURL requests fail because of their size.
Additionally, could there be any firewall rules configured on the router in the RUT240 WAN?

Best regards,

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