@johnpoz I'm not trying to block plex it's just installed on the same computer that blue iris is running on. I have never really messed with Docker or VMs I have tried messing with allowing a device on one VLAN to talk to a device on another VLAN but it wasn't working. I'm sure I was doing something wrong. Do you think the best/easiest route would be to have the plex/blue iris computer on the "Home" VLAN and set up all the cameras on the "ipcamera" VLAN and only let the "ipcamera" VLAN talk to the Plex/blue iris machine IP? That's what I was going to try but I just wanted to make sure I wasn't going about it the wrong way and end up having to redo everything a different way later.

@nick-loenders ah!!! thanks for the info that keeps my curiosity cat purring nicely ;)

Hello @viragomann thanks for your reply: I tried it, so I created this entry in my Cisco: ip route 192.168.106.0 255.255.255.0 192.168.0.30 but can't ping or ssh anything. Any other suggestion? Maybe some configuration on the pfsense side. -- Regards, Marco

@kom Thank you! You were correct. It took me a while to find the existing rules and duplicate them for the other two interfaces. I obviously have a lot to learn about pfsense. I now have one of my two WiFi hubs online so I can start to play with it. This is very different from the iptables that I am used to. Thanks!

Well you could move the mpls connection to a wan on pfsense sure, but that would still need routing.. You could do something dynamic vs static.. But that can add complexity, so unless your using it for monitoring of path to change routing, or networks come and go all the time.. A hand full of static routes is easier solution.

@alteredstate said in How To Direct Traffic For Specific Website(s) Out Specific Gateway?: I would be forced to continually disable and enable the VPN firewall destination rule each time I use Disney+. Just create another wifi network then, when you want to watch Disney, connect to your non vpn wifi. When you want to do whatever else, just switch to your vpn wifi.. I would just watch on my TV to be honest.. Why would anyone watch on little screen when there is a big screen available? But if your going to be using a device where you want to split traffic vpn and non vpn - then yeah the policy routing is really the only way to do that. It can be problematic - especially if laptop is not using pfsense for dns, say doh..

@viragomann I can ping google.com, it works just fine. Indeed, in the logs there seem to be recurring patterns (and I totally missed the flags). home_ip : my home public ip address server_ip : my server public ip address public_ip : multiple public ip addresses were captured by the filter port : multiple port numbers were captured by the filter Here is for the Default deny rule IPv4 : block em0 TCP:PA home_ip:port server_ip:443 (*) block em0 ICMP public_ip server_ip block em0 TCP:S public_ip server_ip:port (mostly port 445) block em0 TCP:A/FA/PA 192.241.206.128:port server_ip:443(**) block em0 TCP:R public_ip:port server_ip:80 (*) this line appears so often that it is difficult to see anything else. (**) I don't know the 192.241.206.128 address, but it is the only one I have with the A, FA and PA flags Some traffic is passing : pass em0 TCP:S server_ip:port 99.86.113.21:443 pass em1 TCP:S 192.168.1.2:46178 99.86.113.21:443 (***) pass em1 TCP:S 192.168.1.101:port 34.122.121.32:80 (32.121.122.34.bc.googleusercontent.com) (***) 192.168.1.2 is another vm (debian) on the LAN --> no internet as well In the end, the Default deny rule IPv4 seems to be blocking inbound traffic. I could see that it was mostly blocking ip addresses referenced as abusive. And I think I have missed something, because I don't see all the LAN activities in the logs (e.g., ping). I am currently working on this issue.

@viragomann Thank you! That plus a blocking rule to prevent the host from going out the gateway I don't want does the trick.

@stephenw10 Really appreciated for the reply, just disabled "reply-to" from the fw rules and the traffic flows to the right BGP path now. Sipher

@viragomann i'll use that than. thanks again. solved.

@viktor_g I have selected the Outgoing Network Interface to WAN2. But this way proxy is connected but the internet does not work. Because the default gateway is WAN1. Internet over proxy only works when Both default gateway and Outgoing Network Interface in squid are the same.

@viragomann Did it via winSCP instead. Thank you