Custom query (937 matches)

On ​http://dashboard.meeting.ietf.org I see the ietf-v6ONLY SSID's number card, but in the graph itself I only see these SSIDs

• ietf
• ietf-legacy105
• eduroam
• ietf-2.4ONLY
• ietf-nat64
• manage

At first I thought maybe it's listing the top 6 SSIDs, but that doesn't make sense because ietf-v6ONLY has more connections than manage (at least right now).

So maybe ietf-v6ONLY was just omitted from the graph unintentionally? If so, could we add it?

I get these DNS servers: 2001:67c:370:229::7 2001:67c:370:229::6

But the don't seem to be doing DNS64, thereby rendering the NAT64 service a little hard to use:

h:NAT64 otroan$ host -t aaaa ipv4only.arpa 2001:67c:370:229::7 Using domain server: Name: 2001:67c:370:229::7 Address: 2001:67c:370:229::7#53 Aliases:

ipv4only.arpa has no AAAA record h:NAT64 otroan$

A bit odd this. When I connect to ietf-nat64, Windows 7 shows up an IPv4 address conflict... IPv6 seems to work though, but I haven't spent much time looking for NAT64 issues yet.

Screen shot of the error msg attached. FYI here's what Windows believes:

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : meeting.ietf.org Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6230 Physical Address. . . . . . . . . : 88-53-2E-B9-56-22 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:67c:370:1998:28cc:dc4c:9703:6781(Preferred) Link-local IPv6 Address . . . . . : fe80::28cc:dc4c:9703:6781%12(Preferred) Autoconfiguration IPv4 Address. . : 169.254.103.129(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : fe80::1998:1%12 DHCPv6 IAID . . . . . . . . . . . : 310924078 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-3B-A2-69-E8-03-9A-3C-67-7A 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