Hyper-V / DHCP Issues

By aclarke_31
in Microsoft (Windows)

 Share

Recommended Posts

Mentor

aclarke_31

Posted
Posted (edited)

Heya everyone :),

 

Having some problems with Hyper-V.

 

As you can see via the diagram, I have created the subnet 10.1.1.1 on my internal network and I'm trying to create a new alternative internal subnet on 10.2.1.*.

 

DHCP is enabled on the LAN interfaces on each virtual router / pfsense installation, however everything in Hyper-V (My Virtual Machines) in the, what I want to be 10.2.1.* subnet, isn't getting a DHCP assigned address, despite me setting up the correct vSwitches on the HyperV host (Yea I've created a Internal LAN vSwitch that all my VM's get assigned to (with the exception of the pfSense installation which has two interfaces. One for internal network and one for external network)).

 

I'm stuck at the moment as even though I've created a 10.2.1.* subnet for my VM's, they,

 

        a). Get no DHCP Address from the pfSense Installation inside Hyper-V.

        b). Despite setting a 10.2.1.* IP to one of the VM's via fixed IP, they still do not ping anything past the pfSense installation inside Hyper-V. (I've checked to make sure that routable traffic can actually hit the pfSense install.

 

From a Virtual Machine inside Hyper-V I can ping 10.2.1.1 (pfSense LAN side interface), anything on 10.2.1.* and 10.1.1.201 (pfSense WAN side interface), but I cannot ping anything in the 10.1.1.* subnet (even though Hyper-V exists on 10.1.1.57 and vCenter 10.1.1.50).

 

The main problem is that no VM's are getting a DHCP assigned IP address, despite DHCP running in the right places.

 

Ummm..... HELP!!!!! Little out of my depth.......

 

Expert knowledge of networking and Hyper-V required for this issue.

 

Apologies to admin's if I've posted this in the wrong place.

 

Thanks anyone that's read this and happy to help.

 

 

hyperv_problems_02012022.png

Edited by aclarke_31
Notation changes
Link to comment
https://www.neowin.net/forum/topic/1414234-hyper-v-dhcp-issues/
Share on other sites
Experienced

Marujan

Posted
Posted (edited)

you made it too difficult for yourself

 

why you use 2 pfsesnse routers? make vlans instead

 

 

 

Grand Master

farmeunit

Posted
Posted

As mentioned by the last poster, why 2 pfSense installs?  

 

We use VMWare and our switches do the routing, but I create a vSwitch tied to an interface, then on the switch UNTAG the VLAN I want it on.  

 

I tried TAGGED VLANs and never could get it working, but I'm not an expert, either.  We are looking at letting our firewall handle routing at some point for settings up some inter-VLANs security policies, but right now it's our core switch.  I really need to set up a homelab, but haven't yet.

 

I can play with it a little later, but hopefully someone else can answer your question.

Mentor

aclarke_31

Posted
  • Author
Posted (edited)

Even if I take out the 2nd pfSense installation, none of my VM's get a DHCP assigned IP from the DHCP Server.

 

Any other recommendations at this point as something I could try?

 

I'll try removing the 2nd DHCP Server that's running on the 10.2.1.* subnet, but I'm sure when I tried this, none of my Hyper-V VM's got a DHCP assigned IP.

 

Marujan: Please explain how I would go about using VLANs for this to work? Thanks

 

Farmeunit: Thanks for the feedback. If you do happen to get this working, please let me know as it would be greatly appreciated. I'm doing something wrong with the configuration, but I can't for the life of me figure out what. Thank you.

 

Thank you for the feedback everyone, please keep feeding this as I would really like to get this fixed.

 

Thanks

Mentor

aclarke_31

Posted
  • Author
Posted (edited)

Even if I try taking out the 2nd pfSense installation and have the 1st pfSense installation handle the IP assignment, even setting this up doesn't allow the VM's to get a valid IP from pfSense installation 1.

 

After checking the configuration, I can manually assign an IP address to a VM on the 10.1.1.* subnet but not ping anything except the 10.1.1.57 (WAN side interface of the Hyper-V install)

 

For some reason, I'm just not getting any DHCP traffic through to the VM's in Hyper-V and I don't know WHY!

 

