What a big hot pile of mess. I am trying to get VM's to work within a fake 192.168.0.0/16 routed to the internet via NAT to my normal internal LAN.
I have got almost the entire way there but I am failing to cross the finish line.
Here is what I have done.
- Created a Logical Network for my Front End
- Created a IP Pool with Gateway defined for my Frontend Logical Network (this is my normal 10.x.x.x real network)
- Created a Logical Network for my Backend
- Created a IP Pool with Gateway defined for my Backend Logical Network which I just used a random subnet space (172.16.99.0/24) and made the gateway .1 (total guess on this one)
- Created a Logical Switch that points at a port profile
- The port profile has both Logical Networks for frontend and backend in it and network virtalization is enabled
- Spun up a Windows Server 2012 R2 box, installed DirectAccess and VPN, Routing, and Remote Access module for PS
- On the Gateway box I ran Install-RemoteAccess -MultiTenancy
- Added the gateway to VMM using this connection string: VMHost=<host4gateway>;GatewayVM=<HyperVNameofGateway>;BackendSwitch=<mylogicalswitch>
- Gateway Test under provider passed
- Edited gateway's connectivity tab enabling front end to front end and backend to backend
- Created a VMNetwork using backend Logical network, isolated, added fake 192.168.0.0/16 subnet, then Connected directly to an addtional logical network, NAT for new Gateway
- Created an IPPool matching the VMSubnet with gateway of .1
- Finally assigned to a VM and tested.
The VM can ping 192.168.0.1 but it can not go past it.
Below is a dump of HNVDiagnositics, however since I dont run a cluster some of it just bombs out but there is more detail in it at least.
Found HNV VM Connected to VMNetwork :VMSubnet found : VMSubnet-Virtual-192.168.0.0-16 192.168.0.0/16
Gateway Subnet : 10.254.254.0/29
Found HNV VM Connected to Gateway : Gateway-ALVHGWW01
Gateway Address : 10.254.254.2
Getting Gateway Configuration for Gateway-ALVHGWW01
<no cluster error>
Validating Provider Address configuration for 172.16.99.10
Gateway PA address 172.16.99.10 is allocated to some other object and is expected to be assigned to NetworkService Gateway-ALVHGWW01
<no cluster error>
Calculating Lookup records for VMNetwork : VMNet_VirtualNetwork_Isolated
Calculating Lookup records for VMNetwork : VMNet_VirtualNetwork_Isolated VMSubnet : VMSubnet-Virtual-192.168.0.0-16
Calculating Lookup records for VMNetwork : VMNet_VirtualNetwork_Isolated for gateway
Expected lookup records on the host alvpocw91.domain.local
CustomerAddressMacAddressProviderAddressVirtualSubnetID
-------------------------------------------------------
192.168.0.101001DD8B71C0112875532
10.254.254.2001DD8B71C04172.16.99.10
192.168.0.11.1.1.112875532
192.0.2.25312875532
Found lookup records on the host alvpocw91.domain.local
CustomerAddressMacAddressProviderAddressVirtualSubnetID
-------------------------------------------------------
192.0.2.2531234567890ab172.16.99.1012875532
192.168.0.1005008e86b4c1.1.1.112875532
10.254.254.2001dd8b71c04172.16.99.1012877863
192.168.0.101001dd8b71c01172.16.99.1012875532
Matching calcuated lookup records against lookup records in host
Lookup records matching in host
Calculating Route records for VMNetwork : VMNet_VirtualNetwork_Isolated VMSubnet : VMSubnet-Virtual-192.168.0.0-16
Expected Route records on the host alvpocw91.domain.local
DestinationPrefix NextHop VirtualSubnetID RoutingDomainID
----------------- ------- --------------- ---------------
192.168.0.0/16 0.0.0.0 12875532 {9c491794-e169-4f1c-a0b0-8404462ce71d}
0.0.0.0/0 10.254.254.2 {9c491794-e169-4f1c-a0b0-8404462ce71d}
Found Route records on the host alvpocw91.domain.local
DestinationPrefix NextHop VirtualSubnetID RoutingDomainID
----------------- ------- --------------- ---------------
192.168.0.0/16 0.0.0.0 12875532 {9C491794-E169-4F1C-A0B0-8404462CE71D}
0.0.0.0/0 10.254.254.2 12877863 {9C491794-E169-4F1C-A0B0-8404462CE71D}
Matching calcuated Route records against Route records in host
Route records matching in host
Calculating Provider Address for VMNetwork : VMNet_VirtualNetwork_Isolated VMSubnet : VMSubnet-Virtual-192.168.0.0-16
Expected provider addresses on the host alvpocw91.domain.local
ProviderAddress PrefixLength VlanID ManagedByCluster
--------------- ------------ ------ ----------------
172.16.99.10 24 3051 False
Found Provider Addresses on the host alvpocw91.domain.local
ProviderAddress PrefixLength VlanID ManagedByCluster
--------------- ------------ ------ ----------------
172.16.99.10 24 3051 False
Matching calcuated Provider Addresses against Provider Addresses in host
Provider Records matching in host
Calculating Provider Routes for VMNetwork : VMNet_VirtualNetwork_Isolated VMSubnet : VMSubnet-Virtual-192.168.0.0-16
Expected provider Routes on the host alvpocw91.domain.local
Found Provider Routes on the host alvpocw91.domain.local
Matching calcuated Route records against Route records in host
Provider routes matching in host
Validating Policies on gateway host
Calculating Lookup records for VMNetwork : VMNet_VirtualNetwork_Isolated VMSubnet : VMSubnet-Virtual-192.168.0.0-16
Running Ping test for VM Win7TestClient from 192.168.0.101 to 10.254.254.2
Ping Failed
Running PA ping from 172.16.99.10 to 172.16.99.10
Successful pings 4
Pinging 172.16.99.10 from 172.16.99.10 with 32 bytes of data:
Reply from 172.16.99.10: bytes=32 time<1ms TTL=128
Reply from 172.16.99.10: bytes=32 time<1ms TTL=128
Reply from 172.16.99.10: bytes=32 time<1ms TTL=128
Reply from 172.16.99.10: bytes=32 time<1ms TTL=128
Ping statistics for 172.16.99.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Running PA ping from 172.16.99.10 to 172.16.99.1
Pinging 172.16.99.1 from 172.16.99.10 with 32 bytes of data:
Reply from 172.16.99.10: Destination host unreachable.
Reply from 172.16.99.10: Destination host unreachable.
Reply from 172.16.99.10: Destination host unreachable.
Reply from 172.16.99.10: Destination host unreachable.
Ping statistics for 172.16.99.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
============================================================================
Status of VM to Gateway test
============================================================================
Gateway VM setup Test : Not run
Gateway VM Cluster Test : Not run
Metadata store for the gateway Test : Not run
Gateway Routing Domain Configuration Test : Not run
Gateway Routing Domain Cluster Object Test : Not run
Routing Configuration in gateway VMs Test : Not run
Host Policy Test : Success
Gateway Host Policy Test : Success
Ping VM to Gateway Test : Failed
Ping VM PA Address to PA Router : Failed (Ignored)
Ping VM PA Address to HNV Gateway's PA : Success
============================================================================
PS C:\Windows\system32>