Fudged up - forgot the IP I granted for Admin Page Access

[systematic]

Think I may have fudged up here by enabling a setting on the router to grant only a cert device or IP to access the routers page. Only issue is I forgot what IP or device that might be.

Any way to get around this without resetting my router to default settings?

I can access the router via SSH - /tmp/home/root#

No idea what commands I can use to see what the IP is?

AC-88U

 

[ColinTaylor]

Try:

nvram get http_client
nvram get http_clientlist

EDIT: If that doesn't provide anything useful try:

nvram get enable_acc_restriction
nvram get restrict_rulelist

 

[AndreiV]

That's why I always have 2 devices granted access.

 

[systematic]

admin@asus:/tmp/home/root# nvram get http_client

0

admin@asus:/tmp/home/root# nvram get http_clientlist

admin@asus:/tmp/home/root# nvram get enable_acc_restriction

0

admin@asus:/tmp/home/root# nvram get restrict_rulelist

 

[systematic]

FFs, i think im screwed. Im guessing that I enabled that setting but I dont know for sure.

All I know is I cannot access the routers main page via a GUI so im guessing I have it enabled.

 

[systematic]

...

 

[L&LD]

https://www.snbforums.com/threads/cant-access-router-via-pc-but-can-via-phone.44792/#post-546206

 

[systematic]

The worry is that I keep doing that and realise i did not enable the setting in the first place. Im assuming I have it set because i cant access the GUI via web browser or phone app or anything.

 

[systematic]

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=10.838 ms

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=3.591 ms

64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=6.082 ms

64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=3.300 ms

64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2.662 ms

64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=2.441 ms

64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=3.172 ms

64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=3.354 ms

64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=4.165 ms

64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=5.127 ms

64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=2.656 ms

64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=2.751 ms

64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=21.828 ms

64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=2.242 ms

64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=2.694 ms

64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=2.816 ms

64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=3.915 ms

64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=2.587 ms

64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=1.586 ms

64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=2.280 ms

64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=1.963 ms

64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=2.849 ms

64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=3.347 ms

64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=3.800 ms

64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=2.631 ms

64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=2.622 ms

64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=1.698 ms

64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=2.923 ms

64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=2.746 ms

 

[systematic]

Could that be the crappy reason why I cant access the admin page ^

 

[systematic]

Ignore. I rebooted the router and im in.