You have high latency+packetloss …. Ouch.

Thank you for the comment. I did believe that the built-in driver would be solid at some point and your post has motivated to go back and convert all my E1000 to vmxnet3 adapters. Hopefully it won't have the interface reassignment issues right after upgrade, that I ran into a while ago :-> @cmb: vmxnet3 in 2.2.x and newer has proven very solid, I'm not aware of any problems with the built-in driver in FreeBSD 10.x versions and it's widely used.

I'm having this issue also. Two different systems at two different sites. Mine is failing on umber of packages to be installed: 1 Number of packages to be upgraded: 66 The process will require 2 MiB more space. 21 MiB to be downloaded. Fetching perl5-5.20.3_13.txz: ....... done pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/All/perl5-5.20.3_13.txz: Operation timed out >>> Locking package pfSense-kernel-pfSense... Locking pfSense-kernel-pfSense-2.3.1_5 It works when I manually wget the link.. both systems are running as VMs on VMWare ESXi. I upgraded my test router to 2.3.2 without issue about 2 and a half weeks ago  :-\

Well, a quick call to the ISP sorted it out. I was using the wrong gateway. (facepalm) What I haven't looked into is why my other two servers are working, albeit still going through the incorrect gateway. Thanks for the help!

Steve gave me access to his code for the Fireboxes, but I gave up, as I wasn't getting very far. I ended up using a splitter cable and a small potentiometer on the two fans on the cpu side and this reduced the noise quite a bit. However, after doing an update from 2.1.5 I found that I was getting a lot of errors in the logs, relating to the NIC's. It's a while ago so I can't remember all that I did, but I believe it was due to an update in the BSD OS. I went back to 2.1.5 and the problem disappeared. I don't know if the situation has changed in the meantime, but I am looking at other devices that have Intel NIC's and may well replace the Proventia at some point.

disable ipv6 and try again

Thanks KOM! This worked like a charm. JayArr

Thanks to all, I've got it all running pretty well. The restore is in the GUI section, which I didn't expect, and that's where I think my confusion came from. I figured I was going to have to cut and paste with vim on a command line and then reboot. I love the fact that you can restore just a section of an old config file, this is a brilliant feature by the devs. In my case, all I really wanted to avoid was typing in all of the static mappings in the DHCP servers and I was able to import all of that in a couple of clicks. Brilliant. Thanks!

Got the same error when i tried initial upgrade from GIU 2.3.1-RELEASE-p5 (amd64) built on Thu Jun 16 12:53:15 CDT 2016 FreeBSD 10.3-RELEASE-p3 Second attempt: _61 MiB to be downloaded. Fetching pfSense-kernel-pfSense-2.3.2.txz: …....... done Fetching pfSense-default-config-2.3.2.txz: . done Fetching pfSense-base-2.3.2.txz: ........ done pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/All/pfSense-base-2.3.2.txz: Operation timed out Locking package pfSense-kernel-pfSense... done. Failed_

There is a period of time during the startup of pfSense, between when an interface is being activated, i.e. "Configuring *** Interface…" and when the firewall rules are applied, i.e. "Configuring firewall......done" in which the system is wide open.

It is saved in the ordinary pfSense config. Just make sure to do regular backup of the config - Diagnostics->Backup & Restore When you have backed up, use at text editor to look in the file you backed up. Search for user names and check they are there.

aii  I realized I downloaded the 32bit by mistake I will download the 64bit and try again I think that might have the problem

Multiple threads on the same thing will not get you help any faster. Also use code tags to avoid a "wall of text" posts.

It's most likely the effect of ARP cache and the modem insisting on not clearing it until the entries time out or it is rebooted. There is a piece of technology designed for the very situation known as "Gratuitous ARP" but if the modem does not honour that there are no other options than the two I already mentioned.

Anybody? I'll settle for not knowing why this interface bricked itself as long as I can force its removal from my system. Is there a command line function that can force the removal of an interface?

Access pfSense via SSH, option Shell (8) and use the command: pfSense-upgrade -d This worked for me.

Out of just pure curiosity why are you wanting to install 2.3.0 vs 2.3.2 – you really should install current.