ESXi 4.0 and pfSense 1.2.3 RC3 gives strange results

fribert

Hi Guys

I'm running the pfSense on a ESXi 4.0.
First install was installed as a 32 bit linux, the nic's are called le0, le1 and le2.
After installing the vmware tools it says unmanaged like others have noted.

I discovered that there were a FreeBSD 32-bit type machine in the 'other' list if I choose type 7 system in ESXi.
So to optimize the setup, I wanted to set that up, instead of a generic linux.

The install itself goes fine.
I can configure a LAN, and I can access the LAN card nicely, no problems.
The nic's are called em0, em1 and em2.

Then I try to restore the config from the first install.

That seems to go fine, it asks me to reassign the nic's, as their names have changed.

After reboot it starts to download all the packages, and it works nicely, and finishes as it should.

BUT, and here's the problem, the LAN card doesn't respond to ping anymore???
I can not in any way connect to the LAN port.

I smell a bug somewhere ;D

Tidder

I have been running pfSense 1.2.3 on ESXi 4.0 for weeks now with no issues. I'm even using a total of 12 virtual nics currently. It sounds like there was something strange in your config file. What if you reloaded it fresh, then applied all your config settings manually rather than uploading a config file? It almost sounds like there is no longer rules to allow you to do anything on the lan.

Have you checked in the console if the NICs are assigned correctly and have the correct IP addresses?

Could very well be that the NICs are assigned incorrectly. Esp with a drastic change like that.

fribert

That was my sentiment as well, something going screwy with the update.
Especially because it works as a straight install.
What architecture are you using for pfSense?

frankies

I've installed Pfsense on Vmware Esxi too but I can't make my ADSL additional ip addresses work through the Virtual IP Addresses option. Is it a known bug? Or I am the only one who is facing this problem?

Thanks

heitor.lessa

I had some problemas too, but just with 1.2.3 version, now I´m using 1.2.2 w/ 200 users and works fine !

Try to change the version.

And remember, take snapshot and backup too ever.