[Berlin-wireless] chris / am-dach-ns5-sw
rainer at strassburger.name
rainer at strassburger.name
Mi Apr 25 18:49:56 CEST 2018
Hallo Perry,
falls Du es noch nicht weisst, oder ist es so von dir gewollt???:
leider hat es wieder nen Problem bei chris mit am-dach-ns5-sw
Werde bis Du mir Freigabe gibst nichts aendern.
Ist einfach nen super Zustand zur Demo des Problems.
Es sind allerdings die zwei meistgenutzen chris-Router betroffen...
Auffaelligkeit:
am-dach-ns5-sw hat firmware kathleen 0.1.0
Probleme sobald von chris aus ueber am-dach-ns5-sw 77.87.48.52 geroutet wird
Habe also anscheinend vorschnell am-dach-rt1 verdaechtigt.
Geht das ganze nicht auch uber diesen???
Bin aber froh dass wir jetzt so ne prima Demosituation haben.
Hoffe der "Taeter" legt bald nen Gestaendnis ab......
Stand:
chris-w5 hat zur Zeit keinen smartgateway gewaehlt.
Warum weiss ich nicht.
Tests von chris-w2 aus:
Problem: traceroute haengt am-dach-ns5-sw
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 10.230.18.184 0.269 ms
2 10.230.145.173 9.316 ms
3 77.87.48.52 3.668 ms !N
bzw nameserver-Probleme ???:
traceroute: bad address 'dev.openwrt.org'
Ping antwortet nicht:
PING 8.8.8.8 (8.8.8.8): 56 data bytes
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
von meinem pc ueber bbb-vpn aus:
dort ist am-dach-ns5-sw anscheinend nicht beteiligt
$ traceroute chris-w2.olsr
traceroute to chris-w2.olsr (10.230.18.189), 30 hops max, 60 byte packets
1 frei.funk (10.36.177.1) 10.059 ms 9.980 ms 9.962 ms
2 10.230.22.1 (10.230.22.1) 100.388 ms * 202.340 ms
3 am-dach-rt1.olsr (77.87.48.50) 203.425 ms 204.252 ms 205.091 ms
4 mid6.tub-core.olsr (10.31.31.77) 205.778 ms 207.184 ms 207.842 ms
5 mid2.chris-core.olsr (10.230.18.181) 208.798 ms 209.626 ms
210.813 ms
6 chris-w2.olsr (10.230.18.189) 211.520 ms 199.982 ms 202.794 ms
Tests von chris-s2 aus:
Stand: Gewaehltes Smartgateway:
am-dach-ns5-sw
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 77.87.48.52 3.636 ms !N
PING 8.8.8.8 (8.8.8.8): 56 data bytes
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
vom PC aus:
$ traceroute chris-s2.olsr
traceroute to chris-s2.olsr (10.230.18.188), 30 hops max, 60 byte packets
1 frei.funk (10.36.177.1) 6.704 ms 6.693 ms 6.629 ms
2 10.230.22.1 (10.230.22.1) 101.848 ms 102.282 ms 107.562 ms
3 am-dach-rt1.olsr (77.87.48.50) 109.196 ms 110.648 ms 111.751 ms
4 mid6.tub-core.olsr (10.31.31.77) 111.747 ms 112.642 ms 113.443 ms
5 mid2.tberg-core.olsr (10.31.3.1) 116.450 ms 116.389 ms 119.069 ms
6 mid3.chris-core.olsr (10.230.18.169) 201.827 ms 256.666 ms
258.868 ms
7 chris-s2.olsr (10.230.18.188) 259.564 ms 162.961 ms 188.105 ms
Gegencheck:
Test von chris-o2 aus:
Stand:
swartgateway:
10.31.11.1 also emma-core
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 10.31.11.93 17.727 ms
2 10.31.11.100 6.812 ms
3 109.68.230.68 4.847 ms
4 77.247.82.163 16.984 ms
5 109.68.226.215 14.873 ms
6 37.49.155.39 23.691 ms
7 108.170.251.129 14.403 ms
8 216.239.59.115 28.851 ms
9 8.8.8.8 22.105 ms
traceroute to dev.openwrt.org (217.115.15.26), 30 hops max, 38 byte packets
1 10.31.11.93 91.654 ms
2 10.31.11.100 6.256 ms
3 109.68.230.68 6.844 ms
4 77.247.82.163 8.288 ms
5 109.68.226.26 13.484 ms
6 62.115.147.68 6.727 ms
7 62.115.139.6 19.645 ms
8 62.115.142.13 28.809 ms
9 62.115.37.102 136.569 ms
10 134.222.48.144 74.168 ms
11 134.222.48.174 34.861 ms
12 134.222.48.147 34.385 ms
13 134.222.48.19 37.440 ms
14 134.222.98.5 38.727 ms
15 217.115.0.161 44.549 ms
16 217.115.0.163 148.108 ms
17 217.115.15.26 89.916 ms
PING dev.openwrt.org (217.115.15.26): 56 data bytes
64 bytes from 217.115.15.26: seq=0 ttl=52 time=37.863 ms
64 bytes from 217.115.15.26: seq=1 ttl=52 time=46.877 ms
64 bytes from 217.115.15.26: seq=2 ttl=52 time=36.062 ms
64 bytes from 217.115.15.26: seq=3 ttl=51 time=39.196 ms
64 bytes from 217.115.15.26: seq=4 ttl=52 time=41.127 ms
--- dev.openwrt.org ping statistics ---
5 packets transmitted, 5 packets received, 0% packet lossPING 8.8.8.8
(8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=55 time=14.369 ms
64 bytes from 8.8.8.8: seq=1 ttl=55 time=16.070 ms
64 bytes from 8.8.8.8: seq=2 ttl=55 time=21.377 ms
64 bytes from 8.8.8.8: seq=3 ttl=55 time=16.299 ms
64 bytes from 8.8.8.8: seq=4 ttl=55 time=16.704 ms
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 14.369/16.963/21.377 ms
round-trip min/avg/max = 36.062/40.225/46.877 ms
vom Pc aus:
$ traceroute chris-o2.olsr
traceroute to chris-o2.olsr (10.230.18.187), 30 hops max, 60 byte packets
1 frei.funk (10.36.177.1) 9.906 ms 9.839 ms 9.820 ms
2 10.230.22.1 (10.230.22.1) 100.199 ms 100.945 ms 102.150 ms
3 am-dach-rt1.olsr (77.87.48.50) 104.871 ms 105.680 ms 106.273 ms
4 mid6.tub-core.olsr (10.31.31.77) 107.035 ms 108.055 ms 108.861 ms
5 mid2.chris-core.olsr (10.230.18.181) 159.664 ms 160.704 ms
162.904 ms
6 chris-o2.olsr (10.230.18.187) 162.910 ms 148.616 ms 149.220 ms
Gegencheck von chris-n2 aus
Test von chris-n2 aus:
Stand:
swartgateway:
10.31.11.1 also emma-core
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 10.31.11.93 55.197 ms
2 10.31.11.100 52.349 ms
3 109.68.230.68 289.353 ms
4 *
5 109.68.226.215 207.887 ms
6 37.49.155.39 121.472 ms
7 108.170.252.1 169.163 ms
8 108.170.226.137 238.037 ms
9 8.8.8.8 228.690 ms
traceroute to dev.openwrt.org (217.115.15.26), 30 hops max, 38 byte packets
1 10.31.11.93 6.043 ms
2 10.31.11.100 9.467 ms
3 109.68.230.68 96.883 ms
4 77.247.82.163 93.400 ms
5 109.68.226.26 98.762 ms
6 62.115.147.68 91.358 ms
7 62.115.139.6 108.652 ms
8 62.115.142.13 86.850 ms
9 62.115.37.102 113.322 ms
10 134.222.48.144 203.731 ms
11 134.222.48.174 219.179 ms
12 134.222.48.147 246.275 ms
13 134.222.48.19 170.213 ms
14 134.222.98.5 45.874 ms
15 217.115.0.161 39.945 ms
16 217.115.0.163 61.274 ms
17 217.115.15.26 43.438 ms
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=54 time=43.116 ms
64 bytes from 8.8.8.8: seq=1 ttl=54 time=20.820 ms
64 bytes from 8.8.8.8: seq=2 ttl=54 time=41.419 ms
64 bytes from 8.8.8.8: seq=4 ttl=54 time=31.394 ms
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max = 20.820/34.187/43.116 ms
PING dev.openwrt.org (217.115.15.26): 56 data bytes
64 bytes from 217.115.15.26: seq=0 ttl=51 time=42.826 ms
64 bytes from 217.115.15.26: seq=1 ttl=51 time=51.143 ms
64 bytes from 217.115.15.26: seq=2 ttl=51 time=166.572 ms
64 bytes from 217.115.15.26: seq=3 ttl=51 time=53.307 ms
--- dev.openwrt.org ping statistics ---
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max = 42.826/78.462/166.572 ms
vom PC aus:
$ traceroute chris-n2.olsr
traceroute to chris-n2.olsr (10.230.18.186), 30 hops max, 60 byte packets
1 frei.funk (10.36.177.1) 6.026 ms 6.026 ms 5.960 ms
2 10.230.22.1 (10.230.22.1) 103.868 ms 103.866 ms 103.850 ms
3 am-dach-rt1.olsr (77.87.48.50) 105.049 ms 109.106 ms 109.106 ms
4 mid6.tub-core.olsr (10.31.31.77) 109.041 ms 113.623 ms 114.385 ms
5 mid2.tberg-core.olsr (10.31.3.1) 115.394 ms 116.419 ms 117.194 ms
6 mid3.chris-core.olsr (10.230.18.169) 122.281 ms 161.625 ms
209.726 ms
7 chris-n2.olsr (10.230.18.186) 210.741 ms 414.824 ms 442.153 ms
und vom chris-core aus:
Gegencheck von chris-n2 aus
Test von chris-core aus:
Stand:
swartgateway:
10.31.11.1 also emma-core
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 10.31.11.93 10.009 ms
2 10.31.11.100 16.935 ms
3 109.68.230.68 13.597 ms
4 77.247.82.163 27.781 ms
5 109.68.226.215 36.091 ms
6 37.49.155.39 36.573 ms
7 108.170.251.129 31.366 ms
8 108.170.226.137 32.108 ms
9 8.8.8.8 25.782 ms
traceroute to dev.openwrt.org (217.115.15.26), 30 hops max, 38 byte packets
1 10.31.11.93 16.905 ms
2 10.31.11.100 58.195 ms
3 109.68.230.68 46.087 ms
4 77.247.82.163 28.939 ms
5 109.68.226.26 26.687 ms
6 62.115.147.68 20.642 ms
7 62.115.139.6 30.628 ms
8 62.115.142.11 38.244 ms
9 62.115.37.102 42.892 ms
10 134.222.48.144 66.519 ms
11 134.222.48.174 82.105 ms
12 134.222.48.147 76.735 ms
13 134.222.48.19 62.180 ms
14 134.222.98.5 45.413 ms
15 217.115.0.161 75.817 ms
16 217.115.0.163 45.782 ms
17 217.115.15.26 42.677 ms
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=55 time=82.136 ms
64 bytes from 8.8.8.8: seq=1 ttl=55 time=87.493 ms
64 bytes from 8.8.8.8: seq=2 ttl=55 time=57.348 ms
64 bytes from 8.8.8.8: seq=3 ttl=55 time=181.884 ms
64 bytes from 8.8.8.8: seq=4 ttl=55 time=50.067 ms
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 50.067/91.785/181.884 ms
PING dev.openwrt.org (217.115.15.26): 56 data bytes
64 bytes from 217.115.15.26: seq=0 ttl=52 time=69.471 ms
64 bytes from 217.115.15.26: seq=1 ttl=52 time=67.764 ms
64 bytes from 217.115.15.26: seq=2 ttl=51 time=60.879 ms
64 bytes from 217.115.15.26: seq=3 ttl=51 time=136.814 ms
--- dev.openwrt.org ping statistics ---
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max = 60.879/83.732/136.814 ms
vom PC aus:
$ traceroute chris-core.olsr
traceroute to chris-core.olsr (10.230.18.185), 30 hops max, 60 byte packets
1 frei.funk (10.36.177.1) 11.010 ms 10.988 ms 10.919 ms
2 10.230.22.1 (10.230.22.1) 99.591 ms 100.905 ms 104.110 ms
3 am-dach-rt1.olsr (77.87.48.50) 105.195 ms 107.549 ms 107.553 ms
4 mid6.tub-core.olsr (10.31.31.77) 107.541 ms 108.264 ms 108.923 ms
5 mid2.tberg-core.olsr (10.31.3.1) 109.550 ms 110.390 ms 111.386 ms
6 chris-core.olsr (10.230.18.185) 255.689 ms 242.949 ms 243.628 ms
vom PC aus:
$ traceroute chris-core.olsr
traceroute to chris-core.olsr (10.230.18.185), 30 hops max, 60 byte packets
1 frei.funk (10.36.177.1) 11.010 ms 10.988 ms 10.919 ms
2 10.230.22.1 (10.230.22.1) 99.591 ms 100.905 ms 104.110 ms
3 am-dach-rt1.olsr (77.87.48.50) 105.195 ms 107.549 ms 107.553 ms
4 mid6.tub-core.olsr (10.31.31.77) 107.541 ms 108.264 ms 108.923 ms
5 mid2.tberg-core.olsr (10.31.3.1) 109.550 ms 110.390 ms 111.386 ms
6 chris-core.olsr (10.230.18.185) 255.689 ms 242.949 ms 243.628 ms
Mehr Informationen über die Mailingliste Berlin