[v3] fff-hoods: Use channel provided by gateway

Submitted by Fabian Blaese on Oct. 9, 2017, 3:56 p.m.

Details

Message ID 20171009155639.30709-1-fabian@blaese.de
State Superseded
Headers show

Commit Message

Fabian Blaese Oct. 9, 2017, 3:56 p.m. 
From: Adrian Schmutzler <freifunk@adrianschmutzler.de>

Only apply after keyXv2 patchset!

Changes in v2:
- rebase due to conflict with 802.11s

Changes in v3:
- Fix wrong variable name introduced in v2

Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Signed-off-by: Fabian Bläse <fabian@blaese.de>
---
 src/packages/fff/fff-hoods/files/usr/sbin/configurehood | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

Patch hide | download patch | download mbox 

diff --git a/src/packages/fff/fff-hoods/files/usr/sbin/configurehood b/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
index 6ff7104..cf5a84b 100755
--- a/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
+++ b/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
@@ -74,8 +74,8 @@  else
 		fi
 		#now we look for phy and add this
 		for phy in $(iw phy | awk '/^Wiphy/{ print $2 }'); do
-			radio="$(wifiAddPhyCond "$phy" "2" "$chan2ghz")"
-			radio5="$(wifiAddPhyCond "$phy" "5" "$chan5ghz")"
+			radio="$(wifiAddPhyCond "$phy" "2" "auto")"
+			radio5="$(wifiAddPhyCond "$phy" "5" "auto")"
 			[ -n "$radio5" ] && radio="$radio5"
 
 			#and here we add the station
@@ -125,10 +125,10 @@  if [ -s /tmp/keyxchangev2data ]; then
 		json_get_var essid essid
 		json_get_var ntpip ntp_ip
 		# i think the next things we don't active this in the first version! we can do it later
-		#json_get_var channel2 channel2
+		json_get_var chan2ghz channel2
 		#json_get_var mode2 mode2
 		json_get_var mesh_type2 mesh_type2
-		#json_get_var channel5 channel5
+		json_get_var chan5ghz channel5
 		#json_get_var mode5 mode5
 		json_get_var mesh_type5 mesh_type5
 		#json_get_var protocol protocol

Comments

Christian Dresel Oct. 10, 2017, 3:09 p.m. 
hi

On 09.10.2017 17:56, Fabian Bläse wrote:
> From: Adrian Schmutzler <freifunk@adrianschmutzler.de>
> 
> Only apply after keyXv2 patchset!
> 
> Changes in v2:
> - rebase due to conflict with 802.11s
> 
> Changes in v3:
> - Fix wrong variable name introduced in v2
> 
> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
> Signed-off-by: Fabian Bläse <fabian@blaese.de>
> ---
>  src/packages/fff/fff-hoods/files/usr/sbin/configurehood | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/src/packages/fff/fff-hoods/files/usr/sbin/configurehood b/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
> index 6ff7104..cf5a84b 100755
> --- a/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
> +++ b/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
> @@ -74,8 +74,8 @@ else
>  		fi
>  		#now we look for phy and add this
>  		for phy in $(iw phy | awk '/^Wiphy/{ print $2 }'); do
> -			radio="$(wifiAddPhyCond "$phy" "2" "$chan2ghz")"
> -			radio5="$(wifiAddPhyCond "$phy" "5" "$chan5ghz")"
> +			radio="$(wifiAddPhyCond "$phy" "2" "auto")"
> +			radio5="$(wifiAddPhyCond "$phy" "5" "auto")"
>  			[ -n "$radio5" ] && radio="$radio5"
>  
>  			#and here we add the station
> @@ -125,10 +125,10 @@ if [ -s /tmp/keyxchangev2data ]; then
>  		json_get_var essid essid
>  		json_get_var ntpip ntp_ip
>  		# i think the next things we don't active this in the first version! we can do it later

auch hier passt der Kommentar nicht mehr, bitte mit
http://lists.freifunk.net/pipermail/franken-dev-freifunk.net/2017-October/012859.html
absprechen damit sich hier nix überschneidet ;)

mfg

Christian

> -		#json_get_var channel2 channel2
> +		json_get_var chan2ghz channel2
>  		#json_get_var mode2 mode2
>  		json_get_var mesh_type2 mesh_type2
> -		#json_get_var channel5 channel5
> +		json_get_var chan5ghz channel5
>  		#json_get_var mode5 mode5
>  		json_get_var mesh_type5 mesh_type5
>  		#json_get_var protocol protocol
>
Christian Dresel Oct. 10, 2017, 4:39 p.m. 
hi

ich hab grad mal ein paar Situationen durchgespielt, "was wäre wenn" Spiele.

Aktuelle Situation:
 - Uplinkrouter ist aus
 - Meshrouter sucht per w2sta nach nen hidden AP findet aber keinen da
keiner vorhanden

Folgende Ausgabe wenn ich /usr/sbin/configurehood aufrufen (hab es davor
schon einige male aufgerufen, ist also nicht der erste Aufruf daher
fehlen schon Files):

root@Test:~# /usr/sbin/configurehood
rm: can't remove '/tmp/keyxchangev2data': No such file or directory
rm: can't remove '/www/public/keyxchangev2data': No such file or directory
sh: auto: out of range
sh: auto: out of range
w2sta
Connecting to [fe80::1%w2sta] ([fe80::1%w2sta]:80)
wget: download timed out
We haven't got a file. We do nothing. We try it again in 5 minutes...

stutzig macht mich die Zeilen:
sh: auto: out of range

Kommt das durch den Autokanalwahl für den wXsta? Wenn ich den
Uplinkrouter wieder einschalte, scheint er ihn aber dennoch zu finden.

root@Test:~# /usr/sbin/configurehood
rm: can't remove '/tmp/keyxchangev2data': No such file or directory
rm: can't remove '/www/public/keyxchangev2data': No such file or directory
sh: auto: out of range
sh: auto: out of range
w2sta
Connecting to [fe80::1%w2sta] ([fe80::1%w2sta]:80)
New file detect, we reconfigure the Node
Setting hood name: FuerthV2
w2ap
w2mesh
Loading wifi
Address already set.
Address already set.
Route already set.
root@Test:~#

Dennoch irritiert mich die Zeile ein wenig.

mfg

Christian


On 10.10.2017 17:09, Christian Dresel wrote:
> hi
> 
> On 09.10.2017 17:56, Fabian Bläse wrote:
>> From: Adrian Schmutzler <freifunk@adrianschmutzler.de>
>>
>> Only apply after keyXv2 patchset!
>>
>> Changes in v2:
>> - rebase due to conflict with 802.11s
>>
>> Changes in v3:
>> - Fix wrong variable name introduced in v2
>>
>> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
>> Signed-off-by: Fabian Bläse <fabian@blaese.de>
>> ---
>>  src/packages/fff/fff-hoods/files/usr/sbin/configurehood | 8 ++++----
>>  1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/src/packages/fff/fff-hoods/files/usr/sbin/configurehood b/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
>> index 6ff7104..cf5a84b 100755
>> --- a/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
>> +++ b/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
>> @@ -74,8 +74,8 @@ else
>>  		fi
>>  		#now we look for phy and add this
>>  		for phy in $(iw phy | awk '/^Wiphy/{ print $2 }'); do
>> -			radio="$(wifiAddPhyCond "$phy" "2" "$chan2ghz")"
>> -			radio5="$(wifiAddPhyCond "$phy" "5" "$chan5ghz")"
>> +			radio="$(wifiAddPhyCond "$phy" "2" "auto")"
>> +			radio5="$(wifiAddPhyCond "$phy" "5" "auto")"
>>  			[ -n "$radio5" ] && radio="$radio5"
>>  
>>  			#and here we add the station
>> @@ -125,10 +125,10 @@ if [ -s /tmp/keyxchangev2data ]; then
>>  		json_get_var essid essid
>>  		json_get_var ntpip ntp_ip
>>  		# i think the next things we don't active this in the first version! we can do it later
> 
> auch hier passt der Kommentar nicht mehr, bitte mit
> http://lists.freifunk.net/pipermail/franken-dev-freifunk.net/2017-October/012859.html
> absprechen damit sich hier nix überschneidet ;)
> 
> mfg
> 
> Christian
> 
>> -		#json_get_var channel2 channel2
>> +		json_get_var chan2ghz channel2
>>  		#json_get_var mode2 mode2
>>  		json_get_var mesh_type2 mesh_type2
>> -		#json_get_var channel5 channel5
>> +		json_get_var chan5ghz channel5
>>  		#json_get_var mode5 mode5
>>  		json_get_var mesh_type5 mesh_type5
>>  		#json_get_var protocol protocol
>>
> 
> 
>
Fabian Blaese Oct. 11, 2017, 7:28 a.m. 
Hi Christian,

