FATA[0001] no such device about nebula HOT 12 CLOSED

The tun driver is loaded automagically on Arch.
However, users upgrading their system might prevent that from happening - when the upgrade pulls in a newer kernel, the old modules for the running kernel are discarded.
Given that a reboot was part of the issue resolution, this very well could've been what happened.

from nebula.

@msmarks can you give us more of the log output?

from nebula.

I had this problem when I tried to run on Arch (also on a RPI), using Ubuntu worked fine so I think this is a problem with how some operating systems create tun interfaces.

from nebula.

@nbrownus When I got this there was no other output, is there a verbose mode I could try?

from nebula.

@obelisk you can set the loglevel to debug in the config.yml file.

from nebula.

@obelisk It's got nothing to do with Arch directly. I'm running it just fine on there.

from nebula.

I will grab some logs and report back!

from nebula.

Changing to debug resulted in no new log lines related to FATA[0000] no such device

from nebula.

Fixed by:

pacman -Syu
<reboot>
modprobe tun
nebula -config /etc/nebula/config.yml

from nebula.

I wonder if the tun device is not loaded automagically on arch.
Mind trying modprobe -a tun and then running again?

from nebula.

@coderobe That seems likely because I'd done a pacman -Syu about an hour before I tried to use Nebula which probably updated the kernel.

from nebula.

Next release will have an improved error message for this, thanks for reporting!

from nebula.