Hello,
I have been using the beta firmware (4.7.0-op24 beta) for a few weeks on my home router and I'm not sure if my issues have been related to that or just bad luck.
I have a Flint 2 at home and a Beryl AX for when I am mobile. Only the Flint 2 has the beta firmware in my setup. The Beryl AX has been rock solid but the Flint 2 has been a bit of a handful from day 1 to make it do what I want it to do.
Firstly, I want to use dual stack networking. IPv6 has been around long enough and things like CGNAT will only become more common whilst people still give the advice to turn off IPv6 to fix common TCP/IP issues this doesn't get to the root cause and only kicks the can further down the road.
IPv6 is something I now have working with my ISP (Hyperoptic in the UK). Native mode appears to be the only reliable way to give IPv6 connectivity on LAN clients. I did get intermittent connectivity on NAT6 but around half the time I found only IPv4 working when checking. I was able to make IPv6 NAT very well through my own Wireguard VPN but this is where my next issue came up.
I operate my own Wireguard server on an opnsense firewall at the edge of my data centre colocated servers. I have observed if the wireguard server disconnects for any reason the only way to reestablish the connection is by rebooting the router. If I restart the interface either through GL iNET, Luci or SSH it just gets stuck at the starting connection phase - this is not a problem I have with my mobile router. I didn't setup the wireguard client until after upgrading the firmware so I am not sure if this was a problem before.
The unreliability of the wireguard client reconnection and data centre classification of my IP addresses has made me change my mind about where/how to route my home network and I've setup a wireguard server on the Flint 2 so I don't have to mess around with VPN policies for things like Reddit and streaming services for the household to get the "it just works" experience. IPv6 on the wireguard server hosted on the Flint 2 would be nice to see and I can see from the op24 beta thread IPv6 is something that is being worked on but can any staff confirm to what extent?
Just a note on the wireguard server. I was trying to configure the interface manually to see if I could get IPv6 working on it but I guess it's not a standard openwrt implementation on GL iNET. I did notice the package manager link gives a 404 but would this be an upstream openwrt issue rather than GL iNET?
Click Install protocol extensions leads to.
Finally, an issue I have just found is I can no longer change any of my wireless, guest wireless or LAN settings from the GL iNET interface. When I open the wireless settings I get a blank central panel and guest wireless/LAN settings give the Unknown error occurred. Please check the network environment or reboot the device.. I am very reluctant to factory reset and have gone on a dig through log files where I have found this in the nginx log:
2024/12/30 23:54:22 [error] 11836#0: *3109 lua entry thread aborted: runtime error: /usr/lib/oui-httpd/rpc/lan:0: bad argument #5 to 'ipcalc' (string expected, got table)
stack traceback:
coroutine 0:
[C]: in function 'ipcalc'
/usr/lib/oui-httpd/rpc/lan: in function </usr/lib/oui-httpd/rpc/lan:0>
/usr/lib/oui-httpd/rpc/lan: in function 'call'
/usr/share/gl-ngx/oui-rpc.lua:108: in function </usr/share/gl-ngx/oui-rpc.lua:71>
/usr/share/gl-ngx/oui-rpc.lua:163: in main chunk, client: 192.168.145.159, server: , request: "POST /rpc HTTP/1.1", host: "192.168.145.254", referrer: "https://192.168.145.254/"
My router is run from 192.168.145.254/24 on the LAN subnet. I found the client with .159 also has an IPv6 address assigned from the ISP /56 subnet- am I getting the error because ipcalc is not escaping the IPv6 address, cannot handle the cidr or is only expecting a single address for each host?
The last time the wireless page definitely worked was when I changed the channel to a fixed channel so all my Ring and Nest devices could see my wireless networks. I know my way around networking and Linux and happy to get into the system at a low level. What diagnostics could I do to determine the cause of the blank wireless page and further troubleshoot the ipcalc error above?
If you are still reading, thanks for taking the time to do so after this turned into a longer than expected post. It was my original intention to put it on the op24 beta issues thread but it's way too long for that and goes off topic in several places. Anyway, IPv6, Wireguard and broken pages are the things I am looking for answers on.
Thanks,
Matt.