Solved

Windows 2008 Hyper-v and pfsense / ddwrt

Posted on 2014-02-05
10
790 Views
Last Modified: 2014-11-12
Hi,

I have a question for the crowd.

We have a DL360 G5 laying around with an intel 1000 PT quad port network interface card, Windows 2008 standard and a requirement for 2 OpenVPN clients.
 
I have been looking into using pfsense for this task, but having some issues with the implementation, I have experience with both pfsense and untangle on dedicated machines, but the virtualization aspect has me a little stumped.

Does anyone have experience with this setup, or a suggestion for something better?

Cheers

Leon
0
Comment
Question by:Leon Kammer
  • 6
  • 3
10 Comments
 
LVL 57

Expert Comment

by:Cliff Galiher
ID: 39837384
You can start by describing the problem. "I'm having some issues with the implementation" isn't exactly descriptive.
0
 
LVL 5

Author Comment

by:Leon Kammer
ID: 39837413
Hi.

Sorry for the lack of description.

I have created the virtual machines, setup the NICs as external legacy adapters.
We can connect to the devices connected to the LAN interface, but cannot get out of the internal network.

The WAN and LAN interfaces both have valid IPs.
The WAN has been assigned 192.168.1.44/16 and can ping the address from the internal network.
The LAN has an IP of 192.168.10.1/16 and we cannot ping this, but can connect to the configurator.
I can see all the devices connected to the LAN connection on the network, and can connect to LAN side of the router. but there is nothing getting past the main gateway.

Leon
0
 
LVL 12

Expert Comment

by:Infamus
ID: 39837421
First of all 192.168.1.0/16 overlaps with 192.168.10.1/16

192.168.1.0/16 covers from 192.168.1.0 to 192.168.255.255
0
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 
LVL 5

Author Comment

by:Leon Kammer
ID: 39837605
Hi infamus,

Sorry for the misleading information, I just checked, and the IPs are 192.168.1.44/24 and 192.168.10.1/24
It's getting late here, the IPs are on 255.255.255.0, not 255.255.0.0

Cheers

Leon
0
 
LVL 57

Expert Comment

by:Cliff Galiher
ID: 39837717
Did you also create two virtual networks? Connecting both VM NICs to the same virtual switch will not accomplish what you want.
0
 
LVL 5

Author Comment

by:Leon Kammer
ID: 39838796
Hi Cliff, thanks for the response.

Yes, I have created 2 External virtual networks for the 2 NIC ports used by pfsense.
These have been assigned to the VM as "WAN" (00:15:5D:01:28:07) and "LAN" (00:15:5D:01:28:06)

From what I am understanding now, (in the physical world), what I have essentially done is take the WAN and LAN sides of a router and plugged them directly into a layer 2 device?

So, what should the setup be?
Do I need to separate the connections into VLANs?

Cheers

Leon
0
 
LVL 57

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 39840247
Nope, shouldn't be necessary. Based on how you described network flow, the issue is not the virtualization setup, but is a configuration of traffic routing within the VM OS itself.
0
 
LVL 5

Author Comment

by:Leon Kammer
ID: 39840333
Hi Cliff,

Thank you very much, I am quite new at this virtualisation concept.
I understand what you are getting at, and will make the adjustments within PFSense.

Thanks again.

Cheers

Leon
0
 
LVL 5

Author Closing Comment

by:Leon Kammer
ID: 39840336
Many thanks, easy to understand.
0
 
LVL 5

Author Comment

by:Leon Kammer
ID: 39850839
For sake of clarity.

When attempting to setup the network adapters within Hyper-V, it creates a local area connection within the parent OS.
Removing all protocols from the created connections forces the VM to use the physical adapter, and therefore creates what is called a dedicated connection within 2008R2 Hyper-V and later.

This is what was causing the issue, PFSense was seeing the network interface created by the network manager, not the physical NIC.

Cheers

Leon
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the hope of saving someone else's sanity... About a year ago we bought a Cisco 1921 router with two ADSL/VDSL EHWIC cards to load balance local network traffic over the two broadband lines we have, but we couldn't get the routing to work consi…
Sometimes drives fill up and we don't know why.  If you don't understand the best way to use the tools available, you may end up being stumped as to why your drive says it's not full when you have no space left!  Here's how you can find out...
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…

827 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question