Avaliable Packages missing cant seem to find
-
john not sure how to set it to look at itself at 127.0.0.1 i know that's one of the rules or nat settings
and not sure what a dnssec root key is anywaysand i forget someone else was helping me before with nordvpn setup was that you john... here i thought nordvpn was a good company but i having issues …
go figure lol
and i unchecked the dns query forwarding
-
so hopefully that fixes it the unchecked query
if this all doesn't work does that mean there is a problem with the nordvpn servers?
-
@comet424 said in Avaliable Packages missing cant seem to find:
here i thought nordvpn was a good company but i having issues
The business model of all those VPN providers is based on FUD, so you can't call any of them "good". Some may even be worse than your actual ISP when it comes to collecting data.
-
ah ok.. ya i did it cuz of data collecting but mostly i sick and tired im in Canada and cant see Olympics time and i wanna see the usa footage and boom you cant geo location shit.. hate that crap lol and if i get Netflix apparently usa Netflix better then Canada content.. or anything really just frustrating.. i need to immigrant to usa lol
but what does FUD mean
so grimson you don't believe in vpns then i take it.. i just learning as i go teach myself and read etc try to make best educated guesses -
You need to uncheck
Do not use the DNS Forwarder/DNS Resolver as a DNS server for the firewallin System > General to have it use the resolver.
However you have the resolver in forwarding mode anyway so it too will be using those DNS servers defined there rather than the root servers.Steve
-
Which looks like it will be fine if you set the firewall itself to use 8.8.8.8 and 8.8.4.4.
If you want the CLIENTS to resolve using those crappy NordVPN DNS servers then tell the CLIENTS to use those as their DNS servers. Either using DHCP or static config on the CLIENTS themselves.
No reason to hobble the firewall itself just because you want some clients to do this VPN geo-shifting thing.
-
oh ok ill look i had unchecked do not do dns query forwarding under the OpenVPN client..
and what does FUD stand for..and ok thanks for inpuit
-
https://en.wikipedia.org/wiki/Fear,_uncertainty_and_doubt
Basically VPN providers telling people that if you don't use a VPN your identity will be stolen in seconds etc.
There are many legitimate reasons to use a VPN of course...
Steve
-
so I changed it so those crapy vpn dns are under dhcp server
and I left the 8 8 8 8
but still package manger looses the packages
now the 3 last pics I did after I unchecked the disable dns forwarder with it checked and without it checked.. didn't work.. but it always works after a reboot of the pfsense… then time goes by yesterday it was still working after couple hours... but this morning boom gone..
so where else do I look for this happening to resolve
-
-
what is the point of pointing pfsense to 8.8.8.8? All that is need for pfsense is loopback..
-
because derelict said to set it to 8,8,8,8
ok ill delete that dns too.
-
hopefully that's right... and if so whats next
-
you can point your clients to 8.8.8.8 if you want.. But pfsense sure doesn't need to be using it.. It can resolve anything it needs to get to.. And also provide that to your clients.. It is way better to resolve than forward or ask some forwarder. That is why that is what pfsense does out of the box resolve.
-
ok ill delete the dns servers then.. so do I leave it unchecked under general the do not enable dns forwarder..
I looked under the system logs only error I found was under OpenVPN
Oct 25 08:29:45 openvpn 35104 WARNING: 'cipher' is used inconsistently, local='cipher AES-256-GCM', remote='cipher AES-256-CBC'
Oct 25 08:29:45 openvpn 35104 WARNING: 'auth' is used inconsistently, local='auth [null-digest]', remote='auth SHA512'so I don't understand though why doesn't the package manager working or the pkg update its like it has no internet.. yet im talking to you with the internet... its like it works for a day then its blocked... a reboot fixes it for the time being then comes back... and I have tried several filter reloads as I was told a while ago its stupid to reboot the pfsense only use filter reload.. but I find it doesn't fix the issue.. but a real reboot fixes it for a while.
is there anywhere else I can look...
would a backup the config file.. format the hard drive and reinstall pfsense and import the file possibly fix it?
-
fix your client setup for your vpn client clearly its tell you there is a problem
With your cipher and your auth.
-
well that's for the client and what does that error mean how do I fix it.. have no idea what that means
so then that is affecting the package manger then
have no idea how to fix that that's a nordvpn
-
well im on tech support with nordvpn hopefully they can fix this 2 errors the packagemanger and the cipher thing
-
so much for a fix... the warnings are ok they say..
and they said the package manager can be buggy at times.. and its not a vpn issueso im back to square one.. package manger or dns lookup works after a reboot.. but for only so long then next day say its non responsive... so I no further ahead... guess I keep playing with settings.. cuz this confusing and there is no defenite answer whats causing this.. if I get too frustrated gues don't matter as it still gives internet to all my devices just itself cant get internet unless you do a reboot
thanks for all the help... ill keep fiddling
-
If you have the resolver still set to forwarding mode you do need at least one DNS server set in System > General.
I would leave 8.8.8.8 in there for now. You can remove it later if you want.The error you are now seeing is different. Previously is was 'no address record' but now it's 'network is unreachable'.
That implies some routing error or maybe something just blocking the traffic.
Check the routing table when you are in that situation. Try pinging pfsense.org from Diag > Ping.Steve
