Custom query (1016 matches)
Results (16 - 18 of 1016)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#18 | pending | High packet loss outside between bar and leisure center | ||
Description |
I've got 3 "bars" out of 4 on the signal meter on the mac, but 40-70% packet loss: tela% ping -c 10 130.129.16.2 PING 130.129.16.2 (130.129.16.2): 56 data bytes 64 bytes from 130.129.16.2: icmp_seq=2 ttl=64 time=1.753 ms 64 bytes from 130.129.16.2: icmp_seq=3 ttl=64 time=1.840 ms 64 bytes from 130.129.16.2: icmp_seq=4 ttl=64 time=27.907 ms 64 bytes from 130.129.16.2: icmp_seq=7 ttl=64 time=2.138 ms 64 bytes from 130.129.16.2: icmp_seq=8 ttl=64 time=1.855 ms 64 bytes from 130.129.16.2: icmp_seq=9 ttl=64 time=1.485 ms --- 130.129.16.2 ping statistics --- 10 packets transmitted, 6 packets received, 40% packet loss round-trip min/avg/max/stddev = 1.485/6.163/27.907/9.726 ms tela% ping -c 10 130.129.16.3 PING 130.129.16.3 (130.129.16.3): 56 data bytes 64 bytes from 130.129.16.3: icmp_seq=1 ttl=64 time=9.906 ms 64 bytes from 130.129.16.3: icmp_seq=2 ttl=64 time=2.538 ms 64 bytes from 130.129.16.3: icmp_seq=4 ttl=64 time=15.788 ms 64 bytes from 130.129.16.3: icmp_seq=5 ttl=64 time=1.902 ms 64 bytes from 130.129.16.3: icmp_seq=6 ttl=64 time=58.854 ms 64 bytes from 130.129.16.3: icmp_seq=8 ttl=64 time=1.711 ms 64 bytes from 130.129.16.3: icmp_seq=9 ttl=64 time=1.936 ms --- 130.129.16.3 ping statistics --- 10 packets transmitted, 7 packets received, 30% packet loss round-trip min/avg/max/stddev = 1.711/13.234/58.854/19.280 ms tela% ping -c 10 130.129.16.1 PING 130.129.16.1 (130.129.16.1): 56 data bytes 64 bytes from 130.129.16.1: icmp_seq=2 ttl=64 time=1.707 ms 64 bytes from 130.129.16.1: icmp_seq=7 ttl=64 time=1.514 ms 64 bytes from 130.129.16.1: icmp_seq=8 ttl=64 time=1.496 ms --- 130.129.16.1 ping statistics --- 10 packets transmitted, 3 packets received, 70% packet loss round-trip min/avg/max/stddev = 1.496/1.572/1.707/0.096 ms My MAC address: 00:1e:c2:b9:ed:7a tela% /System/Library/PrivateFrameworks/Apple80211.framework/Versions/ A/Resources/airport -s SSID BSSID RSSI CHANNEL SECURITY (auth/unicast/group) ietf.1x 00:1a:1e:8e:d7:75 -85 100,+1 WPA2(802.1x/AES/AES) ietf.1x-a 00:1a:1e:8e:d7:74 -84 100,+1 WPA2(802.1x/AES/AES) ietf-v6ONLY 00:1a:1e:8e:d7:73 -84 100 NONE ietf-a 00:1a:1e:8e:d7:70 -85 100,+1 NONE ietf.1x 00:1a:1e:8e:9f:75 -83 60,+1 WPA2(802.1x/AES/AES) ietf.1x-a 00:1a:1e:8e:9f:74 -84 60,+1 WPA2(802.1x/AES/AES) ietf-v6ONLY 00:1a:1e:8e:9f:73 -82 60 NONE ietf 00:1a:1e:8e:9f:72 -81 60 NONE ietf-a 00:1a:1e:8e:9f:70 -81 60,+1 NONE ietf.1x 00:1a:1e:8e:d7:63 -84 13 WPA2(802.1x/AES/AES) ietf-v6ONLY 00:1a:1e:8e:d7:62 -83 13 NONE ietf-v6ONLY 00:1a:1e:88:84:c2 -85 13 NONE ietf 00:1a:1e:88:84:c1 -85 13 NONE ietf 00:1a:1e:8e:d7:61 -84 13 NONE ietf-cgnat 00:1a:1e:8e:d7:60 -83 13 NONE ietf.1x 00:1a:1e:88:84:c3 -83 13 WPA2(802.1x/AES/AES) ietf-cgnat 00:1a:1e:88:84:c0 -85 13 NONE citywest_hotel_3 00:19:5b:42:bc:da -89 6 NONE eircom 00:0b:46:66:d4:fe -86 7 NONE ietf.1x 00:1a:1e:8e:9f:03 -79 6 WPA2(802.1x/AES/AES) ietf-v6ONLY 00:1a:1e:8e:9f:02 -74 6 NONE ietf 00:1a:1e:8e:9f:01 -79 6 NONE ietf-cgnat 00:1a:1e:8e:9f:00 -73 6 NONE ietf.1x 00:1a:1e:8e:9f:63 -71 1 WPA2(802.1x/AES/AES) ietf-v6ONLY 00:1a:1e:8e:9f:62 -71 1 NONE ietf 00:1a:1e:8e:9f:61 -71 1 NONE ietf-cgnat 00:1a:1e:8e:9f:60 -70 1 NONE ietf 00:1a:1e:8e:9f:12 -78 120 NONE tela% /System/Library/PrivateFrameworks/Apple80211.framework/Versions/ A/Resources/airport -I agrCtlRSSI: -82 agrExtRSSI: 0 agrCtlNoise: -93 agrExtNoise: 0 state: running op mode: station lastTxRate: 6 maxRate: 54 lastAssocStatus: 0 802.11 auth: open link auth: unknown BSSID: 0:1a:1e:8e:9f:12 SSID: ietf MCS: -1 channel: 120 |
|||
#19 | worksforme | Vanessa AP | ||
Description |
I have cable but pt no pot AP in room. Sent via BlackBerry by AT&T |
|||
#20 | wontfix | local web cache ? | ||
Description |
My recollection is that there is usually a local cache of the IETF web site. I'm finding things like the agenda page are loading very slowly. Is there a web cache? Could it be malfunctioning? --aaron |
Note: See TracQuery for help on using queries.