ESXi Won't boot PfSense /w passthrough
-
so the physical stops working? Your setup is not a viable option as you posted so its hard for me to speculate what could be the problem
So your picture pfsense doesn't do anything.. Is there a physical switch that connects vmnic0 and 3? What does vmnic2 connect too?
-
I think your misunderstanding me. My set-up works fine…..for 30-60 minutes. Right now I'm just trying to get PfSense working at all. So for testing purposes PfSense's LAN port connects directly to a dell laptop (192.168.1.5), WAN port connects directly to cable modem.
Whats not viable about it? I will definitely switch things up once I get it working and have it take over routing from my Asus router.
my picture doesnt show that I plan on connectting a gigabit switch to PfSense's LAN port (and then a wifi access point to the switch). This is how I plan to connect all my stuff to the internet. I realise right now none of my VM's are routing through PfSense. This is b/c I can't keep PfSense working and they need internet. So they are hooked into my asus router for now.
vmnic3 will eventually connect to real switch, right now dell laptop is connected. Right now vmnic2 unused.
-
your vms are not connected to the pfsense lan network - unless you have some physical switch connecting those physical nics? Makes no sense to go from virtual to physical, back in physical to virtual again. Connect your VMs to the pfsense lan vswitch.
So maybe this helps I added part of my physical network and how it connects to the esxi host nics
-
your vms are not connected to the pfsense lan network - unless you have some physical switch connecting those physical nics?
So maybe this helps I added part of my physical network and how it connects to the esxi host nics
I think you might have missed my previous post were I explained my setup a little better.
@mysongranhills:I think your misunderstanding me. My set-up works fine…..for 30-60 minutes. Right now I'm just trying to get PfSense working at all. So for testing purposes PfSense's LAN port connects directly to a dell laptop (192.168.1.5), WAN port connects directly to cable modem.
Whats not viable about it? I will definitely switch things up once I get it working and have it take over routing from my Asus router.
my picture doesnt show that I plan on connectting a gigabit switch to PfSense's LAN port (and then a wifi access point to the switch). This is how I plan to connect all my stuff to the internet. I realise right now none of my VM's are routing through PfSense. This is b/c I can't keep PfSense working and they need internet. So they are hooked into my asus router for now.
vmnic3 will eventually connect to real switch, right now dell laptop is connected. Right now vmnic2 unused.
Does that make sense?
-
ah ok – so it works for 30 60 mins and then what errors do you get? You just loose your wan connection?
-
ah ok – so it works for 30 60 mins and then what errors do you get? You just loose your wan connection?
Pretty much. No errors in PfSense VM console still shows LAN IP as 192.168.1.1 WAN shows no ip and pings from 192.168.1.5 to 192.168.1.1 come back as timed out or destination unreachable. When 5 minutes earlier WAN had IP pings to LAN int. came back <1ms. Nothing done in PfSense other then boot it up.
-
Does any one know what logs I can check and what I should be looking for? Is this problem I'm having not that common?
-
you can look in pfsense system log, clearly it would report loss of wan IP.. But seems more like problem with your esxi box if you can not ping the lan IP? Does esxi show the nics active.
-
I haven't checked PfSense logs yet b/c I now believe it to be a ESXi issue. Once all the connections dropped I checked the vSwitch and it shows the physical NICs as disconnected for LAN and WAN vSwitches. NIC lights still blinking and laptop still shows connected on ethernet.
Any idea what could be causing this?
-
This is suppose to be only have upgrade adding, etc.. but you could try this
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2019871
What specific build of esxi are you running. Current build is 2143827 and was just released the other day.
I would also check your logs, the logs are in /var/log – enable shell on your esxi host and check them out
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2032076
Location of ESXi 5.1 and 5.5 log files (2032076) -
This is suppose to be only have upgrade adding, etc.. but you could try this
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2019871
What specific build of esxi are you running. Current build is 2143827 and was just released the other day.
I would also check your logs, the logs are in /var/log – enable shell on your esxi host and check them out
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2032076
Location of ESXi 5.1 and 5.5 log files (2032076)Thx. I think I'm on build 16xxxxx. Will update to latest build tonight when I get home and try moving NIC to another PCI-E slot. Could this be a bad NIC ?
Worst case scenario can I use my unused onboard NIC port for WAN and just add use existing VM network for Pfsense LAN?
-
Build 1623387? That is Update 1, way back in March.. Yeah I would update lots of changes and fixes and drivers updated, etc.