Who are these users, are they always the same?  Are they random guests?  What do they need to access while on this wifi?  Is it network resources that are of concern?  What hardware are they connecting to the network with?  Hardware you control or manage or their own? If you have a mix, then yeah multiple wifi networks that have different layers of access to your network or internet.. Would have a network that is from your devices that you manage that can be allowed to access your internal network stuff that they need to access, etc. Then you have a guest network that can use the internet - that would have not access to anything on your network, etc. Maybe you use eap-tls to auth to the normal wifi network, or some other eap that has user name and password even if just peap, etc.  Or sure a nice strong wpa2/aes with a good strong PSK - that maybe gets changed now and then because users leak it out, etc.  Then your guest could be something as simple wide open no auth, or maybe it has captive portal like a hotel, or maybe you use a PSK that is simple to remember and you hand out to your guests, etc.

Thanks now it is updating but i first got this error. –----- Auto upgrade aborted. Downloaded SHA256: 0683264e902d59f7190e71f582d66dbc01382e138d0e632f81dc04cbeb948a3d Needed SHA256: 1a87fd24a383624dd68aec94d100 and when i tried a couple of more times sometimes i got 2.3.1 and some times 2.3.2. but now it is installing 2.3.1.

That's the parallel port driver and should be doing nothing. I believe I remember some previous reports of it spinning on interrupt like that. See if you can disable any parallel ports in your BIOS.

aubrad04…thank you for the reply.  It fixed my issue as well.  Great catch!

From the earlier message it's having trouble reading the USB disk (installing from memstick?) If it's a USB 3 port or stick, try a USB 2 port/stick. It may just be that FreeBSD doesn't get along well with that particular piece of hardware.

Nevermind, was able to figure it out.

Thanks, I did sucessfully installed :)

Thanks, will go look at that … very much appreciated.  I thought it would have been somewhere but my search turned up nothing ...

local-service What does that have to do with resolving local hosts?  That has to do with if dnsmasq will answer you at all.. Accept DNS queries only from hosts whose address is on a local subnet, ie a subnet for which an interface exists on the server. This option only has effect if there are no –interface --except-interface, --listen-address or --auth-server options. local-service That did not change from 2.3 to 2.3.2, why would they have changed that??  It has always been that way.. Did you maybe change your interfaces from all to specific ones, or enable strict binding?  What IP do you hand out to your vpn users to use? I use the resolver, which has acl that you have to add your vpn tunnel networks too..  But when I get to work later I will switch over to the dnsforwarder and test.. leaving that config item in there, etc.

Ok, rebooted the machine and put it into safe mode and verbose. This time I'm getting the WARNING:/ like before Along with.  'Start_init: trying /sbin/init Help please.

I had some issues during my PFSense setup within Hyper-V because any online documentation seems to be out dated. However, I was finally able to get it working just fine now for last week or so. This is one of the guides I used. I'd recommend you skip the apart about using legacy network adaptors. That ended up being my problem, when I was using legacy I was getting very bad downspeeds and/or sometimes unable to connect to the web UI or even ping the gateway. Staying with the default adaptors worked great for me. https://knowledge.zomers.eu/pfsense/Pages/Install-pfSense-on-Windows-2008-Hyper-V-server.aspx I would also recommend that when you get to the section on assigning interfaces to the VM (before you start the PFSense install) that you actually statically assign the MAC addresses. This way you can not mix up which interface is WAN or LAN etc… Hope that helps ya.

@dennypage: I filed a ticket for this issue: https://redmine.pfsense.org/issues/6687 Thank you.  Sure hope someone can fix that.  Sure would be a big help.

I did it removing samba36.conf from /usr/local/etc/pkg/repos

PFBlockerNG 2.1.1_2 Memory Errors

Thanks for the tip. As I stated before there was no changes made, it's fresh out of the box config. However I figured out the problem. The documentation for setting up in Hyper V states to use legacy network adaptor settings. I changed it back from legacy to regular and it jumped back up in speeds. Everything is running fine now.

Try again from ssh or the console using option 13 or "pfSense-upgrade -d" from a shell, and before you start, run "pkg clean"

