1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

not enough IP addresses given

Discussion in 'General Wireless Discussion' started by Tuba, Nov 13, 2018.

  1. Tuba

    Tuba Occasional Visitor

    Joined:
    Oct 23, 2017
    Messages:
    11
    My Asus RT-N66U router log often has this line:

    It's also been losing internet connection overnight so I think it might be related.

    But I've searched for hours and cannot find a clue about this.

    Any ideas?
     
  2. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    6,990
    Location:
    UK
    That's a normal message and can be ignored. BTW PPTP is regarded as insecure so I suggest you use OpenVPN instead if you can.
     
  3. Tuba

    Tuba Occasional Visitor

    Joined:
    Oct 23, 2017
    Messages:
    11
    Thank you!

    I see that PPTP is Point-to-Point Tunneling Protocol. Although I have played around with the VPN settings of my router, I never actually used it.

    I'll try OpenVPN or maybe I'll turn VPN off until I need it.

    Maybe it will fix my nightly connectivity loss!
     
  4. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    6,990
    Location:
    UK
    Look for other clues in the router's syslog.
     
  5. Tuba

    Tuba Occasional Visitor

    Joined:
    Oct 23, 2017
    Messages:
    11
    I've been trying for days. Router logs are the one place where my Google-Fu fails completely.

    Mind if I post some snippets here?
     
  6. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    6,990
    Location:
    UK
    Post it here or upload it to somewhere like pastebin if it's too big. Make sure it covers the period before and after the event. Don't doctor the output as that will only confuse any analysis (but change any references to your public WAN IP address).
     
  7. Tuba

    Tuba Occasional Visitor

    Joined:
    Oct 23, 2017
    Messages:
    11
    Keep trying to post the log but it keeps getting blocked for security on this forum.

    Below is the most I can post before it blocks me. Will try to post a different way. Seriously weird.
    ===================================================
    Here is part of the router log file around the time I unplugged the Ethernet cable from the Verizon FIOS ONT that leads to the router and then plugged it back in. That is how I've been able to get the internet working again.

    192.168.1.10 is the address of my pi-hole DNS ad-blocking Raspberry pi. Don't know what the #53 part means.

    Anything in here look odd?
     
  8. Tuba

    Tuba Occasional Visitor

    Joined:
    Oct 23, 2017
    Messages:
    11
    Here is the log in PNG.
    Tried uploading as a text file but it wouldn't work.
     

    Attached Files:

    Last edited: Nov 13, 2018
  9. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    6,990
    Location:
    UK
    We need to see the log from before you unplugged the Ethernet cable.
     
  10. Tuba

    Tuba Occasional Visitor

    Joined:
    Oct 23, 2017
    Messages:
    11
    Here is the log before unplugging, as a text file.
    Just before this part, the router was rebooted. I had it set to reboot daily at 4am.
     

    Attached Files:

  11. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    6,990
    Location:
    UK
    I can't see anything obvious from the log. It's difficult to know whether the client activity or the incoming connections on port 80 are suspicious as you have redacted so much of the log despite me specifically asking you not to do that.

    Next time it happens try to do some diagnosis from the clients to see whether you have actually lost internet connectivity or whether it's just a DNS problem.
     
  12. Tuba

    Tuba Occasional Visitor

    Joined:
    Oct 23, 2017
    Messages:
    11
    Thanks. I made sure to cover before and after the connection loss. I redacted the IP addresses just because I'm paranoid about putting that stuff on the web (even though they are only internal addresses, they are static). Didn't think that would impact the analysis.

    Good news is that I didn't lose internet last night. The only change was to remove my nightly 4am reboot of the router and to change the WPS button from radio toggle to WPS (I read the button sometimes malfunctions and I don't use it anyway). I expect stopping the reboot fixed it but will post back if I lose connection tonight.

    Thanks again for the help!