Wifi mit nicht überlappenden MAC/BSSID vs verschiedener SSIDs

Technik
1

Ich habe heute einen TP Link WDR3600 v1.4 mit dem Pinneberger Freifunk geflasht. Irgendwie lief auch alles gut und im Konfigmodus war alles i.O…
Dann merkte ich, dass die 2,4GhZ Antenne keine Signale mehr von sich gibt. Ich nochmal rein in den Konfigmodus und alles einmal an und aus geschaltet… Alle Haken sind gesetzt.

Doch nun mag nur noch das 5GhZ WIfi. Darüber komme ich nun per SSH auf den Router drauf und habe mit uci show folgendes zur Ansicht bekommen.

Bildschirmfoto von 2022-01-22 19-18-32
Bildschirmfoto von 2022-01-22 19-18-32535×533 27.1 KB

Könnt ihr vielleicht einen Fehler sehen? Wenn ja - wie kriege ich das berichtigt?

2

Was ist der output von „logread“ nachdem du das wlan mit „wifi“ neu startest.

3

OHA. Da hast Du mir ja wieder eine Aufgabe gestellt.

Wifi starten
Logread auslesen.

Mal schauen ob ich das hin bekomme.

4

Wifi starten habe ich noch nicht hinbekommen.

Aber hier das aktuelle logread

