Pfsense 2.3 and esxi 6 first time install
-
Thanks sorry I'm new to this
Do I have to manually put the Mac in esxi?
Thanks again
-
huh?? Dude look on the props of the nic you have assigned to your pfsense vm… What does it show for the mac??
Mine are manual set in pfsense vm, yes because it makes it very easy to know which is which ;) But they do not have to be.. Here look at my ubuntu vm, etc..
-
Thanks :)
The ones in esxi are totally different to the ones shown under em0 and em1 in pfsense
-
Well how can that possible be?? You have a vnic assigned to pfsense VM, the mac would match up – see my image with pfsense and what esxi shows. If your macs are not matching up then yeah not going to work... You have interfaces messed up?
You have looks like 5 nics in tha esxi host..
-
Really not sure I'll have a play around when I get back in, I have one port built into the motherboard and a 4 port pci-e Intel card so unless somethings going weird with that? The network connection on the mb is the one connecting into my switch and has the esxi management on the Intel card is the one connecting to my isp
-
Well dude I can tell you its never going to freaking work if the mac your VM shows is not what pfsense is showing for its interfaces.. Did you pass the nic through and pfsense is seeing the phsyical nic?
Pfsense is showing 00:0c:29 which is a typical vmware vnic mac… So what do you mean they are not matching up.. What does your pfsense VM show is the mac of the vnic, and what does pfsense vm when your on the console show for the mac?
Make sure you assign the correct em0, or em1 to the right vswitch lan or wan, etc..
-
Thanks no it's set to e1000d and I havnt set a pass thru
I will double check what Mac it's showing as
I added the vswitch in the tutorial for wan but my virgin media modem goes straight into my servers network card and not my hp switch do I need to configure anything extra for this
Thanks again it's much appreciated
-
thanks they do exist as you mentioned within vm, when i set wan to em0 it removes the lan option?
-
restarted everything and all is now working, thanks everyone for your help and support :-)
-
how is it working.. your screenshot of pfsense only shows a wan interface??
Doesn't pfsense default to 192.168.0/24 on its lan?? Be so long since used default on its lan not sure, I know it defaults to 192.168.0 or 192.168.1/24 on its lan.. But those are so common of a network I always change it.. I currently run 192.168.9/24 on pfsense lan..
-
It seemed to want to default to 192.168.1.1 restarted everything and changed it to 192.168.0.1 to Match my current setup power cycled everything again and it started working
If I changed the lan up range would I have to also change my switches up, esxi management to the different range?
-
does not matter what networks you use - but from your post there is on 1 interface and its wan interface.. What exactly are you doing with pfsense with 1 interface??
-
That's the problem I was having I could not get the wan to show along with the LAN when the wan was working it seemed to remove the lan after several restarts they both seemed to appear and the wan recognised my virgin media connection
-
so you have your wan and lan vswitches on different interfaces right? Your not connecting them into the same vswitch
Not sure what you were doing but you shouldn't have to reboot pfsense.
If you had same network on both sides of pfsense wan/lan its going to have problems
-
they were on seperate vswitches with different cards, really not sure what was going on, but they just seemed to spring into life again, hopefully it stays that way, i couldnt even ping the pfsense web gui, but could ping the esxi management interface
-
well your working now, and you have different networks on your wan than your lan right?
-
yes the wan was set to dhcp so it has picked up the 82.x.x.x range my isp provides does that sound okay?
one other strange issue I am having though is I have set the lan dhcp to hand out ip's between .150 and .254 however it doesn't seem to be obeying this and handed out any? any ideas? Thanks very much
-
post your dhcp settings… If your getting other my guess is you have some other dhcp server. Your dhcp client should be able to tell you what the IP of your dhcp server was..
-
it looks like its pointing to the right place, so not sure why the range isnt being taken into account
