Das sieht doch schon besser aus.
Wo steht der router laut Koordinaten denn genau?

Am 5. Juni 2016 21:08:14 MESZ, schrieb Viktor Grosch via Nordwest <nordwest@lists.ffnw.de>:
Hier sind erstmal die Ergebnisse auf Anfrage von Simon:

PING 5.104.106.218 (5.104.106.218): 56 data bytes
64 bytes from 5.104.106.218: seq=0 ttl=57 time=28.445 ms
64 bytes from 5.104.106.218: seq=1 ttl=57 time=27.618 ms
64 bytes from 5.104.106.218: seq=2 ttl=57 time=26.740 ms
64 bytes from 5.104.106.218: seq=3 ttl=57 time=27.370 ms
64 bytes from 5.104.106.218: seq=4 ttl=57 time=29.171 ms
64 bytes from 5.104.106.218: seq=5 ttl=57 time=27.981 ms



PING 2001:4ba0:fffa:23:: (2001:4ba0:fffa:23::): 56 data bytes
ping: sendto: Network is unreachable



traceroute to 5.104.106.218 (5.104.106.218), 30 hops max, 38 byte packets
 1  192.168.0.1 (192.168.0.1)  1.608 ms  0.438 ms  0.408 ms
 2  217.0.119.83 (217.0.119.83)  18.491 ms  18.361 ms  18.203 ms
 3  217.0.72.254 (217.0.72.254)  19.473 ms  19.119 ms  21.625 ms
 4  62.154.15.226 (62.154.15.226)  27.743 ms  217.239.50.70 (217.239.50.70)  28.
 976 ms  217.239.50.94 (217.239.50.94)  27.295 ms
 5  62.157.251.170 (62.157.251.170)  27.868 ms  26.736 ms  28.770 ms
 6  62.141.47.185 (62.141.47.185)  39.722 ms  28.222 ms  134.949 ms
 7  62.141.47.106 (62.141.47.106)  28.195 ms  27.261 ms  27.545 ms
 8  5.104.106.218 (5.104.106.218)  28.863 ms  27.108 ms  27.979 ms


Johannes hat noch ein Tipp gegeben, den hoodselector umbenennen, damit der Chronjob den nicht jede Minute ausführt.
Das hat schon mal dazu geführt, dass ich eine Verbindung aufbauen kann, IPs werden zugewiesen, Seitenaufbau geht, selbst YouTube läuft ohne Probleme.

