[ANNOUNCE] Gluon v2016.1

lumo · 8. Februar 2016 um 11:10

Hallo zusammen, ich hatte mich mal lesen in gluon-mailingliste gehängt. Da kamm frohe Kunde, nicht nur für die bei denen die Karnevalsumzüge abgesagt wurden!

Hi,
I’m happy to announce that Gluon v2016.1 has finally landed!

As you’ve already noticed, this has taken a lot longer than planned. The
change from Barrier Breaker to Chaos Calmer had caused some unexpected
instabilities which had to be addresses before making this release.

The release notes can be found at

https://gluon.readthedocs.org/en/v2016.1/releases/v2016.1.html

SenorKaffee · 8. Februar 2016 um 11:30

Das ist eine gute Nachricht! Gleichmal durchbauen.

adorfer · 8. Februar 2016 um 13:47

5 Beiträge wurden in ein neues Thema verschoben: Schwierigkeiten beim Bauen von Gluon 2015.1

adorfer · 8. Februar 2016 um 13:46

adorfer · 8. Februar 2016 um 13:49

Gerade der Support für 1043v3, 841v10, CPE210v1.1 wird wirklich helfen.

Wer mag, der möge bitte bei einem 841(v9/v10) mit dem neuen Build „MoW“ aktivieren.

Den Node ohne gestecktes Lankabel (nur als "Wifimesh) booten.
Dann schauen, ob sich das Ding noch per IPv6 „non-Linklocal“ erreichen lässt, also ssh, status-Seite.

eriu · 8. Februar 2016 um 15:50

da viele neue Geräte unterstützt werden müssten wir dann die hardware specs der unterstützen Geräte anpassen - Freiwillige vor

Freifunk-Firmware Gluon/Hardware – wiki.freifunk.net

fragstone · 8. Februar 2016 um 19:11

Bin sehr gespannt wie das verhalten in der freien Landschaft sein wird. Es sind doch einige Bugs gerade WLAN basierend einfach auf das nächste Release verschoben worden.

github.com/freifunk-gluon/gluon

gluon-luci-wifi-config: txpowerlist is likely incomplete/wrong

opened 01:12AM - 06 Feb 16 UTC

closed 06:54PM - 23 Feb 17 UTC

Adorfer

0. type: bug

to obtain a valid "txpowerlist" from iwinfo in CC, you need to have the radio in…terface fully initialized (including regdomain and radio channel). This is currently not the case. by consequence the maximum power is for 841v9 at 19dB, and 841v10 at 18dB. In case a user selects the highest available (18dB) and saves that value, he is stuck with a txpower of 18, even if later (during full operation of the node) the txpowerlist would go up to 20 (unless you are running on ch13...)

github.com/freifunk-gluon/gluon

"MoW enabled" nodes need LAN-eth up during boot.

opened 11:34AM - 31 Jan 16 UTC

closed 01:11PM - 30 May 16 UTC

Adorfer

0. type: bug

If you enable MoW (network.mesh_wan.auto=1) this at 841v8/v9/v10 will NOT work …properly (this may apply to more ar71xx and other targets, but untested by me) consequences a) if no LAN (correct, i do not mean WAN) eth link established during boot time, the node will not be reachable by it's IPv6 (from the site.conf's prefix). -> no working bat0-ipv6 (announced, ssh, icpm-echo) b) probably (not fully tested): if LAN established during boot phasis, IPv6 is present, but ping to the IPv6 causes DUP-responses. having WAN link established during boot does not make a difference. uci show, ip a of node in status a) http://pastebin.com/bwdv58Lg

https://github.com/freifunk-gluon/gluon/issues/605

github.com/freifunk-gluon/gluon

autoupdater runs concurrently

opened 11:07PM - 05 Dec 15 UTC

closed 11:32PM - 09 Sep 16 UTC

corny

0. type: bug

