New pfsense install
-
i attempted to install pfsense yesterday and i think i was somewhat successful.
the cpu i was using had 2 nics in it, so i decided to pop in the pfsense cd that i made, just the day before, and attempt the install.
when i popped in the disc, it loaded right up into the screen that prompts you with a 10 second countdown.
i think i pressed 1, boot pfense or something like that. i am at work and i dont remember the details.
it went through the auto negotiate with the nics and then pfsense booted up.
i setup the IP of the pfsense, configured the DHCP settings, and just kind of checked through some of the other prompts on the screen.
for whatever reason, it wasnt pulling the wan ip address, from my cable modem, and i had the second nic plugged into my switch, i could not get my other pc on the network to get an IP address from the pfsense box. so i decided a reboot on the pfense box would do the trick, since i did make changes to the lan ip and the DHCP settings.
well, when i rebooted and clicked option 1, i had to do the config again. i supposed i needed to save the config to a usb device?
is it better to actually install pfsense to the hard drive and then configure it how i want?
thanks for any help.
-
Once you boot the system you'll need to select 99 from the console to install to HD. I believe that pfSense will auto save the config to a USB key or floppy if it finds one, but I can't be sure.
-
Once you boot the system you'll need to select 99 from the console to install to HD. I believe that pfSense will auto save the config to a USB key or floppy if it finds one, but I can't be sure.
ok, so for starters, install to HD.
i can do that.
now, once installed to HD, does it still need a usb to save to or can it save to my hd?
after i install it to the HD, will getting the wan up be a little easier?
typically, what is the process of getting the pfsense to see the wan connection? i have ethernet going straight from cable modem to pfense box. would i need to power cycle my cable modem?
thanks for the info.
-
Can I suggest you RTFM - the Documentation Wiki includes installation tutorials.
Yes, if you install to HD it'll save the settings to the HD.
With Cable Modems you often have to power cycle them if you connect a different system to them.
-
@Cry:
Can I suggest you RTFM - the Documentation Wiki includes installation tutorials.
Yes, if you install to HD it'll save the settings to the HD.
With Cable Modems you often have to power cycle them if you connect a different system to them.
thanks, i will look into that.
typically, is the main setup done in the command mode and then do you guys like to configure the rest via the gui?
is the command part of pfense limited or can you do everything via command?
i prefer to do everything via the guy on another PC, however, i need to get to that part. haha
i am going to check out the guide now, thanks.
-
pfSense is designed to be entirely configured, after the initial install step (ie configuring the LAN and WAN interfaces) by the GUI. It is not intended to be managed by command line, and doing so is non-trivial (also known as, don't think about it ;)).
-
@Cry:
pfSense is designed to be entirely configured, after the initial install step (ie configuring the LAN and WAN interfaces) by the GUI. It is not intended to be managed by command line, and doing so is non-trivial (also known as, don't think about it ;)).
i started reading that guide.
thanks for that.
i think this will make sense once i actually install it on my drive instead of just running it off of the CD. i ran it off of the CD just to see if i could see the actual system before installing it. however, i dont know why i didnt just install it onto that current hd…
-
And i would recommend reading our new featured guide as well:
https://secmachine.com/wp/how-tos/pfsense-installation/
Your comments are welcome.
-
ok, i have clicked on so many links, i am just confused now.
haha….
i am pretty sure i have successfully installed it. it told me to take the CD out and reboot.
when it reboots, it just takes me to a screen where i can choose 1-14 titles pfsense console setup...
is that it as far as the install goes?
if so, there was nothing to it...
-
That sounds about right - your install is complete.
-
@Cry:
That sounds about right - your install is complete.
hmmm, ok.
well i set the ip address of the pfsense box to 192.168.1.2 and i didnt configure anything else.
when i changed the IP it asked me if i wanted to configure DHCP, i said no.
my computer has an ip of 192.168.1.105 and i try to get to the web gui of pfsense, by opening a browser and typing in 192.168.1.2 and it times out.
-
What subnet mask did you configure?
Did the PHY pull link? (as in are you using a crossover cable to connect the PC directly to the pfSense?) -
What subnet mask did you configure?
Did the PHY pull link? (as in are you using a crossover cable to connect the PC directly to the pfSense?)24 bit- 255.255.255.0
both computers are plugged into my switch.
-
Did you set that IP for your LAN or WAN interface - at this point you'll only be able to access it by the LAN interface.
-
@Cry:
Did you set that IP for your LAN or WAN interface - at this point you'll only be able to access it by the LAN interface.
lan
i dont have anything in the wan interface just yet.
-
anyone?
-
If you're paying for support you've got a justification for being impatient. People help you here because they want to. Bumping threads after 6 hours, that's a good way to annoy people and not get any help.
When you log on to the console, you should see the version and LAN IP. Exactly what version and LAN IP are displayed? When you log on, exactly what output do you get from ifconfig and netstat -rn?
-
@Cry:
If you're paying for support you've got a justification for being impatient. People help you here because they want to. Bumping threads after 6 hours, that's a good way to annoy people and not get any help.
When you log on to the console, you should see the version and LAN IP. Exactly what version and LAN IP are displayed? When you log on, exactly what output do you get from ifconfig and netstat -rn?
my apologies…you bring up a good point.
i guess i am just use to faster responses on other forums...then again, most of that stuff is not technology related, just general chat.
the info you need is below.
thanks again.
ver- 1.2.3-rc1-pfsense on pfsense
lan- re0- 192.168.1.5
do you want netstat -rn and ipconfig from a windows pc or from pfsense box?
-
pfSense.
-
@Cry:
pfSense.
ok, which option do i need to prompt to get to a cmd interface to try this?
i tried shell, but that didnt work, and i didnt know how to get to the main menu w/o rebooting.
-
Two ways:
-
SSH onto it
-
Via the local console - serial for embedded installs, keyboard and monitor for full installs
Then look at the screen and pick the option for a shell.
-
-
Try in your browser 192.168.1.5
well i set the ip address of the pfsense box to 192.168.1.2 and i didnt configure anything else.
lan- re0- 192.168.1.5
-
Try in your browser 192.168.1.5
well i set the ip address of the pfsense box to 192.168.1.2 and i didnt configure anything else.
lan- re0- 192.168.1.5
Cry- i will try your suggestion tomorrow, but i am unclear on it…
start pfsense, select the ssh option and type those commands in?
ch- putting that in the browser doesnt open the gui, i tried that after i got done installing pfsense.
thanks guys.
-
Given your state of confusion I'd suggest you use the local console. By that I mean sit at the keyboard and monitor connected to pfSense. Select the menu option for the shell and then type those commands in.
-
@Cry:
Given your state of confusion I'd suggest you use the local console. By that I mean sit at the keyboard and monitor connected to pfSense. Select the menu option for the shell and then type those commands in.
ok, i have a screen of text that i cant type here…
both with ifconfig and netstat -rn
how do i get back to the main menu from the shell?
-
Try in your browser 192.168.1.5
well i set the ip address of the pfsense box to 192.168.1.2 and i didnt configure anything else.
lan- re0- 192.168.1.5
Tom- my point is that it looks like you believe your lan address to be 192.168.1.2 yet your console reports it to you at 192.168.1.5…
Id just suggest you try 192.168.1.5 in a browser while you wait for a response from Cry Havok.
-
Try in your browser 192.168.1.5
well i set the ip address of the pfsense box to 192.168.1.2 and i didnt configure anything else.
lan- re0- 192.168.1.5
Tom- my point is that it looks like you believe your lan address to be 192.168.1.2 yet your console reports it to you at 192.168.1.5…
Id just suggest you try 192.168.1.5 in a browser while you wait for a response from Cry Havok.
my bad guys…
it was 192.168.1.2 when i ran it off the cd. when i installed it to my hard drive i set it to 192.168.1.5
i am sure right now it is 192.168.1.5, which doesn't work in a web browser.
thanks.
-
My other suggestion is that you inadvertently set your lan up on the opposite NIC.
You might try setting up the box to hand out dhcp and then let your computer request its address from the box.
-
Type exit to leave the shell.
At the top of the console screen, when you first log in, it lists your interfaces and IP addresses. Interfaces with a * next to them have a cable connected. Disconnect all but the LAN cable and see which interface has the * next to it.
-
@Cry:
Type exit to leave the shell.
At the top of the console screen, when you first log in, it lists your interfaces and IP addresses. Interfaces with a * next to them have a cable connected. Disconnect all but the LAN cable and see which interface has the * next to it.
thanks for the exit command.
only the LAN is plugged in and it doesn't have a * next to it.
i cant ping anything on my actual network.
-
Ok.
When you log in, what interfaces are listed? I'd expect you to see something like:
WAN* -> rl0 -> 192.168.1.2 LAN* -> re0 -> 192.168.3.4
Can you provide a list of all the interface types, their names and the IP addresses?
ETA: And what one does have a * next to it?
-
@Cry:
Ok.
When you log in, what interfaces are listed? I'd expect you to see something like:
WAN* -> rl0 -> 192.168.1.2 LAN* -> re0 -> 192.168.3.4
Can you provide a list of all the interface types, their names and the IP addresses?
ETA: And what one does have a * next to it?
it looks just like that, but w/o *
my wan is 0.0.0.0 dhcp
lan is 192.168.1.5 -
Then you have no network cables attached to a live interface. Either the NIC is bad, the device on the other end of the cable is bad or the cable is bad.
-
@Cry:
Then you have no network cables attached to a live interface. Either the NIC is bad, the device on the other end of the cable is bad or the cable is bad.
nope…windows XP pro was on this box before i wiped it to install pfsense.
not a big deal since it was a test box, but i browsed online with it every day. it is hooked up to a 16 port gigabit switch that i use for the rest of the PCs on my network.
and i did try a different port before writing this post. even though the port it was on before was the same one that i was using when XP was on the box.
-
Then the other possibility is that you're using hardware without support in FreeBSD. Unfortunately despite prompting you're still not providing the information asked for so it's proving impossible to help you.
-
@Cry:
Then the other possibility is that you're using hardware without support in FreeBSD. Unfortunately despite prompting you're still not providing the information asked for so it's proving impossible to help you.
what other information do you need?
i have tried my best to answer all of your questions so that you can help me get to the gui via the web.
i could not post the info you wanted because my screen was filled with information, the only way to get it to you would be to type it out letter by letter or snap a pic with my camera. however, i don't think that would help.
if i missed a step, something that you asked possibly, i apologize. i have no reason to not provide you guys with any info you might need to help me. well, i guess i could not provide some information, but that would only hurt me.
-
Take a photo if you have to. Helping you with partial information is impossible.
Let's see:
-
the output of ifconfig -a
-
a list of all physical interfaces on the system (or at least a count)
-