I am definitely able to talk to the device (192.168.0.29) through the LAN -- can access web UI and ping it. That's a start.
I can also see the router's web UI at 192.168.0.1.
But the router cannot ping the device.
Maybe this is an address-space issue? The phone and the router are both providing DHCP, and they're both using 192.168.x.x -- but that's same as DSL modem. The router is supposed to act as a client on the portal(?)'s DHCP.
Owait, device can't connect to phone. Ok. :puzzled:
@woozle both using 192.168.0.x (subnet mask usually used for homes is 255.255.255.0) meaning only the last octet/8bits is used for address that computer, rest is the subnet/network mask
@LottieVixen I just wasn't sure if maybe the two DHCP servers were fighting with each other.
...but access to the phone's DHCP should only be through the router anyway, so it shouldn't matter. I know this works because the DSL modem is set up that way too... oh wait! No it isn't. Aha.
Frontier modem is 192.168.254.254, and the router's connection to it is 192.168.254.2.
Ok, so I think I need to tell phone to use 192.168.253.x or something.
@LottieVixen ...aand this apparently cannot be done. There are no controls on the phone for setting subnet mask.
So now it comes down to: can I get the device (wireless hub) to connect to the phone, or not?
I mean, this seems like it should be simple enough. Device sees phone in SSID list.
...owait, *I* know what I'm doing wrong.
The device needs to be plugged into WAN2 on the router, not connected to the LAN in general.
I had it that way before, but spaced out when I took it down to reset.
That makes it harder to interact with its UI, but maybe it will actually start *working*...
Router now shows WAN2 "up", though "Disconnected"; this is progress.
IP address obtained from phone! This too is progress.
"ping 184.108.40.206" through WAN2 works! How about web?...
Hard to say. I think I need to disable WAN1, or make it secondary; it's limping along just enough that the router is trying to use it first...
...and everything's fine for a bit, but then suddenly the router decides it can't talk to the device anymore.
Tearing hair out in 3... 2....
On the internet, everyone knows you're a cat — and that's totally okay.