hahaha had this one today, so i did the following: typed https://this.is.my.wall:443/system.php and changed theme to nervecenter. Oh im on Windows 8.1 ;-)

OK for adding the reboot and installing missing packages after the backup. Thank you very much.

You can add me to the list of people with issues on 2.1.5 with the dnsmasq process eating 100% of a cpu thread and spotty dns functionality from clients on lan/vlan10/vlan20 dhcp'd interfaces. I have 2 Soekris net6501 boxes here on 2.1.5 - I used my spare box to test an upgrade to 2.1.5 awhile back and left it in production with the primary sitting off to the side for a month or so. I then took the primary and put it back into play, ran the upgrade, then imported the backed up config from the backup box. I added 2 vlan interfaces to my lan interface and configured the firewall rules for the new segments and got all of that working as expected. The following morning the issues started up (or I should say users started seeing them). At this point if there was some kind of fix in 2.2, I suppose its a debate of rolling back to 2.1.4, waiting for a 2.1.6 (if they release one with a patch for this), taking my chances on 2.2BETA in production, or waiting for 2.2 release.

Thank you for your reply, good to know I'm free to switch distribution types easily.

I would expect it to run on the GX520 though. Coulc be a disk controller issue or some bios bug that effects FreeBSD. https://forum.pfsense.org/index.php?topic=39824.msg209991#msg209991 Steve

Cool - Hope its good now.

The upgrade file is a tarball that contains all of the binaries and other files for the entire operating system along with pfSense. The new file is unpacked over the entire filesystem, then old/obsolete files are cleaned up, and other tasks are done, etc.

@stephenw10: Where are you seeing this string? In the logs? Only the base URL should appear in the autoupdate settings. That does mean a space would be very easy to overlook though. That's exactly what I was thinking, given that is separate, it'd be easy to slip an extra space into a log somewhere. But grepping through the source, I don't see anywhere that would happen. It definitely doesn't happen in any of the code that actually downloads and installs the updates. There might be a cosmetic bug somewhere where it's slipping in a space in the displayed URL, but I'm not seeing that either.

The driver is now In FreeBSD: https://github.com/markjdb/alx-freebsd/blob/master/README It may be in pfSense 2.2 already, have you tried it? The driver is in 10 stable but not 10.1 which I believe 2.2 is built on. Steve

@GomezAddams: I think you'd have to admit, it would be a nice touch if there were a button on the interface somewhere that says "Add networks to LAN Net". I'd have to disagree with this but I understand where you're coming from. The issue here, if an issue exists, is simply one of nomenclature. The 'LAN net' alias is the LAN interface subnet and no more and it shouldn't be anything else. It needs to remain only that so that it's available for use. Now it might be possible to have an autogenerated alias that represented the LAN subnet plus any routed subnets attached to it. I could imagine it being a logical nightmare to code though.  ;) Steve

The proxy setting for packages broke when we switched to HTTPS, that's since been fixed in 2.2. It hasn't been down at all.

I'll just point out that there are no bugs in the USB subsystem that I know of. I just used that as an example of what could happen. Steve

Ah, thanks, the serial console one pulls from a different file. The memstick/ISO one is labeled as I described. I just updated the serial one to match.

Nobody some idea? :(

@dsense137: Is booting from USB and then configuring the system all I need to do? Yes. However you may need to add the kerncam_delay to the boot loader options depending on your USB hardware. You may also need to point the system to the correct mount point for root, it expects to find it on an IDE interface which it won't be for you. @dsense137: Also, what happens if I shutdown temporarily, will I need to boot from USB and reconfigure? Thanks. No. The configuration is stored on the NanoBSD boot media whatever that may be. Steve

As an aside, take a look at kiTTY, a fork of puTTY.

Yes but that's ok because the image you're writing contains the partition/slice info. It's a raw image of the drive. Unless of course you have other partitions on disk1 you need to keep! Steve

Yes, do you have some good reason to upgrade from a CD rather than downloading the upgrade image directly? I have never tried to do this but if you really need to upgrade from CD then I would mount the CD manually and then run the manual upgrade from the console menu. Steve

Ah sorry, certainly. Firstly if you feel you can use UPnP without causing some security nightmare then just do that because with it enabled 'it just works'. Skype has a settings/preferences page that can be accessed in the application (in the Windows and Linux versions at least). In that it specifies what port it listens for direct incoming connections on and allows you to change it if you wish. Knowing that port you can then set a port forward on WAN for UDP traffic. The option to show info is in the Advanced section labelled 'Display technical call info'. In Windows you can also right click the video window to bring it up during a call but the Linux app seems slightly less…. polished. There doesn't appear to be a way of limiting the video resolution. I was pretty sure there used to be a bandwidth limit you could set but if there was it's gone now. There used to be number of hacks for forcing high resolution video by editing the config file. You might be able to that to force a lower resolution. You could always use a limiter in pfSense to restrict bandwidth. Steve