Hey all, first post here and only just joined, be gentle.
I have only got this router around 3 weeks ago and very happy with it thus far! Its my first openwrt router.
Also, I changed my provider which i am not sure if it does or does not add to my issue? I had it working quite well and I ran the update and changed provider within the a day of each other so I am not sure what affected this. But, I also cannot use the WireGuard as a server anymore. Its enabled, I can connect to it but no connectivity on my mobile. I did recreate the VPN profile. I do not get any clients showing in the VPN server logs when "connected" with my mobile as the client.
I have installed, UPnP, SQM and QOS. Its been fine till the recent 2 changes.
This is the error I get when I run the DDNS test and im not entirely sure if I have ticked something to contribute to this but I dont think I have. I do feel this is as of the update to 4.7.0.
I have also disabled and enabled DDNS, with some time between the toggles.
Any ideas? Thanks in advance...
Error as per below:
The IP address from DDNS domain resolution is not the same as the WAN IP of the device.
You need an Internet Public IP address to use Dynamic DNS.
If this router is behind NAT, you may need to set up port forwarding on your ISP router.
If you have VPN Client enabled, please disable "Services from GL.iNet Use VPN" in the global options.
If you changed your Internet provider, I guess that you have received a new ONT. When you connect your Flint2 to your new ONT, restart the ONT. Also, there is a DDNS service that has been down these days.
ONT is the same one as before. Credentials unchanged. Provider(RSP) has changed. Network owner has not changed if that makes sense. Our network is govt owned here in AUS, the NBN.
The ONT has been restarted several times and have also allowed ample time for DNS to sync up. The DDNS outage however, I was not aware of that! Guessing its ongoing? It would make sense then when looking back on the error. Its not monitoring the IP or not updating as it changes.
In theory that DDNS outage is being resolved since some time ago: GL DDNS outage 12/6 - #44 by clannad
Check if your symptoms are equal to the existent in that thread.
Ok so, having a read of that thread you provided, your right, it should be resolved. Also, thank you.
I have done pretty much what others have, restarting the service(toggle DDNS off/on?) etc.
I have a massive page of this log(yes I masked the address for this post):
Sat Dec 14 20:51:13 2024 daemon.notice miniupnpd[16003]: private/reserved address 1xx.1xx.xx.xx is not suitable for external IP
Am i right to say that UPnP is the cause here?
When i open it, it does say miniupnp so im assuming something is a miss here.
Below is a copy paste from the rules in miniupnp. Bottom 2 lines im ok with but the first 2 i dont recall entering them(defaults)? Or am I looking in the wrong place?
MiniUPnP ACLs
ACLs specify which external ports may be redirected to which internal addresses and ports
Comment
External ports
Internal addresses
Internal ports
Action
Allow high ports
1024-65535
0.0.0.0/0
1024-65535
allow
ā°EditDelete
Default deny
0-65535
0.0.0.0/0
0-65535
deny
ā°EditDelete
Deny OpenVPN
1194
192.168.8.140
1194
deny
ā°EditDelete
Plex
32400
192.168.8.184
32400
allow
ā°EditDelete
Also in miniupnp settings, advanced tab i see:
UPnP lease file /var/run/miniupnpd.leases
Would that be holding the old ip and not updating? If so how would I go about clearing that?
That's new to me, good read. From the link I am understanding this is at my RSP level? Are you sure? Friend of mine who got me onto the same RSP, has the same router, has WireGuard working fine with DDNS. Is there an option I can tick/untick to restore DDNS and WireGuard?
Is this what you mean? 100.100.xx.xx
This is the WAN interface ip(ethernet, that my router gets from my ONT?), not my live ipv4 ip that whatismyipaddress.com picks up.