Massively late reply…... Still looks like they just don't send you an IP address so it just keeps asking. No clue what that could be be.  :-\ Steve

That type of panic is due to a filesystem issue. You can either boot to single user mode and run "fsck -y /" a few times and then reboot, or you can reinstall from a USB memstick with a pfSense ADI installer image. If you need help with either of those tasks, drop a line to our support team and they can get you more specific instructions.

Hi Guys, I tried to run this command but heres what I got rm: /tmp/radiusd_start.lock: No such file or directory any ideas? Thanks

note that your interface name on that hardware may not be igb0, so make sure it is whatever the correct hardware interface name should be before saving.

Tried with another adapter, this time USB2 (the other was USB3). Now the system survives reboots. I will check and let you know. Best regards Kostas

Not enough information to say why. You'll need to look at the logs and describe in much more detail exactly how the clients are failing. The default configuration has unbound configured to use DNSSEC, crypto operations require an updated and accurate clock, so that could be part of it. I have an ALIX 2D3 here as well running 2.3.4 but it doesn't have any problems even with a default configuration with unbound and DNSSEC. It's possible there is something about your particular environment which is preventing it from working.

Thanks for getting back to me so quickly… The Frontier tech said he could not bridge the modem that I have it being DSL and Arris type...I was finally able to get on the pfS setup access areas to start configuration and checked the loop back and network intrusions but never made it past any other screens to configure anything else, will do today. Their router-modem did let me create rules and port forwarding but it did not help with the normal operation and pass through of signal through my access gateway, still red and yellow lights so I know it is being throttled somewhere..( I will try and reinstall pfS to see if maybe something was missed, although all packages installed correctly and it worked with my Charter cable modem-router I bought at Walmart)... NAT could not be changed on my end EVEN BY THE TECH GUY HERE NOW...they say Geek Squad OR THE HIGH PRICE BUSINESS TECHS would have to go into the hidden pages and reset NAT etc... I was hoping a work around was known I could do in Arris setup access area page(s) I'm allowed in, would another over the counter or brand DSL router-modem allow me to change NAT etc...  Thanks for your time and efforts too!

That is great I will look into doing that. The box virtual so we were able to revert back to a snapshot as I wasn't sure what was causing the issue and it has 2GB allocated to it. I will attempt it through the console. Thanks for the input

Search for WebPorts in: /tmp/rules.debug /cf/conf/config.xml The alias type is "port" and its defined name is: "Web Servers" There is some confusion there - am expecting you to have a normal IP alias WebServers and a port alias WebPorts. Post screenshots of the alias edit page(s) and the related rule so we can try and understand what might be happening.

it's probably just the usbmodeswitch is not updated yet to work on your usb modem. you can try sending a AT command on the huawei modem to set it as a modem mode only instead of hybrid mode (eg CD+Memstick >> Drivers and dashboard detected to be installed >> CD+Memstick+Data).

It will probably still need internet if there are any packages involved at all.

Thank You John for responding!  :)

Judging by that last error, the disk is failing or otherwise has a problem being written. Could be a cable or controller, but more often than not it's the disk itself.

You can upgrade in one step. Look over the release notes and upgrade guide, but if you're in a VM then the risk is minimal. 1. Take a config backup 2. Snapshot the VM 3. Remove ALL packages 4. Upgrade to the current version 5. Add packages back 6. Snapshot the VM again 7. Take another config backup Changes to things in the base system are handled automatically by upgrade code. You shouldn't have to worry about much of anything related to Captive Portal or DNS coming from 2.2.x. Maybe you might have to add a zone parameter if you have custom captive portal html but there are plenty of references around to check that. If you had the DNS Forwarder active before, it will still be active on the current version. That didn't change for upgrades, the default changed for new users. (And it changed for 2.2, not 2.3, so you're already past that).