search

NEAT-project / neat

A New, Evolutive API and Transport-Layer Architecture for the Internet
https://www.neat-project.org/
BSD 3-Clause "New" or "Revised" License
66 stars 19 forks source link

Happy eyeballs ipv6 vs Firefox #282

Open bagder opened 7 years ago

bagder commented 7 years ago

Using the test URL http://bsd10.fh-muenster.de/cgi-bin/he and running Firefox-NEAT on an dual-stack network (like for example the Mozilla Paris wifi), NEAT always[*] picks the IPv4 connection.

If I run a "normal" Firefox on the same network, it always[*] picks an IPv6 connection!

[*] = I've reloaded the page many times in both setups and it seems to pick the same one in a reproducible manner

perhurt commented 7 years ago

Is this an issue related to the implementation or just a policy issue? Does Firefox favour IPv6 over IPv4?

bozakov commented 6 years ago

For this scenario, is the Policy Manager running at all?

bagder commented 6 years ago

I used no policy manager when I spotted this behavior.

karlgrin commented 6 years ago

@naeemk should this be considered a bug that needs to be analyzed?

naeemk commented 6 years ago

@karlgrin: yes, I have put in to the hackaton agenda.

perhurt commented 6 years ago

When trying to recreate this, Firefox crashed right after startup. I can see in the debug information printed by NEAT that it opens a number of connections towards several mozilla sites, but crashes before I can interact with the browser.

This type of crash happens both with and without the policy manager enabled.

When building "NEATFox" I followed the instructions in NEAT.md (in bagder/gecko-dev NEAT2-branch) and used the master branch of NEAT. Is the procedure for building NEATFox still the same @bagder ?