NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
TylerDNA
Oct 20, 2017Tutor
Cannot find C6300 debug page
I cannot find the debug page for my C6300. I need it to reset the clock and make some other tweaks to the router's functioning. I have tried http://192.168.0.1/debug.htm (with and without http a...
antinode
Oct 20, 2017Guru
> My router's clock is off by an hour [...]
Time zone?
> [...] I am also getting repeated requests for UDP port 123 in the
> event log for system clock checking.
An actual log excerpt might be more informative than that
description.
> I cannot find the debug page for my C6300. [...]
You might try one of the available programs intended to enable Telnet
access. (I use this: http://antinode.info/nte ) Around here (D7000,
V1.0.1.50_1.0.1) for example:
# ls -l /www/*deb*
-rw-rw-r-- 1 513 514 4279 Jun 22 07:59 /www/debug.htm
-rw-rw-r-- 1 513 514 4627 Jun 22 07:59 /www/debug_mbm.htm
-rw-rw-r-- 1 513 514 573 Jun 22 07:59 /www/debuginfo.htm
- TylerDNAOct 20, 2017Tutor
Copy of Logs:
Description Count Last Occurrence Target Source [DoS attack] Port Scan PROTO:UDP SPT:123 DPT:123 1 Friday, 20 Oct 2017 13:17:55 192.168.0.85 17.253.20.125 [DoS attack] Port Scan PROTO:UDP SPT:123 DPT:123 1 Friday, 20 Oct 2017 13:17:54 192.168.0.70 17.253.20.253 [DoS attack] Port Scan PROTO:UDP SPT:123 DPT:123 1 Friday, 20 Oct 2017 13:17:53 192.168.0.85 17.253.20.125 [DoS attack] Port Scan PROTO:UDP SPT:123 DPT:123 1 Friday, 20 Oct 2017 13:17:52 192.168.0.70 17.253.20.253 [DoS attack] Port Scan PROTO:UDP SPT:123 DPT:123 1 Friday, 20 Oct 2017 13:17:50 192.168.0.85 17.253.20.125 [DoS attack] Port Scan PROTO:UDP SPT:123 DPT:123 1 Friday, 20 Oct 2017 13:17:48 192.168.0.70 17.253.20.253 [DoS attack] Port Scan PROTO:UDP SPT:123 DPT:123 1 Friday, 20 Oct 2017 13:17:47 192.168.0.85 17.253.20.253 [DoS attack] Port Scan PROTO:UDP SPT:123 DPT:123 1 Friday, 20 Oct 2017 13:17:46 192.168.0.32 17.253.20.253 [DoS attack] Port Scan PROTO:UDP SPT:123 DPT:123 1 Friday, 20 Oct 2017 13:17:45 192.168.0.85 17.253.20.253 Firmware Version
V2.01.18There is no option to check or change the time zone for this version of firmware. The manual says:Select ADVANCED > Security > Schedule.
Specify when to block keywords and services:
Days to Block. Select the check box for each day that you want to block the keywords or select the Every Day check box, which automatically selects the check boxes for all days.
Time of Day to Block. Select a start and end time in 24-hour format, or select All Day for 24-hour blocking.
Select your time zone from the menu.
The menu mentioned in #3 does not exist in my settings.
I will check out the debug route you mentioned. Thank you for taking your time to respond to my post.
- TylerDNAOct 20, 2017Tutor
My computer does not like the nte.exe, it keeps coming up with missing .dll errors (missing MSVCR100D.dll). I cannot find anything on google about telnetting into my router. There is most definitely not a way to enable telnet on the GUI, at least not that I can find.
I imagine there is a way to UART into it, but I'd rather not bust out the solder.
- antinodeOct 20, 2017Guru
> [...] (I use this: http://antinode.info/nte )
> [...] (missing MSVCR100D.dll) [...]
For _me_ it works on Windows, but I have Visual Studio installed
there. (I use it mostly on non-Windows systems.) For where to find the
missing DLL:
https://community.netgear.com/t5/x/x/m-p/1388903
> There is most definitely not a way to enable telnet on the GUI, at
> least not that I can find.
I've done it only on plain routers and DSL modem+routers. No bets on
a cable modem+router, but it's a cheap experiment to run. Cable-TV ISPs
tend to be fussy about the firmware which is connected to their
networks. If there's no time-zone setting on the thing, then the ISP
may be responsible for proper time-keeping. On my D7000, debug_mbm.htm
has an "EnableTelnetServer" button, but it leads to a pinkish "403
Forbidden" page. (More impressive Netgear router firmware.)
> Copy of Logs:
> [...]
Looks bogus. It's hard to imagine why the router would be forwarding
incoming NTP (123) traffic to anyone on the LAN. It could be
complaining (spuriously) about responses to outgoing NTP traffic.