nodogsplash2: fix startup failure
The underlying network_get_device() used for option network is not reliable. Use option gatewayinterface for now.
Signed-off-by: Rob White <rob@blue-wave.net>
nodogsplash2: change configuration defaults
Changes:
* set default to NoDogsplash enabled as rest of config should now be safe and is possible to SSH to router to stop NDS if needed
* change clientidletimeout to 120 minutes (2 hours)
* add clientforcetimeout set to 1440 minutes (24 hours)
* comment out the two provided example authenticated_users block lines
* add list authenticated_users 'allow all'
* comment original list authenticated_users allow... entries and leave them as examples
* set preauth default to no use remote DNS. All devices used at a public wifi venues should be configured for DHCP. To force the use of the local DNS server makes DNS tunnelling very inefficient if not unusable on a typical OpenWrt device.
* set fw_mark settings for compatibility with other OpenWrt packages
Enhancements and bug fixes including:
- Developed and Tested against Bird-1.6.3
- New LUCI scripts (Logs, Functions and Filters)
- Enhanced UX and less use of Terminal for daily management
- Improved UX by adding extra information for the administrator
- Refactor DOCN and include missing parts.
- Code cleaning and refactoring
- New DOCN-specific [Repository](https://github.com/eloicaso/bgp-bmx6-bird-docn)
The build id contains the build timestamp by default.
Make this field optional.
Build timestamp prevents reproducible builds [0].
Thanks to the debian project for the patch.
[0] https://reproducible-builds.org/docs/timestamps/
Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
This patch bumps olsr version from 0.9.6.1 to 0.9.6.2
One major bugfix comes with the newer version, which is quite relevant
for our Freifunk mesh network: the feature LinkQualityMult was not
working in 0.9.6.1 and got fixed in the new version.
Tested on 92 productive mesh nodes running current LEDE trunk .
Signed-off-by: Thomas Huehn <thomas@net.t-labs.tu-berlin.de>
batman-adv must make sure that ether_setup is already declared via
linux/netdevice.h before the preprocessor can patch the use of it in
batman-adv. Otherwise it is tried to also patch the declaration of
ether_setup.
Fixes: 8da2f5cbb1 ("batman-adv: upgrade package to latest release 2017.2")
Signed-off-by: Sven Eckelmann <sven@narfation.org>
This patch fixes an issue in the translation table code potentially
leading to a TT Request + Response storm. The issue may occur for nodes
involving BLA and an inconsistent configuration of the batman-adv AP
isolation feature. However, since the new multicast optimizations, a
single, malformed packet may lead to a mesh-wide, persistent
Denial-of-Service, too.
The issue occurs because nodes are currently OR-ing the TT sync flags of
all originators announcing a specific MAC address via the
translation table. When an intermediate node now receives a TT Request
and wants to answer this on behave of the destination node then this
intermediate node now responds with an altered flag field and broken
CRC. The next OGM of the real destination will lead to a CRC mismatch
and triggering a TT Request and Response again.
Furthermore, the OR-ing is currently never undone as long as at least
one originator announcing the according MAC address remains, leading to
the potential persistency of this issue.
This patch fixes this issue by storing the flags used in the CRC
calculation on a a per TT orig entry basis to be able to respond with
the correct, original flags in an intermediate TT Response for one
thing. And to be able to correctly unset sync flags once all nodes
announcing a sync flag vanish for another.
Signed-off-by: Sven Eckelmann <sven@narfation.org>
This package is a transitional package for nodogsplash, so that the old version is still available for those who miss features that have not yet been implemented.
Signed-off-by: Moritz Warning <moritzwarning@web.de>
The upstream project also reverted IGDv2-by-default due to widespread
compatibility problems.
So far all Microsoft operating systems up to Windows 10, Xbox 360, Xbox One
Playstation 3 and Playstation 4 consoles seem to be incompatible to the
new 2.0 standard.
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
Moritz Warning