Nordwest

nordwest@lists.ffnw.de

1 participants
1389 discussions

Kein Internetzugang über meine Freifunkrouter

by Georg

Hallo, seit einigen Tagen habe ich mit Freifunk Probleme. Meine Router verbinden sich wohl mit dem Netzwerk. Ich kann aber über meine Router fast keine Internetseite mehr aufrufen. Nur Freifunkseiten und Google. Woran kann dies liegen? Ich habe meine Router resetet und noch mal konfiguriert, aber es ändert sich nichts. Meine Router: ffnw-bakum-loherstr-router1 Status online, letzte Nachricht vor einer Minute (26.06.2017, 13:09:58) Koordinaten 52°?44,551'?N 008°?11,747'?E Kontakt freifunk(a)rosenbaum-bakum.de Hardware TP-Link TL-WR941N/ND v6 Primäre MAC f4:f2:6d:6e:82:d6 Node ID f4f26d6e82d6 Firmware 20170530 / gluon-v2016.2.5-6-g97f44c20 Site Freifunk Nordwest ffnw-bakum-loherstr-router2 Status online, letzte Nachricht vor 2 Minuten (26.06.2017, 13:15:58) Koordinaten 52°?44,554'?N 008°?11,762'?E Kontakt freifunk(a)rosenbaum-bakum.de Hardware TP-Link TL-WR841N/ND v10 Primäre MAC 60:e3:27:be:62:12 Node ID 60e327be6212 Firmware 20170530 / gluon-v2016.2.5-6-g97f44c20 Freundlichen Gruß, Georg

8 years

Re: [Nordwest] Internet

by Martin Brehme

Hallo zusammen, Stefan war so nett mir zu helfen. Danke dafür. Ich hab aber noch Fragen. Und damit Stefan das nicht alleine machen muss, stell ich die mal hier: OK, woran erkennt man das der Speedtest über den VPN von FF läuft? Ich würde es gerne verstehen. Schließlich bin ich ja auf einem Router der auch in einem lokalen ipv4 Netz hängt. Wie ist dann gesichert, das der Test von der Konsole über den FF VPN Tunnel läuft und nicht über das lokal ipv4 Netz. Und was sagst ihr zu den Geschwindigkeiten? Ist das normal für einen 16000er Anschluss, der etwa real 12000 hat: root@ffnw-muehlen-offloader01:~# iperf3 -c iperf.he.net Connecting to host iperf.he.net, port 5201 [ 4] local 2a03:2260:1001:a800:219:99ff:fe5c:5bcb port 41065 connected to 2001:470:0:238::2 port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 206 KBytes 1.69 Mbits/sec 20 57.1 KBytes [ 4] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec 31 51.9 KBytes [ 4] 2.00-3.00 sec 68.7 KBytes 563 Kbits/sec 26 36.3 KBytes [ 4] 3.00-4.00 sec 93.4 KBytes 765 Kbits/sec 12 28.5 KBytes [ 4] 4.00-5.00 sec 64.8 KBytes 531 Kbits/sec 2 19.5 KBytes [ 4] 5.00-6.00 sec 130 KBytes 1.06 Mbits/sec 0 23.3 KBytes [ 4] 6.00-7.00 sec 64.8 KBytes 531 Kbits/sec 0 23.3 KBytes [ 4] 7.00-8.00 sec 64.8 KBytes 531 Kbits/sec 1 15.6 KBytes [ 4] 8.00-9.00 sec 64.8 KBytes 531 Kbits/sec 1 14.3 KBytes [ 4] 9.00-10.00 sec 76.5 KBytes 627 Kbits/sec 1 14.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 834 KBytes 683 Kbits/sec 94 sender [ 4] 0.00-10.00 sec 702 KBytes 575 Kbits/sec receiver iperf Done. Außerdem habe ich auf dem Router immer noch diese Ausgabe: root@ffnw-muehlen-04:~# hoodselector No VPN connection found Batman gateways found gw source is wan gluon-neighbour-info -i br-wan -p 1001 -d ff02::2 -r hoodselector -t 0.5 No VPN routers over mesh on lan or wan 02:CA:FF:EE:BA:BF 1 Set hood "default" Hood set by batmanHasGateway mode, GW source is mesh on lan/wan root@ffnw-muehlen-04:~# Warum steht da No VPN Routers over mesh on Lan or wan? Der router meshed doch. Und warum steht da Set hood "default" Ich versteh das alles nicht :-( VG Martin Am 23.06.2017 um 16:56 schrieb Stefan: > Hi, > > ja, das geht alles via Tunnel... > > Am 23.06.2017 um 16:53 schrieb Martin Brehme: >> Moin, >> >> also ich hab jetzt auf dem einen Router dies hier bekommen: >> >> root@ffnw-muehlen-04:~# iperf3 -c iperf.he.net >> Connecting to host iperf.he.net, port 5201 >> [ 4] local 2a03:2260:1001:a800:62e3:27ff:feb7:f1d8 port 38471 connected >> to 2001:470:0:238::2 port 5201 >> [ ID] Interval Transfer Bandwidth Retr Cwnd >> [ 4] 0.00-1.00 sec 130 KBytes 1.06 Mbits/sec 2 32.4 KBytes >> [ 4] 1.00-2.00 sec 115 KBytes 946 Kbits/sec 0 35.0 KBytes >> [ 4] 2.00-3.00 sec 89.5 KBytes 732 Kbits/sec 2 25.9 KBytes >> [ 4] 3.00-4.00 sec 101 KBytes 829 Kbits/sec 1 22.0 KBytes >> [ 4] 4.00-5.00 sec 88.2 KBytes 722 Kbits/sec 0 23.3 KBytes >> [ 4] 5.00-6.00 sec 88.2 KBytes 722 Kbits/sec 0 23.3 KBytes >> [ 4] 6.00-7.00 sec 88.2 KBytes 722 Kbits/sec 1 19.5 KBytes >> [ 4] 7.00-8.00 sec 119 KBytes 978 Kbits/sec 1 15.6 KBytes >> [ 4] 8.00-9.00 sec 44.1 KBytes 361 Kbits/sec 3 11.7 KBytes >> [ 4] 9.00-10.00 sec 89.5 KBytes 733 Kbits/sec 2 13.0 KBytes >> - - - - - - - - - - - - - - - - - - - - - - - - - >> [ ID] Interval Transfer Bandwidth Retr >> [ 4] 0.00-10.00 sec 953 KBytes 781 Kbits/sec 12 >> sender >> [ 4] 0.00-10.00 sec 840 KBytes 688 Kbits/sec receiver >> >> >> und hier die Ausgabe auf dem offloader: >> >> root@ffnw-muehlen-offloader01:~# iperf3 -c iperf.he.net >> Connecting to host iperf.he.net, port 5201 >> [ 4] local 2a03:2260:1001:a800:219:99ff:fe5c:5bcb port 41063 connected >> to 2001:470:0:238::2 port 5201 >> [ ID] Interval Transfer Bandwidth Retr Cwnd >> [ 4] 0.00-1.00 sec 192 KBytes 1.57 Mbits/sec 0 38.9 KBytes >> [ 4] 1.00-2.00 sec 131 KBytes 1.07 Mbits/sec 1 38.9 KBytes >> [ 4] 2.00-3.00 sec 67.4 KBytes 552 Kbits/sec 4 36.3 KBytes >> [ 4] 3.00-4.00 sec 130 KBytes 1.06 Mbits/sec 5 28.5 KBytes >> [ 4] 4.00-5.00 sec 66.1 KBytes 542 Kbits/sec 0 31.1 KBytes >> [ 4] 5.00-6.00 sec 76.5 KBytes 627 Kbits/sec 2 24.6 KBytes >> [ 4] 6.00-7.00 sec 131 KBytes 1.07 Mbits/sec 0 29.8 KBytes >> [ 4] 7.00-8.00 sec 66.1 KBytes 542 Kbits/sec 0 31.1 KBytes >> [ 4] 8.00-9.00 sec 130 KBytes 1.06 Mbits/sec 0 31.1 KBytes >> [ 4] 9.00-10.00 sec 64.8 KBytes 531 Kbits/sec 0 33.7 KBytes >> - - - - - - - - - - - - - - - - - - - - - - - - - >> [ ID] Interval Transfer Bandwidth Retr >> [ 4] 0.00-10.00 sec 1.03 MBytes 864 Kbits/sec 12 sender >> [ 4] 0.00-10.00 sec 935 KBytes 766 Kbits/sec receiver >> >> >> Kann ich mir denn sicher sein, das der FF VPN Tunnel benutzt wird und >> nicht die ipv4 Strecke über die Fritzbox? >> >> Gruß >> Martin

