Messages

106

18.1 Legacy Series / Re: Network via intel 350t4v2 - please help

« on: May 14, 2018, 01:58:40 pm »

Why didn't you just disable the onboard NICs in the BIOS/UEFI?
That way they won't even be detected by the OS.

107

General Discussion / Re: Hyper-V 2016 Integration Services

« on: May 12, 2018, 01:17:07 am »

System\Settings\Administration
Close to the bottom there is an option named "Primary Console".
Set that to EFI.

108

General Discussion / Re: Hyper-V 2016 Integration Services

« on: May 12, 2018, 01:10:01 am »

:-) it can be quite annoying, but luckily I hardly had problems setting up my VM at the time.

109

General Discussion / Re: Hyper-V 2016 Integration Services

« on: May 12, 2018, 01:02:30 am »

You didn't miss anything. The installer is just buggy on Gen2.
Keep trying, although I don't think you will have to recreate the VM again.

110

General Discussion / Re: Hyper-V 2016 Integration Services

« on: May 11, 2018, 05:47:33 pm »

I ran into that as well. Remove the VM, start over.
There is another topic which goes deeper into it, with a reply from Fitch iirc explaining a bit about the issue.

It's a weird one, but has been running for me for almost half a year now (tried a test build with FreeBSD kernel 11.1 and Beta too).

111

General Discussion / Re: Hyper-V 2016 Integration Services

« on: May 11, 2018, 01:27:14 pm »

The FreeBSD kernel has these integrated.
It's not like Linux where you have add them manually.

I am running OPNsense in a Gen2 VM at home on my Hyper-V 2016 server, and in Gen1 on 2012 R2 before that.
Runs great.

112

Hardware and Performance / Re: Atom C3000 - do intel nics work?

« on: May 07, 2018, 10:05:59 pm »

OPNsense can use whatever the OS supports.

113

Hardware and Performance / Re: Atom C3000 - do intel nics work?

« on: May 07, 2018, 09:30:34 pm »

The current OPNsense release (18.1.x) runs on top of FreeBSD 11.1.
With some added patches from  HardenedBSD for security.

114

18.1 Legacy Series / Re: 18.1.7 not handing dhcp leases to Windows client's, Mac & Linux are fine

« on: May 07, 2018, 03:05:57 pm »

Reason I asked is that when searching for an answer, I only saw it mentioned with Windows clients and DHCP Relay Agent, but linux working just fine.

I don't have a solution for your, I'm afraid. I don't use the DCHP server in OPNsense.

115

18.1 Legacy Series / Re: 18.1.7 not handing dhcp leases to Windows client's, Mac & Linux are fine

« on: May 07, 2018, 12:36:21 pm »

You're not using DHCP Relay Agent by any chance?

116

18.1 Legacy Series / Re: Not Ready for Prime Time (For Me)

« on: May 06, 2018, 07:44:09 pm »

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.

117

18.1 Legacy Series / Re: Not Ready for Prime Time (For Me)

« on: May 06, 2018, 06:43:32 pm »

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.

118

18.1 Legacy Series / Re: Not Ready for Prime Time (For Me)

« on: May 06, 2018, 05:59:31 pm »

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.

119

18.1 Legacy Series / Re: Not Ready for Prime Time (For Me)

« on: May 06, 2018, 05:20:50 pm »

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.

120

17.7 Legacy Series / Re: I have a problem

« on: April 23, 2018, 01:04:01 pm »

Can't imagine why you're having issues, but for testing purposes could you try other network cards?
Intel is favourable of course, but just to avoid the onboard cards.

Also, why are you running 17.7 and not 18.1? 18.1.6 image/ISO files have been released last week, so please give that a go instead of the old version.