Totally open to suggestions / troubleshooting at this point guys.

 

If you can help I'd be very grateful.

 

Many thanks

Edited by aclarke_31
Notation changes
Mentor

aclarke_31

Posted
  • Author
Posted (edited)

As you can see on the enclosed picture, SRV-HYPERV is online (10.1.1.57) the VM inside the HyperV installation is not getting a DHCP assigned IP.

 

SRV-VCENTER is DHCP assigned an IP of (10.1.1.50), yet I cannot ping beyond the SRV-HYPERV installation,

 

2nd image (one in white) is of the VM machine not being manually assigned an IP of 10.1.1.101 and setting DHCP and DNS to be pfSense installation 1.

 

HELP! Thanks

 

 

 

hyperv_problems_02012022.png

 

 

vswitch_config_03012022.png

Edited by aclarke_31
Notation changes
Mentor

aclarke_31

Posted
  • Author
Posted

Sorry to keep adding to an existing thread but I'm just trying to track down the problem.

 

DHCP is reaching the WAN interface on SRV-HYPERV but the pfSense installation on 10.1.1.1 isn't responding with a DHCP address.

 

Makes me think I've configured something wrong on SRV-HYPERV, althought its picking up a DHCP lease from the pfSense install on 10.1.1.1.

 

I'm checking this through an installation of Wireshark on SRV-HYPERV. I can't attach a Wireshark dump on this site due to limitations of Neowin (shame)

 

If you can help with this guys, I'd be very greatful.

 

Thank you :)

Grand Master

+BudMan MVC

Posted
  • MVC
Posted
  On 03/01/2022 at 20:47, aclarke_31 said:

DHCP is reaching the WAN interface on SRV-HYPERV but the pfSense installation on 10.1.1.1 isn't responding with a DHCP address

Expand  

I am really confused at what your trying to accomplish here..

 

How would stuff behind your 2nd pfsense get dhcp from your 1st pfsense?  So are you using hyper-v or esxi?  I see vm vcenter. But subject says hyper-v

 

So your trying to get vms talking what, vms on your vmware talking to vms on your hyper-v?

 

How are they physically connected?  vlans work different on hyper-v vs vmware, if you want tags to be passed on vmware you have to set the ID to 4095 on the vswitch, etc.

 

I really don't get the want for multiple installs of pfsense, even if you running pfsense as vm on one your hosts, there is no need for another pfsense on some other host to be able to get to some network on the other host..

 

I would love nothing more to help you - but just at a loss to what your actually wanting to do.. But pfsense can only provide dhcp to devices connected to an L2 it has an interface on.  If your wanting your 2nd pfsense wan to get its IP from the 1st pfsense LAN - how exactly are they connected what is this common network, do you have a wire directly connected between the hosts?  Switch, is there any vlans envolved for this connection, etc.

Mentor

aclarke_31

Posted
  • Author
Posted (edited)

1). Hyper-V on top of ESXi

2). Want to get VM's on my HyperV installation talking to my VM's in my ESX-i Installation.

3). No Physical connection apart from the connection from the host server to the  physical router.

4). No longer multiple pfSense installation's, just the one. Had to try and make it more simple.

 

5). Basically I just want my VM's in Hyper-V to have internet access, but as it stands, I can't even get that at the moment.

 

Hopefully this is enough to start us. I'm always available on DM if you need me Budman.

 

SRV-VCENTER is just the name of a virtual machine running ESXi vCenter for my ESXi installation.

 

This is basically all under one physical server and one router.

 

 Cheers for your help 👍

 

 

Mentor

aclarke_31

Posted
  • Author
Posted (edited)

The long and short of it is I'm basically trying to install Exchange in a DataCenter version of Windows Server, however I'm unable to get LAN access / Internet Access through the HyperV installation on SRV-HYPERV (SRV-HYPERV is a virtualised DataCenter Server installation).

 

I want to achieve a virtualised Exchange installation, but have it running through Hyper-V rather than ESXi.

Mentor

aclarke_31

Posted
  • Author
Posted (edited)

Can someone just confirm if its because I'm using virtualised network adapter's in an already virtualised environment?

 

