I just read Connect WiFi — BeagleBoard Documentation and want to keep that function to test for possible webpage application, but for now I would prefer to use wifi for local network client. What would be needed to do? Also, are all three 2.4/5GHz antenna shared by active wifi program?
Upon reading again, it would appear all I need to do is configure a client. Would the Ap persist with client connected to another network?
WL1837 used on BeaglePlay supports concurrent AP and client connections…
Regards,
Thanks, not touching BPay to plugin antennas to configure now because kernel build as directed going.
The BeaglePlay wifi AP, but I don’t get wlan0 as user and sudo wpa_gui has missing qt thingies. When I nano edit the /etc/wpa_supplicant/wpa_supplicant-wlan0.conf as
country=US
ctrl_interface=DIR=/var/run/wpa_supplicant
update_config=1
network={
ssid="BeagleBone-WXYZ"
psk="xxxxxxxxxx"
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
auth_alg=OPEN
mesh_fwding=1
}
no changes occur with reboot or sudo systemctl start wpa_supplicant. Not yet to configure local network client(not AP). Lost.
The BeaglePlay default wifi AP does work with default password, and does not change with cli change.
The BeaglePlay’s SoftAp0 AP credentials are stored in: (for boards wanting to connect into the BeaglePlay)
/etc/hostapd/hostapd.conf
Just edit them and restart hostapd.service
Early boards had:
ssid=BeagleBone-WXYZ
wpa_passphrase=BeagleBone
Where the WXYZ should be replaced by a 4 mac address digits… (BUG, looks it doesn’t…)
Then
BeagleBone → BeaglePlay
So new images are:
ssid=BeaglePlay-WXYZ
wpa_passphrase=BeaglePlay
Regards,
Thanks. If I wanted the BeaglePlay to connect to my local private network would it then be what to use?
The AP is up as prescribed, but I get nothing in wpa_gui. Is there something I need to install or do?
Present setup allows hostapd running AP with BPLAY4DCA addressable from a Windows 10 computer via wifi at 192.168.8.1. Ethernet eth0 is dhcp from home router with internet access on a network 192.168.1.X. This could work as is for testing as I need to connect via wifi only to BPLAY4DCA in hardware application test that would have no ethernet. However, it would not have internet access to updates without eth0. So, question is how to connect to home router for dhcp with wifi client only, or how to configure hostapd to use router as default gateway?
I would also add there is a ruckus getting dhcp values for clients from the router, and if BPlay were to be without eth0, I would think this would be the place it would connectas a client.
How do I get wpagui in Internet to not say "Could not get status from wpa_supplicant?
Does anyone have a default hostapd.conf?
Our copy is under: /etc/bbb.io/templates/bb-hostapd.conf
Maybe… can you please re-explain your hardware and connection map?
Which devices in a generic map, who talks to who, over what kinda of link?
Regards,
I had just got the hostapd.conf off of eMMC to fix mistake I made. What I am trying to do is connect to a wifi AP in my network and not be a hostapd. The Internet-> wpagui does not report anything when told to scan.
I have two network connection points, WR000150(5GHz) and WR0001(2.4GHz), router provides gateway and dhcp.
IDK, it looks like the wpa_gui tool broke…
So using the latest image: Debian Bullseye Xfce Image 2023-08-05
So over serial we see:
debian@BeaglePlay:~$ sudo beagle-version
eeprom:[BEAGLEPLAY-A0-02007801030101640723005162SSSS]
model:[BeagleBoard.org_BeaglePlay]
dogtag:[BeagleBoard.org Debian Bullseye Xfce Image 2023-08-05]
So doing it the normal way, Connect to my testing WiFi network:
debian@BeaglePlay:~$ cat /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
ctrl_interface=DIR=/run/wpa_supplicant GROUP=netdev
update_config=1
p2p_disabled=1
country=US
network={
ssid="BeagleBone"
psk="BeagleBone"
}
Reboot:
debian@BeaglePlay:~$ journalctl -b 0 -k -g wlan
-- Journal begins at Sun 2023-06-18 14:55:54 UTC, ends at Sun 2023-08-13 20:22:51 UTC. --
Aug 13 20:20:16 BeaglePlay kernel: wlan_en: supplied by vdd_3v3
Aug 13 20:20:28 BeaglePlay kernel: wlan0: authenticate with c2:fb:e4:f5:7b:d2
Aug 13 20:20:28 BeaglePlay kernel: wlan0: send auth to c2:fb:e4:f5:7b:d2 (try 1/3)
Aug 13 20:20:28 BeaglePlay kernel: wlan0: authenticated
Aug 13 20:20:28 BeaglePlay kernel: wlan0: associate with c2:fb:e4:f5:7b:d2 (try 1/3)
Aug 13 20:20:28 BeaglePlay kernel: wlan0: RX AssocResp from c2:fb:e4:f5:7b:d2 (capab=0x1511 status=0 aid=1)
Aug 13 20:20:28 BeaglePlay kernel: wlan0: associated
Aug 13 20:20:28 BeaglePlay kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Aug 13 20:20:28 BeaglePlay kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by c2:fb:e4:f>
debian@BeaglePlay:~$ sudo ifconfig -a
SoftAp0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.8.1 netmask 255.255.255.0 broadcast 192.168.8.255
inet6 fe80::6e30:2aff:fe0a:dad3 prefixlen 64 scopeid 0x20<link>
ether 6c:30:2a:0a:da:d3 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 49 bytes 8964 (8.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:0f:e4:93:c2 txqueuelen 0 (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
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 34:08:e1:85:0a:11 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
eth1: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 3a:41:56:1f:32:9d 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
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 210 bytes 18665 (18.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 210 bytes 18665 (18.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lowpan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1280
inet6 fe80::212:4b00:29b9:9884 prefixlen 64 scopeid 0x20<link>
unspec 00-12-4B-00-29-B9-98-84-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 26 bytes 3860 (3.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
usb0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 1c:ba:8c:a2:ed:6b 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
usb1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 1c:ba:8c:a2:ed:6d 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
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.66 netmask 255.255.252.0 broadcast 192.168.3.255
inet6 fe80::6e30:2aff:fe0a:dad2 prefixlen 64 scopeid 0x20<link>
ether 6c:30:2a:0a:da:d2 txqueuelen 1000 (Ethernet)
RX packets 13307 bytes 17007068 (16.2 MiB)
RX errors 0 dropped 117 overruns 0 frame 0
TX packets 5240 bytes 522445 (510.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wpan0: flags=130<BROADCAST,NOARP> mtu 123
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 300 (UNSPEC)
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
wpan1: flags=195<UP,BROADCAST,RUNNING,NOARP> mtu 123
unspec 00-12-4B-00-29-B9-98-84-00-00-00-00-00-00-00-00 txqueuelen 300 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 42 bytes 3696 (3.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
networkctl
debian@BeaglePlay:~$ sudo networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 ether no-carrier configuring
3 eth1 ether off unmanaged
4 wpan0 ieee802154 off unmanaged
5 wpan1 ieee802154 carrier unmanaged
6 lowpan0 6lowpan degraded unmanaged
7 wlan0 wlan routable configured
8 SoftAp0 wlan routable configured
9 docker0 bridge no-carrier unmanaged
10 usb0 gadget no-carrier configuring
11 usb1 gadget no-carrier configuring
11 links listed.
route
debian@BeaglePlay:~$ sudo route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default unifi.gfnd.rcn- 0.0.0.0 UG 1024 0 0 wlan0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
192.168.0.0 0.0.0.0 255.255.252.0 U 0 0 0 wlan0
unifi.gfnd.rcn- 0.0.0.0 255.255.255.255 UH 1024 0 0 wlan0
192.168.8.0 0.0.0.0 255.255.255.0 U 0 0 0 SoftAp0
and we see the world…
debian@BeaglePlay:~$ ping -c3 www.google.com
PING www.google.com (142.250.190.132) 56(84) bytes of data.
64 bytes from ord37s36-in-f4.1e100.net (142.250.190.132): icmp_seq=1 ttl=57 time=26.1 ms
64 bytes from ord37s36-in-f4.1e100.net (142.250.190.132): icmp_seq=2 ttl=57 time=32.5 ms
64 bytes from ord37s36-in-f4.1e100.net (142.250.190.132): icmp_seq=3 ttl=57 time=45.4 ms
--- www.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 26.097/34.663/45.386/8.021 ms
So wpa_gui is broken, do it the old way with /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
Regards,
Thank you!
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.76 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::6e30:2aff:fe0b:8373 prefixlen 64 scopeid 0x20
ether 6c:30:2a:0b:83:73 txqueuelen 1000 (Ethernet)
RX packets 613 bytes 104045 (101.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 55 bytes 12705 (12.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Do I need more specific “configuring” for wlan0 than ssid an password so it’s not configuring and no carrier? It certainly works as is.
sudo networkctl -a
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 ether no-carrier configuring
3 eth1 ether no-carrier unmanaged
4 wpan0 ieee802154 off unmanaged
5 wpan1 ieee802154 carrier unmanaged
6 lowpan0 6lowpan degraded unmanaged
7 wlan0 wlan no-carrier configuring
8 SoftAp0 wlan routable configured
9 usb0 gadget routable configured
10 usb1 gadget no-carrier configuring
11 docker0 bridge no-carrier unmanaged
11 links listed.
Do you have the Antenna’s plugged in?
Check journalctl for connection issues:
journalctl -b 0 -k -g wlan0
Regards,
All 3 wifi, no sub G:
$ sudo journalctl -b 0 -k -g wlan0
– Journal begins at Thu 2023-08-03 19:10:30 UTC, ends at Sun 2023-08-13 22:55:12 UTC. –
– No entries –