New machine pf sense won't install
-
This is getting so frustrating I have been at this for hours. I have a hp compaq pro 6200 mt tower and when I install the latest version of PF it hangs at efi information in particular the "masks" step. I tried to install via cd and usb no luck. When I try the older version 2.3 it install then hangs at the "f1" screen and just keeps rebooting. I have been thorough the forms nothing is working. What could possibly cause this?
-
See Installation Troubleshooting here: https://doc.pfsense.org/index.php/Installing_pfSense
-
Also see: https://doc.pfsense.org/index.php/Boot_Troubleshooting
What install image are you trying exactly? What errors are you seeing exactly?
Steve
-
It would not give an error thats what made it so annoying. I was trying to install the 64 bit 2.4 image iso disk, and right when it begins to install when it starts to show the efi information, it would just freeze at "masks." I could not find anything in the support section about it. I then tried the older 2.3 version which installed =, but would reboot over and over at the "F1" part. Finally I installed 2.3 again this time with usb, and I unchecked "Packet mode" during the install and it worked. I do however, want the updated version but am now afraid of attempting it.
Another random issue I have is, 3 machines are connected to the box via an access point, all three have internet access, however one of them will not allow me to connect to the pf webconfig, the other two work just fine.
-
I had the same issue on my new pfSense box and updating the UEFI of the motherboard seemed to fix the issue.
It was also stuck at "masks" 99% of the time and only sometimes booted.The update fixed that issue permanently.
-
Can that one client ping pfSense? Connect via SSH?
Do you see anything blocked in the firewall log?
Are all three getting IPs via DHCP?Steve
-
Cannot ping, all three are dhcp through a router I am using as an access point. I tried to set the router to dhcp forward to allow pf sense to assign the ip's, however everything lost connection and I had to factory reset the router (dd-wrt fw). Nothing in the firewall log matching the time stamp of trying to login.
-
I had the same issue on my new pfSense box and updating the UEFI of the motherboard seemed to fix the issue.
It was also stuck at "masks" 99% of the time and only sometimes booted.The update fixed that issue permanently.
Thank you, I thought of that. When I looked up my machine, I could not come up with bios anywhere unfortunately.
-
If all three were getting IPs, gateways, subnets etc from the same DHCP server then they should have at least had the same settings.
If the dd-wrt device was still in router mode with NAT all three clients would appear identically to pfSense. There's no way it could distinguish them and block only one.
It looks like whatever was blocking that was in the dd-wrt device or in the client itself.It would be better to setup the dd-wrt router as an access point only. It may have a mode for that where the the WAN port is added to the LAN as a bridge. If not just disable DHCP and connect the link to pfSense to one of the LAN/switch ports.
https://doc.pfsense.org/index.php/Use_an_existing_wireless_router_with_pfSenseSteve
-
If all three were getting IPs, gateways, subnets etc from the same DHCP server then they should have at least had the same settings.
If the dd-wrt device was still in router mode with NAT all three clients would appear identically to pfSense. There's no way it could distinguish them and block only one.
It looks like whatever was blocking that was in the dd-wrt device or in the client itself.It would be better to setup the dd-wrt router as an access point only. It may have a mode for that where the the WAN port is added to the LAN as a bridge. If not just disable DHCP and connect the link to pfSense to one of the LAN/switch ports.
https://doc.pfsense.org/index.php/Use_an_existing_wireless_router_with_pfSenseSteve
That did it! Silly me, I had the cable plugged in the "internet" port on the router. When I switched it, dd-wrt automatically let pf take over dhcp, so now everything works. If only I could find out why I cannot install 3.4 now. :o
