D-Link Wireless Routers for Home and Small Business > DIR-882

Understanding the log file errors [DHCPS-6]

(1/2) > >>

AmyC:
Since setting up our new DIR-882-US A1 there is a continuing error that repeats every 1 minute in our log. Can anyone tell me what exactly error below means?
2018-01-20 13:20:55 [DHCPS-6]: configure_global_option: ****1131****
2018-01-20 13:20:55 [DHCPS-6]: dhcp6s_main: failed to parse configuration file
We have it set up as a DHCP server for our in home network as IP 192.168.1.1. It connects to a Surfboard SB6141 Modem that provides our cable-internet services. The Surfboard claims to also work as a DHCP server if we didn't have a router,  but it's IP range is 192.168.100.1 and it claims it would assign 192.168.100.11 - .42 so I don't believe this is a conflict issue but am not sure.

FurryNutz:
Can you do a factory reset and set up the router from scratch and use the default IP address pool of 192.168.0.1 and see if the same thing happens?

Set IPv6 to Local Only and save settings and check

What is your ISP service?
Does your ISP service have native IPv6 support?

Is the router working otherwise?

AmyC:
Sorry, just getting back to this. They do support IPV6 and according to checks at https://test-ipv6.com/ it is working.  We have Spectrum Cable formerly known as Time Warner. It's been pretty stable and this error in the log has been chronic. I have not factory reset recently though have several times trying to force the faulty beta KRACK patch before tech support confirmed it was faulty. It doesn't seem to be doing any harm as far as I can tell, but then it could be interfering with speed at times because we do see some lagging on the network in general.

AmyC:
P.S. I will try this and let you know (reset and IP change)

FurryNutz:
OK, D-Link has pulled the faulty KRACK beta FW from the site as users were experiencing problems with it. Please factory reset, load v1.01 FW from last year, factory reset then set up the router again from scratch and enable IPv6 configration for your ISP and check the logs and let us know if this is still happening.

Navigation

[0] Message Index

[#] Next page