You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i have the problem, that the luci wireless page dont show any stations connected to dynamic vlans on wpa2 enterprise or wpa2 personal ppsk. i traced it back to the luci code getting a empty vlan list and therefore dont even look at the vlans. the empty vlan list i traced back again first to ubus, which showed empty vlan list (ubus -v call network.wireless status), and this back to netifd, which dont consider the dynamicaly created vlans from hostapd and therefore the ubus vlan list is empty and therefore luci dont check for any stations on dynamic vlan networks.
here is the output of ubus -v call network.wireless status:
netifd collects interface information, but here it only considers the uci config files and this configuration will not include enough information to infer all the correct interface names, nor should it try to.
The second place netifd seems to look for information is in
. Here I am less sure. To me, it looks like it looks through what you should also get using ubus -v call service get_data for entries called wifi-iface. However, even with just a regular configuration, I do not see entries like that here. I may be completely wrong here, or it might be for a type of configuration I simply do not have. I don't know.
In essence, to me it looks like ifnetd only looks at configuration files while looking for wireless devices, and not at actual existing devices and it does not support all possible configuration options (again, I think it really shouldn't). Instead, it likely should get the list of devices from something like ubus call iwinfo devices. Question to the devs: would that work?
i have the problem, that the luci wireless page dont show any stations connected to dynamic vlans on wpa2 enterprise or wpa2 personal ppsk. i traced it back to the luci code getting a empty vlan list and therefore dont even look at the vlans. the empty vlan list i traced back again first to ubus, which showed empty vlan list (ubus -v call network.wireless status), and this back to netifd, which dont consider the dynamicaly created vlans from hostapd and therefore the ubus vlan list is empty and therefore luci dont check for any stations on dynamic vlan networks.
here is the output of ubus -v call network.wireless status:
the output of iwinfo:
as you can see, the vlan interfaces are there, they are just not part of the vlan list and therefore not picked up by luci
thx
The text was updated successfully, but these errors were encountered: