Selected interface is not a WLAN card

[sammy-bulldog]

@metalac

I used a spare ethernet port (eth2) and bridged it with wlan0. I did that by selecting “bridge” mode for BLUE in zone configuration and then assigned both wlan0 and eth2 as “native” for that zone. After a restart the bridge seems to be created and working:

I did it in the same way, but my bridge is not working.
Wifi or eth is working.
The GUI for wlanAP shows: Ausgewähltes Interface ist keine WLAN-Karte!

EDIT: in English
The GUI for wlanAP shows: Selected interface is not a WLAN card!

[manfred_knick]

Same error message over here.
Observations:

• first, only the LAN if was added to the bridge
• removed from bridge ; reboot
• re-added to bridge ; reboot
• ! the green LAN if was added as only member to the bridge

Reverting to former back-up config now.

Re-building bridge, enabling STP tickmark:

• ! the green LAN interface was added as only member to the bridge, again.

Reverting to simpler config: Bridge soleyly over WLAN card.

• WLAN AP: “Selected interface is not a wirless lan card!”
• “Remove selected interface”
• “Please select the wireless lan interface” = options: [ blue0 | green0 ]
• select blue0
• WLAN AP: “Selected interface is not a wirless lan card!” again
• brctl show:
• bridge name bridge id STP enabled interfaces
• blue0 8000.02cff6a4beb8 yes
• NOTE: interfaces ← NONE !

@Sammy-Bulldog: could you please ssh into your IPFire
and call

• brctl show
• ifconfig

please?

Manually reverting to former Zone config (blue0 WLan If only) again.
Disabling MAC Address filtering -not plausible, but just for a test-
and re-building bridge from scratch:
brctl show
bridge name bridge id STP enabled interfaces
blue0 8000.027b0aca8a6e no eth2

! eth2 is my GREEN LAN Interface !

Sorry, but I can’t deny the impression that
“Zone Configuration” → “NIC Assignment” → “Bridge” seems broken a.t.m.

Next OBSERVATION:
Restoring main IPFire backup and then hostapd backup afterwards & reboot,

• the new ssh=enabled config gets correctly deleted,
• the old ssh=disabled config gets correctly implemented,
• the entry disabling MAC Address filtering temporarily entered gets correctly deleted also,
• but
• the new BLUE Bridge Zone Configuration is still active,
• the old singular Zone Configuration is not being restored
• reverting manually & reboot again
• afterwards,
• “Access Point Configuration” correctly and completely shows up again.

What is the current valid place for providing bug reports?
I did not find any “create-new-account” button on bugzilla.ipfire.org.

[anon33261557]

@manfred_knick

I did not find any “create-new-account” button on bugzilla

You can find this several times here in the forum and also in our lovely wiki

Create account for forum, wiki, bugzilla …

In other words: If you can login “here” you already can login “there”

[manfred_knick]

Having tried that, I failed - too tired:
This morning I realized having used a wrong one of my email addresses! Shame on me …
@anon33261557: Thanks a lot!
Suggestion: Add your hint as a link into [wiki.ipfire.org - Bugzilla].

[jschlag (Jonatan Schlag)]

Your credentials working for the wiki as well, so you are able to add this information to the wiki by yourself :-). You do not have to but at least I want to provide this information for everyone reading this later on.

Jonatan

[anon33261557]

@jschlag

Your credentials working for the wiki as well

All can already know this if they read the information behind my provided link above

@jschlag

add this information to the wiki by yourself

Thats why i waited if he maybe comes to the same conclusion

Edit. Have done it by myself now

[manfred_knick]

@anon33261557

Thats why i waited if he maybe comes to the same conclusion

Yes, I did, indeed - congratulations for being quicker …
Admittedly, having spent hours / whole night answering questions,
this one as well as a To-Do “New Bug” entry had to wait
Thanks anyway!

[manfred_knick]

Exploiting some user-free time today, I used “Network” → “Zone configuration”
for combining eth0 and eth3 into one bridge for “Orange” with success:

• ssh → brctl show:
• bridge name: orange0
• interfaces: eth2 , eth3

and back again also.

Thus the due bug report can be limited to combinations of LAN with WLAN into a „Blue“ bridge.

[manfred_knick]

Bug 12601 -
zone configuration / hostapd:
Combining WLAN if with free LAN if into a common “Blue” bridge fails

