muffintastic
Senior Member
Hey,
So, recently I have been having these syslog errors;
I am with Sky Fibre, which is connected and working with an AC3200, all that MAC address OPTION 61 rubbish is fine, then in the latest build for it 380.69 I had that same error with IPV6 errors, which is native on my line, and websites would break or a laptop/desktop couldn't get an local IP to access the network / WAN.
So, I decided to go back to 380.68_4 and IPV6 worked again, and yest I did a clearn NVRAM as such, it's that error with miniupnp that's all of sudden started popping up and will break the connection for 5 minutes and the only cure is either turn UPNP off or reboot the router. Could someone shed any light on this error or is it a hardware failure about to occur?
I am planning to go back to 380.69 and doing a complete NVRAM clear 30/30/30 and starting from scratch again.
So, recently I have been having these syslog errors;
Code:
Jan 19 16:01:56 miniupnpd[676]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jan 19 16:01:56 miniupnpd[676]: Failed to get IP for interface eth0
Jan 19 16:01:56 miniupnpd[676]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
I am with Sky Fibre, which is connected and working with an AC3200, all that MAC address OPTION 61 rubbish is fine, then in the latest build for it 380.69 I had that same error with IPV6 errors, which is native on my line, and websites would break or a laptop/desktop couldn't get an local IP to access the network / WAN.
So, I decided to go back to 380.68_4 and IPV6 worked again, and yest I did a clearn NVRAM as such, it's that error with miniupnp that's all of sudden started popping up and will break the connection for 5 minutes and the only cure is either turn UPNP off or reboot the router. Could someone shed any light on this error or is it a hardware failure about to occur?
I am planning to go back to 380.69 and doing a complete NVRAM clear 30/30/30 and starting from scratch again.