Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - freejack

#1
Thanks for checking it out. Here also for completeness the instance settings -- disable route not set, as documented in the tutorial.

The only thing non-vanilla about my setup, beside being freshly created with 26.7, is the "disable source nat rule generation", as I do not need these for my fully route-able use case.
#2
wg instance has route. But only when route is replicated on interface assignment it is actually created. And wg peers can access.

Otherwise it is missing. And wg peers cannot reach other segments.
#3
Quote from: Bob.Dig on October 14, 2026, 06:09:10 PM
Quote from: freejack on October 10, 2026, 11:55:12 AMWhile the interface edit dialog rejects an ip config for a tunnel, the assignment dialog allows it, so I entered it there.
That is how you do it in OPNsense.

Nope, see the linked road warrior tutorial in my original post. There IPv4 and IPv6 config is documented as "none" for interface assignment in step 4(a). That's leading to missing route. Deviating from the docs and using a static IPv4 config there, with the tunnel's IPv4 settings replicated, leads to a working config.
#4
26.7, 26.10 Series / missing wireguard automatic route
October 10, 2026, 11:55:12 AM
Setting up a new instance and following the Road Warrior tutorial I noticed routing issues for my wg peers (peers get a handshake, but cannot access). And System - Routes - Status did not show a route for the wg interface.

Ignoring the "There is no need to configure IPs on the interface. The tunnel address(es) specified in the Instance configuration for your server will be automatically assigned to the interface once WireGuard is restarted" note from the tutorial and adding the tunnel static ip config for the wg interface as well resolves the issue (route shows up in status, peer can access). While the interface edit dialog rejects an ip config for a tunnel, the assignment dialog allows it, so I entered it there.
#5
Was testing a N5105 this year as well, and observed vm crashes. Turned out the system had ram stability issues.
If you did not yet tested stability you might run mprime and a memchecker for a day each.