absolutxtr

joined 1 year ago
 

I know the IP but I can't connect... Netgear RAXE300 (AXE7800). No matter what I do (wired, static IP with it disconnected from the network, or connected to the network trying to visit from PC on the same network... timeout.)

First time I put it in AP mode while its IP was 192.168.1.1 and after reset, my (wired in) laptop wouldn't reconnect. I tried setting a static IP (e.g. 192.168.1.5) and still it wouldn't let me connect. Since my subnet at home is 192.168.0.x, I was afraid that hooking it in wouldn't work so I just started over with a factory reset, the set the router IP to 192.168.0.4. Everything still worked fine after that and I could access via web broswer.

Then, I put it in AP mode again. And, I can't access it, at all. To be clear, the IP is no longer 192.168.0.4 and I know that and that's fine. I can see it it my main router - it was assigned an IP of 192.168.0.221. But, trying to go to that IP doesn't do anything. Just a "This site can't be reached" message. Tried multiple browsers etc. Confirmed it's not my main router blocking or isolating IPs or whatever, as I can access a different AP (an AX73 router in AP mode) at 192.168.0.5 no problem.

So... what the eff Netgear? Is it impossible to do anything with your routers after I put them in AP mode? Is the only way to get out of AP mode to factory reset? Seriously stupid.

[–] [email protected] 1 points 1 year ago (1 children)

Tried not 40.1 and 100.1 with 40.2 and 100.2 manually set IPs on a hardwired laptop. Neither worked.

Maybe some other user error? Should I not have set a default gateway while setting manual IP? Should I have disconnected modem from router before trying to access? Point is I wanna be able to access it to see what it's saying with less hassle. Doesn't seem like there's a silver bullet for me.

[–] [email protected] 1 points 1 year ago (3 children)

This is good advice. Thank you.

It is 192.168.40.1. or it was. Google sagemcom fast 3896.

[–] [email protected] 1 points 1 year ago

It's not though cuz that doesn't work even when I set a manual IP on that subnet while wired in. It used to be 193.168.40.1. then it was 192.168.100.1. now I don't know what it is. It's a sagemcom f@st3896.

 

I got my ISP to put my modem into bridge mode, so it acts as ONLY a modem. I have my own router, which is on 192.168.0.x with DHCP on and some static IP assignments. Everything works fine. But my modem is on a different subnet, and honestly it changes. It WAS 192.168.40.x but I THINK now it's 192.168.100.x - I have no control over it, it's my ISP that changes it and I have no idea why.

What I want to do is to be able to access my modem management interface so I can see if it's connected to the internet (for troubleshooting, when my internet fails - is it my modem? router? etc.) I can't do that from a PC on the 192.168.0.x subnet obviously. But it's really annoying to physically connect a PC to the modem and set static IPs GUESSING at what subnet the modem management portal is on.

Any advice? Ideally, I'd love for a way to access the management portal from any PC anytime... I guess the solution there would be to put everything on the same subnet? More difficult than it seems when ISP decides to change it on a whim.

As an aside, I tried setting a static IP on a laptop hard-wired into the modem just now and neither 192.16.100.1 nor 192.168.40.1 were allowing me into the modem's management portal so now I'm at a loss. That said... this was while my modem was connected to my router still via a different LAN port. Do I have to disconnect all other LAN ports before it will work? Or has the modem's subnet changed AGAIN?

Thanks for your help.