Page 1 of 2
ISP blocks !
Posted: Sat Oct 16, 2010 9:53 am
by owned66
many ISPs blocks direct IP connections and many people i know experience this
all free proxies expire every 2 hours
is there a way the client could connect to the servers but not through its ip
Re: ISP blocks !
Posted: Sat Oct 16, 2010 2:29 pm
by HaloJones
Is there a reason why the servers couldn't use DNS?
Re: ISP blocks !
Posted: Sat Oct 16, 2010 3:35 pm
by toTOW
For those who wonder why this post seems so aggressive, owned66 lives in the United Arab Emirates. Many countries in this region of the world are known to filter web traffic
Did you try to use a VPN instead of a proxy ?
Re: ISP blocks !
Posted: Sat Oct 16, 2010 4:00 pm
by owned66
toTOW wrote:For those who wonder why this post seems so aggressive, owned66 lives in the United Arab Emirates. Many countries in this region of the world are known to filter web traffic
Did you try to use a VPN instead of a proxy ?
ALL vpns tend to disconnect after 5 mins of inactivity
and many times they are unresponsive and unreliable
there are only 2 solutions
1 is DNS
and 2 is to make a server a proxy for people like me
Re: ISP blocks !
Posted: Sat Oct 16, 2010 4:33 pm
by toTOW
Solution 1 will never happen in my opinion, names are subject to change, and DNS server sometimes have trouble. Using directly the IP probably saves us a lot of issues ... with some bad sides in a few countries where ISP filter traffic
Solution 2 will raise another issue ... the trouble that proxies often causes in FAH (which doesn't support any authentication based proxies) ...
Re: ISP blocks !
Posted: Sat Oct 16, 2010 4:41 pm
by owned66
toTOW wrote:Solution 1 will never happen in my opinion, names are subject to change, and DNS server sometimes have trouble. Using directly the IP probably saves us a lot of issues ... with some bad sides in a few countries where ISP filter traffic
Solution 2 will raise another issue ... the trouble that proxies often causes in FAH (which doesn't support any authentication based proxies) ...
so your saying F@H will never be used by people with IPs blocked ?
Re: ISP blocks !
Posted: Sat Oct 16, 2010 4:57 pm
by bruce
owned66 wrote:so your saying F@H will never be used by people with IPs blocked ?
We are not in a position to say "never" or to even know
for certain what FAH's future plans are. I agree with toTOW's assessment based on what we know about how FAH works today. Can you say for certain that your country will "never" unblock IP connections?
Based on some reasonable assumptions, there's a pretty good chance that that neither your country's policy nor FAH's policy will change any time soon.
Re: ISP blocks !
Posted: Sat Oct 16, 2010 5:11 pm
by owned66
my ISP will never unblock it
each time they do a group of people start a DDos attack and bring the servers down
i remember it happening on 1998
good times LOL
but im still confused about proxies
they worked fine for me (for about 2 hours)
Re: ISP blocks !
Posted: Sat Oct 16, 2010 5:25 pm
by PantherX
Which F@h Client gives you issues? Sometimes I experience it with the GPU Client when it assigns me to a Server that gives 403 Error and there isn't anything that I can do about it
Sometimes, I change the flags, WU Size, Machine ID and I get lucky to be assigned to a different Server.
Re: ISP blocks !
Posted: Sat Oct 16, 2010 6:45 pm
by owned66
PantherX wrote:Which F@h Client gives you issues? Sometimes I experience it with the GPU Client when it assigns me to a Server that gives 403 Error and there isn't anything that I can do about it
Sometimes, I change the flags, WU Size, Machine ID and I get lucky to be assigned to a different Server.
my isp blocks any ip regardless if it exists or not
example
123.45.67.89
is blocked
Re: ISP blocks !
Posted: Sat Oct 16, 2010 9:59 pm
by gwildperson
I'm not sure that's a good example. It's blocked from here in Los Angeles.
C:\Documents and Settings\Gloria>tracert 123.45.67.89
Tracing route to 123.45.67.89 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 105 ms 106 ms 106 ms netblock-xx-xxx-xxx-x.dslextreme.com [68.183.138.1]
3 111 ms 107 ms 106 ms lax1.cr1.gig3.0.37.dslextreme.com [66.51.197.185]
4 88 ms 106 ms 107 ms 66.186.192.157
5 91 ms 106 ms 107 ms f4-1-1.br02.lax.ic.samsungnetworks.net [198.32.146.54]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
(continues to repeat.)
Re: ISP blocks !
Posted: Sun Oct 17, 2010 5:44 am
by owned66
gwildperson wrote:I'm not sure that's a good example. It's blocked from here in Los Angeles.
C:\Documents and Settings\Gloria>tracert 123.45.67.89
Tracing route to 123.45.67.89 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 105 ms 106 ms 106 ms netblock-xx-xxx-xxx-x.dslextreme.com [68.183.138.1]
3 111 ms 107 ms 106 ms lax1.cr1.gig3.0.37.dslextreme.com [66.51.197.185]
4 88 ms 106 ms 107 ms 66.186.192.157
5 91 ms 106 ms 107 ms f4-1-1.br02.lax.ic.samsungnetworks.net [198.32.146.54]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
(continues to repeat.)
how is it not a good example ?
as i already said my ISP blocks ANY numeric address
its blocked regardless if it exists or not
and it isnt blocked for you. it show request timed out because 123.45.67.89 dosnt exist
what do i mean by blocked
it show a pic saying its blocked
Re: ISP blocks !
Posted: Sun Oct 17, 2010 10:34 am
by HaloJones
So what happens if you do an nslookup on
www.ibm.com and then put that IP into your browser?
Re: ISP blocks !
Posted: Sun Oct 17, 2010 12:29 pm
by owned66
HaloJones wrote:So what happens if you do an nslookup on
http://www.ibm.com and then put that IP into your browser?
this is what i see when i do it
Re: ISP blocks !
Posted: Sun Oct 17, 2010 3:38 pm
by P5-133XL
I must be missing something. How does brienposey.com equate to
www.ibm.com?
And then you didn't show a picture of your browser when you put the ip address in.
So how is what you showed have anything to do with what would show using the requested process?
You see I have a real problem with the concept that the isp blocks all ip traffic other than urls. URL's are only used at the very start of the process. You put a URL in the address box, then the browser (using direct IP traffic) will go to a DNS server to decode the URL into an IP address. After that point, the browser uses IP addresses exclusively. To block all IP traffic other than URL's implies blocking all IP traffic other than DNS requests. So they have to be doing something other than blocking all direct IP traffic.
I wonder what happens if you replace the authorized DNS servers in your connection with something like openDNS's IP addresses?