BlockzitatSat Jan 22 15:39:54 2022 daemon.warn dnsmasq[1823]: no servers found in /tmp/resolv.conf.auto, will retry
Sat Jan 22 15:39:54 2022 daemon.info dnsmasq[1823]: read /etc/hosts - 1 addresses
Sat Jan 22 15:39:54 2022 daemon.info dnsmasq[1849]: started, version 2.73 cachesize 150
Sat Jan 22 15:39:54 2022 daemon.info dnsmasq[1849]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
Sat Jan 22 15:39:54 2022 daemon.info dnsmasq[1849]: reading /var/gluon/wan-dnsmasq/resolv.conf
Sat Jan 22 15:39:54 2022 daemon.info dnsmasq[1849]: using nameserver fd61:69d6:e4c::1#53
Sat Jan 22 15:39:54 2022 daemon.info dnsmasq[1849]: using nameserver 192.168.178.1#53
Sat Jan 22 15:39:54 2022 daemon.info dnsmasq[1849]: cleared cache
Sat Jan 22 15:39:55 2022 kern.info kernel: [ 33.130000] batman_adv: bat0: Changing gw mode from: off to: client
Sat Jan 22 15:39:55 2022 kern.info kernel: [ 33.150000] batman_adv: bat0: hop_penalty: Changing from: 30 to: 15
Sat Jan 22 15:39:55 2022 kern.info kernel: [ 33.180000] batman_adv: bat0: multicast_mode: Changing from: enabled to: disabled
Sat Jan 22 15:39:55 2022 kern.info kernel: [ 33.180000] batman_adv: bat0: orig_interval: Changing from: 1000 to: 5000
Sat Jan 22 15:39:55 2022 kern.info kernel: [ 33.750000] br-client: port 3(bat0) entered forwarding state
Sat Jan 22 15:39:56 2022 daemon.notice fastd[2002]: fastd v18 starting
Sat Jan 22 15:39:56 2022 daemon.notice netifd: Interface ‚mesh_vpn‘ is enabled
Sat Jan 22 15:39:56 2022 daemon.notice netifd: Network device ‚mesh-vpn‘ link is up
Sat Jan 22 15:39:56 2022 daemon.notice netifd: Interface ‚mesh_vpn‘ has link connectivity
Sat Jan 22 15:39:56 2022 daemon.notice netifd: Interface ‚mesh_vpn‘ is setting up now
Sat Jan 22 15:39:56 2022 daemon.notice fastd[2002]: changed to UID 0, GID 800
Sat Jan 22 15:39:56 2022 daemon.info fastd[2002]: adding peer <mesh_vpn_backbone_peer_gate03>
Sat Jan 22 15:39:56 2022 daemon.info fastd[2002]: adding peer <mesh_vpn_backbone_peer_gate01>
Sat Jan 22 15:39:56 2022 daemon.info fastd[2002]: adding peer <mesh_vpn_backbone_peer_gate04>
Sat Jan 22 15:39:56 2022 daemon.info fastd[2002]: adding peer <mesh_vpn_backbone_peer_gate05>
Sat Jan 22 15:39:56 2022 daemon.info fastd[2002]: resolving host gate05.hoogi.de' for peer <mesh_vpn_backbone_peer_gate05>... Sat Jan 22 15:39:56 2022 daemon.info fastd[2002]: resolving host gate04.pinneberg.freifunk.net’ for peer <mesh_vpn_backbone_peer_gate04>…
Sat Jan 22 15:39:56 2022 daemon.info fastd[2002]: resolving host gate01.hoogi.de' for peer <mesh_vpn_backbone_peer_gate01>... Sat Jan 22 15:39:56 2022 daemon.info fastd[2002]: resolving host gate03.hoogi.de’ for peer <mesh_vpn_backbone_peer_gate03>…
Sat Jan 22 15:39:56 2022 daemon.info fastd[2002]: resolved host gate01.hoogi.de' successfully Sat Jan 22 15:39:56 2022 daemon.info fastd[2002]: resolved host gate03.hoogi.de’ successfully
Sat Jan 22 15:39:56 2022 daemon.info fastd[2002]: resolved host gate04.pinneberg.freifunk.net' successfully Sat Jan 22 15:39:56 2022 daemon.info fastd[2002]: resolved host gate05.hoogi.de’ successfully
Sat Jan 22 15:39:56 2022 user.emerg syslog: setting up led USB1
Sat Jan 22 15:39:56 2022 user.emerg syslog: Skipping trigger ‚usbdev‘ for led ‚USB1‘ due to missing kernel module
Sat Jan 22 15:39:56 2022 user.emerg syslog: setting up led USB2
Sat Jan 22 15:39:56 2022 user.emerg syslog: Skipping trigger ‚usbdev‘ for led ‚USB2‘ due to missing kernel module
Sat Jan 22 15:39:56 2022 user.emerg syslog: setting up led WLAN2G
Sat Jan 22 15:39:56 2022 kern.info kernel: [ 35.050000] batman_adv: bat0: Adding interface: mesh-vpn
Sat Jan 22 15:39:56 2022 kern.info kernel: [ 35.060000] batman_adv: bat0: The MTU of interface mesh-vpn is too small (1426) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1532 would solve the problem.
Sat Jan 22 15:39:56 2022 kern.info kernel: [ 35.080000] batman_adv: bat0: Interface activated: mesh-vpn
Sat Jan 22 15:39:57 2022 kern.info kernel: [ 35.100000] batman_adv: bat0: no_rebroadcast: Changing from: disabled to: enabled
Sat Jan 22 15:39:57 2022 daemon.notice netifd: Interface ‚mesh_vpn‘ is now up
Sat Jan 22 15:39:57 2022 user.notice firewall: Reloading firewall due to ifup of wan (br-wan)
Sat Jan 22 15:39:57 2022 daemon.info fastd[2002]: sending handshake to <mesh_vpn_backbone_peer_gate01>[81.7.14.115:10000]…
Sat Jan 22 15:39:57 2022 daemon.warn fastd[2002]: sendmsg: Operation not permitted
Sat Jan 22 15:39:57 2022 daemon.info fastd[2002]: resolving host gate01.pinneberg.freifunk.net' for peer <mesh_vpn_backbone_peer_gate01>... Sat Jan 22 15:39:57 2022 daemon.info fastd[2002]: sending handshake to <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000]... Sat Jan 22 15:39:57 2022 daemon.info fastd[2002]: resolving host gate04.freifunk-pinneberg.de’ for peer <mesh_vpn_backbone_peer_gate04>…
Sat Jan 22 15:39:57 2022 daemon.info fastd[2002]: resolved host gate04.freifunk-pinneberg.de' successfully Sat Jan 22 15:39:57 2022 daemon.info fastd[2002]: received handshake response from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000] using fastd v18 Sat Jan 22 15:39:58 2022 user.emerg syslog: /etc/rc.d/S99alfred: waiting 30 secs for br-client address... Sat Jan 22 15:39:58 2022 user.emerg syslog: /etc/rc.d/S99alfred: starting alfred Sat Jan 22 15:39:58 2022 user.emerg syslog: /etc/rc.d/S99alfred: starting batadv-vis Sat Jan 22 15:39:58 2022 daemon.info procd: - init complete - Sat Jan 22 15:39:58 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04> Sat Jan 22 15:39:58 2022 daemon.notice fastd[2002]: connection with <mesh_vpn_backbone_peer_gate04> established. Sat Jan 22 15:39:58 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac’.
Sat Jan 22 15:39:59 2022 user.notice firewall: Reloading firewall due to ifup of wan6 (br-wan)
Sat Jan 22 15:39:59 2022 daemon.warn fastd[2002]: sendmsg: Operation not permitted
Sat Jan 22 15:40:00 2022 daemon.notice netifd: Interface ‚client‘ is now up
Sat Jan 22 15:40:01 2022 kern.notice kernel: [ 40.080000] random: nonblocking pool is initialized
Sat Jan 22 15:40:02 2022 daemon.info fastd[2002]: resolved host gate01.pinneberg.freifunk.net' successfully Sat Jan 22 15:40:03 2022 user.notice firewall: Reloading firewall due to ifup of client (br-client) Sat Jan 22 15:40:44 2022 daemon.info dnsmasq[1823]: reading /tmp/resolv.conf.auto Sat Jan 22 15:40:44 2022 daemon.info dnsmasq[1823]: using local addresses only for domain lan Sat Jan 22 15:40:44 2022 daemon.info dnsmasq[1823]: using nameserver fde8:21c6:9d82::c01#53 Sat Jan 22 15:40:44 2022 daemon.info dnsmasq[1823]: using nameserver fde8:21c6:9d82::d01#53 Sat Jan 22 15:40:44 2022 daemon.info dnsmasq[1823]: using nameserver fde8:21c6:9d82::a01#53 Sun Jan 23 00:05:18 2022 daemon.info fastd[2002]: refreshing session with <mesh_vpn_backbone_peer_gate04> Sun Jan 23 00:05:18 2022 daemon.info fastd[2002]: sending handshake to <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000]... Sun Jan 23 00:05:18 2022 daemon.info fastd[2002]: received handshake response from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000] using fastd v18 Sun Jan 23 00:05:18 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04> Sun Jan 23 00:05:18 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac’.
Sun Jan 23 00:57:15 2022 daemon.info fastd[2002]: refreshing session with <mesh_vpn_backbone_peer_gate04>
Sun Jan 23 00:57:15 2022 daemon.info fastd[2002]: sending handshake to <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000]…
Sun Jan 23 00:57:15 2022 daemon.info fastd[2002]: received handshake response from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000] using fastd v18
Sun Jan 23 00:57:16 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04>
Sun Jan 23 00:57:16 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac'. Sun Jan 23 01:52:07 2022 daemon.info fastd[2002]: refreshing session with <mesh_vpn_backbone_peer_gate04> Sun Jan 23 01:52:07 2022 daemon.info fastd[2002]: sending handshake to <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000]... Sun Jan 23 01:52:07 2022 daemon.info fastd[2002]: received handshake response from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000] using fastd v18 Sun Jan 23 01:52:08 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04> Sun Jan 23 01:52:08 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac’.
Sun Jan 23 02:42:48 2022 daemon.info fastd[2002]: refreshing session with <mesh_vpn_backbone_peer_gate04>
Sun Jan 23 02:42:48 2022 daemon.info fastd[2002]: sending handshake to <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000]…
Sun Jan 23 02:42:48 2022 daemon.info fastd[2002]: received handshake response from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000] using fastd v18
Sun Jan 23 02:42:48 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04>
Sun Jan 23 02:42:48 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac'. Sun Jan 23 02:50:35 2022 daemon.info fastd[2002]: received handshake from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000] Sun Jan 23 02:50:35 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04> Sun Jan 23 02:50:35 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac’.
Sun Jan 23 03:45:25 2022 daemon.info fastd[2002]: received handshake from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000]
Sun Jan 23 03:45:25 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04>
Sun Jan 23 03:45:25 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac'. Sun Jan 23 04:36:19 2022 daemon.info fastd[2002]: received handshake from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000] Sun Jan 23 04:36:19 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04> Sun Jan 23 04:36:19 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac’.
Sun Jan 23 05:29:24 2022 daemon.info fastd[2002]: received handshake from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000]
Sun Jan 23 05:29:24 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04>
Sun Jan 23 05:29:24 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac'. Sun Jan 23 06:22:25 2022 daemon.info fastd[2002]: received handshake from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000] Sun Jan 23 06:22:25 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04> Sun Jan 23 06:22:25 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac’.
Sun Jan 23 07:16:33 2022 daemon.info fastd[2002]: received handshake from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000]
Sun Jan 23 07:16:33 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04>
Sun Jan 23 07:16:33 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac'. Sun Jan 23 08:07:15 2022 daemon.info fastd[2002]: received handshake from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000] Sun Jan 23 08:07:15 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04> Sun Jan 23 08:07:15 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac’.
Sun Jan 23 08:58:01 2022 daemon.info fastd[2002]: received handshake from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000]
Sun Jan 23 08:58:02 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04>
Sun Jan 23 08:58:02 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac'. Sun Jan 23 09:48:23 2022 daemon.info hostapd: client1: STA 04:f1:28:6f:4e:18 IEEE 802.11: authenticated Sun Jan 23 09:48:23 2022 daemon.info hostapd: client1: STA 04:f1:28:6f:4e:18 IEEE 802.11: associated (aid 1) Sun Jan 23 09:51:48 2022 daemon.info fastd[2002]: received handshake from <mesh_vpn_backbone_peer_gate04>[213.133.108.18:10000] Sun Jan 23 09:51:49 2022 daemon.info fastd[2002]: 213.133.108.18:10000 authorized as <mesh_vpn_backbone_peer_gate04> Sun Jan 23 09:51:49 2022 daemon.info fastd[2002]: new session with <mesh_vpn_backbone_peer_gate04> established using method salsa2012+umac’.
Sun Jan 23 09:55:09 2022 daemon.info hostapd: client1: STA 04:f1:28:6f:4e:18 IEEE 802.11: disassociated due to inactivity
Sun Jan 23 09:55:10 2022 daemon.info hostapd: client1: STA 04:f1:28:6f:4e:18 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Jan 23 10:22:28 2022 authpriv.info dropbear[28820]: Child connection from fde8:21c6:9d82:0:eb5a:728f:1ebd:8dc4:57896
Sun Jan 23 10:22:29 2022 authpriv.warn dropbear[28820]: Bad password attempt for ‚root‘ from fde8:21c6:9d82:0:eb5a:728f:1ebd:8dc4:57896
Sun Jan 23 10:22:49 2022 authpriv.notice dropbear[28820]: Password auth succeeded for ‚root‘ from fde8:21c6:9d82:0:eb5a:728f:1ebd:8dc4:57896
Sun Jan 23 10:22:53 2022 kern.info kernel: [40162.300000] device client1 left promiscuous mode
Sun Jan 23 10:22:53 2022 kern.info kernel: [40162.300000] br-client: port 2(client1) entered disabled state
Sun Jan 23 10:22:53 2022 daemon.notice netifd: Network device ‚client1‘ link is down
Sun Jan 23 10:22:53 2022 kern.info kernel: [40162.420000] batman_adv: bat0: Interface deactivated: ibss1
Sun Jan 23 10:22:53 2022 daemon.notice netifd: Network device ‚ibss1‘ link is down
Sun Jan 23 10:22:53 2022 daemon.notice netifd: Interface ‚ibss_radio1‘ has link connectivity loss
Sun Jan 23 10:22:53 2022 kern.info kernel: [40162.480000] batman_adv: bat0: Removing interface: ibss1
Sun Jan 23 10:22:53 2022 daemon.notice netifd: Interface ‚ibss_radio1‘ is disabled
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio1 (28866): Configuration file: /var/run/hostapd-phy1.conf
Sun Jan 23 10:22:55 2022 kern.info kernel: [40164.400000] IPv6: ADDRCONF(NETDEV_UP): client1: link is not ready
Sun Jan 23 10:22:55 2022 kern.info kernel: [40164.430000] device client1 entered promiscuous mode
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio1 (28866): client1: interface state UNINITIALIZED->COUNTRY_UPDATE
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio1 (28866): Using interface client1 with hwaddr ee:ea:fd:da:c0:0c and ssid „pinneberg.freifunk.net“
Sun Jan 23 10:22:55 2022 kern.info kernel: [40164.450000] IPv6: ADDRCONF(NETDEV_CHANGE): client1: link becomes ready
Sun Jan 23 10:22:55 2022 kern.info kernel: [40164.460000] br-client: port 2(client1) entered forwarding state
Sun Jan 23 10:22:55 2022 kern.info kernel: [40164.470000] br-client: port 2(client1) entered forwarding state
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio1 (28866): client1: interface state COUNTRY_UPDATE->ENABLED
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio1 (28866): client1: AP-ENABLED
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): Configuration file: /var/run/hostapd-phy0.conf
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): Duplicate BSSID 10:fe:ed:84:5f:f9 on interface ‚clientpsk‘ and ‚client0‘.
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): 1 errors found in configuration file ‚/var/run/hostapd-phy0.conf‘
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): Failed to set up interface with /var/run/hostapd-phy0.conf
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): Failed to initialize interface
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): cat: can’t open ‚/var/run/wifi-phy0.pid‘: No such file or directory
Sun Jan 23 10:22:55 2022 kern.info kernel: [40164.710000] IPv6: ADDRCONF(NETDEV_UP): ibss1: link is not ready
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): Command failed: Invalid argument
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): Device setup failed: HOSTAPD_START_FAILED
Sun Jan 23 10:22:55 2022 kern.info kernel: [40164.760000] ibss1: Created IBSS using preconfigured BSSID 0a:00:ba:dc:ab:1e
Sun Jan 23 10:22:55 2022 kern.info kernel: [40164.770000] ibss1: Creating new IBSS network, BSSID 0a:00:ba:dc:ab:1e
Sun Jan 23 10:22:55 2022 kern.info kernel: [40164.780000] IPv6: ADDRCONF(NETDEV_CHANGE): ibss1: link becomes ready
Sun Jan 23 10:22:55 2022 daemon.notice netifd: Network device ‚ibss1‘ link is up
Sun Jan 23 10:22:56 2022 daemon.notice netifd: Interface ‚ibss_radio1‘ is enabled
Sun Jan 23 10:22:56 2022 daemon.notice netifd: Interface ‚ibss_radio1‘ has link connectivity
Sun Jan 23 10:22:56 2022 daemon.notice netifd: Interface ‚ibss_radio1‘ is setting up now
Sun Jan 23 10:22:56 2022 daemon.notice netifd: Network device ‚client1‘ link is up
Sun Jan 23 10:22:56 2022 kern.info kernel: [40165.630000] batman_adv: bat0: Adding interface: ibss1
Sun Jan 23 10:22:56 2022 kern.info kernel: [40165.640000] batman_adv: bat0: Interface activated: ibss1
Sun Jan 23 10:22:56 2022 daemon.notice netifd: Interface ‚ibss_radio1‘ is now up
Sun Jan 23 10:22:57 2022 kern.info kernel: [40166.470000] br-client: port 2(client1) entered forwarding state

