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

    DHCP does not work correctly on WAN interface

    DHCP and DNS
    8
    15
    13.6k
    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.
    • D
      danswartz
      last edited by

      Hmmm, could be an odd incompatibility between the freebsd dhcp client and your ISP's dhcp server.  Not sure offhand what to suggest…

      p.s. some years back, a friend of mine had been using a firewall appliance from GTA and had to replace it with a different product since their DHCP client seemed to misbehave when dealing with his new ISP.  I mention this because GTA's firewall product is based on a FreeBSD kernel and utilities, so it wouldn't be the first time I have seen this.

      1 Reply Last reply Reply Quote 0
      • AhnHELA
        AhnHEL
        last edited by

        From the GUI, go to Diagnostics/Command

        type in "dhclient fxp1"

        Click on Execute.

        Should stop those annoying requests.

        For those with other NIC's, the command is "dhclient (WAN interface name)"

        http://www.nabble.com/dhclient-cant-renew-lease.-td22166599.html

        AhnHEL (Angel)

        1 Reply Last reply Reply Quote 0
        • L
          liontaur
          last edited by

          I'm having the same problem but thankfully i've got a static IP from my ISP (sunwave.net). When I changed my account with them to static IPs they said to still use DHCP for whatever reason. Now my logs are filling up with

          Oct 29 18:42:42 	dhclient[350]: SENDING DIRECT
Oct 29 18:42:42 	dhclient[350]: DHCPREQUEST on bge0 to 208.98.210.129 port 67
Oct 29 18:41:53 	dhclient[350]: SENDING DIRECT
Oct 29 18:41:53 	dhclient[350]: DHCPREQUEST on bge0 to 208.98.210.129 port 67
Oct 29 18:41:13 	dhclient[350]: SENDING DIRECT
Oct 29 18:41:13 	dhclient[350]: DHCPREQUEST on bge0 to 208.98.210.129 port 67
Oct 29 18:40:47 	dhclient[350]: SENDING DIRECT
Oct 29 18:40:47 	dhclient[350]: DHCPREQUEST on bge0 to 208.98.210.129 port 67
Oct 29 18:40:25 	dhclient[350]: SENDING DIRECT
Oct 29 18:40:25 	dhclient[350]: DHCPREQUEST on bge0 to 208.98.210.129 port 67
Oct 29 18:40:02 	dhclient[350]: SENDING DIRECT
Oct 29 18:40:02 	dhclient[350]: DHCPREQUEST on bge0 to 208.98.210.129 port 67

          Until finally

          Oct 29 18:43:34 	dhclient[350]: bound to 208.98.XXX.XXX -- renewal in 43200 seconds.
Oct 29 18:43:34 	dhclient[350]: DHCPACK from 208.98.210.131
Oct 29 18:43:34 	dhclient[350]: DHCPREQUEST on bge0 to 255.255.255.255 port 67

          So no real problem for me since everything still works, just a pain having all this crap in the logs.

          1 Reply Last reply Reply Quote 0
          • AhnHELA
            AhnHEL
            last edited by

            Yes, eventually it will get an address but will repeat SENDING DIRECT after the next renewal time filling up your logs again.

            Should it happen again, just use the command I mentioned above and it should stop it for good until your next reboot.

            I have 3 pfSense sites, this happens on both my sites that use Optimum Online Cable.  The site that has Time Warner Road Runner Cable does not have this issue at all so it has something to do with the ISP's DHCP Server.

            AhnHEL (Angel)

            1 Reply Last reply Reply Quote 0
            • A
              anetre
              last edited by

              Had the same problem DHCPREQUEST but received no DHCPACK on opt1. However, proper functioning of the WAN.
              Normally dhclinet attempt to get a new IP and it begins with the mid-Lessing time, but when lesing time has expired will send a broadcast, then you lose the network maybe 1-2 seconds before regaining the connection and have an IP address .

              Did a packet capture on opt1 but saw no DHCP request to the DHCP server, do not know where the traffic went, but it did not take the correct route, try adding a static route to the server and then it worked immediately, and renew the less every time.

              The problem seems to be the ISP's DHCP server is not in the same subnet as opt1 IP-address and traffic does not route correctly. They use a DHCP Relay function to a central DHCP server for every customer, insted of one in every local telephone station. (i am using ADSL)

              To finde the server to make a static route
              cat /var/db/dhclient.leases. [interface name]
              look for the "option dhcp-server-identifier", where you'll find the DHCP servers IP-adress and then add a static route for it

              Before:

              
