Persistent Internet Connection- available in pfSense?
-
I'm thinking that if you can ping 8.8.8.8 when your internet is "down", your internet isn't down…
Yes, I already know about this.
When symptom, occurs, ISP dns server, is not reachable using Ping command.
Whereas Google free DNS server is reachable.
But internet surf in not available.
pfSense WAN interface still showing the WAN adsl PPOE connection is UP and running. -
Setting an external monitor IP that really becomes inaccessible will at least give you a record of when the connection fails. You can use that to compare your logs or as data to complain to your ISP
I am afraid, that is not much I can do, complaining this issue to the ONLY ISP available in small town.
Complaint may be accepted, but problem will still exist.
That is just bad customer service, that is way it works in my country.Usually, folks in the city won't complain, they just switch to another ISP since there are more choices available.
-
I am thinking may be 1 of the PCs is infected with malware or trojan or botnet or some malicious program,
and it is blasting out SPAM continuously…....And the ISP is blocking my dynamic WAN IP address, to stop the SPAM traffic flowing out the internet. ::)
-
When you think it is down, try to ping some other known IP addresses that should respond, like:
216.146.35.35 - DynDNS
216.146.36.36
8.8.8.8 - Googel DNS
8.8.4.4
208.67.222.222 - OpenDNS
208.67.220.220If those are all reachable, then you seem to still have internet routing.
Then try looking up names:
nslookup pfsense.org.and so on.
If it is just DNS name lookup that is broken, then point your pfSense to some of the above addresses for DNS, in System->General Setup.
-
Ok, thank you all for contributing your answers to my question.
Greatly appreciated! ;DI follow the advice from phil.davis
And see how it goes….. -
Phill is right, but this will only work if ISP provided DNS server is the issue.
-
Phill is right, but this will only work if ISP provided DNS server is the issue.
Yes, the ISP does provides its own DNS servers
See below:DNS server(s)
127.0.0.1
161.142.2.17<–---- This the 1st DNS server prodvided.
161.142.212.17<----This the 2nd DNS server provided.
192.168.1.1I am suspecting the routing (DNS traffic to the ISP DNS servers) is a bit unreliable.
-
I actually doubt this is going to fix your problem but its worth a try.
-
I actually doubt this is going to fix your problem but its worth a try.
Yes, I also doubt it, but what to do? There is only 1 crappy ISP doing business in a small town.
There is no alternative ISP available that I can switch to…..to get a better quality link connection. :)The only thing I can do is try on my end first and see it helps or not. :)
-
See - Its strange that a crappy ISP would be fixed with hardware resets and reboots on your end.
Seems more likely something on your end is to fault. -
Your provider may or may not use connection profiling to increase stability. Here in the UK it's a well known issue. For example:
http://www.thinkbroadband.com/faq/sections/radsl.html#229
And
http://en.wikipedia.org/wiki/ADSL_Max#Rate_adaptation_and_BT_Wholesale.27s_.27Dynamic_Line_Management.27_.28DLM.29
If you don't know I would try to avoid it!See - Its strange that a crappy ISP would be fixed with hardware resets and reboots on your end.
Well presumably that results in a new WAN IP address which might well restore the connection if it is being filtered as a result of some upstream malware detection. If that's true then the same thing would happen if you renew your IP by manually disconnecting and reconnecting the PPPoE session.
Steve
-
Yes - Now this I can agree with, but thats a user issue.
I think trying it a couple days with a clean install of whatever OS he likes is probably a good idea.
If malware is the problem, don't need to be bouncing his pfsense box all the time. Needs to get rid of the malware.
