@wallabybob: What version of pfSense are you using? Have you tried the newly released pfSense 2.0.3? Yep…the issue is fixed in the newly released 2.0.3 :) Just installed the 2.0.3 and I tried both the factory reset of modem and unplugging it for a couple of minutes and both times pfsense was able to recover within minutes of the modem completing its booting process and then my VPN connections were also up within a few seconds after the WAN was up. Logs Apr 15 22:11:52 check_reload_status: Linkup starting re0 Apr 15 22:11:52 kernel: re0: link state changed to DOWN Apr 15 22:11:54 php: : DEVD Ethernet detached event for wan Apr 15 22:11:54 dhclient[51151]: connection closed Apr 15 22:11:54 dhclient[51151]: connection closed Apr 15 22:11:54 dhclient[51151]: exiting. Apr 15 22:11:54 dhclient[51151]: exiting. Apr 15 22:11:56 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:11:56 kernel: arpresolve: can't allocatae rlplriensfool vfeo:r c9a9n.'2t2 8a.l1l1o6c.a1t Apr 15 22:11:56 kernel: e Apr 15 22:11:56 kernel: llinfo for 99.228.116.1 Apr 15 22:11:56 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:11:57 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:11:57 kernel: arpresolve: caarnp'rte saolllvoec:a tcea nl'lti naflol ofcoart e l9l9i.n2f2o8 .f1o1r6 .1 Apr 15 22:11:57 kernel: 9 Apr 15 22:11:57 kernel: 9.228.116.1 Apr 15 22:11:57 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:11:57 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:11:58 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:11:58 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:11:58 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:11:58 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:11:59 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:11:59 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:11:59 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:00 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:00 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:00 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:00 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:00 apinger: ALARM: OpenVPNPIAGateway(10.199.230.1) *** down *** Apr 15 22:12:00 apinger: ALARM: GW_WAN(99.228.116.1) *** down *** Apr 15 22:12:00 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:01 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:01 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:01 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:01 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:01 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:01 apinger: ALARM: VPN(10.154.1.1) *** down *** Apr 15 22:12:01 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:01 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:02 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:02 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:02 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:02 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:03 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:03 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:03 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:03 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:03 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:04 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:04 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:04 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:05 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:05 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:05 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:05 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:06 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:06 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:06 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:06 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:06 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:06 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:07 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:07 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:07 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:08 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:08 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:08 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:09 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:09 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:09 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:09 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:10 kernel: arpresolve: can't allocate llinfo for 9a9.r2p2r8e.s1o1l6v.e1: Apr 15 22:12:10 kernel: Apr 15 22:12:10 kernel: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:10 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:10 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:10 check_reload_status: Reloading filter Apr 15 22:12:11 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:11 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:11 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:11 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:12 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:12 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:12 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:14 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:14 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:14 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:15 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:15 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:15 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:15 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:15 kernel: arpresolve: can't allocataer plrleisnoflov ef:o rc an9'9t. 22a8l.l1o1c6a.t1e Apr 15 22:12:15 kernel: Apr 15 22:12:15 kernel: llinfo for 99.228.116.1 Apr 15 22:12:15 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:15 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:16 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:16 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:16 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:16 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:16 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:16 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:16 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:17 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:17 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:17 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:18 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:18 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:18 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:18 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:18 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:18 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:18 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:19 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:19 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:19 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:20 kernel: <<77>a>raprrperseoslovlev:e :c acna'nt' ta lallolcoactaet el llilnifnof of ofro r 9999..222288..111166.1. Apr 15 22:12:20 kernel: 1 Apr 15 22:12:20 kernel: Apr 15 22:12:20 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:21 kernel: <<77>>aarrpprreessoollvvee:: ccaann''tt aallllooccaattee lllilnifnfoo ffoorr 9999..222288..111166..11 Apr 15 22:12:21 kernel: Apr 15 22:12:21 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:21 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:21 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:21 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:21 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:22 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:22 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:22 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:23 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:23 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:23 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:24 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:24 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:24 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:24 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:25 kernel: arpresolve: cana'rtp raelsloolcvaet:e lclainn'fto aflolro cat9e9 .l2l2i8n.f1o1 6f.o1r Apr 15 22:12:25 kernel: Apr 15 22:12:25 kernel: 99.228.116.1 Apr 15 22:12:25 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:25 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:25 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:25 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:25 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:25 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:25 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:26 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:26 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:26 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:26 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:26 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:26 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:26 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:27 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:27 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:27 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:27 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:27 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:27 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:27 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:27 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:27 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:28 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:28 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:28 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:28 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:28 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:28 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:28 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:28 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:29 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:29 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:29 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:29 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:29 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:29 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:29 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:30 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:30 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:30 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:31 kernel: <<77>>aarrpprreessoollvvee:: ccaann''tt aallllooccaattee lllliinnffoo ffoorr 999.92.2282.81.1161.61. Apr 15 22:12:31 kernel: 1 Apr 15 22:12:31 kernel: Apr 15 22:12:31 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:31 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:31 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:31 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:31 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:32 kernel: <<7>a7r>parrepsroelsvoel:v ec:a nc'atn 'atl laolclaotcea tlel ilnlfion ffoo rf or 99.9292.8.21218.61.161. Apr 15 22:12:32 kernel: 1 Apr 15 22:12:32 kernel: Apr 15 22:12:32 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:32 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:33 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:33 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:33 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:33 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:34 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:34 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:34 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:34 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:34 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:34 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:34 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:34 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:35 kernel: arpresolve: can't allaocratper eslolilnvfeo: fcoarn 't 9a9l.l2o2c8a.t1e1 6l.l1i Apr 15 22:12:35 kernel: n Apr 15 22:12:35 kernel: fo for 99.228.116.1 Apr 15 22:12:35 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:36 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:36 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:36 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:37 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:37 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:37 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:37 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:38 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:38 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:38 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:38 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:38 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:38 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:38 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:38 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:38 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:38 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:38 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:39 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:39 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:39 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:39 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:39 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:39 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:39 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:40 kernel: arpresolve: can't allocate llinfaor pforre sol9v9.e2:2 8c.a1n1'6t. 1a Apr 15 22:12:40 kernel: l Apr 15 22:12:40 kernel: locate llinfo for 99.228.116.1 Apr 15 22:12:40 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:40 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:41 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:41 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:41 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:41 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:41 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:41 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:41 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:42 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:42 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:42 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:43 kernel: <<77>>aarrpprreessoollvvee:: ccaann''tt aallllooccaattee lllliinnffoo ffoorr 9999..222288..111166..11 Apr 15 22:12:43 kernel: Apr 15 22:12:43 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:43 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:43 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:43 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:43 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:44 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:44 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:44 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:45 kernel: arpresolve: can't allocate llinfo for 99.228.11a6.r1p Apr 15 22:12:45 kernel: r Apr 15 22:12:45 kernel: esolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:45 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:45 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:46 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:46 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:46 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:46 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:46 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:46 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:46 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:46 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:46 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:47 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:47 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:47 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:48 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:48 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:48 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:49 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:49 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:49 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:12:52 kernel: ovpnc1: link state changed to DOWN Apr 15 22:12:52 kernel: ovpnc2: link state changed to DOWN Apr 15 22:12:52 check_reload_status: Reloading filter Apr 15 22:13:12 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:13 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:17 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:21 check_reload_status: Linkup starting re0 Apr 15 22:13:21 kernel: re0: link state changed to UP Apr 15 22:13:23 php: : DEVD Ethernet attached event for wan Apr 15 22:13:23 php: : HOTPLUG: Configuring interface wan Apr 15 22:13:23 dhclient: PREINIT Apr 15 22:13:23 dhclient[6434]: DHCPREQUEST on re0 to 255.255.255.255 port 67 Apr 15 22:13:24 lighttpd[29055]: (connections.c.1721) SSL (error): 5 -1 1 Operation not permitted Apr 15 22:13:24 lighttpd[29055]: (connections.c.1721) SSL (error): 5 -1 1 Operation not permitted Apr 15 22:13:24 dhclient[6434]: DHCPREQUEST on re0 to 255.255.255.255 port 67 Apr 15 22:13:25 dhclient[6434]: DHCPREQUEST on re0 to 255.255.255.255 port 67 Apr 15 22:13:25 check_reload_status: Linkup starting re0 Apr 15 22:13:25 kernel: re0: link state changed to DOWN Apr 15 22:13:26 dhclient[6434]: DHCPREQUEST on re0 to 255.255.255.255 port 67 Apr 15 22:13:27 check_reload_status: Linkup starting re0 Apr 15 22:13:27 kernel: re0: link state changed to UP Apr 15 22:13:27 php: : DEVD Ethernet detached event for wan Apr 15 22:13:27 dhclient[6565]: connection closed Apr 15 22:13:27 dhclient[6565]: connection closed Apr 15 22:13:27 dhclient[6565]: exiting. Apr 15 22:13:27 dhclient[6565]: exiting. Apr 15 22:13:27 php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf re0 > /tmp/re0_output > /tmp/re0_error_output' returned exit code '15', the output was '' Apr 15 22:13:29 php: : DEVD Ethernet attached event for wan Apr 15 22:13:29 php: : HOTPLUG: Configuring interface wan Apr 15 22:13:29 dhclient: PREINIT Apr 15 22:13:29 dhclient[12806]: DHCPREQUEST on re0 to 255.255.255.255 port 67 Apr 15 22:13:30 dhclient[12806]: DHCPREQUEST on re0 to 255.255.255.255 port 67 Apr 15 22:13:31 dhclient[12806]: DHCPREQUEST on re0 to 255.255.255.255 port 67 Apr 15 22:13:32 dhclient[12806]: DHCPREQUEST on re0 to 255.255.255.255 port 67 Apr 15 22:13:34 dhclient[12806]: DHCPREQUEST on re0 to 255.255.255.255 port 67 Apr 15 22:13:34 dhclient[12806]: DHCPNAK from 192.168.100.1 Apr 15 22:13:34 dhclient[12806]: DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 2 Apr 15 22:13:36 dhclient[12806]: DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 5 Apr 15 22:13:36 dhclient[12806]: DHCPOFFER from 192.168.100.1 Apr 15 22:13:36 dhclient[12806]: Bogus Host Name option 12: 150mbps_link_host (150mbps_link_host) Apr 15 22:13:36 dhclient[12806]: Bogus Host Name option 12: 150mbps_link_host (150mbps_link_host) Apr 15 22:13:36 dhclient: ARPSEND Apr 15 22:13:36 dhclient[12806]: DHCPOFFER from 192.168.100.1 Apr 15 22:13:38 dhclient: ARPCHECK Apr 15 22:13:38 dhclient[12806]: DHCPREQUEST on re0 to 255.255.255.255 port 67 Apr 15 22:13:38 dhclient[12806]: DHCPACK from 192.168.100.1 Apr 15 22:13:38 dhclient[12806]: Bogus Host Name option 12: 150mbps_link_host (150mbps_link_host) Apr 15 22:13:38 dhclient[12806]: Bogus Host Name option 12: 150mbps_link_host (150mbps_link_host) Apr 15 22:13:38 dhclient: BOUND Apr 15 22:13:38 dhclient: Starting add_new_address() Apr 15 22:13:38 dhclient: ifconfig re0 inet 192.168.100.10 netmask 255.255.255.0 broadcast 192.168.100.255 Apr 15 22:13:38 dhclient: New IP Address (re0): 192.168.100.10 Apr 15 22:13:38 dhclient: New Subnet Mask (re0): 255.255.255.0 Apr 15 22:13:38 dhclient: New Broadcast Address (re0): 192.168.100.255 Apr 15 22:13:38 dhclient: New Routers (re0): Apr 15 22:13:38 dhclient: Adding new routes to interface: re0 Apr 15 22:13:38 dhclient: Creating resolv.conf Apr 15 22:13:38 check_reload_status: rc.newwanip starting re0 Apr 15 22:13:38 dhclient[12806]: bound to 192.168.100.10 -- renewal in 30 seconds. Apr 15 22:13:40 php: : rc.newwanip: Informational is starting re0. Apr 15 22:13:40 php: : rc.newwanip: on (IP address: 192.168.100.10) (interface: wan) (real interface: re0). Apr 15 22:13:40 apinger: Exiting on signal 15. Apr 15 22:13:41 check_reload_status: Reloading filter Apr 15 22:13:41 apinger: Starting Alarm Pinger, apinger(24149) Apr 15 22:13:41 apinger: No usable targets found, exiting Apr 15 22:13:41 php: : DynDns: updatedns() starting Apr 15 22:13:41 php: : Dyndns debug information: Could not resolve checkip.dyndns.org to ip using interface ip 192.168.100.10. Apr 15 22:13:41 php: : DynDns: Current WAN IP could not be determined, skipping update process. Apr 15 22:13:41 php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Apr 15 22:13:42 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:43 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:43 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:44 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:44 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:44 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:44 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:44 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:45 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:46 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:47 php: : Resyncing OpenVPN instances for interface WAN. Apr 15 22:13:47 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:47 php: : Creating rrd update script Apr 15 22:13:47 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:48 ntpdate[60602]: can't find host 0.pfsense.pool.ntp.org Apr 15 22:13:48 ntpdate[60602]: no servers can be used, exiting Apr 15 22:13:48 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:50 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:52 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:53 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:54 ntpdate[4013]: can't find host 0.pfsense.pool.ntp.org Apr 15 22:13:54 ntpdate[4013]: no servers can be used, exiting Apr 15 22:13:55 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:57 dnsmasq[8421]: reading /etc/resolv.conf Apr 15 22:13:57 dnsmasq[8421]: using nameserver 208.67.222.222#53 Apr 15 22:13:57 dnsmasq[8421]: using nameserver 208.67.222.222#53 Apr 15 22:13:57 dnsmasq[8421]: using nameserver 208.67.220.220#53 Apr 15 22:13:57 dnsmasq[8421]: using nameserver 208.67.220.220#53 Apr 15 22:13:58 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:58 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:58 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:58 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:13:59 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:14:00 ntpdate[8205]: can't find host 0.pfsense.pool.ntp.org Apr 15 22:14:00 ntpdate[8205]: no servers can be used, exiting Apr 15 22:14:01 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:14:03 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:14:05 ntp: Giving up on time sync after 3 attempts. Apr 15 22:14:05 kernel: arpresolve: can't allocate llinfo for 99.228.116.1 Apr 15 22:14:05 php: : pfSense package system has detected an ip change 99.228.117.xxx -> 192.168.100.10 ... Restarting packages. Apr 15 22:14:05 check_reload_status: Starting packages Apr 15 22:14:07 ntpd_intres[9240]: host name not found: 0.pfsense.pool.ntp.org Apr 15 22:14:07 php: : Restarting/Starting all packages. Apr 15 22:14:07 SnortStartup[10933]: Snort START For SNORT for WAN(18563_re0)... Apr 15 22:14:08 dhclient[21049]: DHCPREQUEST on re0 to 192.168.100.1 port 67 Apr 15 22:14:09 dhclient[21049]: DHCPREQUEST on re0 to 192.168.100.1 port 67 Apr 15 22:14:09 SnortStartup[11603]: Snort START For SNORT for VPN1(4655_ovpnc1)... Apr 15 22:14:11 dhclient[21049]: DHCPREQUEST on re0 to 192.168.100.1 port 67 Apr 15 22:14:11 SnortStartup[16716]: Snort START For SNORT for VPN2(28360_ovpnc2)... Apr 15 22:14:14 dhclient[21049]: DHCPREQUEST on re0 to 192.168.100.1 port 67 Apr 15 22:14:20 dhclient[21049]: DHCPREQUEST on re0 to 192.168.100.1 port 67 Apr 15 22:14:32 dhclient[21049]: DHCPREQUEST on re0 to 255.255.255.255 port 67 Apr 15 22:14:39 dhclient: EXPIRE Apr 15 22:14:39 dhclient: Deleting old routes Apr 15 22:14:39 dhclient: PREINIT Apr 15 22:14:39 dhclient[21049]: DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 2 Apr 15 22:14:40 dhclient[21049]: DHCPOFFER from 7.2.120.1 Apr 15 22:14:40 dhclient: ARPSEND Apr 15 22:14:42 dhclient: ARPCHECK Apr 15 22:14:42 dhclient[21049]: DHCPREQUEST on re0 to 255.255.255.255 port 67 Apr 15 22:14:42 dhclient[21049]: DHCPACK from 7.2.120.1 Apr 15 22:14:42 dhclient: BOUND Apr 15 22:14:42 dhclient: Deleting old routes Apr 15 22:14:42 dhclient: Starting add_new_address() Apr 15 22:14:42 dhclient: ifconfig re0 inet 99.228.117.xxx netmask 255.255.254.0 broadcast 255.255.255.255 Apr 15 22:14:42 dhclient: New IP Address (re0): 99.228.117.xxx Apr 15 22:14:42 dhclient: New Subnet Mask (re0): 255.255.254.0 Apr 15 22:14:42 dhclient: New Broadcast Address (re0): 255.255.255.255 Apr 15 22:14:42 dhclient: New Routers (re0): 99.228.116.1 Apr 15 22:14:42 dhclient: Adding new routes to interface: re0 Apr 15 22:14:42 dhclient: /sbin/route add default 99.228.116.1 Apr 15 22:14:42 dhclient: Creating resolv.conf Apr 15 22:14:42 check_reload_status: rc.newwanip starting re0 Apr 15 22:14:42 dhclient[21049]: bound to 99.228.117.xxx -- renewal in 263472 seconds. Apr 15 22:14:44 php: : rc.newwanip: Informational is starting re0. Apr 15 22:14:44 php: : rc.newwanip: on (IP address: 99.228.117.xxx) (interface: wan) (real interface: re0). Apr 15 22:14:44 php: : ROUTING: setting default route to 99.228.116.1 Apr 15 22:14:45 check_reload_status: Reloading filter Apr 15 22:14:45 apinger: Starting Alarm Pinger, apinger(38212) Apr 15 22:14:45 php: : DynDns: updatedns() starting Apr 15 22:14:45 php: : DynDns debug information: 99.228.117.xxx extracted from local system. Apr 15 22:14:45 php: : DynDns: Current WAN IP: 99.228.117.xxx Cached IP: 99.228.117.xxx Apr 15 22:14:45 php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Apr 15 22:14:45 dnsmasq[8421]: reading /etc/resolv.conf Apr 15 22:14:45 dnsmasq[8421]: using nameserver 208.67.222.222#53 Apr 15 22:14:45 dnsmasq[8421]: using nameserver 208.67.222.222#53 Apr 15 22:14:45 dnsmasq[8421]: using nameserver 208.67.220.220#53 Apr 15 22:14:45 dnsmasq[8421]: using nameserver 208.67.220.220#53 Apr 15 22:14:51 php: : Resyncing OpenVPN instances for interface WAN. Apr 15 22:14:51 php: : Creating rrd update script Apr 15 22:14:53 ntpdate[40454]: adjust time server 64.6.144.6 offset -0.032301 sec Apr 15 22:14:53 php: : pfSense package system has detected an ip change 192.168.100.10 -> 99.228.117.xxx ... Restarting packages. Apr 15 22:14:53 check_reload_status: Starting packages Apr 15 22:14:54 kernel: ovpnc2: link state changed to UP Apr 15 22:14:54 check_reload_status: rc.newwanip starting ovpnc2 Apr 15 22:14:55 kernel: ovpnc1: link state changed to UP Apr 15 22:14:55 check_reload_status: rc.newwanip starting ovpnc1 Apr 15 22:14:55 php: : Restarting/Starting all packages. Apr 15 22:14:55 SnortStartup[49123]: Snort START For SNORT for WAN(18563_re0)... Apr 15 22:14:56 php: : rc.newwanip: Informational is starting ovpnc2. Apr 15 22:14:56 php: : rc.newwanip: on (IP address: 10.131.1.6) (interface: opt2) (real interface: ovpnc2). Apr 15 22:14:56 php: : Removing static route for monitor 10.199.230.1 and adding a new route through 10.160.230.5 Apr 15 22:14:56 php: : Removing static route for monitor 10.154.1.1 and adding a new route through 10.131.1.5 Apr 15 22:14:56 apinger: Exiting on signal 15. Apr 15 22:14:57 php: : rc.newwanip: Informational is starting ovpnc1. Apr 15 22:14:57 php: : rc.newwanip: on (IP address: 10.160.230.6) (interface: opt1) (real interface: ovpnc1). Apr 15 22:14:57 php: : Removing static route for monitor 10.199.230.1 and adding a new route through 10.160.230.5 Apr 15 22:14:57 php: : Removing static route for monitor 10.154.1.1 and adding a new route through 10.131.1.5 Apr 15 22:14:57 check_reload_status: Reloading filter Apr 15 22:14:57 apinger: Starting Alarm Pinger, apinger(52725) Apr 15 22:14:57 SnortStartup[54188]: Snort START For SNORT for VPN1(4655_ovpnc1)... Apr 15 22:14:59 SnortStartup[59715]: Snort START For SNORT for VPN2(28360_ovpnc2)... Apr 15 22:15:00 dnsmasq[8421]: reading /etc/resolv.conf Apr 15 22:15:00 dnsmasq[8421]: using nameserver 208.67.222.222#53 Apr 15 22:15:00 dnsmasq[8421]: using nameserver 208.67.222.222#53 Apr 15 22:15:00 dnsmasq[8421]: using nameserver 208.67.220.220#53 Apr 15 22:15:00 dnsmasq[8421]: using nameserver 208.67.220.220#53 Apr 15 22:15:02 php: : Creating rrd update script Apr 15 22:15:03 php: : Creating rrd update script Apr 15 22:15:03 php: : pfSense package system has detected an ip change 10.160.1.10 -> 10.131.1.6 ... Restarting packages. Apr 15 22:15:05 ntpdate[55722]: adjust time server 64.6.144.6 offset -0.026199 sec Apr 15 22:15:05 php: : pfSense package system has detected an ip change 10.118.230.10 -> 10.160.230.6 ... Restarting packages. Apr 15 22:15:05 check_reload_status: Starting packages Apr 15 22:15:07 php: : Restarting/Starting all packages. Apr 15 22:15:07 SnortStartup[63617]: Snort START For SNORT for WAN(18563_re0)... Apr 15 22:15:09 SnortStartup[777]: Snort START For SNORT for VPN1(4655_ovpnc1)... Apr 15 22:15:11 SnortStartup[2297]: Snort START For SNORT for VPN2(28360_ovpnc2)...

