Port Forwarding does not work anymore

Hi ​@Tommie van Odido.

I don’t have an option to access my local network currently.

I can obtain external IP address from exposed devices of my local network, IP address was changed indeed, the new one (86.90.*.*) is from *.fixed.kpn.net pool and seems accessible from internet but I cannot confirm that.

Odido support specialist has confirmed some settings of my Zyxel router remotely during a call, do you know if it is possible to check/update those port forwarding settings too by a support specialist remotely?

Thanks.

You say your external IP is accessible from the internet (but can’t confirm). What exactly is the problem then, because port forwarding should work then.

What ports have you forwarded? To what services and internal IP’s? Did the internal IP of the device you forward to maybe change?

Port forwarding should be independent of your external IP. If you use that new external IP after changing, the port forwarding would still be in place. The only problem could be that your internal device got a different IP (if you didn’t choose a static internal IP or “reserved” the IP for that device in the dhcp).

BTW. You can use DDNS (Dynamic DNS) to create a hostname. When the IP changes, you should still be able to use the same hostname to access your services (the hostname will resolve to the new external IP). But that might be for later when we get port forwarding working again.

I have cameras in my local network, they connect to internet and report their external IP addresses - that is how I know the new external address. I'm already using ddns and updated my host with that external IP. But I cannot confirm that this new IP is the same as my Zyxel WAN address, so maybe my router is behind Odido/KPN NAT now.

I also have a web server in my network, it has static IP address via DHCP static lease, and Zyxel router port forwarding leads to that server. It was working well before that internet outage, and I haven't changed my network and router configurations since that time.

So, I suspect the one of the following problems:

1. I'm behind NAT now and it is a reason why I cannot connect.

2. Configuration of my Zyxel port forwarding and/or static leases was changed by Odido somehow during that outage.

You mean CGNAT (Carrier Grade NAT) but Odido doesn’t use CGNAT on it’s fiber networks.

Your internal IP’s assigned through dhcp could have changed (if they where not “reserved” via the “Static DHCP” tab under the Thuisnetwerken menu.

You say the webserver had a static IP via DHCP static lease. Did you set that via the Static DHCP tab? And you have nothing set static in the server itself?

Is that server working on your internal network? That’s the first thing to check.

If it is, then you need to check the port forwarding, if they are still set correctly (and are active).

Then you can use a tool like https://portchecker.co/ to see if the port is open.

Did you use 443 or 80 for the webserver? You can check Onderhoud > Extern beheer if HTTPS isn’t used by the router itself on the WAN interface. But my guess it’s not because otherwise you would get the router interface when accessing https on your external IP.

As last resort you can delete the port forward rules and add them again. I would find it strange that this would be needed (especially because routers like the ones for Klik & Klaar get a new IP every night). Just try it with the 443 forward first to see if you get that one working.

Hello.

Now I returned back to home and found that my new external IP address at the modem’s WAN port differs from the port reported by my Kruidvat camera (that is strange by the way).

Port forwarnig works well at that real external IP address, so the problem is solved.

Thanks for your participation.