Fetching package: connection reset by peer
-
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"?
-
For me, the first is to configure the network interfaces and I don't care about the default config...
So I haven't even dealt with it yet
btw:
The pfSense DNS system is atom safe and works very well -
Mmm, listening for queries on 'all' should not be a problem. That's the default setting as you say.
Queries cannot actually come into WAN unless you have added rules to allow it.Steve
-
It started working after I changed those settings and unbound restarted. This was the only option that changed.
