Custom query (937 matches)

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

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

I get an ipv6 address (2001:df8::16:ba8d:12ff:fe12:4a2e) but can't ping6 anything, including my default gateway (2604:8800:100:f8::1).

ipv4 works fine.