Fuchs, Martin schreef:
Hi !
A friend of mine has a strange problem: everytime he reboots his
pfsense his dyndns updates with 192.0.2.112
He had this problem with 1.2.2 and now updatet to 1.2.3 RC3 and it
still exists…
Anyone hast he same issues ?
Any ideas ?
Regards,
Martin
Is 192.0.2.112 not a public range ?
I saw people responding NAT related issues... but I thought 192.168.x.y,
172.16.x.y - 172.32.x.y AND 10.x.y.z were NAT'ted addresses. All the
rest (other than 234.x.y.z) are public addresses.
It might still be a natted situation, but then it would be a bad choice
to have 192.0.x.y as a private range !!
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Commercial support available - https://portal.pfsense.org