[anon33261557]

@manfred_knick

can be limited to combinations of LAN with WLAN into a „Blue“ bridge

I can not check this myself sorry, no free NIC. But it seems @ms itself have a working blue Lan / Wifi bridge here.

IPFire 2.25 - Core Update 155 released [SECURITY ADVISORY] - The IPFire Blog

Hope this info can be usefull in some way…

[manfred_knick]

@anon33261557

But it seems @ms itself have a working blue Lan / Wifi bridge here.

Perhaps I’m friggin’ blind - didn’t catch what you are pointing at.

In case you are pointing at STP: playing around with that did not help either …

Thanks.

[anon33261557]

@manfred_knick

Perhaps I’m friggin’ blind

A little story on this topic. I’ve seen a lot of postings in the past where people have complained that the zone configuration not to work as it should. I saw postings, if I remember correctly, that @luani was working on this and that this should be resolved now. Now I read your posting and meant to understand that you said this still does not work with blue wifi/lan. All I meant is if STP works, it should also work without it. And it just doesn’t work under certain circumstances, which is unclear at the moment, but not absolutely not working.

Perhaps better in other words. What I mean is, it seems blue wifi/lan bridge works for some and for some under certain circumstances not. BUT not, it basically does not work for anyone.

If I completely misinterpreted your posting, just ignore it

As i said before, I hope…

[manfred_knick]

@anon33261557 , I was puzzled because I did not find anything concerning @ms in the Blog post your link provided …

Thanks for your clarification, anyway!
To me, this suggests collecting working and non-working examples is needed in order to further fence this problem in.

@metalac , @Sammy-Bulldog :
Could you please be so kind as to also disclose your HW involved,
as well as IPFire core / hostapd version?
Thanks!

I just discovered that hostap - hostapd/wpa_supplicant displays hostap_2_9 as latest stable release,
whereas “hostapd -v” displays “hostapd v2.10-devel”.

Having noticed 12585 – Update with core 154 stops hostapd on some hardware.
→ “Downgrading hostapd from 581dfcc-54 to 2.9-52 fixed it”,
I downgraded to hostapd-2.9-52.ipfire also, but to no avail:
Again “brctl show” listed my green eth if as only single member.
And the error message from the title as well.
So I switched back again.

[lexuspolaris]

I know this is a very very old post but since I got the same error-message and the only conversations, google spit out about this, are IPFire-related, I thought I could provide some findings.

As I said I get the same error-message with a pretty modern WIFI-module. In my case there is no bridging or anything involved, I just told WLanAP to “take over” my wlan0-interface (including the MAC-address) and then the error message is there.

I did some research and found that “Ausgewähltes Interface ist keine WLAN-Karte!” shows up when something is returning ‘wlanap no interface’.

Line 3007 here → ipfire-2.x/langs/de/cgi-bin/de.pl at master · ipfire/ipfire-2.x · GitHub

I looked for it in the wlanap.cgi and found that this is the answer when iwconfig cannot read the informations about or the status of the module.

I tried “iwconfig” and it gives back “wlan0 no wireless extensions”. So in my case it’s because either the kernel of my IPFire-instance or the driver for the module will not support iwconfig anymore (or more specific the way it’s reading out the interfaces).

iwconfig: wlan0 no wireless extensions

I already checked the solution in the posting, in my case both options, “CONFIG_WIRELESS_EXT” and “CONFIG_CFG80211_WEXT”, are activated. It still could has something to do with the kernel because I did a major upgrade recently and WLanAP worked with the older one (went from 6.9 to 6.10). But it could also be the driver (ath12k in my case), since they updated it to a great extent.

Anyway, maybe this will help someone at some point.

Greetings

Alex

[lexuspolaris]

Small update with a solution for people, who have my problem (so no bridging involved, etc.).

Just open the wlanap.cgi file in the console (e.g. over ssh) and swap the commands.

I changed

my $cmd_out = /usr/sbin/iwconfig $INTF 2>/dev/null;

to

my $cmd_out = /usr/sbin/iw $INTF info 2>/dev/null;

and the line

$cmd_out = /usr/sbin/iwconfig $INTF | /bin/grep "Mode:Master";

to

$cmd_out = /usr/sbin/iw $INTF info | /bin/grep "type AP";

