Avaliable Packages missing cant seem to find
-
no those are the vpn dns server ones
i followed the instructions here
https://nordvpn.com/tutorials/pfsense/pfsense-openvpn/ -
Hmm, should be good then. If you do to Diag > DNSlookup does it show success for all entries against pfsense.org?
Steve
-
-
i tried several google.com nordvpn.com still same error
and cant even pingyet i have internet so im confused
-
frustrating i reboot the pfsense and it works the packages show... and the dns lookups work.. but 5 -10 min after the damn thing is gone and the dnslookup fails... would this be a dns server from the nordvpn being problem or a setting in pfsense
-
Probably the way you have your DNS configured. Hard to say if it's "nordvpn" or not.
Personally, I would not accept a default route from a VPN provider. I would enable Don't pull routes and policy route over the VPN instead.
-
oh ok and why is that what does that mean
and ok where i set that...
thank you for all your inputs so far..
-
It's a setting in the OpenVPN client setup.
Currently when you connect the server pushes a new default route to pfSense which you can see in your routing table.
If you disable that you then have to route traffic you want to use the VPN manually with policy rules. That can still be everything if you need it to be.You have the option set to 'not use the resolver for the firewall itself' in System > General whcih is why the DNSLookup results only show those two DNS servers. If you unchecked that it would also try the local resolver at 127.0.0.1 which will likely always work and is why you other clients still work.
It's interesting that those servers don;t work though with the default route being over the VPN. Was the VPN connected when you ran those tests?You could add another DNS server and set the pppoe gateway, say 8.8.8.8, and that will always work.
Steve
-
ok hope i did this right... as ill see if it fails lol..seems after 5 10 min yesterday i don't remember as i dosed off and woke up today and couldn't do the packages or the dns lookup all fails.. i reboot and it works..
so here is image.... and i already had the Do not use the DNS Forwarder/DNS Resolver as a DNS server for the firewall already checked off
-
the above didn't work i back to blank package manager... and the dns lookup doesn't work again
works right after a reboot but after 2 hours i just re tried and she don't work.. but i have internet etc -
i do notice some websites wont work.. like canadacomputers.com when searching.. doesn't always works times out... even if i turn off and on the OpenVPN client no go.. but when i reboot the pfsense.. the dnslookup works... the package manger works.. and the website for searching computer parts works again.. so i frustrated... i didn't have issues till i installed the squid but i have that uninstalled now... but i cant find why i keep loosing out... if part of the program glitched or its a toggle check box … works for a while after a reboot then stops
-
So after some time you just see 'no response' from 8.8.8.8 if you run a lookup?
But initially after a reboot all three servers respond?
Odd. Do you see anything blocked in the firewall log on port 53?
Steve
-
ill have to take a new pic i lost it but when i do a reboot.. only 2 servers respond on that dnslookup.
right now i cant do a package manger i get no packages again.. i ran dnslook up the 8 8 8 8 responds
i looked at logs no port 53 blocked just other ports it shows
-
here is image after i do a reboot i checked package manger and it shows up.. and i took a dnslookup… i find that people say use the filter reload so you don't have to reboot the pfsense computer but i find that does nothing.. a real reboot makes it work for a bit
-
It would help to use name servers that actually respond if you are having DNS issues. Those 103.86.96/99 servers look like they are garbage. Why use them?
-
@derelict said in Avaliable Packages missing cant seem to find:
Those 103.86.96/99 servers look like they are garbage. Why use them?
Have to HIDE my p0rn surfing from my ISP don't ya know ;) Those are nordvpn dns servers..
-
Just switch to the resolver, it's much more reliable than those NordVPN DNS servers.
-
lol haha ya gotta hide the porn.. lol it also for geo location websites i cant access when im in Canada and i want other content
and ya those servers are the nordvpn.. it just started not to long ago this issueas for the resolver is that the dns resolver ..
this is my setup for that
-
Well your clients might be using pfsense, which pfsense resolves. But from your dns diag output you don't have pfsense pointing to itself (resolver)
So it has to use whatever shitty dns you tell it to use, like those nordvpn servers that don't answer or answer in 200+ ms
Just let pfsense point to itself - loopback 127.0.0.1, and NOTHING else and yes have the resolver enabled and NOT in forwarder mode and you should be good and pfsense can find anything it needs to find to update itself.
If you want some clients to use your vpn dns - then point to them on the client side, etc.
-
@comet424 said in Avaliable Packages missing cant seem to find:
it just started not to long ago this issue
Then contact their support if their DNS servers are flaky, maybe they forgot to update the DNSSEC root key.
-
Good luck them even knowing what that is ;)
-
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 firewall
in 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