Debugging

Warnings

Antennas automatically updates to the latest version. When it does so, all of its services are restarted. This causes a roughly 30 second drop in wireless connection. Therefore, what you though was a bug might just be your system updating. Care is taken to batch up releases to prevent frequent downtime.

Using the network-manager snap is not recommended. It and other snaps that manipulate the system networking may or may not conflict with Antennas.

Tips

View all logs with snap logs -n=all antennas or view the latest logs of a specific service with snap logs -n=99 antennas.hostapd. You can increase the verbosity of logs that are available to view by enabling Antennas's debug mode with sudo antennas.config set --debug true. It is not recommended to leave debug mode on when not debugging.

To debug an Antennas build you can inspect it after building with snapcraft build --shell. Within the container you can see the state of various steps in the snap lifecycle. For example, go to /root/staging to see bin, sbin, and /usr/bin for your staged package binaries.

To debug an installed Antennas snap your can inspect it after installing with snap run --shell antennas.hostapd (where "hostapd" is the service). From there you can run commands like printenv.

To debug permissions check if permissions are assigned with snap connections antennas. Check if its using something protected by permissions with the snappy-debug snap or by checking dmesg.

To check what is inside the compressed snap, run unsquashfs ./antennas_1_arm64.snap.

To check port usage on Ubuntu Core, run sudo ss -lpnut.