Hi,
So I'm stuck with a bit of a predicament, and have reverted to posting on the Forum.
I'm really new to forms so I'm giving it my best shot.
I have setup a Untangle firewall build 11.1.0 for a client of mine.
The machine has multiple NICs of which three are utilized.
One is designated to be for the internal LAN, and two are connected to WAN links.
Everything is working 100% on the firewall, besides the predicament which has presented itself.
One of the WAN connections is a 2Mb link, and has a static IP Address (WAN Alpha)
The second WAN connection is a 10Mb link, and has a dynamically changing IP Address (WAN Beta)
As WAN Alpha as a static IP, a A Record has been setup on the hosted DNS to point to this address, and this is working fine.
However as WAN Beta has a dynamically changing address, the DynDNS service is used to ensure the public DNS record is updated.
The problem lies with that Untangle periodically checks WAN IP Addresses, and determines at times that WAN Alpha's address is different to WAN Beta's, and then updates the DynDNS with the IP Address of WAN Alpha.
This inevitably causes problems.
The firewall channels all traffic (SMTP, POP3, RCP, HTTP, HTTPS, FTP) outbound, and inbound through WAN Beta, as this is the faster connection.
WAN Alpha is primarly used only for for RPC traffic (this is as per client instructions)
I have searched through the Forum, as well as consulted with support regarding this issue, and have been advised to setup WAN Balancer Rules, as well as Routing rules, however these do work to some extent, though the before mentioned problem still remains.
I have gone as far as to setup a rule to ensure that DynDNS only updates to through WAN Beta, and still at times DynDNS is updated with WAN Alpha's IP Address.
I require help in ensuring that only WAN Beta's IP Address is used to Update the DynDNS record.
Any help of suggestions are welcome, and should more information be needed I can provide this.
Thanks and regards,
Lex
So I'm stuck with a bit of a predicament, and have reverted to posting on the Forum.
I'm really new to forms so I'm giving it my best shot.
I have setup a Untangle firewall build 11.1.0 for a client of mine.
The machine has multiple NICs of which three are utilized.
One is designated to be for the internal LAN, and two are connected to WAN links.
Everything is working 100% on the firewall, besides the predicament which has presented itself.
One of the WAN connections is a 2Mb link, and has a static IP Address (WAN Alpha)
The second WAN connection is a 10Mb link, and has a dynamically changing IP Address (WAN Beta)
As WAN Alpha as a static IP, a A Record has been setup on the hosted DNS to point to this address, and this is working fine.
However as WAN Beta has a dynamically changing address, the DynDNS service is used to ensure the public DNS record is updated.
The problem lies with that Untangle periodically checks WAN IP Addresses, and determines at times that WAN Alpha's address is different to WAN Beta's, and then updates the DynDNS with the IP Address of WAN Alpha.
This inevitably causes problems.
The firewall channels all traffic (SMTP, POP3, RCP, HTTP, HTTPS, FTP) outbound, and inbound through WAN Beta, as this is the faster connection.
WAN Alpha is primarly used only for for RPC traffic (this is as per client instructions)
I have searched through the Forum, as well as consulted with support regarding this issue, and have been advised to setup WAN Balancer Rules, as well as Routing rules, however these do work to some extent, though the before mentioned problem still remains.
I have gone as far as to setup a rule to ensure that DynDNS only updates to through WAN Beta, and still at times DynDNS is updated with WAN Alpha's IP Address.
I require help in ensuring that only WAN Beta's IP Address is used to Update the DynDNS record.
Any help of suggestions are welcome, and should more information be needed I can provide this.
Thanks and regards,
Lex