C:\Users\Me>ping assign.stanford.edu
Pinging vsp10v-vz00.stanford.edu [171.67.108.200] with 32 bytes of data:
Reply from 171.67.108.200: bytes=32 time=22ms TTL=52
Reply from 171.67.108.200: bytes=32 time=22ms TTL=52
Reply from 171.67.108.200: bytes=32 time=22ms TTL=52
Reply from 171.67.108.200: bytes=32 time=22ms TTL=52
Ping statistics for 171.67.108.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 22ms, Average = 22ms
C:\Users\Me>ping 171.67.108.200
Pinging 171.67.108.200 with 32 bytes of data:
Reply from 171.67.108.200: bytes=32 time=22ms TTL=52
Reply from 171.67.108.200: bytes=32 time=22ms TTL=52
Reply from 171.67.108.200: bytes=32 time=23ms TTL=52
Reply from 171.67.108.200: bytes=32 time=23ms TTL=52
Ping statistics for 171.67.108.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 23ms, Average = 22ms
AtwaterFS wrote:DNS is not black magic - it works for the rest of the Internet...
In this guy's case easiest thing would be to find a VPN to an unfiltered network that can be kept alive indefinitely
Yep. And he get in trouble for violating that country's laws that attempt to protect citizens from the dangers of exposure to certain aspects of foreign culture.
P5-133XL wrote:I must be missing something. How does brienposey.com equate to http://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?
on that pic was just giving an example on what i see i was too lazy to upload a pic then post
and this is what i see when i go into ANY numeric address
P5-133XL wrote:That was a question I asked earlier only with OpenDNS rather than googleDNS --
P5-133XL wrote:
I wonder what happens if you replace the authorized DNS servers in your connection with something like openDNS's IP addresses?
Depending upon the software that the ISP installed, there might be issues with the hosts file too for it can take precedence over the DNS server.
tried it didnt do ****
i guess ill have to use a vpn that shuts down every 6 hours OR F@H makes a proxy server for us
(i tried free proxy which worked but it expires every 2 hours)
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
It wouldn't help : the FAH client doesn't access to domains ... it directly accesses IP addresses which seems to be forbidden for owned66.
There is not need to argue about the possible solutions since there are only two :
- to use of a proxy (which uses an url and not an IP address)
- to use a VPN (which also allow access by url and not IP address)
Here is a good place to start to choose a VPN provider : http://www.start-vpn.com/ (you'll find a huge list of providers and some tests and user opinions).
Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
