Dev

dev@lists.ffnw.de

632 discussions

Start a nNew thread

[Fwd: [Babel-users] About shncpd, the planned replacement for ahcpd]

by Bjoern Franke

Klingt durchaus interessant :) -- xmpp bjo(a)schafweide.org

8 years, 8 months

git - Änderungen am REMOTE Repository

by picard

hallo, ich bin GIT neuling (warnung vor meiner unwissenheit) und steh vor einem problem. wie ist der workflow bei euch? ich möchte wissen wann eine änderung an datei XYZ passiert. https://git-scm.com/book/de/v1/Git-Grundlagen-%C3%84nderungen-am-Repository… aber das erklärt mir nicht meine frage. an einem linux kann man einfach per lwatch überwachung anstellen, aber git? schreibe ich mir einen cron? hmm... also woher weiss ich das sich REMOTE DATEI XYZ geändert hat? ich sehe probleme z.b bei einer datei *.kdbx (dies ist eine DB datei die von mehreren menschen bearbeitet wird) woher weiß ich das jemand anders sie geändert hat/hatte? danke im voraus -- gruß pic @ME https://wiki.nordwest.freifunk.net/picard

8 years, 8 months

Fwd: Re: Re: [B.A.T.M.A.N.] Kernel crashes when using more than one interface in bat0

by Bjoern Franke

-------- Ursprüngliche Nachricht -------- Von: Simon Wunderlich <sw(a)simonwunderlich.de> Gesendet: 20. August 2015 13:09:51 MESZ An: b.a.t.m.a.n(a)lists.open-mesh.org CC: Bjoern Franke <bjo(a)nord-west.org> Betreff: Re: Re: [B.A.T.M.A.N.] Kernel crashes when using more than one interface in bat0 Hi Bjoern, thanks a lot for reporting this issue - it looks like there are some problems in the cleanup of OGMs when fragmentation is used. For now, I've created a ticket here: https://www.open-mesh.org/issues/223 Thanks, Simon On Tuesday 18 August 2015 18:35:17 Bjoern Franke wrote: > Am Dienstag, den 18.08.2015, 10:08 +0200 schrieb Bastian Bittorf: > > * Bjoern Franke <bjo(a)nord-west.org> [18.08.2015 09:47]: > > > Unfornately we have no logs now, because after the crashes no ssh > > > -access to the servers are possible. > > > > try to set > > > > /sbin/sysctl -w kernel.panic_on_oops=1 > > /sbin/sysctl -w kernel.panic=10 > > /sbin/sysctl -w vm.panic_on_oom=2 > > > > if the devices crashed (and reboots now) you have > > the crash in the file: > > > > /sys/kernel/debug/crashlog > > Thanks for the hint, it did not work on the debian machines, but I got > the systems running with crashkernel enabled. Now we got the first > crash: > https://p.rrbone.net/paste/nnNHrIJI#oHfBMOs2 > > Regards > Bjoern -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

8 years, 8 months

Netzsetupalternativen: babel

by Bjoern Franke

Hoi, tcatm bastelt an einer Babel-Variante für Gluon: https://github.com/freifunk-gluon/gluon/tree/babel Die Idee dabei ist wohl u.a., dass die Clients die "gluon-next-node" -Anycast-IP als Defaultroute verwenden, eine Automatik soll dann auch Roaming ermöglichen. site.(conf|mk) gibts unter https://gist.github.com/tcatm/7c031738d2382bb21bed Ich werde die Tage mal ein Testsetup bauen. vg -- xmpp bjo(a)schafweide.org

8 years, 9 months

Wikiartikel: Router/Hardware

by Robin Matulinski

8 years, 9 months

[Fwd: [B.A.T.M.A.N.] Fwd: [Babel-users] Fwd: Why we switched to Babel]

by Bjoern Franke

FYI und tcatm fragte vorhin in #gluon, ob Interesse an babel in Gluon bestehe... -- xmpp bjo(a)schafweide.org

8 years, 9 months

Cangelog 0.6

by Jan-Tarek Butt