Blockzitat

5

Du hast Dir selbst in den Fuß geschossen mit Deinem Private-Wifi.
Fehlermeldung steht da ja:

Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): Configuration file: /var/run/hostapd-phy0.conf
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): Duplicate BSSID 10:fe:ed:84:5f:f9 on interface ‚clientpsk‘ and ‚client0‘.
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): 1 errors found in configuration file ‚/var/run/hostapd-phy0.conf‘
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): Failed to set up interface with /var/run/hostapd-phy0.conf
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): Failed to initialize interface
Sun Jan 23 10:22:55 2022 daemon.notice netifd: radio0 (28841): cat: can’t open ‚/var/run/wifi-phy0.pid‘:

Ich habe mal im anderen Thread eine Warnung drangeschrieben.

6

Das ist das erste Gerät das deswegen meckert. Hmmm… Blöd.

Gibt es noch Rettung? Wie kann ich das beheben?

7

Wie im anderen Thread geschrieben: Anleitung von Gluon oder aus dem Freifunk-Wiki benutzen.

8

Für mein Verständnis. Ich möchte ja lernen.

Wo ist der technische Unterschied? Ich brauche ein zusätzliches WLAN das auch über das WIfi Mesh geht…Das macht das „private WLAN“ doch nicht, oder?

9

