Ok thanks for sharing. Sometimes those problems are the most difficult, where a small assumption was made incorrect.

quagga does routing not firewalling. with quagga you'd need to setup all tunnel networks with openvpn and you DONT push any other routes. you setup the vpn-interfaces that quagga needs to run on then, basically on each node, you'd have to insert what local subnets you wish to publish (you could choose to publish them all, but this is often not wanted) quagga will failover, depending on the cost you give each interface. there can be some issues with full mesh in case quagga decides to push tunnel subnets … but that can be worked around if needed

I don't know between 2 modems > load balancer Duolinks SW24 | Pfsense | LAN or 2 modems > 1 Pfsense for load balancing | 2nd Pfsense for Squid + others | LAN Little bit tired by that  :(

Please don't double post.

Like the others posted: the ping is going out, but ZyXEL isn't responding at all. Since this is a capture, it has nothing to do with the firewall or routes, as it's in the L2 interface level, nothing has been done to the packets yet. I think you might have a problem on the ZyXEL side, not on the pfSense side. Your trace is correct at least, so now you know how to capture packets, which is a great tool with network diagnostics! Beware though, packet captures are not always useful when for example you have a firewall or routing problem since firewalling and routing happen after the packets leave the interface and to in to processing software like pf.

@kejianshi: 明白 internet > router1 LAN 192.168.0.1/24 > pfsense wan 192.168.0.50 + LAN 10.10.10.1/23 From 10.10.10.x you can ping anything on 192.168.1.0/24 but from 192.168.1.0/24 you can't ping anything on 10.10.10.0/24 (LAN side) 对不对? This is very normal.  NAT will prevent it I'm pretty sure you have 2 layers of NAT. Make things simple.  Get rid of all the routers EXCEPT pfsense if possible. I could tell you how to forward a bunch of ports, but better to simplify your network first. 对对对，要怎样做呢?

I'm not a sales guy, and this is totally going to sound like a pitch.  A reference guide was the reason I paid for the Gold Membership.  In my opinion, totally worth the price I paid having an overview of the feature set. That said, there is a doc WIKI:  https://doc.pfsense.org/ The categories view (contained in the above link):  https://doc.pfsense.org/index.php/Special:Categories Lastly the NAT view (again contained in the above link):  https://doc.pfsense.org/index.php/Category:NAT In those instances where I know what I want to do but don't know the technical term, Google searches on what I'm after usually get me close enough. The pfSense forums have helped me out as well.  I'm still pretty new to them, and trying to become more active.  This really is a great product, especially for the SMB market I support in consulting.  Looking forward to possibly using in enterprise spaces as well.

Hi first of all: thanks for pushing me in the right direction. The route on the client side (10.41.41.244) was on the wrong interface…my mistake!

I am not seeing anything in the logs or dmesg during boot.  It is odd that I can backup and restore to another system and everything works.

Thank you for your input to help optimize my mtu settings. My mtu settings are only experimental. Some settings did cause packet fragmentation and even timeouts. In the end, I remembered that the pfsense traffic shaper was given a low speed for the wan port and needed a bump up. Doh!

Can your get pfsense to send out an email when a connection is back UP?

Hi Dan, I ran into almost the same problem. My problem is, that my standardgateway has already been assigned to another WAN interface connected to a different router, that I use for all my vlans. But in your case, the second wan interface will use the standardgateway from the first wan interface, so you should have no trouble at all. Kind regards, MisterIX.

Thanks guys, going to enable the option and play around with it.

Yeap different networks and route between them