Bug in TL-R470T+ for SIP Connections and DynDNS
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Bug in TL-R470T+ for SIP Connections and DynDNS
Model :
Hardware Version :
Firmware Version :
ISP :
I would like to report 2 bugs which I believe I could find on product Loadbalancer TL-R470T+.
Bug 1:
I have a TL-R470T+ v4.0 running firmware 20150526 Rel.71817s (latest version available) which I use purely for Active/Backup Internet with two different connections. Behind this TL-R470T+ I have some equipment like SIP Clients (an ATA hardware) and which connect to an external VoIP server in the Internet. When a Internet failover occurs from WAN1 to WAN2 the only thing that doesn't keep working are the SIP Clients.
Looking at Maintenance, "NAT Table" I can see the the previously opened connection to the SIP server keeps bounded to go out via WAN1 although the connection is already down and everything is going out via WAN2. Even if I restart the SIP Clients it doesn't work and it is unable to connect. Looking again at NAT Table it can still see that same connection trying to go out via WAN1 which is Down.
If I reboot the TL-R470T+ (and it clears the NAT Table) then it works again and the SIP Clients can connect.
The solution to that perhaps could be clear the NAT Table when a failover occurs from one WAN port to another.
Bug 2:
One of the TL-R470T+ I have the WAN2 is primary and WAN1 is secondary. However when I have both connections Up and everything is going out via the primary (WAN2) the Services, Dynamic DNS, DynDNS doesn't change the "WAN Port" to WAN2, but keeps choosing WAN1 which is secondary and is in standby. I have even rebooted the TL-R470T+ but with no effect, it keeps sending to DynDNS service the WAN1 IP address which is wrong.
Solution is make the DynDNS aware of which is the primary connection or make the service to know which is the correct Public IP and send the correct one to the DynDNS service.
Hardware Version :
Firmware Version :
ISP :
I would like to report 2 bugs which I believe I could find on product Loadbalancer TL-R470T+.
Bug 1:
I have a TL-R470T+ v4.0 running firmware 20150526 Rel.71817s (latest version available) which I use purely for Active/Backup Internet with two different connections. Behind this TL-R470T+ I have some equipment like SIP Clients (an ATA hardware) and which connect to an external VoIP server in the Internet. When a Internet failover occurs from WAN1 to WAN2 the only thing that doesn't keep working are the SIP Clients.
Looking at Maintenance, "NAT Table" I can see the the previously opened connection to the SIP server keeps bounded to go out via WAN1 although the connection is already down and everything is going out via WAN2. Even if I restart the SIP Clients it doesn't work and it is unable to connect. Looking again at NAT Table it can still see that same connection trying to go out via WAN1 which is Down.
If I reboot the TL-R470T+ (and it clears the NAT Table) then it works again and the SIP Clients can connect.
The solution to that perhaps could be clear the NAT Table when a failover occurs from one WAN port to another.
Bug 2:
One of the TL-R470T+ I have the WAN2 is primary and WAN1 is secondary. However when I have both connections Up and everything is going out via the primary (WAN2) the Services, Dynamic DNS, DynDNS doesn't change the "WAN Port" to WAN2, but keeps choosing WAN1 which is secondary and is in standby. I have even rebooted the TL-R470T+ but with no effect, it keeps sending to DynDNS service the WAN1 IP address which is wrong.
Solution is make the DynDNS aware of which is the primary connection or make the service to know which is the correct Public IP and send the correct one to the DynDNS service.
