Fetching package: connection reset by peer

DaddyGo · Sep 12, 2020, 6:09 PM

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

Yes, no problem with other files.

This means that it is not just a DNS issue. (and access time)
Since, for example, I was able to install iperf perfectly with OP

float · Sep 12, 2020, 6:11 PM

[2.4.5-RELEASE][admin@]/root: fetch -v -o /dev/null https://firmware.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-pfSense_factory-v2_4_5/All/whois-5.2.17.txz
resolving server address: firmware.netgate.com:443
SSL options: 83004bff
Peer verification enabled
Using CA cert file: /usr/local/etc/ssl/cert.pem
Verify hostname
TLSv1.2 connection established using ECDHE-RSA-AES256-GCM-SHA384
Certificate subject: /OU=Domain Control Validated/OU=PositiveSSL Wildcard/CN=.netgate.com
Certificate issuer: /C=GB/ST=Greater Manchester/L=Salford/O=Sectigo Limited/CN=Sectigo RSA Domain Validation Secure Server CA
requesting https://firmware.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-pfSense_factory-v2_4_5/All/whois-5.2.17.txz
remote size / mtime: 59136 / 1580490860
/dev/null 82% of 57 kB 595 Bps 17s
fetch: https://firmware.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-pfSense_factory-v2_4_5/All/whois-5.2.17.txz: Connection reset by peer

And no issue with another package:
[2.4.5-RELEASE][admin@]/root: fetch -v -o /dev/null https://firmware.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-pfSense_factory-v2_4_5/All/arm-none-eabi-gcc-6.4.0_7.txz
resolving server address: firmware.netgate.com:443
SSL options: 83004bff
Peer verification enabled
Using CA cert file: /usr/local/etc/ssl/cert.pem
Verify hostname
TLSv1.2 connection established using ECDHE-RSA-AES256-GCM-SHA384
Certificate subject: /OU=Domain Control Validated/OU=PositiveSSL Wildcard/CN=*.netgate.com
Certificate issuer: /C=GB/ST=Greater Manchester/L=Salford/O=Sectigo Limited/CN=Sectigo RSA Domain Validation Secure Server CA
requesting https://firmware.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-pfSense_factory-v2_4_5/All/arm-none-eabi-gcc-6.4.0_7.txz
remote size / mtime: 20132092 / 1580488881
/dev/null 19 MB 1164 kBps 17s

DaddyGo · Sep 12, 2020, 6:17 PM

is there any way (PC, MAC, Linux) to download the file behind pfSense?
you said you can access the download with a browser

float · Sep 12, 2020, 6:21 PM

Yes, the file is on my windows desktop. I can download it with my other freebsdserver too.

[@ ~]$ fetch -o /dev/null https://firmware.netgate.com/pkg/pfSense_factory-v2_4_5_amd64-pfSense_factory-v2_4_5/All/whois-5.2.17.txz
/dev/null 57 kB 304 kBps 00s

Rico · Sep 12, 2020, 6:28 PM

I'd try to reinstall pfSense and check again vanilla with fetch from the local console.

-Rico

DaddyGo · Sep 12, 2020, 6:29 PM

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

Yes, the file is on my windows desktop. I can download it with my other freebsdserver too.

Well, then the package is passed trough on pfSense, ergo something happens in the XG-7100

when, the box want to install the package on your own

DaddyGo · Sep 12, 2020, 6:33 PM

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

I'd try to reinstall pfSense and check again vanilla with fetch from the local console.

that is exactly what I would do

+++edit:
you have a factory snapshot of the XG-7100

float · Sep 12, 2020, 6:37 PM

Ok, i'll reinstall. The other thing that is quite weird is that none of the IPV4 DNS-servers are responding, but all the IPV6 are.

DaddyGo · Sep 12, 2020, 6:38 PM

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

none of the IPV4 DNS-servers are responding,

that's what I saw too

DaddyGo · Sep 12, 2020, 6:39 PM

@float

what do you use, Unbound?

float · Sep 12, 2020, 6:39 PM

Yes, dns resolver

DaddyGo · Sep 12, 2020, 6:41 PM

@float
and....????

float · Sep 12, 2020, 6:42 PM

These are my servers:

DaddyGo · Sep 12, 2020, 6:48 PM

@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 · Sep 12, 2020, 6:53 PM

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

-Rico

float · Sep 12, 2020, 6:55 PM

@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 · Sep 13, 2020, 1:28 PM

@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 · Sep 12, 2020, 6:58 PM

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

I"ll reinstall tomorrow :-)

I look forward to your feedback

stephenw10 · Sep 12, 2020, 8:40 PM

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 · Sep 13, 2020, 5:21 AM

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: