1666557 - TRR NAT64 prefixing should work in the separate Socket Process

Status: RESOLVED FIXED

(Core :: Networking: DNS, enhancement, P3)

Description

[mcccs]

The connectivity service doesn't run when network.http.network_access_on_socket_process.enabled. This bug is about fixing this for NAT64 TRR prefixing code.

When [the socket process is] enabled, all DNS resolutions are preformed in a different process, so the connectivity checker isn't in the same process, so we can't directly access the prefixes.

Comment 1

[Valentin Gosu [:valentin] (he/him)]

Basically what we need is to make netwerk/test/unit/test_trr_nat64.js pass with the socket process.

Comment 2

[Kershaw Chang [:kershaw]]

Attachment: Bug 1666557 - Make TRR NAT64 prefixing work with socket process, r=#necko

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/8000eadc16ec
Make TRR NAT64 prefixing work with socket process, r=necko-reviewers,dragana

Comment 4

[Cristian Tuns]

Backed out for causing hybrid bustages on TRRServiceChild.cpp

• Backout link
• Push with failures
• Failure Log

Comment 5

[Kershaw Chang [:kershaw]]

https://treeherder.mozilla.org/jobs?repo=try&revision=4aab6c6d6d63d102eef2d524b0a5323e42265e4e

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/e1252130916b
Make TRR NAT64 prefixing work with socket process, r=necko-reviewers,dragana

Comment 7

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/e1252130916b