I have managed to get the update from 2.3.1 to 2.3.1p5 working, but like you say, it takes a long time to complete. And i have used the 2Gb image, i think is gonna take a while longer for the 4Gb image. I have also the feeling that 2.3.1p5 is still verry unstable, i have opened another topic about problems with timeout errors at boot, and corrupting after reboot or shutdown. Grtz DeLorean

New traffic graphs are coming in 2.4 most likely. preview: https://forum.pfsense.org/index.php?topic=113513.msg636707#msg636707

You can back up your config, install a full install, and restore your config. You just can't upgrade in place.

Just a note about DHCP - when you enable DHCP on an interface, pfSense puts an (unseen) rule on the interface to allow incoming DHCP requests. So that is why DHCP works even when you have no user-added pass rule.

Ah ok, that worked, thanks.

PM sent!  Thanks!!

What version of pfSense are you using? And can you try that pkg install from the command line to see if any additional info is printed? ssh in or use the console, enter option 8 for a shell, then run: pkg install pfSense-pkg-openvpn-client-export

Amazing!!! it work I can now access the GUI Thank you :)

Ah, I see, thanks. I must've been on a slightly earlier build.

You're the BEST, ptt! I couldn't execute the command directly on the pfSense Shell, so I put the encrypted file onto a CentOS 6 install I have here and decrypted it. I then moved the decrypted file to the USB thumb drive, put it back into the pfSense box, rebooted it and it restored the config automatically. Thanks SO much for the help!

You do have a point about it being convoluted. This is the least costly/most work option. There are other options. like buying a laptop for non gaming  & important stuff, just use the present one for windows gaming only . Maybe in a KVM switch for convenience. Just exploring my options now before deciding to upgrade to the 'free' windows 10.

