Pkg tool needs some common sense?

chrcoluk

as dok stated that wouldnt have helped.

kpa

The problem comes from libfetch (it uses an imported version of the library) as far as I know. Libfetch has a global timeout that can be configured but no provisions for configuring a specific IPv6 -> IPv4 fallback timeout in case IPv6 connections are not working.

kpa

You can put this into /usr/local/etc/pkg.conf to force the use of just IPv4:


IP_VERSION=4

You can also disable autofetching of the repo catalogs on every operation.


REPO_AUTOUPDATE=NO

That might mess with the GUI updater though, use with care.

PiBa

There is also a 'prefer IPv4' checkbox in the system/advanced settings.. might be safer assuming it solves this..

luckman212

@kpa:

You can put this into /usr/local/etc/pkg.conf to force the use of just IPv4:
IP_VERSION=4
You can also disable autofetching of the repo catalogs on every operation.
REPO_AUTOUPDATE=NO
That might mess with the GUI updater though, use with care.

Maybe this should automatically be done by /etc/rc.bootup "just in case" and then removed after platform_booting is false? Or, try to do some simplye connectivity checks to whatever URL is specified in pfSense-repo.conf … e.g.

test to see if its DNS can be resolved and then
test if it's pingable

before trying to do anything whatsoever with remote pkg commands?

yon

yes, me too, ipv6 all down in v2.4.1, i have to back to 2.4.0 ok.

Guest

@yon:

yes, me too, ipv6 all down in v2.4.1, i have to back to 2.4.0 ok.

I must have two very strange systems running 2.4.1 then, IPv6 is working fine on both of them, one using statics and one using DHCP6.

doktornotor

@yon:

yes, me too, ipv6 all down in v2.4.1, i have to back to 2.4.0 ok.

This is NOT the thread for debugging your broken 12WAN setups. Kindly leave it alone.

Guest

Snigger… ;D

yon

@doktornotor:

@yon:

yes, me too, ipv6 all down in v2.4.1, i have to back to 2.4.0 ok.

This is NOT the thread for debugging your broken 12WAN setups. Kindly leave it alone.

Are there any rules to limit the number of use? Is this a child's toy? Not a professional tool？ ???
I would like any product to be tested in a complex and rigorous environment in order to find possible problems, rather than fear of problems and not dare to use.

Steve_B

No doubt you would like that for free, too?

Guest

@yon:

@doktornotor:

@yon:

yes, me too, ipv6 all down in v2.4.1, i have to back to 2.4.0 ok.

This is NOT the thread for debugging your broken 12WAN setups. Kindly leave it alone.

Are there any rules to limit the number of use? Is this a child's toy? Not a professional tool？ ???
I would like any product to be tested in a complex and rigorous environment in order to find possible problems, rather than fear of problems and not dare to use.

Perhaps your requirements need professional support, here's the link to enable you to purchase it. https://www.pfsense.org/get-support/

perlenbacher

At least that support will come without all the snipey comments and abuse. Probably a good buy…

chrcoluk

@kpa:

You can put this into /usr/local/etc/pkg.conf to force the use of just IPv4:
IP_VERSION=4
You can also disable autofetching of the repo catalogs on every operation.
REPO_AUTOUPDATE=NO
That might mess with the GUI updater though, use with care.

excellent thank you.

I will see if I can get someone to add options for this in the GUI.

chrcoluk

@yon:

yes, me too, ipv6 all down in v2.4.1, i have to back to 2.4.0 ok.

I dont blame blame 2.4.1 for the ipv6 issue, it was down to an exotic config I had in place, and was just coincidence this is the first time I have ran a restore with that config which broke ipv6.

My ipv6 has been fine since I fixed the config issue. I waited to fix it as was advised in the pfsense UI to not make any config changes with a config restore in process.

Guest

@chrcoluk:

@kpa:
You can put this into /usr/local/etc/pkg.conf to force the use of just IPv4:
IP_VERSION=4
You can also disable autofetching of the repo catalogs on every operation.
REPO_AUTOUPDATE=NO
That might mess with the GUI updater though, use with care.
excellent thank you.

I will see if I can get someone to add options for this in the GUI.

OK Chris, I've added the two you mentioned in the email, threw me a bit as they are ENV vars now, no longer in a conf file!

Do you or anyone else want other vars added, the two that shout at me are these:

FETCH_RETRY: integer
Number of times to retry a failed fetch of a file. Default:
3.

FETCH_TIMEOUT: integer
Maximum number of seconds to wait for any one file to down-
load from the network, either by SSH or any of the protocols
supported by fetch(3) functions. Default: 30.

chrcoluk

thanks bud, I will give it a whirl later today :)

Guest

@chrcoluk:

thanks bud, I will give it a whirl later today :)

Forget the package timout & retry, they are already set to 5 & 2 respectively in the code anyway.

doktornotor

@marjohn56:

@chrcoluk:

thanks bud, I will give it a whirl later today :)

Forget the package timout & retry, they are already set to 5 & 2 respectively in the code anyway.

Yeah that has no effect at all on anything.

Guest

@doktornotor:

@marjohn56:

@chrcoluk:

thanks bud, I will give it a whirl later today :)

Forget the package timout & retry, they are already set to 5 & 2 respectively in the code anyway.

Yeah that has no effect at all on anything.

Perhaps the two I've added will have some effect, at least the use v4 one might.