While starting wimoved in OpenWRT 22.03, the following issue is seen. Could you provid

Issues starting wimoved about wimoved HOT 6 CLOSED

wimove-oss commented on June 11, 2024

Issues starting wimoved

from wimoved.

Comments (6)

rubensfig commented on June 11, 2024

Sorry for the early bug report. It appears that the deamon is working on the background, and the previous message encountered is related to starting the second instance in the foreground.

However, a second issue was found. When connecting to the stations, it appears hostapd is not able to create the vlan interface. The debug log is

Wed Jun  7 16:13:50 2023 daemon.info hostapd: wlan0: STA 42:7e:de:b5:fe:b5 RADIUS: VLAN ID 4096
Wed Jun  7 16:13:50 2023 kern.info kernel: [ 1802.246632] br-lan: port 6(wlan0.4096) entered blocking state
Wed Jun  7 16:13:50 2023 kern.info kernel: [ 1802.252507] br-lan: port 6(wlan0.4096) entered disabled state
Wed Jun  7 16:13:50 2023 kern.info kernel: [ 1802.258520] device wlan0.4096 entered promiscuous mode
Wed Jun  7 16:13:50 2023 kern.info kernel: [ 1802.263836] br-lan: port 6(wlan0.4096) entered blocking state
Wed Jun  7 16:13:50 2023 daemon.info hostapd: wlan0: STA 42:7e:de:b5:fe:b5 IEEE 802.11: authenticated
Wed Jun  7 16:13:50 2023 kern.info kernel: [ 1802.269641] br-lan: port 6(wlan0.4096) entered forwarding state
Wed Jun  7 16:13:50 2023 daemon.info hostapd: wlan0: STA 42:7e:de:b5:fe:b5 IEEE 802.11: associated (aid 1)
Wed Jun  7 16:13:50 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 42:7e:de:b5:fe:b5
Wed Jun  7 16:13:50 2023 daemon.info hostapd: wlan0: STA 42:7e:de:b5:fe:b5 RADIUS: starting accounting session F317B7EA33F63C42
Wed Jun  7 16:13:50 2023 user.debug wimoved[3157]: [DEBUG] 2023-06-07 16:13:50,751 EventLoop.cpp:31 - handle_connect called 42:7e:de:b5:fe:b5 with vlan_id 4096
Wed Jun  7 16:13:50 2023 user.info wimoved[3157]: [INFO] 2023-06-07 16:13:50,751 EventLoop.cpp:33 - Station 42:7e:de:b5:fe:b5 connected to AP for VXLAN 13 at interface wlan0
Wed Jun  7 16:13:50 2023 user.debug wimoved[3157]: [DEBUG] 2023-06-07 16:13:50,751 BridgePerVxlanRenderer.cpp:14 - Calling: setup_station(42:7e:de:b5:fe:b5)
Wed Jun  7 16:13:50 2023 user.info wimoved[3157]: [INFO] 2023-06-07 16:13:50,759 Socket.cpp:62 - Created VXLAN 13
Wed Jun  7 16:13:50 2023 user.info wimoved[3157]: [INFO] 2023-06-07 16:13:50,759 Socket.cpp:85 - Created Bridge bridge13
Wed Jun  7 16:13:50 2023 kern.warn kernel: [ 1802.299275] netlink: 'wimoved': attribute type 15 has an invalid length.
Wed Jun  7 16:13:50 2023 kern.info kernel: [ 1802.308033] bridge13: port 1(vxlan13) entered blocking state
Wed Jun  7 16:13:50 2023 kern.info kernel: [ 1802.313945] bridge13: port 1(vxlan13) entered disabled state
Wed Jun  7 16:13:50 2023 kern.info kernel: [ 1802.319822] device vxlan13 entered promiscuous mode
Wed Jun  7 16:13:50 2023 kern.info kernel: [ 1802.324858] bridge13: port 1(vxlan13) entered blocking state
Wed Jun  7 16:13:50 2023 kern.info kernel: [ 1802.330585] bridge13: port 1(vxlan13) entered forwarding state
Wed Jun  7 16:13:50 2023 user.info wimoved[3157]: [INFO] 2023-06-07 16:13:50,789 Socket.cpp:109 - Connected vxlan13 to bridge13
Wed Jun  7 16:13:50 2023 user.err wimoved[3157]: [ERROR] 2023-06-07 16:13:50,790 EventLoop.cpp:39 - station could not be bridged to vxlan interface: Could not get interface: vlan4096 No such device - Will now send deauth packet

