Messages

Hi guys,

I'm running the 19.1 clean install on an Intel NUC.

In the past i've been able to run my WAN connection PPPoE via a USB3 to Ethernet dongle using opensense version 17 and 18, but 19 is being very fussy

I've tried about 4 different USB to Ethernet adapters, and they all "detect" as bind-able interfaces, but all have some trade offs/issues

most are unstable, and will connect to my ISP for almost 1 min, then disconnect.
others will connect, and stay connected but limit my speed to 40Mbit.

pretty frustrating, any idea on workarounds? kernel update maybe, i dunno...

Cheers.

Thanks for pointing out the version difference, yes I am 100% sure its the traffic graphs dropping the WAN, my connection is super stable, will say online for weeks, but soon as i idle in that menu, WAN connection drops.

I will do a baremetal backup, update the release version, and try again.

Cheers

Hey Guys,

Just letting you know I found a bug, every time I click on Reporting>Traffic Graph and wait for a little while and watch the PC's on my network show traffic out the WAN, the WAN connection disconnects after about 20sec.

Only way to get it back is, disable/re-enable the WAN interface or reboot the PC

Details:
OPNsense 18.1.6-amd64
FreeBSD 11.1-RELEASE-p9
OpenSSL 1.0.2o 27 Mar 2018

Running on Intel NUC with USB to ethernet as WAN interface (if that helps)

Let me know if you need any other info.

Cheers.

Hey Guys,

M4DM4NZ here, wow this HOW-TO I started over a year ago has had some major viewing, so i figured I better keep you all up to date with my current configuration.

Sorry i haven't been on here posting much, life stuff gets in the way of geek stuff now and then...

Anyway, I recently had issues with my VPN dropping out a few months ago and figured I better update opnsense to a more current version as I've been using 17.something for a while now.

I cant say exactly what i did, but from memory I've backed up my current config from 17.x and restored it overtop of a clean install of 18.x

I do recall some funky things happening as it wasn't a smooth transfer and involved a lot of trial and error test.

So... I'm gonna go over my current working config soon and post some settings here once get home from work.

Thank you all for your effort in keeping this thread active, and big thanks to conanTheRouter and NilsS for maintaining my How-To and adding some cool functions.

Keep you all posted soon with config updates :)

I did manage to get it going (kinda).

I inverted my original setup so by default all traffic passes by the VPN, then set a rule pointing a single PC on my network to have access to the WAN directly. (DMZ)

After messing around with these setting for HOURS! I did manage to get it working, but it wasn't stable.

I had to flip the gateway setting in the LAN rule for the single PC that required WAN access, then flip it back so the gateway was using the VPN, then flip it back again.

It worked fine (untill that single PC released/renewed its IP address)

so, for now I've reverted back to 17.x until i can find more time to take another look at it.

Keep you posted.

Hi Andrea,

Well, I'm a little stuck too... I wrote the original HOW-TO for getting this going under 17.x but this new version is not playing nice.

I've been trying a combination of settings but no luck so far, fingers crosses, this could just be a bug that gets corrected in the next update.

Will keep everyone posted on here if i find a work-around.

Cheers :)

[Source: VPNRouter]

M4DM4NZ .....

Step 9:

Rule 1:

Shouldn't

Source:  VPNRouter

actually be

Source:  VPNTraffic

Thanks for spotting that dude, I have updated the Guide...

Thanks dude, i'll give it a blast tonight :)

Hey guys,

Did a clean install of 17.7 on my Intel NUC on the weekend, fresh install with no plugins/mods enabled,
Got my LAN interface setup as re01, and WAN setup as ue0.

The WAN interface is a USB to Ethernet dongle(plug) whatever, and it all works fine. Dont have any rules setup yet,  its pretty much a clean install.

Problem is, if i reboot or cold boot the system, the WAN interface disappears!
When i log back in to the GUI, the WAN interface is just "unassigned" and i have to add it again to get it working.

I've tried about 4 different brands of USB to Ethernet interfaces, and they all work prefect, until I reboot.

Can anyone explain whats happening here?

Cheers.

Hey Guys,

having a problem with opnsense, Im running 17.1.8 on an Intel NUC, my WAN connection is a USB to Ethernet dongle and after configuring the interface everything works fine.

BUT, once i reboot the PC the WAN interface just disappears, I have to manually add it again in the interfaces menu.

Weird huh? anyone else come across this issue?

Hi

I have been trying to get this working, all the ip addresses I setup to go through the VPN work correctly. However any traffic not going via the VPN can not reach the internet. The 1st time I tried these steps I could get the internet to work if I set a static ip address with a DNS. The second time I tried everything seemed to connect correctly to the internet but I still could not reach anything and setting a manual ip and DNS did not work this time.

Is there any way to test why this is not working correctly?

thanks

Hi Pauld70,

not sure whats going wrong there, but just to compare, I also have my DNS set to static using googles DNS 8.8.8.8 as secondary and opensens default IP 192.168.1.1 as the primary

Hope this helps.

Cheers

Hi Tsol,

The certs in step one are created by your VPN provider, ie. the ones you download from the particular VPN provider your registered with.

Not sure about the Adguard DNS stuff, haven't had time to play with it much :/

Cheers

Hey mate,

No i haven't tried using other DNS providers besides my VPN provider, but i'll look into this.

I'm pretty sure when my VPN connection drops out (which doesn't happen that often) traffic to my torrent client just stops. I'll check my settings soon and post an update.

Cheers.

Thanks Eptesicus :)

Yeah I tested the DNS leak on my setup using dnsleaktest.com and found no issues, my results pointed to the correct DNS server of my VPN Provider so I'm guessing your issue could be with your VPN provider.

Maybe try connecting another pc directly to the DMZ and installing the VPN client software supplied from your VPN Provider, then try the dnsleaktest.com again.

Cheers :)

FYI, I've written up a detailed HOW-TO on this subject:

https://forum.opnsense.org/index.php?topic=4979.msg19771#msg19771