No connection with router after changing its IP to network prefix

2

I changed IP of my router from 192.168.1.1 to 192.168.1.0, which is my network prefix. What should I do to retrieve connection to my router?

UPDATE

I am on LEDE project and router TP-Link Archer C7. One thing I came up with was running some startup script via USB drive. Do you have any ideas for such implementation?

pt12lol

Posted 2017-08-16T00:28:51.940

Reputation: 125

I'm surprised it allowed that, it's an invalid IP address. Either it's still on the previous .1.1 address, or it's reset itself to the factory default (probably also .1.1). If you can't contact it on either, I'd suggest a hardware reset. – Ian – 2017-08-16T00:34:13.783

@Ian I am on LEDE project, what allows a lot. Aren't there any hack like running startup script from USB setting it back? – pt12lol – 2017-08-16T00:38:39.167

Factory reset and connect with default IP per that configuration and then reconfigure, push the config backup file back to it, etc. – Pimp Juice IT – 2017-08-16T01:32:01.167

Do you know how to restore factory settings on this router under lede? For me even 30-30-30 method does not work. – pt12lol – 2017-08-16T02:33:16.517

Answers

2

You can try configuring your computer with the IP address 192.168.1.2 with the subnet mask 255.255.0.0.

With the subnet mask 255.255.0.0, the IP address 192.168.1.0 is just another node on the network instead of being the network address.

Once you've fixed your problem, put your computer's subnet mask back to whatever it was before.

This is all you can do from the client side to make communication with the router possible. If the router is unresponsive despite this approach, then your only option is the reset of last resort on the router.

I say Reinstate Monica

Posted 2017-08-16T00:28:51.940

Reputation: 21 477

This generates timeout after some time – pt12lol – 2017-08-16T02:46:02.773

I mean timeout after attempting to connect over both http and ssh. – pt12lol – 2017-08-16T03:02:24.390

And it is actually an improvement, because the previous error was immediate unreachable response. But still does not enable to fix my issue completely. – pt12lol – 2017-08-16T03:04:03.233

If you ping the router do you get a response? If after pinging it, is there an entry for it in your arp cache (indicating it's responding to arp requests)? – I say Reinstate Monica – 2017-08-16T03:18:55.573

Yup, pings are getting back, but arp keeps silence on it. – pt12lol – 2017-08-16T03:41:21.827

What I've proposed in my answer is all you can do from the client side to make it possible to communicate with the router. If the router can't process the IP traffic despite receiving it, then it looks like your only option is to reset it. I'll update my answer accordingly. – I say Reinstate Monica – 2017-08-16T03:48:42.000