Fetching package: connection reset by peer
-
Probably this:
https://docs.netgate.com/pfsense/en/latest/install/upgrade-troubleshooting.html?highlight=pkg%20server#pkg-pfsense-org-has-no-a-aaaa-record -
The problem occurs for every lookup.
Is this normal behavior because of this option:
-
@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?
-
Option disabled:
Option enabled:
-
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
-
Ohhh....interesting
what packages are running? Snort or Suricata, pfBlockerNG ....? -
All my IPv4 DNS-servers are not responding.
-
@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
-
The problem occurred before installing pfblocker.
Installed packages:
-
@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
-
Are you even using those? Unbound running in forwarding mode?
-
Yes in forward mode - I have no issues on the network clients - everything is resolved by pfsense
-
Cats bury it so they can't see it!
(You know what I mean if you have a cat) -
Yes, I changed them 5 minutes ago to test and take a screenshot
Do you mean that the no response is normal in "dns lookup" because they have to use port 853 and not the standard port 53? -
TRY:
DNS hostname - cloudflare-dns.com -
@float said in Fetching package: connection reset by peer:
because they have to use port 853 and not the standard port 53?
BINGO
-
Ok, thanks. So I don't have to worry about the "dns lookup" saying no response?
-
@float said in Fetching package: connection reset by peer:
dns lookup" saying no response?
but yes and it's getting weirder
-
No that not OK. All of those servers should respond to DoT queries.
If you have a host name there it must match as it will be used for verification. But you don't need to have one.
Steve
-
Try something, really just optional
DNS hostname - cloudflare-dns.com