Whit a huge mug of Tschunkand an imperial inspiration from the cccCamp2015. The 0.6 firmware is now stable and ready for release. 1. Change GLUON base from v2014.4.x up to v2015.1.x. Thats included the following main changes: Changes up to v2015.1.2 Added hardware support ar71xx-generic TP-Link TL-WA830RE (v1) TP-Link TL-WA801N/ND v1 TL-WA701N/ND (v2) TL-WA801N/ND (v1) TL-WA830RE (v2) TL-WR740N / TL-WR741ND (v5) TP-Link TL-WA830RE v2: remove BROKEN New features The x86-generic and x86-kvm_guest images now support two ethernet interfaces by default. If two interfaces exist during the first boot, eth0 will be used as LAN and eth1 as WAN. * Ubiquiti Loco M, Picostation M and Rocket M now get their own images (which are just copies of the Bullet M image)so it’s more obvious for users which image to use. * The x86-generic images now contain the e1000e ethernet driver by default. Bugfixes Fix German “Expert Mode” label (was “Export Mode”). Fix download of OpenSSL during build because of broken OpenSSL download servers. Fix ABI break causing kernel panics when trying to use network-related modules from the official OpenWrt repository (like kmod-pppoe). Fix race conditions breaking parallel build occasionally. A broken network configuration would be generated when an older Gluon version was updated to 2015.1 with mesh_on_lan enabled in site.conf. Minor announced/alfred JSON format fixes (don’t output empty lists where empty objects would be expected). * Fix another ABI incompatiblity with the upstream kernel modules which prevented loading some filesystem-related modules. * Fix potential MAC address conflicts on x86 target when using mesh-on-wan/lan. * Fix signal strength indicators on TP-LINK CPE210/510. * Fix the model name string on some NETGEAR WNDR3700v2. * Fix 5GHz WLAN switching channels and losing connectivity when other WLANs using the same channel are detected (including other Gluon nodes...); see https://github.com/freifunk-gluon/gluon/issues/386. * Fix DNS resolution for mesh VPN on IPv6-only WAN; see https://github.com/freifunk-gluon/gluon/issues/397. * gluon-mesh-batman-adv-15: update batman-adv to 2015.0 with additional bugfixes (fixes various minor bugs). * gluon-mesh-batman-adv-15: fix forwarding of fragmented frames over multiple links with different MTUs. Additional changes up to v2015.1.x Enable DIRECT_IO kernel config Fixes a kernel incompatiblity with the upstream OpenWrt modules regarding filesystem drivers (and probably other modules related to block devices). x86-generic: add kmod-e1000e network driver Always use eth0 address as primary address on x86 and brcm2708 These targets don't have a WLAN adapter by default, so it doesn't make sense to default to the phy0 address. gluon-mesh-batman-adv-core: adjust rssid config to renamed WLAN interfaces This should fix the signal strength indicators on the TP-Link CPE210/510. gluon-mesh-batman-adv-core: unconditionally set the WAN MAC address This fixes MAC address conflicts on devices which use the eth0 as primary address. 2. Add the package ffnw-banner for a ffnw specific shell banner. 3. Add the package opkgconf to change the openWRT repo urls. because of working global IPv6 4. Add and update the packages libwlocate and lwtrace for wifi triangulation. This works together with the geolocator in the package ffnw-node-info. libwlocate uses openWlanMap.org for triangulation 5. Add the package ffnw-node-info. This is the full cloned gluon-node-info package with additional changes. The main change is the so called geolocator that can be used to locate the position of the router via wifi triangulation and set the geolocation. The geolocator works actually only on VPNrouters, a new libwlocation libray is in manufacturing Add the package ffnw-config-mode-geo-location and ffnw-config-mode-contact-info. ffnw-config-mode-geo-location can now configure the geolocator to set automatically triangulated positions. ffnw-config-mode-contact-info cloned by gluon-config-mode-contact-info because of package-conflicts.The geolocator works actually only on VPNrouters, a new libwlocation libray is in manufacturing In case of that gluon-node-info and gluon-config-mode-geo-location and gluon-config-mode-contact-info will be dropped. 6. Remove Netmon geolocation synchronisation code from packages/configurator. 7. Change netmon ULA address to the domain netmon.ffnw. 8. Nodewatcher: add geo-location to node.data whit best regards Jan-Tarek Butt

8 years, 9 months

[Fwd: [gluon] Proposal for online configuration of node information]

by Bjoern Franke

FYI -- xmpp bjo(a)schafweide.org

8 years, 9 months

Continuous Integration System

by Clemens John

Hi, kurze Info ausm Admin Team. Für die Entwicklung von Netmon SC haben wir mit Gitlab CI ein Continuous Integration System aufgesetzt. Dieses liegt unter: https://ci.nordwest.freifunk.net/ Es gibt auch bereits einen Runner-Server auf dem Projekte automatisiert ausgeführt werden können, dieser sollte allerdings nur für weniger rechenintensive Anwendungen genutzt werden. Falls sich damit jemand beschäftigen will um z.B. automatisiert Firmwares zu bauen, sollte ein Runner auf einem heimischen Gerät aufgesetzt werden. Dieser sollte sich Problemlos einbinden lassen. Technische Doku zu Runnern: https://wiki.nordwest.freifunk.net/Technik/Dokumentation/Gitlab#Runner_f.2B… LG Clemens

8 years, 9 months

[Fwd: [gluon] [ANNOUNCE] Gluon 2015.1.2]

by Bjoern Franke

FYI Vielleicht sollten wir für 0.6 2015.1 auslassen und gleich 2015.1.2 nehmen. -- xmpp bjo(a)schafweide.org

8 years, 9 months

← Newer
1
...
56
57
58
59
60
61
62
63
64
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Dev