Custom query (902 matches)

Filters
 
or
 
  
 
Columns

Show under each result:


Results (85 - 87 of 902)

Ticket Resolution Summary Owner Reporter
#1085 fixed Wi-Fi flakey in Zurich D panda@… ray@…
Description
Hi Jim and co -

FYI, the Wi-Fi seems to be suffering somewhat in Zurich D.

% ping 31.133.128.1
PING 31.133.128.1 (31.133.128.1): 56 data bytes
64 bytes from 31.133.128.1: icmp_seq=0 ttl=64 time=70.279 ms
64 bytes from 31.133.128.1: icmp_seq=1 ttl=64 time=55.285 ms
64 bytes from 31.133.128.1: icmp_seq=2 ttl=64 time=140.829 ms
64 bytes from 31.133.128.1: icmp_seq=3 ttl=64 time=252.530 ms
64 bytes from 31.133.128.1: icmp_seq=4 ttl=64 time=649.491 ms
64 bytes from 31.133.128.1: icmp_seq=5 ttl=64 time=181.937 ms
64 bytes from 31.133.128.1: icmp_seq=6 ttl=64 time=222.974 ms
Request timeout for icmp_seq 7
64 bytes from 31.133.128.1: icmp_seq=7 ttl=64 time=1897.860 ms
64 bytes from 31.133.128.1: icmp_seq=8 ttl=64 time=1951.382 ms
Request timeout for icmp_seq 10
64 bytes from 31.133.128.1: icmp_seq=9 ttl=64 time=2506.882 ms
64 bytes from 31.133.128.1: icmp_seq=10 ttl=64 time=1597.103 ms
64 bytes from 31.133.128.1: icmp_seq=11 ttl=64 time=2576.747 ms
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
64 bytes from 31.133.128.1: icmp_seq=12 ttl=64 time=5114.501 ms
64 bytes from 31.133.128.1: icmp_seq=13 ttl=64 time=4204.371 ms
64 bytes from 31.133.128.1: icmp_seq=14 ttl=64 time=3350.782 ms
64 bytes from 31.133.128.1: icmp_seq=15 ttl=64 time=2869.893 ms
64 bytes from 31.133.128.1: icmp_seq=16 ttl=64 time=2258.604 ms
64 bytes from 31.133.128.1: icmp_seq=17 ttl=64 time=2808.947 ms
64 bytes from 31.133.128.1: icmp_seq=18 ttl=64 time=1923.856 ms
64 bytes from 31.133.128.1: icmp_seq=19 ttl=64 time=2028.737 ms
64 bytes from 31.133.128.1: icmp_seq=20 ttl=64 time=1993.952 ms
64 bytes from 31.133.128.1: icmp_seq=21 ttl=64 time=2092.593 ms

% ifconfig en0
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether a4:5e:60:cf:bf:9b
	inet6 fe80::1ccc:7c66:e6d2:b53b%en0 prefixlen 64 secured scopeid 0x4
	inet6 2001:67c:370:128:448:9ce1:407:9e71 prefixlen 64 autoconf secured
	inet6 2001:67c:370:128:c55b:6eb6:be50:ed25 prefixlen 64 autoconf temporary
	inet 31.133.135.81 netmask 0xfffff000 broadcast 31.133.143.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
#1086 fixed IPv6 failing in Zurich A panda@… mcr@…
Description

Hi, I'm in Zurich A on IETF network. IPv4 working great.

wlan0     Link encap:Ethernet  HWaddr 08:11:96:01:81:e0  
          inet addr:31.133.141.144  Bcast:31.133.143.255  Mask:255.255.240.0
          inet6 addr: 2001:67c:370:128:a11:96ff:fe01:81e0/64 Scope:Global
          inet6 addr: fe80::a11:96ff:fe01:81e0/64 Scope:Link

dooku-[~](2.3.0) mcr 10053 %iwconfig wlan0
wlan0     IEEE 802.11  ESSID:"ietf"  
          Mode:Managed  Frequency:5.745 GHz  Access Point: FC:5B:39:32:D6:8E   
          Bit Rate=39 Mb/s   Tx-Power=15 dBm   

dooku-[~](2.3.0) mcr 10051 %ping6 obiwan.sandelman.ca
PING obiwan.sandelman.ca(obiwan.sandelman.ca) 56 data bytes
... no answers.


tcpdump shows:
13:30:29.462685 IP6 2001:67c:370:128:a11:96ff:fe01:81e0 > 2607:f0b0:f:2::247: ICMP6, echo request, seq 5, length 64

traceroute -6 obiwan.sandelman.ca gets no reply, not even first hop:

