reply to Ree
Re: Hitron troubles Perhaps the routers can only handle class C private network addresses... it really isn't a big deal.
Considering CIDR was introduced in 1993, I'd expect that it wouldn't be a problem with an RG that I bought only a few years ago.
In any case, using 192.168.0.x appears to have resolved the problem for me, thanks OP! I was using a 10.x.x.x address because at one time I was frequently VPNing to a network that used 192.168.x.x addresses, causing conflicts.
reply to morpheus69
said by morpheus69:Yeah I dunno. It functions with the class A, other than the lack of UPnP and inability to save port forward rules on restart. Same behaviour happened with 192.168.1.1 -- didn't think to try something else in the 192.168.0.* range to see if that would have worked.
Perhaps the routers can only handle class C private network addresses... it really isn't a big deal.
And yeah, it's not a big deal. I'm just used to typing 10.20.30.* from work, so re-used that at home. 192.168.0.* is cool with me too though.
And jmcneill, glad this solved your problem too!
You can't assign class A addresses to most (all?) consumer network devices, or class B either. The subnet mask only goes from /24 and up.
10.20.30.0/24 is still class C.
Router not liking anything then the factory default subnet is definitely funky though.