Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    WAN DHCP Issue

    Scheduled Pinned Locked Moved
    DHCP and DNS
    2
    3
    3.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      PistolPete
      last edited by

      Hi All,

      I have my WAN connected to my cable modem which gets it's IP address via DHCP from my ISP and passes that to the WAN port (Is this 0 IP bridging??)

      Anyway, in the logs a DHCPREQUEST goes out to 255.255.255.255, and an offer comes back from 10.x.x.x and give my IP address with a 5 day lease.  All good so far.
      However, in 2.5 days the logs start filling with DHCPREQUESTs repeatedly going to a 62.x.x.x (this is a public IP assigned to my ISP but is the address of the TFTP server for pulling the cable modem config file from, not the DHCP server)

      2010-05-03 10:55:14,Daemon.Info,192.168.0.1,May  3 10:55:14 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:55:14,Daemon.Info,192.168.0.1,May  3 10:55:14 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:55:14,Daemon.Info,192.168.0.1,May  3 10:55:14 dhclient[17663]: SENDING DIRECT
2010-05-03 10:55:14,Daemon.Info,192.168.0.1,May  3 10:55:14 dhclient[17663]: SENDING DIRECT
2010-05-03 10:55:27,Daemon.Info,192.168.0.1,May  3 10:55:27 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:55:27,Daemon.Info,192.168.0.1,May  3 10:55:27 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:55:27,Daemon.Info,192.168.0.1,May  3 10:55:27 dhclient[17663]: SENDING DIRECT
2010-05-03 10:55:27,Daemon.Info,192.168.0.1,May  3 10:55:27 dhclient[17663]: SENDING DIRECT
2010-05-03 10:55:41,Daemon.Info,192.168.0.1,May  3 10:55:41 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:55:41,Daemon.Info,192.168.0.1,May  3 10:55:41 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:55:41,Daemon.Info,192.168.0.1,May  3 10:55:41 dhclient[17663]: SENDING DIRECT
2010-05-03 10:55:41,Daemon.Info,192.168.0.1,May  3 10:55:41 dhclient[17663]: SENDING DIRECT
2010-05-03 10:55:58,Daemon.Info,192.168.0.1,May  3 10:55:58 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:55:58,Daemon.Info,192.168.0.1,May  3 10:55:58 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:55:58,Daemon.Info,192.168.0.1,May  3 10:55:58 dhclient[17663]: SENDING DIRECT
2010-05-03 10:55:58,Daemon.Info,192.168.0.1,May  3 10:55:58 dhclient[17663]: SENDING DIRECT
2010-05-03 10:56:16,Daemon.Info,192.168.0.1,May  3 10:56:16 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:56:16,Daemon.Info,192.168.0.1,May  3 10:56:16 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:56:16,Daemon.Info,192.168.0.1,May  3 10:56:16 dhclient[17663]: SENDING DIRECT
2010-05-03 10:56:16,Daemon.Info,192.168.0.1,May  3 10:56:16 dhclient[17663]: SENDING DIRECT
2010-05-03 10:56:32,Daemon.Info,192.168.0.1,May  3 10:56:32 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:56:32,Daemon.Info,192.168.0.1,May  3 10:56:32 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:56:32,Daemon.Info,192.168.0.1,May  3 10:56:32 dhclient[17663]: SENDING DIRECT
2010-05-03 10:56:32,Daemon.Info,192.168.0.1,May  3 10:56:32 dhclient[17663]: SENDING DIRECT
2010-05-03 10:56:52,Daemon.Info,192.168.0.1,May  3 10:56:52 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:56:52,Daemon.Info,192.168.0.1,May  3 10:56:52 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:56:52,Daemon.Info,192.168.0.1,May  3 10:56:52 dhclient[17663]: SENDING DIRECT
2010-05-03 10:56:52,Daemon.Info,192.168.0.1,May  3 10:56:52 dhclient[17663]: SENDING DIRECT
2010-05-03 10:57:43,Daemon.Info,192.168.0.1,May  3 10:57:43 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:57:43,Daemon.Info,192.168.0.1,May  3 10:57:43 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:57:43,Daemon.Info,192.168.0.1,May  3 10:57:43 dhclient[17663]: SENDING DIRECT
2010-05-03 10:57:43,Daemon.Info,192.168.0.1,May  3 10:57:43 dhclient[17663]: SENDING DIRECT
2010-05-03 10:59:16,Daemon.Info,192.168.0.1,May  3 10:59:16 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:59:16,Daemon.Info,192.168.0.1,May  3 10:59:16 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:59:16,Daemon.Info,192.168.0.1,May  3 10:59:16 dhclient[17663]: SENDING DIRECT
2010-05-03 10:59:16,Daemon.Info,192.168.0.1,May  3 10:59:16 dhclient[17663]: SENDING DIRECT
2010-05-03 10:59:38,Daemon.Info,192.168.0.1,May  3 10:59:38 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:59:38,Daemon.Info,192.168.0.1,May  3 10:59:38 dhclient[17663]: DHCPREQUEST on re0 to 62.30.64.113 port 67
2010-05-03 10:59:38,Daemon.Info,192.168.0.1,May  3 10:59:38 dhclient[17663]: SENDING DIRECT
2010-05-03 10:59:38,Daemon.Info,192.168.0.1,May  3 10:59:38 dhclient[17663]: SENDING DIRECT

      Eventually, it'll send a request to 255.255.255.255 and all will be well again.

      Should I be bothered by the extra requests, can I stop them?

      1 Reply Last reply Reply Quote 0
      • P
        PistolPete
        last edited by

        Anyone??

        1 Reply Last reply Reply Quote 0
        • Cry HavokC
          Cry Havok
          last edited by

          I saw exactly that problem on the Telewest (now VirginMedia) network many years ago and had some chats with their back end technical staff at the time (I have a background in networking and took great care to email in a ticket that would demonstrate the problem, that I knew what I was talking about and that I wanted to help them fix their system).

          The problem was with the DHCP servers at the ISP and wasn't something that could be fixed at the customer end.  They did fix it, but obviously the problem is back.  There isn't anything you can do unfortunately except log a ticket with them and get frustrated over explaining the problem (since most of their customer base won't have noticed).

          1 Reply Last reply Reply Quote 0
          • First post
            Last post