On Wed, May 14, 2008 at 2:02 PM, Cameron Dale <[EMAIL PROTECTED]> wrote:
> On 5/14/08, Chris Lawrence <[EMAIL PROTECTED]> wrote:
>> For the moment, I've done a manual hack to HTTPServer.py (adding
>> addr.startswith('192.168.') to the IP permission check) to allow local
>> IP addresses behind my firewall to download Packages files, but it
>> would be nice to have a configurable option in apt-p2p.conf that
>> includes a list/netmask/wildcard/something of permissible addresses
>> (as was the case for debtorrent).
>
> Thanks for the suggestion. This option had occurred to me before, but
> there are issues that prevent me from implementing it, so the
> inclusion of only the localhost address was intentional.
>
> The main reason is the obtaining of hashes from downloaded Packages
> files uses python-apt, which requires knowledge of the architecture.
> You may experience problems with the finding of hashes because of
> this, especially if you have multiple architectures accessing apt-p2p
> on the same host. However you may not have any problems, in which case
> please let me know and I'll consider adding the option.
>
> Because I excluded proxy functionality, I'm also not sure what will
> happen if multiple requests come in to apt-p2p at the same time from
> different hosts. Again there may be problems, there may not. Adding
> support for multiple concurrent connections would also be the hardest
> part of implementing this (otherwise simple) option.
>
>> The functions for IP checks in the
>> python-ipy package might be helpful in this regard.
>
> Thanks for the tip, I wasn't aware of that package, and it looks really
> useful.
I haven't had any trouble using apt-p2p (on an unstable amd64 box)
from my MacBook that runs testing i386 in Parallels, but I hadn't
really investigated whether it was doing peer downloads or mirror
downloads for those packages. It's entirely possible it's making
apt-p2p deeply confused.
The simultaneity issue might be problematic, though; I don't think
I've tried both at the same time.
Chris
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