Das löschen des privaten WLAN, bzw, das hinzufügen eines privaten WLAN hat nicht geholfen.
Ich habe meinen „Kniff“ für den Rasenmäher im Wiki ebenfalls gefunden. Steht etwas weiter unter.
https://wiki.freifunk.net/Konsole#Extra_verschl.C3.BCsseltes_Freifunk-WLAN_anbieten

10

Dies steht in der fehlerhaften Datei.

interface=clientpsk                                                      
ctrl_interface=/var/run/hostapd                                          
ap_isolate=1                                                             
disassoc_low_ack=1                                                       
preamble=1                                                               
wmm_enabled=1                                                            
ignore_broadcast_ssid=0                                                  
uapsd_advertisement_enabled=1                                            
wpa_passphrase=!RasenMaeher!                                             
auth_algs=1                                                              
wpa=2                                                                    
wpa_pairwise=CCMP                                                        
ssid=Outdoor                                                             
bridge=br-client                                                         
wpa_key_mgmt=WPA-PSK                                                     
okc=0                                                                    
disable_pmksa_caching=1        
bssid=10:fe:ed:84:5f:f9        
                               
                             
bss=client0                  
ctrl_interface=/var/run/hostapd
ap_isolate=1                   
disassoc_low_ack=1             
preamble=1                     
wmm_enabled=1                  
ignore_broadcast_ssid=0        
uapsd_advertisement_enabled=1  
auth_algs=1                    
wpa=0                          
ssid=pinneberg.freifunk.net    
bridge=br-client               
bssid=10:fe:ed:84:5f:f9
11

