by foq » Wed May 01, 2024 5:22 pm
The server should be connectable again, again (again?). More CGNAT weirdness, but this time I think I've found the root cause (and here up until now I was thinking they'd just periodically remove "no cgnat" people from some list, whether accidentally or purposefully, heh). When I would call and complain about CGNAT, the ISP would add my router's MAC address to some whitelist and CGNAT would be removed... but, whenever my router would reboot, it would seemingly grab a MAC address from a random device on the network and report that, rather than reporting its own. I did have a custom firmware (Asus-wrt Merlin) installed, and I've since installed the stock firmware again, which magically gave me a real public IP again (I probably had CGNAT removed the first time before I installed Merlin), so hopefully the MAC fuckery was something Merlin was doing.
So hopefully the server will be more stable now. I'm sorry I haven't been able to get to it sooner. I know the server's been unreachable for a little while now at this point, but I've been quite busy with some real life stuff. But we should be all good now. If we still have problems with CGNAT after this, my next move will be to go and buy a new router. This one still works fine outside of some MAC fuckery, but it's also quite old and has been EOL for some time now, so getting a new one at this point wouldn't necessarily break my heart either.
The server should be connectable again, again (again?). More CGNAT weirdness, but this time I think I've found the root cause (and here up until now I was thinking they'd just periodically remove "no cgnat" people from some list, whether accidentally or purposefully, heh). When I would call and complain about CGNAT, the ISP would add my router's MAC address to some whitelist and CGNAT would be removed... but, whenever my router would reboot, it would seemingly grab a MAC address from a random device on the network and report that, rather than reporting its own. I did have a custom firmware (Asus-wrt Merlin) installed, and I've since installed the stock firmware again, which magically gave me a real public IP again (I probably had CGNAT removed the first time before I installed Merlin), so hopefully the MAC fuckery was something Merlin was doing.
So hopefully the server will be more stable now. I'm sorry I haven't been able to get to it sooner. I know the server's been unreachable for a little while now at this point, but I've been quite busy with some real life stuff. But we should be all good now. If we [i]still[/i] have problems with CGNAT after this, my next move will be to go and buy a new router. This one still works fine outside of some MAC fuckery, but it's also quite old and has been EOL for some time now, so getting a new one at this point wouldn't necessarily break my heart either.