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

    WAN fails to fetch IP address from router's DHCP server (SOLVED)

    Scheduled Pinned Locked Moved DHCP and DNS
    7 Posts 2 Posters 2.9k Views
    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.
    • B
      Blunder
      last edited by

      As per the title, a new install of RC3 does not pick up an address from the DHCP server running on the ADSL router.

      System is:
      ISP => Router (with DHCP enabled) => pfSense WAN => LAN interface of pfSense running DHCP server  => Switch (which is tied to Local machines).

      Running 2.0-RC3 (i386)
      built on Tue Jun 21 16:50:25 EDT 2011 full install.

      The web admin shows the WAN as up but with an address of 0.0.0.0. instead of the 192.168.178.XXX that it should be.

      The IP address is served up correctly when connected to various Linux machines and an XP box.

      I had RC1 running without problems until upgrading to RC3 via the web interface. It then disconnected itself from the LAN at regular intervals and had to be rebooted.

      I have also re-installed on another machine, so does not appear to be a hardware problem.

      Any ideas. I'm sure it's me that is the problem, not pfsense!

      Update

      Found this

      
Sep 16 17:40:03 	syslogd: kernel boot file is /boot/kernel/kernel
Sep 16 17:40:40 	dhclient: FAIL
Sep 16 17:41:42 	dhclient: FAIL
Sep 16 17:42:44 	dhclient: FAIL
Sep 16 17:43:46 	dhclient: FAIL
Sep 16 17:44:48 	dhclient: FAIL
Sep 16 17:45:50 	dhclient: FAIL
Sep 16 17:46:52 	dhclient: FAIL
Sep 16 17:47:54 	dhclient: FAIL
Sep 16 17:48:56 	dhclient: FAIL
Sep 16 17:49:58 	dhclient: FAIL
Sep 16 17:51:00 	dhclient: FAIL
Sep 16 17:52:02 	dhclient: FAIL
Sep 16 17:53:04 	dhclient: FAIL
Sep 16 17:54:06 	dhclient: FAIL
Sep 16 17:55:08 	dhclient: FAIL
Sep 16 17:56:10 	dhclient: FAIL
Sep 16 17:57:12 	dhclient: FAIL
Sep 16 17:58:14 	dhclient: FAIL
Sep 16 17:59:16 	dhclient: FAIL
Sep 16 18:00:18 	dhclient: FAIL
Sep 16 18:01:20 	dhclient: FAIL

      So performed a packet capture.

      
17:50:38.093637 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:50:50.096531 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:51:01.114447 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:51:03.117426 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:51:07.120378 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:51:11.123344 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:51:17.126289 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:51:25.129217 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:51:35.132127 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:51:43.135061 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:51:57.137932 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:52:03.155878 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:52:05.158859 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:52:07.161842 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:52:09.164826 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:52:11.167800 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:52:15.170770 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:52:20.173726 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:52:26.176670 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:52:38.179564 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:52:51.182451 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:53:05.200324 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:53:06.203316 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:53:07.206303 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:53:08.209301 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:53:09.212286 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:53:11.215273 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:53:14.218244 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:53:19.221202 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:53:32.675083 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:53:47.730951 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:53:56.298874 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:54:04.301815 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:54:07.319775 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:54:08.322760 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:54:10.325749 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:54:15.328704 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:54:28.331588 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
17:54:37.334509 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
      1 Reply Last reply Reply Quote 0
      • W
        wallabybob
        last edited by

        Its possible your packet capture didn't capture something crucial but it rather looks like the DHCP request pfSense sends is not soliciting a response from your router. Does the router have some kind of log which might explain what is going on? Have you got some kind of filter in the router that would stop it assigning an address to pfSense?

        Do you get a better result with a more current 2.0 build?

        What is the FreeBSD name of your pfSense WAN interface? (Could be re0, em0, em3, xl2, … )

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

          I'll try a longer capture.

          There is a log in the router but nothing for the LAN, It may have overflowed. I will try a restart.

          I searched for snapshots of 2.0 but have not found any yet. Do you have a link?

          WAN is fwe0

          Edit. Found snapshots. Will download and try.

          http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_RELENG_2_0/livecd_installer/?C=M;O=D

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

            Nothing in router log

            PFsense log

            
