Jump to content

taz

Active Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by taz

  1. Hi Infiltrator, the problem is not resolved. I use a ssh proxy to browse hak5.org ;)
  2. Thanks VaKo, I just send to you a private message.
  3. Hi, digip : With the DNS of my ISP : grep nameserver /etc/resolv.conf nameserver 212.27.40.241 nameserver 212.27.40.240 Nslookup : nslookup for hak5.org ;; connection timed out; no servers could be reached With OpenDNS : grep nameserver /etc/resolv.conf nameserver 208.67.222.222 Nsloopup : nslookup for hak5.org ;; connection timed out; no servers could be reached VaKo : I'm unable to send private message to you :/ The error message is "You are not allowed to use the messenger feature on this board". VaKo do you want my skype adress or something like that to make tests ? Thanks.
  4. Hi, digip : I'm agree with VaKo, the DNS are not in cause. Of course with a proxy, I can access to the website. I'm in my parent's house right now, and I use a private ssh proxy sock to browse the forum :) VaKo : The IP of my parent's house is <redacted> Thanks :) taz.
  5. Hi digip, impressive answer :) Here the answer about your questions : - I suppose my OS is not in cause, because : I did all test with my Mac OS X laptop. - I did one test with Linux in my friend house, he is also on Free.fr ISP and he has the same problem. Traceroute form my friend house : traceroute to www.hak5.org (66.11.227.124), 30 hops max, 60 byte packets 1 fw-foret.foret (192.168.0.1) 0.124 ms 0.153 ms 0.185 ms 2 88.171.3.254 (88.171.3.254) 21.337 ms 23.803 ms 24.417 ms 3 * 213.228.20.254 (213.228.20.254) 26.562 ms * 4 lyon-crs16-1-be1003.intf.routers.proxad.net (212.27.50.102) 32.675 ms 33.860 ms 34.588 ms 5 th2-crs16-1-be2001.intf.routers.proxad.net (212.27.59.29) 42.429 ms 43.101 ms 43.840 ms 6 bzn-crs16-1-be2000.intf.routers.proxad.net (212.27.57.210) 46.012 ms 45.168 ms 45.894 ms 7 londres-6k-1-po101.intf.routers.proxad.net (212.27.51.186) 60.411 ms 47.426 ms 47.795 ms 8 newyork-6k-1-po1.intf.routers.proxad.net (212.27.58.206) 163.055 ms * * 9 NYCL-PEER-03.twtelecom.net (198.32.118.36) 119.878 ms 120.538 ms 121.503 ms 10 pdx1-ar3-xe-1-0-0-0.us.twtelecom.net (66.192.240.190) 196.437 ms 197.129 ms 198.547 ms 11 ge-8-2-20.acs-rtr06.ptldor02.iinet.com (198.145.240.169) 200.747 ms 201.032 ms 201.542 ms 12 198.145.40.101 (198.145.40.101) 203.455 ms 203.478 ms 204.867 ms 13 198.145.179.222 (198.145.179.222) 189.567 ms 189.885 ms 190.891 ms 14 66-11-225-95.iinet.pdx.dotster.net (66.11.225.95) 191.391 ms 190.849 ms 193.987 ms 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * I don't know if the problem is the limit of jump allowed by 66.11.225.95. I think it's as you said a blacklist in 66.11.225.95 or it's 66.11.225.95 don't know the route to address 88.171.3.254. I can't change my MAC or my ip address because my ISP block it. I don't know what else to try... Do you have to root access to 66.11.225.95 ? Thanks, taz.
  6. Hi Sparda, thanks for your quick answer :) So, how can I check if there are banned ip address in free.fr ? The router was reboot, but the problem is the same. In fact the problem exist since 2 or 3 month. Thanks, taz.
  7. Hi there, I have a problem to access to your website from some ISP. - My ISP in my apartment is www.free.fr : I can access to your website :) - My parent's ISP is www.free.fr too, and I can't access to your website. - On both I use the same DNS server. I made a "traceroute www.hak5.org" from both location and it result this : From my apartment : (is working) traceroute www.hak5.org traceroute to www.hak5.org (66.11.227.124), 64 hops max, 52 byte packets 1 192.168.0.254 (192.168.0.254) 1.835 ms 1.182 ms 1.120 ms 2 82.240.63.254 (82.240.63.254) 23.390 ms 30.251 ms 20.738 ms 3 marseille-6k-1-a5.routers.proxad.net (213.228.12.126) 28.062 ms 19.874 ms 20.649 ms 4 lyon-crs16-1-be1003.intf.routers.proxad.net (212.27.50.102) 25.160 ms 54.455 ms 46.133 ms 5 th2-crs16-1-be2001.intf.routers.proxad.net (212.27.59.29) 62.962 ms 30.787 ms 36.144 ms 6 bzn-crs16-1-be2000.intf.routers.proxad.net (212.27.57.210) 47.874 ms 32.551 ms 31.902 ms 7 londres-6k-1-po101.intf.routers.proxad.net (212.27.51.186) 46.195 ms 55.842 ms 60.833 ms 8 newyork-6k-1-po1.intf.routers.proxad.net (212.27.58.206) 114.916 ms 114.362 ms 113.591 ms 9 nycl-peer-03.twtelecom.net (198.32.118.36) 140.597 ms 117.539 ms 124.396 ms 10 pdx1-ar3-xe-1-0-0-0.us.twtelecom.net (66.192.240.190) 188.734 ms 190.450 ms 188.415 ms 11 * ge-8-2-20.acs-rtr05.ptldor02.iinet.com (198.145.240.166) 200.960 ms * 12 198.145.40.101 (198.145.40.101) 235.538 ms 199.387 ms 195.868 ms 13 198.145.179.222 (198.145.179.222) 214.160 ms 190.542 ms 194.466 ms 14 66-11-225-95.iinet.pdx.dotster.net (66.11.225.95) 206.077 ms 204.204 ms 205.033 ms 15 66-11-227-124.managemyvps.com (66.11.227.124) 204.756 ms 198.736 ms 223.988 ms From my parent's house : (is not working) traceroute www.hak5.org traceroute to www.hak5.org (66.11.227.124), 64 hops max, 52 byte packets 1 192.168.0.254 (192.168.0.254) 13.091 ms 0.951 ms 1.078 ms 2 88.166.241.254 (88.166.241.254) 20.789 ms 21.422 ms 20.265 ms 3 78.254.7.158 (78.254.7.158) 20.836 ms 20.084 ms 20.946 ms 4 sf283-1-v902.intf.nra.proxad.net (78.254.254.89) 20.778 ms 21.268 ms 22.977 ms 5 ban83-1-v900.intf.nra.proxad.net (78.254.254.85) 21.014 ms 21.697 ms 21.465 ms 6 lbe83-1-v902.intf.nra.proxad.net (78.254.254.81) 22.129 ms 20.755 ms 20.493 ms 7 scy83-1-v900.intf.nra.proxad.net (78.254.254.77) 22.713 ms 22.276 ms 22.057 ms 8 cio13-1-v902.intf.nra.proxad.net (78.254.254.73) 20.794 ms 21.950 ms 22.329 ms 9 au213-1-v900.intf.nra.proxad.net (78.254.254.69) 22.557 ms 21.020 ms 22.843 ms 10 au113-1-v902.intf.nra.proxad.net (78.254.254.65) 22.563 ms 21.468 ms 21.823 ms 11 peh13-1-v900.intf.nra.proxad.net (78.254.254.61) 22.545 ms 21.685 ms 22.420 ms 12 cor13-1-v902.intf.nra.proxad.net (78.254.254.57) 37.587 ms 22.984 ms 22.061 ms 13 * * marseille-6k-1-v900.intf.nra.proxad.net (78.254.254.53) 31.939 ms 14 lyon-crs16-1-be1003.intf.routers.proxad.net (212.27.50.102) 26.172 ms 26.929 ms 26.294 ms 15 th2-crs16-1-be2001.intf.routers.proxad.net (212.27.59.29) 34.536 ms 32.028 ms * 16 bzn-crs16-1-be2000.intf.routers.proxad.net (212.27.57.210) 35.136 ms 33.900 ms 35.572 ms 17 londres-6k-1-po101.intf.routers.proxad.net (212.27.51.186) 47.413 ms 50.634 ms 47.001 ms 18 newyork-6k-1-po1.intf.routers.proxad.net (212.27.58.206) 115.385 ms 115.305 ms 115.259 ms 19 nycl-peer-03.twtelecom.net (198.32.118.36) 115.520 ms 115.269 ms 115.043 ms 20 pdx1-ar3-xe-1-0-0-0.us.twtelecom.net (66.192.240.190) 187.846 ms 188.563 ms 189.134 ms 21 ge-8-2-20.acs-rtr06.ptldor02.iinet.com (198.145.240.169) 191.017 ms 190.904 ms 190.837 ms 22 198.145.40.101 (198.145.40.101) 189.420 ms 190.099 ms 191.060 ms 23 198.145.179.222 (198.145.179.222) 190.943 ms 191.258 ms 191.167 ms 24 66-11-225-95.iinet.pdx.dotster.net (66.11.225.95) 189.726 ms 190.959 ms 195.389 ms 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * 31 * * * 32 * * * 33 * * * 34 * * * 35 * * * 36 * * * 37 * * * 38 * * * 39 * * * 40 * * * 41 * * * 42 * * * 43 * * * 44 * * * 45 * * * 46 * * * 47 * * * 48 * * * 49 * * * 50 * * * 51 * * * 52 * * * 53 * * * 54 * * * 55 * * * 56 * * * 57 * * * 58 * * * 59 * * * 60 * * * 61 * * * 62 * * * 63 * * * 64 * * * I don't understand the problem. Do you have a idea how to solve th problem please :) Thanks for your help, taz.
×
×
  • Create New...