Auf einem meiner funktionierenden Router sieht das so aus:

interface=client0                                                        
ctrl_interface=/var/run/hostapd                                          
ap_isolate=1                                                             
disassoc_low_ack=1                                                       
preamble=1                                                               
wmm_enabled=1                                                            
ignore_broadcast_ssid=0                                                  
uapsd_advertisement_enabled=1                                            
auth_algs=1                                                              
wpa=0                                                                    
ssid=pinneberg.freifunk.net                                              
bridge=br-client                                                         
bssid=e2:f6:eb:57:a6:d0                                                  
                                                                         
                                                                         
bss=clientpsk                  
ctrl_interface=/var/run/hostapd
ap_isolate=1                   
disassoc_low_ack=1             
preamble=1                     
wmm_enabled=1                  
ignore_broadcast_ssid=0        
uapsd_advertisement_enabled=1  
wpa_passphrase=rasenmaeher     
auth_algs=1                    
wpa=2                          
wpa_pairwise=CCMP              
ssid=rasenmaeher               
bridge=br-client               
wpa_key_mgmt=WPA-PSK           
okc=0                          
disable_pmksa_caching=1        
bssid=ec:08:6b:57:fb:d4
12

Spontan fällt mir folgender Unterschied auf:
„defekten“ Router:
interface=clientpsk
bss=client0

