Opened 8 months ago

Closed 8 months ago

#1249 closed request (not broken)

nat64 in terminal room

Reported by: mcr@… Owned by: Clemens Schrimpe
Priority: tbd Milestone: ietf-103
Component: nat64 Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

I'm trying to live on the NAT64.
(Founda  few bugs in the rest of the Internet)

I'm in the terminal room this morning.
I'm not getting to github.com (IPv4 only):

% ping github.com
PING github.com(ec2-13-229-188-59.ap-southeast-1.compute.amazonaws.com (64:ff9b::de5:bc3b)) 56 data bytes
... no reply.

% ping www.google.com
PING www.google.com(sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004)) 56 data bytes
64 bytes from sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004): icmp_seq=1 ttl=54 time=31.4 ms
64 bytes from sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004): icmp_seq=2 ttl=54 time=31.8 ms

My dual-stack home desktop:
% ping obiwan.sandelman.ca
PING obiwan.sandelman.ca(obiwan.sandelman.ca (2607:f0b0:f:2::247)) 56 data bytes
64 bytes from obiwan.sandelman.ca (2607:f0b0:f:2::247): icmp_seq=1 ttl=46 time=367 ms

details for me.
I will live on this network for awhile until I find I need github :-)
Oh, that's now.

dooku-[~](system) mcr 10138 %ifconfig wlan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::a11:96ff:fe01:81e0  prefixlen 64  scopeid 0x20<link>
        inet6 2001:67c:370:1998:ac32:98c6:bc97:67a6  prefixlen 64  scopeid 0x0<global>
        inet6 2001:67c:370:1998:a11:96ff:fe01:81e0  prefixlen 64  scopeid 0x0<global>
        ether 08:11:96:01:81:e0  txqueuelen 1000  (Ethernet)
        RX packets 14359628  bytes 4726467908 (4.4 GiB)
        RX errors 0  dropped 64  overruns 0  frame 0
        TX packets 2683303  bytes 898675406 (857.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

dooku-[~](system) mcr 10139 %iwconfig wlan0
wlan0     IEEE 802.11  ESSID:"ietf-nat64"
          Mode:Managed  Frequency:5.24 GHz  Access Point: 38:90:A5:F6:30:2C
          Bit Rate=12 Mb/s   Tx-Power=15 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=68/70  Signal level=-42 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1  Invalid misc:10   Missed beacon:0

Change history (5)

comment:1 Changed 8 months ago by llynch@…

Component: incomingnat64
Owner: changed from < default > to Clemens Schrimpe
Status: newassigned

comment:2 in reply to:  2 ; Changed 8 months ago by mcr@…

Okay, so maybe the problem is subtler, of false.
Does github.com even accept ping packets, as I can't ping them on IPv4?
Looks like ssh actually works.


comment:3 Changed 8 months ago by jim@…

The understanding in the NOC is that the GitHub? instance in SE Asia is spun up on AWS infrastructure in Singapore. They recently (as in the last few days) stopped responding to pings, but otherwise was fully functional. In other words, it's not actually a functional failure. Does that match your understanding?

comment:4 in reply to:  4 ; Changed 8 months ago by mcr@…

IETF Tickets/NOC <tickets@meeting.ietf.org> wrote:
    > The understanding in the NOC is that the GitHub instance in SE Asia is
    > spun up on AWS infrastructure in Singapore. They recently (as in the last
    > few days) stopped responding to pings, but otherwise was fully functional.
    > In other words, it's not actually a functional failure. Does that match
    > your understanding?

yeah, it seems to.

comment:5 Changed 8 months ago by Clemens Schrimpe

Resolution: not broken
Status: assignedclosed

It is being translated correctly and it also traceroutes nicely. It is just the end system not replying to pings.
(tried with native IPv4 @ 13.229.188.59)

¯\_(ツ)_/¯

Note: See TracTickets for help on using tickets.