In Hyper-v none of my NIC port can get wan ip

[CarsonKT]

It's interesting that if I put hen my behind my wifi router for testing I can get a IP by go to the interface-wan save and apply, I didn't change a there, and I will receive
"unknown status 1073807384 received"

After I finished most config I decide to put the vm behind the modem and turn the wifi router to a AP, now pfSense can't get IP address from cable modem

Here are 3 ports
On board one is 8111e
Dual port HP nc340t which is Intel pro 1000
I tried everyone of them and the WAN address is 0.0.0.0

Sometimes it gets IP from cable modem shows 192.168.100.10 and once the modem fully initialized the IP will again becomes 0.0.0.0

On the other hand if I connect my wifi router to cable modem, after it says 192.168.100.10 it will quickly get a IP 24.xx.xx.xx from my ISP

Any ideas? Thanks,

[CyanPixie]

I have a similar setup to you and think that I had the same issue as you - but it was quite a while ago, so forgive me if this doesn't work.

So, in Hyper-V I have 2 Virtual Switches on my network. I have the Standard Virtual Switch which is bound to the server NIC ports where the internal network traffic flows and is plugged into my internal switch - which would be your Wifi AP. I additionally have a Modem Virtual Switch - which is bound to the PFSense WAN interface. The modem VS is then bound to one of the NIC ports and I plug the modem into that port using a crossover cable. However, the way I made it all tie together is to change my modem into bridge mode. The PFSense WAN interface will then do the authentication. Since my ISP uses PPPoE to authenticate I just put my PPPoE settings in and everything starts working. I am sure you can find your authentication setting out from the modem itself or from your ISP. Your WAN interface should then get the IP address from the ISP.

Hopefully this will help you.

[CarsonKT]

Thanks for you reply, I am using cable modem DCM476 and I believe the modem will put itself into bridge mode once it's connected

but somehow this just won't work for me, and I finally give up and switched to ESXI 6 and now everything works fine

[l0rdraiden]

@CarsonKT:

It's interesting that if I put hen my behind my wifi router for testing I can get a IP by go to the interface-wan save and apply, I didn't change a there, and I will receive
"unknown status 1073807384 received"

After I finished most config I decide to put the vm behind the modem and turn the wifi router to a AP, now pfSense can't get IP address from cable modem

Here are 3 ports
On board one is 8111e
Dual port HP nc340t which is Intel pro 1000
I tried everyone of them and the WAN address is 0.0.0.0

Sometimes it gets IP from cable modem shows 192.168.100.10 and once the modem fully initialized the IP will again becomes 0.0.0.0

On the other hand if I connect my wifi router to cable modem, after it says 192.168.100.10 it will quickly get a IP 24.xx.xx.xx from my ISP

Any ideas? Thanks,

Did you fixed this issue?
I have exactly the same problem, I have tried everything (hours of troubleshooting) without finding a solution.

Any help is welcome.

[phase1]

Hey guys…. I had the same problem back than when first trying out pfSense...

Have you guys tried a crossover cable??
Also as a test have you tried using a switch in the middle of your NIC and VM??

[l0rdraiden]

@phase1:

Hey guys…. I had the same problem back than when first trying out pfSense...

Have you guys tried a crossover cable??
Also as a test have you tried using a switch in the middle of your NIC and VM??

I haven't tried any of this, for now I have moved to unraid and it just work.
If someone can confirm that with the crossover cable works, I could try as well, but even if it works with a switch I won't use hyper-v in this case.

I have tried almost everything already, play with network settings, adapters options, driver settings…

[provels]

Only replying because I had a (possibly) similar problem recently.  Maybe it will help a Googler from the future…

I had pfSense 2.4.3 64-bit running in a 2012R2 VM just fine, but then the Meltdown/Spectre exploits were announced, so I reverted to my old 32-bit Via hardware box.  I decided to give the VM another shot, but when I booted it up it would occasionally get a WAN IP (but mostly not) but no Internet.  After much hair-pulling, including rebuilding and restoring several times, I disconnected the WAN vSwitch and deleted/recreated it.  Got a WAN IP, no issue.  Then I faced a strange problem that I could not get Internet access from my 2 wireless access points (on the same net as the wired).  I was unable to resolve any DNS addresses from devices behind the wireless, even though I could ping through the pfSense (to, say, www.google.com) by IP.  Nothing in the Unbound logs (Forwarder did not work either).  I could RDP to another wired box across the wireless, and get Internet fine.  Ended up disconnecting the LAN vSwitch from all my VMs and deleted/recreated it as well.

All fine now.  Bits, gotta love 'em...  ::)

Hope this saves someone some grief.