„laufender“ Router:
interface=client0
bss=clientpsk

Könnte es daran liegen? Wie kriege ich das berichtigt?
Editor vi scheint meine Änderungen mit :wq nicht speichern zu wollen.

Der laufende Router hat als
Interface=client0 die Definitionen für den Freifunk und als bss=clientpsk das zusätzliche WLAN für IoT Geräte stehen:
Bei dem defekten Router steht als Interface=clientpsk das zusätzliche WLAN für IoT Geräte und als bss=client0 die Definitionen für den Freifunk.

Das ist das Ergebnis von diesem Config Anpassungen

echo "config wifi-iface 'client_radiopsk'
       option ifname 'clientpsk'
       option network 'client'
       option disabled '0'
       option device 'radio0'
       option mode 'ap'
       option ssid 'freifunk als Passwort'
       option encryption 'psk2+ccmp'
       option key 'freifunk'
   " | ssh root@$ROUTER_IP 'cat >> /etc/config/wireless'
ssh root@$ROUTER_IP "wifi"

Aus dem deutschen Wiki: IoT Geräte im Freifunk einbinden

13

Ich habe den defekten Router nun im Konfig Modus gestartet und die 2,4GHz Antenne komplett deaktiviert:

Bildschirmfoto von 2022-01-23 19-00-43
Bildschirmfoto von 2022-01-23 19-00-43757×387 31.2 KB