On one node with ``` root@somenode:~# uptime 23:48:41 up 3 days, root@somenode:~# ps PID USER VSZ STAT COMMAND 1 root 1388 S /sbin/procd 2 root 0 SW [kthreadd] 3 root 0 SW [ksoftirqd/0] 5 root 7 root 0 SW< [khelper] 62 root 65 root 0 SW< [bioset] 67 root 0 SW< [kblockd] 100 root 0 SW [kswapd0] 147 root 178 root 292 root 0 SW< [deferwq] 363 root 446 root 892 S /sbin/ubusd 447 root 603 root 695 root 0 SW< [cfg80211] 830 root 835 root 943 root 1608 S /sbin/netifd 974 root 994 root 1003 root 1008 root 1041 root 1051 root 1125 root 1282 root 1313 root 1334 root 1340 root 1386 root 1434 root 1640 nobody 1902 root 2557 root 0 SW [kworker/0:3] 3010 root 3013 root 3023 root 0 Z [sh] 3129 root 3131 root 3144 root 3145 root 4772 root 0 Z [sh] 4826 root 4827 root 5656 root 5658 root 5662 root 5663 root 5753 root 5757 root 5759 root 5760 root 8352 root 8354 root 8358 root 8359 root 9126 root 9128 root 9132 root 0 Z [sh] 9183 root 9184 root 10611 root 10616 root 10617 root 10618 root 11439 root 11444 root 11445 root 11446 root 11462 root 11503 root 12031 root 12033 root 12038 root 0 Z [sh] 12099 root 12100 root 14067 root 14072 root 14074 root 14075 root 14929 root 16847 root 16944 root 0 SW [kworker/0:0] 17185 root 17187 root 17191 root 17192 root 17311 root 17316 root 17317 root 17318 root 17435 root 17437 root 17441 root 0 Z [sh] 17500 root 17501 root 18092 root 18094 root 18098 root 18099 root 18953 root 18960 root 18971 root 18972 root 19766 root 21013 root 0 SW [kworker/0:1] 21349 root 21350 root 21363 root 1392 S -ash 21368 root 1388 R ps 21369 root 21370 root 1036 R jshn -w 22019 root 22024 root 22025 root 0 Z [sh] 22045 root 22046 root 23324 root 23326 root 23330 root 23331 root 24215 root 24220 root 24221 root 24222 root 25814 root 0 DW [kworker/0:2] 26316 root 26908 root 26911 root 26934 root 26937 root 29222 root 29227 root 29228 root 0 Z [sh] 29300 root 29301 root 29338 root 29340 root 29344 root 29345 root 30421 root 30428 root 30437 root 30438 root 30490 root 30495 root 30496 root 0 Z [sh] 30529 root 30530 root 30612 root 30617 root 30628 root 30629 root 31101 root 31106 root 31108 root 31109 root 31630 root 31905 root 31912 root 31922 root 0 Z [sh] 31994 root 31995 root 32294 root 32299 root 32300 root 0 Z [sh] 32359 root 32360 root ``` a high load I found multiple autoupdater processes running. Cou…ld we use a lockfile to prevent this? 9:09, load average: 3.03, 2.52, 2.28 0 SW< [kworker/0:0H] 0 SW< [writeback] 0 SW [fsnotify_mark] 0 SW< [ath79-spi] 0 SWN [jffs2_gcd_mtd3] 772 S /sbin/askfirst ttyS0 /bin/ash --login 0 SW< [bat_events] 1036 S /sbin/logd -S 16 1600 S /usr/sbin/haveged -w 1024 -d 32 -i 32 -v 1 1392 S /usr/sbin/crond -f -c /etc/crontabs -l 5 1152 S /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300 788 S /usr/sbin/gluon-crond /lib/gluon/cron 1108 S /usr/sbin/gluon-radvd -i br-client -p 2001:bf7:540::/64 1132 S /usr/sbin/uhttpd -f -h /lib/gluon/status-page/www -r somenode -x /c 916 S /usr/sbin/dnsmasq -x /var/run/gluon-wan-dnsmasq.pid -u root -i lo -p 54 -h -r 3292 R /usr/bin/fastd --config - --daemon --pid-file /var/run/fastd.mesh_vpn.pid 1392 S /usr/sbin/ntpd -n -p 1.ntp.services.bremen.freifunk.net -p 2.ntp.services.brem 1112 S /usr/sbin/alfred -i br-client -b bat0 1320 S /usr/sbin/batadv-vis -i bat0 -s 812 S odhcp6c -s /lib/netifd/dhcpv6.script -t120 br-client 1388 S udhcpc -p /var/run/udhcpc-br-wan.pid -s /lib/netifd/dhcp.script -f -t 0 -i br- 812 S odhcp6c -s /lib/netifd/dhcpv6.script -P0 -t120 br-wan 924 S /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf -k 2152 S /usr/bin/respondd -g ff02::2:1001 -p 1001 -c return require("gluon.announced") 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2080 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1584 S /usr/sbin/hostapd -P /var/run/wifi-phy0.pid -B /var/run/hostapd-phy0.conf 1576 S /usr/sbin/hostapd -P /var/run/wifi-phy1.pid -B /var/run/hostapd-phy1.conf 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 0 SW [kworker/u2:2] 1220 S /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1168 S /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300 1508 S {dhcpv6.script} /bin/sh /lib/netifd/dhcpv6.script br-client ra-updated 1504 R {dhcpv6.script} /bin/sh /lib/netifd/dhcpv6.script br-client ra-updated 1508 S {dhcpv6.script} /bin/sh /lib/netifd/dhcpv6.script br-client ra-updated 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 0 SW [kworker/u2:1] 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 0 SW [kworker/u2:0] 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s 1388 S /bin/sh -c /usr/sbin/autoupdater --fallback 2072 S {autoupdater} /usr/bin/lua /usr/sbin/autoupdater --fallback 1388 S sh -c wget -T 120 -O- 'http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/s 1396 S wget -T 120 -O- http://[2a03:b0c0:3:d0::19:4001]/ffhb-mirror/firmware/stable/s

