Yesterday evening our ADSL stopped working (it does that a lot... fiber installation will hopefully be finished by the end of the month though!) and then the router didn't respond to DNS queries even for local addresses...
I'm not sure why it happened, shouldn't the LAN part work a normally even when WAN is down? Unfortunately it was late so I didn't have time to make a deeper analyze.
Maybe this is just a problem of how the WAN status is identified?
I also noticed some kind of redirect in the browser, I don't remember the exact URL now but it was something like http://<router IP>/<some_file>.htm?flag=3
I just remember the flag part, that is was an underscore in the file name, it was a .htm and that it had no port information. My router is set up for https only and on a 4 digit port number to not interfere with having port 80 forwarded to another machine. So of course there was no response, the router doesn't listen on port 80.
I can imagine it could be redirect to a page telling the WAN is down, but why would I reach such a page when trying to connect to a computer on the LAN?
I'm not sure why it happened, shouldn't the LAN part work a normally even when WAN is down? Unfortunately it was late so I didn't have time to make a deeper analyze.
Maybe this is just a problem of how the WAN status is identified?
I also noticed some kind of redirect in the browser, I don't remember the exact URL now but it was something like http://<router IP>/<some_file>.htm?flag=3
I just remember the flag part, that is was an underscore in the file name, it was a .htm and that it had no port information. My router is set up for https only and on a 4 digit port number to not interfere with having port 80 forwarded to another machine. So of course there was no response, the router doesn't listen on port 80.
I can imagine it could be redirect to a page telling the WAN is down, but why would I reach such a page when trying to connect to a computer on the LAN?
