Messages

Sorry for being late.

the command: curl -4 https://ifconfig.co
returns the 189.x.x.x

"Does your ISP employ carrier grade NAT perhaps?"  I don't know, the ISP have some odd configuration for sure, as this is the first time i have this problem. Anyways, the IP on the interface is a valid internet IP and is the one i can access from outside and send to the  no-ip service, if i can just make the dyndns pluggin send it instead of auto-resolve would solve the problem.

The Dyndns pluggin is updating the wrong ip to the no-ip service. it updates a 189.x.x.x, when it should be 100.x.x.x (this is the IP i can access from outside).
It does seens to be a problem with the the way the detection is made and some configuration in the provider as other "detectors" have the same problem (www.whatismyip.com for example).  In the no-ip APP i have the option to use the interface IP instead of the auto detection, but i cannot find this option in the pluggin. And install the app on another machine is not a solution becouse the moden is plugged in the router's interface, so another machine with the app would have the same auto detection problem.

So the questions are:
      1 - There is a way to use the interface's IP instead of the auto detection with the dyndns pluggin?
      2 - If not, being opnsense built into a linux distribution there is any alternative app that i can install into it to update no-ip?  (i ask becouse i am not a linux guy, so any help would be welcome).