Problems installing and problems
First off I want to say hello to everyone…. Hello!
I`m trying to makea virtual lab to play around with just to get some server 2012 expirence. Around oct I had a virtual lab setup and it worked fine.
m having problems seting this lab back up but ive just notice a lot of errors going on during install. My first error that i see talks a bout this durin g installation
It runs fine and I select 1 and it starts going through the proccess.. Then right before I go to hit the I key I see this
Starting device manger....Pfscl: count not find server
...pfsct: could not find server..
everything above and below checks ok..
Then I press I and install fine..
Then when reboting I take cd out which sometimes it gives me a unmount errror but then it goes through the process and I hit f1. Sometimes it jus stalls here or other time its runns and gives me this error half way done
Fatal trap 12: page fault
while in kernal
Fault code superviso rread page not present.
I go to set my router up and server 08 and 12 have no internet access but I think it due to errors.
My network is as follow
Verzion router/w to box running virtual box (pfsense)
My machine ip is 192.168.1.5
pfsense is givng me when i can make it there.
192.168.1.15 (dchp) em0
I`m seving the server 192.168.1.10 255.255.255 subnet 192.168.1.1 gateway and dns for not and there is no internet connecting.
PFsense can png but my server can not ping anything..
BTW using both 32bit and 64 bit versions of pfsense i`ve tried versions 2 and up
You can't have the same subnet in two places with any firewall or router, make LAN or WAN something other than 192.168.1.x.
yikes forgot about that.
Ok wan is now 10.1.10.1
I can ping router from server and router can ping server but i still cant get into the internet.. any ideas
is your modem set to 10.1.10.x subnet?
did you gave gateway information to pfsense or are you using dhcp with wan side?
my modem is giving out 192.168.1.5 to my host computer
I set my wan on pfesense to 10.1.10.1 ad the lan to 192.168.2.1
nothing semed to work..
My Actual Lan in my hous is 192.168.1.x/24
I could careless what my virtual lab ip is.. I`m banging my head agaist the desk at this point. I dont remember it being so hard last time haha..
**** ok.. when setting reinstalling the wan is auto set to 192.168.1.16(DCPH)
I set the lan to 10.1.10.1
so I got
In this setup I can ping my 10.1.10.1, 192.168.1.1, 192.168.1.16, other devices in the house. But my virtual server is at 10.1.10.10/24 can not be pinged. No internet access as well.. PLEASE HELP.
Is there a setting in my actual ISP router that i need to change maybe?
ok i messd up on my lest post…
From the server 10.1.10.10 I can ping the pfsense lan and wan. I can ping my ISP router and my host computer...
I cant however ping yahoo.com
I also can not ping server to server or machine to server on the lan(pfsense) Example
Server 2012 10.1.10.10 can not ping server 2008 10.1.10.20 etc
Both can ping 10.1.10.1, 192.168.1.18, etc
wow i need to proof read my posts before posting them.. Sorry All
So since I was able to ping everything but not ping across the LAN (EM1) I figured it was something wrong with it..
I went into the em1 websetting and checked off block private networks and block bogon networks.. On both the wan and the lan.. One of those worked because I can now ping acroos em1 and I have internet acess. Can anyone tell me why? I do not rememeber doing this before?
Also.. Since i`m stil la newbie to this am I opening up an attack on my computer? Or is it safe since its all virtual?
em1 is your LAN interface, yes?
It has an IP of 10.1.10.1/24 which is inside the RFC1918 private IPv4 address space. Hence if you have 'block private networks' checked pfSense will block packets initiating connections coming from the LAN subnet.
You are not opening anything to attack by unchecking these on your LAN interface. By unchecking these on WAN you are no longer specifically blocking these things on that interface. However you are still not opening up the WAN interface to packets from the WAN side because everything is blocked by default anyway. You would have to put in specific allow rules on WAN to open it. In your case the WAN interface is in a private network so you probably should have it unchecked.