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(
and ifdown(
# 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.