Messages

1

Virtual private networks / Re: Wireguard connection to VPN not working in 23.7.9

« on: December 08, 2023, 08:51:41 pm »

Following the guide here, I managed to get it working, but disabling / enabling one rule as well (guess rules needs refresh)

https://github.com/FingerlessGlov3s/OPNsensePIAWireguard

2

23.7 Legacy Series / Re: VPN & Gateway issues recently

« on: December 08, 2023, 08:14:42 pm »

I think I have the same issue:

https://forum.opnsense.org/index.php?topic=37433.0

3

Virtual private networks / Re: Wireguard connection to VPN not working in 23.7.9

« on: December 08, 2023, 08:03:09 pm »

So this happened when I updated from 23.7.3 to 23.7.9 does anyone have any Idea on what I can do to debug or find out what is failing? Where to start looking?
It's been rock stable up until now

Thinking about reverting back to a openVpn setup, but really like wireguard.

4

Virtual private networks / Wireguard connection to VPN not working in 23.7.9

« on: December 07, 2023, 11:25:51 pm »

I get the following error Crash report

Code: [Select]

[07-Dec-2023 23:15:00 Europe/Stockholm] TypeError: explode(): Argument #2 ($string) must be of type string, array given in /usr/local/opnsense/mvc/app/controllers/OPNsense/Wireguard/Api/ClientController.php:80
Stack trace:
#0 /usr/local/opnsense/mvc/app/controllers/OPNsense/Wireguard/Api/ClientController.php(80): explode(',', Array)
#1 [internal function]: OPNsense\Wireguard\Api\ClientController->setClientAction('b090adb7-4325-4...')
#2 [internal function]: Phalcon\Dispatcher\AbstractDispatcher->callActionMethod(Object(OPNsense\Wireguard\Api\ClientController), 'setClientAction', Array)
#3 [internal function]: Phalcon\Dispatcher\AbstractDispatcher->dispatch()
#4 /usr/local/opnsense/www/api.php(24): Phalcon\Mvc\Application->handle('/api/wireguard/...')
#5 {main}


I can also see in the wireguard log:

Code: [Select]


wireguard /usr/local/opnsense/scripts/Wireguard/wg-service-control.php: ROUTING: not a valid interface gateway address: ''


Code: [Select]

FreeBSD 13.2-RELEASE-p5 stable/23.7-n254837-8806e8fefb1 SMP amd64
OPNsense 23.7.9 7d9231b7d
Plugins os-ddclient-1.17 os-iperf-1.0_1 os-udpbroadcastrelay-1.0_3 os-wireguard-2.5_1
Time Thu, 07 Dec 2023 23:23:27 +0100
OpenSSL 1.1.1w
Python 3.9.18
PHP 8.2.12

Any one know what's up? Or can direct me to another thread with similar problems?

How do I do a full downgrade including plugins to a previous version?

5

20.1 Legacy Series / Re: Problem with interface configuration (Default interface not found)

« on: March 30, 2020, 04:39:46 pm »

Thanks for the reply!

That helped!

I suspect I have a somewhat strange config after some imports of pfsense config.
I had also the wrong static ipv4 config for the interface.

Change from 10.0.30.1/32 to 10.0.30.1/24

(for Vlan 30).

Regards S.

6

20.1 Legacy Series / Problem with interface configuration (Default interface not found)

« on: March 30, 2020, 12:58:13 pm »

Hi!

I'm trying to migrate from Pfsense to Opnsense. My current problem is that I can't add my VLAN interfaces.
I have added the VLANs, but when I assign it to a new interface and reboot, I get the message:

"Default interface not found -- Running interface assignment option"
When that is done my WAN and LAN are swapped and I have to do manual assignment.

The hardware I'm using is a Qotom with 4xIntel nics, I can assign all NICS and boot without problem, but as soon as I add a VLAN via LAN this happens. This setup works fine in pfsense.

I've tried adding delay in /boot/loader.conf.local where I have added the entry:
kern.cam.boot_delay="10000"

But that does not help.
 
Would be really grateful for any pointers, since I'm really looking forward to start using opnsense!
It's a bit of mess to migrate since I don't want to cut off internet here at home for too long, so
doing dual boot pfsense / opnsense with two different ssd:s.

Regards S