Custom query (816 matches)

Filters
 
or
 
  
 
Columns

Show under each result:


Results (55 - 57 of 816)

Ticket Resolution Summary Owner Reporter
#1159 wontfix ietf-nat64 gives IPv4 address conflict message panda@… brian.e.carpenter@…
Description

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

#1158 worksforme CRL unavailable on v6only panda@… lee@…
Description
When I connect to the ietf-NAT64 or ietf-v6ONLY SSID, I can't reach CRL
http://crl.startfieldtech.com/sfig2s1-64.crl.

Lee


#1157 fixed Network connectivity issue for network "ietf" con@… glen@…
Description

Lisa Winkler, an AMS staff person, working on a late-model Macbook on site, has been unable to retrieve mail from our corporate IMAP server.

Her computer was connected to network "ietf", and email checks were coming to us over IPV4. Connections were timing out and no mail was flowing.

Her iPhone was connected to network "ietf-hotel", and was able to check email with no problem (connections were over IPV6).

Her Mac was unable to connect to network "ietf-hotel", but *was* able to connect to network "ietf-legacy". Thus connected, she is now able to pull email with no problem (connections are also over IPV6).

She may not be available for troubleshooting, but I was asked to report this inasmuch as it may happen to others and may indicate a problem on the main "ietf" network.

Thanks and best regards to you all! Glen

Note: See TracQuery for help on using queries.