New pfsense install
-
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.4Can 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.4Can 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)
-