That’s all and it works because “iwconfig” is only used to ask the interface status regarding “up” or “down”. For detailled informations about channel, requencies, txpower, connected stations, etc. “iw” is used anyway.

[lexuspolaris]

Hey guys,

during the testing of my new WiFi7-Interface, I noticed some more “problems” with the WLanAP-page, so I wrote (or more created) a little patch.

It does completely remove the need for “iwconfig” (only “iw” from now on).

It adds two more encryption options for wpa3 and wpa2+3, using GCMP-256 and WPA-PSK-SHA256/GCMP-256 respectively (if it works, depends on your modul, see “iw list” for supported encryption methods).

It adds two really useful options (exclude_dfs and background_radar) which save a lot of time when testing WiFi (since the frequencys 5600Mhz - 5650Mhz have 600 second cac_time by law). For now they are deactivated by default because the functions depend on the used modul and it’s not possible to switch them on and off within the WUI. Maybe sometime in the future I will add a checkbox.

And it makes the page kind of “WiFi-7-ready”, including basic activating of 802.11ax and 802.11be.

For better compatibility I only added the standard-options (so only 80Mhz, no 80+80, 160, 320 or other special options).

From 802.11ax on there’s no “capabs” anymore, the options have to be handed over to the hostapd.conf line by line, so it will be a bit difficult to implement them in the template at whole.

Anyway, it’s a start, have fun with it!

