Wireshark-dev: Re: [Wireshark-dev] Menagerie
From: Dario Lombardo <dario.lombardo.ml@xxxxxxxxx>
Date: Fri, 27 Feb 2015 15:22:39 +0100
The size is not huge. Why not just host it on the wireshark main site? Torrent is amazing, but I think it is needed only when the size is really huge.

On Fri, Feb 27, 2015 at 3:17 PM, Evan Huus <eapache@xxxxxxxxx> wrote:
1.8 GB

I think it's a routing problem, not a torrent problem, I probably need
to open a hole in my firewall or something. I'm at work now anyways,
so I'll look at it again tonight unless somebody beats me to it.

Evan

On Fri, Feb 27, 2015 at 9:07 AM, Dario Lombardo
<dario.lombardo.ml@xxxxxxxxx> wrote:
> Should be supported by your torrent client (maybe create torrent or
> something). Once you succeded, send us the torrent.
> How large it is?
>
> On Fri, Feb 27, 2015 at 2:42 PM, Evan Huus <eapache@xxxxxxxxx> wrote:
>>
>> Although it seems it's not working for me to download on my laptop - I
>> need to figure out how to properly create/host/seed a torrent I
>> guess...
>>
>> Evan
>>
>> On Fri, Feb 27, 2015 at 8:26 AM, Evan Huus <eapache@xxxxxxxxx> wrote:
>> > I have a local copy that I grabbed by logging into the host server -
>> > I've created a torrent of it (attached) which I am currently seeding,
>> > so you should be able to grab it from me (and if you do, please seed
>> > to others in return!).
>> >
>> > Gerald hopefully this is OK, as far as I know all of the relevant
>> > captures are publicly available on Bugzilla or the wiki anyways.
>> >
>> > Evan
>> >
>> > P.S. This is a snapshot of the menagerie as of today, of course.
>> >
>> > On Fri, Feb 27, 2015 at 8:00 AM, Dario Lombardo
>> > <dario.lombardo.ml@xxxxxxxxx> wrote:
>> >> On Fri, Feb 27, 2015 at 1:55 PM, Evan Huus <eapache@xxxxxxxxx> wrote:
>> >>>
>> >>>
>> >>> I'm not sure if there is a more convenient way to download the entire
>> >>> menagerie available to the general public.
>> >>
>> >>
>> >> Who can know that? Gerald maybe? It would be very useful when
>> >> conducting
>> >> large scale tests to have access to a local copy of them, just like the
>> >> buildbot.
>> >>
>> >>
>> >> ___________________________________________________________________________
>> >> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
>> >> Archives:    http://www.wireshark.org/lists/wireshark-dev
>> >> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>> >>
>> >> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>>
>> ___________________________________________________________________________
>> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
>> Archives:    http://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>>
>> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>
>
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe