×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

vap0 and 19.04.2

  • Posts: 389
  • Thank you received: 15
Hello,

Looks vap0 is no longer working. I started from check-wlanconn.

Virtual Access Point STARTED
astroberry@astroberry:~$ sudo /usr/local/bin/astroberry_wireless
Checking if connected to AP.......... Not connected
Trying to connect to known AP
command failed: No such device (-19)
Starting Virtual Access Point
command failed: No such device (-19)
SIOCSIFADDR: No such device
vap0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
vap0: ERROR while getting interface flags: No such device
vap0: ERROR while getting interface flags: No such device
Configuration file: /etc/hostapd/hostapd.conf
Could not read interface vap0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=vap0 disabled_11b_rates=0
Could not read interface vap0 flags: No such device
nl80211 driver initialization failed.
vap0: interface state UNINITIALIZED->DISABLED
vap0: AP-DISABLED
hostapd_free_hapd_data: Interface vap0 wasn't started
Job for dnsmasq.service failed because the control process exited with error code.
See "systemctl status dnsmasq.service" and "journalctl -xe" for details.
Virtual Access Point READY

I was just starting to use new settings. I normalized all conf files and noting changed except for dnsmasq.conf. The interface=vap0 was missing after an update. I added it back and restarted. I still do not have wireless.

astroberry@astroberry:~$ systemctl status dnsmasq.service
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset:
Active: failed (Result: exit-code) since Thu 2019-10-17 20:34:50 EDT; 7min ag
Process: 2199 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=1/FAI

Oct 17 20:34:50 astroberry.local systemd[1]: Starting dnsmasq - A lightweight DH
Oct 17 20:34:50 astroberry.local dnsmasq[2199]: dnsmasq: bad option at line 667
Oct 17 20:34:50 astroberry.local dnsmasq[2199]: bad option at line 667 of /etc/d
Oct 17 20:34:50 astroberry.local dnsmasq[2199]: FAILED to start up
Oct 17 20:34:50 astroberry.local systemd[1]: dnsmasq.service: Control process ex
Oct 17 20:34:50 astroberry.local systemd[1]: dnsmasq.service: Failed with result
Oct 17 20:34:50 astroberry.local systemd[1]: Failed to start dnsmasq - A lightwe

I am still investigating the mashup of the latest Ubuntu-mate update. I forgot to add the "=" sign.
4 years 5 months ago #44741

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15

Replied by John Robison on topic vap0 and 19.04.2

Hello,

With the syntax error corrected, the dnsmasq still has problems with vap0.

stroberry@astroberry:~$ systemctl status dnsmasq.service
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset:
Active: failed (Result: exit-code) since Thu 2019-10-17 20:48:38 EDT; 10s ago
Process: 1643 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUC
Process: 1644 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=

Oct 17 20:48:56 astroberry dnsmasq[1798]: dnsmasq: syntax check OK.
Oct 17 20:48:56 astroberry dnsmasq[1799]: dnsmasq: unknown interface vap0
Oct 17 20:48:56 astroberry dnsmasq[1799]: unknown interface vap0
Oct 17 20:48:56 astroberry dnsmasq[1799]: FAILED to start up
Oct 17 20:48:56 astroberry systemd[1]: dnsmasq.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Oct 17 20:48:56 astroberry systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
Oct 17 20:48:56 astroberry systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.

ok, This might be the smoking gun.

Oct 17 20:47:38 astroberry NetworkManager[505]: <info> [1571359658.0063] ifupdown: interface-parser: parsing file /etc/network/interfaces
Oct 17 20:47:38 astroberry NetworkManager[505]: <info> [1571359658.0065] ifupdown: interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d
Oct 17 20:47:38 astroberry NetworkManager[505]: <info> [1571359658.0067] ifupdown: interface-parser: finished parsing file /etc/network/interfaces
Oct 17 20:47:38 astroberry NetworkManager[505]: <info> [1571359658.0156] ifupdown: No dns-nameserver configured in /etc/network/interfaces
Oct 17 20:47:38 astroberry NetworkManager[505]: <warn> [1571359658.0172] ifupdown: invalid connection read from /etc/network/interfaces: 802-11-wireless.ssid: property is missing

Something must be explicitly stated. This would mean some of the stated solutions will need to be updated to 19.04.2 standards. However, the wpaconf file has those details in it. Somehow the conf file may not be parsed properly. This has specific details about vlan0. Uggh. change happens to all good things.

This says that wpa_supplicant was initiated. However, /var/run/wpa_supplicant no longer exists. I guess something got whacked during an upgrade.

