hmmm - while I can understand why you can not ping pfsense wan IP from your current lan. Until you allow that on firewall rule that would be blocked. I don't understand why you can not ping your router ip 192.168.0.1 from pfsense diag tools? Or cmd line of pfsense via console access on esxi?
Can you post your interface status from pfsense for wan
Problem is -- I am headed out of town early tmrw morning.. Tell you what, let me grab 2.0.3 and add it real quick to my esxi host.. Give me a few minutes..
edit.. Ok downloaded pfSense-LiveCD-2.0.3-RELEASE-i386-20130412-1022.iso
Created a Vm.. put one interface in my lan vswitch, other in dmz vswitch - set its mac so I knew which one it was. Changed it too version 9 vm. Booted the CD.. clicked easy setup.
So it defaulted to dhcp on wan and got an IP in my lan
So then from that esxi console I changed its wan IP to be on static on my network 192.168.1.150, changed the lan network to 192.168.0.0/24 - this is via option 2 in that above screen
Now I did not set a gateway yet for wan, but it lets me ping IPs on my lan network
So now let me fire up vm on that dmz segment that gets IP via dhcp from pfsense dhcp. - brb
edit2: Ok its been like 5 minutes maybe..
So put a vm on the lan segment of pfsense vswitch so I could connect to it and finish the wizard
So its gets an IP from pfsense dhcp - but it can't go anywhere yet
So I fire up a browser and connect to pfsense - mine is 192.168.0.1 vs your 192.168.1.1 -- my normal lan is 192.168.1 vs 192.168.0 like you have so I just reversed them. And my current pfsense router is 192.168.1.253 vs your 192.168.0.1
So running through the wizard it asks me for dns for pfsense -- which is why I put in my current router (pfsense in my case) 192.168.1.253
It then asks me for gateway
Remember I had changed its IP from the esxi console to be static and on my network already -- see the early screeny
Now the wizard does some stuff
It will finish after a few seconds.. I then went to diag ping area and can ping google
And as you can see my vm can now ping google (internet access) connect to the lan side of my new vm pfsense behind another VM pfsense in my case vs your actual router can ping as well
So not sure what your doing wrong - are you not completing the wizard? So then I go in and change the firewall rules to allow access from my current lan (pfsense wan for web gui access) via my vm on the lan side of pfsense
And there you go I have wan gui access
So that was my 10 minute tutorial - I have to hit the road for trip at 5am.. I will be back on Monday - more than happy to help you figure out where your problem is. If need be you can let me remote in and we will get you fixed up! Hope this helps
From what you posted it looks correct from my quick look - but if your pfsense wan interface can not ping stuff on your current lan - then no its never going to work.. You need to be able to ping your router 192.168.0.1 from pfsense on 192.168.0.210 - if not, then nope never going to work.. So need to figure out what is not right.
So you can see my vswitches.. Here is where I brought up my pfsense 203 (pf203)
And the w7-new is the box I used to connect to pfsense I was setting up. The pfsense-vm which is my actual gateway router does have an interface in that vswitch - but its on a different segment