| Message ID | 20171030153602.2027-1-fff@chrisi01.de |
|---|---|
| State | Changes Requested |
| Headers | show |
diff --git a/bsp/ar71xx/.config b/bsp/ar71xx/.config index 0a5b9b9..bf2a2f4 100644 --- a/bsp/ar71xx/.config +++ b/bsp/ar71xx/.config @@ -66,6 +66,8 @@ CONFIG_TARGET_DEVICE_ar71xx_generic_DEVICE_ubnt-nano-m=y CONFIG_TARGET_DEVICE_PACKAGES_ar71xx_generic_DEVICE_ubnt-nano-m="" CONFIG_TARGET_DEVICE_ar71xx_generic_DEVICE_ubnt-unifi=y CONFIG_TARGET_DEVICE_PACKAGES_ar71xx_generic_DEVICE_ubnt-unifi="" +CONFIG_TARGET_DEVICE_ar71xx_generic_DEVICE_ubnt-unifiac-lite=y +CONFIG_TARGET_DEVICE_PACKAGES_ar71xx_generic_DEVICE_ubnt-unifiac-lite="-kmod-ath10k kmod-ath10k-ct" CONFIG_BUSYBOX_CUSTOM=y CONFIG_TARGET_PER_DEVICE_ROOTFS=y # CONFIG_BUSYBOX_CONFIG_BRCTL is not set diff --git a/bsp/board_ar71xx.bsp b/bsp/board_ar71xx.bsp index 1137b0d..71baba4 100644 --- a/bsp/board_ar71xx.bsp +++ b/bsp/board_ar71xx.bsp @@ -26,6 +26,7 @@ images=("lede-ar71xx-generic-cpe210-220-squashfs-sysupgrade.bin" "lede-ar71xx-generic-tl-mr3020-v1-squashfs-sysupgrade.bin" "lede-ar71xx-generic-ubnt-bullet-m-squashfs-sysupgrade.bin" "lede-ar71xx-generic-ubnt-unifi-squashfs-sysupgrade.bin" + "lede-ar71xx-generic-ubnt-unifiac-lite-squashfs-sysupgrade.bin" "lede-ar71xx-generic-tl-wdr3500-v1-squashfs-sysupgrade.bin" "lede-ar71xx-generic-tl-wdr3600-v1-squashfs-sysupgrade.bin" "lede-ar71xx-generic-tl-wdr4300-v1-squashfs-sysupgrade.bin" diff --git a/src/packages/fff/fff-boardname/Makefile b/src/packages/fff/fff-boardname/Makefile index 31e6731..499ae91 100644 --- a/src/packages/fff/fff-boardname/Makefile +++ b/src/packages/fff/fff-boardname/Makefile @@ -1,7 +1,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=fff-boardname -PKG_VERSION:=0.0.2 +PKG_VERSION:=3 PKG_RELEASE:=1 PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME) diff --git a/src/packages/fff/fff-boardname/files/etc/uci-defaults/50-fff-boardname b/src/packages/fff/fff-boardname/files/etc/uci-defaults/50-fff-boardname index 94b9884..45d6db7 100755 --- a/src/packages/fff/fff-boardname/files/etc/uci-defaults/50-fff-boardname +++ b/src/packages/fff/fff-boardname/files/etc/uci-defaults/50-fff-boardname @@ -31,6 +31,9 @@ case "$BOARD" in unifi) BOARD=ubnt-unifi ;; + unifiac-lite) + BOARD=ubnt-unifiac-lite + ;; loco-m-xw) BOARD=ubnt-loco-m-xw ;; diff --git a/src/packages/fff/fff-network/Makefile b/src/packages/fff/fff-network/Makefile index b7805c8..f0c20c6 100644 --- a/src/packages/fff/fff-network/Makefile +++ b/src/packages/fff/fff-network/Makefile @@ -1,7 +1,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=fff-network -PKG_VERSION:=8 +PKG_VERSION:=9 PKG_RELEASE:=1 PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME) diff --git a/src/packages/fff/fff-network/ar71xx/network.ubnt-unifiac-lite b/src/packages/fff/fff-network/ar71xx/network.ubnt-unifiac-lite new file mode 100644 index 0000000..92285ca --- /dev/null +++ b/src/packages/fff/fff-network/ar71xx/network.ubnt-unifiac-lite @@ -0,0 +1,16 @@ +WANDEV=eth0 +SWITCHDEV=eth0 +CLIENT_PORTS="" +WAN_PORTS="" +BATMAN_PORTS="" +ONE_PORT="YES" + +. /etc/network.mode +. /lib/functions/system.sh +. /lib/functions/uci-defaults.sh +. /lib/ar71xx.sh + +# Load second MAC from Flash because we haven't any Interface with this MAC where we can copy the MAC from + +NEWROUTERMAC=$(mtd_get_mac_binary EEPROM 0x0) +ROUTERMAC=w2mesh \ No newline at end of file diff --git a/src/packages/fff/fff-network/files/usr/sbin/configurenetwork b/src/packages/fff/fff-network/files/usr/sbin/configurenetwork index c6b3113..173e270 100755 --- a/src/packages/fff/fff-network/files/usr/sbin/configurenetwork +++ b/src/packages/fff/fff-network/files/usr/sbin/configurenetwork @@ -184,6 +184,10 @@ if [[ -n "$ROUTERMAC" ]]; then echo "Fixing MAC on br-mesh (mesh)" sleep 10 NEW_MACADDR=$(cat /sys/class/net/$ROUTERMAC/address) + # We need this to set the original MAC for the ubnt-unifiac-lite from a variable and not from an Interface + if [[ -n "$NEWROUTERMAC" ]]; then + NEW_MACADDR=$NEWROUTERMAC + fi uci set network.mesh.macaddr=$NEW_MACADDR uci commit ifconfig br-mesh down
Hi Am Montag, den 30.10.2017, 16:36 +0100 schrieb Christian Dresel: > This is the correct firmware for the Unifi AC Mesh > I have only tested at Unifi AC Mesh and not at Unifi AC lite > But my information is, that both have the same Hardware > > Signed-off-by: Christian Dresel <fff@chrisi01.de> > > --- > > v2: > - remove CONFIG_PACKAGE_ATH_DFS=y & CONFIG_ATH_USER_REGD=y because > is already in dependencies > active > - remove tab and use spaces > - remove ETHMESHMAC > - remove debug output in configurenetwork > [..] > diff --git a/src/packages/fff/fff-network/files/usr/sbin/configurenetwork b/src/packages/fff/fff-network/files/usr/sbin/configurenetwork > index c6b3113..173e270 100755 > --- a/src/packages/fff/fff-network/files/usr/sbin/configurenetwork > +++ b/src/packages/fff/fff-network/files/usr/sbin/configurenetwork > @@ -184,6 +184,10 @@ if [[ -n "$ROUTERMAC" ]]; then > echo "Fixing MAC on br-mesh (mesh)" > sleep 10 > NEW_MACADDR=$(cat /sys/class/net/$ROUTERMAC/address) > + # We need this to set the original MAC for the ubnt-unifiac-lite from a variable and not from an Interface > + if [[ -n "$NEWROUTERMAC" ]]; then > + NEW_MACADDR=$NEWROUTERMAC > + fi Hm.. Nee.. Lasst uns das bitte _vorher_ umbauen, dass die MAC Adressen in den network.xx Files gesetzt werden. Tim
Bevor wir den applien, brauchen wir https://pw.freifunk-franken.de/patch/649/ fff-hoods/fff-wireless: Don't delete WiFi devices Sonst kann man das 5 GHz nicht deaktivieren. Grüße Adrian > -----Original Message----- > From: franken-dev [mailto:franken-dev-bounces@freifunk.net] On Behalf > Of Tim Niemeyer > Sent: Freitag, 3. November 2017 14:03 > To: Christian Dresel <fff@chrisi01.de>; franken-dev@freifunk.net > Subject: Re: [PATCH v2] Add support for Unifi AC Mesh > > Hi > > Am Montag, den 30.10.2017, 16:36 +0100 schrieb Christian Dresel: > > This is the correct firmware for the Unifi AC Mesh I have only tested > > at Unifi AC Mesh and not at Unifi AC lite But my information is, that > > both have the same Hardware > > > > Signed-off-by: Christian Dresel <fff@chrisi01.de> > > > > --- > > > > v2: > > - remove CONFIG_PACKAGE_ATH_DFS=y & CONFIG_ATH_USER_REGD=y > because is > > already in dependencies > > active > > - remove tab and use spaces > > - remove ETHMESHMAC > > - remove debug output in configurenetwork > > > [..] > > diff --git > > a/src/packages/fff/fff-network/files/usr/sbin/configurenetwork > > b/src/packages/fff/fff-network/files/usr/sbin/configurenetwork > > index c6b3113..173e270 100755 > > --- a/src/packages/fff/fff-network/files/usr/sbin/configurenetwork > > +++ b/src/packages/fff/fff-network/files/usr/sbin/configurenetwork > > @@ -184,6 +184,10 @@ if [[ -n "$ROUTERMAC" ]]; then > > echo "Fixing MAC on br-mesh (mesh)" > > sleep 10 > > NEW_MACADDR=$(cat /sys/class/net/$ROUTERMAC/address) > > + # We need this to set the original MAC for the > > + ubnt-unifiac-lite > > from a variable and not from an Interface > > + if [[ -n "$NEWROUTERMAC" ]]; then > > + NEW_MACADDR=$NEWROUTERMAC > > + fi > Hm.. Nee.. Lasst uns das bitte _vorher_ umbauen, dass die MAC Adressen in > den network.xx Files gesetzt werden. > > Tim
Am Freitag, den 03.11.2017, 20:55 +0100 schrieb mail@adrianschmutzler.de: > Bevor wir den applien, brauchen wir > > https://pw.freifunk-franken.de/patch/649/ fff-hoods/fff-wireless: > Don't delete WiFi devices > > Sonst kann man das 5 GHz nicht deaktivieren. Das soll hier doch gar nicht deaktiviert werden? Ggfs benötigt es auch mehr Erklärung an dem "Don't delete WiFi devices" Patch?: --- %< --- We only want to remove WiFi interfaces, not devices during reconfiguration. This still allows for complete reconfiguration, but does not remove device attributes like a disabled 5 GHz or similar. --- >% --- Dieser Patch fügt doch weder das disabled noch ein anderes Attribut an? Tim > > Grüße > > Adrian > > > -----Original Message----- > > From: franken-dev [mailto:franken-dev-bounces@freifunk.net] On > > Behalf > > Of Tim Niemeyer > > Sent: Freitag, 3. November 2017 14:03 > > To: Christian Dresel <fff@chrisi01.de>; franken-dev@freifunk.net > > Subject: Re: [PATCH v2] Add support for Unifi AC Mesh > > > > Hi > > > > Am Montag, den 30.10.2017, 16:36 +0100 schrieb Christian Dresel: > > > This is the correct firmware for the Unifi AC Mesh I have only > > > tested > > > at Unifi AC Mesh and not at Unifi AC lite But my information is, > > > that > > > both have the same Hardware > > > > > > Signed-off-by: Christian Dresel <fff@chrisi01.de> > > > > > > --- > > > > > > v2: > > > - remove CONFIG_PACKAGE_ATH_DFS=y & CONFIG_ATH_USER_REGD=y > > > > because is > > > already in dependencies > > > active > > > - remove tab and use spaces > > > - remove ETHMESHMAC > > > - remove debug output in configurenetwork > > > > > > > [..] > > > diff --git > > > a/src/packages/fff/fff-network/files/usr/sbin/configurenetwork > > > b/src/packages/fff/fff-network/files/usr/sbin/configurenetwork > > > index c6b3113..173e270 100755 > > > --- a/src/packages/fff/fff- > > > network/files/usr/sbin/configurenetwork > > > +++ b/src/packages/fff/fff- > > > network/files/usr/sbin/configurenetwork > > > @@ -184,6 +184,10 @@ if [[ -n "$ROUTERMAC" ]]; then > > > echo "Fixing MAC on br-mesh (mesh)" > > > sleep 10 > > > NEW_MACADDR=$(cat /sys/class/net/$ROUTERMAC/address) > > > + # We need this to set the original MAC for the > > > + ubnt-unifiac-lite > > > from a variable and not from an Interface > > > + if [[ -n "$NEWROUTERMAC" ]]; then > > > + NEW_MACADDR=$NEWROUTERMAC > > > + fi > > > > Hm.. Nee.. Lasst uns das bitte _vorher_ umbauen, dass die MAC > > Adressen in > > den network.xx Files gesetzt werden. > > > > Tim > >
Hi Am 03.11.2017 um 22:59 schrieb Tim Niemeyer: > Am Freitag, den 03.11.2017, 20:55 +0100 schrieb > mail@adrianschmutzler.de: >> Bevor wir den applien, brauchen wir >> >> https://pw.freifunk-franken.de/patch/649/ fff-hoods/fff-wireless: >> Don't delete WiFi devices >> >> Sonst kann man das 5 GHz nicht deaktivieren. > Das soll hier doch gar nicht deaktiviert werden? https://wiki.freifunk-franken.de/w/Portal:Hardware/UnifiACMesh Diese Befehle würden nach den aktuellen Stand so nicht wirklich klappen, so ist das Gerät nur Indoor legal zu verwenden was irgendwie sinnlos ist. Ich denke daher kommt das Veto. Ob das Veto aus dem Grund gerechtertigt ist kann ich nicht beurteilen, man müsste höchstens dazu schreiben das es eben zum aktuellen Zeitunkt NUR indoor verwendbar ist mfg Christian > > Ggfs benötigt es auch mehr Erklärung an dem "Don't delete WiFi devices" > Patch?: > --- %< --- > We only want to remove WiFi interfaces, not devices during > reconfiguration. This still allows for complete reconfiguration, > but does not remove device attributes like a disabled 5 GHz or > similar. > --- >% --- > > Dieser Patch fügt doch weder das disabled noch ein anderes Attribut an? > > Tim > >> Grüße >> >> Adrian >> >>> -----Original Message----- >>> From: franken-dev [mailto:franken-dev-bounces@freifunk.net] On >>> Behalf >>> Of Tim Niemeyer >>> Sent: Freitag, 3. November 2017 14:03 >>> To: Christian Dresel <fff@chrisi01.de>; franken-dev@freifunk.net >>> Subject: Re: [PATCH v2] Add support for Unifi AC Mesh >>> >>> Hi >>> >>> Am Montag, den 30.10.2017, 16:36 +0100 schrieb Christian Dresel: >>>> This is the correct firmware for the Unifi AC Mesh I have only >>>> tested >>>> at Unifi AC Mesh and not at Unifi AC lite But my information is, >>>> that >>>> both have the same Hardware >>>> >>>> Signed-off-by: Christian Dresel <fff@chrisi01.de> >>>> >>>> --- >>>> >>>> v2: >>>> - remove CONFIG_PACKAGE_ATH_DFS=y & CONFIG_ATH_USER_REGD=y >>> because is >>>> already in dependencies >>>> active >>>> - remove tab and use spaces >>>> - remove ETHMESHMAC >>>> - remove debug output in configurenetwork >>>> >>> [..] >>>> diff --git >>>> a/src/packages/fff/fff-network/files/usr/sbin/configurenetwork >>>> b/src/packages/fff/fff-network/files/usr/sbin/configurenetwork >>>> index c6b3113..173e270 100755 >>>> --- a/src/packages/fff/fff- >>>> network/files/usr/sbin/configurenetwork >>>> +++ b/src/packages/fff/fff- >>>> network/files/usr/sbin/configurenetwork >>>> @@ -184,6 +184,10 @@ if [[ -n "$ROUTERMAC" ]]; then >>>> echo "Fixing MAC on br-mesh (mesh)" >>>> sleep 10 >>>> NEW_MACADDR=$(cat /sys/class/net/$ROUTERMAC/address) >>>> + # We need this to set the original MAC for the >>>> + ubnt-unifiac-lite >>>> from a variable and not from an Interface >>>> + if [[ -n "$NEWROUTERMAC" ]]; then >>>> + NEW_MACADDR=$NEWROUTERMAC >>>> + fi >>> Hm.. Nee.. Lasst uns das bitte _vorher_ umbauen, dass die MAC >>> Adressen in >>> den network.xx Files gesetzt werden. >>> >>> Tim >> >>
Hi Am 3. November 2017 23:02:57 MEZ schrieb Christian Dresel <fff@chrisi01.de>: >Hi > >Am 03.11.2017 um 22:59 schrieb Tim Niemeyer: >> Am Freitag, den 03.11.2017, 20:55 +0100 schrieb >> mail@adrianschmutzler.de: >>> Bevor wir den applien, brauchen wir >>> >>> https://pw.freifunk-franken.de/patch/649/ fff-hoods/fff-wireless: >>> Don't delete WiFi devices >>> >>> Sonst kann man das 5 GHz nicht deaktivieren. >> Das soll hier doch gar nicht deaktiviert werden? >https://wiki.freifunk-franken.de/w/Portal:Hardware/UnifiACMesh > >Diese Befehle würden nach den aktuellen Stand so nicht wirklich >klappen, >so ist das Gerät nur Indoor legal zu verwenden was irgendwie sinnlos >ist. Ich denke daher kommt das Veto. Ob das Veto aus dem Grund >gerechtertigt ist kann ich nicht beurteilen, man müsste höchstens dazu >schreiben das es eben zum aktuellen Zeitunkt NUR indoor verwendbar ist Ah achso. Tja. Dann muß den anderen Patch mal jemand reviewen. Dieser hier muss ja eh rebased werden. :) Tim > >mfg > >Christian >> >> Ggfs benötigt es auch mehr Erklärung an dem "Don't delete WiFi >devices" >> Patch?: >> --- %< --- >> We only want to remove WiFi interfaces, not devices during >> reconfiguration. This still allows for complete reconfiguration, >> but does not remove device attributes like a disabled 5 GHz or >> similar. >> --- >% --- >> >> Dieser Patch fügt doch weder das disabled noch ein anderes Attribut >an? >> >> Tim >> >>> Grüße >>> >>> Adrian >>> >>>> -----Original Message----- >>>> From: franken-dev [mailto:franken-dev-bounces@freifunk.net] On >>>> Behalf >>>> Of Tim Niemeyer >>>> Sent: Freitag, 3. November 2017 14:03 >>>> To: Christian Dresel <fff@chrisi01.de>; franken-dev@freifunk.net >>>> Subject: Re: [PATCH v2] Add support for Unifi AC Mesh >>>> >>>> Hi >>>> >>>> Am Montag, den 30.10.2017, 16:36 +0100 schrieb Christian Dresel: >>>>> This is the correct firmware for the Unifi AC Mesh I have only >>>>> tested >>>>> at Unifi AC Mesh and not at Unifi AC lite But my information is, >>>>> that >>>>> both have the same Hardware >>>>> >>>>> Signed-off-by: Christian Dresel <fff@chrisi01.de> >>>>> >>>>> --- >>>>> >>>>> v2: >>>>> - remove CONFIG_PACKAGE_ATH_DFS=y & CONFIG_ATH_USER_REGD=y >>>> because is >>>>> already in dependencies >>>>> active >>>>> - remove tab and use spaces >>>>> - remove ETHMESHMAC >>>>> - remove debug output in configurenetwork >>>>> >>>> [..] >>>>> diff --git >>>>> a/src/packages/fff/fff-network/files/usr/sbin/configurenetwork >>>>> b/src/packages/fff/fff-network/files/usr/sbin/configurenetwork >>>>> index c6b3113..173e270 100755 >>>>> --- a/src/packages/fff/fff- >>>>> network/files/usr/sbin/configurenetwork >>>>> +++ b/src/packages/fff/fff- >>>>> network/files/usr/sbin/configurenetwork >>>>> @@ -184,6 +184,10 @@ if [[ -n "$ROUTERMAC" ]]; then >>>>> echo "Fixing MAC on br-mesh (mesh)" >>>>> sleep 10 >>>>> NEW_MACADDR=$(cat /sys/class/net/$ROUTERMAC/address) >>>>> + # We need this to set the original MAC for the >>>>> + ubnt-unifiac-lite >>>>> from a variable and not from an Interface >>>>> + if [[ -n "$NEWROUTERMAC" ]]; then >>>>> + NEW_MACADDR=$NEWROUTERMAC >>>>> + fi >>>> Hm.. Nee.. Lasst uns das bitte _vorher_ umbauen, dass die MAC >>>> Adressen in >>>> den network.xx Files gesetzt werden. >>>> >>>> Tim >>> >>>
hi Am 03.11.2017 um 23:06 schrieb Tim Niemeyer: > Hi > > Am 3. November 2017 23:02:57 MEZ schrieb Christian Dresel <fff@chrisi01.de>: >> Hi >> >> Am 03.11.2017 um 22:59 schrieb Tim Niemeyer: >>> Am Freitag, den 03.11.2017, 20:55 +0100 schrieb >>> mail@adrianschmutzler.de: >>>> Bevor wir den applien, brauchen wir >>>> >>>> https://pw.freifunk-franken.de/patch/649/ fff-hoods/fff-wireless: >>>> Don't delete WiFi devices >>>> >>>> Sonst kann man das 5 GHz nicht deaktivieren. >>> Das soll hier doch gar nicht deaktiviert werden? >> https://wiki.freifunk-franken.de/w/Portal:Hardware/UnifiACMesh >> >> Diese Befehle würden nach den aktuellen Stand so nicht wirklich >> klappen, >> so ist das Gerät nur Indoor legal zu verwenden was irgendwie sinnlos >> ist. Ich denke daher kommt das Veto. Ob das Veto aus dem Grund >> gerechtertigt ist kann ich nicht beurteilen, man müsste höchstens dazu >> schreiben das es eben zum aktuellen Zeitunkt NUR indoor verwendbar ist > Ah achso. > > Tja. Dann muß den anderen Patch mal jemand reviewen. > > Dieser hier muss ja eh rebased werden. :) ihr wart so fleißig das ich jetzt wieder etwasÜberblick verloren habe ;) Ich schau es mir die Tage mal an und mach dann nen rebase. Hab es mit der Kiste jetzt nicht soooo eilig. mfg Christian > > Tim > >> mfg >> >> Christian >>> Ggfs benötigt es auch mehr Erklärung an dem "Don't delete WiFi >> devices" >>> Patch?: >>> --- %< --- >>> We only want to remove WiFi interfaces, not devices during >>> reconfiguration. This still allows for complete reconfiguration, >>> but does not remove device attributes like a disabled 5 GHz or >>> similar. >>> --- >% --- >>> >>> Dieser Patch fügt doch weder das disabled noch ein anderes Attribut >> an? >>> Tim >>> >>>> Grüße >>>> >>>> Adrian >>>> >>>>> -----Original Message----- >>>>> From: franken-dev [mailto:franken-dev-bounces@freifunk.net] On >>>>> Behalf >>>>> Of Tim Niemeyer >>>>> Sent: Freitag, 3. November 2017 14:03 >>>>> To: Christian Dresel <fff@chrisi01.de>; franken-dev@freifunk.net >>>>> Subject: Re: [PATCH v2] Add support for Unifi AC Mesh >>>>> >>>>> Hi >>>>> >>>>> Am Montag, den 30.10.2017, 16:36 +0100 schrieb Christian Dresel: >>>>>> This is the correct firmware for the Unifi AC Mesh I have only >>>>>> tested >>>>>> at Unifi AC Mesh and not at Unifi AC lite But my information is, >>>>>> that >>>>>> both have the same Hardware >>>>>> >>>>>> Signed-off-by: Christian Dresel <fff@chrisi01.de> >>>>>> >>>>>> --- >>>>>> >>>>>> v2: >>>>>> - remove CONFIG_PACKAGE_ATH_DFS=y & CONFIG_ATH_USER_REGD=y >>>>> because is >>>>>> already in dependencies >>>>>> active >>>>>> - remove tab and use spaces >>>>>> - remove ETHMESHMAC >>>>>> - remove debug output in configurenetwork >>>>>> >>>>> [..] >>>>>> diff --git >>>>>> a/src/packages/fff/fff-network/files/usr/sbin/configurenetwork >>>>>> b/src/packages/fff/fff-network/files/usr/sbin/configurenetwork >>>>>> index c6b3113..173e270 100755 >>>>>> --- a/src/packages/fff/fff- >>>>>> network/files/usr/sbin/configurenetwork >>>>>> +++ b/src/packages/fff/fff- >>>>>> network/files/usr/sbin/configurenetwork >>>>>> @@ -184,6 +184,10 @@ if [[ -n "$ROUTERMAC" ]]; then >>>>>> echo "Fixing MAC on br-mesh (mesh)" >>>>>> sleep 10 >>>>>> NEW_MACADDR=$(cat /sys/class/net/$ROUTERMAC/address) >>>>>> + # We need this to set the original MAC for the >>>>>> + ubnt-unifiac-lite >>>>>> from a variable and not from an Interface >>>>>> + if [[ -n "$NEWROUTERMAC" ]]; then >>>>>> + NEW_MACADDR=$NEWROUTERMAC >>>>>> + fi >>>>> Hm.. Nee.. Lasst uns das bitte _vorher_ umbauen, dass die MAC >>>>> Adressen in >>>>> den network.xx Files gesetzt werden. >>>>> >>>>> Tim >>>>
Ja, aber um sie legal außen zu betreiben muss man 5 GHz deaktivieren. Und im Moment ist das nicht möglich. Grüße Adrian On November 3, 2017 10:59:55 PM GMT+01:00, Tim Niemeyer <tim@tn-x.org> wrote: Am Freitag, den 03.11.2017, 20:55 +0100 schrieb mail@adrianschmutzler.de: > Bevor wir den applien, brauchen wir > > https://pw.freifunk-franken.de/patch/649/ fff-hoods/fff-wireless: > Don't delete WiFi devices > > Sonst kann man das 5 GHz nicht deaktivieren. Das soll hier doch gar nicht deaktiviert werden? Ggfs benötigt es auch mehr Erklärung an dem "Don't delete WiFi devices" Patch?: --- %< --- We only want to remove WiFi interfaces, not devices during reconfiguration. This still allows for complete reconfiguration, but does not remove device attributes like a disabled 5 GHz or similar. --- >% --- Dieser Patch fügt doch weder das disabled noch ein anderes Attribut an? Tim > > Grüße > > Adrian > > > -----Original Message----- > > From: franken-dev [mailto:franken-dev-bounces@freifunk.net] On > > Behalf > > Of Tim Niemeyer > > Sent: Freitag, 3. November 2017 14:03 > > To: Christian Dresel <fff@chrisi01.de>; franken-dev@freifunk.net > > Subject: Re: [PATCH v2] Add support for Unifi AC Mesh > > > > Hi > > > > Am Montag, den 30.10.2017, 16:36 +0100 schrieb Christian Dresel: > > > This is the correct firmware for the Unifi AC Mesh I have only > > > tested > > > at Unifi AC Mesh and not at Unifi AC lite But my information is, > > > that > > > both have the same Hardware > > > > > > Signed-off-by: Christian Dresel <fff@chrisi01.de> > > > > > > --- > > > > > > v2: > > > - remove CONFIG_PACKAGE_ATH_DFS=y & CONFIG_ATH_USER_REGD=y > > > > because is > > > already in dependencies > > > active > > > - remove tab and use spaces > > > - remove ETHMESHMAC > > > - remove debug output in configurenetwork > > > > > > > [..] > > > diff --git > > > a/src/packages/fff/fff-network/files/usr/sbin/configurenetwork > > > b/src/packages/fff/fff-network/files/usr/sbin/configurenetwork > > > index c6b3113..173e270 100755 > > > --- a/src/packages/fff/fff- > > > network/files/usr/sbin/configurenetwork > > > +++ b/src/packages/fff/fff- > > > network/files/usr/sbin/configurenetwork > > > @@ -184,6 +184,10 @@ if [[ -n "$ROUTERMAC" ]]; then > > > echo "Fixing MAC on br-mesh (mesh)" > > > sleep 10 > > > NEW_MACADDR=$(cat /sys/class/net/$ROUTERMAC/address) > > > + # We need this to set the original MAC for the > > > + ubnt-unifiac-lite > > > from a variable and not from an Interface > > > + if [[ -n "$NEWROUTERMAC" ]]; then > > > + NEW_MACADDR=$NEWROUTERMAC > > > + fi > > > > Hm.. Nee.. Lasst uns das bitte _vorher_ umbauen, dass die MAC > > Adressen in > > den network.xx Files gesetzt werden. > > > > Tim > >
Hi Am 4. November 2017 00:02:16 MEZ schrieb Adrian Schmutzler <mail@adrianschmutzler.de>: >Ja, aber um sie legal außen zu betreiben muss man 5 GHz deaktivieren. Hm.. wir sollten die Firmware einfach zulassen.. Tim >Und im Moment ist das nicht möglich. > >Grüße > >Adrian > >On November 3, 2017 10:59:55 PM GMT+01:00, Tim Niemeyer <tim@tn-x.org> >wrote: >Am Freitag, den 03.11.2017, 20:55 +0100 schrieb >mail@adrianschmutzler.de: >> Bevor wir den applien, brauchen wir >> >> https://pw.freifunk-franken.de/patch/649/ fff-hoods/fff-wireless: >> Don't delete WiFi devices >> >> Sonst kann man das 5 GHz nicht deaktivieren. >Das soll hier doch gar nicht deaktiviert werden? > >Ggfs benötigt es auch mehr Erklärung an dem "Don't delete WiFi devices" >Patch?: >--- %< --- >We only want to remove WiFi interfaces, not devices during >reconfiguration. This still allows for complete reconfiguration, >but does not remove device attributes like a disabled 5 GHz or >similar. >--- >% --- > >Dieser Patch fügt doch weder das disabled noch ein anderes Attribut an? > >Tim > >> >> Grüße >> >> Adrian >> >> > -----Original Message----- >> > From: franken-dev [mailto:franken-dev-bounces@freifunk.net] On >> > Behalf >> > Of Tim Niemeyer >> > Sent: Freitag, 3. November 2017 14:03 >> > To: Christian Dresel <fff@chrisi01.de>; franken-dev@freifunk.net >> > Subject: Re: [PATCH v2] Add support for Unifi AC Mesh >> > >> > Hi >> > >> > Am Montag, den 30.10.2017, 16:36 +0100 schrieb Christian Dresel: >> > > This is the correct firmware for the Unifi AC Mesh I have only >> > > tested >> > > at Unifi AC Mesh and not at Unifi AC lite But my information is, >> > > that >> > > both have the same Hardware >> > > >> > > Signed-off-by: Christian Dresel <fff@chrisi01.de> >> > > >> > > --- >> > > >> > > v2: >> > > - remove CONFIG_PACKAGE_ATH_DFS=y & CONFIG_ATH_USER_REGD=y >> > >> > because is >> > > already in dependencies >> > > active >> > > - remove tab and use spaces >> > > - remove ETHMESHMAC >> > > - remove debug output in configurenetwork >> > > >> > >> > [..] >> > > diff --git >> > > a/src/packages/fff/fff-network/files/usr/sbin/configurenetwork >> > > b/src/packages/fff/fff-network/files/usr/sbin/configurenetwork >> > > index c6b3113..173e270 100755 >> > > --- a/src/packages/fff/fff- >> > > network/files/usr/sbin/configurenetwork >> > > +++ b/src/packages/fff/fff- >> > > network/files/usr/sbin/configurenetwork >> > > @@ -184,6 +184,10 @@ if [[ -n "$ROUTERMAC" ]]; then >> > > echo "Fixing MAC on br-mesh (mesh)" >> > > sleep 10 >> > > NEW_MACADDR=$(cat /sys/class/net/$ROUTERMAC/address) >> > > + # We need this to set the original MAC for the >> > > + ubnt-unifiac-lite >> > > from a variable and not from an Interface >> > > + if [[ -n "$NEWROUTERMAC" ]]; then >> > > + NEW_MACADDR=$NEWROUTERMAC >> > > + fi >> > >> > Hm.. Nee.. Lasst uns das bitte _vorher_ umbauen, dass die MAC >> > Adressen in >> > den network.xx Files gesetzt werden. >> > >> > Tim >> >>
This is the correct firmware for the Unifi AC Mesh I have only tested at Unifi AC Mesh and not at Unifi AC lite But my information is, that both have the same Hardware Signed-off-by: Christian Dresel <fff@chrisi01.de> --- v2: - remove CONFIG_PACKAGE_ATH_DFS=y & CONFIG_ATH_USER_REGD=y because is already in dependencies active - remove tab and use spaces - remove ETHMESHMAC - remove debug output in configurenetwork bsp/ar71xx/.config | 2 ++ bsp/board_ar71xx.bsp | 1 + src/packages/fff/fff-boardname/Makefile | 2 +- .../files/etc/uci-defaults/50-fff-boardname | 3 +++ src/packages/fff/fff-network/Makefile | 2 +- .../fff/fff-network/ar71xx/network.ubnt-unifiac-lite | 16 ++++++++++++++++ .../fff/fff-network/files/usr/sbin/configurenetwork | 4 ++++ 7 files changed, 28 insertions(+), 2 deletions(-) create mode 100644 src/packages/fff/fff-network/ar71xx/network.ubnt-unifiac-lite