8 years

letzte automatische Firmwareupdate

by Gert Lieske

Moin, seit dem letzten Update habe ich inButjadingen (Burhave Deichgraf) mit mehreren Routern und 2 CPE210 das diese auf der Map rot/blau blinken und klickt man den Router an kommt das Butjadingen-Deichgraf-C3 Status online, letzte Nachricht vor 12 Minuten (23.06.2017, 14:39:40) Koordinaten 53°?34,408'?N 008°?21,762'?E Kontakt ve17c(a)web.de Hardware TP-Link TL-WDR3600 v1 Primäre MAC 10:fe:ed:40:7c:c6 Node ID 10feed407cc6 Firmware 20170530 / gluon-v2016.2.5-6-g97f44c20 Site Freifunk Nordwest Teil des Netzes 6 Monate IP Adressen 2a03:2260:1001:b000:12fe:edff:fe40:7cc6 <http://[2a03:2260:1001:b000:12fe:edff:fe40:7cc6]/> fd74:fdaa:9dc4:0:12fe:edff:fe40:7cc6 <http://[fd74:fdaa:9dc4:0:12fe:edff:fe40:7cc6]/> fd74:fdaa:9dc4:b000:12fe:edff:fe40:7cc6 <http://[fd74:fdaa:9dc4:b000:12fe:edff:fe40:7cc6]/> fe80::12fe:edff:fe40:7cc6 Autom. Updates aktiviert (stable) Clients keine (10 in der lokalen Wolke) Client-Statistik wobei bei allen Routern der Gateway fehlt, bei den CPE210 fehlte zusätzlich auch die IP6-Adresse, mittlerweile fehlen jetzt zwei Router und zwei CPE210 komplett, habe den Fehler begangen einen funktionierenden Router mal zu rebooten,jetzt fehlt dem auch das Gateway und per Terminal komme ich an diese Geräte nicht mehr dran, biite um eine schnelle Lösungj da bei uns etzt die Turis einfliegen und die möchten ein funktionierendes WLAN benutzen. Gruß Gert Butjadingen

8 years

FYI: VDS für Kläger in Münster gekippt

by Simon Kurka

http://www.zeit.de/amp/digital/datenschutz/2017-06/vorratsdatenspeicherung-…

8 years

Zugang ins Internet soll bei meinen Routern tot sein.

by Martin Brehme

