Omega 2S+: No WiFi Support with OpenWRT 21.02
-
@IBH said in Omega 2S+: No WiFi Support with OpenWRT 21.02:
image right
@crispyoz I've managed and fixed the issue by getting the hostapd, the wifi is up now , I can my SSSID in the list of the WiFi but I couldn't connect on it . Do I need to make some other configuration?
This my wifi status:root@OpenWrt:/# wifi status { "radio0": { "up": true, "pending": false, "autostart": true, "disabled": false, "retry_setup_failed": false, "config": { "path": "platform/10300000.wmac", "channel": "1", "band": "2g", "htmode": "HT20", "disabled": false }, "interfaces": [ { "section": "default_radio0", "ifname": "wlan0", "config": { "mode": "ap", "ssid": "OpenWrt", "encryption": "none", "network": [ "lan" ], "mode": "ap" }, "vlans": [ ], "stations": [ ] } ] } }
-
@IBH When you try to connect to the hotspot and it fails, what error are you getting? type logread and look for any errors reported by hostapd.
-
@crispyoz I got this:
Sun Apr 23 12:18:53 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED fa:89:87:9c:e5:ee Sun Apr 23 12:19:12 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED fa:89:87:9c:e5:ee Sun Apr 23 12:19:12 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: disassociated Sun Apr 23 12:19:13 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) Sun Apr 23 12:19:24 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: authenticated Sun Apr 23 12:19:24 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: associated (aid 1) Sun Apr 23 12:19:24 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED fa:89:87:9c:e5:ee Sun Apr 23 12:19:45 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED fa:89:87:9c:e5:ee Sun Apr 23 12:19:45 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: authenticated Sun Apr 23 12:19:45 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: associated (aid 1) Sun Apr 23 12:19:45 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED fa:89:87:9c:e5:ee Sun Apr 23 12:22:32 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED fa:89:87:9c:e5:ee Sun Apr 23 12:22:32 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: disassociated Sun Apr 23 12:22:33 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) Sun Apr 23 12:22:39 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: authenticated Sun Apr 23 12:22:39 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: associated (aid 1) Sun Apr 23 12:22:39 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED fa:89:87:9c:e5:ee Sun Apr 23 12:22:51 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED fa:89:87:9c:e5:ee Sun Apr 23 12:22:51 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: disassociated Sun Apr 23 12:22:52 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
-
@crispyoz I could now connect to the OpenWrt ssid but with no internet connection. Do you have any idea please why?
There is my logs:Sun Apr 23 12:36:15 2023 kern.info kernel: [ 1010.402205] br-lan: port 2(wlan0) entered blocking state Sun Apr 23 12:36:15 2023 kern.info kernel: [ 1010.408376] br-lan: port 2(wlan0) entered disabled state Sun Apr 23 12:36:15 2023 kern.info kernel: [ 1010.415584] device wlan0 entered promiscuous mode Sun Apr 23 12:36:15 2023 kern.info kernel: [ 1010.571804] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Sun Apr 23 12:36:15 2023 kern.info kernel: [ 1010.578739] br-lan: port 2(wlan0) entered blocking state Sun Apr 23 12:36:15 2023 kern.info kernel: [ 1010.585353] br-lan: port 2(wlan0) entered forwarding state Sun Apr 23 12:36:15 2023 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->ENABLED Sun Apr 23 12:36:15 2023 daemon.notice hostapd: wlan0: AP-ENABLED Sun Apr 23 12:36:17 2023 daemon.notice netifd: Wireless device 'radio0' is now up Sun Apr 23 12:36:17 2023 daemon.notice netifd: Network device 'wlan0' link is up Sun Apr 23 12:36:18 2023 daemon.err onionApp[5184]: + exec Sun Apr 23 12:36:20 2023 daemon.info dnsmasq[2786]: read /etc/hosts - 4 addresses Sun Apr 23 12:36:20 2023 daemon.info dnsmasq[2786]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses Sun Apr 23 12:36:20 2023 daemon.info dnsmasq[2786]: read /tmp/hosts/odhcpd - 0 addresses Sun Apr 23 12:36:20 2023 daemon.info dnsmasq-dhcp[2786]: read /etc/ethers - 0 addresses Sun Apr 23 12:36:28 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: authenticated Sun Apr 23 12:36:28 2023 daemon.info hostapd: wlan0: STA fa:89:87:9c:e5:ee IEEE 802.11: associated (aid 1) Sun Apr 23 12:36:28 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED fa:89:87:9c:e5:ee Sun Apr 23 12:36:28 2023 daemon.info dnsmasq-dhcp[2786]: DHCPREQUEST(br-lan) 192.168.3.225 fa:89:87:9c:e5:ee Sun Apr 23 12:36:28 2023 daemon.info dnsmasq-dhcp[2786]: DHCPACK(br-lan) 192.168.3.225 fa:89:87:9c:e5:ee root@OpenWrt:/#
-
@IBH This is covered in the docs
-
@crispyoz Hi, I don't have the wifisetup command :
root@OpenWrt:/# wifisetup
/bin/ash: wifisetup: not found
-
@crispyoz Could you please share your /etc/config/firewall file?
root@OpenWrt:/# cat /tmp/dhcp.leases
1682298022 32:e8:eb:f4:bf:dd 192.168.3.249 * 01:32:e8:eb:f4:bf:dd
-
@Lazar-Demin Now, I have the wifi AP , I can connect my phone to onion wifi but with no internet connection. I've checked the firewall configuration and it looks like the doc shared by @crispyoz .Also I got this output :
root@OpenWrt:/# cat /tmp/dhcp.leases 1682298022 32:e8:eb:f4:bf:dd 192.168.3.249 * 01:32:e8:eb:f4:bf:dd
Any help please?
-
@IBH How is your Omega connected to the internet? Ethernet or wifi?
Like I mentioned in another thread, you should expect that a lot of the existing Omega2 documentation probably won't work out of the box on the new beta firmware (or any firmware based on newer OpenWRT versions).
So while firmware based on newer openwrt doesn't have the Onion-specific
wifisetup
utility, the same concepts will apply. Meaning you should still check that your firewall is configured to allow input, output, and forwarding between the network interface with the internet connection and the Omega's Wi-Fi AP.Let us know how it goes.
-
@IBH I think this is the key firewall rule:
config zone
option name 'wan'
list network 'wan'
list network 'wwan'
option output 'ACCEPT'
option masq '1'
option mtu_fix '1'
option input 'ACCEPT'
option forward 'ACCEPT'It causes masquerading of the sta through the ap.