dhcpcd-discuss

On Mon, 27 Apr 2020 at 19:51, Roy Marples <roy@xxxxxxxxxxxx> wrote:

> Hi Ben
>
> On 27/04/2020 07:30, Ben Woods wrote:
> > Hi Roy,
> >
> > I am having a few issues using the dhcpcd git repo, and I was hoping you
> could
> > help me diagnose them. I am unsure if these 2 issues are related or not.
> >
> > 1. Unable to download recent commit - file appears to be truncated (too
> small)
> >
> > $ curl -O
> > "
> https://roy.marples.name/cgit/dhcpcd.git/snapshot/dhcpcd-1e29ac03a30a4da556e1e9ad16af7b7872d6d7b0.tar.xz
> "
> >
> > $ ls -lah dhcpcd-1e29ac03a30a4da556e1e9ad16af7b7872d6d7b0.tar.xz
> > -rw-r--r--  1 woodsb02  wheel    48K 27 Apr 14:26
> > dhcpcd-1e29ac03a30a4da556e1e9ad16af7b7872d6d7b0.tar.xz
> >
> > $ tar xzf dhcpcd-1e29ac03a30a4da556e1e9ad16af7b7872d6d7b0.tar.xz
> > dhcpcd-1e29ac03a30a4da556e1e9ad16af7b7872d6d7b0/configure: Lzma library
> error:
> >   No progress is possible
> > tar: Error exit delayed from previous errors.
> >
>
> Try using J rather then z
>
> $ tar xJf dhcpcd-1e29ac03a30a4da556e1e9ad16af7b7872d6d7b0.tar.xz
>
> Works fine.
>

Good point on the "J", but its still not working for me. The downloaded
file is only 48 KB, but should be more like 244 KB.
I just spun up 3 VMs in different geographical areas and found the
difference:
Sydney, Australia - file size = 40662 bytes - extract fails
New Jersey, USA - file size = 81622 bytes - extract fails
Paris, France - file size = 244672 bytes - extract works fine

Is there a CDN at play here which is not syncing correctly?


> 2. Unable to clone git repo
> >
> > $ git clone git://roy.marples.name/dhcpcd.git <
> http://roy.marples.name/dhcpcd.git>
> > Cloning into 'dhcpcd'...
> > fatal: unable to connect to roy.marples.name <http://roy.marples.name>:
> > roy.marples.name <http://roy.marples.name>[0: 81.108.15.115]:
> errno=Connection
> > refused
>
> This is now resolved, thanks for the heads up.
>

Thanks - its working for me again now.


> roy.marples.name <http://roy.marples.name>[1: 2001:470:690c:1::61]:
> errno=No
> > route to host
>
> Hmmmm, how did that happen?
> I've re-uploaded a fixed DNS zone.
>

I think its my IPv6 setup being broken - please ignore that one :)

Thanks,
Ben