Hyper-V WAN uses hosts WiFi NIC



  • 2.2-BETA  (amd64) built on Wed Oct 08 06:53:41 CDT 2014

    Hyper-V WAN uses hosts WiFi NIC mostly does not work.  Unable to renew IP address via WebUI and Console

    Other (Windows) guests can use External/WiFi Hyper-V switch configuration.

    Thanks
    Seth



  • @Seth:

    Hyper-V WAN uses hosts WiFi NIC mostly does not work.

    Try that sentence again in a English readable way.
    Really no clue what you mean by that.



  • @Seth:

    2.2-BETA  (amd64) built on Wed Oct 08 06:53:41 CDT 2014

    Hyper-V WAN uses hosts WiFi NIC mostly does not work.  Unable to renew IP address via WebUI and Console

    Other (Windows) guests can use External/WiFi Hyper-V switch configuration.

    Thanks
    Seth

    Had the same issue, if it's consumer windows (8, 8.1) it's because of the way that Windows turns the NIC into a bridge to share it with the host OS.  I worked around it by using VirtualBox, or by setting a static.



  • I've been playing with this on and off and have determined that both static and dynamic IPv4 address have the same issue.  I've replicated this on 2 different laptops and 2 different OS (Win8.1 and Win10)  It's more likely an incompatibility on the MS or FreeBSD side with the synthetic network driver.

    Any thoughts would be appreciated.
    Seth



  • Have you reproduced this on something a little more current and less beta?  That 2.2-beta is more than 6 months old, it's not the final code for 2.2 and there have been 2 updated releases since.



  • I should have mentioned that in my last post.  Yes 2.2 Release 64bit.



  • 2.2.2 is current.  I generally don't waste time debugging problems with older versions.  Update to current release if possible and then reproduce your problem.



  • Again I mistyped.  I am running  pfSense 2.2.2-Release-pfSense (amd64).

    I've also simplified the the config to rule out load balance and fail-over configuration issue.  That said the VM has 2 NICs.  External associated with a physical WiFi adapter serving as WAN.  The second is a Private virtual adapter associated to the LAN adapter in pfSense.

    While running a packet trace from the pfSense VM I could see the traffic stop then resume.  No network errors just ICMP echo reply stopped  I've included the RRD graph and packet trace snapshot.  Nothing telling in the Gateway logs.
    192.168.3.147 in the VMs WAN interface IP.
    192.168.20.254 is the VMs LAN interface IP.

    Thanks
    Seth






  • Anything in the System log when the outage occurs?



  • Afraid not

    
    Jun 18 07:37:46 	check_reload_status: Reloading filter
    Jun 18 07:37:46 	check_reload_status: Restarting OpenVPN tunnels/interfaces
    Jun 18 07:37:46 	check_reload_status: Restarting ipsec tunnels
    Jun 18 07:37:46 	check_reload_status: updating dyndns WAN_DHCP
    Jun 18 07:31:24 	check_reload_status: Reloading filter
    Jun 18 07:31:24 	check_reload_status: Restarting OpenVPN tunnels/interfaces
    Jun 18 07:31:24 	check_reload_status: Restarting ipsec tunnels
    Jun 18 07:31:24 	check_reload_status: updating dyndns WAN_DHCP
    Jun 18 07:26:15 	check_reload_status: Reloading filter
    Jun 18 07:26:15 	check_reload_status: Restarting OpenVPN tunnels/interfaces
    Jun 18 07:26:15 	check_reload_status: Restarting ipsec tunnels
    Jun 18 07:26:15 	check_reload_status: updating dyndns WAN_DHCP
    Jun 18 07:23:00 	check_reload_status: Reloading filter
    Jun 18 07:23:00 	check_reload_status: Restarting OpenVPN tunnels/interfaces
    Jun 18 07:23:00 	check_reload_status: Restarting ipsec tunnels
    
    


  • No idea, sorry.


Log in to reply