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*...

Follow

Router now shows WAN2 "up", though "Disconnected"; this is progress.

IP address obtained from phone! This too is progress.

"ping 8.8.8.8" 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...

The problem now seems to be that the interface for configuring the router's "link backup" feature is incompatible with my browser.

It's needlessly graphical in one place -- something they could have done with checkboxes or radio buttons requires dragging something on the screen.

I was using Pale Moon, but apparently it doesn't work with Firefox 53.0.3 either.

...or maybe the icons are actually greyed-out? Unclear.

Oh, there we go. Can only be 1 rule in the list?? wtf.

Seems to be working.

...and I know it's working because I just heard @Harena's machines come back online.

(...and toot.cat was giving me a "429 throttled" message for a bit; couldn't post. Am I posting too much?)

...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....

Got it working again; not sure what I did.

...and then, as I'm getting everything set so I can talk to Frontier tech support, the DSL modem decides it can connect.
.
.
.
.
.
Okay.

At least I'm ready for the next time this happens.

(That was half an hour ago; got distracted before posting.)

Sign in to participate in the conversation
Toot.Cat

A Mastodon instance for cats, the people who love them, and kindness in general. We strive to be a radically inclusive safe space. By creating an account, you agree to follow our CoC.