13:30:52.235056 IP6 2001:67c:370:128:a11:96ff:fe01:81e0.41885 > 2607:f0b0:f:2::247.33450: UDP, length 32
13:30:52.235156 IP6 2001:67c:370:128:a11:96ff:fe01:81e0.40217 > 2607:f0b0:f:2::247.33451: UDP, length 32
13:30:52.235207 IP6 2001:67c:370:128:a11:96ff:fe01:81e0.43104 > 2607:f0b0:f:2::247.33452: UDP, length 32
13:30:52.235250 IP6 2001:67c:370:128:a11:96ff:fe01:81e0.36767 > 2607:f0b0:f:2::247.33453: UDP, length 32
13:30:52.235294 IP6 2001:67c:370:128:a11:96ff:fe01:81e0.60832 > 2607:f0b0:f:2::247.33454: UDP, length 32
13:30:52.235339 IP6 2001:67c:370:128:a11:96ff:fe01:81e0.46167 > 2607:f0b0:f:2::247.33455: UDP, length 32


dooku-[~](2.3.0) mcr 10056 %ip -6 route ls
2001:67c:370:128::/64 dev wlan0  proto kernel  metric 256  expires 2591998sec
fe80::/64 dev wlan0  proto kernel  metric 256 
default via fe80::128:1 dev wlan0  proto ra  metric 1024  expires 598sec hoplimit 64

yet, I'm clearly able to reach the 
dooku-[~](2.3.0) mcr 10058 %ping6 fe80::128:1%wlan0
PING fe80::128:1%wlan0(fe80::128:1) 56 data bytes
64 bytes from fe80::128:1: icmp_seq=1 ttl=64 time=24.8 ms
64 bytes from fe80::128:1: icmp_seq=2 ttl=64 time=28.5 ms


so, just to be sure, let's show mac addresses of router:

dooku-[~](2.3.0) mcr 10004 %sudo tcpdump -e -i wlan0 -n -p ip6 and not port 5353
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 262144 bytes
13:32:03.625923 08:81:f4:8a:a7:f0 > 08:11:96:01:81:e0, ethertype IPv6 (0x86dd), length 150: fe80::128:1 > ff02::1: ICMP6, router advertisement, length 96
13:32:05.234207 00:00:5e:00:02:80 > 33:33:00:00:00:12, ethertype IPv6 (0x86dd), length 94: fe80::128:2 > ff02::12: ip-proto-112 40
13:32:05.278574 08:11:96:01:81:e0 > 00:00:5e:00:02:80, ethertype IPv6 (0x86dd), length 94: 2001:67c:370:128:a11:96ff:fe01:81e0.50299 > 2607:f0b0:f:2::247.33434: UDP, length 32
13:32:05.278658 08:11:96:01:81:e0 > 00:00:5e:00:02:80, ethertype IPv6 (0x86dd), length 94: 2001:67c:370:128:a11:96ff:fe01:81e0.60173 > 2607:f0b0:f:2::247.33435: UDP, length 32
13:32:05.278706 08:11:96:01:81:e0 > 00:00:5e:00:02:80, ethertype IPv6 (0x86dd), length 94: 2001:67c:370:128:a11:96ff:fe01:81e0.48191 > 2607:f0b0:f:2::247.33436: UDP, length 32
13:32:05.278758 08:11:96:01:81:e0 > 00:00:5e:00:02:80, ethertype IPv6 (0x86dd), length 94: 2001:67c:370:128:a11:96ff:fe01:81e0.59227 > 2607:f0b0:f:2::247.33437: UDP, length 32
13:32:05.278804 08:11:96:01:81:e0 > 00:00:5e:00:02:80, ethertype IPv6 (0x86dd), length 94: 2001:67c:370:128:a11:96f


which looks right:

dooku-[~](2.3.0) mcr 10060 %ip -6 neigh show
fe80::128:3 dev wlan0 lladdr 80:71:1f:c3:90:00 router STALE
fe80::128:1 dev wlan0 lladdr 00:00:5e:00:02:80 router DELAY


I also tried ping6 google.com, and ping6 www.v6.facebook.com (which is where I noticed breakage originally) V6 was working for me in Zurich C this morning.

#1089 fixed Weird nat64 network behavior panda@… furry13@…
Description
Hi guys,

Lorenzo and I are seeing smth very weird while connecting to nat64 SSID.
I'm attaching .pcap file but let me explain what's happening:

- my laptop connects to wifi, sends and RS (packet #4), gets an RA (packet #33).
The RA contains RDNSS info and PIO, so my host configures LLA and two
GUAs (performing DAD) and then starts sending DNS requests (packets
#47 ...)
No response. At some point (packet #144) my host sends NS for the
router address (fe80::1998:1), gets a response, keeps sending DNS
requests - no response.
Then, suddenly, after ~11 seconds after sending the very first RS
(packet #4 mentioned above), my host receives two DAD packets for its
own GUAs (packets #265 and 267) sent by some Cisco device (MAC
address: 00:3a:7d:71:93:89).
My host responds and suddenly everything starts working - my host is
getting DNS responses back etc....

Any idea what it is?

-- 
SY, Jen Linkova aka Furry

nat64-1.pcap

Note: See TracQuery for help on using queries.