#1186 closed request (duplicate)

ietf-NAT64 no route

Reported by: lee@… Owned by: panda@…
Priority: tbd Milestone: ietf-100
Component: nat64 Keywords: nat64
Cc: Clemens, Schrimpe, <csch@…> My Current Location: Canning
My MAC Address: My OS:

Description

In Canning, 6man WG during no-ipv4 experiment. At first, took a long time to attach to ietf-nat64. A couple of minutes.
Then for a little while the name servers were unreachable. 2001:67c:370:229::7
2001:67c:370:229::6
Then it worked.

An hour later, I lost it again:
$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384

options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=1<PERFORMNUD>

gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

ether 60:c5:47:03:ac:bc
inet6 fe80::62c5:47ff:fe03:acbc%en0 prefixlen 64 scopeid 0x4
inet 169.254.254.15 netmask 0xffff0000 broadcast 169.254.255.255
inet6 2001:67c:370:1998:62c5:47ff:fe03:acbc prefixlen 64 autoconf
inet6 2001:67c:370:1998:c15:546f:c892:f5c3 prefixlen 64 autoconf temporary
nd6 options=1<PERFORMNUD>
media: autoselect
status: active

en1: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500

options=60<TSO4,TSO6>
ether b2:00:14:44:f6:e0
media: autoselect <full-duplex>
status: inactive

p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304

ether 02:c5:47:03:ac:bc
media: autoselect
status: inactive

bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 62:c5:47:30:76:00
Configuration:

id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2

member: en1 flags=3<LEARNING,DISCOVER>

ifmaxaddr 0 port 5 priority 0 path cost 0

nd6 options=1<PERFORMNUD>
media: <unknown type>
status: inactive

$ traceroute6 2001:67c:370:229::7
connect: No route to host

Still had the same two name servers configured, but couldn't reach them.
Switched to ietf-v6ONLY and I have access again.

Change history (2)

comment:1 Changed 11 months ago by llynch@…

Cc: Clemens Schrimpe <csch@…> added
Component: incomingnat64
Owner: changed from llynch@… to panda@…
Status: newassigned

Thanks for trying the NAT64 network (SSID ietf-nat64) and reporting
your experience. As far as we can tell, the issue you reported is
either an issue of the NAT64 implementation's handling of that
specific traffic or the given application vendor's implementation.
We're collecting all the issues that come up and will pass the
reports back to the vendor at the end of the week. Hopefully this
will lead to better implementations and greater functionality for
the next meeting. If you're curious about other known issues,
please see https://tickets.meeting.ietf.org/wiki/nat64

If you have additional input on this issue please update the ticket,
if you see new issues please open additional tickets.

Also see: https://tickets.meeting.ietf.org/wiki/nat64
for a list of known issues!

Thanks -

comment:2 Changed 11 months ago by jim@…

Resolution: duplicate
Status: assignedclosed

Lee, actually this looks to be an infrastructure or RF issue. It's being tracked in Ticket #1185, so I'll close this as a duplicate. We're working on it...

  • Jim
Note: See TracTickets for help on using tickets.