[Bug] Use public IP option in Dynamic DNS don't work if interface is a vlan

[pulcov]

Hello,

I use 2 interfaces : WAN (Public IP 88.188.XX.XXX) and WAN2 (Private IP 172.31.20.1). WAN2 is vlan of LAN interface.

I configure Gatway Group with WAN2 tier 1 and WAN tier 2.
Dynamic DNS is configure to use this Gatway Group.

When i check "Use public IP" option in Dynamic DNS, this is my WAN IP that is return and not Public WAN2 IP.

I verify this result with command line : curl –interface 172.31.20.1 --ipv4 http://checkip.dyndns.org

Result:
<title>Current IP Check</title>Current IP Address: 88.188.XX.XXX

Best Regards,

[doktornotor]

@pulcov:

WAN2 is vlan of LAN interface.

Huh?!?

@pulcov:

When i check "Use public IP" option in Dynamic DNS, this is my WAN IP that is return and not Public WAN2 IP.
I verify this result with command line : curl –interface 172.31.20.1 --ipv4 http://checkip.dyndns.org

Double huh?!? 172.16/12 (172.16.0.0 - 172.31.255.255) is RFC1918 space, and not any public IP.

[pulcov]

@pulcov:

WAN2 is vlan of LAN interface.

To be more precis, my second internet acces is a vlan of my LAN card.

@pulcov:

When i check "Use public IP" option in Dynamic DNS, this is my WAN IP that is return and not Public WAN2 IP.
I verify this result with command line : curl –interface 172.31.20.1 --ipv4 http://checkip.dyndns.org

In Dynamic DNS, option "Use public IP" is described like this : "If the interface IP is private, attempt to fetch and use the public IP instead."

[doktornotor]

Thanks for "clarification". Good luck.

[pulcov]

I have try with phisical interface and i have the same issue. Curl command seems to go out by default route