Messages

Thanks, didn't know where to look. I think I've found the issue (obfuscated the key a bit):

Code Select Expand


root@OPNsense:~ # /usr/local/etc/rc.d/wireguard restart
wg-quick: `wg0' is not a WireGuard interface
[#] wireguard-go wg0
INFO: (wg0) 2020/06/15 09:35:05 Starting wireguard-go version 0.0.20200320
[#] wg setconf wg0 /tmp/tmp.v90Z9IPh/sh-np.zTQZji
Key is not the correct length or format: `**********hLQ0vXOb0DxHAtnAvK38ZJYduidtVX**='
Configuration parsing error
[#] rm -f /var/run/wireguard/wg0.sock


Looks like I made a copy-paste error. After re-entering the correct key (and saving it), everything started working again.

Thanks!

Hi,

After an update to the most recent version from Opnsense ( OPNsense 20.1.7-amd64), my wireguard install suddenly ceased working. I am running Wireguard plugin 1.1. The only thing I see in the logs is this:

2020-06-14T19:21:49   kernel: wg0: link state changed to DOWN
2020-06-14T19:21:49   kernel: tun0: changing name to 'wg0'
2020-06-14T19:21:49   kernel: tun0: link state changed to UP

Now, there's probably more to this error than the logs show in the GUI, but I don't know where to look or how to troubleshoot this. Can someone point me in the right direction?

Solved the issue. Apparently, I created a peer without a public key in the past. Since it was not working, I deleted the plugin and reinstalled it. I think that wg0.conf wasn't deleted when I removed the plugin (have not verified this), so the old settings were still there. Deleted wg0.conf, deleted the plugin, rebooted opnsense, installed the plugin and this time I got the wg0 interface.

Thanks for all the support!

Now onto the next challenge. I am connected to the Opnsense firewall, but cannot reach anything on the network or on the internet...

SSH, Type 8 for Console, then:

/usr/local/etc/rc.d/wireguard restart

Running that command gives:

/usr/local/etc/rc.d/wireguard restart
wg-quick: `wg0' is not a WireGuard interface

• wireguard-go wg0
  INFO: (wg0) 2019/12/11 07:23:21 Starting wireguard-go version 0.0.20191012
  
• wg setconf wg0 /tmp/tmp.64MsU480/sh-np.qmmiA2
  Line unrecognized: `PublicKey='
  Configuration parsing error
  
• rm -f /var/run/wireguard/wg0.sock
  

When I look at /usr/local/etc/wireguard/wg0.conf, I get the following:

[Interface]
Address = 10.0.2.0/24
DNS = 1.1.1.1
ListenPort = 51820
PrivateKey = CN93K+/YuYpMlQbCm0caalsRnJWU+EfP4kgU+g*****=
[Peer]
PublicKey = QKXb7WW8VdGGDLz4LMOleM/Eh8tq8fGTYnPZmf*****=
AllowedIPs = 10.0.2.2/32
PersistentKeepalive = 60
[Peer]
PublicKey =
AllowedIPs = 10.0.2.3/32
PersistentKeepalive = 60

So only the peer public key is empty, but that is correct right? Since this is the server.

Can you start WireGuard via CLI and check the output?

Could you explain to me how to do that? Probably need to ssh in and then?

I thought it kept running, but the service keeps stopping. Only see this in the logs:

Dec 10 23:07:30   kernel: wg0: link state changed to DOWN
Dec 10 23:07:30   kernel: tun0: changing name to 'wg0'

I am trying to get wireguard going using this tutorial: https://blog.linuxserver.io/2019/11/16/setting-up-wireguard-on-opnsense-android/

One of the steps I need to take is to create a new assignment for wg0, so that traffic can flow. However, when I go to assignments, wg0 is nowhere to be found. Logging in via ssh and listing all the interfaces gives me only the WAN and LAN. I installed the plugin using the System - Firmware - Plugins method.

Anyone any idea what might be going wrong here?

** Oplossing staat hier: https://forum.opnsense.org/index.php?topic=15247.msg69515#msg69515 **


Hallo daar!

Ik probeer wireguard aan de praat te krijgen middels deze tutorial: https://blog.linuxserver.io/2019/11/16/setting-up-wireguard-on-opnsense-android/

Een van de stappen is dat je een nieuwe assignment aanmaakt voor wg0, zodat het verkeer zijn weg kan vinden. Echter, ik zie onder assignments -> new nergens wg0 staan. Als ik via ssh inlog en de interfaces erbij pak, zie ik alleen WAN en LAN staan. I heb de plugin gewoon via System - Firmware - Plugins geinstalleerd. Iemand enig idee wat er verkeerd gaat? Heeft iemand dit werkend gekregen?

Added screenshots to show the actual errors:

https://ibb.co/z5sQsyD
https://ibb.co/W3PN9BJ

Hoi,

Om dit probleem op te lossen, https://forum.opnsense.org/index.php?topic=15137.0, ben ik op zoek naar een download van Opnsense 17.7. Ik kan deze echter nergens meer vinden. Heeft iemand een werkende link toevallig?

**** Opgelost! Zie https://forum.opnsense.org/index.php?topic=15135.0 ****

[** I fixed the issue, see below for the steps **]

** I fixed the issue, see below for the steps **

Not sure if the his the correct subforum, let me know I need to post this in a sub. Also posted this in the Dutch subforum.

I am trying to install Opnsense 19.7 on a Zotac CI329 Nano (https://www.zotac.com/us/product/mini_pcs/ci329-nano). Whatever I tried, I get a error 19 during the installation and end up in mountroot. I tried installing Pfsense and FreeNAS: same error. Tried installing Ubuntu 18.4.3: worked flawless the first time installing it. No problems what so ever. What I've tried so far:

1. Multiple USB sticks to rule out that 1 might be broken (even bought a new one from the store)
2. Setting set kern.cam.boot_delay="10000" or set kern.cam.boot_delay="30000" through option 3
3. Setting hw.sdhci.enable_msi=0, hint.sdhci_pci.0.disabled=1, hint.sdhci_pci.1.disabled=1 through option 3
4. Turned legacy boot on, AHCI turned on and UEFI off.
5. Tried installing 18.7, same error
6. Updated BIOS to latest version and retried all the steps mentioned above.
7. Also tried to boot from a SD card, same results.
8. Booted an USB 2.0 stick from the USB 2.0 port. Same error.

USB-sticks have been created using Rufus or physdiskwrite (as recommended on the site).

Does anyone have any tips on how to troubleshoot this further? Or solutions to use?  Maybe version 17 would work and the upgrade from there? (however, I can't find it anywhere as a download). Haven't found a way to get all the crashlogs to the USB-stick. I am about to pull out all my hair and send this box back...

** I fixed the issue**

What I did was the following:

0. Keep in mind that I updated the BIOS the version that was available on the 30th of November 2019.
1. Reset the bios to the default settings.
2. Enable legacy boot, disable UEFI boot
3. Define the internal harddrive as an SSD instead of harddrive (in the devices menu)
4. Created a live-cd/usb with gparted on it. Threw away all the partition present on the hard dive and set a new MBR (type msdos). Save and exit.
5. Went to the store, got a USB 2.0 flash drive.
6. Downloaded OPNsense-19.7-OpenSSL-vga-amd64, extracted it and "burned" it to the flash drive with Rufus.
7. Put the USB 2.0 flash drive in the single USB 2.0 slot on the back of the device.
8. Boot the machine.
8.1 Pray to Terminus or Chenghuangshen that this will work.
9. Profit! The machine boots correctly and I can install Opnsense.

[*** Opgelost! Zie https://forum.opnsense.org/index.php?topic=15137.msg68996#msg68996 voor beschrijving ***]

*** Opgelost! Zie https://forum.opnsense.org/index.php?topic=15137.msg68996#msg68996 voor beschrijving ***

Hi,

Ik probeer opnsense te draaien op een Zotac CI329 Nano (https://www.zotac.com/us/product/mini_pcs/ci329-nano). Wat ik ook probeer, ik krijg steeds de error 19 tijdens het installeren en beland ik in mountroot. Ik krijg een soortgelijke error bij het installeren van Pfsense en Freebsd. Ubuntu wordt in 1x foutloos geinstalleerd. Wat heb ik al geprobeerd:

1. Meerdere USB sticks om uit te sluiten dat 1 wellicht stuk is (maakte geen verschil)
2. Toevoegen van set kern.cam.boot_delay="10000" of set kern.cam.boot_delay="30000" middels optie 3
3. Toevoegen van hw.sdhci.enable_msi=0, hint.sdhci_pci.0.disabled=1, hint.sdhci_pci.1.disabled=1 middels optie 3
4. Legacy boot staat aan, AHCI staat aan, UEFI staat uit.
5. Bios bijgewerkt naar laatste versie.
6. Geprobeerd 18.7 te installeren, zelfde error.

Usb-sticks zijn gemaakt middels Rufus of physdiskwrite (zoals aanbevolen op Opnsense site).

Weet iemand wat ik nog meer kan proberen? Of hoe ik dit beter kan troubleshooten? Ik heb nog geen manier gevonden om de logs makkelijk over te zetten naar de usb-stick. Sta op het punt mijn haren uit te trekken en deze box terug te sturen...