we can discuss 4.7.0 op24 here. [4.7.0-op24] Known bugs
1 Like
We also find this issue and have fixed it, you can try it in next v4.7.0 version.
1 Like
It's the API on NordVPN's side that limits access to only 20 servers per country.
Another reason why Nord just sucks. It's a pity that they are so famous, because of those aggressive advertisements.
1 Like
Understood. But I only see servers from Seattle city, and nowhere else. Do you know why?
1 Like
I don't know do I have bug in clients page every few seconds appear then disappeared list between main router (Flint 2) and access point (Flint 2 with same SSID)... Also wrong icons between wired and wireless.
I'm not sure, but perhaps is something linked to this workaround patch?
We've also discovered that the reason for this is a recent problem with the official OpenWrt online firmware build service.
For this kind of issue, could you please take a screenshot? It can help us to reproduce the problem better.
https://forum.gl-inet.com/t/new-firmware-version-4-7-being-released-for-beta-testing/47616/188?u=slesar
Screenshot about wrong icon between wired and wireless.
Later I'll make animation screenshot about appear and disappear clients list.
We are working on it, please wait a while.
I just upgraded to 4.7.0 'Stable' on my Flint2, downloaded this morning. I had a problem passing the new create WIFI SSID/credentials screen, pressing 'Next' didn't do anything, whatever I tried/entered in the SSID/password boxes.
I had to do a full reset using the button. Only then I could properly enter the SSID/password. Upon entering the new UI, all seems working well.
Then I change the LAN subnet from 192.168.8.x to 192.169.1.x
From that moment on the new UI on port 80 doesn't work anymore (constant error messages 'No related RPC reply'), I had to use the old standard OpenWRT Luci UI on port 8080 to at least get the box further configurable.
It seems there's a hardcoded IP address in the UI code, pointing to the 192.168.8.1 ??
Anyone else seeing these issues? any solution?
If enter the 192.169.1.1 on the GL GUI -> Network ->LAN, it cannot be allowed to apply. Since it is not a standard IPv4 private network.
If in the apply in the Luci, it indeed can be applied, and the WebUI seems also work well, and the API indeed error, but apply again, that the GL GUI no issue occurs.
What the usage scenarios do you have to this subnet?
3 Likes
sorry, typo. It was 192.168.1.1 of course. Already for the last 34 years, since I know about TCP/IP and it's number ranges, I never used any 192.169.x.y.
Some screens work 'a bit', like the kernel log screen.
This screen give a bit more info maybe:
I had more examples but my 'new user' status disallows me from putting more screenshots in.
On port 8080 I have the full standard OpenWRT GUI working.
Is there something I can test/do to make the GL GUI working again?
I saw more mentions of this error 'no related RPC found' but never a solution. And the weird thing is, it worked fine before I changed the router IP address to 192.168.1.1.
Thanks
Indeed private IP addresses are known.
192.168.0.0/16 gives multiple C-class subnets (254 addresses)
So use 192.168.x.0/24
For larger subnets (B or A) use something in 172.16.0.0/12 or even 10.0.0.0/8
Using non-private IP addresses is not forbidden or made impossible, but you will not be able to reach that part of the Internet. Some routers might warn you, or block it.
1 Like
The IP address typo in my forum message was literally just that, a typo, on the router itself it was always correct, 192.168.1.1.
So what could be the reason for the messed up GL GUI situation and what can you recommend me? Redownload and reapply the stable 4.7.0 (same as this morning) or go now for the 4.7.0-op24, if I really want to reinstall?
I did a re flash, same file (4.7.0 stable), preserve settings. Same issue, nothing changed