Do I need to use, or passthrough a physical NIC / port from the ESXi Install to the router / switch to try and get around this problem? - Just realised that I can't do this as I need nested virtualization on SRV-HYPERV to allow VM's to run inside a virtualized host.

 

I would hope that Windows would be able to cope with this but I could be wrong.

 

Thanks

Edited by aclarke_31
Grand Master

Brandon H Supervisor

Posted
  • Supervisor
Posted

might need to start from scratch and go through the network setup step by step. I know those two have been willing to do a remote session to help with that kind of thing when needed before. doesn't hurt to ask at least :)

Mentor

aclarke_31

Posted
  • Author
Posted

I'm willing to do anything Brandon to get it to work because I want to get an Exchange 2010 installation running on my home system but virtualised fully for scaleability.

 

Anything that the guys can do to help I'd be very very greatful for?

 

Would it be helpful to let you guys know what I'm working with so you can let me know if I'm just trying to achieve the impossible?

 

I was thinking its because I've virtualised my Hyper-V installation in DataCenter inside of ESXi.

 

This was the only thing I could think of that could be causing the problem because I'm using virtualized NIC's inside a virtualized installation.

 

Either way I'm at a bit of a loss at the moment and would really appreciated some help from somewhere.

 

I have Exchange 2010 Enterprise, Windows Server 2019, unlicenced version of Windows Server 2022 that I'm kinda working with at the moment and ESXi 7.0.2 (not patched to 7.0.2b yet)

 

Thank you :D

Mentor

aclarke_31

Posted
  • Author
Posted

Its not really the Exchange Server's that's giving me the problem @warwagon. Its the VM's inside HyperV inside ESXi that don't seem to be picking up a DHCP lease and I don't understand why.

 

If you could help to get to the bottom of this, it would be AMAZING!!! lol

 

Thank you guys :)

Grand Master

Brandon H Supervisor

Posted
  • Supervisor
Posted
  On 07/01/2022 at 17:04, warwagon said:

I'll let Budman tackle this one. I don't do much work at all with Exchange servers.

Expand  

sounds like Exchange is his end goal but the issue at hand is the DHCP setups for the virtual environments

Mentor

aclarke_31

Posted
  • Author
Posted

Thank you @warwagon for having a look for me.

 

Warwagon's had a good look and even he can't understand why its not working guys.

 

@BudMan , my saving grace, I hope you have your networking head free at some point to lend a hand because we both couldn't get to the bottom of it.

 

Thank you anyone else that can put some input in.

 

Thanks

Grand Master

+Warwagon MVC

Posted
  • MVC
Posted
  On 07/01/2022 at 17:09, Brandon H said:

sounds like Exchange is his end goal but the issue at hand is the DHCP setups for the virtual environments

Expand  

Just remotely connected in and we brainstormed for the last 3 hours over remote support and telegram. It looks like it should be working but it's not. So i've gone about as far as I can go.

 

Internet works just great inside server 2022 but just won't pass it onto any of the VM in hyper V .. I also look up the how do it in hyper V and everything looks to be configured correctly.

Grand Master

+BudMan MVC

Posted
  • MVC
Posted

This weekend is bad - week 18 of football, and I leading by 10 points for the pool for the season..  But sure during the week be happy to remote in and take a look see.  Only good thing with work from home, is I do seem to find more "play" time for stuff that interests me vs real life work ;) hehehe

 

Pretty sure we could find some time and take a look see.

 

Simple test, sniff on pfsense - if your not seeing the dhcp discover, then no its not going to work.

Mentor

aclarke_31

Posted
  • Author
Posted

YAY!!!!!! Thank you Slaughthus. That was the exact article I was looking for. Me and Warwagon couldn't get our heads round this last night, but after some serious investigation, you provided the answer. I couldn't figure out why it wasn't passing DHCP over, but forged transmits was the answer. :)

 

All my VM's are getting DHCP requests now from my 1 pfSense installation, which is AMAZING!

 

Thank you ever so much to @warwagon for spending the time with us last night trying to figure out why this wasn't working and thank you ever so much to @slaughterhus for his resolution article :)

 

We can close a ticket! HURRAY!

  • Circaflex, +Warwagon, CloudEngineer and 1 other
  • Like 4

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.