2.0 Release on Hyper-V W2K8R2
Ive been at this for a few days now. Ive googled everything I can think of but no one has a answer besides ifconfig de0 down then up and dhclient de0. I just got a dual port nic card and a riser card for my rackable systems 2U server. I can configure the nics in and windows and add them to pfsense no problem. I an unable to get the nics to see any exterior or interior network. I can not get my current pfsense router to see the vm or anything. I am unable to ping the VM and it wont lease DHCP or get DHCP.
What in gods name am I doing wrong? Everyone else can get this working but me for some unknown reason. I love networking and problem solving but this is stressing me out beyond belief.
Im at the point where I will pay someone to RDP in with my supervision and fix it enough to where it sees my modem and sees my lan.
Also please dont respond with it is testing only or it wont work. Unless my version specifically wont work.
heper last edited by
did you read this: http://forum.pfsense.org/index.php/topic,44568.0.html
also, use 2.0.1, it has various security fixes + some bug fixes
Yeah I did that was the first FAQ. I can't broadcast any requests on LAN either.
Also in the first post it describes portions from that.
cicero44bc last edited by
Legacy NICs? Dropped to shell and taken the interface down and back up again? Cures my issues of the exact same symptoms.
It doesn't fix it is the problem. I did two installs with it to.
cicero44bc last edited by
May be post a diagram of how this is set out as from your description I cannot clear deduce the current setup. From
I can configure the nics in and windows and add them to pfsense no problem.
and the fact you posted this in a Visualization forum and say you've done this http://forum.pfsense.org/index.php/topic,44568.0.html it would appear that you've set pfsense up as a VM and are mapping the ports on the NIC to the pfsense VM.
I can not get my current pfsense router to see the vm or anything.
it could be that you've got a physical pfsense router that you're having trouble getting to work with VMs on a LAN and get an IP on the WAN NIC?
Not trying to be obstructive or simple just to understand.
I may well create a Hyper-V VM and host it somewhere for people to download if this would be of any use.
Mats last edited by
You need an aditional download for some of them to get Vlan support and Hyper-V do use that.
Ran into it on a 2008R2 Hyper-V with an ISA server as guest, same problems as you had
They are server grade Intel nics, MT series I believe. Do I need to configure the nics in a certain way?