Not Ready for Prime Time (For Me)

[ghowey]

Since it would appear that pfSense is moving towards a paid product in lieu of opensource I thought to give OPNsense a go. Identical configuration as my production pfSense on MS HyperV 2016 provided me no connection to the outside world. Since both are based on FreeBSD 11.1 I would have expected a similar experience. Fours hours of configuration and multiple clean installations still provided no internet connectivity......

Will try again on the next release!

[mimugmail]

With this kind of solving problems also the next 20 releases will do it.
You really should consider asking questions to your problems here in order to get them solved.

I'm running multiple OPNs on HyperV in production.

[ghowey]

I was not really looking for resolution just making a statement. However, my problem is no internet connectivity with WAN (hn0) on HyperV 2016 set to DHCP, just as in the pfSense install. Interface is set to DHCP with Spectrum ISP (Formerly TWC) provider. Should be just plug and play, GUI shows interface enable properly, does not pull an IP address.

[weust]

I've been running OPNsense on either Hyper-V 2012 R2 and 2016 for some years now, never and issue.
Gen1 and Gen2 type, internet cable in it's own VMSwitch or through a VLAN on my Cisco switch and configured on the NIC in the settings of the VM.

You're not making a statement at all. You didn't get it working. That is it.

[ghowey]

I would like to get it working, I have tried both Gen1 and Gen2 VM's. Internet Cable to VM Switch manager as you, configured just as pfSense, still unable to pull ip address on WAN (hn0). Just curious as to what release of 18.1 you are using? This is HyperV 2016, not Windows Server 2016, thinking that does not really make a difference.

[weust]

For me it's home use, so Hyper-V 2016 Free. Hyper-V 2012 R2 Free till the dsy 2016 was released, basically.

Right now I am running the latest, 18.1.7.

One thing I do, because of my ISP, is set the WAN NIC to a static MAC address.
In the beginning with the first VM, I set the dynamically assigned MAC address to static.
That helps when I test things and create a different VM. I just copy over that MAC address so I don't have to restart the cable modem.

If your setup is internet cable to physical Hyper-V port and you're created a VMSwitch using that NIC port, it should work.
Just keep in mind that per default, on the first boot, hn0 is LAN and hn1 is WAN. So opt for manually assigning the NICs.

[ghowey]

You would think I would check the obvious, after reading your last post I feel like a blithering idiot! My configuration for all purposes is identical to yours, no problem with hn0 vs hn1. I have not been copying the MAC over, a simple restart of the cable modem resolved all my connectivity. I however cannot get the installer to run through the GUI with a Type2 machine. I have no issues with using Type1 machine, that is what I use for pfSense. Thank You...........

[weust]

Not sure if you're angry at me, or that I helped you in the right way...

In any case, my post was just to show how I have done things since early 2015 when I started using OPNsense after stopping pfSense for the obvious reasons.

[franco]

Hello,

For Hyper-V OPNsense is as close to FreeBSD as it possibly gets. Where this leaves pfSense I cannot say, but I would assume it's the same.

With that being said, there are three possibilities here:

1. Setups quirks that have been needed in the past were forgotten when trying new things. It happens to all of us.

2. Hyper-V host environments can cause occasional guest issues. I think there are reports for this on this forum.

3. There is indeed a bug which could be traced via https://bugs.freebsd.org/bugzilla/ , but I'd rather know this than what software works best for whom and why.


Cheers,
Franco

[ghowey]

weust, I am not angry at all, your post illuminated the simplicity of my obvious error, I appreciate your help! franco, I have never installed pfSense on a Type2 HyperV envelope, so I am not sure about the particulars to get either to install on a Type2! I did find it interesting  the live version would boot and run on the Type2, when invoking the installer via the GUI it hung I believe at the third screen, selecting the guided install. Perhaps something undiscovered with my configuration. I am perfectly happy with a Type1 VM, I feel like pfSense is moving towards a paid platform, it is time to move away!

Once again, Thanks!

[franco]

I think we found our deviation. Make sure you use 18.1.6 images to install, also try selecting font 8x14 and guided install. See more on this subject on Gen 2 below:

https://github.com/opnsense/core/issues/2254#issuecomment-382915270

Would love to hear if this worked for you too or not.


Cheers,
Frnaco

[weust]

Good to read that :-)

One thing I had with the 18.1 image was the hanging too.
Only thing that helped was remove the VM, and create a new now.
No clue why, but it helped.

And also, don't forget to disable Secure Boot.