[Berlin-wireless] chris / am-dach-ns5-sw gateway Problem Endless story
rainer at strassburger.name
rainer
Di Mai 1 01:41:52 CEST 2018
chris / am-dach-ns5-sw
Die endlose Geschichte-- Kapitel 999.....
Bitte dies unzuverlässige Gateway am dach abschalten.
Danke
von chris-o2 aus:
Smartgaetway:
10.31.48.5 ; am-dach-ns5-sw
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
raceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 77.87.48.52 3.474 ms
2 10.31.33.17 12.767 ms
3 *
4 *
5 *
6 *
7 *
8 *
9 *
10 *
11 *
12 *
13 *
14 *
von chris-n2 aus:
KEIN Smartgateway gewaehlt
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=2 ttl=53 time=49.839 ms
64 bytes from 8.8.8.8: seq=3 ttl=53 time=36.591 ms
64 bytes from 8.8.8.8: seq=4 ttl=53 time=41.670 ms
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 3 packets received, 40% packet loss
round-trip min/avg/max = 36.591/42.700/49.839 ms
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 10.230.18.184 0.465 ms
2 10.230.145.173 1.804 ms
3 77.87.48.52 4.938 ms
4 10.31.33.17 9.688 ms
5 *
6 *
7 *
8 *
9 88.134.237.176 20.819 ms
10 *
11 *
12 *
13 *
14 *
15 *
16 *
17 *
18 8.8.8.8 33.634 ms
von chris-s2 aus:
Smartgaetway:
10.31.48.5 ; am-dach-ns5-sw
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
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=3 ttl=53 time=38.825 ms
64 bytes from 8.8.8.8: seq=4 ttl=53 time=40.794 ms
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 2 packets received, 60% packet loss
round-trip min/avg/max = 38.825/39.809/40.794 ms
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 77.87.48.52 3.533 ms
2 10.31.33.17 16.892 ms
3 *
4 *
5 *
6 *
7 88.134.237.176 25.721 ms
8 88.134.237.147 24.952 ms
9 *
10 108.170.241.161 51.536 ms
11 *
12 *
13 *
14 *
15 *
16 *
17 *
18 *
19 *
20 *
21 *
22 *
23 *
24 *
25 *
26 *
27 *
28 *
29 *
30 *
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 77.87.48.52 3.583 ms
2 10.31.33.17 14.267 ms
3 *
4 91.64.85.254 30.689 ms
5 *
6 *
7 *
8 *
9 *
10 *
11 *
12 *
13 *
14 *
15 *
16 *
17 *
18 *
19 8.8.8.8 39.373 ms
traceroute: bad address 'dev.openwrt.org'
ping: bad address 'dev.openwrt.org'
Server: 127.0.0.1
Address 1: 127.0.0.1 localhost
nslookup: can't resolve 'dev.openwrt.org': Name or service not known
von chris-w2 aus:
Smartgaetway:
10.31.48.5 ; 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.569 ms
2 10.31.33.17 12.936 ms
3 *
4 *
5 *
6 *
7 *
8 *
9 *
10 *
11 *
12 *
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
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=3 ttl=53 time=39.146 ms
64 bytes from 8.8.8.8: seq=4 ttl=53 time=45.795 ms
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 2 packets received, 60% packet loss
round-trip min/avg/max = 39.146/42.470/45.795 ms
Gegencheck: hier keine Probleme.
von chris-core aus:
Smartgaetway: 10.31.11.1 ; emma-core
traceroute to dev.openwrt.org (217.115.15.26), 30 hops max, 38 byte packets
1 10.31.11.93 12.801 ms
2 10.31.11.100 12.399 ms
3 109.68.230.68 15.986 ms
4 77.247.82.163 11.106 ms
5 109.68.226.26 16.450 ms
6 62.115.147.68 11.868 ms
7 62.115.139.6 27.988 ms
8 62.115.140.19 27.809 ms
9 62.115.37.102 27.433 ms
10 134.222.48.144 50.501 ms
11 134.222.48.174 43.216 ms
12 134.222.48.147 37.686 ms
13 134.222.48.19 39.192 ms
14 134.222.98.5 45.597 ms
15 217.115.0.164 46.794 ms
16 217.115.15.26 45.305 ms
PING dev.openwrt.org (217.115.15.26): 56 data bytes
64 bytes from 217.115.15.26: seq=0 ttl=53 time=41.196 ms
64 bytes from 217.115.15.26: seq=1 ttl=53 time=46.364 ms
64 bytes from 217.115.15.26: seq=2 ttl=53 time=47.544 ms
64 bytes from 217.115.15.26: seq=3 ttl=53 time=48.024 ms
--- dev.openwrt.org ping statistics ---
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max = 41.196/45.782/48.024 ms
Macht echt kein Spass.
Das Problem geht dieses Jahr in den 5.Monat....
Mehr Informationen über die Mailingliste Berlin