I've had the exact same issue, with crashing quite frequently. I tracked this down to the use of IPv6, where disabling the interface that maps to my HE.NET tunnel stopped the frequent crashing. I assumed it was related to IPv6 because of the presence of related stack frames. It started after upgrading to 2.3, tested again with 2.3.1-RELEASE-p5 (i386), crashes similarly. Thanks. – Here's my crash stack: Tracing pid 12 tid 100029 td 0xc706e320 kdb_enter(c147c596,c147c596,c1643747,c1fb7b9c,0,...) at kdb_enter+0x3d/frame 0xc1fb7b48 vpanic(c1643747,c1fb7b9c,c1fb7b9c,c1fb7bb4,c12e79ab,...) at vpanic+0x13b/frame 0xc1fb7b7c panic(c1643747,0,0,0,c6bd1030,...) at panic+0x1b/frame 0xc1fb7b90 dblfault_handler() at dblfault_handler+0xab/frame 0xc1fb7b90 --- trap 0x17, eip = 0xc0d3c828, esp = 0xc6bd0fd0, ebp = 0xc6bd1030 --- cpu_search_lowest(c1f97158,c6bd1068,2,56f000,0,...) at cpu_search_lowest+0x18/frame 0xc6bd1030 cpu_search_lowest(c1f97144,c6bd10c0,0,54,c720b320,...) at cpu_search_lowest+0x17e/frame 0xc6bd1098 sched_pickcpu(c6bd1120,c1f97158,c6bd1128,0,2c0,...) at sched_pickcpu+0x230/frame 0xc6bd10ec sched_add(c720b320,0,1,d2ff05,2710) at sched_add+0x69/frame 0xc6bd1128 sched_wakeup(c720b320,c130ddd8,c720b320,c6bd1190,c0d60631,...) at sched_wakeup+0x161/frame 0xc6bd1150 setrunnable(c720b320,c6bd1198,0,c6bd1200,c0d10056,...) at setrunnable+0x42/frame 0xc6bd1164 sleepq_resume_thread(0,0,c1480b7a,37e,c706e320,...) at sleepq_resume_thread+0x101/frame 0xc6bd1190 sleepq_timeout(c720b320,c354e56e,c7091000,0,0,...) at sleepq_timeout+0x93/frame 0xc6bd11b8 softclock_call_cc(1,c6bd12b8,c0cb2ff2,1,0,...) at softclock_call_cc+0x192/frame 0xc6bd1244 callout_process(f192ad29,3604,c6bd1330,c0d3c98e,c1f97158,...) at callout_process+0x26e/frame 0xc6bd12b8 handleevents(0,c2,0,0,0,...) at handleevents+0x270/frame 0xc6bd1308 timercb(c7091064,0,1,c6f10c80,700,...) at timercb+0x346/frame 0xc6bd1364 hpet_intr_single(c7091064,c7097d40,c6bd1410,0,c6bd13c8,...) at hpet_intr_single+0x190/frame 0xc6bd1390 hpet_intr(c7091000,0,c706e320,14,c6ef4f14,...) at hpet_intr+0x6d/frame 0xc6bd13a8 intr_event_handle(c6f14100,c6bd1410,2710,c6bd1410,c1e907fc,...) at intr_event_handle+0x85/frame 0xc6bd13c8 intr_execute_handlers(c6ef4f14,c6bd1410,0) at intr_execute_handlers+0x42/frame 0xc6bd13e8 lapic_handle_intr(32,c6bd1410) at lapic_handle_intr+0x40/frame 0xc6bd1400 Xapic_isr1() at Xapic_isr1+0x43/frame 0xc6bd1400 --- interrupt, eip = 0xc12d6087, esp = 0xc6bd1450, ebp = 0xc6bd1454 --- spinlock_exit(c1e907fc,0,0,0) at spinlock_exit+0x27/frame 0xc6bd1454 wakeup_one(c1e907fc,c8304a00,5d,0,6f7c249) at wakeup_one+0x3d/frame 0xc6bd1474 ng_worklist_add(50939500,338,28,1,10000000,...) at ng_worklist_add+0xc0/frame 0xc6bd149c ng_queue_rw(0,c7646800,c841f900,0,c6bd14fc,...) at ng_queue_rw+0xa5/frame 0xc6bd14c8 ng_snd_item(c7f259c0,0,c769c180,0,5c,...) at ng_snd_item+0xde/frame 0xc6bd14fc ng_iface_send(2,1,0,c8304e00,1,...) at ng_iface_send+0xe4/frame 0xc6bd152c ng_iface_start(c7646800,c841f900,0,f5ae2a93,f19140c1,...) at ng_iface_start+0x42/frame 0xc6bd1560 if_transmit(c7646800,c841f900,4,c841f900,0,...) at if_transmit+0x154/frame 0xc6bd1598 ng_iface_output(c7646800,c841f900,c6bd17f8,0,c6bd1770,...) at ng_iface_output+0x1ca/frame 0xc6bd15c8 pf_test(2,c7646800,c6bd1874,0,0,...) at pf_test+0x2a5e/frame 0xc6bd1830 pf_check_out(0,c6bd1874,c7646800,2,0,...) at pf_check_out+0x29/frame 0xc6bd1850 pfil_run_hooks(c2021dfc,c6bd1944,c7646800,2,0,...) at pfil_run_hooks+0x88/frame 0xc6bd18a8 ip_output(c841f900,0,0,0,0,...) at ip_output+0xa3f/frame 0xc6bd1968 in_gif_output(c7207400,c841f900,29,0,c7582c80,...) at in_gif_output+0x135/frame 0xc6bd19bc gif_transmit(c7207400,c841f900,7,1c) at gif_transmit+0x37a/frame 0xc6bd19f0 gif_output(c7207400,c841f900,c6bd1ce8,0,be74,fd011080,fc0ac741) at gif_output+0x4b/frame 0xc6bd1a10 nd6_output_ifp(c841f900,c6bd1ce8,0,0,0,...) at nd6_output_ifp+0xe3/frame 0xc6bd1a40 nd6_output(c7207400,c7207400,c841f900,c6bd1ce8,0,...) at nd6_output+0x1aa/frame 0xc6bd1ac0 pf_test6(2,c7207400,c6bd1d6c,c8e24ccc,c6bd1fd8,...) at pf_test6+0x27c1/frame 0xc6bd1d28 pf_check6_out(0,c6bd1d6c,c7207400,2,c8e24ccc,...) at pf_check6_out+0x29/frame 0xc6bd1d48 pfil_run_hooks(c20237e4,c6bd1efc,c7207400,2,c8e24ccc,...) at pfil_run_hooks+0x88/frame 0xc6bd1da0 ip6_output(c841f900,0,c6bd1fd8,0,0,...) at ip6_output+0x1464/frame 0xc6bd1f28 tcp_output(c7f3b8e8,41c70ac9,41c70afc,0,c20226ec,...) at tcp_output+0x1d8b/frame 0xc6bd2098 tcp_do_segment(c78af9f0,c7f3b8e8,48,33,0,...) at tcp_do_segment+0x3d7a/frame 0xc6bd2150 tcp_input(c8438a00,28,0,c6bd22e0,0,...) at tcp_input+0x12e7/frame 0xc6bd2258 tcp6_input(c6bd236c,c6bd2368,6,0,0,...) at tcp6_input+0x1b9/frame 0xc6bd2298 ip6_input(c8438a00,c7646800,0,c0e85166,c1e85240,...) at ip6_input+0xca2/frame 0xc6bd2448 netisr_dispatch_src(a,0,c8438a00) at netisr_dispatch_src+0x8b/frame 0xc6bd2490 netisr_dispatch(a,c8438a00,7b,0,c0e8eff6,...) at netisr_dispatch+0x20/frame 0xc6bd24a4 gif_input(c8438a00,c7207400,29,0,0,...) at gif_input+0x335/frame 0xc6bd24d8 in_gif_input10(c8438a00,14,4,1,14,...) at in_gif_input10+0x57/frame 0xc6bd2500 encap4_input(c8438a00,14,c7646800,1,0,...) at encap4_input+0x210/frame 0xc6bd2560 ip_input(c8438a00,c12d6070,0,c6bd260c,c0d6074a,...) at ip_input+0x2d2/frame 0xc6bd25c8 netisr_dispatch_src(1,0,c8438a00) at netisr_dispatch_src+0x8b/frame 0xc6bd2610 netisr_dispatch(1,c8438a00,4,c8438a00,2,...) at netisr_dispatch+0x20/frame 0xc6bd2624 ng_iface_rcvdata(c769c180,c7f259c0,c784cbec,c784cb98,c6bd2688,...) at ng_iface_rcvdata+0xea/frame 0xc6bd264c ng_apply_item(0,c1f96860,c6bd26dc,c0cf4203,c6bd26dc,...) at ng_apply_item+0x22d/frame 0xc6bd26a8 ng_snd_item(c7f259c0,0,c76e2380,0,0,...) at ng_snd_item+0x19d/frame 0xc6bd26dc ng_tcpmss_rcvdata(c76e2500,c7f259c0,0,0,c76e0680,...) at ng_tcpmss_rcvdata+0xa8/frame 0xc6bd2724 ng_apply_item(0,c80fc640,c841e900,0,c7f28b40,...) at ng_apply_item+0x22d/frame 0xc6bd2780 ng_snd_item(c7f259c0,0,c76e0480,0,c7f259c0,...) at ng_snd_item+0x19d/frame 0xc6bd27b4 ng_ppp_comp_recv(21,0,1,c8438a00,c7724000,...) at ng_ppp_comp_recv+0x158/frame 0xc6bd27e0 ng_ppp_crypt_recv(21,0,0,c6bd282c,c0d889ed,...) at ng_ppp_crypt_recv+0x70/frame 0xc6bd27fc ng_ppp_rcvdata(c76e2400,c7f259c0,c7ead01a,c81d67c0,c706e320,...) at ng_ppp_rcvdata+0x2db/frame 0xc6bd2858 ng_apply_item(0,101a8c0,c8e2b1f8,c841e900,0,...) at ng_apply_item+0x22d/frame 0xc6bd28b4 ng_snd_item(c7f259c0,0,c76e0e80,0,c6bd2a08,...) at ng_snd_item+0x19d/frame 0xc6bd28e8 ng_tee_rcvdata(c76e0100,c7f259c0,264,c841e900,0,...) at ng_tee_rcvdata+0x156/frame 0xc6bd2910 ng_apply_item(0,c8480006,6,400000c0,c841e900,...) at ng_apply_item+0x22d/frame 0xc6bd296c ng_snd_item(c7f259c0,0,c76e0180,0,b275d85b,...) at ng_snd_item+0x19d/frame 0xc6bd29a0 ng_pppoe_rcvdata_ether(c76e0500,c7f259c0,0,c6bd2a88,c70dae40,...) at ng_pppoe_rcvdata_ether+0x2a3/frame 0xc6bd2a1c ng_apply_item(0,c70cd800,c8438a00,0,c6bd2aac,...) at ng_apply_item+0x22d/frame 0xc6bd2a78 ng_snd_item(c7f259c0,0,c76e0300,0,c70cd800,...) at ng_snd_item+0x19d/frame 0xc6bd2aac ng_ether_input_orphan(c70cd800,c8438a00,c8e20fc8,c6bd2b20,c1052dad,...) at ng_ether_input_orphan+0x66/frame 0xc6bd2acc ether_demux(c70cd800,c8438a00,6,c70d2240,c6bd2b90,...) at ether_demux+0x1e7/frame 0xc6bd2af8 ether_nh_input(c8438a00,c709d9bc,c709d000,c838a900,c6bd2bb4,...) at ether_nh_input+0x36b/frame 0xc6bd2b48 netisr_dispatch_src(9,0,c8438a00) at netisr_dispatch_src+0x8b/frame 0xc6bd2b90 netisr_dispatch(9,c8438a00) at netisr_dispatch+0x20/frame 0xc6bd2ba4 ether_input(c70cd800,c8438a00,c6bd2bf8,c6f16000,0,...) at ether_input+0x19/frame 0xc6bd2bb4 re_rxeof(c1f86e80,c6f16000,0,0,0,...) at re_rxeof+0x4a4/frame 0xc6bd2c08 re_intr_msi(c709d000,0,246,0,a525361c,...) at re_intr_msi+0x107/frame 0xc6bd2c3c intr_event_execute_handlers(109,c6f15880,c147739b,55b,ffffffff,...) at intr_event_execute_handlers+0xaa/frame 0xc6bd2c68 ithread_loop(c70cadc0,c6bd2ce8,ffffffff,ffffffff,fffbffff,...) at ithread_loop+0x80/frame 0xc6bd2ca4 fork_exit(c0cd81d0,c70cadc0,c6bd2ce8) at fork_exit+0xa3/frame 0xc6bd2cd4 fork_trampoline() at fork_trampoline+0x8/frame 0xc6bd2cd4

