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

    WAN link going down

    Problems Installing or Upgrading pfSense Software
    9
    62
    14.4k
    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.
    • Q
      q54e3w
      last edited by

      that didn't fix it, so I rebooted the modem, leaving pfsense up, at least this gets a DHCPACK back now.

      The virgin modem appears to boot in router mode, assigns itself 192.168.100.1 and then transitions at some point shortly after to routing mode and passes through the public IP (something like a 213.81.x.x… or 85.3.x.x...)
      I wonder if this 100.1 assignment is causing some DHCP weirdness as the modem goes through its initialisation and various boot up addresses?

      
Mar  2 10:27:36 pfsense dhclient: ARPSEND\
Mar  2 10:27:38 pfsense dhclient: ARPCHECK\
Mar  2 10:27:38 pfsense dhclient[98982]: DHCPREQUEST on igb4 to 255.255.255.255 port 67\
Mar  2 10:27:39 pfsense dhclient[98982]: DHCPACK from 192.168.100.1\
Mar  2 10:27:39 pfsense dhclient: BOUND\
Mar  2 10:27:39 pfsense dhclient: Starting add_new_address()\
Mar  2 10:27:39 pfsense dhclient: ifconfig igb4 inet 192.168.100.2 netmask 255.255.255.0 broadcast 192.168.100.255\
Mar  2 10:27:39 pfsense dhclient: New IP Address (igb4): 192.168.100.2\
Mar  2 10:27:39 pfsense dhclient: New Subnet Mask (igb4): 255.255.255.0\
Mar  2 10:27:39 pfsense dhclient: New Broadcast Address (igb4): 192.168.100.255\
Mar  2 10:27:39 pfsense dhclient: New Routers (igb4): 192.168.100.1\
Mar  2 10:27:39 pfsense dhclient: Adding new routes to interface: igb4\
Mar  2 10:27:39 pfsense dhclient: /sbin/route add default 192.168.100.1\
Mar  2 10:27:39 pfsense dhclient: Creating resolv.conf\
Mar  2 10:27:39 pfsense dhclient[98982]: bound to 192.168.100.2 -- renewal in 30 seconds.\
Mar  2 10:28:09 pfsense dhclient[40839]: DHCPREQUEST on igb4 to 192.168.100.1 port 67\
Mar  2 10:28:11 pfsense dhclient[40839]: DHCPREQUEST on igb4 to 192.168.100.1 port 67\
Mar  2 10:28:14 pfsense dhclient[40839]: DHCPREQUEST on igb4 to 192.168.100.1 port 67\
Mar  2 10:28:17 pfsense dhclient[40839]: DHCPREQUEST on igb4 to 192.168.100.1 port 67\
Mar  2 10:28:24 pfsense dhclient[40839]: DHCPREQUEST on igb4 to 192.168.100.1 port 67\
Mar  2 10:28:35 pfsense dhcpd: Received signal 15, initiating shutdown.\
Mar  2 10:28:35 pfsense dhcpd: Disabling output on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling input on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling output on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling input on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling output on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling input on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling output on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling input on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling output on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling input on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling output on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling input on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:28:36 pfsense dhclient[40839]: DHCPREQUEST on igb4 to 255.255.255.255 port 67\
Mar  2 10:28:36 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:28:36 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:28:36 pfsense dhcpd: All rights reserved.\
Mar  2 10:28:36 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:28:36 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:28:36 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:28:36 pfsense dhcpd: All rights reserved.\
Mar  2 10:28:36 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:28:36 pfsense dhcpd: Wrote 0 deleted host decls to leases file.\
Mar  2 10:28:36 pfsense dhcpd: Wrote 0 new dynamic host decls to leases file.\
Mar  2 10:28:36 pfsense dhcpd: Wrote 45 leases to leases file.\
Mar  2 10:28:36 pfsense dhcpd: Listening on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:28:36 pfsense dhcpd: Listening on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:28:36 pfsense dhcpd: Listening on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:28:36 pfsense dhcpd: Listening on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:28:36 pfsense dhcpd: Listening on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:28:36 pfsense dhcpd: Listening on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   Socket/fallback/fallback-net\
Mar  2 10:28:36 pfsense dhclient[1281]: connection closed\
Mar  2 10:28:36 pfsense dhclient[1281]: exiting.\
Mar  2 10:28:42 pfsense dhclient: PREINIT\
Mar  2 10:28:42 pfsense dhclient[80861]: DHCPREQUEST on igb4 to 255.255.255.255 port 67\
Mar  2 10:28:43 pfsense dhclient: EXPIRE\
Mar  2 10:28:43 pfsense dhclient: Deleting old routes\
Mar  2 10:28:43 pfsense dhclient: PREINIT\
Mar  2 10:28:43 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 1\
Mar  2 10:28:44 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 1\
Mar  2 10:28:45 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 2\
Mar  2 10:28:47 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 4\
Mar  2 10:28:51 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 8\
Mar  2 10:28:59 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 17\
Mar  2 10:29:16 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 16}

      again still no joy, so I disconnected the coastal line, waited a few minutes and reconnected….

      1 Reply Last reply Reply Quote 0
      • Q
        q54e3w
        last edited by

        again still no joy, so I disconnected the coaxial line which I understand can reset things at virgins end due to the MAC address reset. I waited a few minutes and reconnected the coax and captured this.
        Would be good to have somebody confirm but it looks to me like the vrigin modem negotiates a DHCP lease from the virgin media GW.

        [2.2-RELEASE][admin@pfsense.irj972.local.lan]/root: tcpdump -i igb4\
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode\
listening on igb4, link-type EN10MB (Ethernet), capture size 65535 bytes\
10:38:13.658310 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:15.047877 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:38:15.086648 IP 10.27.136.1.bootps > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.bootpc: BOOTP/DHCP, Reply, length 316\
10:38:15.176944 ARP, Request who-has cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net tell cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net, length 28\
10:38:15.594105 ARP, Request who-has cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net tell cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net, length 28\
10:38:15.600021 ARP, Reply cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:38:15.600036 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:15.608152 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:15.622611 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:15.637099 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:15.638239 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 117\
10:38:15.638511 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:15.638660 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:15.661244 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 117\
10:38:15.673595 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:15.673712 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:15.674048 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:15.674328 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:15.710833 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:15.711183 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 533\
10:38:15.745467 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 117\
10:38:15.745911 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:15.759017 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:15.759238 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:15.759287 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:15.790297 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:15.818350 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:15.818782 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:15.857357 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 245\
10:38:15.857697 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:15.858050 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 165\
10:38:15.899339 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:15.951189 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net > cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net: ICMP echo request, id 130, seq 256, length 60\
10:38:15.957000 IP cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net: ICMP echo reply, id 130, seq 256, length 60\
10:38:16.002543 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:16.003158 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:16.041375 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 117\
10:38:16.041743 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:16.051124 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 133\
10:38:16.065174 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 133\
10:38:16.093319 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 245\
10:38:16.131283 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:16.141407 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:16.141935 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:16.179642 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 117\
10:38:16.180115 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:16.243918 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.61583 > k.root-servers.net.domain: 57511% [1au] NS? . (28)\
10:38:16.255615 IP k.root-servers.net.domain > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.61583: 57511*- 14/0/25 NS a.root-servers.net., NS b.root-servers.net., NS c.root-servers.net., NS d.root-servers.net., NS e.root-servers.net., NS f.root-servers.net., NS g.root-servers.net., NS h.root-servers.net., NS i.root-servers.net., NS j.root-servers.net., NS k.root-servers.net., NS l.root-servers.net., NS m.root-servers.net., RRSIG (913)\
10:38:16.256152 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.50492 > l.root-servers.net.domain: 12578% [1au] DNSKEY? . (28)\
10:38:16.278963 IP l.root-servers.net.domain > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.50492: 12578*- 3/0/1 DNSKEY, DNSKEY, RRSIG (736)\
10:38:16.536884 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:16.577165 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:16.577512 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:16.615412 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 165\
10:38:16.615899 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:16.656012 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.60824 > M.ROOT-SERVERS.NET.domain: 30021% [1au] NS? . (28)\
10:38:16.667146 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 149\
10:38:16.685334 IP M.ROOT-SERVERS.NET.domain > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.60824: 30021*- 14/0/25 NS b.root-servers.net., NS i.root-servers.net., NS l.root-servers.net., NS g.root-servers.net., NS a.root-servers.net., NS f.root-servers.net., NS c.root-servers.net., NS e.root-servers.net., NS k.root-servers.net., NS m.root-servers.net., NS h.root-servers.net., NS d.root-servers.net., NS j.root-servers.net., RRSIG (913)\
10:38:16.685924 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.26257 > M.ROOT-SERVERS.NET.domain: 8122% [1au] DNSKEY? . (28)\
10:38:16.713171 IP M.ROOT-SERVERS.NET.domain > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.26257: 8122*- 3/0/1 DNSKEY, DNSKEY, RRSIG (736)\
10:38:16.729432 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:16.729823 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:16.768085 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 117\
10:38:16.768440 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:17.006453 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net > cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net: ICMP echo request, id 130, seq 512, length 60\
10:38:17.013215 IP cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net: ICMP echo reply, id 130, seq 512, length 60\
10:38:17.053584 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 133\
10:38:17.067222 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 133\
10:38:18.065828 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net > cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net: ICMP echo request, id 130, seq 768, length 60\
10:38:18.065999 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 133\
10:38:18.071851 IP cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net: ICMP echo reply, id 130, seq 768, length 60\
10:38:18.079356 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 133\
10:38:18.427756 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:38:19.121650 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net > cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net: ICMP echo request, id 130, seq 1024, length 60\
10:38:19.121814 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 133\
10:38:19.127987 IP cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net: ICMP echo reply, id 130, seq 1024, length 60\
10:38:19.135479 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 133\
10:38:19.924837 ARP, Request who-has cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net tell cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net, length 28\
10:38:19.930943 ARP, Reply cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:38:19.930958 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:20.122180 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net > cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net: ICMP echo request, id 130, seq 1280, length 60\
10:38:20.122361 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 133\
10:38:20.127772 IP cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net: ICMP echo reply, id 130, seq 1280, length 60\
10:38:20.140226 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 133\
10:38:20.202386 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 197\
10:38:20.202910 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:20.237363 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 325\
10:38:20.479222 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:20.479742 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:20.518208 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 309\
10:38:20.518523 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:20.518705 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:20.519222 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:20.519381 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:20.519653 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:20.550474 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 117\
10:38:20.550962 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:20.551048 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 181\
10:38:20.551876 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 117\
10:38:20.552117 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:20.552188 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 181\
10:38:20.582866 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 181\
10:38:20.583145 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 149\
10:38:20.583818 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 181\
10:38:20.584054 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 181\
10:38:20.598241 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:20.614806 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 165\
10:38:20.615144 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:20.615355 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:20.617676 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 149\
10:38:20.617990 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:20.618234 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:20.651157 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 117\
10:38:20.652043 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 133\
10:38:21.517359 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:38:24.607424 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:38:25.145919 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:38:25.414180 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:38:26.137660 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:38:28.084075 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:28.084266 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:38:28.123458 IP 10.27.136.1.bootps > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.bootpc: BOOTP/DHCP, Reply, length 316\
10:38:28.136368 ARP, Request who-has cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net tell cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net, length 28\
10:38:28.266095 ARP, Request who-has cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net tell cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net, length 28\
10:38:28.272086 ARP, Reply cpc72581-cmbg14-2-0-gw.5-4.cable.virginm.net is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:38:28.272103 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:28.324193 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:28.339882 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 165\
10:38:28.341461 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:28.619894 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 197\
10:38:28.620442 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:28.635640 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 325\
10:38:28.636499 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:28.655552 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:28.666238 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 565\
10:38:28.666875 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:28.682244 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:28.682560 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:28.682601 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 421\
10:38:28.683123 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:28.689463 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 117\
10:38:28.720179 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 101\
10:38:28.720432 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 101\
10:38:28.986263 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 373\
10:38:28.986926 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 117\
10:38:29.001284 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 165\
10:38:29.171210 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081 > 84.39.116.179.http: UDP, length 133\
10:38:29.186619 IP 84.39.116.179.http > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.13081: UDP, length 133\
10:38:29.199276 IP cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.54228 > e.root-servers.net.domain: 58019% [1au] NS? . (28)\
10:38:29.213551 IP e.root-servers.net.domain > cpc72581-cmbg14-2-0-cust19.5-4.cable.virginm.net.54228: 58019*- 14/0/25 NS a.root-servers.net., NS b.root-servers.net., NS c.root-servers.net., NS d.root-servers.net., NS e.root-servers.net., NS f.root-servers.net., NS g.root-servers.net., NS h.root-servers.net., NS i.root-servers.net., NS j.root-servers.net., NS k.root-servers.net., NS l.root-servers.net., NS m.root-servers.net., RRSIG (913)}

        and the dhcp.log, still pfSense struggling to find its feet.

        Mar  2 10:29:56 pfsense dhclient: PREINIT\
