What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

[ 3006.102_4 alpha Build(s) ] available build(s)

Status
Not open for further replies.
how do i get back into my router i switched from both to https only to get in and am now locked out . Unfortunatly I have forgetten how to get back in , my mind is blank
sorry for the stupid question
 
i have something strange suddenly icmp pings are not long working

see it worked before
1744132739609.png

respond from icmp ping is still on
1744132757208.png


i have my isp modem in bridge mode
nothing has changed
 
View attachment 64876

i checked if my wan ip is still the same and it is
That suggests the rules might not be generated. What’s the output from
Code:
iptables-save -c | grep icmp
nvram get misc_ping_x
I might also be getting my logic inverted on whether the setting is active or inactive. Never bothered to use this option myself.
 
That suggests the rules might not be generated. What’s the output from
Code:
iptables-save -c | grep icmp
nvram get misc_ping_x
I might also be getting my logic inverted on whether the setting is active or inactive. Never bothered to use this option myself.
1744137372896.png



someone also did a trace route
1 2ms 2ms 2ms 192.168.178.1
2 * * * Request timed out.
3 9ms 10ms 9ms amr-rc0011-cr102-et115-251.core.as33915.net [213.51.194.237]
4 * * * Request timed out.
5 13ms 14ms 15ms rt-rc0173-cr102-new-be2-2.core.as33915.net [213.51.7.247]
6 15ms 14ms 13ms 212.142.54.50
7 28 ms 26 ms 26 ms f229062.upc-f.chello.nl [80.56.x
8 * * * Request timed out.
9 * f229062.upc-f.chello.nl [80.56.x] reports: Destination host unreachable.

they also stated this
The router does respond, but with a destination host unreachable for its own IPv4 address, strange. A traceroute from here also looks a bit strange, why the trace does not end at hop 7 is not clear to me.
 
View attachment 64878


someone also did a trace route
1 2ms 2ms 2ms 192.168.178.1
2 * * * Request timed out.
3 9ms 10ms 9ms amr-rc0011-cr102-et115-251.core.as33915.net [213.51.194.237]
4 * * * Request timed out.
5 13ms 14ms 15ms rt-rc0173-cr102-new-be2-2.core.as33915.net [213.51.7.247]
6 15ms 14ms 13ms 212.142.54.50
7 28 ms 26 ms 26 ms f229062.upc-f.chello.nl [80.56.x
8 * * * Request timed out.
9 * f229062.upc-f.chello.nl [80.56.x] reports: Destination host unreachable.

they also stated this
The router does respond, but with a destination host unreachable for its own IPv4 address, strange. A traceroute from here also looks a bit strange, why the trace does not end at hop 7 is not clear to me.
The first command got mixed up. Please run
Code:
iptables-save -c | grep icmp
 
i have something strange suddenly icmp pings are not long working

see it worked before
View attachment 64874
respond from icmp ping is still on
View attachment 64875

i have my isp modem in bridge mode
nothing has changed

This is an ASUS issue. I have ran into this several times when hosting servers inside my network and not in a DMZ. Im not sure what the radial is supposed to do but I just put in a forwarding entry for the ICMP protocol and it works fine. I have seen this on several generations of ASUS routers with stock firmware. Its likely the radial is not doing what we expect it to but could still be working as designed.
 
Status
Not open for further replies.

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top