Last 50 system log entries
Sep 16 20:10:54 	kernel: ugen3.1: <via>at usbus3
Sep 16 20:10:54 	kernel: uhub3: <via 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus3
Sep 16 20:10:54 	kernel: ugen4.1: <via>at usbus4
Sep 16 20:10:54 	kernel: uhub4: <via 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4
Sep 16 20:10:54 	kernel: Root mount waiting for: usbus4 usbus3 usbus2 usbus1 usbus0
Sep 16 20:10:54 	kernel: uhub0: 2 ports with 2 removable, self powered
Sep 16 20:10:54 	kernel: uhub1: 2 ports with 2 removable, self powered
Sep 16 20:10:54 	kernel: uhub2: 2 ports with 2 removable, self powered
Sep 16 20:10:54 	kernel: uhub3: 2 ports with 2 removable, self powered
Sep 16 20:10:54 	kernel: Root mount waiting for: usbus4
Sep 16 20:10:54 	kernel: Root mount waiting for: usbus4
Sep 16 20:10:54 	kernel: Root mount waiting for: usbus4
Sep 16 20:10:54 	kernel: uhub4: 8 ports with 8 removable, self powered
Sep 16 20:10:54 	kernel: Trying to mount root from ufs:/dev/ad0s1a
Sep 16 20:10:54 	kernel: ugen1.2: <usb>at usbus1
Sep 16 20:10:54 	kernel: ukbd0: <usb 0="" 2="" usb="" keykoard,="" class="" 0,="" rev="" 1.10="" 1.10,="" addr="">on usbus1
Sep 16 20:10:54 	kernel: kbd2 at ukbd0
Sep 16 20:10:54 	kernel: uhid0: <usb 0="" 2="" usb="" keykoard,="" class="" 0,="" rev="" 1.10="" 1.10,="" addr="">on usbus1
Sep 16 20:10:54 	kernel: pflog0: promiscuous mode enabled
Sep 16 20:10:55 	apinger: Starting Alarm Pinger, apinger(21081)
Sep 16 20:10:55 	apinger: No usable targets found, exiting
Sep 16 20:10:56 	check_reload_status: Linkup starting em0
Sep 16 20:10:56 	kernel: em0: link state changed to UP
Sep 16 20:11:55 	dhclient: FAIL
Sep 16 20:12:13 	php: : OpenNTPD is starting up.
Sep 16 20:12:13 	dhcpd: Internet Systems Consortium DHCP Server 4.2.1-P1
Sep 16 20:12:13 	dhcpd: Copyright 2004-2011 Internet Systems Consortium.
Sep 16 20:12:13 	dhcpd: All rights reserved.
Sep 16 20:12:13 	dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Sep 16 20:12:13 	dnsmasq[35641]: started, version 2.55 cachesize 10000
Sep 16 20:12:13 	dnsmasq[35641]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP
Sep 16 20:12:13 	dnsmasq[35641]: no servers found in /etc/resolv.conf, will retry
Sep 16 20:12:13 	dnsmasq[35641]: no servers found in /etc/resolv.conf, will retry
Sep 16 20:12:13 	dnsmasq[35641]: read /etc/hosts - 2 addresses
Sep 16 20:12:13 	check_reload_status: Updating all dyndns
Sep 16 20:12:16 	check_reload_status: Restarting ipsec tunnels
Sep 16 20:12:18 	php: : Creating rrd update script
Sep 16 20:12:19 	php: : Restarting/Starting all packages.
Sep 16 20:12:20 	php: : IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
Sep 16 20:12:21 	login: login on ttyv0 as root
Sep 16 20:12:21 	sshlockout[8984]: sshlockout/webConfigurator v3.0 starting up
Sep 16 20:12:22 	check_reload_status: Reloading filter
Sep 16 20:12:57 	dhclient: FAIL
Sep 16 20:13:59 	dhclient: FAIL
Sep 16 20:15:01 	dhclient: FAIL
Sep 16 20:16:03 	dhclient: FAIL
Sep 16 20:16:19 	check_reload_status: Linkup starting em1
Sep 16 20:16:19 	kernel: em1: link state changed to UP
Sep 16 20:16:19 	kernel: vr0: link state changed to DOWN
Sep 16 20:16:19 	check_reload_status: Linkup starting vr0</usb></usb></usb></via></via></via></via>

            Packet capture with router reboot.

            20:28:29.273992 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:28:30.276977 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:28:32.279967 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:28:36.282930 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:28:41.285886 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:28:50.288807 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:29:09.291640 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:29:26.294488 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:29:31.312443 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:29:32.315427 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:29:33.318423 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:29:34.321430 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:29:36.324399 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:29:38.327378 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:29:41.330353 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:29:48.333295 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:29:55.336232 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:30:07.339138 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:30:15.342055 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:30:25.344966 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:30:33.362896 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:30:35.365876 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:30:40.368835 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:30:45.371789 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:30:58.374672 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:31:14.377533 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:31:35.395348 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:31:36.398333 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:31:37.401329 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:31:39.404313 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:31:41.407290 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:31:43.410267 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:31:46.413251 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:31:52.432200 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:31:59.437136 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:32:13.541014 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:32:29.557874 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:32:37.575800 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:32:39.578783 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:32:43.581747 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:32:50.584740 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:02.587582 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:13.590484 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:28.593351 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:39.611251 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:40.614242 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:41.617237 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:42.620220 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:43.623218 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:44.626208 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:45.629189 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:47.632176 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:50.635210 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:33:57.638100 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:34:07.641058 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:34:20.643893 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:34:28.646823 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:34:36.649796 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:34:41.667705 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:34:42.670686 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:34:43.673687 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:34:44.676679 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:34:45.679670 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:34:47.682647 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:34:52.685612 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:35:00.688539 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:35:09.691458 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:35:18.694380 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:35:34.697239 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:35:43.715159 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:35:45.718140 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:35:47.721123 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:35:51.724085 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:35:55.727054 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:36:00.730008 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:36:06.732955 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:36:19.735856 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:36:27.738772 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:36:45.756617 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:36:46.759591 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:36:47.762592 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:36:49.765575 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:36:52.768547 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:37:00.771480 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:37:15.774347 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:37:22.777286 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:37:36.780161 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:37:47.798064 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
