Ivan Shmakov
2015-01-17 08:40:40 UTC
Back in June, Iâve had a use case for Polipo to bind to an
explicit address when doing outgoing connections. Iâve
ended up implementing the feature with the patch MIMEd.
Unfortunately, around that time the Git repository [1] (which
still seem to be described as the primary one at [2]) went down,
leaving me unable to check if my changeâs still needed, and I
dropped the case.
Now that Iâve fetched the recent Git history from [3] (where the
development has seem to be moved since) I see that with
2e2d55d6b391 (which dates back to November), support for a
similar âproxyOutgoingAddressâ option was added to the code.
Sadly, this new option would be unsuitable for my needs, as it
provides no support for IPv6, /and/ it provides no support for
specifying several possible addresses to bind to. (Which is a
natural prerequisite for an ambivalent application, as in
dual-stack environments, it needs at least /two/ addresses â the
IPv6 one and the IPv4 one â to try to bind to.)
I have no spare time right now to try and suggest a patch to
merge the IPv6 and multiple addresses support to the current
Polipo, but still provide my patch for any interested party to
consider.
TIA.
[1] git://git.wifi.pps.univ-paris-diderot.fr/polipo
[2] http://www.pps.univ-paris-diderot.fr/~jch/software/polipo/
[3] git://github.com/jech/polipo.git
explicit address when doing outgoing connections. Iâve
ended up implementing the feature with the patch MIMEd.
Unfortunately, around that time the Git repository [1] (which
still seem to be described as the primary one at [2]) went down,
leaving me unable to check if my changeâs still needed, and I
dropped the case.
Now that Iâve fetched the recent Git history from [3] (where the
development has seem to be moved since) I see that with
2e2d55d6b391 (which dates back to November), support for a
similar âproxyOutgoingAddressâ option was added to the code.
Sadly, this new option would be unsuitable for my needs, as it
provides no support for IPv6, /and/ it provides no support for
specifying several possible addresses to bind to. (Which is a
natural prerequisite for an ambivalent application, as in
dual-stack environments, it needs at least /two/ addresses â the
IPv6 one and the IPv4 one â to try to bind to.)
I have no spare time right now to try and suggest a patch to
merge the IPv6 and multiple addresses support to the current
Polipo, but still provide my patch for any interested party to
consider.
TIA.
[1] git://git.wifi.pps.univ-paris-diderot.fr/polipo
[2] http://www.pps.univ-paris-diderot.fr/~jch/software/polipo/
[3] git://github.com/jech/polipo.git
--
FSF associate member #7257 http://boycottsystemd.org/ ⊠3013 B6A0 230E 334A
FSF associate member #7257 http://boycottsystemd.org/ ⊠3013 B6A0 230E 334A