The relevant configuration files:

/etc/config/wireless
config wifi-device 'radio0'
        option type 'mac80211'
        option path 'soc/soc:pcie/pci0000:00/0000:00:01.0/0000:01:00.0'
        option channel '36'
        option band '5g'
        option htmode 'VHT80'
        option country 'FR'
        option cell_density '0'
        option isolate '1'
        option per_sta_vif '1'
        option vlan_file '/etc/hostapd.vlan'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option encryption 'none'
        option macaddr '14:91:82:32:91:96'
        option ssid 'OpenWrt-1900'
        option isolate '1'
        option per_sta_vif '1'
        option vlan_file '/etc/hostapd.vlan'

config wifi-device 'radio1'
        option type 'mac80211'
        option path 'soc/soc:pcie/pci0000:00/0000:00:02.0/0000:02:00.0'
        option channel '1'
        option band '2g'
        option htmode 'HT20'
        option disabled '1'
        option country 'FR'
        option isolate '1'
        option per_sta_vif '1'
        option vlan_file '/etc/hostapd.vlan'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'OpenWrt'
        option encryption 'none'
        option macaddr '14:91:82:32:91:95'
        option isolate '1'
        option per_sta_vif '1'
        option vlan_file '/etc/hostapd.vlan'

/etc/hostapd.vlan

*   vlan#

/etc/wimoved/config
# Default configuration
hapd_group=network

from wimoved.

dasGoogle commented on June 11, 2024

Hi Rubens,

as a first troubleshooting step, could you stop the wimved service so that the station will not be immediately deauthed when the error occurs and then perfom the following steps?

Connect the station to the Wi-Fi network
Take a look whether a vlan interface is created for the station using ip l and see what it is called

from wimoved.

rubensfig commented on June 11, 2024

Hello,

Apologies for the long time in coming back to you, and thank you for the support!

So, with the wimoved service stopped, and connecting to the device, the following logs are seen.

Jun 23 08:48:39 OpenWrt hostapd: wlan1: STA f4:f2:6d:1b:62:8d RADIUS: VLAN ID 4096
Jun 23 08:48:39 OpenWrt kernel: [  277.346877] br-lan: port 6(wlan1.4096) entered blocking state
Jun 23 08:48:39 OpenWrt kernel: [  277.352704] br-lan: port 6(wlan1.4096) entered disabled state
Jun 23 08:48:39 OpenWrt kernel: [  277.358741] device wlan1.4096 entered promiscuous mode
Jun 23 08:48:39 OpenWrt kernel: [  277.364023] br-lan: port 6(wlan1.4096) entered blocking state
Jun 23 08:48:39 OpenWrt kernel: [  277.369849] br-lan: port 6(wlan1.4096) entered forwarding state
Jun 23 08:48:39 OpenWrt hostapd: wlan1: STA f4:f2:6d:1b:62:8d IEEE 802.11: authenticated
Jun 23 08:48:39 OpenWrt hostapd: wlan1: STA f4:f2:6d:1b:62:8d IEEE 802.11: associated (aid 1)
Jun 23 08:48:39 OpenWrt hostapd: wlan1: AP-STA-CONNECTED f4:f2:6d:1b:62:8d
Jun 23 08:48:39 OpenWrt hostapd: wlan1: STA f4:f2:6d:1b:62:8d RADIUS: starting accounting session 65C81018D3BD0AFE

The vlan interface created is then visible.

19: wlan1.4096: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UNKNOWN qlen 1000
    link/ether c0:56:27:b8:d7:82 brd ff:ff:ff:ff:ff:ff

It is a bit strange, since the contents of the hostapd are.

/etc/hostapd.vlan
*   vlan#

from wimoved.

dasGoogle commented on June 11, 2024

Exactly, I believe that the issue lies with the hostapd.vlan file.

Did you use the ansible deployment or did you deploy manually?

I was told that the whitespace in that file is quite critical, so (in case you copied it by hand from the guide) you could try directly copying the file: https://github.com/WiMoVE-OSS/deployment/blob/main/roles/access-point/files/hostapd.vlan

from wimoved.

Issues starting wimoved about wimoved HOT 6 CLOSED

Comments (6)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent