Fetching package: connection reset by peer
-
@float said in Fetching package: connection reset by peer:
and inside pfSense? (nslookup)
-
[2.4.5-RELEASE][admin@]/root: nslookup www.facebook.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53Non-authoritative answer:
www.facebook.com canonical name = star-mini.c10r.facebook.com.
Name: star-mini.c10r.facebook.com
Address: 157.240.210.35
Name: star-mini.c10r.facebook.com
Address: 2a03:2880:f121:83:face:b00c:0:25de -
Okay, if you like 8.8.8.8
just a little plus, you might want to disable 53 if you only want to use DoT
and point all DNS requests to pfSense (manualy or DHCP)
try to use only static entries (DHCP) and uncheck it, this
oh and get ready for the new craziness DoH
-
Thank you. Everything is working as it should, only pfsense is being funny, right?
-
@float said in Fetching package: connection reset by peer:
pfsense is being funny, right?
The deeper you dive into it, the more funny it will be.
You'll see how serious the stuff is.
RED circle 18 - Caution this is addictive -
I reinstalled pfsense from the install image of netgate. Same issue. All the DNS-servers return "no response" on the firewall (no changes made on the settings). Nice extra problem: none of the clients can contact the dns servers, so they don't have any internet...
-
After your restored your config I assume? The default install resolves as expected?
-
I didn't restore my config. Default install doesn't resolve.
-
@float said in Fetching package: connection reset by peer:
Default install doesn't resolve.
Can you only connect to your ISP's modem / router?
-
I can resolve any host on pfsense, but not on the clients after pfsense. Pfsense is making the connection with the modem.
-
@float said in Fetching package: connection reset by peer:
Pfsense is making the connection with the modem.
I was just wondering if you don't have some crazy ISP filtering ...
So,
Are the interfaces configured correctly in Unbound?
and
do clients' DNS point to pfSense?
-
Can you ping out from clients by IP?
Is Unbound actually running? Any errors in the resolver log?
Steve
-
Ok, I found the error. Selecting "ALL" in "Network interfaces" doesn't work, but when I select "LAN" and "localhost" it works.
-
@float said in Fetching package: connection reset by peer:
Sep 13 19:19:23 portal unbound: [50875:0] info: reply from <.> 1.0.0.1#853
That's not the default config, it's using DoT to cloudflare.
Does it resolve with the default config? Unbound resolving directly?
Steve
-
@float said in Fetching package: connection reset by peer:
"Network interfaces" doesn't work, but when I select "LAN" and "localhost" it works.
Hmmm
-
@DaddyGo Weird, I just put "ALL" again and now it works. I'll reinstall and try again.
@stephenw10 I'll reinstall and try again.
-
@float said in Fetching package: connection reset by peer:
I'll reinstall and try again.
No, no, Unbound has to restart, it's such an animal
-
I want to know if you actually have to click on "ALL" in order to make it work. Because after I changed it to "LAN" and "localhost" it worked.
-
Don't forget that "ALL" includes the WAN!
Unbound always restarts anyway, see DHCP leases or pfBlockerNG lists reload, etc -
Then that would be the cause of my error. Weird because the default install of pfsense is "all"?