20:37:49.801046 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
            1 Reply Last reply Reply Quote 0
            • B
              Blunder
              last edited by

              Now running
              2.00-RC3 (i386)
              built on Sun Sep 11 21:07:26 EDT 2011

              Same problem

              Sep 16 20:43:08 	check_reload_status: Syncing firewall
Sep 16 20:43:08 	check_reload_status: Syncing firewall
Sep 16 21:43:41 	dhclient: FAIL
Sep 16 20:43:41 	check_reload_status: Syncing firewall
Sep 16 20:43:41 	check_reload_status: Syncing firewall
Sep 16 20:43:45 	dhclient[9244]: connection closed
Sep 16 20:43:45 	dhclient[9244]: connection closed
Sep 16 20:43:45 	dhclient[9244]: exiting.
Sep 16 20:43:45 	dhclient[9244]: exiting.
Sep 16 21:43:46 	dhclient: PREINIT
Sep 16 21:43:46 	dhclient[40537]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 1
Sep 16 21:43:47 	dhclient[40537]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 1
Sep 16 21:43:48 	dhclient[40537]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 1
Sep 16 21:43:49 	dhclient[40537]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 1
Sep 16 21:43:50 	dhclient[40537]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 2
Sep 16 21:43:52 	dhclient[40537]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 2
Sep 16 21:43:54 	dhclient[40537]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 3
Sep 16 21:43:57 	dhclient[40537]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 3
Sep 16 21:44:00 	dhclient[40537]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 8
Sep 16 21:44:08 	dhclient[40537]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 13
Sep 16 21:44:21 	dhclient[40537]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 15
Sep 16 21:44:36 	dhclient[40537]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 11
Sep 16 21:44:47 	dhclient[40537]: No DHCPOFFERS received.
Sep 16 21:44:47 	dhclient[40537]: No working leases in persistent database - sleeping.
Sep 16 21:44:47 	dhclient: FAIL
Sep 16 21:44:47 	root: rc.update_bogons.sh is starting up.
Sep 16 20:44:47 	check_reload_status: Reloading all
Sep 16 21:44:48 	root: rc.update_bogons.sh is beginning the update cycle.
Sep 16 21:44:48 	root: Could not download http://files.pfsense.org/mirrors/bogon-bn-nonagg.txt
Sep 16 21:44:48 	root: rc.update_bogons.sh is starting up.
Sep 16 21:44:48 	root: rc.update_bogons.sh is sleeping for 44492
Sep 16 21:44:48 	dhclient[61151]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 2
Sep 16 21:44:50 	dhclient[61151]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 3
Sep 16 21:44:53 	php: : rc.reload_all: Reloading all configuration settings.
Sep 16 21:44:53 	dhclient[61151]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 4
Sep 16 21:44:55 	dhcpd: Internet Systems Consortium DHCP Server 4.2.1-P1
Sep 16 21:44:55 	dhcpd: Copyright 2004-2011 Internet Systems Consortium.
Sep 16 21:44:55 	dhcpd: All rights reserved.
Sep 16 21:44:55 	dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Sep 16 21:44:55 	dhclient: PREINIT
Sep 16 21:44:55 	dhclient[17823]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 1
Sep 16 21:44:56 	dhclient[17823]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 2
Sep 16 21:44:57 	dhclient[61151]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 8
Sep 16 21:44:58 	dhclient[17823]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 2
Sep 16 21:45:00 	dhclient[17823]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 3
Sep 16 21:45:03 	dhclient[17823]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 3
Sep 16 21:45:05 	dhclient[61151]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 18
Sep 16 21:45:06 	dhclient[17823]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 3
Sep 16 21:45:09 	dhclient[17823]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 4
Sep 16 21:45:13 	dhclient[17823]: DHCPDISCOVER on fwe0 to 255.255.255.255 port 67 interval 8
              1 Reply Last reply Reply Quote 0
              • W
                wallabybob
                last edited by

                The FreeBSD fwe device is Ethernet over firewire. Are you really using that for your WAN interface? (see dhclient reports in the log you posted.)

                It looks as if your box has interfaces em0, em1 and vr0. Perhaps you meant to use vr0 for WAN.

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

                  Thank you wallabybob, spot on.

                  I had thought interface name was a bit odd, but as it was auto detected by pfsense, I thought little more about it!
                  Silly me. :-[

                  WAN now on vr0, LAN on em0, leaving me em1 & 2 for opt1 & 2.

                  Now that pfsense is up and running again, thanks to your kind help, I can start to struggle with captive portal!

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