#1037 closed defect (worksforme)
IPv6 problems in Studio 4
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | minor | Milestone: | ietf-097 |
Component: | network | Keywords: | |
Cc: | My Current Location: | ||
My MAC Address: | My OS: |
Description
Same problem with IPv6 in Studio 4. Re: IPv6 problems in Grand ballroom 2 dooku-[~] mcr 10130 %ip -6 route ls 2001:67c:370:128::/64 dev wlan0 proto kernel metric 256 expires 2591996sec fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::128:1 dev wlan0 proto ra metric 1024 expires 596sec hoplimit 64 dooku-[~] mcr 10131 %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=1.43 ms ^C --- fe80::128:1%wlan0 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.437/1.437/1.437/0.000 ms dooku-[~] mcr 10132 %ping6 www.google.com PING www.google.com(nrt20s01-in-x04.1e100.net) 56 data bytes ^C --- www.google.com ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2016ms dooku-[~] mcr 10133 %iwconfig wlan0 wlan0 IEEE 802.11 ESSID:"ietf-legacy" Mode:Managed Frequency:5.825 GHz Access Point: FC:5B:39:53:D8:6F Bit Rate=6 Mb/s Tx-Power=15 dBm Michael Richardson <mcr+ietf@sandelman.ca> wrote: > {I would try the ietf non-legacy network, but I have local issues with wicd, > I think I need to put in the CA value, which I haven't done yet} > dooku-[~] mcr 10096 %ping www.google.com > PING www.google.com (172.217.24.132) 56(84) bytes of data. > 64 bytes from nrt20s01-in-f4.1e100.net (172.217.24.132): icmp_seq=1 ttl=55 time=33.1 ms > 64 bytes from nrt20s01-in-f4.1e100.net (172.217.24.132): icmp_seq=2 ttl=55 time=... > dooku-[~] mcr 10097 %ping6 www.google.com > PING www.google.com(nrt20s01-in-x04.1e100.net) 56 data bytes > ... > {no v6 connectivity} > dooku-[~] mcr 10098 %ip -6 neigh show > fe80::128:1 dev wlan0 lladdr 00:00:5e:00:02:80 router REACHABLE > dooku-[~] mcr 10101 %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=12.9 ms > 64 bytes from fe80::128:1: icmp_seq=2 ttl=64 time=1.56 ms > ^C > dooku-[~] mcr 10099 %sudo rdisc6 wlan0 > [sudo] password for mcr: > Soliciting ff02::2 (ff02::2) on wlan0... > Hop limit : 64 ( 0x40) > Stateful address conf. : No > Stateful other conf. : Yes > Router preference : medium > Router lifetime : 600 (0x00000258) seconds > Reachable time : unspecified (0x00000000) > Retransmit time : unspecified (0x00000000) > Source link-layer address: 00:00:5E:00:02:80 > Recursive DNS server : 2001:67c:370:229::6 > Recursive DNS server : 2001:67c:370:229::7 > DNS servers lifetime : 1800 (0x00000708) seconds > Prefix : 2001:67c:370:128::/64 > Valid time : 2592000 (0x00278d00) seconds > Pref. time : 604800 (0x00093a80) seconds > from fe80::128:1 > dooku-[~] mcr 10100 %iwconfig wlan0 > wlan0 IEEE 802.11 ESSID:"ietf-legacy" > Mode:Managed Frequency:5.22 GHz Access Point: FC:5B:39:53:D5:EF > Bit Rate=6 Mb/s Tx-Power=15 dBm > Retry short limit:7 RTS thr:off Fragment thr:off > Power Management:off > Link Quality=63/70 Signal level=-47 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:1 Invalid misc:19 Missed beacon:0 > -- > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works > -= IPv6 IoT consulting =- -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
Attachments (1)
Change history (6)
Changed 4 years ago by
Attachment: | signature.asc added |
---|
comment:1 Changed 4 years ago by
Component: | incoming → network |
---|---|
Owner: | changed from llynch@… to creilly@… |
Status: | new → assigned |
Type: | request → defect |
comment:2 Changed 4 years ago by
Priority: | tbd → minor |
---|
Michael,
Sorry you are experiencing some issues. We are not seeing any issues at this time with v6 from the Wired LAN or Wireless. If you wouldn't mind stoping by the NoC in Studio 5 when you have a free moment, we can troubleshoot your issue further. It may be something specific to your device.
Thank you for your patience.
-Con
comment:3 Changed 4 years ago by
Resolution: | → worksforme |
---|---|
Status: | assigned → closed |
comment:4 Changed 4 years ago by
Just spoke with Michael in the NoC, he was able to un-stuck his Linux Laptop. We asked him to report the issue should it persist, we would then dig deeper into the logs on his laptop.
-Con
Note: See TracTickets for help on using tickets.
Added by email2trac