A lot more information needed to answer that.  ;) Which Watchguard hardware? What access points? How are they connected? Which pfSense install type? Anything else you thing may be relevant. Steve

YES!! This has been bothering me for months! This fixes it. Thank you. @eduardr: My particular problem was I had set the DNS forwarder service to bind only to the LAN IP's, and it turns out Localhost needs to be added to the list to bind to as well - otherwise the firewall itself cannot resolve the dns name for the update server. This post had the info that clued me in - https://forum.pfsense.org/index.php?topic=68164.15

I could not get Name to work. Got Lucky and Auto worked. Thanks for your Help Jerry

Thanks Steve! That would explain all this certainly. I'm very happy to re-read the page you linked to that shows that ad0 error can be ignored- I was yet to go back and check that was exactly what mine was reporting. Up until now have been having trouble getting the WAN port to pickup a routable address from the bridged cable modem/4 port switch.  Any of the pfSense's hosts' Intel NICs will happily pickup an IPv4 address if I connect them to a network with a DHCP server, but when I connect them to the cable modem's 3rd or 4th port it won't. It shows a link light and negotiates speed & duplex- but won't bring up an IP connection. I've tried assigning WAN to other ports, manually setting duplex to Full and Half. Other devices on my network pickup a routable address if I plug them into the cable modem instead of the pfSense host (LATER EDIT: but only ones which have been conected to it before) In the end I read in another post that this is expected behaviour with cable modems/networks. After re-booting the cable modem it came up fine.  Had some weird things happen during all this with the dhcpd/local interface after completing the webgui's config wizard. Couldn't regain access from the LAN and had to reboot a few times. Maybe my Netgear gigabit RTL card is not getting a warm welcome (it worked well under m0n0wall). Anyway… thanks again. Finally it is time to try the lusher pastures over here at pfSense! On the way home today I found a better rig to use- thrown out in the street just like the old one. An old AMD Sempron 1800+ powered Compaq desktop PC. It has better BIOS configuration screens- and the CPU is a 25W thermal design rather than the 65W Pentium D. The RAM from the old box fits, so now I have 2GB and after disabling all the unused hardware/interfaces such as Audio,I/O, etc. much faster boot and a bigger LED to tell me its on. Yay!

@phil.davis: [There is 64-bit installer for pfSense, so it will be easy to try that. [/quote] Are you sure the installer actually 64bit and not just the resulting OS that is installed?  Because I did download and have been testing with the AMD64 builds and nothing I have done works.  It might also just be a missing efiboot files,  I haven't have time to checkout the disc structure yet.

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? :(