github.com/freifunk-gluon/gluon

TP-Link 841n V10 + 940nV3 + 941ndV6 have less transmitting power (dbm) than specification?

opened 11:36PM - 11 Nov 15 UTC

closed 07:44PM - 08 Sep 16 UTC

KK4

2. status: invalid 3. topic: hardware

Ih tested three TP-Link 841n V10 + 940nV3 + 941ndV6, and all have 18 dbm only as… max also, In LuCI the v9 has range "standard" , 19 dbm = 79 mW, 18 ... and so on the V10 has "standard", 18 dbm = 63 mW , 17 ... and so on (19 dbm is missing) the 940/941 have "standard", 20 dbm = 100 mw, 19 dbm ... and so on I think, "standard" should be the next step above always. However, all these give effective 18 dbm = 63 mW only, even if I set "standard" or the next max I tested this with both, the orginal firmware as well as with the last FF firmware, it is same. (the original firmware has three settings only, "high", "middle", "low". I asked TP-Link technical support Matthias Korn Technical Support Engineer and got (for the 841n V10 only, for 940/041 they could nit provide the specifications ) the answer below: "hier ist kein Fehler vorhanden sondern alles völlig normal" "Laut den Spezifikationen des TL-WR841N(UN) Version 9.0 betragen die maximal gemessenen dbm Werte 20dbm für 11b, 21dbm für 11g und 20dbm für 11n. Beim TL-WR841N(UN) Version 10.0 betragen diese Werte 19dbm für 11b, 21dbm für 11g und 21dbm für 11n. " "die Spezifikationen für ihre Hardware Versionen von TL-WR940N und TL-WR941ND habe ich nicht vorliegen. " This means, that these three have a clear worse transmitting power than the 841n V9 and than the 1043nd v2 divergent to the specifcations ? pecifications I fond says for all hese three the same: 20dbm http://www.tp-link.com/lk/products/details/cat-9_TL-WR841N.html#specifications http://www.tp-link.com/lb/products/details/cat-9_TL-WR941ND.html

Gruß
Thomas

MrMM · 8. Februar 2016 um 20:14

Da sehe ich keine dramatischen Sachen bei, bei der Sendeleistung sind wir im Ernstfall zu gering, damit können wir leben.

Der Autoupdater wurde deutlich optimiert:

github.com/freifunk-gluon/gluon

Problems after autoupdate

opened 02:13AM - 07 Dec 15 UTC

closed 05:33AM - 05 Feb 16 UTC

A-Kasper

0. type: bug 0. type: regression

I've got many reports (about 12), that nodes are dead after autoupdate (master).… I can't say in which cases this happens. different hardware is affected. All devices are working fine after a powercycle. I just had one case with my own routers. I was in hurry and needed to make the network work again, so there was no time for deeper investigations. But I can report, that I was able to connect to the router via LAN IP and SSH. It still answered, so it wasn't frozen. Seems like something doesn't always come up after autoupdate. Can someone confirm this issue?

Das Mesh on WAN den Knoten stört wenn kein Kabel im WAN Port steckt ist auch kein Grund das Release heraus zu zögern

Das WiFi Stack Problem konnte ich bei mir nicht reproduzieren.

Ich bin der Meinung es ist soweit die Firmware mit gutem Gewissen in die Beta und Experimental Branches auszurollen. Nur sofern sie sich verhält wie erwartet geht sie dann auch in den stable Branch.

adorfer · 8. Februar 2016 um 21:23

Das MoW stört auf 841&Co, wenn ein Kabel am Lan-Port steckt beim Boot.