Das kommt aus der Überprüfung in fff-wireless, ob der Kanal 2,4 oder 5 GHz ist. Siehe dazu auch mein Kommentar im fff-wireless Patch.

Fabian

On 10 October 2017 18:39:45 GMT+02:00, Christian Dresel <fff@chrisi01.de> wrote:
>hi
>
>ich hab grad mal ein paar Situationen durchgespielt, "was wäre wenn"
>Spiele.
>
>Aktuelle Situation:
> - Uplinkrouter ist aus
> - Meshrouter sucht per w2sta nach nen hidden AP findet aber keinen da
>keiner vorhanden
>
>Folgende Ausgabe wenn ich /usr/sbin/configurehood aufrufen (hab es
>davor
>schon einige male aufgerufen, ist also nicht der erste Aufruf daher
>fehlen schon Files):
>
>root@Test:~# /usr/sbin/configurehood
>rm: can't remove '/tmp/keyxchangev2data': No such file or directory
>rm: can't remove '/www/public/keyxchangev2data': No such file or
>directory
>sh: auto: out of range
>sh: auto: out of range
>w2sta
>Connecting to [fe80::1%w2sta] ([fe80::1%w2sta]:80)
>wget: download timed out
>We haven't got a file. We do nothing. We try it again in 5 minutes...
>
>stutzig macht mich die Zeilen:
>sh: auto: out of range
>
>Kommt das durch den Autokanalwahl für den wXsta? Wenn ich den
>Uplinkrouter wieder einschalte, scheint er ihn aber dennoch zu finden.
>
>root@Test:~# /usr/sbin/configurehood
>rm: can't remove '/tmp/keyxchangev2data': No such file or directory
>rm: can't remove '/www/public/keyxchangev2data': No such file or
>directory
>sh: auto: out of range
>sh: auto: out of range
>w2sta
>Connecting to [fe80::1%w2sta] ([fe80::1%w2sta]:80)
>New file detect, we reconfigure the Node
>Setting hood name: FuerthV2
>w2ap
>w2mesh
>Loading wifi
>Address already set.
>Address already set.
>Route already set.
>root@Test:~#
>
>Dennoch irritiert mich die Zeile ein wenig.
>
>mfg
>
>Christian
>
>
>On 10.10.2017 17:09, Christian Dresel wrote:
>> hi
>> 
>> On 09.10.2017 17:56, Fabian Bläse wrote:
>>> From: Adrian Schmutzler <freifunk@adrianschmutzler.de>
>>>
>>> Only apply after keyXv2 patchset!
>>>
>>> Changes in v2:
>>> - rebase due to conflict with 802.11s
>>>
>>> Changes in v3:
>>> - Fix wrong variable name introduced in v2
>>>
>>> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
>>> Signed-off-by: Fabian Bläse <fabian@blaese.de>
>>> ---
>>>  src/packages/fff/fff-hoods/files/usr/sbin/configurehood | 8
>++++----
>>>  1 file changed, 4 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
>b/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
>>> index 6ff7104..cf5a84b 100755
>>> --- a/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
>>> +++ b/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
>>> @@ -74,8 +74,8 @@ else
>>>  		fi
>>>  		#now we look for phy and add this
>>>  		for phy in $(iw phy | awk '/^Wiphy/{ print $2 }'); do
>>> -			radio="$(wifiAddPhyCond "$phy" "2" "$chan2ghz")"
>>> -			radio5="$(wifiAddPhyCond "$phy" "5" "$chan5ghz")"
>>> +			radio="$(wifiAddPhyCond "$phy" "2" "auto")"
>>> +			radio5="$(wifiAddPhyCond "$phy" "5" "auto")"
>>>  			[ -n "$radio5" ] && radio="$radio5"
>>>  
>>>  			#and here we add the station
>>> @@ -125,10 +125,10 @@ if [ -s /tmp/keyxchangev2data ]; then
>>>  		json_get_var essid essid
>>>  		json_get_var ntpip ntp_ip
>>>  		# i think the next things we don't active this in the first
>version! we can do it later
>> 
>> auch hier passt der Kommentar nicht mehr, bitte mit
>>
>http://lists.freifunk.net/pipermail/franken-dev-freifunk.net/2017-October/012859.html
>> absprechen damit sich hier nix überschneidet ;)
>> 
>> mfg
>> 
>> Christian
>> 
>>> -		#json_get_var channel2 channel2
>>> +		json_get_var chan2ghz channel2
>>>  		#json_get_var mode2 mode2
>>>  		json_get_var mesh_type2 mesh_type2
>>> -		#json_get_var channel5 channel5
>>> +		json_get_var chan5ghz channel5
>>>  		#json_get_var mode5 mode5
>>>  		json_get_var mesh_type5 mesh_type5
>>>  		#json_get_var protocol protocol
>>>
>> 
>> 
>>
Adrian Schmutzler Oct. 13, 2017, 3:12 p.m. 
Hallo,

