[solved]First install - Dhcp works - Can't ping Pfsense or reach webconfigurator

schiedamnees

I have the following situation:

Wireless
Modem (router) ->
Firewall (pfsense) -> Switch -> PC & MAC

Modem ip 192.168.2.1 Dhcp from 192.168.2.1 - 192.168.2.30 (subnetmask 255.255.255.0)
Pfsense WAN ip 192.168.2.8
LAN ip 192.168.1.1 Dhcp from 192.168.1.2 - 192.168.1.10 (subnetmask 255.255.255.0)

Ping pfsense to pc (example 192.168.1.5) are ok
Ping pc to pfsense doesn't work.

And i can't reach the webconfigurator from wan or lan side.

I did a clean install on my machine

My knowledge of networking and stuff isn't that good but i got pfsense working before (in an other setup) and this is a pretty straight forward (testing) setup i would guess.

And i searched the forum but couldn't get any further…

wallabybob

@schiedamnees:

Ping pc to pfsense doesn't work.

ping by name? ping by IP address? What is the reported error message?

schiedamnees

it was ping bij ip adres.. trough my make and i tought it gave no route? i will have try again?

wallabybob

I need more information to work with. Please provide the ping command and error response. If the PC is a windows PC please provide the complete output of the following command typed into a Command Prompt box: ipconfig /all

schiedamnees

Ok, I can't check it immediately because i have to work but tonight i wil try to ping from a pc and mac and on the pc i wil show the ipconfig /all

Any more i have figure out? to get it clear for you guys?

thnx

wallabybob

There are many possible causes for what you describe. It might take a few iterations of you providing more information and then being asked further questions before the particular cause applying to your situation can be identified.

The current outstanding questions are to see if your PC has the correct DNS and default route.

Gertjan

On a 'default' install you could even ommit to hook up the 'WAN' of the pfsense box when setting up.

Just a "LAN" nic with a switch on it. On this switch you hook up your PC (like this you won't get bugged by crossed network cables - the switch will auto-sense everything).
When initial setup is done (nic's on pfsense are assigned = LAN, WAN, Opt1, etc. - IP LAN pfsense = 192.168.1.1 - DHCP on "LAN" is activated) your PC "LAN" should acquire an IP (with mask and gateway, which is pfsense).

Now, your PC can ping the pfsense box, and better yet, you could do browse to the web configurator.

In your case I suspect that the link between nic LAN (pfsense) and your PC is not ok.

Btw : when I login into pfsense, I have this :
*** Welcome to pfSense 1.2.3-RELEASE-pfSense on pfsense ***
WAN* -> sis0 -> 90.50.127.126(PPPoE)
LAN* -> fxp0 -> 192.168.1.1
OPT1(Wifi)* -> sis1 -> 192.168.2.1
OPT2(DMZ)* -> sis2 -> 192.168.4.1

Btw : I’m not using DHCP (client) on my WAN nic, it’s PPPoE because I prefer to have the real Internet IP on my pfsense box – gives me less latency and the “router behind router” concept is also harder to handle.

schiedamnees

This is really embarrasing..

it was just an broken nic… so i bought a new one and it works like charm!

What confiused me was the fact that i could ping from pfsense to my pc but not the other way around but what wireshark told me that the wan interface was pinging me... so i switched the network cables... en i could go to the network interface!!

Thnx!