Fetching package: connection reset by peer

[float]

Yes, dns resolver

[DaddyGo]

@float
and....????

[float]

These are my servers:

[DaddyGo]

@float

unnecessary so many DNS servers
and by that you throw your privacy

is IPv6 important to you?
it’s not really time yet, so

++++edit:
it won’t make life faster just tell more everyone what you want to know

++++edit2:
DoT and DNSSEC are very important towards CloudFlare (1.1.1.1 / 1.0.0.1)

like:

[Rico]

What's not to understand about plain VANILLA for testing?

-Rico

[float]

@DaddyGo Yes, I know. I was testing with multiple DNS server, but the error stays the same "no response" from IPv4 dns server. I"ll reinstall tomorrow :-)

[DaddyGo]

@Rico said in Fetching package: connection reset by peer:

What's not to understand about plain VANILLA for testing?

Huuu, but confident
We're not talking about anymore, my friend Rico ...
Also read a little above

[DaddyGo]

@float said in Fetching package: connection reset by peer:

I"ll reinstall tomorrow :-)

I look forward to your feedback

[stephenw10]

Mmm, must be something specific to you. I can install fine to a 7100 here:

[2.4.5-RELEASE][admin@7100.stevew.lan]/root: pkg -d install whois
DBG(1)[57064]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[57064]> PkgRepo: verifying update for pfSense-core
DBG(1)[57064]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[57064]> Fetch: fetching from: https://files01.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-core/meta.conf with opts "i"
DBG(1)[57064]> Fetch: fetching from: https://files01.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-core/meta.txz with opts "i"
DBG(1)[57064]> Fetch: fetching from: https://files01.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-core/packagesite.txz with opts "i"
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
DBG(1)[57064]> PkgRepo: verifying update for pfSense
DBG(1)[57064]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[57064]> Fetch: fetching from: https://files01.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-pfSense_factory-v2_4_5/meta.conf with opts "i"
DBG(1)[57064]> Fetch: fetching from: https://files01.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-pfSense_factory-v2_4_5/meta.txz with opts "i"
DBG(1)[57064]> Fetch: fetching from: https://files01.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-pfSense_factory-v2_4_5/packagesite.txz with opts "i"
pfSense repository is up to date.
All repositories are up to date.
DBG(1)[57064]> want to get an advisory lock on a database
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	whois: 5.2.17 [pfSense]

Number of packages to be installed: 1

58 KiB to be downloaded.

Proceed with this action? [y/N]: y
DBG(1)[57064]> Fetch: fetching from: https://files01.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-pfSense_factory-v2_4_5/All/whois-5.2.17.txz with opts "i"
[1/1] Fetching whois-5.2.17.txz: 100%   58 KiB  59.1kB/s    00:01    
Checking integrity...DBG(1)[57064]> Binary> loading /var/cache/pkg/whois-5.2.17-e7a0f0313c.txz
DBG(1)[57064]> check integrity for 1 items added
 done (0 conflicting)
DBG(1)[57064]> want to upgrade advisory to exclusive lock
[1/1] Installing whois-5.2.17...
[1/1] Extracting whois-5.2.17: 100%
DBG(1)[57064]> release an exclusive lock on a database
DBG(1)[57064]> release an advisory lock on a database

Weird it's just that pkh though. You might have a corrupted version cached maybe?
Try: pkg-static clean

Steve

[float]

I tried to install the package again this morning (without reinstalling). No issues. The package installed.

The only issue remaining is the non response from the external DNS servers:

[stephenw10]

Probably this:
https://docs.netgate.com/pfsense/en/latest/install/upgrade-troubleshooting.html?highlight=pkg%20server#pkg-pfsense-org-has-no-a-aaaa-record

[float]

The problem occurs for every lookup.

Is this normal behavior because of this option:

[DaddyGo]

@float said in Fetching package: connection reset by peer:

Is this normal behavior because of this option:

Hmmmm sure

btw:
what does DNS lookup point to 1.1.1.1?

[float]

Option disabled:

Option enabled:

[stephenw10]

Mmm, no response from Cloudflare is not good. Not much we can do about that though. You don't have some conflicting route for 1.x.x.x somehow?

You should remove those servers if they are not giving you responses.

Steve

[DaddyGo]

@float

Ohhh....interesting
what packages are running? Snort or Suricata, pfBlockerNG ....?

[float]

All my IPv4 DNS-servers are not responding.

[DaddyGo]

@float said in Fetching package: connection reset by peer:

All my IPv4 DNS-servers are not responding.

because the Suricata
home NET / external NET

or pfBlockerNG blocks lists CloudFlare DNS IPs in a stupid way

[float]

The problem occurred before installing pfblocker.

Installed packages:

[DaddyGo]

@float said in Fetching package: connection reset by peer:

The problem occurred before installing pfblocker.

Temporarily stop all packages and PING out the box to 1.1.1.1