Oh and I use the most recent hostapd 2.11, which was released about two weeks ago (https://w1.fi/). You may need to update to get full Wifi6-support (WiFi 7 is still experimental).

--- /srv/web/ipfire/cgi-bin/wlanap-original.cgi	2024-08-05 17:07:49.252130494 +0200
+++ /srv/web/ipfire/cgi-bin/wlanap-patched.cgi	2024-08-05 17:07:49.255130557 +0200
@@ -229,7 +229,7 @@
 	&Header::closepage();
 	exit;
 }else{
-	my $cmd_out = `/usr/sbin/iwconfig $INTF 2>/dev/null`;
+	my $cmd_out = `/usr/sbin/iw dev $INTF info 2>/dev/null`;
 
 	if ( $cmd_out eq '' ){
 		$message = "$Lang::tr{'wlanap no interface'}";
@@ -240,9 +240,11 @@
 			$wlan_card_status = 'down';
 		}else{
 			$wlan_card_status = 'up';
-			$cmd_out = `/usr/sbin/iwconfig $INTF | /bin/grep "Mode:Master"`;
-			if ( $cmd_out ne '' ){
+			$cmd_out = `/usr/local/bin/wlanapctrl status | /bin/grep "not"`;
+			if ( $cmd_out eq '' ){
 				$wlan_ap_status = 'up';
+			}else{
+				$wlan_ap_status = 'down';
 			}
 		}
 	}
@@ -416,6 +418,8 @@
 		<option value='an' $selected{'HW_MODE'}{'an'}>802.11an</option>
 		<option value='gn' $selected{'HW_MODE'}{'gn'}>802.11gn</option>
 		<option value='ac' $selected{'HW_MODE'}{'ac'}>802.11ac</option>
+		<option value='ax' $selected{'HW_MODE'}{'ax'}>802.11ax</option>
+		<option value='be' $selected{'HW_MODE'}{'be'}>802.11be</option>
 	</select>
 </td></tr>
 END
@@ -454,8 +458,10 @@
 		<option value='wpa1' $selected{'ENC'}{'wpa1'}>WPA1</option>
 		<option value='wpa2' $selected{'ENC'}{'wpa2'}>WPA2</option>
 		<option value='wpa3' $selected{'ENC'}{'wpa3'}>WPA3</option>
+		<option value='wpa3-strong' $selected{'ENC'}{'wpa3-strong'}>WPA3 (GCMP-256)</option>
 		<option value='wpa1+2' $selected{'ENC'}{'wpa1+2'}>WPA1+2</option>
 		<option value='wpa2+3' $selected{'ENC'}{'wpa2+3'}>WPA2+3</option>
+		<option value='wpa2+3-strong' $selected{'ENC'}{'wpa2+3-strong'}>WPA2+3 (WPA-PSK-SHA256 / GCMP-256)</option>
 	</select>
 </td></tr>
 <tr><td width='25%' class='base'>Passphrase:&nbsp;</td><td class='base' colspan='3'><input type='text' name='PWD' size='30' value='$wlanapsettings{'PWD'}' /></td></tr>
@@ -592,13 +598,18 @@
 ieee80211d=1
 ieee80211h=1
 channel=$wlanapsettings{'CHANNEL'}
+### Two useful options, which save time, but functions depend on modul ###
+### Will create check-box eventually to activate manually ###
+#acs_exclude_dfs=1
+#enable_background_radar=1
 END
 ;
+### hereinafter I changed the order of the in individual options to match up with the original hostapd.conf ###
  if ( $wlanapsettings{'HW_MODE'} eq 'an' ){
 	print CONFIGFILE <<END
 hw_mode=a
-ieee80211n=1
 wmm_enabled=1
+ieee80211n=1
 ht_capab=$wlanapsettings{'HTCAPS'}
 END
 ;
@@ -606,8 +617,8 @@
  }elsif ( $wlanapsettings{'HW_MODE'} eq 'gn' ){
 	print CONFIGFILE <<END
 hw_mode=g
-ieee80211n=1
 wmm_enabled=1
+ieee80211n=1
 ht_capab=$wlanapsettings{'HTCAPS'}
 END
 ;
@@ -615,12 +626,42 @@
  }elsif ( $wlanapsettings{'HW_MODE'} eq 'ac' ){
 	print CONFIGFILE <<END
 hw_mode=a
+wmm_enabled=1
+ieee80211n=1
+ht_capab=$wlanapsettings{'HTCAPS'}
 ieee80211ac=1
+vht_capab=$wlanapsettings{'VHTCAPS'}
+vht_oper_chwidth=1
+END
+;
+
+ }elsif ( $wlanapsettings{'HW_MODE'} eq 'ax' ){
+	print CONFIGFILE <<END
+hw_mode=a
+wmm_enabled=1
 ieee80211n=1
+ht_capab=$wlanapsettings{'HTCAPS'}
+ieee80211ac=1
+vht_capab=$wlanapsettings{'VHTCAPS'}
+vht_oper_chwidth=1
+ieee80211ax=1
+he_oper_chwidth=1
+END
+;
+
+ }elsif ( $wlanapsettings{'HW_MODE'} eq 'be' ){
+	print CONFIGFILE <<END
+hw_mode=a
 wmm_enabled=1
+ieee80211n=1
 ht_capab=$wlanapsettings{'HTCAPS'}
+ieee80211ac=1
 vht_capab=$wlanapsettings{'VHTCAPS'}
 vht_oper_chwidth=1
+ieee80211ax=1
+he_oper_chwidth=1
+ieee80211be=1
+eht_oper_chwidth=1
 END
 ;
 
@@ -692,6 +733,8 @@
 
  if ( $wlanapsettings{'ENC'} eq 'wpa1'){
 	print CONFIGFILE <<END
+### Added "wpa3-strong" and "wpa2+3-strong", that contain better encryption ###
+### Will create drop-down-field eventually to choose manually ###
 ######################### wpa hostapd configuration ############################
 #
 wpa=1
@@ -720,6 +763,16 @@
 rsn_pairwise=CCMP
 END
 ;
+ }elsif ( $wlanapsettings{'ENC'} eq 'wpa3-strong'){
+	print CONFIGFILE <<END
+######################### wpa hostapd configuration ############################
+#
+wpa=2
+wpa_passphrase=$wlanapsettings{'PWD'}
+wpa_key_mgmt=SAE
+rsn_pairwise=GCMP-256
+END
+;
  } elsif ( $wlanapsettings{'ENC'} eq 'wpa1+2'){
 	print CONFIGFILE <<END
 ######################### wpa hostapd configuration ############################
@@ -740,6 +793,16 @@
 wpa_key_mgmt=WPA-PSK SAE
 rsn_pairwise=CCMP
 END
+;;
+ }elsif ( $wlanapsettings{'ENC'} eq 'wpa2+3-strong'){
+	print CONFIGFILE <<END
+######################### wpa hostapd configuration ############################
+#
+wpa=2
+wpa_passphrase=$wlanapsettings{'PWD'}
+wpa_key_mgmt=WPA-PSK-SHA256 SAE
+rsn_pairwise=GCMP-256
+END
 ;
  }
 	close CONFIGFILE;