@ual4720: My Issue: My phones wont register with the VOIP server unless the VOIP server is set as the primary or first DNS in pfsense>services>dhcp server and My workstations are unable to resolve the primary domain controller unless it is set as my primary or first DNS in pfsense>services>dhcp server. 1. What version(s) of pfSense are in use? 2. Do you have the same name registered in multiple DNS servers with different IP addresses, for example pbx.mydomain.org as x.y.z.3 in the VOIP server and pbx.mydomain.com as x.y.z.15 in the PDC? If so, why? 3. Why don't you configure the VOIP server as the first DNS in pfsense1 and the PDC as the first DNS in pfSense2? 4. Can you give me details of why the phones don't register with the VOIP server … (Can't resolve name of the VOIP server? Can't reach the VOIP server? ...) 5.  Can you give more details of why the workstations are "unable to resolve the primary domain controller unless it is set as my primary or first DNS in pfsense>services>dhcp server "? They take notice of only the first DNS provided by DHCP and the other servers can't resolve the name? 6. Is DNS forwarder enabled in any of the pfSense boxes?  Why?

The only thing I can think of is to check the DHCP config matches the LAN.  Maybe the DHCP server is giving out addresses in the wrong address space for that LAN segment & routing is getting confused.

I didn't set it up that way.  Either CentOS did, or the guy using this machine did.  We don't use ipv6 in our network right now anyway.

Thanks Phil, that pointed me in the right direction. The solution was to add the following line to the advanced options of the DNS Forwarder configuraitn page: local=/subdomain.domain.com/

I made this change a couple of weeks ago: https://github.com/pfsense/pfsense/commit/87b9167234eed690ad6150624169f289f5075625 Now in 2.1 by default it just logs minimal success messages and actual errors. The other "progress scores" that it was logging only come if you enable the verbose logging option in Services->Dynamic DNS, Edit an entry.

Wow, that's shorter than I imagined. Thanks for responding…

Thank You. I have been pulling my hair out with this one, too. Then I saw this post and tried swapping out an old linksys switch.. Lo and behold, everything started working! The whole family are happy!

Why didn't you just use the built-in DNS forwarder host override settings if you are using static IPs or the DHCP server's static maqppings if you are using DHCP to assign addresses? With those two I have all my DNS needs for my LAN covered.

Brilliant. That's the ( so far ) bit I missed with floating queue rules.

i managed to change the LAN ip to 172.16.200.254 but when i change my wan tp static i dont get internet it only works when set to dhcp

Sorry, I overlooked that part.  That was just an example, I have three search domains I need.

Was there ever a solution found to this, because I'm having the same issue?

DHCP is on ports 67 and 68

Thanks :) I have choose the static IP solution.

Fixed/Solved. Was a series of comedy of errors. Had to use a console on FreeBSD server, a console on pfsense, and web access to pfsense. in pfsense shut-off DHCP server while there also removed static DHCP to 192.168.34.50 with bogus MAC to act as a placeholder.  This was first error.  ARP picked up address and showed in ARP table, but obviously it was linked to the wrong MAC address. cleaned out the ARP cache or reboot on pfsense arp -a on FreeBSD shows pfsense gateway ping to pfsense works arp on pfsense now shows 192.168.34.50 mapped to correct MAC address !! ping to FreeBSD still not working ? 8.) FreeBSD firewall rule drops (blocks) packets instead of reject.  Hence no ping.  Duh! Sort of error #2 (mental error?) Adjust firewall rules for testing.  Reset. Ok, now what about ssh into FreeBSd from pfsense console?  Nope - reject.  So its getting a response of sorts. Error #3 - FreeBSD ssh config was set to only listen on old address of server, not 192.168.34.50.  Fixed. Now have ssh access from pfsense console to FreeBSd server. Now what about original endpoint - WAN access to webserver 192.168.34.51? Yup. Thanks for pointing to arp to help trouble-shoot this. Peter

thx. that works perfect. exactly what i was looking for.

as ns0.thepiratebay.org probably will not answer DNS requests from anyone anyhow. I doubt they would do recursive, but yeah they are going to answer for records in thepiratebay.org domain - its an authoritative server for that zone.  It better answer for it. You you prob need .se, because thebay.org redirects to .se domain

Yeah I see right there in dhcp problems Also note that each time a new VM is created it’s assigned a new hardware address. You can change hardware address manually on the Advanced tab of VM Network Adapter Configuration should you need to do so. If you wireless card does not allow promiscuous, use of other macs - then use a different wireless card, or use a wire. Wouldn't another option just to set static IP?  Or use Natted connection under VM software vs bridged.