Nov 6 15:22:46 	dhclient[400]: bound to 81.233.xx.xxx -- renewal in 600 seconds.
Nov 6 15:22:46 	dhclient[400]: DHCPACK from 81.232.150.1
Nov 6 15:22:46 	dhclient[400]: DHCPREQUEST on em2 to 255.255.255.255 port 67
Nov 6 15:21:51 	dhclient[400]: SENDING DIRECT
Nov 6 15:21:51 	dhclient[400]: DHCPREQUEST on em2 to 62.20.251.122 port 67
Nov 6 15:21:17 	dhclient[400]: SENDING DIRECT
Nov 6 15:21:17 	dhclient[400]: DHCPREQUEST on em2 to 62.20.251.122 port 67

              After:

              
Nov 6 15:42:46 	dhclient[400]: bound to 81.233.xx.xxx -- renewal in 600 seconds.
Nov 6 15:42:46 	dhclient[400]: DHCPACK from 62.20.251.122
Nov 6 15:42:46 	dhclient[400]: SENDING DIRECT
Nov 6 15:42:46 	dhclient[400]: DHCPREQUEST on em2 to 62.20.251.122 port 67
Nov 6 15:32:46 	dhclient[400]: bound to 81.233.xx.xxx -- renewal in 600 seconds.
Nov 6 15:32:46 	dhclient[400]: DHCPACK from 62.20.251.122
Nov 6 15:32:46 	dhclient[400]: SENDING DIRECT
Nov 6 15:32:46 	dhclient[400]: DHCPREQUEST on em2 to 62.20.251.122 port 67
              1 Reply Last reply Reply Quote 0
              • W
                wallabybob
                last edited by

                Your default route is not over the WAN interface?

                1 Reply Last reply Reply Quote 0
                • 8
                  80286
                  last edited by

                  I have similar problem - my pfsense 1.2.2 can't renew IP address if the modem was suddenly powered down, lost link from the provider OR if the WAN cable was unplugged without properly releasing the IP address.
                  If any of the above happens - the whole LAN will sit without internet until you do a manual release/renew or completely restart the router.

                  Apparently pfsense after doing full handshake first time doesn't do it afterwards and hence not getting an IP address. But this is just a guess.

                  We have two routers to choose from: crappy Dlink that freezes under heavy load, and pfsense that doesn't freeze, but has this significant DHCP renewing problem.

                  Is there any way to schedule pfsense to automatically reboot at, say 7AM everyday - because right now what they do is manually power down the router (using a button on the case) and pfsense tells in the logs that "/was not properly unmounted, filesystem not clean". I am afraid its not going to boot one day.

                  As far as I know my provider uses Cisco routers, may be they have some proprietary DHCP algorithms.

                  Here is a log if anybody is interested and thank you.

                  Nov 10 16:35:46 	kernel: fxp0: link state changed to DOWN
