- Dec 22, 2015
-
-
Michael Schwarz authored
As TP-Link 841v10 are not supported by gluon 2015.1.x, they need to be feed with the experimental firmware. Since the experimental firmware could break a router, we want these aliens to update only from stable versions.
-
Michael Schwarz authored
-
- Nov 03, 2015
-
-
Michael Schwarz authored
-
- Sep 09, 2015
-
-
Karsten Böddeker authored
-
- Feb 21, 2015
-
-
Stefan Laudemann authored
As '/lib/netifd/hostapd.sh' and '/lib/wifi/mac80211.sh' should never be called directly (but only be included from other files like '/lib/netifd/ wireless/mac80211.sh', these files do not need to have an execute bit set, which on the other hand would be ensured by using the $(INSTALL_BIN) macro in the make file. The $(CP) macro would simply copy the files from the package into the image and preserve their permissions. Signed-off-by:
Stefan Laudemann <thisco@webcake.de>
-
Stefan Laudemann authored
For an so far unknown reason one of the nodes in the testing stream had an additional open WLAN called 'OpenWrt' after updating from v0.5.3 to v0.6.0~rc2. It has to be mentioned, though, that this node used a heavily customized network configuration prior to the update to fullfil some very specific needs. It should however be avoided that a new network suddenly appears after applying an update in any case. As a cause for this, the mac80211.sh located in '/lib/wifi/' has been identified, which scans for unknown PHYs when executed and adds them along with such an example network to '/etc/config/wireless'. For a pure OpenWRT router this behaviour is not that much a problem, as the radio itself gets deactivated by adding an "option disabled '1'" that must be removed manually by a user. In comb- ination with Gluon this becomes critical, as the gluon-mesh-batman-adv- core package would enable the radio automatically, such that a node can connect to other Freifunk nodes over WiFi. Generally, a network 'OpenWrt' should not exist anymore in '/etc/config/wireless' by that time. The reason for which in the case mentioned above there was such an entry is still unknown. In order to exclude such a security risk, for now we provide a modified copy of '/lib/wifi/mac802111.sh' with this packages, in which the corresponding lines to add a default/example network 'OpenWrt' have been removed compeletely. This modified version of the script replaces the original script at build-time. Signed-off-by:
Stefan Laudemann <thisco@webcake.de>
-
- Feb 20, 2015
-
-
Stefan Laudemann authored
As it turned out, the old hostapd.sh from BB does not provide all the necessary functions needed by the mac80211.sh that got added in commit f2d78863. The corresponding hostapd.sh from the CC trunk [1] however has this functions and works fine in BB already. Hence, we add the netifd.sh from [1] into the package because of the fixes in mac80211.sh in CC that did not get backported to BB (yet). netifd.sh gets renamed to hostapd.sh by the Makefile for the hostapd package and copied to /lib/netifd. [1] https://dev.openwrt.org/browser/trunk/package/network/services/hostapd/files/netifd.sh?rev=44438 Signed-off-by:
Stefan Laudemann <thisco@webcake.de>
-
- Feb 12, 2015
-
-
Stefan Laudemann authored
As mentioned in [1], the hwmodes "11ng" and "11na" are no longer valid in BB and become "11g" and "11a". Enabling 802.11n modes are set via the htmode option now. Moreover, as the version of BB we rely on with Gluon v2014.4 comes with a faulty setup script for mac80211 that prevents setting of htmode in adhoc mode, we replace the default script with a newer one from [2]. Additionally, the mcast_rate value did not get applied correctly in the BB base of v2014.4, which gets fixed by this exchange as well. [1] https://dev.openwrt.org/ticket/17541 [2] https://dev.openwrt.org/browser/trunk/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh?rev=43853
-
- Feb 03, 2015
-
-
Stefan Laudemann authored
The package by now was rather aimed to target on the migration of TP-Link TL-WR1043NDv2 devices from a pseudo-stable firmware to the officially stable version 0.6.0. However, as it might become necessary to change other configuration values from AA to be compliant with their corresponding values in BB independent from the particular hardware-type, the package got renamed to reflect this use. Moreover, as there only is the need to migrate TP-Link TL-WR1043NDv2 devices once, with the new name the package can be reused for the migration to Chaos Calmer by adapting the included scripts.
-