Quote:
Originally Posted by bera
A couple of (slightly unrelated) questions:
- Since all browsing traffic seems to be proxied through a server at amazon how can this be circumvented and connect e.g. through wi-fi directly using your own ISP (without going through the amazon proxy)?
|
that already happens.
err this is obviously AMENDED. don't bother trying to backstep it and
traceroute to google.com (173.194.34.135), 30 hops max, 38 byte packets
1 BThomehub.home (192.168.1.99) 11.040 ms 96.180 ms 99.431 ms
I vis tracerrouted these: They are BT in UK
2 217.32.143.99(217.99.143.99) 19.429 ms 18.378 ms 18.093 ms
It goes on... for the vaguely interested.
Code:
3 217.99.144.99 (217.99.144.99) 19.132 ms 18.357 ms 18.565 ms
4 213.90.181.99(213.99.181.99) 21.486 ms 20.671 ms 21.172 ms
5 217.99.169.99 (217.99.169.99) 21.015 ms 21.471 ms 21.049 ms
6 217.99.169.99 (217.99.169.199) 21.116 ms 21.850 ms 20.594 ms
7 109.99.251.99 (109.99.251.99) 20.160 ms 109.99.251.99 (109.199.251.99) 20.295 ms 109.199.251.99 (109.199.251.99) 21.697 ms
8 core1-te0-12-0-6.ealing.ukcore.bt.net (109.159.251.99) 27.979 ms core1-te0-4-0-2.ealing.ukcore.bt.net (109.159.251.99) 35.703 ms core2-te0-2-4-0.ilford.ukcore.bt.net (109.159.251.99) 36.531 ms
9 peer1-xe3-3-0.telehouse.ukcore.bt.net (109.159.254.99) 26.137 ms peer1-xe3-0-1.telehouse.ukcore.bt.net (109.159.254.99) 28.722 ms 28.205 ms
10 195.99.126.99 (195.99.126.99) 25.872 ms 195.99.125.25 (195.99.125.99) 26.698 ms 195.99.126.99 (195.99.126.99) 26.966 ms
11 209.85.252.99 (209.85.252.99) 28.604 ms 27.916 ms 31.220 ms
12 209.85.253.99 (209.85.253.99) 28.673 ms 28.813 ms 27.778 ms
Code:
13 lhr14s21-in-f7.1e100.net (173.194.34.99) 26.539 ms 27.136 ms 27.058 ms < --- I'm gurgle me...
So in answer to your question: when you go via Wifi it is not proxied AFAICT.
hth