Messages

61

18.1 Legacy Series / Hyper-V Gen 2 VM Issues/Workarounds (Supported in Build 18.1/FreeBSD 11.1)

« on: February 02, 2018, 12:02:52 am »

Figured it would be good to have a thread for those specifically running build 18.1 in a Hyper-V Virtual Machine. In this case using the new Gen 2 support which is included in build 18.1 due to the upgrade to FreeBSD 11.1 as the core.

The first issue I noticed is on a clean install.

The installer launches, allows for selecting Keyboard and Display Type/Font
Hit Enter
Freezes on screen where the Guided Install selection is.

However, it is not actually frozen... CTRL+ALT+Delete will still command a shutdown/reboot.

I noticed a weird workaround... change the font/display selection to a really large font (first or section option if I remember correctly)... then go back and change it to the smaller Thin font option.  It will mess up the wallpaper shown on the screen, but the menu options actually work and will install successfully.

-  Feel Free to add to this or other issues, fixes, or workarounds for Hyper-V Gen 2 related discoveries. -

62

18.1 Legacy Series / Re: Testing the latest versions

« on: January 10, 2018, 05:17:21 pm »

I updated to this build as well using the command line. Now I cannot access the management interface from an external web browser outside my network. Not sure if a SSL configuration changed for the Cipher with the new build or if it is a bug.

Google Chrome: ERR_SSL_PROTOCOL_ERROR

IE: This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.

63

18.1 Legacy Series / Re: [CALL FOR TESTING] FreeBSD 11.1, newer Realtek vendor driver and more

« on: October 28, 2017, 02:49:36 am »

opnsense-update -bkgr 18.1.b -n "snapshots\/beta"

This command isn't working properly for me.  It Fetches the first file ****.obsolete... done  the second file *****.txz comes up with an opnsense-verify error 04091068 rsa routines  bad signature.  Signature is not valid.

Any ideas?

My current build:
OPNsense 18.1.a_291-amd64
FreeBSD 11.0-RELEASE-p12
OpenSSL 1.0.2l 25 May 2017

64

18.1 Legacy Series / Re: How to test the development version

« on: October 19, 2017, 01:36:10 am »

I edited the Makefile to bypass the missing files (wpa_supplicant) was also missing.

OPNsense 18.1.a_261-amd64
FreeBSD 11.0-RELEASE-p12
OpenSSL 1.0.2l 25 May 2017

I thought it was supposed to include FreeBSD 11.1 ?

65

18.1 Legacy Series / Re: How to test the development version

« on: October 19, 2017, 12:44:53 am »

I keep getting a Missing dependency: hostapd error when trying to run the make upgrade command.

66

15.7 Legacy Series / Re: How do I restart openvpn client from the command prompt?

« on: June 27, 2017, 05:11:00 pm »

I was just wondering if these or similar OpenVPN restart commands/scripts were ever implemented or if there are any other similar recommendations?

I would like OPNSense to restart my OpenVPN client running at:    /usr/local/sbin/openvpn --config /var/etc/openvpn/client2.conf     every evening at midnight (12AM). I was thinking about using CRON but wasn't sure the best way on how to implement it myself.

I am currently running 17.1.8 OPNSense

Thanks

67

17.1 Legacy Series / IPv6 / DNS

« on: February 02, 2017, 05:03:30 am »

I updated to 17.1 this evening....

I am having 2 new issues, maybe someone could shine some light.

1. If I leave the DNS servers blank on System-> Settings -> General. Even with  "Allow DNS server list to be overridden by DHCP/PPP on WAN" checked... there are no DNS servers passed over to DHCP clients on the LAN using the DNS severs on the WAN interface.

2. IPv6 on Comcast... WAN has IPv6 address.  I can ping from OPNSense web interface to ipv6 address. However no client on the LAN network can.  It is set to "Track Interface" for IPv6 on LAN.   Then WAN / 0 down below under Track Interface settings.   I also noticed no IPv6 DNS servers are being passed over DHCP from the WAN address.

Just curious if anyone has any suggestions on what to try to fix these issues.

68

16.7 Legacy Series / OPNSense (Hyper-V) w/Private Internet Access VPN

« on: December 30, 2016, 04:05:49 am »

I currently am running a new OPNsense setup...

I have a Windows Server 2016 on a computer running Hyper-V with OPNsense installed.

Utilizing 2 NIC's... one for WAN (Cable Modem Attached), and one for LAN to my switches in my house with other wired devices utilizing Hyper-V Virtual Switches.

This is working great after I got it all setup today...

The next question is that I have a subscription to PIA (Private Internet Access) VPN.
I would like to route (most) of my traffic through this... with exception to a few devices such as my home security system, Wi-Fi calling cell phones, and a few other things.

I was wondering what would be the easiest way to segment some of the network traffic and use PIA in an OpenVPN Client setup?

Would VLANs be best and route an entire VLAN through the VPN? or create another virtual interface and static route through the VPN?

I am open to suggestions or if anyone can point me to a guide that has done this sort of setup before...

Thanks!