Status VOR der Umbenennung:


 batctl gwl
      Gateway      (#/255)           Nexthop [outgoingIF]: advertised uplink bandwidth ... [B.A.T.M.A.N. adv 2015.1, MainIF/MAC: mesh-vpn/a2:f7:c1:77:e2:5a (bat0)]
No gateways in range ...



/etc/config/fastd

config fastd 'sample_config'
        option enabled '0'
        option syslog_level 'info'
        list method 'salsa2012+umac'
        option mode 'tap'
        option interface 'tap0'
        option mtu '1426'
        option forward '0'
        option secure_handshakes '1'

config peer 'sample_peer'
        option enabled '0'
        option net 'sample_config'
        option key '0000000000000000000000000000000000000000000000000000000000000000'

config peer_group 'sample_group'
        option enabled '0'
        option net 'sample_config'

config fastd 'mesh_vpn'
        option enabled '1'
        option mtu '1312'
        option group 'gluon-fastd'
        option status_socket '/var/run/fastd.mesh_vpn.socket'
        option packet_mark '1'
        option syslog_level 'verbose'
        option mode 'tap'
        option secure_handshakes '1'
        option interface 'mesh-vpn'
        option secret '78c43014df4787ea79d0e78a2fbe4d546e6eb27714831f57a8a58becc0ac1153'
        list method 'salsa2012+umac'

config peer_group 'mesh_vpn_backbone'
        option enabled '1'
        option peer_limit '1'
        option net 'mesh_vpn'

config peer 'mesh_vpn_backbone_peer_lk_fri01'
        option enabled '1'
        option key '613ffbc8a5a2b1a8602866c0bd44afddecee79c49cde52ee4dd5df73c88d0437'
        option net 'mesh_vpn'
        list remote '"lk-fri01.sn.ffnw.de" port 10001'
        option group 'mesh_vpn_backbone'



Status NACH der Umbenennung:

batctl gwl
      Gateway      (#/255)           Nexthop [outgoingIF]: advertised uplink bandwidth ... [B.A.T.M.A.N. adv 2015.1, MainIF/MAC: mesh-vpn/a2:f7:c1:77:e2:5a (bat0)]
   2e:99:b2:0a:25:a1 (194) 8e:95:b6:13:6f:1e [  mesh-vpn]: 100.0/100.0 MBit
=> 8e:95:b6:13:6f:1e (215) 8e:95:b6:13:6f:1e [  mesh-vpn]: 1000.0/1000.0 MBit
   ce:47:d3:02:f5:bd (166) 8e:95:b6:13:6f:1e [  mesh-vpn]: 1000.0/1000.0 MBit
   12:b2:19:08:61:6c (175) 8e:95:b6:13:6f:1e [  mesh-vpn]: 1000.0/1000.0 MBit
   52:ba:56:97:9f:2e (194) 8e:95:b6:13:6f:1e [  mesh-vpn]: 100.0/100.0 MBit


/etc/config/fastd

config fastd 'sample_config' option enabled '0' option syslog_level 'info' list method 'salsa2012+umac' option mode 'tap' option interface 'tap0' option mtu '1426' option forward '0' option secure_handshakes '1' config peer 'sample_peer' option enabled '0' option net 'sample_config' option key '0000000000000000000000000000000000000000000000000000000000000000' config peer_group 'sample_group' option enabled '0' option net 'sample_config' config fastd 'mesh_vpn' option enabled '1' option mtu '1312' option group 'gluon-fastd' option status_socket '/var/run/fastd.mesh_vpn.socket' option packet_mark '1' option syslog_level 'verbose' option mode 'tap' option secure_handshakes '1' option interface 'mesh-vpn' option secret '78c43014df4787ea79d0e78a2fbe4d546e6eb27714831f57a8a58becc0ac1153' list method 'salsa2012+umac' config peer_group 'mesh_vpn_backbone' option enabled '1' option peer_limit '1' option net 'mesh_vpn' config peer 'mesh_vpn_backbone_peer_default02' option enabled '1' option key '32a02dd5e6b9233926e178ac609023ad30bcf26954d38d410088bbdc0b2258cb' option net 'mesh_vpn' list remote '"default02.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default03' option enabled '1' option key '9737c65a17cfaa8339315ee53d2b9e02520733780362efacf9503737f5a23204' option net 'mesh_vpn' list remote '"default03.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default04' option enabled '1' option key '18199a10620dbd13728a09402ca2364436ca27e46e669a2ebdfe20976dc45e6f' option net 'mesh_vpn' list remote '"default04.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default05' option enabled '1' option key '5c1738236ba6930f654fd5e815e0c63ac03f81551ee2b183045b256fb133f77d' option net 'mesh_vpn' list remote '"default05.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default06' option enabled '1' option key '22e270ff9b2d1017c3a0b00dd22a58ef7e5915a355eeb16f0b8b52d7eb377869' option net 'mesh_vpn' list remote '"default06.ffnw.de" port 11111' option group 'mesh_vpn_backbone'

Am 5. Juni 2016 um 13:53 schrieb Simon Kurka via Nordwest <nordwest@lists.ffnw.de>:
Könntest du nochmal mit 1.0 pings ausführen auf:
5.104.106.218
2001:4ba0:fffa:23::

Das ist default02.ffnw.de aufgelöst.

Außerdem ein traceroute auf die IPv4.
-- 
Viele Grüße,
Simon

_______________________________________________
Nordwest mailing list
Nordwest@lists.ffnw.de
https://lists.ffnw.de/mailman/listinfo/nordwest




Nordwest mailing list
Nordwest@lists.ffnw.de
https://lists.ffnw.de/mailman/listinfo/nordwest

--
vg
Stefan