Open Bug 1666557 Opened 8 months ago Updated 8 months ago

TRR NAT64 prefixing should work in the separate Socket Process

Categories

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

enhancement

Tracking

()

People

(Reporter: mcccs, Unassigned)

References

(Blocks 3 open bugs)

Details

(Whiteboard: [necko-triaged])

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]
You need to log in before you can comment on or make changes to this bug.