Installation: Unable to browse the Login Page
-
I'm used to XenServer. "Unplugging" NICs is problematic but it works great in general.
-
Well, I was just wondering if this guy was using something free and simple like vmplayer, which can make reaching your LAN address a pain.
-
Hard to say. People have enough trouble with pfSense in general, and that is not to fault pfSense at all. They lack a basic understanding of what is required to run a firewall. Then they toss a virtual environment in there and come here…
It gets tiresome....
-
I resemble that remark!
-
Well, I was just wondering if this guy was using something free and simple like vmplayer, which can make reaching your LAN address a pain.
Hi, yes I am currently using the Oracle VM Virtual Box to install PFsense. I am trying to test out how does all these works. Am I able to create a test environment using these free platforms? Regarding the plug-in and unplugging the cables, for my case i think is just enabling the "Network settings" from the VirtualBox settings correct?
-
To configure pfsense you will either need to have a virtual machine with a desktop and web browser on the same internal network as pfsense (resource heavy), or NAT to VM LAN (PITA), or disable firewall with pfctl -d command in the pfsense shell and then access via the wan address for initial setup. I assume this is just a learning experiment?
-
Another option is running playback enableallowallwan in menu option 12 then connecting to the WAN address if you have connectivity to that.
That's pretty much how I do all my lab work since all of the LAN side hosts for the testing devices are usually virtual as well. The VM lab "WAN" is actually downstream of my workstation on its own pfSense interface on my edge device.
-
Hi, can you all share with me do I need to do any configuration in order for me to browse the PFsense admin page on my local machine?
I am installing the PFsense on the VMware on the same PC.
-
Dear all, and I am keep getting this error when I try to load the page.
-
Go to your console for pfsense.
Open a shell.
Type pfctl -d
Type the ip for the wan interface in your browser.
Configure your pfsense -
Go to your console for pfsense.
Open a shell.
Type pfctl -d
Type the ip for the wan interface in your browser.
Configure your pfsenseHi Kejianshi, thanks for your reply. But when i typed in the command, it shows me pf: Command not found.
What should I do with it?
-
When pfsense boots, it shows you a list of choices. Select the number for "shell".
Once it is in the shell, type pfctl -d and hit enter.
If this isn't working, you are doing something very wrong.
-
When pfsense boots, it shows you a list of choices. Select the number for "shell".
Once it is in the shell, type pfctl -d and hit enter.
If this isn't working, you are doing something very wrong.
Ya its not working ….. any idea why? Is there anyway to do a repair?
-
I'd reinstall and try again.
-
I'd reinstall and try again.
I have tried twice. but still the same.
On the very first time, I am able to open it using Ubuntu vmware. But later I tried to configure to use my windows to browse the page, then all the configurations not working.
Not sure which part of the setting up or configuration not working well. Please advise.
-
Are you using the wan or address? is this a physical machine or a virtual machine? Is there another router involved?
-
Are you using the wan or address? is this a physical machine or a virtual machine? Is there another router involved?
I am using address. Its a virtual machine, no other router involve, only using local machine.
-
By the way, any configuration i need to do in order for my local browser can access the PFsense admin page?
-
No. You just need to be able to connect to the IP address of an interface that is passed by firewall rules. Normally this is LAN. You have received two suggstions above that will enable access on WAN (pfctl -d, and playback enableallowallwan.)
It is not pfSense. It is your virtual environment and how you have things structured.
-
I bet neither of the interfaces is bridged. Probably the wan should be bridged, not nat and not internal.
And since the WAN IP will be private, be sure to uncheck the "plock private" on interfaces for wan.
Keep banging away. You will get it.