@viragomann I solved it by compiling in the WAN interface "IPv4 Upstream gateway" and saving again "Automatic outbound NAT rule generation. (IPsec passthrough included) " Automatic rules have been created Thanks

Can only operate on the information given. First step: Firewall > NAT, Outbound Switch to Hybrid mode. Create a DO NOT NAT rule on WAN for source 99.xxx.254.40/29. Create a new inside interface. Number it 99.xxx.254.41 /29 Put hosts on that interface on 99.xxx.254.42 - .46 /29 gateway 99.xxx.254.41 Make firewall rules on the interface to pass the desired outbound traffic.

I have now added a VLAN to the LAN port in proxmox and created a bridge from that. This I have added to pfSense with the first address of the ip subnet which will act as gateway for the /29 addresses from the guests/hosts on the network. So far so good.

I think this might be an issue with the setting of "Skip Rules When Gateway is Down". It seems I want this setting enabled so that when the cable modem gateway specified in the allow rule is down, the rule doesn't just turn into an allow rule for the default gateway (which has become the 3g backup connection).

https://docs.netgate.com/pfsense/en/latest/multiwan/load-balance-and-failover.html -Rico

Hi, Without seeing other details of your configuration, it seems that you may have to use "policy based routing" in your LAN rules, meaning you may have to assign two rules and specify which gateway to use for the two different destinations. in the rules section, click on Advanced, and scroll down and then specify which gateway. this may help. we had a similar issue recently with our multi-wan setup.

Okay, that issue were going pretty weird already. You can simply check your public IP by going to https://whatismyipaddress.com or something like that in the clients browser.

I've set up a VIP between my two BGP routers, and set upstream gateway to this VIP

@Raffi_ Yep, I've got it set up like that already.

@johnpoz The LAN subnet configuration was ok, because I changed it when I installed the pfsense (otherwise as you said before it would have overlapped ISP router’s LAN). Looks a lil strange to me that I didn’t find the problem. Maybe looking at the state table would have been a good idea but since I’ve solved it “the easy way” and the state table is now renewed it’s useless now to take a look at it. Thanks for the help by the way!

Cannot see any files. Just take screenshots of the modem gui pages

@brightwolf You can set a custom MAC address after you enable an interface. [image: 1600814695373-screenshot673423.png] 5th line down, under the specific interface settings screen. Jeff

@dgilmour77 , I have the same problem with a configuration similar to yours. I cannot recall it for sure, but I think DynDNS worked OK in dual WAN prior to release 2.4. Pfsense documentation advises us to use GW groups as interfaces for DynDNS, but doing so has the effect you have described. I wonder if something like that happens with dual WAN load balancing scenarios, i.e., although both WANs may be up, traffic will only flow through one of them. BTW, as for the DynDNS situation, I am using the workaround suggested by @viragomann.

@Rico The configuration for each interface did not have the name or the gateway configured. Once I configured those I could set a monitor IP and everything worked.

@gswhite said in pFsense unable to install packages: Anyone come across this issue before please that could offer advice or help? Try running these from a console and make sure you are on 2.4.5-p1: pkg-static -vv pkg-static update -f pkg-static upgrade -n

@heper said in Gateway based on source: @sr10977 said in Gateway based on source: If traffic comes in to WAN A, it goes out via WAN A (default) If traffic comes in to WAN B, it goes out via WAN A (default) that's not default ... that's assymetric routing & will fail miserably. you probably have some configuration problem this behavior occurs when upstream gateway is not set on WAN interfaces