Mit dieser Einstellung habe ich über die Extra „IoT SSID“ Zugang zum Internet. Auf der 2,4GHz Antenne wird kein Mesh hergestellt.

Im zweiten Versuch aktivierte ich den Button „Mesh aktivieren“ und lasse Client aktivieren aus.
Mit dieser Einstellung habe ich über die Extra „IoT SSID“ Zugang zum Internet. Auf der 2,4GHz Antenne wird jetzt ein Mesh hergestellt.

Wie bekomme ich den Client Acess auch noch an, ohne das mir das Mesh und die „Extra IoT SSID“ wieder aus geht?

14 
`Sun Jan 23 19:21:18 2022 daemon.notice netifd: radio1 (3167): client1: interface state COUNTRY_UPDATE->ENABLED
Sun Jan 23 19:21:18 2022 daemon.notice netifd: radio1 (3167): client1: AP-ENABLED 
Sun Jan 23 19:21:18 2022 kern.info kernel: [  519.130000] IPv6: ADDRCONF(NETDEV_CHANGE): client1: link becomes ready
Sun Jan 23 19:21:18 2022 kern.info kernel: [  519.350000] IPv6: ADDRCONF(NETDEV_UP): ibss1: link is not ready
Sun Jan 23 19:21:18 2022 kern.info kernel: [  519.380000] ibss1: Created IBSS using preconfigured BSSID 0a:00:ba:dc:ab:1e
Sun Jan 23 19:21:18 2022 kern.info kernel: [  519.390000] ibss1: Creating new IBSS network, BSSID 0a:00:ba:dc:ab:1e
Sun Jan 23 19:21:18 2022 kern.info kernel: [  519.400000] IPv6: ADDRCONF(NETDEV_CHANGE): ibss1: link becomes ready
Sun Jan 23 19:21:18 2022 daemon.notice netifd: Network device 'ibss1' link is up
Sun Jan 23 19:21:18 2022 daemon.notice netifd: Interface 'ibss_radio1' is enabled
Sun Jan 23 19:21:18 2022 daemon.notice netifd: Interface 'ibss_radio1' has link connectivity 
Sun Jan 23 19:21:18 2022 daemon.notice netifd: Interface 'ibss_radio1' is setting up now
Sun Jan 23 19:21:18 2022 daemon.notice netifd: Network device 'client1' link is up
Sun Jan 23 19:21:18 2022 kern.info kernel: [  520.010000] IPv6: ADDRCONF(NETDEV_UP): clientpsk: link is not ready
Sun Jan 23 19:21:18 2022 daemon.notice netifd: radio0 (3251): Configuration file: /var/run/hostapd-phy0.conf
Sun Jan 23 19:21:18 2022 kern.info kernel: [  520.040000] device clientpsk entered promiscuous mode
Sun Jan 23 19:21:18 2022 kern.info kernel: [  520.040000] br-client: port 3(clientpsk) entered forwarding state
Sun Jan 23 19:21:18 2022 kern.info kernel: [  520.050000] br-client: port 3(clientpsk) entered forwarding state
Sun Jan 23 19:21:18 2022 daemon.notice netifd: radio0 (3251): clientpsk: interface state UNINITIALIZED->COUNTRY_UPDATE
Sun Jan 23 19:21:18 2022 daemon.notice netifd: radio0 (3251): Using interface clientpsk with hwaddr 10:fe:ed:84:5f:f9 and ssid "Outdoor"
Sun Jan 23 19:21:19 2022 kern.info kernel: [  520.330000] batman_adv: bat0: Adding interface: ibss1
Sun Jan 23 19:21:19 2022 kern.info kernel: [  520.340000] batman_adv: bat0: Interface activated: ibss1
Sun Jan 23 19:21:19 2022 kern.info kernel: [  520.360000] br-client: port 3(clientpsk) entered disabled state
Sun Jan 23 19:21:19 2022 daemon.notice netifd: Interface 'ibss_radio1' is now up
Sun Jan 23 19:21:19 2022 kern.info kernel: [  521.070000] br-client: port 2(client1) entered forwarding state
Sun Jan 23 19:21:20 2022 kern.info kernel: [  521.220000] IPv6: ADDRCONF(NETDEV_CHANGE): clientpsk: link becomes ready
Sun Jan 23 19:21:20 2022 kern.info kernel: [  521.230000] br-client: port 3(clientpsk) entered forwarding state
Sun Jan 23 19:21:20 2022 kern.info kernel: [  521.230000] br-client: port 3(clientpsk) entered forwarding state
Sun Jan 23 19:21:20 2022 daemon.notice netifd: radio0 (3251): clientpsk: interface state COUNTRY_UPDATE->ENABLED
Sun Jan 23 19:21:20 2022 daemon.notice netifd: radio0 (3251): clientpsk: AP-ENABLED 
Sun Jan 23 19:21:20 2022 daemon.info fastd[1982]: resolving host `gate04.freifunk-pinneberg.de' for peer <mesh_vpn_backbone_peer_gate04>...
Sun Jan 23 19:21:20 2022 daemon.info fastd[1982]: resolving host `gate04.freifunk-pinneberg.de' failed: Name or service not known
Sun Jan 23 19:21:20 2022 kern.info kernel: [  521.460000] IPv6: ADDRCONF(NETDEV_UP): ibss0: link is not ready
Sun Jan 23 19:21:20 2022 kern.info kernel: [  521.500000] ibss0: Created IBSS using preconfigured BSSID 0a:00:ba:dc:ab:1e
Sun Jan 23 19:21:20 2022 kern.info kernel: [  521.510000] ibss0: Creating new IBSS network, BSSID 0a:00:ba:dc:ab:1e
Sun Jan 23 19:21:20 2022 kern.info kernel: [  521.520000] IPv6: ADDRCONF(NETDEV_CHANGE): ibss0: link becomes ready
Sun Jan 23 19:21:20 2022 daemon.notice netifd: Network device 'ibss0' link is up
Sun Jan 23 19:21:20 2022 daemon.notice netifd: Network device 'clientpsk' link is up
Sun Jan 23 19:21:20 2022 daemon.notice netifd: Interface 'ibss_radio0' is enabled
Sun Jan 23 19:21:20 2022 daemon.notice netifd: Interface 'ibss_radio0' has link connectivity 
Sun Jan 23 19:21:20 2022 daemon.notice netifd: Interface 'ibss_radio0' is setting up now
Sun Jan 23 19:21:20 2022 daemon.info fastd[1982]: resolving host `gate05.pinneberg.freifunk.net' for peer <mesh_vpn_backbone_peer_gate05>...
Sun Jan 23 19:21:21 2022 daemon.info fastd[1982]: resolving host `gate05.pinneberg.freifunk.net' failed: Name or service not known
Sun Jan 23 19:21:21 2022 kern.info kernel: [  522.170000] batman_adv: bat0: Adding interface: ibss0
Sun Jan 23 19:21:21 2022 kern.info kernel: [  522.170000] batman_adv: bat0: Interface activated: ibss0
Sun Jan 23 19:21:21 2022 daemon.notice netifd: Interface 'ibss_radio0' is now up
Sun Jan 23 19:21:22 2022 kern.info kernel: [  523.230000] br-client: port 3(clientpsk) entered forwarding state
Sun Jan 23 19:21:27 2022 daemon.info fastd[1982]: resolving host `gate03.freifunk-pinneberg.de' for peer <mesh_vpn_backbone_peer_gate03>...
Sun Jan 23 19:21:27 2022 daemon.info fastd[1982]: resolving host `gate03.freifunk-pinneberg.de' failed: Name or service not known
Sun Jan 23 19:21:33 2022 daemon.info fastd[1982]: resolving host `gate01.pinneberg.freifunk.net' for peer <mesh_vpn_backbone_peer_gate01>...
Sun Jan 23 19:21:33 2022 daemon.info fastd[1982]: resolving host `gate01.pinneberg.freifunk.net' failed: Name or service not known
`