[Freifunk-Bonn] Deutliche Netzwerk-Probleme
d.theisen at gmx.net
d.theisen at gmx.net
Fr Jul 4 11:58:07 CEST 2014
Hi!
Ich sitze gerade neben einem neuen Knoten „kermit“ (841ND) mit 50Mit uplink:
-----------------------------------------------------
BARRIER BREAKER (1.1 (ff-kbu), 1.1)
-----------------------------------------------------
root at kermit:~# batctl gwl
Gateway (#/255) Nexthop [outgoingIF]: gw_class ... [B.A.T.M.A.N. adv 2013.4.0, MainIF/MAC: mesh-vpn/76:ea:3a:a8:66:8e (bat0)]
=> 56:54:78:6b:e2:34 (255) 56:54:78:6b:e2:34 [ mesh-vpn]: 215 - 96MBit/96MBit
52:54:00:4a:0d:02 (225) 56:54:78:6b:e2:34 [ mesh-vpn]: 41 - 2048KBit/512KBit
06:80:5b:34:b7:f9 (198) 56:54:78:6b:e2:34 [ mesh-vpn]: 207 - 48MBit/48MBit
02:ff:0f:a5:7d:05 (251) 02:ff:0f:a5:7d:05 [ mesh-vpn]: 215 - 96MBit/96MBit
root at kermit:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=48 time=24.104 ms
64 bytes from 8.8.8.8: seq=1 ttl=48 time=23.505 ms
64 bytes from 8.8.8.8: seq=2 ttl=48 time=23.061 ms
64 bytes from 8.8.8.8: seq=3 ttl=48 time=23.216 ms
64 bytes from 8.8.8.8: seq=4 ttl=48 time=23.140 ms
64 bytes from 8.8.8.8: seq=5 ttl=48 time=22.972 ms
64 bytes from 8.8.8.8: seq=6 ttl=48 time=23.579 ms
64 bytes from 8.8.8.8: seq=7 ttl=48 time=22.829 ms
64 bytes from 8.8.8.8: seq=8 ttl=48 time=23.001 ms
64 bytes from 8.8.8.8: seq=9 ttl=48 time=22.997 ms
64 bytes from 8.8.8.8: seq=10 ttl=48 time=23.130 ms
64 bytes from 8.8.8.8: seq=11 ttl=48 time=23.184 ms
64 bytes from 8.8.8.8: seq=12 ttl=48 time=23.158 ms
64 bytes from 8.8.8.8: seq=13 ttl=48 time=23.062 ms
64 bytes from 8.8.8.8: seq=14 ttl=48 time=23.587 ms
64 bytes from 8.8.8.8: seq=15 ttl=48 time=23.168 ms
64 bytes from 8.8.8.8: seq=16 ttl=48 time=23.197 ms
^C
--- 8.8.8.8 ping statistics ---
17 packets transmitted, 17 packets received, 0% packet loss
root at kermit:~# ifconfig
bat0 Link encap:Ethernet HWaddr 66:BC:68:F5:0F:BF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70456 errors:0 dropped:0 overruns:0 frame:0
TX packets:9501 errors:0 dropped:55 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11767440 (11.2 MiB) TX bytes:1428175 (1.3 MiB)
br-freifunk Link encap:Ethernet HWaddr 74:EA:3A:A7:66:8E
inet6 addr: fe80::76ea:3aff:fea7:668e/64 Scope:Link
inet6 addr: 2001:67c:20a0:b102:76ea:3aff:fea7:668e/64 Scope:Global
inet6 addr: 2001:67c:20a0:b101:76ea:3aff:fea7:668e/64 Scope:Global
inet6 addr: fdd3:5d16:b5dd:0:76ea:3aff:fea7:668e/64 Scope:Global
inet6 addr: 2001:67c:20a0:b103:76ea:3aff:fea7:668e/64 Scope:Global
inet6 addr: 2001:67c:20a0:b105:76ea:3aff:fea7:668e/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:62399 errors:0 dropped:0 overruns:0 frame:0
TX packets:521 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4875682 (4.6 MiB) TX bytes:64488 (62.9 KiB)
br-wan Link encap:Ethernet HWaddr 74:EA:3A:A7:66:8F
inet addr:192.168.178.25 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: fdd3:5d16:b5dd:0:76ea:3aff:fea7:668f/64 Scope:Global
inet6 addr: 2001:4dd1:b1b7:0:76ea:3aff:fea7:668f/64 Scope:Global
inet6 addr: fe80::76ea:3aff:fea7:668f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:169268 errors:0 dropped:0 overruns:0 frame:0
TX packets:30099 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:32849868 (31.3 MiB) TX bytes:5692775 (5.4 MiB)
eth0 Link encap:Ethernet HWaddr 74:EA:3A:A7:66:8D
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:5
eth1 Link encap:Ethernet HWaddr 74:EA:3A:A7:66:8F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:169270 errors:0 dropped:0 overruns:0 frame:0
TX packets:30094 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:35219740 (33.5 MiB) TX bytes:5692054 (5.4 MiB)
Interrupt:4
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:400 errors:0 dropped:0 overruns:0 frame:0
TX packets:400 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:46081 (45.0 KiB) TX bytes:46081 (45.0 KiB)
mesh-vpn Link encap:Ethernet HWaddr 76:EA:3A:A8:66:8E
inet6 addr: fe80::74ea:3aff:fea8:668e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1426 Metric:1
RX packets:161716 errors:0 dropped:0 overruns:0 frame:0
TX packets:18814 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:23181263 (22.1 MiB) TX bytes:2583395 (2.4 MiB)
wlan0 Link encap:Ethernet HWaddr 74:EA:3A:A7:66:8E
inet6 addr: fe80::76ea:3aff:fea7:668e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1528 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:183949 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:25351486 (24.1 MiB)
wlan0-1 Link encap:Ethernet HWaddr 76:EA:3A:A7:66:8E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9517 errors:0 dropped:0 overruns:0 frame:0
TX packets:67624 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1439125 (1.3 MiB) TX bytes:12679256 (12.0 MiB)
root at kermit:~#
---------------------------------------------
Dem Router geht’s soweit prächtig.
Als WLAN-Client allerdings sieht das ganz anders aus:
---------------------------------------------
Last login: Fri Jul 4 03:22:35 on ttys003
Wanzling:~ theisen$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
64 bytes from 8.8.8.8: icmp_seq=9 ttl=51 time=598.093 ms
Request timeout for icmp_seq 10
64 bytes from 8.8.8.8: icmp_seq=11 ttl=51 time=93.018 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=51 time=177.791 ms
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
^C
--- 8.8.8.8 ping statistics ---
18 packets transmitted, 3 packets received, 83.3% packet loss
round-trip min/avg/max/stddev = 93.018/289.634/598.093/220.842 ms
Wanzling:~ theisen$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 20:c9:d0:88:00:77
inet6 fe80::22c9:d0ff:fe88:77%en0 prefixlen 64 scopeid 0x4
inet6 2001:67c:20a0:b102:22c9:d0ff:fe88:77 prefixlen 64 autoconf
inet6 2001:67c:20a0:b102:2085:11ce:dc2e:b4f8 prefixlen 64 autoconf temporary
inet6 2001:67c:20a0:b103:22c9:d0ff:fe88:77 prefixlen 64 detached autoconf
inet6 2001:67c:20a0:b103:51ad:ce52:cf47:33a9 prefixlen 64 detached autoconf temporary
inet6 fdd3:5d16:b5dd::22c9:d0ff:fe88:77 prefixlen 64 autoconf
inet6 fdd3:5d16:b5dd::708c:d093:981c:47b1 prefixlen 64 autoconf temporary
inet6 2001:67c:20a0:b101:22c9:d0ff:fe88:77 prefixlen 64 detached autoconf
inet6 2001:67c:20a0:b101:a8dc:fec0:3160:c1ed prefixlen 64 detached autoconf temporary
inet 172.27.57.113 netmask 0xffffc000 broadcast 172.27.63.255
inet6 2001:67c:20a0:b105:22c9:d0ff:fe88:77 prefixlen 64 autoconf
inet6 2001:67c:20a0:b105:4039:71dc:557a:e89b prefixlen 64 autoconf temporary
nd6 options=1<PERFORMNUD>
media: autoselect
status: active
---------------------------------------------
Reboot des Routers hat nichts geholfen.
Der Durchsatz ist nie über 1 Mbit downstream. Speedtest konnte meist nicht beendet werden wegen Download-Fehlern.
Hoffentlich helfen die o.G. Infos euch, die Situation zu verbessern.
Gruß,
g3ntleman
Mehr Informationen über die Mailingliste Freifunk-Bonn