Closed Bug 807989 Opened 12 years ago Closed 12 years ago

IPv6 some parts of Mozilla service don't work over IPv6 tunnel

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task, P5)

x86_64
Linux

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mcepl, Assigned: nmaul)

Details

(Whiteboard: [triaged 20121109])

Attachments

(1 file)

When having computer connected to IPv6 via tunnel by Hurrican Electric (see the attached setup script run through NetworkManager script) various services (especially all POST commands) stopped working.

Particularly:
- it was not possible to login to BMO ... after either going through Persona ID login or using normal login/password combination I've got "The connection was reset" error
- upload of new version of extension (e.g., on https://addons.mozilla.org/cs/developers/addon/deduplicate-tabs/versions#version-upload) stalls. There is no error anywhere, but after downloading either 0% or 8% (not more) of the extension, there is no more progress.

When the IPv6 tunnel is removed, everything works flawlessly.
Not Services; over the wall wi' ye!
Assignee: nobody → server-ops-webops
Component: General → Server Operations: Web Operations
Product: Mozilla Services → mozilla.org
QA Contact: nmaul
Version: unspecified → other
Assignee: server-ops-webops → nmaul
Priority: -- → P5
Whiteboard: [triaged 20121109]
CC'ing a couple relevant folks for AMO... oremj / clouserw, any ideas on why new addon uploads would not work over IPv6? Perhaps something in the app expects a v4 address and is confused otherwise?


I tested the BMO login issue with my Hurricane Electric tunnel up and running, and I can log in just fine using either Persona or the normal login system. It's been a while since you filed this bug (sorry), perhaps something has changed that I'm not aware of... is this working for you now? If not, would it be possible for you to include a tcpdump of the exchange?

justdave: any thoughts on BMO + IPv6?



PS: I use that add-on myself... love it, thanks!
I have IPv6 at home, and things seem to be working fine for me, and I do appear to be using IPv6 to reach it.
I see your setup script doesn't set an MTU size for the tunnel...  offen when you're using a tunnel, there is a little bit of packet overhead related to the tunnel encapsulation, and you need to substract that overhead off the MTU size of the packets you'll be sending through it.  Linux by default uses 1500 for the MTU.  Depending on the type of tunneling you're using, you probably need to set it to either 1492 or 1480 on the tunnel interface.
I think there was something wrong with my IPv6 tunnel setup. This default Hurrican Electric setup script doesn’t work correctly over NATed IPv4 connection. I have switched to SixXS and aiccu, and now everything works smoothly.

Sorry, for bothering you.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: