×

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

Bi-monthly release with minor bug fixes and improvements

Ubuntu Mate 19.04 and Astroberry

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

I bit on the move to 19.04. Now, Astroberry WAP does not give an IP address anymore. I know I ensured no config file was altered . Any conf file is in order. Apparently something has changed that now does not allow DHCP to be shared with WLAN.

DHCPCD.CONF looks fine.

WPA_SUPPLICANT.CONF looks fine.

Connect to Astroberry WAP and receive no DHCP. Hmm...

To me, I see too many WLAN0 config options. SSID = astroberryPI is listed as a configuration but nothing show up there. What a challenge. 19.04 is too new.
4 years 6 months ago #43168

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

  • Posts: 389
  • Thank you received: 15
hello.

Rest and fresh review reveals the culprit. The network for VAP is not defined. I tried to use bridge to bridge between vap0 and wlan0 explicitly. Under 16.04 and 18.04, no bridge was required. A bridge requires iptables. Here is my ifconfig output. The virtual network, vap0 , does not have a network defined. Hence, when I connect, I get the universal subnet mask of 255.255.0.0 as generated by "no, you didn't get an IP from your provider. The virtual IP wlan0 is dependent on receiving help from something. Time to build a bridge.

vap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.149.232 netmask 255.255.0.0 broadcast 169.254.255.255
inet6 fe80::7227:4587:bb11:12c3 prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:62:37:f8 txqueuelen 1000 (Ethernet)
RX packets 2249 bytes 682949 (682.9 KB)
RX errors 0 dropped 4 overruns 0 frame 0
TX packets 681 bytes 226004 (226.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b8:27:eb:62:37:f8 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
4 years 6 months ago #43180

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

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

Apparently, vap0 and wlan0 are in conflict with DHCP.CD. Ok. When upgrading from 18.04 to 19.04, the config files pushed contained wlan0 as the recipient of DHCPCD benefits. This overwrote the vap0 settings. I dutifully replaced wlan0 with vap0 to get back to normal. Sysl;og says that isn't working.

Sep 11 11:10:00 astroberry dhcpcd[526]: vap0: IAID eb:62:37:f8
Sep 11 11:10:00 astroberry dhcpcd[526]: vap0: IAID conflicts with one assigned to wlan0
Sep 11 11:10:00 astroberry dhcpcd[526]: vap0: adding address fe80::7227:4587:bb11:12c3

File structures for IPV4 and IPV6 are listed as owned by wlan0. Just removing them in a conf file does nothing to clean up the file system, Time for the wrecking ball.

This is a look from another angle. Yep. Failed is bad.

stroberry@astroberry:~$ sudo wpa_cli reconfigure
[sudo] password for astroberry:
Selected interface 'vap0'
FAIL
Last edit: 4 years 6 months ago by John Robison.
4 years 6 months ago #43200

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

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

I am happy to report; conflict has been resolved. I had to normalize INTERFACAES, HOSTPAD.CONF, DNSMASQ.CONF and DHCPCP.CONF,

INTERFACES
auto lo vap0 wlan0 MyNIC

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-conf /etc/wpa_supplicant/wpa_supplicant.conf

iface wlan0 inet manual
iface MyNIC inet manual

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

DNSMASQ.CONF

interface=vap0


DHCPCP.CONF,

interface vap0
static ip_address=192.168.10.1/24
static routers=192.168.10.1
static domain_name_servers=192.168.10.1
The following user(s) said Thank You: Radek Kaczorek
4 years 6 months ago #43204

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

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

For certain, Moving to 19.04 was a good choice. The boot time is significant more faster. I will be interested to see the number of apps migrating to be 19.04 compliant.
4 years 6 months ago #43205

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

  • Posts: 62
  • Thank you received: 10
I would agree, but I see several strange issues:

screen resolution suddenly very low,
PHD2 guiding became really, really bad, still works though (related to screen resolution issue???)
Filter change creates hangups almost nightly. NO: nightly
post flip alignment hangs on occasion
and my iMac has to think a lot more for some reason, as documented by the cooling fan coming on, which it didn't need before
and there is more....

about to revert to my old setup...

Any behavioral changes in your setup?

Thanks
4 years 4 months ago #45865

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

Time to create page: 0.645 seconds