ESXI WAN IP

[Alme55]

Hello guys,

Please bare with me as I explain my issue.

I have a dedicated server which came with ESXI 6.5 pre-installed. There is just one IP dedicated to this, the management IP:  62.121.90.xx/27 from where I can log to ESXI. This instance had just one NIC installed at this IP. No NAT. I asked from my hosting provider to issue me a second IP which is of 83.159.147.XXX/26. What I want to do is the following:

pfSense with two  network adapters one WAN where I can connect the internet and the second one I would like to use internally for Nating with other vms.

I have created the following:

Problem is that when I assign the new IP (83.159.147.XXX) to the WAN interface of pfSense I am not able to reach internet.

Any ideas what I'm doing wrong?

[IT_pilot]

Where is NICK connected?

Click here, what shows?

[Alme55]

Thank you for your reply. Here is what it shows:

[IT_pilot]

You do not have VLANs on cisco.

But pointed VLAN on Port Group "WAN"

You need at least two VLANs.

I think you should still read An Introduction to vSphere Networking: vSwitch & VLAN

Although in your case it's easier to assign a management IP 83.159.147.XXX and VLAN ID 0 (WAN VLAN ID 0)

[Alme55]

Hello,

Thank you for your answer. I read the article your shared carefully but I am still not able to understand your answer. Can you please elaborate a little bit on that?

[a_p_]

The two IP addresses you got from your provider are from two different subnets. Did your provider give you instructions on how to configure the ESXi host's network in regards of e.g. VLAN IDs, or did he provide/add a second vmnic (uplink) for the second network?

André

[Alme55]

Hello. No information was provided by the host. I raise a ticket and they recommended me to come to this forum since esxi networking is out of the support scope. In the past I have always been able to work on hosts where nat was already in place hence did not have to face such issues. Also there appear to be two physical NICs on my host: vmnic1 which is the one you see on the photos above and also vmic0 which says Link down.

But if we forget about the second IP for the moment, even with just one IP allocated to the ESXI management itself, how would I achieve my goal of having even a single machine connected to internet?

[IT_pilot]

Without a connection scheme (including physical equipment) and a detailed description, it is difficult to specifically answer something.

It seems to me that your whole architecture is not right.

For example, you still have not answered why you have a WAN VLAN ID 1. You yourself specified ID "1"?

P.S.

"But if we forget about the second IP for the moment, even with just one IP allocated to the ESXI management itself, how would I achieve my goal of having even a single machine connected to internet?"- No. Through the management network, or rather through the IP dedicated to the ESXi, you do not connect the VM.

Virtual machine port group and VMkernel port can be in the same subnet. But at the same time, another IP address is needed for the VM.

My advice is based only on guesswork.

You can get one more IP 83.159.147.XXX/26 for VMkernel. And write VLAN ID 0 for WAN. But I'm not sure that without setting up a physical port it will all work.

[Alme55]

Hello,

WAN VLAN ID 1 was added by me in an attempt of trying things out. I have removed it now so you can ignore it.

Lets start with a fresh install:

I received the ESXI 6.5 with the management IP: 62.121.90.xx

By default this IP is assigned to vmnic1 which also hast vSwitch0 attached with the following ports:
VMkernel Port - Management Network with vmk0: 62.121.90.xx 

Vm Network

I would like to create one VM within this ESXI and be able to reach the internet. What network adapter do I select? Do I have to create a new one? After that, since there is no DHCP and ESXI does not support NAT what IP do I assign to this new machine to be able to route properly and reach out?

Thank you in advance for your time.

[IT_pilot]

without a connection scheme, I have only guesswork that you do not make it clear.

Did you try to put VLAN ID 0 on Vm Network (Virtual machine port group "WAN")?