astroberry wpa_supplicant[506]: Successfully initialized wpa_supplicant

astroberry@astroberry:~$ sudo /var/run/wpa_supplicant GROUP=netdev
[sudo] password for astroberry:
env: '/var/run/wpa_supplicant': No such file or directory
astroberry@astroberry:~$ ls /var/run/wpa_supplicant
ls: cannot access '/var/run/wpa_supplicant': No such file or directory
astroberry@astroberry:~$ ls /var/run/
NetworkManager dhcpcd.unpriv.sock openvpn-client sshd
agetty.reload dnsmasq openvpn-server sshd.pid
alsa gpsd.sock plymouth sudo
avahi-daemon initctl resolvconf systemd
avahi-dnsconfd.pid lightdm rsyslogd.pid thd.socket
console-setup lightdm.pid samba tmpfiles.d
crond.pid lock sendsigs.omit.d udev
crond.reboot log shm udisks2
cups mount snapd-snap.socket user
dbus network snapd.socket utmp
dhcpcd.pid nginx.pid speech-dispatcher uuidd
dhcpcd.sock openvpn spice-vdagentd xtables.lock
astroberry@astroberry:~$

Where would someone get the wpa_supplicant?
4 years 5 months ago #44744

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15

Replied by John Robison on topic vap0 and 19.04.2

Hello,

Unwrapping an onion is tough. Ok. Now, wpa _supplicant is showing up in the logs. However, interfaces has some problems.

Oct 17 19:41:46 astroberry wpa_supplicant[480]: Successfully initialized wpa_supplicant
Oct 17 20:16:25 astroberry wpa_supplicant[480]: Successfully initialized wpa_supplicant
Oct 17 20:47:37 astroberry wpa_supplicant[506]: Successfully initialized wpa_supplicant
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: Successfully initialized wpa_supplicant
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: Could not read interface wlan0 flags: No such device
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: nl80211: Driver does not support authentication/association or connect commands
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: Could not read interface wlan0 flags: No such device
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: rfkill: Cannot get wiphy information
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: Could not read interface wlan0 flags: No such device
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: WEXT: Could not set interface 'wlan0' UP
Oct 17 21:16:30 astroberry wpa_supplicant[3735]: wlan0: Failed to initialize driver interface
Oct 17 21:23:37 astroberry wpa_supplicant[458]: Successfully initialized wpa_supplicant
Oct 17 21:23:37 astroberry wpa_supplicant[478]: Successfully initialized wpa_supplicant

I removed wlan0 as the device is not on my RPI3B+. I will see if this clears up these errors. I copied from this site what as verified as working Now it isn't.
Last edit: 4 years 5 months ago by John Robison. Reason: Syntax correction
4 years 5 months ago #44747

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15

Replied by John Robison on topic vap0 and 19.04.2

Hello,

Nearing an end. Which, we will see tomorrow. This is the result of 'journelctl -ex'. Failed are the results. Tomorrow. Next clear night is several days away.

-- An ExecStart= process belonging to unit dnsmasq.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 2.
Oct 17 22:23:35 astroberry.local dnsmasq[2435]: FAILED to start up
Oct 17 22:23:35 astroberry.local systemd[1]: dnsmasq.service: Failed with result
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: www.ubuntu.com/support
--
-- The unit dnsmasq.service has entered the 'failed' state with result 'exit-cod
Oct 17 22:23:35 astroberry.local systemd[1]: Failed to start dnsmasq - A lightwe
-- Subject: A start job for unit dnsmasq.service has failed
-- Defined-By: systemd
-- Support: www.ubuntu.com/support
--
-- A start job for unit dnsmasq.service has finished with a failure.
--
-- The job identifier is 1366 and the job result is failed.
Oct 17 22:23:35 astroberry.local sudo[2297]: pam_unix(sudo:session): session clo

Here are the error codes.

Oct 17 22:17:08 astroberry dnsmasq[1712]: dnsmasq: syntax check OK.
Oct 17 22:17:08 astroberry dnsmasq[1713]: dnsmasq: unknown interface vap0
Oct 17 22:17:08 astroberry dnsmasq[1713]: unknown interface vap0
Oct 17 22:17:08 astroberry dnsmasq[1713]: FAILED to start up
Oct 17 22:17:08 astroberry systemd[1]: dnsmasq.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Oct 17 22:17:08 astroberry systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
Oct 17 22:17:08 astroberry systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.

Notice no line other than vap0 is the reference. The vap0 is not loaded which causes dnsmasq to quit.
Last edit: 4 years 5 months ago by John Robison.
4 years 5 months ago #44750

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15

Replied by John Robison on topic vap0 and 19.04.2

Hello,

Apparently, the wireless device appears down. Here is an excerpt from "journalctl -e".

astroberry@astroberry:~$ journalctl -e | grep "vap0"
Oct 18 16:00:42 astroberry.local ifup[597]: Cannot find device "vap0"
Oct 18 16:00:42 astroberry.local ifup[597]: ifup: failed to bring up vap0
Oct 18 16:00:42 astroberry.local NetworkManager[461]: <info> [1571428842.1409] ifupdown: guessed connection type (vap0) = 802-3-ethernet
Oct 18 16:00:42 astroberry.local NetworkManager[461]: <info> [1571428842.1411] ifupdown: update_connection_setting_from_if_block: name:vap0, type:802-3-ethernet, id:Ifupdown (vap0), uuid: b77903f0-c28d-8b04-0e87-b3cba551dbae
Oct 18 16:00:42 astroberry.local NetworkManager[461]: <info> [1571428842.1475] ifupdown: guessed connection type (vap0) = 802-11-wireless
Oct 18 16:00:42 astroberry.local NetworkManager[461]: <info> [1571428842.1477] ifupdown: update_connection_setting_from_if_block: name:vap0, type:802-11-wireless, id:Ifupdown (vap0), uuid: b77903f0-c28d-8b04-0e87-b3cba551dbae
Oct 18 16:00:42 astroberry.local NetworkManager[461]: <info> [1571428842.1477] ifupdown: update wireless settings (vap0).
Oct 18 16:00:42 astroberry.local NetworkManager[461]: <info> [1571428842.1483] ifupdown: update wireless security settings (vap0).

This has me stumped. To me vap0 is not tied to a hardware device. The hardware device tie-in is defined in hostapd. So, vap0 is not getting linked to a device. Syslog and journalctl are not finding an hostapd messages. More digging to come.

Here is the other stumping item. How is it the eth0 has been deprecated in Ubuntu-Mate, yet, I have this in the logs.

Oct 18 16:00:41 astroberry.local kernel: lan78xx 1-1.1.1:1.0 enxb827eb3762ad: renamed from eth0
Oct 18 16:00:39 astroberry.local dhcpcd[439]: dhcpcd_prestartinterface: eth0: No such device
Oct 18 16:00:39 astroberry.local dhcpcd[439]: eth0: unknown carrier, waiting for interface flags
Oct 18 16:00:41 astroberry.local dhcpcd[439]: dhcpcd_prestartinterface: eth0: No such device
Oct 18 16:00:41 astroberry.local dhcpcd[439]: eth0: unknown carrier, waiting for interface flags
Oct 18 16:00:41 astroberry.local dhcpcd[439]: enxb827eb3762ad: IAID conflicts with one assigned to eth0
Oct 18 16:00:40 astroberry.local dhcpcd[439]: enxb827eb3762ad: IAID conflicts with one assigned to eth0
Oct 18 16:07:15 astroberry.local dhcpcd[1016]: eth0: removing interface


hostapd.conf

interface=vap0
driver=nl80211
country_code=US
ssid=astroberry
hw_mode=g
ieee80211n=1
channel=6
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=astroberry
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP

interfaces

# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

# The loopback network interface

#auto lo vap0 wlan0 enxb827eb3762ad
auto lo vap0 enxb827eb3762ad

iface lo inet loopback

iface vap0 inet static
address 192.168.10.1
network 192.168.10.0
netmask 255.255.255.0


allow-hotplug vap0
iface vap0 inet dhcp
wpa-ssid astroberry
dns-nameserver 192.168.10.1

wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

#iface wlan0 inet manual
iface enxb827eb3762ad inet manual

#auto wlan1
#iface wlan1 inet static
#address 192.168.10.1
#netmask 255.255.255.0

wpa_supplicant.conf (by the way, ctrl_interface does not exist.)

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=00

network={
scan_ssid=1
ssid="astroberry"
psk="astroberry"
}

if Syntax is now more strict, this could explain why vap0 is not being setup.

ifconfig -a