Mar  2 10:29:56 pfsense dhclient: EXPIRE\
Mar  2 10:29:56 pfsense dhclient: Deleting old routes\
Mar  2 10:29:56 pfsense dhclient: PREINIT\
Mar  2 10:29:56 pfsense dhclient[60333]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 2\
Mar  2 10:29:56 pfsense dhclient[60333]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 2\
Mar  2 10:29:58 pfsense dhclient[60333]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 4\
Mar  2 10:30:02 pfsense dhclient[60333]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 9\
Mar  2 10:30:11 pfsense dhclient[60333]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 8\
Mar  2 10:30:19 pfsense dhclient[60333]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 11\
Mar  2 10:30:30 pfsense dhclient[60333]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 19\
Mar  2 10:30:49 pfsense dhclient[60333]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 4\
Mar  2 10:30:53 pfsense dhclient[60333]: No DHCPOFFERS received.\
Mar  2 10:30:53 pfsense dhclient[60333]: Trying recorded lease 86.5.163.20\
Mar  2 10:30:53 pfsense dhclient: TIMEOUT\
Mar  2 10:30:53 pfsense dhclient: Starting add_new_address()\
Mar  2 10:30:53 pfsense dhclient: ifconfig igb4 inet 86.5.163.20 netmask 255.255.255.0 broadcast 255.255.255.255\
Mar  2 10:30:53 pfsense dhclient: New IP Address (igb4): 86.5.163.20\
Mar  2 10:30:53 pfsense dhclient: New Subnet Mask (igb4): 255.255.255.0\
Mar  2 10:30:53 pfsense dhclient: New Broadcast Address (igb4): 255.255.255.255\
Mar  2 10:30:53 pfsense dhclient: New Routers (igb4): 86.5.163.1\
Mar  2 10:30:54 pfsense dhclient: New Routers (igb4): 86.5.163.1\
Mar  2 10:30:55 pfsense dhclient: Deleting old routes\
Mar  2 10:30:55 pfsense dhclient[60333]: bound: renewal in 237608 seconds.\
Mar  2 10:30:58 pfsense dhcpd: Received signal 15, initiating shutdown.\
Mar  2 10:30:58 pfsense dhcpd: Disabling output on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:30:58 pfsense dhcpd: Disabling input on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:30:58 pfsense dhcpd: Disabling output on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:30:58 pfsense dhcpd: Disabling input on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:30:58 pfsense dhcpd: Disabling output on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:30:58 pfsense dhcpd: Disabling input on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:30:58 pfsense dhcpd: Disabling output on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:30:58 pfsense dhcpd: Disabling input on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:30:58 pfsense dhcpd: Disabling output on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:30:58 pfsense dhcpd: Disabling input on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:30:58 pfsense dhcpd: Disabling output on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:30:58 pfsense dhcpd: Disabling input on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:30:58 pfsense dhclient[175]: igb4 link state up -> down\
Mar  2 10:30:59 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:30:59 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:30:59 pfsense dhcpd: All rights reserved.\
Mar  2 10:30:59 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:30:59 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:30:59 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:30:59 pfsense dhcpd: All rights reserved.\
Mar  2 10:30:59 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:30:59 pfsense dhcpd: Wrote 0 deleted host decls to leases file.\
Mar  2 10:30:59 pfsense dhcpd: Wrote 0 new dynamic host decls to leases file.\
Mar  2 10:30:59 pfsense dhcpd: Wrote 45 leases to leases file.\
Mar  2 10:30:59 pfsense dhcpd: Listening on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:30:59 pfsense dhcpd: Sending on   BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:30:59 pfsense dhcpd: Listening on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:30:59 pfsense dhcpd: Sending on   BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:30:59 pfsense dhcpd: Listening on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:30:59 pfsense dhcpd: Sending on   BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:30:59 pfsense dhcpd: Listening on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:30:59 pfsense dhcpd: Sending on   BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:30:59 pfsense dhcpd: Listening on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:30:59 pfsense dhcpd: Sending on   BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:30:59 pfsense dhcpd: Listening on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:30:59 pfsense dhcpd: Sending on   BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:30:59 pfsense dhcpd: Sending on   Socket/fallback/fallback-net\
Mar  2 10:30:59 pfsense dhclient[71056]: connection closed\
Mar  2 10:30:59 pfsense dhclient[71056]: exiting.\
Mar  2 10:31:09 pfsense dhcpd: DHCPREQUEST for 192.168.70.103 from 68:96:7b:a4:cf:8e (iPhone7) via igb7\
Mar  2 10:31:09 pfsense dhcpd: DHCPACK on 192.168.70.103 to 68:96:7b:a4:cf:8e (iPhone7) via igb7\
Mar  2 10:31:15 pfsense dhcpd: Received signal 15, initiating shutdown.\
Mar  2 10:31:15 pfsense dhcpd: Disabling output on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:31:15 pfsense dhcpd: Disabling input on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:31:15 pfsense dhcpd: Disabling output on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:31:15 pfsense dhcpd: Disabling input on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:31:15 pfsense dhcpd: Disabling output on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:31:15 pfsense dhcpd: Disabling input on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:31:15 pfsense dhcpd: Disabling output on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:31:15 pfsense dhcpd: Disabling input on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:31:15 pfsense dhcpd: Disabling output on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:31:15 pfsense dhcpd: Disabling input on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:31:15 pfsense dhcpd: Disabling output on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:31:15 pfsense dhcpd: Disabling input on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:31:16 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:31:16 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:31:16 pfsense dhcpd: All rights reserved.\
Mar  2 10:31:16 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:31:16 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:31:16 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:31:16 pfsense dhcpd: All rights reserved.\
Mar  2 10:31:16 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:31:16 pfsense dhcpd: Wrote 0 deleted host decls to leases file.\
Mar  2 10:31:16 pfsense dhcpd: Wrote 0 new dynamic host decls to leases file.\
Mar  2 10:31:16 pfsense dhcpd: Wrote 45 leases to leases file.\
Mar  2 10:31:16 pfsense dhcpd: Listening on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:31:16 pfsense dhcpd: Sending on   BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:31:16 pfsense dhcpd: Listening on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:31:16 pfsense dhcpd: Sending on   BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:31:16 pfsense dhcpd: Listening on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:31:16 pfsense dhcpd: Sending on   BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:31:16 pfsense dhcpd: Listening on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:31:16 pfsense dhcpd: Sending on   BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:31:16 pfsense dhcpd: Listening on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:31:16 pfsense dhcpd: Sending on   BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:31:16 pfsense dhcpd: Listening on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:31:16 pfsense dhcpd: Sending on   BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:31:16 pfsense dhcpd: Sending on   Socket/fallback/fallback-net\
Mar  2 10:31:31 pfsense dhcpd: Received signal 15, initiating shutdown.\
Mar  2 10:31:31 pfsense dhcpd: Disabling output on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:31:31 pfsense dhcpd: Disabling input on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:31:31 pfsense dhcpd: Disabling output on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:31:31 pfsense dhcpd: Disabling input on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:31:31 pfsense dhcpd: Disabling output on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:31:31 pfsense dhcpd: Disabling input on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:31:31 pfsense dhcpd: Disabling output on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:31:31 pfsense dhcpd: Disabling input on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:31:31 pfsense dhcpd: Disabling output on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:31:31 pfsense dhcpd: Disabling input on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:31:31 pfsense dhcpd: Disabling output on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:31:31 pfsense dhcpd: Disabling input on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:31:33 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:31:33 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:31:33 pfsense dhcpd: All rights reserved.\
Mar  2 10:31:33 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:31:33 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:31:33 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:31:33 pfsense dhcpd: All rights reserved.\
Mar  2 10:31:33 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:31:33 pfsense dhcpd: Wrote 0 deleted host decls to leases file.\
Mar  2 10:31:33 pfsense dhcpd: Wrote 0 new dynamic host decls to leases file.\
Mar  2 10:31:33 pfsense dhcpd: Wrote 45 leases to leases file.\
Mar  2 10:31:33 pfsense dhcpd: Listening on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:31:33 pfsense dhcpd: Sending on   BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:31:33 pfsense dhcpd: Listening on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:31:33 pfsense dhcpd: Sending on   BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:31:33 pfsense dhcpd: Listening on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:31:33 pfsense dhcpd: Sending on   BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:31:33 pfsense dhcpd: Listening on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:31:33 pfsense dhcpd: Sending on   BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:31:33 pfsense dhcpd: Listening on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:31:33 pfsense dhcpd: Sending on   BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:31:33 pfsense dhcpd: Listening on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:31:33 pfsense dhcpd: Sending on   BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:31:33 pfsense dhcpd: Sending on   Socket/fallback/fallback-net\
Mar  2 10:31:48 pfsense dhcpd: Received signal 15, initiating shutdown.\
Mar  2 10:31:48 pfsense dhcpd: Disabling output on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:31:48 pfsense dhcpd: Disabling input on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:31:48 pfsense dhcpd: Disabling output on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:31:48 pfsense dhcpd: Disabling input on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:31:48 pfsense dhcpd: Disabling output on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:31:48 pfsense dhcpd: Disabling input on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:31:48 pfsense dhcpd: Disabling output on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:31:48 pfsense dhcpd: Disabling input on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:31:48 pfsense dhcpd: Disabling output on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:31:48 pfsense dhcpd: Disabling input on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:31:48 pfsense dhcpd: Disabling output on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:31:48 pfsense dhcpd: Disabling input on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:31:49 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:31:49 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:31:49 pfsense dhcpd: All rights reserved.\
Mar  2 10:31:49 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:31:49 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:31:49 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:31:49 pfsense dhcpd: All rights reserved.\
Mar  2 10:31:49 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:31:49 pfsense dhcpd: Wrote 0 deleted host decls to leases file.\
Mar  2 10:31:49 pfsense dhcpd: Wrote 0 new dynamic host decls to leases file.\
Mar  2 10:31:49 pfsense dhcpd: Wrote 45 leases to leases file.\
Mar  2 10:31:49 pfsense dhcpd: Listening on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:31:49 pfsense dhcpd: Sending on   BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:31:49 pfsense dhcpd: Listening on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:31:49 pfsense dhcpd: Sending on   BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:31:49 pfsense dhcpd: Listening on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:31:49 pfsense dhcpd: Sending on   BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:31:49 pfsense dhcpd: Listening on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:31:49 pfsense dhcpd: Sending on   BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:31:49 pfsense dhcpd: Listening on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:31:49 pfsense dhcpd: Sending on   BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:31:49 pfsense dhcpd: Listening on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:31:49 pfsense dhcpd: Sending on   BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:31:49 pfsense dhcpd: Sending on   Socket/fallback/fallback-net\
Mar  2 10:31:49 pfsense dhclient[47596]: dhclient already running, pid: 47434.\
Mar  2 10:31:49 pfsense dhclient[47596]: exiting.\
Mar  2 10:32:04 pfsense dhcpd: Received signal 15, initiating shutdown.\
Mar  2 10:32:04 pfsense dhcpd: Disabling output on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:32:04 pfsense dhcpd: Disabling input on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:32:04 pfsense dhcpd: Disabling output on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:32:04 pfsense dhcpd: Disabling input on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:32:04 pfsense dhcpd: Disabling output on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:32:04 pfsense dhcpd: Disabling input on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:32:04 pfsense dhcpd: Disabling output on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:32:04 pfsense dhcpd: Disabling input on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:32:04 pfsense dhcpd: Disabling output on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:32:04 pfsense dhcpd: Disabling input on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:32:04 pfsense dhcpd: Disabling output on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:32:04 pfsense dhcpd: Disabling input on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:32:05 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:32:05 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:32:05 pfsense dhcpd: All rights reserved.\
Mar  2 10:32:05 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:32:05 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:32:05 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:32:05 pfsense dhcpd: All rights reserved.\
Mar  2 10:32:05 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:32:05 pfsense dhcpd: Wrote 0 deleted host decls to leases file.\
Mar  2 10:32:05 pfsense dhcpd: Wrote 0 new dynamic host decls to leases file.\
Mar  2 10:32:05 pfsense dhcpd: Wrote 45 leases to leases file.\
Mar  2 10:32:05 pfsense dhcpd: Listening on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:32:05 pfsense dhcpd: Sending on   BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:32:05 pfsense dhcpd: Listening on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:32:05 pfsense dhcpd: Sending on   BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:32:05 pfsense dhcpd: Listening on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:32:05 pfsense dhcpd: Sending on   BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:32:05 pfsense dhcpd: Listening on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:32:05 pfsense dhcpd: Sending on   BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:32:05 pfsense dhcpd: Listening on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:32:05 pfsense dhcpd: Sending on   BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:32:05 pfsense dhcpd: Listening on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:32:05 pfsense dhcpd: Sending on   BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:32:05 pfsense dhcpd: Sending on   Socket/fallback/fallback-net\
Mar  2 10:33:03 pfsense dhcpd: DHCPREQUEST for 192.168.50.104 from 8c:70:5a:68:8f:6c (t420) via igb5\
Mar  2 10:33:03 pfsense dhcpd: DHCPACK on 192.168.50.104 to 8c:70:5a:68:8f:6c (t420) via igb5\

        and a packet capture of the WAN interface which showed it seemed to be progressing at this point although still not active.
        The ping to 10.40.0.1 is a getaway ping to a VPN DNS server

        
