WAN2 configuration for mobile hotspot

[andersostling56]

My small business have an RV345 router since a couple of years back. Works great with our providers ADSL line. However, the copper network will be discontinued shortly, so we are looking at a mobile network solution while keeping the router.

So I have bought a Inseego FW3100 along with a 5G contract in order to evaluate if this is good enough for us. I connected the Inseego to WAN2 as a first step (no other configuration in the RV345). In the Status overview, WAN2 is shown as "Offline" although I have verified that it is online and connected to the mobile network. If I connect directly to the Inseego's wifi, I do have full and speedy internet access.

Is there any other settings that I need to configure in order to have the WAN2 recognized?

[balaji.bandi]

Inseego FW3100 - if this setup to offer a DHCP on Lanport (i am in guess that where your WAN port connecting)

then WAN2 should get DHCP IP offer and that should work ?

If I connect directly to the Inseego's wifi,

connect laptop to ethernet port and test it.

[andersostling56]

This is how it looks on the Status screen in the router. I expected a DHCP adress in there but none is shown. On picture 2, you can see the Inseegos status where it has got an IP from the mobile operator.

 

[Flavio Miranda]

@andersostling56 

Go to Wan config and change the precedence to 2

[andersostling56]

I did that. Wan1 is prio 1 and Wan2 prio 2. But I thought that was only for failover. What about the missing info and "Offline" status in the Status screen? Maybe I should configure static IP for WAN2 like the info I see in the Inseego's screen?

 EDIT: I changed the IP info on WAN2 from DHCP to static and added the values from the Inseego panel. That changed the status from Offline to Online, and if I traceroute from an internal host to the mobile vendor's gateway it looks fine. xx6 beeing the WAN ip and xx7 the GW.

Now I just need to figure out how to test properly. I will go back to the site tomorrow and pull out the WAN1 cable just to see what happens.

sysman@hp-srv03:~$ traceroute -4 83.182.xxx.xx7
traceroute to 83.182.164.217 (83.182.xxx.xx7), 30 hops max, 60 byte packets
1 gateway.hoganas-platslagaren.se (10.0.2.1) 0.557 ms 0.621 ms 0.757 ms
2 m83-182-164-216.cust.tele2.se (83.182.xxx.xx6) 2994.814 ms !H 2994.822 ms !H 2994.781 ms !H
sysman@hp-srv03:~$ traceroute -4 83.182.xxx.xx6
traceroute to 83.182.164.216 (83.182.xxx.xx6), 30 hops max, 60 byte packets
1 m83-182-164-216.cust.tele2.se (83.182.xxx.xx6) 0.722 ms 0.893 ms 1.050 ms

[Flavio Miranda]

Test with on link, change the precedence and repeat the test.

[andersostling56]

Sorry, dont understand "test with on link". Can you elaborate?