Hallo zusammen, ich brauche noch mal Eure Hilfe. Ich habe hier im Ort auf dem Dachboden eines Hauses (Unterkunft für Geflüchtete) einen Offloader und zwei Router (ffnw-muehlen-offloader-01, ffnw-muehlen-04 und ffnw-muehlen-05). Alle drei Geräte sind per Kabel an einer Fritzbox angeschlossen - haben also alle eine ipv4 Adresse. Der offloader macht das VPN ins FF Netz. Das ganze läuft über einen 16000er Anschluss von EWE. Das ganze hat bis vor ein paar Tagen mehr oder weniger problemlos funktioniert. Seit dem kommen verstärkt Meldungen: "Das Internet ist tot" Wenn ich mit Grafana (https://grafana.ffnw.de/dashboard/db/single-node-hopglass?var-hostname=ffnw…) nachsehe, dann sieht alles so aus wie immer. Ich komme von zu Hause auch von meinem FF Router per ssh auf die Router auf dem Dachboden. Ich habe einen 50000er Anschluss von EWE. Ich habe jetzt auf dem einen Router mal den hoodselector ausgeführt: root@ffnw-muehlen-04:~# hoodselector No VPN connection found Batman gateways found gw source is wan gluon-neighbour-info -i br-wan -p 1001 -d ff02::2 -r hoodselector -t 0.5 No VPN routers over mesh on lan or wan Interface mesh_lan enabled. Testing neighboring adhoc networks for batman advanced gw connection. The following wireless networks have been found: 42 2437 02:ca:ff:ee:ba:bf ffnw-mesh_ 42 2437 02:ca:ff:ee:ba:bf ffnw-mesh_ 43 2437 02:ca:ff:ee:ba:bf mesh.ffnw After filtering we will test the following wireless networks: 42 2437 02:ca:ff:ee:ba:bf ffnw-mesh_ 43 2437 02:ca:ff:ee:ba:bf mesh.ffnw Prepare configuration for testing wireless networks... VPN stopped. Testing MESH 02:ca:ff:ee:ba:bf... VPN started. Interface br-client restarted. Wireless restarted. Finished testing wireless networks, restored previous configuration Neighoring freifunk batman advanced mesh with BSSID 02:ca:ff:ee:ba:bf found Set hood "default" Hood set by scan mode Interface mesh_lan enabled. root@ffnw-muehlen-04:~# Was bedeutet das? Warum die default Hood? Hier noch ein logread vom offloader. Der ist ja offensichtlich in der VEC Hood. root@ffnw-muehlen-offloader01:~# logread Thu Jun 22 10:20:02 2017 daemon.info fastd[3060]: adding peer <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 10:20:02 2017 daemon.info fastd[3060]: resolving host `lk-vec01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer_lk_vec01_10002>... Thu Jun 22 10:20:02 2017 daemon.notice netifd: Bridge 'br-client' link is down Thu Jun 22 10:20:02 2017 daemon.notice netifd: Interface 'client' has link connectivity loss Thu Jun 22 10:20:02 2017 kern.info kernel: [ 170.103824] br-client: port 1(bat0) entered disabled state Thu Jun 22 10:20:02 2017 daemon.info fastd[3060]: resolved host `lk-vec01.sn.ffnw.de' successfully Thu Jun 22 10:20:02 2017 kern.info kernel: [ 170.206996] br-client: port 1(bat0) entered forwarding state Thu Jun 22 10:20:02 2017 kern.info kernel: [ 170.224031] br-client: port 1(bat0) entered forwarding state Thu Jun 22 10:20:02 2017 daemon.notice netifd: Bridge 'br-client' link is up Thu Jun 22 10:20:02 2017 daemon.notice netifd: Interface 'client' has link connectivity Thu Jun 22 10:20:02 2017 daemon.notice netifd: Interface 'client' is setting up now Thu Jun 22 10:20:02 2017 kern.info kernel: [ 170.255239] batman_adv: bat0: Adding interface: mesh-vpn Thu Jun 22 10:20:02 2017 kern.info kernel: [ 170.271275] batman_adv: bat0: The MTU of interface mesh-vpn is too small (1312) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1532 would solve the problem. Thu Jun 22 10:20:02 2017 kern.info kernel: [ 170.343991] batman_adv: bat0: Interface activated: mesh-vpn Thu Jun 22 10:20:02 2017 kern.info kernel: [ 170.384423] batman_adv: bat0: no_rebroadcast: Changing from: disabled to: enabled Thu Jun 22 10:20:02 2017 daemon.warn dnsmasq[2423]: no servers found in /tmp/resolv.conf.auto, will retry Thu Jun 22 10:20:02 2017 daemon.notice netifd: Interface 'mesh_vpn' is now up Thu Jun 22 10:20:02 2017 daemon.notice netifd: Interface 'client' is now down Thu Jun 22 10:20:02 2017 daemon.notice netifd: Interface 'client' is setting up now Thu Jun 22 10:20:04 2017 kern.info kernel: [ 172.220013] br-client: port 1(bat0) entered forwarding state Thu Jun 22 10:20:04 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[[2a01:4f8:161:5205::23]:10002]... Thu Jun 22 10:20:13 2017 daemon.notice netifd: Interface 'client' is now up Thu Jun 22 10:20:13 2017 user.notice firewall: Reloading firewall due to ifup of client (br-client) Thu Jun 22 10:20:25 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Thu Jun 22 10:20:25 2017 daemon.info fastd[3060]: resolving host `lk-vec01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer_lk_vec01_10002>... Thu Jun 22 10:20:25 2017 daemon.info fastd[3060]: resolved host `lk-vec01.sn.ffnw.de' successfully Thu Jun 22 10:20:25 2017 daemon.info fastd[3060]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Thu Jun 22 10:20:26 2017 daemon.info fastd[3060]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 10:20:26 2017 daemon.notice fastd[3060]: connection with <mesh_vpn_backbone_peer_lk_vec01_10002> established. Thu Jun 22 10:20:26 2017 daemon.info fastd[3060]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Thu Jun 22 10:20:29 2017 daemon.info dnsmasq[2423]: reading /tmp/resolv.conf.auto Thu Jun 22 10:20:29 2017 daemon.info dnsmasq[2423]: using local addresses only for domain lan Thu Jun 22 10:20:29 2017 daemon.info dnsmasq[2423]: using nameserver 2a03:b0c0:3:d0::bd6:b001#53 Thu Jun 22 10:20:29 2017 daemon.info dnsmasq[2423]: using nameserver 2001:67c:18e8:0:2::181#53 Thu Jun 22 10:20:30 2017 user.notice firewall: Reloading firewall due to ifupdate of client (br-client) Thu Jun 22 10:23:22 2017 kern.info kernel: [ 370.858520] br-client: Multicast hash table chain limit reached: bat0 Thu Jun 22 10:23:22 2017 kern.warn kernel: [ 370.877971] br-client: Cannot rehash multicast hash table, disabling snooping: bat0, 440, -22 Thu Jun 22 10:30:00 2017 user.notice root: netmon-node-client[3640]: Netmon Node Client is disabled. Thu Jun 22 10:40:00 2017 user.notice root: netmon-node-client[3988]: Netmon Node Client is disabled. Thu Jun 22 10:50:00 2017 user.notice root: netmon-node-client[4342]: Netmon Node Client is disabled. Thu Jun 22 11:00:00 2017 user.notice root: netmon-node-client[4690]: Netmon Node Client is disabled. Thu Jun 22 11:10:00 2017 user.notice root: netmon-node-client[5038]: Netmon Node Client is disabled. Thu Jun 22 11:10:51 2017 daemon.info fastd[3060]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 11:10:51 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Thu Jun 22 11:10:51 2017 daemon.info fastd[3060]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Thu Jun 22 11:10:51 2017 daemon.info fastd[3060]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 11:10:51 2017 daemon.info fastd[3060]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Thu Jun 22 11:20:00 2017 user.notice root: netmon-node-client[5393]: Netmon Node Client is disabled. Thu Jun 22 11:30:00 2017 user.notice root: netmon-node-client[5742]: Netmon Node Client is disabled. Thu Jun 22 11:40:00 2017 user.notice root: netmon-node-client[6092]: Netmon Node Client is disabled. Thu Jun 22 11:50:00 2017 user.notice root: netmon-node-client[6448]: Netmon Node Client is disabled. Thu Jun 22 12:00:00 2017 user.notice root: netmon-node-client[6801]: Netmon Node Client is disabled. Thu Jun 22 12:05:01 2017 daemon.info fastd[3060]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 12:05:01 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Thu Jun 22 12:05:02 2017 daemon.info fastd[3060]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Thu Jun 22 12:05:02 2017 daemon.info fastd[3060]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 12:05:02 2017 daemon.info fastd[3060]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Thu Jun 22 12:10:00 2017 user.notice root: netmon-node-client[7153]: Netmon Node Client is disabled. Thu Jun 22 12:20:00 2017 user.notice root: netmon-node-client[7497]: Netmon Node Client is disabled. Thu Jun 22 12:30:00 2017 user.notice root: netmon-node-client[7848]: Netmon Node Client is disabled. Thu Jun 22 12:40:00 2017 user.notice root: netmon-node-client[8202]: Netmon Node Client is disabled. Thu Jun 22 12:50:00 2017 user.notice root: netmon-node-client[8549]: Netmon Node Client is disabled. Thu Jun 22 12:59:25 2017 daemon.info fastd[3060]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 12:59:25 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Thu Jun 22 12:59:25 2017 daemon.info fastd[3060]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Thu Jun 22 12:59:25 2017 daemon.info fastd[3060]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 12:59:25 2017 daemon.info fastd[3060]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Thu Jun 22 13:00:00 2017 user.notice root: netmon-node-client[8898]: Netmon Node Client is disabled. Thu Jun 22 13:10:00 2017 user.notice root: netmon-node-client[9254]: Netmon Node Client is disabled. Thu Jun 22 13:20:00 2017 user.notice root: netmon-node-client[9617]: Netmon Node Client is disabled. Thu Jun 22 13:30:00 2017 user.notice root: netmon-node-client[9966]: Netmon Node Client is disabled. Thu Jun 22 13:40:00 2017 user.notice root: netmon-node-client[10314]: Netmon Node Client is disabled. Thu Jun 22 13:49:52 2017 daemon.info fastd[3060]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 13:49:52 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Thu Jun 22 13:49:52 2017 daemon.info fastd[3060]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Thu Jun 22 13:49:52 2017 daemon.info fastd[3060]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 13:49:52 2017 daemon.info fastd[3060]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Thu Jun 22 13:50:00 2017 user.notice root: netmon-node-client[10663]: Netmon Node Client is disabled. Thu Jun 22 14:00:01 2017 user.notice root: netmon-node-client[11008]: Netmon Node Client is disabled. Thu Jun 22 14:10:01 2017 user.notice root: netmon-node-client[11363]: Netmon Node Client is disabled. Thu Jun 22 14:20:00 2017 user.notice root: netmon-node-client[11712]: Netmon Node Client is disabled. Thu Jun 22 14:30:00 2017 user.notice root: netmon-node-client[12066]: Netmon Node Client is disabled. Thu Jun 22 14:40:01 2017 user.notice root: netmon-node-client[12417]: Netmon Node Client is disabled. Thu Jun 22 14:42:23 2017 daemon.info fastd[3060]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 14:42:23 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Thu Jun 22 14:42:23 2017 daemon.info fastd[3060]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Thu Jun 22 14:42:23 2017 daemon.info fastd[3060]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 14:42:23 2017 daemon.info fastd[3060]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Thu Jun 22 14:50:01 2017 user.notice root: netmon-node-client[12781]: Netmon Node Client is disabled. Thu Jun 22 15:00:01 2017 user.notice root: netmon-node-client[13137]: Netmon Node Client is disabled. Thu Jun 22 15:10:01 2017 user.notice root: netmon-node-client[13494]: Netmon Node Client is disabled. Thu Jun 22 15:20:01 2017 user.notice root: netmon-node-client[13851]: Netmon Node Client is disabled. Thu Jun 22 15:30:01 2017 user.notice root: netmon-node-client[14220]: Netmon Node Client is disabled. Thu Jun 22 15:32:57 2017 daemon.info fastd[3060]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 15:32:57 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Thu Jun 22 15:32:57 2017 daemon.info fastd[3060]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Thu Jun 22 15:32:57 2017 daemon.info fastd[3060]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 15:32:57 2017 daemon.info fastd[3060]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Thu Jun 22 15:40:01 2017 user.notice root: netmon-node-client[14582]: Netmon Node Client is disabled. Thu Jun 22 15:50:01 2017 user.notice root: netmon-node-client[14944]: Netmon Node Client is disabled. Thu Jun 22 16:00:01 2017 user.notice root: netmon-node-client[15306]: Netmon Node Client is disabled. Thu Jun 22 16:10:01 2017 user.notice root: netmon-node-client[15672]: Netmon Node Client is disabled. Thu Jun 22 16:20:01 2017 user.notice root: netmon-node-client[16033]: Netmon Node Client is disabled. Thu Jun 22 16:24:26 2017 daemon.info fastd[3060]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 16:24:26 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Thu Jun 22 16:24:26 2017 daemon.info fastd[3060]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Thu Jun 22 16:24:26 2017 daemon.info fastd[3060]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 16:24:26 2017 daemon.info fastd[3060]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Thu Jun 22 16:30:01 2017 user.notice root: netmon-node-client[16390]: Netmon Node Client is disabled. Thu Jun 22 16:40:01 2017 user.notice root: netmon-node-client[16750]: Netmon Node Client is disabled. Thu Jun 22 16:50:01 2017 user.notice root: netmon-node-client[17115]: Netmon Node Client is disabled. Thu Jun 22 17:00:01 2017 user.notice root: netmon-node-client[17475]: Netmon Node Client is disabled. Thu Jun 22 17:10:01 2017 user.notice root: netmon-node-client[17842]: Netmon Node Client is disabled. Thu Jun 22 17:15:39 2017 daemon.info fastd[3060]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 17:15:39 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Thu Jun 22 17:15:39 2017 daemon.info fastd[3060]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Thu Jun 22 17:15:39 2017 daemon.info fastd[3060]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 17:15:39 2017 daemon.info fastd[3060]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Thu Jun 22 17:20:01 2017 user.notice root: netmon-node-client[18202]: Netmon Node Client is disabled. Thu Jun 22 17:30:01 2017 user.notice root: netmon-node-client[18564]: Netmon Node Client is disabled. Thu Jun 22 17:40:01 2017 user.notice root: netmon-node-client[18925]: Netmon Node Client is disabled. Thu Jun 22 17:50:01 2017 user.notice root: netmon-node-client[19286]: Netmon Node Client is disabled. Thu Jun 22 18:00:01 2017 user.notice root: netmon-node-client[19649]: Netmon Node Client is disabled. Thu Jun 22 18:06:04 2017 daemon.info fastd[3060]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 18:06:04 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Thu Jun 22 18:06:04 2017 daemon.info fastd[3060]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Thu Jun 22 18:06:04 2017 daemon.info fastd[3060]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 18:06:04 2017 daemon.info fastd[3060]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Thu Jun 22 18:10:01 2017 user.notice root: netmon-node-client[20028]: Netmon Node Client is disabled. Thu Jun 22 18:20:01 2017 user.notice root: netmon-node-client[20378]: Netmon Node Client is disabled. Thu Jun 22 18:30:01 2017 user.notice root: netmon-node-client[20742]: Netmon Node Client is disabled. Thu Jun 22 18:40:01 2017 user.notice root: netmon-node-client[21104]: Netmon Node Client is disabled. Thu Jun 22 18:50:01 2017 user.notice root: netmon-node-client[21461]: Netmon Node Client is disabled. Thu Jun 22 19:00:01 2017 user.notice root: netmon-node-client[21815]: Netmon Node Client is disabled. Thu Jun 22 19:00:47 2017 daemon.info fastd[3060]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 19:00:47 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Thu Jun 22 19:00:47 2017 daemon.info fastd[3060]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Thu Jun 22 19:00:47 2017 daemon.info fastd[3060]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 19:00:47 2017 daemon.info fastd[3060]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Thu Jun 22 19:10:01 2017 user.notice root: netmon-node-client[22180]: Netmon Node Client is disabled. Thu Jun 22 19:20:01 2017 user.notice root: netmon-node-client[22550]: Netmon Node Client is disabled. Thu Jun 22 19:30:01 2017 user.notice root: netmon-node-client[22914]: Netmon Node Client is disabled. Thu Jun 22 19:40:01 2017 user.notice root: netmon-node-client[23270]: Netmon Node Client is disabled. Thu Jun 22 19:50:01 2017 user.notice root: netmon-node-client[23616]: Netmon Node Client is disabled. Thu Jun 22 19:53:22 2017 daemon.info fastd[3060]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 19:53:22 2017 daemon.info fastd[3060]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Thu Jun 22 19:53:22 2017 daemon.info fastd[3060]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Thu Jun 22 19:53:22 2017 daemon.info fastd[3060]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Thu Jun 22 19:53:22 2017 daemon.info fastd[3060]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Thu Jun 22 19:57:14 2017 authpriv.info dropbear[23884]: Child connection from fd74:fdaa:9dc4:0:c66e:1fff:fe41:6727:41363 Thu Jun 22 19:57:20 2017 authpriv.notice dropbear[23884]: Password auth succeeded for 'root' from fd74:fdaa:9dc4:0:c66e:1fff:fe41:6727:41363 Thu Jun 22 19:59:45 2017 authpriv.info dropbear[23884]: Exit (root): Exited normally Thu Jun 22 20:00:01 2017 user.notice root: netmon-node-client[23996]: Netmon Node Client is disabled. Thu Jun 22 20:05:16 2017 authpriv.info dropbear[24205]: Child connection from fd74:fdaa:9dc4:0:c66e:1fff:fe41:6727:41368 Thu Jun 22 20:05:22 2017 authpriv.notice dropbear[24205]: Password auth succeeded for 'root' from fd74:fdaa:9dc4:0:c66e:1fff:fe41:6727:41368 root@ffnw-muehlen-offloader01:~# Wie kann ich von einem Router auf der Konsole am besten testen, wie gut die Verbindung ins Internet ist? Kann ich sicher sein, das ich von der Konsole per wget nicht über das lokale ipv4 Netz rausgehe, sondern über das FF VPN. Martin

8 years

Neuer Beitrag: Wir machen Sommerpause

by WordPress

Auf unserem Freifunk Nordwest Blog wurde ein neuer Artikel veröffentlicht: Wir machen Sommerpause Hier lesen: https://ffnw.de/wir-machen-sommerpause/ ############# In diesem Jahr gibt es bei uns ein kleines Novum: wir machen von Anfang Juli bis Ende August Sommerpause. Damit wollen wir unseren engagierten Mitstreitern danken und euch die Möglichkeit geben sich ausgiebig zu erholen und Kraft für die zweite Jahreshälfte zu sammeln. Unsere regelmäßigen Treffen finden im Juli und im August daher nicht statt… ############# Viele Grüße Freifunk Nordwest --- P.S. Dies ist einen automatisch erstellte Benachrichtigung, die bei der Veröffentlichung des Artikels automatisch versendet wurde.

8 years

Sommerpause

by Stefan

Liebe Freifunker, wer viel im Jahr macht, darf sich auch mal eine Auszeit können - wir haben in den vergangenen Monaten soviele tolle Sachen mit euch erlebt und können auf das vergangene halbe Jahr stolz zurückblicken. Wir haben uns im letzten Jahr auf einzelnen Treffen gewundert, warum kaum Personen anwesend waren. Grund dafür sind zum einen in den Hochschulen und Universitäten Klausuren sowie der Sommerurlaub. Wir möchten in diesem Jahr die beidenen kommenden Treffen, am 07.07.2017 sowie am 04.08.2017 ausfallen lassen - unsere Entscheidung beruht sich darauf, dass teilweise Gäste anwesend waren, bevor überhaupt jemand von uns da war. Natürlich würden wir außerhalb der "offiziellen" Treffen kleine Bastelrunden oder Admintreffen planen. Lasst es euch gut gehen! Viele Grüße, der Vorstand

8 years

Probleme mit Update

by Martin Brehme

Hallo, ich möchte den offloader ffnw-muehlen-offloader01 updaten und bekomme die folgende Fehlermeldung beim manuellen Update: root@ffnw-muehlen-offloader01:~# autoupdater -f Connecting to autoupdate.ffnw ([2a01:4f8:192:832b:8::1]:80) - 100% |*********************************************************************************************************************************************| 55087 0:00:00 ETA New version available. Stopping cron... Stopping haveged... Stopping micrond... Stopping sysntpd... Stopping gluon-radvd... Stopping uhttpd... Stopping sse-multiplexd... Stopping gluon-respondd... vm.drop_caches = 3 Connecting to autoupdate.ffnw ([2a03:4000:6:8025::1]:80) lua_Tg19t9 6% |******** | 358k 0:08:46 ETA Invalid image checksum! Starting gluon-respondd... Starting sse-multiplexd... Starting uhttpd... Starting gluon-radvd... Starting cron... Starting haveged... Starting micrond... Starting sysntpd... No usable mirror found. Das Update hat heute von den beiden Routern ffnw-muehlen-04 und ffnw-muehlen-05 problemlos geklappt. Der offloader klappt nicht. Hier noch das logread: root@ffnw-muehlen-offloader01:~# logread Wed Jun 21 18:24:57 2017 kern.info kernel: [ 9.296647] usbcore: registered new interface driver r8152 Wed Jun 21 18:24:57 2017 kern.info kernel: [ 9.314020] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded Wed Jun 21 18:24:57 2017 kern.debug kernel: [ 9.331058] r8169 0000:08:00.0: irq 26 for MSI/MSI-X Wed Jun 21 18:24:57 2017 kern.info kernel: [ 9.331506] r8169 0000:08:00.0 eth0: RTL8168c/8111c at 0xf8bea000, 00:19:99:5c:5b:cb, XID 1c2000c0 IRQ 26 Wed Jun 21 18:24:57 2017 kern.info kernel: [ 9.360180] r8169 0000:08:00.0 eth0: jumbo features [frames: 6128 bytes, tx checksumming: ko] Wed Jun 21 18:24:57 2017 kern.info kernel: [ 9.386250] usbcore: registered new interface driver rtl8150 Wed Jun 21 18:24:57 2017 kern.info kernel: [ 9.407637] sis900.c: v1.08.10 Apr. 2 2006 Wed Jun 21 18:24:57 2017 kern.info kernel: [ 9.420765] usbcore: registered new interface driver usbhid Wed Jun 21 18:24:57 2017 kern.info kernel: [ 9.437481] usbhid: USB HID core driver Wed Jun 21 18:24:57 2017 kern.info kernel: [ 9.464183] via_rhine: v1.10-LK1.5.1 2010-10-09 Written by Donald Becker Wed Jun 21 18:24:57 2017 kern.info kernel: [ 9.488788] xt_time: kernel timezone is -0000 Wed Jun 21 18:24:57 2017 kern.info kernel: [ 9.503779] usbcore: registered new interface driver asix Wed Jun 21 18:24:57 2017 kern.info kernel: [ 9.520914] usbcore: registered new interface driver dm9601 Wed Jun 21 18:24:57 2017 daemon.notice haveged: haveged starting up Wed Jun 21 18:24:57 2017 daemon.info haveged: haveged: ver: 1.9.1; arch: x86; vend: ; build: (gcc 4.8.3 IV); collect: 128K Wed Jun 21 18:24:57 2017 daemon.info haveged: haveged: cpu: (); data: 32K (P); inst: 32K (P); idx: 19/40; sz: 32237/65877 Wed Jun 21 18:24:57 2017 daemon.info haveged: haveged: fills: 0, generated: 0 Wed Jun 21 18:24:58 2017 cron.info crond[1527]: crond (busybox 1.23.2) started, log level 5 Wed Jun 21 18:24:58 2017 authpriv.info dropbear[1548]: Not backgrounding Wed Jun 21 18:24:58 2017 daemon.warn netifd: You have delegated IPv6-prefixes but haven't assigned them to any interface. Did you forget to set option ip6assign on your lan-interfaces? Wed Jun 21 18:24:58 2017 kern.info kernel: [ 11.861745] r8169 0000:08:00.0 eth0: link down Wed Jun 21 18:24:58 2017 kern.info kernel: [ 11.875242] r8169 0000:08:00.0 eth0: link down Wed Jun 21 18:24:58 2017 kern.info kernel: [ 11.889626] device eth0 entered promiscuous mode Wed Jun 21 18:24:58 2017 kern.info kernel: [ 11.907445] IPv6: ADDRCONF(NETDEV_UP): br-wan: link is not ready Wed Jun 21 18:24:58 2017 daemon.notice netifd: Interface 'wan6' is enabled Wed Jun 21 18:24:58 2017 daemon.notice netifd: Interface 'wan' is enabled Wed Jun 21 18:24:58 2017 daemon.notice netifd: Interface 'mesh_wan' is enabled Wed Jun 21 18:24:58 2017 daemon.notice netifd: Interface 'loopback' is enabled Wed Jun 21 18:24:58 2017 daemon.notice netifd: Interface 'loopback' is setting up now Wed Jun 21 18:24:58 2017 daemon.notice netifd: Interface 'loopback' is now up Wed Jun 21 18:24:58 2017 daemon.notice netifd: Network device 'lo' link is up Wed Jun 21 18:24:58 2017 daemon.notice netifd: Interface 'loopback' has link connectivity Wed Jun 21 18:24:59 2017 daemon.info dnsmasq[1774]: started, version 2.73 cachesize 150 Wed Jun 21 18:24:59 2017 daemon.info dnsmasq[1774]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify Wed Jun 21 18:24:59 2017 daemon.info dnsmasq[1774]: DNS service limited to local subnets Wed Jun 21 18:24:59 2017 daemon.info dnsmasq[1774]: using local addresses only for domain lan Wed Jun 21 18:24:59 2017 daemon.warn dnsmasq[1774]: no servers found in /tmp/resolv.conf.auto, will retry Wed Jun 21 18:24:59 2017 daemon.info dnsmasq[1774]: read /etc/hosts - 1 addresses Wed Jun 21 18:24:59 2017 daemon.info dnsmasq[1780]: started, version 2.73 cachesize 150 Wed Jun 21 18:24:59 2017 daemon.info dnsmasq[1780]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify Wed Jun 21 18:24:59 2017 daemon.warn dnsmasq[1780]: no servers found in /var/gluon/wan-dnsmasq/resolv.conf, will retry Wed Jun 21 18:24:59 2017 daemon.info dnsmasq[1780]: cleared cache Wed Jun 21 18:24:59 2017 daemon.notice fastd[1836]: fastd v18 starting Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'mesh_vpn' is enabled Wed Jun 21 18:24:59 2017 daemon.notice netifd: Network device 'mesh-vpn' link is up Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'mesh_vpn' has link connectivity Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'mesh_vpn' is setting up now Wed Jun 21 18:24:59 2017 daemon.notice fastd[1836]: changed to UID 0, GID 800 Wed Jun 21 18:24:59 2017 daemon.info fastd[1836]: adding peer <mesh_vpn_backbone_peer_lk_vec01_10002> Wed Jun 21 18:24:59 2017 daemon.info fastd[1836]: resolving host `lk-vec01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer_lk_vec01_10002>... Wed Jun 21 18:24:59 2017 daemon.info fastd[1836]: resolving host `lk-vec01.sn.ffnw.de' failed: Name or service not known Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.576828] batman_adv: bat0: Adding interface: primary0 Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.592781] batman_adv: bat0: Interface activated: primary0 Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.610125] 8021q: adding VLAN 0 to HW filter on device bat0 Wed Jun 21 18:24:59 2017 daemon.info procd: - init complete - Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'bat0' is enabled Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.665976] device bat0 entered promiscuous mode Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.699107] batman_adv: bat0: Adding interface: mesh-vpn Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.715056] batman_adv: bat0: The MTU of interface mesh-vpn is too small (1312) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1532 would solve the problem. Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.787646] batman_adv: bat0: Interface activated: mesh-vpn Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.811705] br-client: port 1(bat0) entered forwarding state Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.828703] br-client: port 1(bat0) entered forwarding state Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.848375] batman_adv: bat0: Changing gw mode from: off to: client Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.873525] batman_adv: bat0: gw_sel_class: Changing from: 20 to: 1 Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.899996] batman_adv: bat0: no_rebroadcast: Changing from: disabled to: enabled Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'client' is enabled Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'local_node' is enabled Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'local_node' is setting up now Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'local_node' is now up Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.924344] device br-client entered promiscuous mode Wed Jun 21 18:24:59 2017 kern.info kernel: [ 12.946484] batman_adv: bat0: hop_penalty: Changing from: 30 to: 15 Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'mesh_vpn' is now up Wed Jun 21 18:24:59 2017 daemon.notice netifd: Network device 'bat0' link is up Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'bat0' has link connectivity Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'bat0' is setting up now Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'bat0' is now up Wed Jun 21 18:24:59 2017 daemon.notice netifd: Bridge 'br-client' link is up Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'client' has link connectivity Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'client' is setting up now Wed Jun 21 18:24:59 2017 daemon.notice netifd: MAC VLAN 'local-node' link is up Wed Jun 21 18:24:59 2017 daemon.notice netifd: Interface 'local_node' has link connectivity Wed Jun 21 18:25:00 2017 kern.info kernel: [ 13.008428] batman_adv: bat0: multicast_mode: Changing from: enabled to: disabled Wed Jun 21 18:25:00 2017 user.notice firewall: Reloading firewall due to ifup of local_node (local-node) Wed Jun 21 18:25:00 2017 kern.info kernel: [ 13.140314] batman_adv: bat0: orig_interval: Changing from: 1000 to: 5000 Wed Jun 21 18:25:00 2017 user.notice sysctl: net.ipv6.conf.br-client.forwarding = 0 Wed Jun 21 18:25:00 2017 kern.info kernel: [ 13.740788] r8169 0000:08:00.0 eth0: link up Wed Jun 21 18:25:00 2017 kern.info kernel: [ 13.754368] br-wan: port 1(eth0) entered forwarding state Wed Jun 21 18:25:00 2017 kern.info kernel: [ 13.770568] br-wan: port 1(eth0) entered forwarding state Wed Jun 21 18:25:00 2017 daemon.notice netifd: Network device 'eth0' link is up Wed Jun 21 18:25:00 2017 daemon.notice netifd: Bridge 'br-wan' link is up Wed Jun 21 18:25:00 2017 daemon.notice netifd: Interface 'wan6' has link connectivity Wed Jun 21 18:25:00 2017 daemon.notice netifd: Interface 'wan6' is setting up now Wed Jun 21 18:25:00 2017 daemon.notice netifd: Interface 'wan' has link connectivity Wed Jun 21 18:25:00 2017 daemon.notice netifd: Interface 'wan' is setting up now Wed Jun 21 18:25:00 2017 daemon.notice netifd: Interface 'mesh_wan' has link connectivity Wed Jun 21 18:25:00 2017 daemon.notice netifd: Interface 'mesh_wan' is setting up now Wed Jun 21 18:25:00 2017 kern.info kernel: [ 13.788028] IPv6: ADDRCONF(NETDEV_CHANGE): br-wan: link becomes ready Wed Jun 21 18:25:00 2017 daemon.notice netifd: wan (2189): udhcpc (v1.23.2) started Wed Jun 21 18:25:01 2017 kern.info kernel: [ 13.899739] batman_adv: bat0: Adding interface: br-wan Wed Jun 21 18:25:01 2017 kern.info kernel: [ 13.915174] batman_adv: bat0: The MTU of interface br-wan is too small (1500) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1532 would solve the problem. Wed Jun 21 18:25:01 2017 kern.info kernel: [ 13.987324] batman_adv: bat0: Interface activated: br-wan Wed Jun 21 18:25:01 2017 daemon.notice netifd: wan (2189): Sending discover... Wed Jun 21 18:25:01 2017 daemon.notice netifd: Interface 'mesh_wan' is now up Wed Jun 21 18:25:01 2017 kern.info kernel: [ 14.820015] br-client: port 1(bat0) entered forwarding state Wed Jun 21 18:25:01 2017 kern.notice kernel: [ 14.944429] random: nonblocking pool is initialized Wed Jun 21 18:25:02 2017 kern.info kernel: [ 15.770013] br-wan: port 1(eth0) entered forwarding state Wed Jun 21 18:25:04 2017 daemon.notice netifd: wan (2189): Sending discover... Wed Jun 21 18:25:04 2017 daemon.notice netifd: wan (2189): Sending select for 192.168.178.49... Wed Jun 21 18:25:04 2017 daemon.notice netifd: wan (2189): Lease of 192.168.178.49 obtained, lease time 864000 Wed Jun 21 18:25:04 2017 daemon.notice netifd: Interface 'wan' is now up Wed Jun 21 18:25:04 2017 user.notice firewall: Reloading firewall due to ifup of wan (br-wan) Wed Jun 21 18:25:04 2017 daemon.info dnsmasq[1774]: exiting on receipt of SIGTERM Wed Jun 21 18:25:04 2017 daemon.info dnsmasq[2336]: started, version 2.73 cachesize 150 Wed Jun 21 18:25:04 2017 daemon.info dnsmasq[2336]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify Wed Jun 21 18:25:04 2017 daemon.info dnsmasq[2336]: DNS service limited to local subnets Wed Jun 21 18:25:04 2017 daemon.info dnsmasq[2336]: using local addresses only for domain lan Wed Jun 21 18:25:04 2017 daemon.warn dnsmasq[2336]: no servers found in /tmp/resolv.conf.auto, will retry Wed Jun 21 18:25:04 2017 daemon.info dnsmasq[2336]: read /etc/hosts - 1 addresses Wed Jun 21 18:25:04 2017 daemon.info dnsmasq[2336]: read /tmp/hosts/dhcp - 0 addresses Wed Jun 21 18:25:04 2017 daemon.info dnsmasq[1780]: reading /var/gluon/wan-dnsmasq/resolv.conf Wed Jun 21 18:25:04 2017 daemon.info dnsmasq[1780]: using nameserver 192.168.178.1#53 Wed Jun 21 18:25:11 2017 daemon.notice netifd: Interface 'client' is now up Wed Jun 21 18:25:11 2017 user.notice firewall: Reloading firewall due to ifup of client (br-client) Wed Jun 21 18:25:23 2017 daemon.info fastd[1836]: resolving host `lk-vec01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer_lk_vec01_10002>... Wed Jun 21 18:25:23 2017 daemon.info fastd[1836]: resolved host `lk-vec01.sn.ffnw.de' successfully Wed Jun 21 18:25:41 2017 daemon.info fastd[1836]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[[2a01:4f8:161:5205::23]:10002]... Wed Jun 21 18:26:01 2017 daemon.info fastd[1836]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Wed Jun 21 18:26:01 2017 daemon.info fastd[1836]: resolving host `lk-vec01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer_lk_vec01_10002>... Wed Jun 21 18:26:01 2017 daemon.info fastd[1836]: resolved host `lk-vec01.sn.ffnw.de' successfully Wed Jun 21 18:26:01 2017 daemon.info fastd[1836]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Wed Jun 21 18:26:01 2017 daemon.info fastd[1836]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Wed Jun 21 18:26:01 2017 daemon.notice fastd[1836]: connection with <mesh_vpn_backbone_peer_lk_vec01_10002> established. Wed Jun 21 18:26:01 2017 daemon.info fastd[1836]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Wed Jun 21 18:26:04 2017 daemon.info dnsmasq[2336]: reading /tmp/resolv.conf.auto Wed Jun 21 18:26:04 2017 daemon.info dnsmasq[2336]: using local addresses only for domain lan Wed Jun 21 18:26:04 2017 daemon.info dnsmasq[2336]: using nameserver 2a03:b0c0:3:d0::bd6:b001#53 Wed Jun 21 18:26:04 2017 daemon.info dnsmasq[2336]: using nameserver 2001:67c:18e8:0:2::181#53 Wed Jun 21 18:26:04 2017 user.notice firewall: Reloading firewall due to ifupdate of client (br-client) Wed Jun 21 18:26:18 2017 kern.info kernel: [ 91.905941] br-client: Multicast hash table chain limit reached: bat0 Wed Jun 21 18:29:43 2017 kern.info kernel: [ 296.760280] br-client: Multicast hash table chain limit reached: bat0 Wed Jun 21 18:29:43 2017 kern.warn kernel: [ 296.779729] br-client: Cannot rehash multicast hash table, disabling snooping: bat0, 432, -22 Wed Jun 21 18:30:55 2017 authpriv.info dropbear[2631]: Child connection from fd74:fdaa:9dc4:0:c66e:1fff:fe41:6727:41328 Wed Jun 21 18:31:02 2017 authpriv.notice dropbear[2631]: Password auth succeeded for 'root' from fd74:fdaa:9dc4:0:c66e:1fff:fe41:6727:41328 Wed Jun 21 18:31:21 2017 authpriv.info dropbear[2631]: Exit (root): Exited normally Wed Jun 21 19:18:49 2017 daemon.info fastd[1836]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Wed Jun 21 19:18:49 2017 daemon.info fastd[1836]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Wed Jun 21 19:18:49 2017 daemon.info fastd[1836]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Wed Jun 21 19:18:49 2017 daemon.info fastd[1836]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Wed Jun 21 19:18:49 2017 daemon.info fastd[1836]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Wed Jun 21 20:12:47 2017 daemon.info fastd[1836]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Wed Jun 21 20:12:47 2017 daemon.info fastd[1836]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Wed Jun 21 20:12:47 2017 daemon.info fastd[1836]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Wed Jun 21 20:12:47 2017 daemon.info fastd[1836]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Wed Jun 21 20:12:47 2017 daemon.info fastd[1836]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Wed Jun 21 21:06:42 2017 daemon.info fastd[1836]: refreshing session with <mesh_vpn_backbone_peer_lk_vec01_10002> Wed Jun 21 21:06:42 2017 daemon.info fastd[1836]: sending handshake to <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002]... Wed Jun 21 21:06:42 2017 daemon.info fastd[1836]: received handshake response from <mesh_vpn_backbone_peer_lk_vec01_10002>[5.9.56.23:10002] using fastd v18 Wed Jun 21 21:06:42 2017 daemon.info fastd[1836]: 5.9.56.23:10002 authorized as <mesh_vpn_backbone_peer_lk_vec01_10002> Wed Jun 21 21:06:42 2017 daemon.info fastd[1836]: new session with <mesh_vpn_backbone_peer_lk_vec01_10002> established using method `salsa2012+umac'. Wed Jun 21 21:32:44 2017 authpriv.info dropbear[8167]: Child connection from fd74:fdaa:9dc4:0:c66e:1fff:fe41:6727:41335 Wed Jun 21 21:32:55 2017 authpriv.notice dropbear[8167]: Password auth succeeded for 'root' from fd74:fdaa:9dc4:0:c66e:1fff:fe41:6727:41335 Wed Jun 21 21:34:49 2017 daemon.info haveged: haveged: Stopping due to signal 15 Wed Jun 21 21:34:49 2017 kern.info kernel: [11402.096197] sysctl (8282): drop_caches: 3 Wed Jun 21 21:35:57 2017 cron.info crond[8373]: crond (busybox 1.23.2) started, log level 5 Wed Jun 21 21:35:57 2017 daemon.notice haveged: haveged starting up Wed Jun 21 21:35:57 2017 daemon.info haveged: haveged: ver: 1.9.1; arch: x86; vend: ; build: (gcc 4.8.3 IV); collect: 128K Wed Jun 21 21:35:57 2017 daemon.info haveged: haveged: cpu: (); data: 32K (P); inst: 32K (P); idx: 19/40; sz: 32237/65877 Wed Jun 21 21:35:57 2017 daemon.info haveged: haveged: fills: 0, generated: 0 Wed Jun 21 21:36:35 2017 daemon.info haveged: haveged: Stopping due to signal 15 Wed Jun 21 21:36:35 2017 kern.info kernel: [11508.084664] sysctl (8484): drop_caches: 3 Wed Jun 21 21:37:19 2017 cron.info crond[8569]: crond (busybox 1.23.2) started, log level 5 Wed Jun 21 21:37:19 2017 daemon.notice haveged: haveged starting up Wed Jun 21 21:37:19 2017 daemon.info haveged: haveged: ver: 1.9.1; arch: x86; vend: ; build: (gcc 4.8.3 IV); collect: 128K Wed Jun 21 21:37:19 2017 daemon.info haveged: haveged: cpu: (); data: 32K (P); inst: 32K (P); idx: 19/40; sz: 32237/65877 Wed Jun 21 21:37:19 2017 daemon.info haveged: haveged: fills: 0, generated: 0 VG Martin

8 years

Merkwürdiges Meshnetz beim Router

by Martin Brehme

Auf meinem Router ffnw-muehlen-01 habe ich ein Meshnetz ffnw-mesh_02:00:0a:12:a8:00 Was bedeutet das? Martin

8 years

Test an Mailingliste

by Martin Brehme

Hallo, Meine Mails an die Liste gehen nicht raus. Wer kann das lesen? Martin

8 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Nordwest