Custom query (1016 matches)
Results (163 - 165 of 1016)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1239 | fixed | ipv6 wonkiness | ||
Description |
howdy! I noticed that i can't ping (ipv6 ping) a bunch of things like: ~$ ping ipv6.google.com PING ipv6.google.com(sin10s02-in-x0e.1e100.net (2404:6800:4003:80d::200e)) 56 data bytes ^C --- ipv6.google.com ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1020ms $ ping www.google.com PING www.google.com(sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004)) 56 data bytes ^C --- www.google.com ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2028ms $ ping mailserver.ops-netman.net PING mailserver.ops-netman.net(mail-v6.ops-netman.net (2606:700:e:550:b00b::b00b)) 56 data bytes ^C --- mailserver.ops-netman.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1002ms I thought (until the third item) that this was my fault ... but! I think it's not (at least not for the reason I originally thought)... I also can't connect over ipv6 to services which SHOULD be running, like: $ telnet ipv6.google.com 443 Trying 2404:6800:4003:80d::200e... ^C $ telnet www.google.com 443 Trying 2404:6800:4003:80d::2004... ^C $ telnet mailserver.ops-netman.net 22 Trying 2606:700:e:550:b00b::b00b... ^C I CAN connect to these from a point not on the current IETF network: $ telnet mailserver.ops-netman.net 22 Trying 2606:700:e:550:b00b::b00b... Connected to mailserver.ops-netman.net. Escape character is '^]'. SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.10 morrowc@mailserver:~$ telnet 2404:6800:4003:80d::200e 443 Trying 2404:6800:4003:80d::200e... Connected to 2404:6800:4003:80d::200e. Escape character is '^]'. ^C etc... I'm currently connected like: wlp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 31.133.150.204 netmask 255.255.240.0 broadcast 31.133.159.255 inet6 2001:67c:1232:144:b9ed:17ed:ae56:8b13 prefixlen 64 scopeid 0x0<global> inet6 fe80::62c4:fd66:ec98:d73 prefixlen 64 scopeid 0x20<link> ether f8:59:71:bc:c5:8c txqueuelen 1000 (Ethernet) RX packets 31475690 bytes 39753655118 (37.0 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 8273253 bytes 3693695699 (3.4 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 morrowc@morrowc-glaptop2:~$ iw wlp4s0 link Connected to 74:3e:2b:fd:a9:c8 (on wlp4s0) SSID: ietf-hotel freq: 2412 RX: 22645257 bytes (76760 packets) TX: 5949851 bytes (12409 packets) signal: -62 dBm tx bitrate: 130.0 MBit/s MCS 14 short GI bss flags: short-preamble short-slot-time dtim period: 1 beacon int: 100 |
|||
#1187 | pending | ipv6 temp address rotation(?) on win10 breaks long-lived connections | ||
Description |
Hello, My problem probably isn't due to the ietf-nat64 network, as I've seen this happen in other v6 enabled networks as well, but here goes anyway as a FYI: I'm using the ietf-nat64 wifi with a Windows 10 (1709 update) client and my long-lived v6-tcp connections like ssh (putty client with keepalive set) tend to hang after some time. This has also happened to me reguarly on earlier versions of Windwows. For the hangup to occur it usually takes between tens of minutes to about an hour or two. After I login to the same host again, I see the v6 address I'm coming from has changed from the previous address. So it looks like windows, for some reason or another, is disabling the old temp v6 addresses while there still are tcp connections open. It should not work like this, but I guess it could just be a feature in windows. Other than long-lived tcp connections breaking for me, the nat64 network seems to be working fine. Maybe you could switch within the next couple of meetings to a v6 / nat64 mode on the default "ietf" network and provide native v4 only on a non-default ssid. Here's an excerpt from an ipv6 enabled server log (timestamps utc+2): Nov 14 07:31:47 rerun sshd[29389]: Accepted publickey for oh2kku from 2001:67c:370:1998:e0f2:6c45:5267:eccb port 49682 ssh2 Nov 14 07:43:16 rerun sshd[29464]: Accepted publickey for oh2kku from 2001:67c:370:1998:e0f2:6c45:5267:eccb port 49271 ssh2 Nov 14 08:01:32 rerun sshd[29600]: Accepted publickey for oh2kku from 2001:67c:370:1998:f8f8:3610:14ed:9171 port 49309 ssh2 Nov 14 09:50:38 rerun sshd[29996]: Accepted publickey for oh2kku from 2001:67c:370:1998:f8f8:3610:14ed:9171 port 63756 ssh2 Nov 14 10:21:35 rerun sshd[30090]: Accepted publickey for oh2kku from 2001:67c:370:1998:b8f2:7bcf:5b90:7771 port 57115 ssh2 Nov 14 11:00:14 rerun sshd[30214]: Accepted publickey for oh2kku from 2001:67c:370:1998:c834:4990:2112:ba9b port 55005 ssh2 This is from a v4-only server log, probably only the second last line was from a connection terminated due to address change: 2017-11-14T07:51:40.270398+02:00 woodstock sshd[28904]: Accepted publickey for oh2kku from 31.130.238.245 port 49279 ssh2 2017-11-14T10:34:23.665509+02:00 woodstock sshd[3739]: Accepted publickey for oh2kku from 31.130.238.174 port 53071 ssh2 2017-11-14T10:55:40.395275+02:00 woodstock sshd[4780]: Accepted publickey for oh2kku from 31.130.238.126 port 49939 ssh2 2017-11-14T11:13:12.825515+02:00 woodstock sshd[5609]: Accepted publickey for oh2kku from 31.130.238.126 port 55528 ssh2 This is what "ipconfig /all" on windows said a moment ago: Wireless LAN adapter Wi-Fi: Connection-specific DNS Suffix . : meeting.ietf.org Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 7265 Physical Address. . . . . . . . . : 10-02-B5-92-63-05 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:67c:370:1998:a002:1880:27bb:f006(Preferred) Temporary IPv6 Address. . . . . . : 2001:67c:370:1998:c834:4990:2112:ba9b(Preferred) Link-local IPv6 Address . . . . . : fe80::a002:1880:27bb:f006%10(Preferred) Autoconfiguration IPv4 Address. . : 169.254.240.6(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : fe80::1998:1%10 DHCPv6 IAID . . . . . . . . . . . : 168821429 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-F1-DE-FB-10-02-B5-92-63-05 DNS Servers . . . . . . . . . . . : 2001:67c:370:229::7 2001:67c:370:229::6 NetBIOS over Tcpip. . . . . . . . : Enabled Connection-specific DNS Suffix Search List : meeting.ietf.org Tapio |
|||
#537 | fixed | ipv6 routing up yet? | ||
Description |
I'm sitting in my hotel room, using the wired Ethernet connectivity which apparently comes from the IETF right now, unless the hotel offers me IPv6 addresses... But there doesn't appear to be IPv6 connectivity. You probably knew this, and are building the network as we speak. But just in case you didn't I'm reporting it... root@dummy:/home/jar/LME/HORD/hord-main# ping6 www.kame.net PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes From rtra.meeting.ietf.org icmp_seq=5 Destination unreachable: No route From rtra.meeting.ietf.org icmp_seq=6 Destination unreachable: No route From rtra.meeting.ietf.org icmp_seq=7 Destination unreachable: No route root@dummy:/home/jar/LME/HORD/hord-main# ping6 www.google.com PING www.google.com(sea09s02-in-x10.1e100.net) 56 data bytes From rtra.meeting.ietf.org icmp_seq=1 Destination unreachable: No route From rtra.meeting.ietf.org icmp_seq=2 Destination unreachable: No route From rtra.meeting.ietf.org icmp_seq=3 Destination unreachable: No route ^C --- www.google.com ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2003ms root@dummy:/home/jar/LME/HORD/hord-main# ping6 www.ietf.org PING www.ietf.org(mail.ietf.org) 56 data bytes From 2001:df8:0:4::3 icmp_seq=1 Time exceeded: Hop limit From 2001:df8:0:4::3 icmp_seq=2 Time exceeded: Hop limit From 2001:df8:0:4::3 icmp_seq=3 Time exceeded: Hop limit root@dummy:/home/jar/LME/HORD/hord-main# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:24:be:80:4f:f1 inet addr:130.129.68.97 Bcast:130.129.71.255 Mask:255.255.248.0 inet6 addr: 2001:df8:0:64:224:beff:fe80:4ff1/64 Scope:Global inet6 addr: fe80::224:beff:fe80:4ff1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:786604 errors:0 dropped:0 overruns:0 frame:0 TX packets:259325 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:420504180 (420.5 MB) TX bytes:43691060 (43.6 MB) Interrupt:16 Jari |
Note: See TracQuery for help on using queries.