Messages

Does anyone actually respond to the posts with any help?  Is there a better forum to post these questions / problems on to?

Like most forums, people respond if they feel they can offer any help or advice.  Generally no replies, means nobody has any advice for you. 

I've posted recently and had replies. 

[/32]

Sorry, I'm probably being stupid here, I've tried doing as you suggested.  Something happens, basically any traffic in my browser is redirected to my OPNsense install.   :o

I've put a gateway IP into the local instance
(Doesn't work if I leave out the /32 - tunnel doesn't come up or show in "List configuration")

Local Instance



Endpoint



List Configuration



I've created the interface for Mullvad



And then a gateway with the assigned IP of the tunnel address of the local instance





So I think everything up to this point is good.  :D

I'm going to guess it's the following bits that have me confused, as I'm clearly missing something, and I'm sure those wiser than me will laugh at my mistake......

I've got an Outbound NAT rule



A Mullvad NAT Rule



And finally a LAN Firewall Rule (deactivated at the moment as enabling it results in everything redirecting to my OPNSense address. 



Really appreciate the advice.  Sorry for another lengthy post.

Ah, OK, added the IPV4 tunnel address on my local Mullvad WireGuard instance as the Gateway IP.  That worked.

I'm still not getting my traffic routed over the interface though, so presumably I need to add another rule in somewhere?

You need to put an IP address into gateway and also add this IP in gateway field in local instance. Then you can do routing via Firewall rules

Forgot to mention that I'd tried that and got the error message:

"The gateway address "10.249.0.1" does not lie within one of the chosen interface's IPv4 subnets."

So the thing that confuses me, is which IPV4 subnet is applicable to the Mullvad interface?  Another IP in the same range as the tunnel address?

So I recently migrated to OPNsense from Pfsense, I'm very impressed and glad I made the switch.  I've been experimenting with WireGuard a fair bit and have written a couple of blog posts on my progress so far with an OPNsense WireGuard "server" and Android and Ubuntu desktop "clients", so my next step was to try and setup Mullvad as the "server" and OPNsense as the "client"

I've been referencing the guides below:

https://wiki.opnsense.org/manual/how-tos/wireguard-client-mullvad.html
https://wiki.opnsense.org/manual/how-tos/wireguard-client-azire.html
https://www.routerperformance.net/opnsense-wireguard-plugin-azirevpn/

I can get the tunnel up, as evidenced here. (wg1, wg0 is my "WireGuard server for connection to my LAN remotely." and am using a custom port to receive the incoming connection.









(If I do not disable routes then I find all my internet access from LAN disappears.)

Undeterred I figured some manual routing would work and give me more granular control over things, so I created an interface.



and added a firewall rule



But traffic is still going out over WAN, rather than the Mullvad interface.  I tried to create a gateway, as shown here



and can manually bring it up, by clicking on the grey arrow, although I'm not sure how having the gateway really changes anything given my existing NAT rule.



I'm obviously missing something, but I'll be damned if I know what, and if anyone can give me some pointers I'd be very grateful indeed.

Sorry for the lengthy post/pictures, but figured it would be better to have too much information, rather than not enough.

Thanks

C

I've published my article now.  The link is:

https://blog.linuxserver.io/2019/11/24/connect-an-ubuntu-client-to-opnsense-wireguard-tunnel-with-a-gui-toggle-in-gnome/

I've already posted a link to my first WireGuard guide last week on connecting an Android phone to an OPNsense WireGuard tunnel here. 

(The direct link is https://blog.linuxserver.io/2019/11/16/setting-up-wireguard-on-opnsense-android/.)

This is my second guide on connecting an Ubuntu desktop to WireGuard and implementing a menu system to toggle the tunnel up/down.

Can read it on the blog of LinuxServer.io, an opensource docker group I belong to here.

https://blog.linuxserver.io/2019/11/24/connect-an-ubuntu-client-to-opnsense-wireguard-tunnel-with-a-gui-toggle-in-gnome/

I hope some of you find it useful.

I think it's a great idea!

Joined.

I'm just writing a guide on how I got WireGuard working with Ubuntu 19.10 as a client.  Should be finished and published by next weekend.   I'll pm you a preview now, and you can act as a tester.  It's the second part of the guide I published yesterday which is on the linuxserver.io blog here.

EDIT:  I've sent you a PM to the draft of the WireGuard Ubuntu guide.

Really nice, I'll link it on my site

Oh wow, awesome, thanks! 

And your hard work is very much appreciated.

Hey everyone, new to OPNsense, been wanting to try it out for a long time, but knowing I'd have to start from scratch after using Pfsense for a couple of years meant I had a degree of inertia.  WireGuard was the impetus I needed and I'm glad I jumped ship.

I've written a OPNsense WireGuard guide on the blog of LinuxServer.io an opensource docker group I belong to, figured it might be useful to some people here so here's a link.

https://blog.linuxserver.io/2019/11/16/setting-up-wireguard-on-opnsense-android/

Hope it helps one or two of you getting started with WireGuard.

Got another one in the pipeline to connect an Ubuntu laptop to OPNsense as well.

I know it might be easy to a lot of you, but a couple of things tripped me up, so I decided to write a guide.