Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#171 closed defect (fixed)

IPv6 is broken on ietf-portal SSID

Reported by: morrowc@… Owned by: kemp@…
Priority: critical Milestone:
Component: portal Keywords: ipv6, wireless, portal
Cc: My Current Location: Athens/IDR
My MAC Address: My OS:

Description

It seems that (from some simple testing/attempts to get on the portal network) that:
o portal network is receiving AAAA dns responses
o portal network has RA/ipv6 addressing active
o ipv6 is actually active (to local resources, portal/noc.meeting.ietf.org)
o ipv6 connections to tcp/80 && tcp/443 is firewalled/broken

This means that the portal page is broken unless you tell firefox (or other browser) to NOT use ipv6. This seems like a fail for the ietf :(

-chris

Change history (5)

comment:1 Changed 8 years ago by llynch@…

Component: wirelessportal
Owner: changed from chelliot@… to kemp@…
Status: newassigned

John -

I think this falls into your bucket.

  • Lucy

comment:2 Changed 8 years ago by kemp@…

Status: assignedaccepted

comment:3 Changed 8 years ago by kemp@…

Resolution: fixed
Status: acceptedclosed

Known behavior. We require people to auth-by-v4 webpage.
If you go to: http://www.google.com/, that should get you going.
Thank you for the notification. We should try to fix this issue
in the next rev/generation.

  • John

comment:4 in reply to:  3 Changed 8 years ago by anonymous

Replying to kemp@ns.uoregon.edu:

Known behavior. We require people to auth-by-v4 webpage.

could your firewall send back some clue about this? hanging for multiple minutes on v6 failures just looks bad, the IETF really ought to be able to do this 'better' (or 'properly'). Also, how can the apache box NOT do v6? it's pingable over v6, perhaps at least redirect to a v4 only hostname?

If you go to: http://www.google.com/, that should get you going.

can't do this until you auth to the wireless right? so.. if I can't (without minutes delays for every part of the page) get auth'd I can't get to www.google.com either.

Thank you for the notification. We should try to fix this issue
in the next rev/generation.

ok... it's pretty badly broken now though.

-chris

  • John

comment:5 Changed 8 years ago by llynch@…

Milestone: IETF 79

Milestone IETF 79 deleted

Note: See TracTickets for help on using tickets.