1
15.7 Legacy Series / Re: Howto bind outgoing traffic from opnsense (localhost) to specific WAN interface?
« on: March 10, 2016, 09:09:44 pm »
Late reply by me. Thanks for the link.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
15.7 Legacy Series / Re: Howto bind outgoing traffic from opnsense (localhost) to specific WAN interface?
« on: January 27, 2016, 11:02:47 pm »
I thought of that as well, unfortunately it's not the case. My WAN gateway is set as the default gateway, but the box still use my second VPN gateway.
3
15.7 Legacy Series / Howto bind outgoing traffic from opnsense (localhost) to specific WAN interface?
« on: January 24, 2016, 02:27:10 pm »
Hi,
I have a multi-WAN setup.
I've used outbound NAT rules and firewall rules to route outgoing traffic from subnets to the OpenVPN interfaces. This is working well.
However, I wish to setup dyndns to cloudns.net using the WAN IP. Cloudns.net is not one of the listed providers for setting up dyndns in opnsense, so I was planning to add it myself as a cron job or similar. Hence relying on that the correct WAN interface is used for outgoing traffic from the opnsense host itself. But localhost is using one of the VPN interfaces for outgoing traffic.
I have tried setting up similar firewall rules to make 127.0.0.1 use the WAN interface for outgoing traffic. I have tried putting this rule on all different interfaces, but outgoing traffic from localhost always go through one of the VPN interfaces.
How can I control which WAN interface opnsense (localhost) use for outgoing traffic?
Regards,
Peter
I have a multi-WAN setup.
- WAN with DHCP from my ISP
- OpenVPN client
- OpenVPN client 2
I've used outbound NAT rules and firewall rules to route outgoing traffic from subnets to the OpenVPN interfaces. This is working well.
However, I wish to setup dyndns to cloudns.net using the WAN IP. Cloudns.net is not one of the listed providers for setting up dyndns in opnsense, so I was planning to add it myself as a cron job or similar. Hence relying on that the correct WAN interface is used for outgoing traffic from the opnsense host itself. But localhost is using one of the VPN interfaces for outgoing traffic.
I have tried setting up similar firewall rules to make 127.0.0.1 use the WAN interface for outgoing traffic. I have tried putting this rule on all different interfaces, but outgoing traffic from localhost always go through one of the VPN interfaces.
How can I control which WAN interface opnsense (localhost) use for outgoing traffic?
Regards,
Peter
Pages: [1]