Noob question for vmnic
-
Should I have 2 physical nic?
-
Should I have 2 physical nic?
If you don't, you are going to have use VLANs to separate the WAN and LAN traffic on the same physical NIC.
As it says in the tutorial:
Assuming you are just working with just two NICs in your ESXi host…
Now we need to link the second physical NIC (vmnic1), to a new vSwitch.
-
Yeah, I just have one. Considering the image attached, what do you suggest? and thank you for your help :)
-
Buy another NIC. Get an Intel one, if you can.
It will probably cost you a lot less than a VLAN-capable switch and will certainly be easier to configure (as described in the tutorial).
-
Well, what are you trying to do? Or, more importantly, what do you want pfSense to do for you?
If you want this pfSense virtual machine to be the router for your organization/location, then, yes, you're either going to need another physical port or a VLAN capable switch.
If you're just playing around to see what it does and/or just need it to filter for some virtual machines that you want to sit "behind" the pfSense VM, then you create a new vSwitch with no external physical NICs, connect the "LAN" side of your pfSense VM to it and the WAN side to the vSwitch with the physical NIC. Just be careful not to accidentally reverse it, then you may end up with another DHCP source on your regular LAN.
-
Thank you guys actually I need to:
1- Block some ports such as 25 on all vms.
2- Currently all vms are connected to vmnetwork with static ips, I want to give each vm a local ip and set static ip within pfsense. -
Thank you guys actually I need to:
1- Block some ports such as 25 on all vms.
2- Currently all vms are connected to vmnetwork with static ips, I want to give each vm a local ip and set static ip within pfsense.Great, do my last paragraph. If you need deeper instruction, let us know. You may need to be slightly versed in 1:1 NAT, otherwise, it shouldn't be difficult if you're familiar with ESX(i) and standard firewall/router practices.
-
Hmm, may I have you online in teamviewer?
-
Hmm, may I have you online in teamviewer?
Not for free ;)
Actually, not really, I wouldn't really be up for it even if I was getting paid, but that's what you should be looking for, a vendor/consultant. If you're not up for learning both ESXi and pfSense from the ground up (and/or standard router/firewall practices) you should have a vendor/consultant work this out with you. Otherwise, you're going to get it working, but have no clue what to do when something needs to get changed or go wrong. A vendor can either show you what you need to know or be on the ready to help you.
BTW, I purposely said "when", not "if" for a reason.
pfSense is a very capable platform that is very capable of enterprise level stability and performance, but you (or someone easily accessible and responsive) still need to know what it's doing for you before you simply plug it in and start depending on it.
I mean, if you're blocking port 25 I presume you're blocking email, which means these are not virtual machines you have full control of? And if someone else has "control" of them, then they presumably depend on you to keep them working.
-
I understand, I did not want it for free :P
I could not find a source to learn more, I am stuck with this vnic issue :(