Nov 10 16:35:53 	kernel: fxp0: link state changed to UP
Nov 10 16:35:57 	check_reload_status: rc.linkup starting
Nov 10 16:35:59 	php: : Processing fxp0 - start
Nov 10 16:35:59 	php: : DEVD Ethernet attached event for fxp0
Nov 10 16:35:59 	php: : HOTPLUG: Configuring wan interface fxp0
Nov 10 16:36:02 	dhclient[949]: short write: wanted 20 got 0 bytes
Nov 10 16:36:02 	dhclient[949]: short write: wanted 20 got 0 bytes
Nov 10 16:36:02 	dhclient[949]: exiting.
Nov 10 16:36:02 	dhclient[949]: exiting.
Nov 10 16:36:02 	dhclient[40814]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
Nov 10 16:36:11 	last message repeated 4 times
Nov 10 16:36:19 	dhclient[40814]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 2
Nov 10 16:36:21 	dhclient[40814]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 3
Nov 10 16:36:24 	dhclient[40814]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 8
Nov 10 16:36:32 	dhclient[40814]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 14
Nov 10 16:36:41 	kernel: fxp0: link state changed to DOWN
Nov 10 16:36:42 	kernel: fxp0: link state changed to UP
Nov 10 16:36:46 	dhclient[40814]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 9
Nov 10 16:36:55 	dhclient[40814]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 15
Nov 10 16:37:10 	dhclient[40814]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 10
Nov 10 16:37:14 	kernel: fxp0: link state changed to DOWN
Nov 10 16:37:20 	dhclient[40814]: No DHCPOFFERS received.
Nov 10 16:37:20 	dhclient[40814]: Trying recorded lease 10.10.67.20
Nov 10 16:37:21 	dhclient[40814]: bound: renewal in 68860 seconds.
Nov 10 16:37:23 	dnsmasq[979]: exiting on receipt of SIGTERM
Nov 10 16:37:24 	dnsmasq[41025]: started, version 2.39 cachesize 150
Nov 10 16:37:24 	dnsmasq[41025]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
Nov 10 16:37:24 	dnsmasq[41025]: reading /etc/resolv.conf
Nov 10 16:37:24 	dnsmasq[41025]: using nameserver 10.10.10.84#53
Nov 10 16:37:24 	dnsmasq[41025]: using nameserver 10.10.10.85#53
Nov 10 16:37:24 	dnsmasq[41025]: read /etc/hosts - 2 addresses
Nov 10 16:37:26 	dhcpd: Internet Systems Consortium DHCP Server V3.0.5
Nov 10 16:37:26 	dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Nov 10 16:37:26 	dhcpd: All rights reserved.
Nov 10 16:37:26 	dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 10 16:37:26 	php: : Processing start -
Nov 10 16:37:26 	php: : Not a valid interface action ""
Nov 10 16:37:26 	php: : Processing -
Nov 10 16:37:26 	php: : Not a valid interface action ""
Nov 10 16:37:26 	check_reload_status: reloading filter
Nov 10 16:37:29 	kernel: fxp0: link state changed to UP
Nov 10 16:37:32 	kernel: fxp0: link state changed to DOWN
Nov 10 16:37:33 	kernel: fxp0: link state changed to UP
Nov 10 16:37:34 	check_reload_status: rc.linkup starting
Nov 10 16:37:36 	php: : Processing fxp0 - start
Nov 10 16:37:36 	php: : DEVD Ethernet attached event for fxp0
Nov 10 16:37:36 	php: : HOTPLUG: Configuring wan interface fxp0
Nov 10 16:37:39 	dhclient[40997]: short write: wanted 20 got 0 bytes
Nov 10 16:37:39 	dhclient[40997]: short write: wanted 20 got 0 bytes
Nov 10 16:37:39 	dhclient[40997]: exiting.
Nov 10 16:37:39 	dhclient[40997]: exiting.
Nov 10 16:37:39 	dhclient[41213]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
Nov 10 16:37:47 	last message repeated 3 times
Nov 10 16:37:51 	dhclient[41213]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1
Nov 10 16:37:52 	dhclient[41213]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1
Nov 10 16:37:53 	dhclient[41213]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 2
Nov 10 16:37:55 	dhclient[41213]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 5
Nov 10 16:38:00 	dhclient[41213]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 10
Nov 10 16:38:10 	dhclient[41213]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 20
Nov 10 16:38:10 	dhclient[41213]: DHCPOFFER from 10.10.67.253
Nov 10 16:38:12 	dhclient[41213]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
Nov 10 16:38:12 	dhclient[41213]: DHCPACK from 10.10.67.253
Nov 10 16:38:12 	dhclient[41213]: bound to 10.10.66.67 -- renewal in 259200 seconds.
Nov 10 16:38:15 	dnsmasq[41025]: exiting on receipt of SIGTERM
Nov 10 16:38:16 	dnsmasq[41387]: started, version 2.39 cachesize 150
Nov 10 16:38:16 	dnsmasq[41387]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
Nov 10 16:38:16 	dnsmasq[41387]: reading /etc/resolv.conf
Nov 10 16:38:16 	dnsmasq[41387]: using nameserver 10.10.10.84#53
Nov 10 16:38:16 	dnsmasq[41387]: using nameserver 10.10.10.85#53
Nov 10 16:38:16 	dnsmasq[41387]: read /etc/hosts - 2 addresses
Nov 10 16:38:17 	dhcpd: Internet Systems Consortium DHCP Server V3.0.5
Nov 10 16:38:17 	dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Nov 10 16:38:17 	dhcpd: All rights reserved.
Nov 10 16:38:17 	dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 10 16:38:17 	php: : Processing start - fxp0
Nov 10 16:38:17 	php: : Hotplug event detected for start but ignoring since interface is not set for DHCP
Nov 10 16:38:17 	php: : Processing fxp0 - start
Nov 10 16:38:17 	php: : DEVD Ethernet attached event for fxp0
Nov 10 16:38:17 	php: : HOTPLUG: Configuring wan interface fxp0
Nov 10 16:38:21 	dhclient[41359]: short write: wanted 20 got 0 bytes
Nov 10 16:38:21 	dhclient[41359]: short write: wanted 20 got 0 bytes
Nov 10 16:38:21 	dhclient[41359]: exiting.
Nov 10 16:38:21 	dhclient[41359]: exiting.
Nov 10 16:38:21 	dhclient[41457]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
Nov 10 16:38:21 	dhclient[41457]: DHCPACK from 10.10.67.254
Nov 10 16:38:21 	dhclient[41457]: bound to 10.10.66.67 -- renewal in 259200 seconds.
Nov 10 16:38:23 	dnsmasq[41387]: exiting on receipt of SIGTERM
Nov 10 16:38:25 	dnsmasq[41540]: started, version 2.39 cachesize 150
Nov 10 16:38:25 	dnsmasq[41540]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
Nov 10 16:38:25 	dnsmasq[41540]: reading /etc/resolv.conf
Nov 10 16:38:25 	dnsmasq[41540]: using nameserver 10.10.10.84#53
Nov 10 16:38:25 	dnsmasq[41540]: using nameserver 10.10.10.85#53
Nov 10 16:38:25 	dnsmasq[41540]: read /etc/hosts - 2 addresses
Nov 10 16:38:26 	dhcpd: Internet Systems Consortium DHCP Server V3.0.5
Nov 10 16:38:26 	dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Nov 10 16:38:26 	dhcpd: All rights reserved.
Nov 10 16:38:26 	dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 10 16:38:26 	php: : Processing start -
Nov 10 16:38:26 	php: : Not a valid interface action ""
Nov 10 16:38:26 	php: : Processing -
Nov 10 16:38:26 	php: : Not a valid interface action ""
Nov 10 16:38:26 	check_reload_status: rc.newwanip starting
Nov 10 16:38:28 	php: : Informational: rc.newwanip is starting fxp0.
Nov 10 16:38:28 	php: : rc.newwanip working with (IP address: 10.10.66.67) (interface: wan) (interface real: fxp0).
Nov 10 16:38:35 	php: : Informational: DHClient spawned /etc/rc.newwanip and the new ip is wan - 10.10.66.67.
Nov 10 16:38:35 	php: : Creating rrd update script
Nov 10 16:38:39 	php: : Resyncing configuration for all packages.
Nov 10 16:38:41 	kernel: fxp0: promiscuous mode disabled
Nov 10 16:38:44 	php: : pfSense package system has detected an ip change 10.10.67.20 -> 10.10.66.67 ... Restarting packages.
Nov 10 16:38:44 	php: : Configuring slbd
Nov 10 16:38:44 	check_reload_status: reloading filter
Nov 10 16:38:49 	check_reload_status: updating dyndns
Nov 10 16:39:58 	kernel: fxp0: link state changed to DOWN
Nov 10 16:40:41 	kernel: fxp0: link state changed to UP
Nov 10 16:40:41 	check_reload_status: rc.linkup starting
Nov 10 16:40:43 	php: : Processing fxp0 - start
Nov 10 16:40:43 	php: : DEVD Ethernet attached event for fxp0
Nov 10 16:40:43 	php: : HOTPLUG: Configuring wan interface fxp0
Nov 10 16:40:46 	dhclient[41511]: short write: wanted 20 got 0 bytes
Nov 10 16:40:46 	dhclient[41511]: short write: wanted 20 got 0 bytes
Nov 10 16:40:46 	dhclient[41511]: exiting.
Nov 10 16:40:46 	dhclient[41511]: exiting.
Nov 10 16:40:46 	dhclient[42111]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
Nov 10 16:40:55 	last message repeated 3 times
Nov 10 16:41:05 	dhclient[42111]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1
Nov 10 16:41:06 	dhclient[42111]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 2
Nov 10 16:41:08 	dhclient[42111]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 3
Nov 10 16:41:11 	dhclient[42111]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 5
Nov 10 16:41:16 	dhclient[42111]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 5
Nov 10 16:41:21 	dhclient[42111]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 8
Nov 10 16:41:29 	dhclient[42111]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 21
Nov 10 16:41:29 	kernel: fxp0: link state changed to DOWN
Nov 10 16:41:30 	kernel: fxp0: link state changed to UP
Nov 10 16:41:32 	kernel: fxp0: link state changed to DOWN
Nov 10 16:41:36 	kernel: fxp0: link state changed to UP
Nov 10 16:41:50 	dhclient[42111]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 11
Nov 10 16:42:01 	dhclient[42111]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 5
Nov 10 16:42:06 	dhclient[42111]: No DHCPOFFERS received.
Nov 10 16:42:06 	dhclient[42111]: Trying recorded lease 10.10.66.67
Nov 10 16:42:07 	dhclient[42111]: bound: renewal in 258975 seconds.
Nov 10 16:42:09 	dnsmasq[41540]: reading /etc/resolv.conf
Nov 10 16:42:09 	dnsmasq[41540]: using nameserver 10.10.10.84#53
Nov 10 16:42:09 	dnsmasq[41540]: using nameserver 10.10.10.85#53
Nov 10 16:42:09 	dnsmasq[41540]: exiting on receipt of SIGTERM
Nov 10 16:42:10 	dnsmasq[42257]: started, version 2.39 cachesize 150
Nov 10 16:42:10 	dnsmasq[42257]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
Nov 10 16:42:10 	dnsmasq[42257]: reading /etc/resolv.conf
Nov 10 16:42:10 	dnsmasq[42257]: using nameserver 10.10.10.84#53
Nov 10 16:42:10 	dnsmasq[42257]: using nameserver 10.10.10.85#53
Nov 10 16:42:10 	dnsmasq[42257]: read /etc/hosts - 2 addresses
Nov 10 16:42:12 	dhcpd: Internet Systems Consortium DHCP Server V3.0.5
Nov 10 16:42:12 	dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Nov 10 16:42:12 	dhcpd: All rights reserved.
Nov 10 16:42:12 	dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 10 16:42:12 	php: : Processing start -
Nov 10 16:42:12 	php: : Not a valid interface action ""
Nov 10 16:42:12 	php: : Processing -
Nov 10 16:42:12 	php: : Not a valid interface action ""
Nov 10 16:42:12 	check_reload_status: reloading filter
Nov 10 16:42:21 	dhcpd: uid lease 192.168.0.197 for client 00:19:b9:1a:11:45 is duplicate on 192.168.0/24
Nov 10 16:42:21 	dhcpd: uid lease 192.168.0.197 for client 00:19:b9:1a:11:45 is duplicate on 192.168.0/24
Nov 10 16:42:24 	kernel: fxp0: link state changed to DOWN
Nov 10 16:42:26 	kernel: fxp0: link state changed to UP
Nov 10 16:42:30 	check_reload_status: rc.linkup starting
Nov 10 16:42:32 	php: : Processing fxp0 - start
Nov 10 16:42:32 	php: : DEVD Ethernet attached event for fxp0
Nov 10 16:42:32 	php: : HOTPLUG: Configuring wan interface fxp0
Nov 10 16:42:35 	dhclient[42229]: short write: wanted 20 got 0 bytes
Nov 10 16:42:35 	dhclient[42229]: short write: wanted 20 got 0 bytes
Nov 10 16:42:35 	dhclient[42229]: exiting.
Nov 10 16:42:35 	dhclient[42229]: exiting.
Nov 10 16:42:35 	dhclient[42445]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
Nov 10 16:42:45 	last message repeated 4 times
Nov 10 16:42:53 	dhclient[42445]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 2
Nov 10 16:42:55 	dhclient[42445]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 4
Nov 10 16:42:58 	kernel: fxp0: link state changed to DOWN
Nov 10 16:42:59 	dhclient[42445]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 10
Nov 10 16:43:09 	dhclient[42445]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 14
Nov 10 16:43:13 	kernel: fxp0: link state changed to UP
Nov 10 16:43:16 	kernel: fxp0: link state changed to DOWN
Nov 10 16:43:17 	kernel: fxp0: link state changed to UP
Nov 10 16:43:23 	dhclient[42445]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 12
Nov 10 16:43:35 	dhclient[42445]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 12
Nov 10 16:43:47 	dhclient[42445]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 7
Nov 10 16:43:54 	dhclient[42445]: No DHCPOFFERS received.
Nov 10 16:43:54 	dhclient[42445]: Trying recorded lease 10.10.66.67
Nov 10 16:43:55 	dhclient[42445]: bound: renewal in 258867 seconds.
Nov 10 16:43:57 	dnsmasq[42257]: exiting on receipt of SIGTERM
Nov 10 16:43:58 	dnsmasq[42664]: started, version 2.39 cachesize 150
Nov 10 16:43:58 	dnsmasq[42664]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
Nov 10 16:43:58 	dnsmasq[42664]: reading /etc/resolv.conf
Nov 10 16:43:58 	dnsmasq[42664]: using nameserver 10.10.10.84#53
Nov 10 16:43:58 	dnsmasq[42664]: using nameserver 10.10.10.85#53
Nov 10 16:43:58 	dnsmasq[42664]: read /etc/hosts - 2 addresses
Nov 10 16:44:00 	dhcpd: Internet Systems Consortium DHCP Server V3.0.5
Nov 10 16:44:00 	dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Nov 10 16:44:00 	dhcpd: All rights reserved.
Nov 10 16:44:00 	dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 10 16:44:00 	php: : Processing start -
Nov 10 16:44:00 	php: : Not a valid interface action ""
Nov 10 16:44:00 	php: : Processing -
Nov 10 16:44:00 	php: : Not a valid interface action ""
Nov 10 16:44:00 	check_reload_status: reloading filter
Nov 10 16:44:37 	dhcpd: uid lease 192.168.0.196 for client 00:06:5b:50:a3:66 is duplicate on 192.168.0/24
Nov 10 16:46:37 	dhcpd: uid lease 192.168.0.196 for client 00:06:5b:50:a3:66 is duplicate on 192.168.0/24
Nov 10 16:46:37 	dhcpd: uid lease 192.168.0.196 for client 00:06:5b:50:a3:66 is duplicate on 192.168.0/24
Nov 10 16:49:28 	dhcpd: uid lease 192.168.0.197 for client 00:19:b9:1a:11:45 is duplicate on 192.168.0/24
Nov 10 16:49:49 	dhcpd: uid lease 192.168.0.197 for client 00:19:b9:1a:11:45 is duplicate on 192.168.0/24
Nov 10 16:58:41 	check_reload_status: reloading filter
******************NO INTERNET UP UNTIL THIS POINT - I DID MANUAL RELEASE/RENEW HERE**************************
Nov 10 17:15:54 	dhclient[42446]: connection closed
Nov 10 17:15:54 	dhclient[42446]: connection closed
Nov 10 17:15:54 	dhclient[42446]: exiting.
Nov 10 17:15:54 	dhclient[42446]: exiting.
Nov 10 17:15:56 	dhclient[46138]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
Nov 10 17:16:01 	dhclient[46138]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
Nov 10 17:16:01 	dhclient[46138]: DHCPACK from 10.10.67.254
Nov 10 17:16:02 	dhclient[46138]: bound to 10.10.66.67 -- renewal in 259200 seconds.
Nov 10 17:16:02 	check_reload_status: rc.newwanip starting
Nov 10 17:16:04 	php: : Informational: rc.newwanip is starting fxp0.
Nov 10 17:16:04 	php: : rc.newwanip working with (IP address: 10.10.66.67) (interface: wan) (interface real: fxp0).
Nov 10 17:16:10 	php: : Informational: DHClient spawned /etc/rc.newwanip and the new ip is wan - 10.10.66.67.
Nov 10 17:16:10 	dnsmasq[42664]: reading /etc/resolv.conf
Nov 10 17:16:10 	dnsmasq[42664]: using nameserver 10.10.10.84#53
Nov 10 17:16:10 	dnsmasq[42664]: using nameserver 10.10.10.85#53
Nov 10 17:16:10 	php: : Creating rrd update script
Nov 10 17:16:10 	php: : Configuring slbd
Nov 10 17:16:10 	check_reload_status: reloading filter
Nov 10 17:16:15 	check_reload_status: updating dyndns
                  1 Reply Last reply Reply Quote 0
                  • D
                    danswartz
                    last edited by

                    sure, create a cron job.

                    1 Reply Last reply Reply Quote 0
                    • 8
                      80286
                      last edited by

                      In Cron is it possible to schedule release/renew of DHCP lease? How would the script look like?

                      For reboot every day at 6AM, would this be correct? Thank you very much.

                      minute  hour  	mday  	month  	wday  	who  	command
 *   	 6   	 *   	 *   	 *   	root   	shutdown -r now
                      1 Reply Last reply Reply Quote 0
                      • 8
                        80286
                        last edited by

                        Found a better solution here:
                        http://forum.pfsense.org/index.php/topic,17243.msg89348.html#msg89348

                        1 Reply Last reply Reply Quote 0
                        • B
                          basse
                          last edited by

                          Hello!
                          I just installed pfsense and I have the same problem, almost..

                          I only get a lease ack if/when the dhcprequest is sent to 255.255.255.255:

                          boot:
                          Nov 28 09:17:31 dhclient[5711]: DHCPREQUEST on em0 to 255.255.255.255 port 67
                          Nov 28 09:17:32 dhclient[5711]: bound to 85.24.. – renewal in 450 seconds.

                          then, 450 secs later:
                          Nov 28 09:25:04 dhclient[5711]: DHCPREQUEST on em0 to 85.24.202.1 port 67
                          Nov 28 09:25:04 dhclient[5711]: SENDING DIRECT
                          Nov 28 09:25:07 dhclient[5711]: DHCPREQUEST on em0 to 85.24.202.1 port 67
                          Nov 28 09:25:07 dhclient[5711]: SENDING DIRECT

                          this goes on until:
                          Nov 28 09:45:23 dhclient[5711]: DHCPREQUEST on em0 to 255.255.255.255 port 67
                          Nov 28 09:45:24 dhclient[5711]: DHCPACK from 85.24.202.1
                          Nov 28 09:45:24 dhclient[5711]: bound to 85.24.. – renewal in 450 seconds.

                          What I have found so far:
                          On my windows machine, I get a new lease directly after 450 secs, when the DHCPREQUEST is sent directly to the dhcp-server.
                          So I ran wireshark, and the Windows request has lots of more stuff (OPTION, and different stuff in some of the OPTION) than what the PFSENSE-request has...

                          So, any idés of how to solve this?
                          The problem is that sometimes the 255.255.255.255 request after 2x450 secs gives me a new IP, or, does not work at all, so that I manually has to go into the pfsense webinterface and renew the ip :(

                          this is what pfsense looks like: ( i tried to add as much as I could to the dhcpd-conf file, but it´s still not enough)
                          http://basse.host22.com/junk/greenshot_2009-11-28_09-53-02.png
                          and windows:
                          http://basse.host22.com/junk/greenshot_2009-11-28_09-52-46.png

                          Any help would be really appreciated!

                          update:
                          I tried the 2.0 alpha, and it worked great! Any ETA on a stable 2.0? :P
                          I will try to capture these updates also, and see how they differ from the current stable pfsense updates...

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.