astroberry@astroberry:~$ ifconfig -a
enxb827eb3762ad: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.200.26 netmask 255.255.255.0 broadcast 192.168.200.255
inet6 fe80::e04a:2e47:f180:98a7 prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:37:62:ad txqueuelen 1000 (Ethernet)
RX packets 3505 bytes 2006909 (2.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3553 bytes 438246 (438.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 805 bytes 71294 (71.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 805 bytes 71294 (71.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

No vap0 is listed. Under Advanced Network Configuration, I created a vap0 interface. Before I had a wlan0. Neither show up in ifconfig. Which makes me wonder, what Advanced Network Configuration actually does. To me, it does nothing but create a file that does not get used by anything.
Last edit: 4 years 5 months ago by John Robison.
4 years 5 months ago #44790

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15

Replied by John Robison on topic vap0 and 19.04.2

Hello,

Finally, I have the smoking gun. Unmasking hostapd, allowed me to look under the covers. It is a mess.

Oct 18 17:04:09 astroberry.local systemd[1]: hostapd.service: Service RestartSec=2s expired, scheduling restart.
Oct 18 17:04:09 astroberry.local systemd[1]: hostapd.service: Scheduled restart job, restart counter is at 20.
-- Automatic restarting of the unit hostapd.service has been scheduled, as the result for
-- Subject: A stop job for unit hostapd.service has finished
-- A stop job for unit hostapd.service has finished.
-- Subject: A start job for unit hostapd.service has begun execution
-- A start job for unit hostapd.service has begun execution.
Oct 18 17:04:09 astroberry.local hostapd[7987]: Configuration file: /etc/hostapd/hostapd.conf
Oct 18 17:04:09 astroberry.local hostapd[7987]: Could not read interface vap0 flags: No such device
Oct 18 17:04:09 astroberry.local hostapd[7987]: nl80211: Driver does not support authentication/association or connect commands
Oct 18 17:04:09 astroberry.local hostapd[7987]: nl80211: deinit ifname=vap0 disabled_11b_rates=0
Oct 18 17:04:09 astroberry.local hostapd[7987]: Could not read interface vap0 flags: No such device
Oct 18 17:04:09 astroberry.local hostapd[7987]: nl80211 driver initialization failed.
Oct 18 17:04:09 astroberry.local hostapd[7987]: vap0: interface state UNINITIALIZED->DISABLED
Oct 18 17:04:09 astroberry.local hostapd[7987]: vap0: AP-DISABLED
Oct 18 17:04:09 astroberry.local hostapd[7987]: hostapd_free_hapd_data: Interface vap0 wasn't started
Oct 18 17:04:09 astroberry.local systemd[1]: hostapd.service: Control process exited, code=exited, status=1/FAILURE
-- An ExecStart= process belonging to unit hostapd.service has exited.
Oct 18 17:04:09 astroberry.local systemd[1]: hostapd.service: Failed with result 'exit-code'.
-- The unit hostapd.service has entered the 'failed' state with result 'exit-code'.
-- Subject: A start job for unit hostapd.service has failed
-- A start job for unit hostapd.service has finished with a failure.


Using the tool scripts does not change this issue.
4 years 5 months ago #44794

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15

Replied by John Robison on topic vap0 and 19.04.2

Update

After multiple effort attempts, I have come to the conclusion that vap0 is a shim created by some process. Hostapd is now at version 3.9. IEEE80211N optioon is no longer required.

I have now gone back to the FAQ and looked up Raspberry PI. I relooked at what client I had on my iPAD/iPhone and installed the latest RealVNC. I am now back in business. Apparently, an update from UBUNTU-MATE whacked RealVNC. Now, I am at UBUNTU-MATE 19.10.

Thank you.
Last edit: 4 years 5 months ago by John Robison.
4 years 5 months ago #44993

Please Log in or Create an account to join the conversation.

  • Posts: 983
  • Thank you received: 375

Replied by Radek Kaczorek on topic vap0 and 19.04.2

Please upgrade to Astroberry 2.0.0 - www.astroberry.io/
4 years 3 months ago #46842

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15

Replied by John Robison on topic vap0 and 19.04.2

Hello,

Thank you for the reply. I substituted wlan0 for vap0. I also installed RealVNC. Everything is 90% working. I have to hardwire the AstroBerry network into my iPad network connection, e.g. manual. Everything VPN works on AB 1.1 with RealVNC.

I have toyed with AB 2.01. I kicked the tires so to say. If I see the need for an RPI 4, I will use AB 2.01.

At the present, AB 1.1 has the Debug tools necessary to validate and explicitly defined a problem. Under AB 2.01, INDI devices have DEBUG disabled.

Sometimes, updates break things. Finding root cause is better than being frustrated and denigrating the team and package. Nothing gets better being frustrated and angry.
Last edit: 4 years 3 months ago by John Robison. Reason: Syntax
4 years 3 months ago #46872

Please Log in or Create an account to join the conversation.

Moderators: Radek Kaczorek
Time to create page: 1.291 seconds