I took a quick look at the Nighthawk VDSL D700 instructions, being unfamiliar with the device, and found that under the "Manage the WAN and LAN Network Settings" section they have a "IPTV" mode where you can designate that the #4 LAN port can be set in what appears to be a DMZ.  The item attached at that port 'shares' the internet IP that the modem gets.  I use ATT UVerse with their modem/router and have been putting my Zyxel, and now my pfSense VM in the DMZ and I got everything working including the OpenVPN.  Hopefully following those instructions can get your pfSense setup on an internet IP without having to change much else on your router.  Remember that you should have pfSense set with a LAN IP network range different from what the Nighthawk gives out on its other LAN ports, and everything attached to the pfSense router will be isolated from anything attached to the Nighthawk's other ports and wireless.  So if the goal is to have everything running through pfSense, the Nighthawk's wireless and its other LAN ports should not be used if you get working this way.  UVerse is not PPPOE so I don't have to think about logging in, but as the modem is still doing so, and passing the internet IP to the LAN port 4, you should be able to leave pfSense WAN in DHCP and attach it to port 4 on your Nighthawk.  Hope this helps.

Difficult to help you with the provided information…. Maybe can be this --> https://forum.pfsense.org/index.php?topic=113881.msg633813#msg633813

Did you check my reply here? https://forum.pfsense.org/index.php?topic=114633.msg637424#msg637424

my observations after looking around the office at the cables here is that none of them are labeled for CAT5 or CAT6 My own experience over the last (ahem..) 30+ years of playing with networks, cabling, PC's and a variety of attached devices is you generally get what you pay for. If you buy patch cables from a reputable source, they'll be properly labelled and perform as expected. Unlabelled and DIY cables (don't ever, ever, ever, ever make/use hand made cables) are simply ticking disasters waiting to bite you (that goes for both CAT5e & CAT6). Especially these days when I can buy 10' pre-made patch cables for < $2, what's the point in risking anything else? I'd much rather chase logistical problems in network design than potentially flaky hardware and connections any day. Just my $.02