Native IPv6 client redirected to IPv4-only mirror
Bug #1595563 reported by
RoyK
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Raspbian |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
apt-get install <something> on a client with only IPv6 got redirected to a mirror with only IPv4, and apt failed. Quick-and-dirty "solution" was to use a proxy. I'm not sure what's best, to only add mirrors with both stacks, or to filter it somehow smarter, but it should definitely be solved.
roy
Changed in raspbian: | |
status: | New → Won't Fix |
To post a comment you must log in.
Unfortunately there are a couple of problems.
1. Mirrorbrain (the software behind mirrordirector. raspbian. org) has no option to mark mirrors as "ipv4 only".
2. Even if we could mark IPv4 only mirrors as such doing so would be a tradeoff. It would allow some v6-only clients to work that currently fail. On the other hand it is likely to mean that some dual-stack clients get sent to more distant mirrors. Pulling out v4-only mirrors completely seems even worse.
My general position is that currently a node that can only access v6 servers cannot be reasonablly considered to be "on the internet". Those wanting to run v6 only networks should consider deploying a NAT64/DNS64 gateway to allow access to v4 servers.
Another alternative is not to use mirrordirector. raspbian. org and instead to configure a mirror explicitly.