Closed Bug 1666557 Opened 2 years ago Closed 1 year ago

TRR NAT64 prefixing should work in the separate Socket Process

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
96 Branch
Tracking Status
firefox96 --- fixed

People

(Reporter: mcccs, Assigned: kershaw)

References

(Blocks 3 open bugs)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

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.

Blocks: doh, IPv6

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

Blocks: socket-proc
Severity: -- → S3
Status: UNCONFIRMED → NEW
Depends on: 1589781
Ever confirmed: true
Priority: -- → P3
Whiteboard: [necko-triaged]
Assignee: nobody → kershaw
Status: NEW → ASSIGNED
Pushed by kjang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8000eadc16ec
Make TRR NAT64 prefixing work with socket process, r=necko-reviewers,dragana

Backed out for causing hybrid bustages on TRRServiceChild.cpp

Flags: needinfo?(kershaw)
Pushed by kjang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e1252130916b
Make TRR NAT64 prefixing work with socket process, r=necko-reviewers,dragana
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch
You need to log in before you can comment on or make changes to this bug.