@frog You are better off with an external modem that connects via Ethernet. Makes it completely transparent to pfSense. LM1200 $40 from Netgear, $25 from Amazon I have the older LB2120 connected to pfSense for dual WAN failover. But I came across this Huawei E3372s LTE USB-stick Link interface: /dev/cuaU0.1 Init string: &F&C1&D2E0S0=0 And this Modems reported to work as Ethernet devices Huawei E3372-325 https://docs.netgate.com/pfsense/en/latest/cellular/hardware.html

@Lauryx Ok, so perhaps it's the Static route that you are missing then. If you go into System / Routing and static routes you need to add a route to 192.186.0.0/24 using the Wireguard Gateway. Again, how you do this on the OpenWRT side is something I don't know...

@pablomichelin NAT the entire subnet at each end like the Netgate docs then. Documentation

@Gblenn To be honest its not very often i do it. just a pain if i have to and then restart the process. @Gertjan oh cool i will give that a try

@khb But to answer your question. You should use the 2100 because of the superior feature set and support that comes with it compared to Edgerouter 4. Not to mention pfBlockerNG and so on.

@CFC Thanks for the reply Glad you are back in business. I'm about to swap out my pfSense firewall for a dumb router and see what happens. If the problem remains I'll follow your route. If the problem goes away I'll know its the pfSense. Thanks for the feedback.

@Altamir said in Multi WAN: Is the Claro modem using PPPoe or PPPoa by chance?

@coxhaus ok maybe something to think about. I have a tp link switch with layer 2/3

@alfredudu de onde vem esta informação?

@Farh Disabling reply-to on the accessed node - yeah, this could be a reason. When enabled, replies are directed to the gateway, which is stated in the interface settings. Disabling reply-to could lead into issues with multi-WAN setup, however. To avoid this, you can add pass rules to the top of the WAN rule set only for the source of the WAN subnet and disable reply-to in the advanced options.

@viragomann Perfect, that worked! Thanks! [image: 1731938720015-bridge-fixed.png]

@viragomann Hello again, everything is working fine. But sometimes have a delay in opening sites, like 1,2 sec delays. Looks like resolving delay. Could you please give a tip, what to check? Here are my settings: [image: 1731410427102-screenshot_12-11-2024_131743_192.168.20.1.jpeg] [image: 1731410442292-screenshot_12-11-2024_131718_192.168.20.1.jpeg] [image: 1731410454773-screenshot_12-11-2024_13209_192.168.20.1.jpeg] [image: 1731410740333-screenshot_12-11-2024_132517_192.168.20.1.jpeg] [image: 1731410746346-screenshot_12-11-2024_13254_192.168.20.1.jpeg] [image: 1731410752328-screenshot_12-11-2024_132453_192.168.20.1.jpeg] [image: 1731410764546-screenshot_12-11-2024_132425_192.168.20.1.jpeg] [image: 1731410853300-screenshot_12-11-2024_132438_192.168.20.1.jpeg] [image: 1731411059274-screenshot_12-11-2024_133042_192.168.20.1.jpeg] [image: 1731411066508-screenshot_12-11-2024_132922_192.168.20.1.jpeg] Unbound " network interfaces " also checked all local interfaces as well and " outbound network interfaces " only localhost

After further investigation, the ISP was at fault and wasn't able to find a resolution with them. Moved ISPs and the issues went away.

@Charlie48 You can connect two NICs to the ISP box though, I think, but you can only state the gateway on one of them. This would not have any drawbacks, however. I expect, that the DHCP sets also the default gateway. Then just assign the static IP to the other NIC without stating a gateway.

@gld yeah normally pfsense by default will hand out the interface the dhcp server is running on as the gateway, and you can leave it blank - you should kind of see the IP of the interface in the settings just greyed out.. But it seems, that if you switch to kea, and then back this fails.. [image: 1731257211940-other.jpg] Yeah I would say its some sort of bug with moving to kea and then back? But I had moved to kea when it first came out just to see and it was working. But that was back with 23.09, maybe something in 24.03 is flaky... If still doing it when 24.11 drops I will check and see and if not already there put in a bug report. But your the 2nd person I have seen with same sort of issue, no gateway and had switch to kea and then back.