Messages

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!

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...........

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.

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.

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!

Thank you for not judging! I was not aware that pfSense had removed support for PPTP, but I am not surprised. I myself use OpenVPN for all my connections. I was aware that NAT 1:1 mappings with multiple public IP's would make this possible, but honestly we spend quiet a bit of money with our ISP for one IP per location, and of course multiple IP's are not free! I am bound by budget constraints, more so being a NPO. Our "Guest" uses four clients per location when there. I was just curious if a resolution had been considered or possible with OPNsense. Although PPTP is no longer secure, I can see in the pfSense forums there are quiet a bit of users that would welcome such a resolution! Irregardless, I will be taking OPNsense on a "test drive" as soon as feasible! I feel sure you have expanded on pfSense!

Thanks, Greg.

Good Morning! Just a quick question concerning OPNsense. And please don't beat me up about pptp, I realize it is a compromised protocol. I manage a network for a NPO with several sites, and have happily used pfSense with OpenVPN site-to-site for years, and it is great! However, the pptp limitations are very painful. We have a very important "Guest" that uses our facilities a couple of times a year, and this "Guest" still uses multiple pptp client connections to a single server with one public IP. Therefore only one outgoing connection is possible. Are multiple pptp connections behind OPNsense possible? I apologize if this question has already been asked, but I found no reference while searching the forum.

Thanks, Greg.