das mit dem auto/out of range werde ich am WE schön machen.

Wo ich mir nicht sicher bin, ist ob man die "can't remove" Meldungen unterdrücken sollte. Meinungen?

Grüße

Adrian

> -----Original Message-----
> From: Christian Dresel [mailto:fff@chrisi01.de]
> Sent: Dienstag, 10. Oktober 2017 18:40
> To: Fabian Bläse <fabian@blaese.de>; franken-dev@freifunk.net
> Cc: Adrian Schmutzler <freifunk@adrianschmutzler.de>
> Subject: Re: [PATCH v3] fff-hoods: Use channel provided by gateway
> 
> hi
> 
> ich hab grad mal ein paar Situationen durchgespielt, "was wäre wenn" Spiele.
> 
> Aktuelle Situation:
>  - Uplinkrouter ist aus
>  - Meshrouter sucht per w2sta nach nen hidden AP findet aber keinen da
> keiner vorhanden
> 
> Folgende Ausgabe wenn ich /usr/sbin/configurehood aufrufen (hab es davor
> schon einige male aufgerufen, ist also nicht der erste Aufruf daher fehlen
> schon Files):
> 
> root@Test:~# /usr/sbin/configurehood
> rm: can't remove '/tmp/keyxchangev2data': No such file or directory
> rm: can't remove '/www/public/keyxchangev2data': No such file or directory
> sh: auto: out of range
> sh: auto: out of range
> w2sta
> Connecting to [fe80::1%w2sta] ([fe80::1%w2sta]:80)
> wget: download timed out
> We haven't got a file. We do nothing. We try it again in 5 minutes...
> 
> stutzig macht mich die Zeilen:
> sh: auto: out of range
> 
> Kommt das durch den Autokanalwahl für den wXsta? Wenn ich den
> Uplinkrouter wieder einschalte, scheint er ihn aber dennoch zu finden.
> 
> root@Test:~# /usr/sbin/configurehood
> rm: can't remove '/tmp/keyxchangev2data': No such file or directory
> rm: can't remove '/www/public/keyxchangev2data': No such file or directory
> sh: auto: out of range
> sh: auto: out of range
> w2sta
> Connecting to [fe80::1%w2sta] ([fe80::1%w2sta]:80) New file detect, we
> reconfigure the Node Setting hood name: FuerthV2 w2ap w2mesh Loading
> wifi Address already set.
> Address already set.
> Route already set.
> root@Test:~#
> 
> Dennoch irritiert mich die Zeile ein wenig.
> 
> mfg
> 
> Christian
> 
> 
> On 10.10.2017 17:09, Christian Dresel wrote:
> > hi
> >
> > On 09.10.2017 17:56, Fabian Bläse wrote:
> >> From: Adrian Schmutzler <freifunk@adrianschmutzler.de>
> >>
> >> Only apply after keyXv2 patchset!
> >>
> >> Changes in v2:
> >> - rebase due to conflict with 802.11s
> >>
> >> Changes in v3:
> >> - Fix wrong variable name introduced in v2
> >>
> >> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
> >> Signed-off-by: Fabian Bläse <fabian@blaese.de>
> >> ---
> >>  src/packages/fff/fff-hoods/files/usr/sbin/configurehood | 8 ++++----
> >>  1 file changed, 4 insertions(+), 4 deletions(-)
> >>
> >> diff --git a/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
> >> b/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
> >> index 6ff7104..cf5a84b 100755
> >> --- a/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
> >> +++ b/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
> >> @@ -74,8 +74,8 @@ else
> >>  		fi
> >>  		#now we look for phy and add this
> >>  		for phy in $(iw phy | awk '/^Wiphy/{ print $2 }'); do
> >> -			radio="$(wifiAddPhyCond "$phy" "2" "$chan2ghz")"
> >> -			radio5="$(wifiAddPhyCond "$phy" "5" "$chan5ghz")"
> >> +			radio="$(wifiAddPhyCond "$phy" "2" "auto")"
> >> +			radio5="$(wifiAddPhyCond "$phy" "5" "auto")"
> >>  			[ -n "$radio5" ] && radio="$radio5"
> >>
> >>  			#and here we add the station
> >> @@ -125,10 +125,10 @@ if [ -s /tmp/keyxchangev2data ]; then
> >>  		json_get_var essid essid
> >>  		json_get_var ntpip ntp_ip
> >>  		# i think the next things we don't active this in the first
> >> version! we can do it later
> >
> > auch hier passt der Kommentar nicht mehr, bitte mit
> > http://lists.freifunk.net/pipermail/franken-dev-freifunk.net/2017-Octo
> > ber/012859.html absprechen damit sich hier nix überschneidet ;)
> >
> > mfg
> >
> > Christian
> >
> >> -		#json_get_var channel2 channel2
> >> +		json_get_var chan2ghz channel2
> >>  		#json_get_var mode2 mode2
> >>  		json_get_var mesh_type2 mesh_type2
> >> -		#json_get_var channel5 channel5
> >> +		json_get_var chan5ghz channel5
> >>  		#json_get_var mode5 mode5
> >>  		json_get_var mesh_type5 mesh_type5
> >>  		#json_get_var protocol protocol
> >>
> >
> >
> >
Fabian Blaese Oct. 13, 2017, 5:12 p.m. 
Hallo Adrian,