Right, so I gave up on my install completely, I have gone for a complete reinstall, I'm still not seeing consistent internet access though. What I have done: Tried two different versions of pfsense as clean installs on esxi host, no back up from config xml, set them both up from new. Initial version that exhibited problems 2.3.1 i386 - problems described in this thread. New versions tried: 2.2.6 x64 2.3.2 x64 Both new (clean) versions exhibit the same gateway issues. Known differences from my initial setup, both the 2.2.6 and 2.3.2 x64 versions seem to have DNS resolver enabled by default, I was originally using dns forwarder. I don't recall if this was something I changed originally, it would have been years ago if I did. Not sure if/how this affects my problems now. I don't know if I should go back to an even older version to check if that would work, but from by best memory 2.2.6 was working for me in my initial setup. So this is currently leading me to think this a setup issue of my making. No surprises there…! :o So, in the new versions I have installed I am seeing WAN Interface gets an IP no problems. WAN_DHCP gateway fluctuates between online and offline quite frequently and regularly, and hence internet access is affected inline with this. My system log seems to point to something weird going on with WAN, namely it repeats this error over and over again. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Can anyone explain what is going on here?? Is this a problem that I should fix?? My gateway logs are taken up with dpinger alerts that show the fluctuating internet access. See below. Aug 7 18:57:38 dpinger WAN_DHCP 176.26.X.X: Alarm latency 8826us stddev 9725us loss 21% Aug 7 18:58:08 dpinger WAN_DHCP 176.26.X.X: Alarm latency 1178329us stddev 6722886us loss 70% Aug 7 18:58:39 dpinger WAN_DHCP 176.26.X.X: Alarm latency 7930us stddev 2873us loss 53% Aug 7 18:59:08 dpinger WAN_DHCP 176.26.X.X: Clear latency 7733us stddev 2029us loss 5% Aug 7 19:00:50 dpinger WAN_DHCP 176.26.X.X: Alarm latency 7837us stddev 2265us loss 21% Aug 7 19:01:25 dpinger WAN_DHCP 176.26.X.X: Alarm latency 1800145us stddev 8209140us loss 81% Aug 7 19:01:57 dpinger WAN_DHCP 176.26.X.X: Alarm latency 7688us stddev 640us loss 50% Aug 7 19:02:27 dpinger WAN_DHCP 176.26.X.X: Clear latency 20475us stddev 44552us loss 7% Aug 7 19:13:26 dpinger WAN_DHCP 176.26.X.X: Alarm latency 9490us stddev 16525us loss 21% Aug 7 19:15:04 dpinger WAN_DHCP 176.26.X.X: Clear latency 83613us stddev 641992us loss 14% Aug 7 19:15:16 dpinger WAN_DHCP 176.26.X.X: Alarm latency 79299us stddev 671765us loss 21% Aug 7 19:15:55 dpinger WAN_DHCP 176.26.X.X: Alarm latency 1556632us stddev 8193464us loss 75% Aug 7 19:16:20 dpinger WAN_DHCP 176.26.X.X: Alarm latency 8150us stddev 2703us loss 60% Aug 7 19:16:54 dpinger WAN_DHCP 176.26.X.X: Clear latency 7864us stddev 1783us loss 5% Aug 7 19:18:58 dpinger WAN_DHCP 176.26.X.X: Alarm latency 7711us stddev 403us loss 22% Aug 7 19:19:30 dpinger WAN_DHCP 176.26.X.X: Alarm latency 2216698us stddev 8411963us loss 73% Aug 7 19:20:06 dpinger WAN_DHCP 176.26.X.X: Alarm latency 0us stddev 0us loss 100% Aug 7 19:20:09 dpinger WAN_DHCP 176.26.X.X: Alarm latency 35555248us stddev 1018363us loss 94% Aug 7 19:20:46 dpinger WAN_DHCP 176.26.X.X: Alarm latency 7738us stddev 641us loss 68% Aug 7 19:21:08 dpinger WAN_DHCP 176.26.X.X: Alarm latency 1045933us stddev 6229170us loss 68% Aug 7 19:21:40 dpinger WAN_DHCP 176.26.X.X: Alarm latency 11149us stddev 7093us loss 92% Aug 7 19:22:00 dpinger WAN_DHCP 176.26.X.X: Alarm latency 11225886us stddev 19425589us loss 89% Aug 7 19:22:26 dpinger WAN_DHCP 176.26.X.X: Alarm latency 7700us stddev 460us loss 59% Aug 7 19:22:59 dpinger WAN_DHCP 176.26.X.X: Clear latency 7673us stddev 507us loss 6% Aug 7 19:25:38 dpinger WAN_DHCP 176.26.X.X: Alarm latency 8322us stddev 2945us loss 22% Aug 7 19:26:09 dpinger WAN_DHCP 176.26.X.X: Alarm latency 1275590us stddev 6943279us loss 73% Aug 7 19:26:39 dpinger WAN_DHCP 176.26.X.X: Alarm latency 8116us stddev 2273us loss 51% Aug 7 19:27:08 dpinger WAN_DHCP 176.26.X.X: Clear latency 8017us stddev 2098us loss 5% Aug 7 19:33:26 dpinger WAN_DHCP 176.26.X.X: Alarm latency 8084us stddev 2627us loss 22% Aug 7 19:34:49 dpinger WAN_DHCP 176.26.X.X: Clear latency 7715us stddev 681us loss 5% That's all for this update I think, I'm happy to provide anything that would be of use to help diagnose this. Note the above log snippets are from the 2.3.2 x64 version. I figure I might as well use the latest version that I would prefer to continue with going forwards - even if it currently isn't working! Any suggestions or discussion welcomed!  :) rancid

Looks like a failed upgrade for some reason in the OP as the info posted indicates the kernel is still RELENG_2_3_0, not RELENG_2_3_2. See if there is anything interesting in /cf/conf/upgrade_log.txt

It probably isn't locked up there. At that point it switches over to displaying the pfSense startup console messages, but for some reason it cannot. It's possible there is something amiss with the console or terminal settings on the box at that point. By far the fastest and easiest way to recover is to reinstall and restore your configuration. If you don't have a backup, use the "rescue config.xml" option in the installer – multiple times if it fails the first try -- and you'll be back up in a few minutes. If you haven't yet registered your firewall, do so and/or login to https://portal.pfsense.org/ and you should have a link to the factory firmware for that unit. If your support expired, just grab the ADI install image from pfsense.org for 2.3.2 and do the same.