<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Ich weck das mal wieder auf:<div class=""><br class=""></div><div class="">Komischerweise lief die NanoStation mit dem Fehler noch eine Woche, dann hat sich ohne jegliches zutun das Problem von alleine gelöst. </div><div class="">Jetzt ist aber wieder da. Sven, ich kann mit der config irgendwie nicht viel anfangen, mir springt da nichts sofort ins Auge.</div><div class=""><br class=""></div><div class="">traceroute zum benachbarten Router geht:</div><div class=""><span id="diag-rc-output" class=""><pre class="">traceroute to 10.36.207.1 (10.36.207.1), 30 hops max, 38 byte packets
1 10.36.207.1 1.312 ms</pre><pre class=""><font face="Helvetica" class="">Zum Uplink-Router auch:</font></pre><pre class=""><span id="diag-rc-output" class=""><pre class="">traceroute to 10.36.203.3 (10.36.203.3), 30 hops max, 38 byte packets
1 10.36.203.102 1.255 ms
2 10.36.203.102 1.201 ms</pre><pre class=""><font face="Helvetica" class="">Zu 1.1.1.1 aber nicht:</font></pre></span></pre></span></div><div class=""><div><span id="diag-rc-output" class=""><pre class="">traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 38 byte packets
1 *
2 *
3 *
[…]
30 *</pre></span><div class="">Der direkt via WLAN verbunden Router (10.36.207.1) geht komischerweise:</div><div class=""><br class=""></div><div class=""><span id="diag-rc-output" class=""><pre class="">traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 38 byte packets
1 10.36.203.3 7.639 ms
2 192.168.178.1 3.463 ms
3 *
4 83.169.180.214 15.758 ms
5 88.134.192.5 16.112 ms
6 88.134.237.176 20.914 ms
7 88.134.237.147 16.416 ms
8 193.178.185.17 39.268 ms
9 1.1.1.1 19.233 ms</pre></span><div class="">Was nun?</div></div><div class=""><br class=""></div><div class="">Hat das vielleicht was mit der vorhin erwähnten „Grenze“ zu tun? [1]</div><div class=""><br class=""></div><div class="">Viele Grüße </div><div class=""><br class=""></div><div class="">Karl</div><div class=""><br class=""></div><div class="">[1] <a href="https://lists.berlin.freifunk.net/pipermail/berlin/2018-August/038165.html" class="">https://lists.berlin.freifunk.net/pipermail/berlin/2018-August/038165.html</a></div><div class=""><br class=""></div><blockquote type="cite" class=""><div class="">Am 03.07.2018 um 17:19 schrieb Sven Roederer <<a href="mailto:freifunk@it-solutions.geroedel.de" class="">freifunk@it-solutions.geroedel.de</a>>:</div><br class="Apple-interchange-newline"><div class=""><div class="">Karl,<br class=""><br class="">eine mir bekannte M2loco sieht wie folgt aus:<br class="">VPN03, WAN an der ethernet-buchse,<br class=""><br class="">root@Adlershof-Eigeninitiative:~# cat /proc/cpuinfo<br class="">system type : Atheros AR7241 rev 1<br class="">machine : Ubiquiti Bullet M<br class=""><br class=""><br class="">root@Adlershof-Eigeninitiative:~# cat /etc/config/network<br class=""><br class="">config interface 'loopback'<br class=""> option ifname 'lo'<br class=""> option proto 'static'<br class=""> option ipaddr '127.0.0.1'<br class=""> option netmask '255.0.0.0'<br class=""><br class="">config globals 'globals'<br class=""> option ula_prefix 'fd1e:7899:43ca::/48'<br class=""><br class="">config interface 'tunl0'<br class=""> option ifname 'tunl0'<br class=""> option proto 'none'<br class=""><br class="">config interface 'ffuplink'<br class=""> option ifname 'ffuplink'<br class=""> option proto 'none'<br class=""><br class="">config rule 'olsr_allif_ipv4'<br class=""> option lookup 'olsr'<br class=""> option priority '1000'<br class=""><br class="">config rule 'localnets_allif_ipv4'<br class=""> option lookup 'localnets'<br class=""> option priority '2000'<br class=""><br class="">config rule 'olsr_tunnel_tunl0_ipv4'<br class=""> option lookup 'olsr-tunnel'<br class=""> option priority '19999'<br class=""> option in 'tunl0'<br class=""><br class="">config rule 'olsr_default_tunl0_ipv4'<br class=""> option lookup 'olsr-default'<br class=""> option priority '20000'<br class=""> option in 'tunl0'<br class=""><br class="">config rule 'olsr_default_unreachable_tunl0_ipv4'<br class=""> option action 'unreachable'<br class=""> option priority '20001'<br class=""> option in 'tunl0'<br class=""><br class="">config interface 'wireless0'<br class=""> option netmask '255.255.255.255'<br class=""> option proto 'static'<br class=""> option ipaddr '10.230.126.250'<br class=""> option ip6assign '64'<br class=""><br class="">config interface 'dhcp'<br class=""> option proto 'static'<br class=""> option dns '85.214.20.141 213.73.91.35 194.150.168.168 2001:4ce8::53 2001:910:800::12'<br class=""> option netmask '255.255.255.0'<br class=""> option ip6assign '64'<br class=""> option ipaddr '10.230.144.1'<br class=""> option type 'bridge'<br class=""> option _orig_ifname 'eth0 wlan0-dhcp-2 wlan0-2'<br class=""> option _orig_bridge 'true'<br class=""><br class="">config rule 'olsr_tunnel_wireless0_ipv4'<br class=""> option lookup 'olsr-tunnel'<br class=""> option priority '19999'<br class=""> option in 'wireless0'<br class=""><br class="">config rule 'olsr_default_wireless0_ipv4'<br class=""> option lookup 'olsr-default'<br class=""> option priority '20000'<br class=""> option in 'wireless0'<br class=""><br class="">config rule 'olsr_default_unreachable_wireless0_ipv4'<br class=""> option action 'unreachable'<br class=""> option priority '20001'<br class=""> option in 'wireless0'<br class=""><br class="">config rule 'olsr_tunnel_dhcp_ipv4'<br class=""> option lookup 'olsr-tunnel'<br class=""> option priority '19999'<br class=""> option in 'dhcp'<br class=""><br class="">config rule 'olsr_default_dhcp_ipv4'<br class=""> option lookup 'olsr-default'<br class=""> option priority '20000'<br class=""> option in 'dhcp'<br class=""><br class="">config rule 'olsr_default_unreachable_dhcp_ipv4'<br class=""> option action 'unreachable'<br class=""> option priority '20001'<br class=""> option in 'dhcp'<br class=""><br class="">config interface 'wan'<br class=""> option proto 'dhcp'<br class=""> option ifname 'eth0'<br class=""> option peerdns '0'<br class=""><br class=""><br class=""><br class="">Am 28.06.2018 um 13:46 schrieb Karl Beecken:<br class=""><blockquote type="cite" class="">Voilà:<br class=""><br class="">root@amalienpark-physiologicum-berlin:~# cat /etc/config/network<br class=""><br class="">config interface 'loopback'<br class="">option ifname 'lo'<br class="">option proto 'static'<br class="">option ipaddr '127.0.0.1'<br class="">option netmask '255.0.0.0'<br class=""><br class="">config globals 'globals'<br class="">option ula_prefix 'fda2:b034:f0a4::/48'<br class=""><br class="">config interface 'tunl0'<br class="">option ifname 'tunl0'<br class="">option proto 'none'<br class=""><br class="">config device 'ffuplink_dev'<br class="">option type 'veth'<br class="">option name 'ffuplink'<br class="">option peer_name 'ffuplink_wan'<br class=""><br class="">config interface 'ffuplink'<br class="">option ifname 'ffuplink'<br class="">option proto 'dhcp'<br class=""><br class="">config rule 'olsr_allif_ipv4'<br class="">option lookup 'olsr'<br class="">option priority '1000'<br class=""><br class="">config rule 'localnets_allif_ipv4'<br class="">option lookup 'localnets'<br class="">option priority '2000'<br class=""><br class="">config rule 'olsr_tunnel_tunl0_ipv4'<br class="">option lookup 'olsr-tunnel'<br class="">option priority '19999'<br class="">option in 'tunl0'<br class=""><br class="">config rule 'olsr_default_tunl0_ipv4'<br class="">option lookup 'olsr-default'<br class="">option priority '20000'<br class="">option in 'tunl0'<br class=""><br class="">config rule 'olsr_default_unreachable_tunl0_ipv4'<br class="">option action 'unreachable'<br class="">option priority '20001'<br class="">option in 'tunl0'<br class=""><br class="">config interface 'wireless0'<br class="">option netmask '255.255.255.255'<br class="">option proto 'static'<br class="">option ipaddr '10.36.203.105'<br class="">option ip6assign '64'<br class=""><br class="">config interface 'dhcp'<br class="">option proto 'static'<br class="">option dns '85.214.20.141 213.73.91.35 194.150.168.168 2001:4ce8::53 2001:910:800::12'<br class="">option ifname 'eth0'<br class="">option netmask '255.255.255.192'<br class="">option ip6assign '64'<br class="">option ipaddr '10.36.207.129'<br class="">option type 'bridge'<br class=""><br class="">config rule 'olsr_tunnel_wireless0_ipv4'<br class="">option lookup 'olsr-tunnel'<br class="">option priority '19999'<br class="">option in 'wireless0'<br class=""><br class="">config rule 'olsr_default_wireless0_ipv4'<br class="">option lookup 'olsr-default'<br class="">option priority '20000'<br class="">option in 'wireless0'<br class=""><br class="">config rule 'olsr_default_unreachable_wireless0_ipv4'<br class="">option action 'unreachable'<br class="">option priority '20001'<br class="">option in 'wireless0'<br class=""><br class="">config rule 'olsr_tunnel_dhcp_ipv4'<br class="">option lookup 'olsr-tunnel'<br class="">option priority '19999'<br class="">option in 'dhcp'<br class=""><br class="">config rule 'olsr_default_dhcp_ipv4'<br class="">option lookup 'olsr-default'<br class="">option priority '20000'<br class="">option in 'dhcp'<br class=""><br class="">config rule 'olsr_default_unreachable_dhcp_ipv4'<br class="">option action 'unreachable'<br class="">option priority '20001'<br class="">option in 'dhcp'<br class=""><br class="">Ach so:<br class=""><br class=""><blockquote type="cite" class="">Ich gehe mal davon aus, dass du bezüglich der XW bzw. XM Version die richtige anhand des Etikettes auf der Rückseite ausgewählt hast. Dies gilt auch für die Version. Da gibts ja auch 1.0/1.1 und 2.0.<br class=""></blockquote><br class="">Ich hab die Version genommen, die im Webinterface der Stock-FW angezeigt wurde. <br class=""><blockquote type="cite" class="">Dann kann das schonmal als Fehlerquelle ausgeschlossen werden.<br class="">Kannst du uns mal die Datei /etc/config/network schicken? Vllt hilft ein manueller Eintrag oder du versuchst über das Webinterface die WAN Schnittstellen selbst anzulegen.<br class=""></blockquote><br class="">Hab ich schon versucht, hat nicht funktioniert:<br class=""><blockquote type="cite" class=""><br class=""><blockquote type="cite" class=""> […], wenn ich dann aber ein <br class=""> WAN-Interface konfiguriere (ich hab dabei von einem funktionierendem <br class=""> Knoten abgeschrieben) verteilt die NanoStation brav IPs, es gibt aber <br class=""> keinerlei Internetzugriff, auch nicht vom Router aus.<br class=""></blockquote></blockquote><br class=""><br class="">_______________________________________________<br class="">Berlin mailing list<br class=""><a href="mailto:Berlin@berlin.freifunk.net" class="">Berlin@berlin.freifunk.net</a><br class="">http://lists.berlin.freifunk.net/cgi-bin/mailman/listinfo/berlin<br class="">Diese Mailingliste besitzt ein �ffentlich einsehbares Archiv<br class=""><br class=""></blockquote><br class="">_______________________________________________<br class="">Berlin mailing list<br class=""><a href="mailto:Berlin@berlin.freifunk.net" class="">Berlin@berlin.freifunk.net</a><br class="">http://lists.berlin.freifunk.net/cgi-bin/mailman/listinfo/berlin<br class="">Diese Mailingliste besitzt ein ffentlich einsehbares Archiv</div></div></blockquote></div><br class=""></div></body></html>