ich würde sie unterdrücken; ist an der Stelle ja gewünschtes Verhalten und ich sehe grade auch nicht, wie das bei Problemen helfen könnte.

Fabian

> On 13. Oct 2017, at 17:12, mail@adrianschmutzler.de wrote:
> 
> Hallo,
> 
> das mit dem auto/out of range werde ich am WE schön machen.
> 
> Wo ich mir nicht sicher bin, ist ob man die "can't remove" Meldungen unterdrücken sollte. Meinungen?
> 
> Grüße
> 
> Adrian
> 
>> -----Original Message-----
>> From: Christian Dresel [mailto:fff@chrisi01.de]
>> Sent: Dienstag, 10. Oktober 2017 18:40
>> To: Fabian Bläse <fabian@blaese.de>; franken-dev@freifunk.net
>> Cc: Adrian Schmutzler <freifunk@adrianschmutzler.de>
>> Subject: Re: [PATCH v3] fff-hoods: Use channel provided by gateway
>> 
>> hi
>> 
>> ich hab grad mal ein paar Situationen durchgespielt, "was wäre wenn" Spiele.
>> 
>> Aktuelle Situation:
>> - Uplinkrouter ist aus
>> - Meshrouter sucht per w2sta nach nen hidden AP findet aber keinen da
>> keiner vorhanden
>> 
>> Folgende Ausgabe wenn ich /usr/sbin/configurehood aufrufen (hab es davor
>> schon einige male aufgerufen, ist also nicht der erste Aufruf daher fehlen
>> schon Files):
>> 
>> root@Test:~# /usr/sbin/configurehood
>> rm: can't remove '/tmp/keyxchangev2data': No such file or directory
>> rm: can't remove '/www/public/keyxchangev2data': No such file or directory
>> sh: auto: out of range
>> sh: auto: out of range
>> w2sta
>> Connecting to [fe80::1%w2sta] ([fe80::1%w2sta]:80)
>> wget: download timed out
>> We haven't got a file. We do nothing. We try it again in 5 minutes...
>> 
>> stutzig macht mich die Zeilen:
>> sh: auto: out of range
>> 
>> Kommt das durch den Autokanalwahl für den wXsta? Wenn ich den
>> Uplinkrouter wieder einschalte, scheint er ihn aber dennoch zu finden.
>> 
>> root@Test:~# /usr/sbin/configurehood
>> rm: can't remove '/tmp/keyxchangev2data': No such file or directory
>> rm: can't remove '/www/public/keyxchangev2data': No such file or directory
>> sh: auto: out of range
>> sh: auto: out of range
>> w2sta
>> Connecting to [fe80::1%w2sta] ([fe80::1%w2sta]:80) New file detect, we
>> reconfigure the Node Setting hood name: FuerthV2 w2ap w2mesh Loading
>> wifi Address already set.
>> Address already set.
>> Route already set.
>> root@Test:~#
>> 
>> Dennoch irritiert mich die Zeile ein wenig.
>> 
>> mfg
>> 
>> Christian
>> 
>> 
>> On 10.10.2017 17:09, Christian Dresel wrote:
>>> hi
>>> 
>>> On 09.10.2017 17:56, Fabian Bläse wrote:
>>>> From: Adrian Schmutzler <freifunk@adrianschmutzler.de>
>>>> 
>>>> Only apply after keyXv2 patchset!
>>>> 
>>>> Changes in v2:
>>>> - rebase due to conflict with 802.11s
>>>> 
>>>> Changes in v3:
>>>> - Fix wrong variable name introduced in v2
>>>> 
>>>> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
>>>> Signed-off-by: Fabian Bläse <fabian@blaese.de>
>>>> ---
>>>> src/packages/fff/fff-hoods/files/usr/sbin/configurehood | 8 ++++----
>>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>>> 
>>>> diff --git a/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
>>>> b/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
>>>> index 6ff7104..cf5a84b 100755
>>>> --- a/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
>>>> +++ b/src/packages/fff/fff-hoods/files/usr/sbin/configurehood
>>>> @@ -74,8 +74,8 @@ else
>>>> 		fi
>>>> 		#now we look for phy and add this
>>>> 		for phy in $(iw phy | awk '/^Wiphy/{ print $2 }'); do
>>>> -			radio="$(wifiAddPhyCond "$phy" "2" "$chan2ghz")"
>>>> -			radio5="$(wifiAddPhyCond "$phy" "5" "$chan5ghz")"
>>>> +			radio="$(wifiAddPhyCond "$phy" "2" "auto")"
>>>> +			radio5="$(wifiAddPhyCond "$phy" "5" "auto")"
>>>> 			[ -n "$radio5" ] && radio="$radio5"
>>>> 
>>>> 			#and here we add the station
>>>> @@ -125,10 +125,10 @@ if [ -s /tmp/keyxchangev2data ]; then
>>>> 		json_get_var essid essid
>>>> 		json_get_var ntpip ntp_ip
>>>> 		# i think the next things we don't active this in the first
>>>> version! we can do it later
>>> 
>>> auch hier passt der Kommentar nicht mehr, bitte mit
>>> http://lists.freifunk.net/pipermail/franken-dev-freifunk.net/2017-Octo
>>> ber/012859.html absprechen damit sich hier nix überschneidet ;)
>>> 
>>> mfg
>>> 
>>> Christian
>>> 
>>>> -		#json_get_var channel2 channel2
>>>> +		json_get_var chan2ghz channel2
>>>> 		#json_get_var mode2 mode2
>>>> 		json_get_var mesh_type2 mesh_type2
>>>> -		#json_get_var channel5 channel5
>>>> +		json_get_var chan5ghz channel5
>>>> 		#json_get_var mode5 mode5
>>>> 		json_get_var mesh_type5 mesh_type5
>>>> 		#json_get_var protocol protocol
>>>> 
>>> 
>>> 
>>> 
> 
> 
> --
> franken-dev mailing list
> franken-dev@freifunk.net
> http://lists.freifunk.net/mailman/listinfo/franken-dev-freifunk.net