10:50:02.460055 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.37612 > 199.7.83.42.domain: 58016% [1au] DNSKEY? . (28)\
10:50:02.483860 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 778: 199.7.83.42.domain > 86.5.163.20.37612: 58016*- 3/0/1 DNSKEY, DNSKEY, RRSIG (736)\
10:50:02.808637 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 83: 86.5.163.20.4709 > 10.6.0.1.domain: 53865+ PTR? 4.0.41.198.in-addr.arpa. (41)\
10:50:03.345093 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 49410, length 60\
10:50:04.365906 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 49666, length 60\
10:50:05.427545 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 49922, length 60\
10:50:05.491557 0c:c4:7a:07:d3:4c (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:50:06.455536 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:50:06.474062 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype ARP (0x0806), length 60: Reply 86.5.163.1 is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:50:06.474076 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 50178, length 60\
10:50:08.581018 0c:c4:7a:07:d3:4c (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:50:11.194770 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:50:11.643708 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:50:12.570778 0c:c4:7a:07:d3:4c (oui Unknown) > 33:33:00:01:00:02 (oui Unknown), ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 inf-req\
10:50:13.018553 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:50:15.334642 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:50:15.371990 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 358: 10.27.136.1.bootps > 86.5.163.20.bootpc: BOOTP/DHCP, Reply, length 316\
10:50:15.384957 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:50:15.780096 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:50:15.787368 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype ARP (0x0806), length 60: Reply 86.5.163.1 is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:50:15.787379 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 52482, length 60\
10:50:16.515551 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.64443 > 192.36.148.17.domain: 46729% [1au] NS? . (28)\
10:50:16.540247 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 955: 192.36.148.17.domain > 86.5.163.20.64443: 46729*- 14/0/25 NS h.root-servers.net., NS e.root-servers.net., NS m.root-servers.net., NS g.root-servers.net., NS d.root-servers.net., NS f.root-servers.net., NS k.root-servers.net., NS c.root-servers.net., NS i.root-servers.net., NS b.root-servers.net., NS a.root-servers.net., NS l.root-servers.net., NS j.root-servers.net., RRSIG (913)}
        1 Reply Last reply Reply Quote 0
        • Q
          q54e3w
          last edited by

          I'm not sure if this relates but it happened at about the time the WAN came back to life. webgui access was slow so I had opened a new SSH to pfSense and restarted php and webgui (options 16 & 11). I was packet capturing igb4 when it came back up, perhaps the answer lies in here somewhere????

          [2.2-RELEASE][admin@pfsense.irj972.local.lan]/root: tcpdump -i igb4 -e\
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode\
listening on igb4, link-type EN10MB (Ethernet), capture size 65535 bytes\
10:54:06.082443 0c:c4:7a:07:d3:4c (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:54:08.334709 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:54:08.382180 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 358: 10.27.136.1.bootps > 86.5.163.20.bootpc: BOOTP/DHCP, Reply, length 316\
10:54:10.414556 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:54:10.431928 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 358: 10.27.136.1.bootps > 86.5.163.20.bootpc: BOOTP/DHCP, Reply, length 316\
10:54:10.445186 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:54:10.526505 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:54:10.533724 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype ARP (0x0806), length 60: Reply 86.5.163.1 is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:54:10.533755 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.60949 > 199.7.83.42.domain: 1572% [1au] NS? . (28)\
10:54:10.556539 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 955: 199.7.83.42.domain > 86.5.163.20.60949: 1572*- 14/0/25 NS a.root-servers.net., NS b.root-servers.net., NS c.root-servers.net., NS d.root-servers.net., NS e.root-servers.net., NS f.root-servers.net., NS g.root-servers.net., NS h.root-servers.net., NS i.root-servers.net., NS j.root-servers.net., NS k.root-servers.net., NS l.root-servers.net., NS m.root-servers.net., RRSIG (913)\
10:54:10.958970 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 83: 86.5.163.20.27346 > 10.6.0.1.domain: 3982+ PTR? 1.163.5.86.in-addr.arpa. (41)\
10:54:11.471532 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 45315, length 60\
10:54:11.573864 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.53673 > 128.63.2.53.domain: 16340% [1au] NS? . (28)\
10:54:11.670936 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 955: 128.63.2.53.domain > 86.5.163.20.53673: 16340*- 14/0/25 NS a.root-servers.net., NS b.root-servers.net., NS c.root-servers.net., NS d.root-servers.net., NS e.root-servers.net., NS f.root-servers.net., NS g.root-servers.net., NS h.root-servers.net., NS i.root-servers.net., NS j.root-servers.net., NS k.root-servers.net., NS l.root-servers.net., NS m.root-servers.net., RRSIG (913)\
10:54:11.671566 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.52571 > 128.63.2.53.domain: 57284% [1au] DNSKEY? . (28)\
10:54:11.766351 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 778: 128.63.2.53.domain > 86.5.163.20.52571: 57284*- 3/0/1 DNSKEY, DNSKEY, RRSIG (736)\
10:54:12.471524 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 45571, length 60\
10:54:13.532080 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 45827, length 60\
10:54:14.571331 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 46083, length 60\
10:54:15.593151 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:54:15.600351 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype ARP (0x0806), length 60: Reply 86.5.163.1 is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:54:15.600366 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 46339, length 60\
10:54:16.037663 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 83: 86.5.163.20.11119 > 208.67.222.222.domain: 3982+ PTR? 1.163.5.86.in-addr.arpa. (41)\
10:54:20.598352 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:54:20.730431 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:54:21.787229 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:54:23.893674 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:54:23.933139 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 358: 10.27.136.1.bootps > 86.5.163.20.bootpc: BOOTP/DHCP, Reply, length 316\
10:54:23.946232 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:54:24.894081 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:54:24.899870 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype ARP (0x0806), length 60: Reply 86.5.163.1 is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:54:24.899886 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 48643, length 60\
10:54:25.075941 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.7830 > 199.7.91.13.domain: 5900% [1au] NS? . (28)\
10:54:25.104182 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 955: 199.7.91.13.domain > 86.5.163.20.7830: 5900*- 14/0/25 NS j.root-servers.net., NS a.root-servers.net., NS l.root-servers.net., NS b.root-servers.net., NS c.root-servers.net., NS i.root-servers.net., NS e.root-servers.net., NS g.root-servers.net., NS d.root-servers.net., NS k.root-servers.net., NS h.root-servers.net., NS m.root-servers.net., NS f.root-servers.net., RRSIG (913)\
10:54:25.104697 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.14951 > 193.0.14.129.domain: 12171% [1au] DNSKEY? . (28)\
10:54:25.119198 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 778: 193.0.14.129.domain > 86.5.163.20.14951: 12171*- 3/0/1 DNSKEY, DNSKEY, RRSIG (736)\
10:54:25.354855 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 84: 86.5.163.20.8647 > 10.6.0.1.domain: 64149+ PTR? 13.91.7.199.in-addr.arpa. (42)\
10:54:25.895069 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 48899, length 60\
10:54:26.896673 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 49155, length 60\
10:54:27.897081 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 49411, length 60\
10:54:28.898080 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:54:28.904480 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype ARP (0x0806), length 60: Reply 86.5.163.1 is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:54:28.904489 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 49667, length 60\
10:54:29.232433 0c:c4:7a:07:d3:4c (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:54:32.322647 0c:c4:7a:07:d3:4c (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:54:34.087494 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:54:35.093240 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:54:35.412984 0c:c4:7a:07:d3:4c (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:54:37.147264 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:54:37.186480 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 358: 10.27.136.1.bootps > 86.5.163.20.bootpc: BOOTP/DHCP, Reply, length 316\
10:54:37.200013 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:54:38.209533 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:54:38.215685 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype ARP (0x0806), length 60: Reply 86.5.163.1 is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:54:38.215702 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 51971, length 60\
10:54:38.305335 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.16065 > 192.33.4.12.domain: 48610% [1au] NS? . (28)\
10:54:38.325506 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 955: 192.33.4.12.domain > 86.5.163.20.16065: 48610*- 14/0/25 NS m.root-servers.net., NS a.root-servers.net., NS e.root-servers.net., NS f.root-servers.net., NS h.root-servers.net., NS l.root-servers.net., NS c.root-servers.net., NS j.root-servers.net., NS g.root-servers.net., NS b.root-servers.net., NS i.root-servers.net., NS k.root-servers.net., NS d.root-servers.net., RRSIG (913)\
10:54:38.325974 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.14029 > 128.63.2.53.domain: 49826% [1au] DNSKEY? . (28)\
10:54:38.419966 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 778: 128.63.2.53.domain > 86.5.163.20.14029: 49826*- 3/0/1 DNSKEY, DNSKEY, RRSIG (736)\
10:54:38.618358 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 84: 86.5.163.20.26250 > 10.6.0.1.domain: 43443+ PTR? 12.4.33.192.in-addr.arpa. (42)\
10:54:39.271518 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 52227, length 60\
10:54:40.296688 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 52483, length 60\
10:54:41.331078 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 52739, length 60\
10:54:42.345078 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:54:42.352900 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype ARP (0x0806), length 60: Reply 86.5.163.1 is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:54:42.352909 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 52995, length 60\
10:54:47.209071 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:54:47.508734 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:54:51.682477 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:54:51.724021 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 358: 10.27.136.1.bootps > 86.5.163.20.bootpc: BOOTP/DHCP, Reply, length 316\
10:54:51.737032 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:54:52.773536 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:54:52.780237 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype ARP (0x0806), length 60: Reply 86.5.163.1 is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:54:52.780255 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 55555, length 60\
10:54:52.866051 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.40876 > 128.63.2.53.domain: 42576% [1au] NS? . (28)\
10:54:52.959730 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 955: 128.63.2.53.domain > 86.5.163.20.40876: 42576*- 14/0/25 NS a.root-servers.net., NS b.root-servers.net., NS c.root-servers.net., NS d.root-servers.net., NS e.root-servers.net., NS f.root-servers.net., NS g.root-servers.net., NS h.root-servers.net., NS i.root-servers.net., NS j.root-servers.net., NS k.root-servers.net., NS l.root-servers.net., NS m.root-servers.net., RRSIG (913)\
10:54:52.960371 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.52067 > 192.5.5.241.domain: 24293% [1au] DNSKEY? . (28)\
10:54:52.979001 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 778: 192.5.5.241.domain > 86.5.163.20.52067: 24293*- 3/0/1 DNSKEY, DNSKEY, RRSIG (736)\
10:54:53.126863 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 84: 86.5.163.20.63969 > 10.6.0.1.domain: 20882+ PTR? 241.5.5.192.in-addr.arpa. (42)\
10:54:53.835519 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 55811, length 60\
10:54:54.897520 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 56067, length 60\
10:54:54.972477 0c:c4:7a:07:d3:4c (oui Unknown) > 33:33:00:01:00:02 (oui Unknown), ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 inf-req\
10:54:55.908083 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 56323, length 60\
10:54:56.909075 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:54:56.916953 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype ARP (0x0806), length 60: Reply 86.5.163.1 is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:54:56.916962 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 56579, length 60\
10:55:01.652612 0c:c4:7a:07:d3:4c (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:55:01.840345 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:55:01.948237 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:55:04.742625 0c:c4:7a:07:d3:4c (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:55:05.984245 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 86.5.163.20.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:22:68:1f:74:81 (oui Unknown), length 300\
10:55:06.022854 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 358: 10.27.136.1.bootps > 86.5.163.20.bootpc: BOOTP/DHCP, Reply, length 316\
10:55:06.036054 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:55:06.984083 00:22:68:1f:74:81 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:55:06.990445 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype ARP (0x0806), length 60: Reply 86.5.163.1 is-at 00:21:55:cb:93:da (oui Unknown), length 46\
10:55:06.990457 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 59139, length 60\
10:55:07.102458 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.58188 > 199.7.83.42.domain: 7978% [1au] NS? . (28)\
10:55:07.125399 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 955: 199.7.83.42.domain > 86.5.163.20.58188: 7978*- 14/0/25 NS a.root-servers.net., NS b.root-servers.net., NS c.root-servers.net., NS d.root-servers.net., NS e.root-servers.net., NS f.root-servers.net., NS g.root-servers.net., NS h.root-servers.net., NS i.root-servers.net., NS j.root-servers.net., NS k.root-servers.net., NS l.root-servers.net., NS m.root-servers.net., RRSIG (913)\
10:55:07.125964 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.24946 > 199.7.83.42.domain: 49091% [1au] DNSKEY? . (28)\
10:55:07.148634 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 778: 199.7.83.42.domain > 86.5.163.20.24946: 49091*- 3/0/1 DNSKEY, DNSKEY, RRSIG (736)\
10:55:07.984076 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 59395, length 60\
10:55:08.984082 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 59651, length 60\
10:55:09.984414 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 59907, length 60\
10:55:11.022775 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 60163, length 60\
10:55:12.084530 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 60419, length 60\
10:55:13.145076 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 60675, length 60\
10:55:14.207515 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 60931, length 60\
10:55:15.226327 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 61187, length 60\
10:55:16.230240 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 61443, length 60\
10:55:17.292500 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 61699, length 60\
10:55:18.293059 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 61955, length 60\
10:55:19.293496 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 62211, length 60\
10:55:20.295718 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 62467, length 60\
10:55:21.351634 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 62723, length 60\
10:55:22.413512 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 62979, length 60\
10:55:23.475509 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 63235, length 60\
10:55:24.537513 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 63491, length 60\
10:55:25.544002 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 63747, length 60\
10:55:26.106484 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 70: 86.5.163.20.16425 > a.root-servers.net.domain: 23585% [1au] NS? . (28)\
10:55:26.137378 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 955: a.root-servers.net.domain > 86.5.163.20.16425: 23585*- 14/0/25 NS a.root-servers.net., NS b.root-servers.net., NS c.root-servers.net., NS d.root-servers.net., NS e.root-servers.net., NS f.root-servers.net., NS g.root-servers.net., NS h.root-servers.net., NS i.root-servers.net., NS j.root-servers.net., NS k.root-servers.net., NS l.root-servers.net., NS m.root-servers.net., RRSIG (913)\
10:55:26.412333 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 83: 86.5.163.20.42748 > 10.6.0.1.domain: 65077+ PTR? 4.0.41.198.in-addr.arpa. (41)\
10:55:26.606516 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 64003, length 60\
10:55:27.668507 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 64259, length 60\
10:55:27.892905 0c:c4:7a:07:d3:4c (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:55:28.709068 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 64515, length 60\
10:55:29.711533 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 64771, length 60\
10:55:30.713178 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 65027, length 60\
10:55:30.982770 0c:c4:7a:07:d3:4c (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:55:31.475156 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 83: 86.5.163.20.44796 > 208.67.222.222.domain: 65077+ PTR? 4.0.41.198.in-addr.arpa. (41)\
10:55:31.495504 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 115: 208.67.222.222.domain > 86.5.163.20.44796: 65077 1/0/0 PTR a.root-servers.net. (73)\
10:55:31.713176 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 65283, length 60\
10:55:32.775509 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 4, length 60\
10:55:33.837509 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 260, length 60\
10:55:34.072969 0c:c4:7a:07:d3:4c (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c (oui Unknown), length 548\
10:55:34.899509 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 516, length 60\
10:55:35.922444 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 772, length 60\
10:55:36.922440 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 1028, length 60\
10:55:37.960272 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 1284, length 60\
10:55:39.010335 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 1540, length 60\
10:55:40.072519 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 1796, length 60\
10:55:40.936545 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 82: 86.5.163.20.56601 > 10.6.0.1.domain: 10077+ A? 0.pfsense.pool.ntp.org. (40)\
10:55:41.105518 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 2052, length 60\
10:55:42.167500 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 2308, length 60\
10:55:43.229516 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 2564, length 60\
10:55:44.230233 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 2820, length 60\
10:55:45.250323 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 3076, length 60\
10:55:46.036645 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 82: 86.5.163.20.39144 > 208.67.222.222.domain: 10077+ A? 0.pfsense.pool.ntp.org. (40)\
10:55:46.074178 00:21:55:cb:93:da (oui Unknown) > 00:22:68:1f:74:81 (oui Unknown), ethertype IPv4 (0x0800), length 146: 208.67.222.222.domain > 86.5.163.20.39144: 10077 4/0/0 A 5.83.190.253, A 213.199.225.30, A 77.66.33.146, A 87.106.176.225 (104)\
10:55:46.074309 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 82: 86.5.163.20.44752 > 10.6.0.1.domain: 55072+ AAAA? 0.pfsense.pool.ntp.org. (40)\
10:55:46.293444 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 3332, length 60\
10:55:47.355518 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 3588, length 60\
10:55:48.417516 00:22:68:1f:74:81 (oui Unknown) > 00:21:55:cb:93:da (oui Unknown), ethertype IPv4 (0x0800), length 94: 86.5.163.20 > 10.4.0.1: ICMP echo request, id 130, seq 3844, length 60\
^C\
151 packets captured\
151 packets received by filter\
0 packets dropped by kernel\
[2.2-RELEASE][admin@pfsense.irj972.local.lan]/root:}
          1 Reply Last reply Reply Quote 0
          • X
            xtofh
            last edited by

            Hi, update from this side of the water  ;D

            Today (after 3 days without a problem) it occured again.

            netstat-nr output attached, as well as the sysctl dev.em.1. I didn't reboot yet, but I switched to a different fw with 2.1.5. (still have the 2.2 around but can't continue losing connection at random times) Other logs are still available, I have not rebooted the 2.2 firewall yet.

            I also think it has something to do with the dhcp discovery not working correct. (or different from 2.1.5)

            My setup is also: cable modem <-> pfsense. (but in Belgium, provider: Telenet)

            Any advice as to what a logical next step would be?

            netstat-nr.txt
            sysctl-dev-em1.txt

            1 Reply Last reply Reply Quote 0
            • Q
              q54e3w
              last edited by

              Good point, thanks for reminding me. During my most recent issue I tried plugging my modem into a working and previously in service 2.1.5 box on identical hardware (supermicro a1srm-2758f) which also failed to obtain a WAN IP address. I didn't test this as extensively as my 2.2 as time was pushing on by then.

              1 Reply Last reply Reply Quote 0
              • X
                xtofh
                last edited by

                @irj972:

                Good point, thanks for reminding me. During my most recent issue I tried plugging my modem into a working and previously in service 2.1.5 box on identical hardware (supermicro a1srm-2758f) which also failed to obtain a WAN IP address. I didn't test this as extensively as my 2.2 as time was pushing on by then.

                Hm, strange. On my end, as soon as I switch my WAN cable to the 2.1.5 box, that 2.1.5 box gets an IP immediately.

                1 Reply Last reply Reply Quote 0
                • Q
                  q54e3w
                  last edited by

                  Next time it drops I'll try again to verify, possibly my fiddling influenced something?
                  If I purchase gold, would this get further attention? I need this system reliable for some upcoming work where I'll need to be able to vpn back in to my home office.

                  1 Reply Last reply Reply Quote 0
                  • X
                    xtofh
                    last edited by

                    I checked the 2.2 now, after leaving it unplugged from WAN for a night. Plugged in the WAN but it still didn't get an IP.

                    The only thing I see is dhcp requests, the 2.1.5 on that same network (we get multiple IPs from the isp via dhcp) works without a problem.

                    On the 2.2 this was the tcpdump on the WAN interface:

                    08:36:46.129955 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0d:88:cc:fa:2e, length 300
08:36:48.519874 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0d:88:cc:fa:2e, length 300
08:36:52.380571 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0d:88:cc:fa:2e, length 300
...

                    After a reboot, it got an IP just fine.. I'm seeing the same behavior on another firewall, remote this one, so we're holding off updating to 2.2 for now.  :-\

                    Kristof.

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      Packet capture on a mirror port upstream of WAN.  Identify the difference between the DHCP requests before and after reboot.  Submit findings as a bug report.

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

                      1 Reply Last reply Reply Quote 0
                      • X
                        xtofh
                        last edited by

                        Is packet capture on the firewall itself ok also? (I don't have a very intelligent switch on that end)

                        Kristof

                        1 Reply Last reply Reply Quote 0
                        • DerelictD
                          Derelict LAYER 8 Netgate
                          last edited by

                          I would say, considering what you're asserting, no.  Capturing on the interface is not okay.

                          Just because a packet capture on WAN captures something doesn't mean it was actually sent on the wire.

                          Eliminate all doubt and capture on the switch.  Then you KNOW.

                          Chattanooga, Tennessee, USA
                          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                          Do Not Chat For Help! NO_WAN_EGRESS(TM)

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            Though capturing on the WAN interface and comparing with 2.1.5 will tell you something. If they're identical then try and capture upstream to see if they're different at that point. That tells you where the change is occurring.

                            Steve

                            1 Reply Last reply Reply Quote 0
                            • Q
                              q54e3w
                              last edited by

                              so following my latest WAN drop, I did a bit more investigating. I believe I have found a way to force the WAN dropping issue. I don't have a switch to capture on unfortunately, my system is simple , i.e broadband modem -> pfsense 2.2.

                              this is what Ive discovered,

                              If I power my modem up, let it sync with the Virgin media network and then connect my pfsense WAN interface I get a DHCP address immediately. I can then unplug either coaxial or cat5 WAN cables and pfsense still gets DHCP immediately.

                              If I connect my WAN interface before I power up my modem, when it syncs I do not get a DHCP address but see the repeating pattern of DHCP hunting.I believe something like my broadband line dropping or virgin lease expiration forces this type of reset and hence pfSense does not see a DHCP address.

                              I'd like to do a packet capture of my WAN interface in both modes, one showing immediate DHCP allocation and one showing the looping error so somebody with greater knowledge could review and and raise a bug if its appropriate.
                              Is there a preferred format or command line to capture WAN interface data, I'd like to ensure I get everything thats needed.

                              1 Reply Last reply Reply Quote 0
                              • X
                                xtofh
                                last edited by

                                I was away for a while but upon returning have updated our 2.2 to 2.2.1-RELEASE.

                                This was 4 days ago and since then we've not seen any issues. (doesn't mean anything yet, but I'm hopeful) I've got tcpdump running to make sure I catch anything weird if it occurs. To be sure it's okay I think I need to give it 3-4 weeks.

                                @irj972, I'm not sure what the requested tcpdump parameters are but I use these:```
                                tcpdump -i em1 -nnvvXSs 1514

                                1 Reply Last reply Reply Quote 0
                                • T
                                  TieT
                                  last edited by

                                  I recently did a new full install (after /etc/ got corrupted due to bad power off) and I haven't had the WAN link loss issue.

                                  But as irj972 stated, when pfsense is booted before the modem is booted it fails to get a IP addresss, i've also noticed this.

                                  1 Reply Last reply Reply Quote 0
                                  • X
                                    xtofh
                                    last edited by

                                    @TieT:

                                    I recently did a new full install (after /etc/ got corrupted due to bad power off) and I haven't had the WAN link loss issue.

                                    Thanks for the update. And are you now running 2.2.1 or still 2.2 ?

                                    1 Reply Last reply Reply Quote 0
                                    • T
                                      TieT
                                      last edited by

                                      @xtofh:

                                      @TieT:

                                      I recently did a new full install (after /etc/ got corrupted due to bad power off) and I haven't had the WAN link loss issue.

                                      Thanks for the update. And are you now running 2.2.1 or still 2.2 ?

                                      2.2.1-RELEASE (i386)
                                      built on Fri Mar 13 08:16:53 CDT 2015
                                      FreeBSD 10.1-RELEASE-p6

                                      You're welcome  ;)

                                      1 Reply Last reply Reply Quote 0
                                      • X
                                        xtofh
                                        last edited by

                                        I keep losing my ip on the WAN interface. (connected to switch, and that connects to the cable modem of business TELENET in Belgium)

                                        As soon as this happens I get these (repeating) requests on the WAN interface of the DHCP interface:

                                        16:39:41.829043 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 00:0d:88:cc:XX:XX, length 300, xid 0x304889c7, Flags [none] (0x0000)
  Client-Ethernet-Address 00:0d:88:cc:XX:XX
  Vendor-rfc1048 Extensions
    Magic Cookie 0x63825363
    DHCP-Message Option 53, length 1: Discover
    Requested-IP Option 50, length 4: 81.82.XX.YY
    Client-ID Option 61, length 7: ether 00:0d:88:cc:XX:XX
    Hostname Option 12, length 7: "pfsense"
    Parameter-Request Option 55, length 9:
      Subnet-Mask, BR, Time-Zone, Classless-Static-Route
      Default-Gateway, Domain-Name, Domain-Name-Server, Hostname
      Option 119
0x0000:  4510 0148 0000 0000 8011 3996 0000 0000  E..H......9.....
0x0010:  ffff ffff 0044 0043 0134 4260 0101 0600  .....D.C.4B`....
0x0020:  3048 89c7 0000 0000 0000 0000 0000 0000  0H..............
0x0030:  0000 0000 0000 0000 000d 88cc fa2f 0000  ............./..
0x0040:  0000 0000 0000 0000 0000 0000 0000 0000  ................
0x0050:  0000 0000 0000 0000 0000 0000 0000 0000  ................
0x0060:  0000 0000 0000 0000 0000 0000 0000 0000  ................
0x0070:  0000 0000 0000 0000 0000 0000 0000 0000  ................
0x0080:  0000 0000 0000 0000 0000 0000 0000 0000  ................
0x0090:  0000 0000 0000 0000 0000 0000 0000 0000  ................
0x00a0:  0000 0000 0000 0000 0000 0000 0000 0000  ................
0x00b0:  0000 0000 0000 0000 0000 0000 0000 0000  ................
0x00c0:  0000 0000 0000 0000 0000 0000 0000 0000  ................
0x00d0:  0000 0000 0000 0000 0000 0000 0000 0000  ................
0x00e0:  0000 0000 0000 0000 0000 0000 0000 0000  ................
0x00f0:  0000 0000 0000 0000 0000 0000 0000 0000  ................
0x0100:  0000 0000 0000 0000 6382 5363 3501 0132  ........c.Sc5..2
0x0110:  0451 52d1 2c3d 0701 000d 88cc fa2f 0c07  .QR.,=......./..
0x0120:  7066 7365 6e73 6537 0901 1c02 7903 0f06  pfsense7....y...
0x0130:  0c77 ff00 0000 0000 0000 0000 0000 0000  .w..............
0x0140:  0000 0000 0000 0000                      ........

                                        But no reply from upstream. However, this literally never happens with 2.1.5. The firewall with 2.2.1 (before 2.2) was a fresh install.

                                        I have now re-enabled IPv6 (but not actively using it) on our pfsense WAN interface, our provider also hands out IPv6 addresses. I don't expect this to change anything but still.

                                        Any suggestions on how to get the right stuff to the developers so there might be a fix for this?

                                        Regards,
                                        Kristof.

                                        1 Reply Last reply Reply Quote 0
                                        • T
                                          TieT
                                          last edited by

                                          Hi xTofh

                                          Telenet is working on their infrastructure, maybe this could explain the loss off connection ?
                                          Also I don't use IPv6 and i'm not facing these problems (Telenet Whoppa)

                                          Source:
                                          http://klantenservice.telenet.be/content/van-welke-internetabonnementen-passen-we-de-naam-en-snelheden-aan-vanaf-29-maart-2015

                                          1 Reply Last reply Reply Quote 0
                                          • T
                                            TieT
                                            last edited by

                                            Spoke too soon … lost my wan again, after starting a vpn connection, will add more details when i get home

                                            :Update:

                                            My HDD crashed ... thank god for backups  ;D
                                            After swapping the HDD, everything is working fine again

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