Have my IP been banned?

[clange]

Hi

I have been unable to reach *.osdev.org the last few days when trying from home. It works fine when accesing from anywhere else.

I just wanted to check if my IP (2.104.152.51) has been banned for some reason? If it has please let me know what to do to lift the ban.

If there is no ban I have to check with my Telecom provider.

Thanks in advance.

Christian

[AJ]

Hi,

That IP is not in our banlist, but you may want to check with Spamhaus. Typically if you were in our banlist, you would see a reason for the ban when you try to load the site.

Cheers,
Adam

[chase]

Can you ping the server? What does traceroute show?

I can't ping you from the osdev server but I can from home. From the server a traceroute to you looks like:

Code: Select all

traceroute 2.104.152.51
traceroute to 2.104.152.51 (2.104.152.51), 30 hops max, 60 byte packets
 1  router1-dal.linode.com (67.18.7.161)  1.259 ms  1.241 ms  1.303 ms
 2  xe-2-0-0.car03.dllstx2.networklayer.com (67.18.7.89)  0.188 ms  0.226 ms  0.303 ms
 3  po101.dsr01.dllstx2.networklayer.com (70.87.254.73)  0.580 ms  0.599 ms  0.620 ms
 4  po21.dsr01.dllstx3.networklayer.com (70.87.255.65)  0.759 ms  0.737 ms  0.736 ms
 5  ae16.bbr02.eq01.dal03.networklayer.com (173.192.18.228)  0.449 ms  0.610 ms  0.588 ms
 6  ae-11-0.pr0.dfw10.tbone.rr.com (66.109.9.97)  0.553 ms  0.486 ms  0.489 ms
 7  ae-1-0.cr0.dfw10.tbone.rr.com (66.109.6.178)  54.851 ms ae-10-0.cr0.dfw10.tbone.rr.com (66.109.9.104)  51.967 ms  50.356 ms
 8  66.109.9.40 (66.109.9.40)  48.603 ms ae-2-0.cr0.chi30.tbone.rr.com (66.109.6.23)  48.064 ms 66.109.9.40 (66.109.9.40)  47.851 ms
 9  ae-0-0.cr0.chi10.tbone.rr.com (66.109.6.20)  56.903 ms  55.005 ms  52.369 ms
10  ae-4-0.cr0.nyc20.tbone.rr.com (66.109.6.24)  46.311 ms 107.14.19.35 (107.14.19.35)  51.596 ms  55.444 ms
11  107.14.19.147 (107.14.19.147)  45.471 ms  45.446 ms ae-0-0.pr0.nyc20.tbone.rr.com (66.109.6.157)  45.739 ms
12  xe-3-2-0-6.nyk2nqp1.us.ip.tdc.net (198.32.118.51)  45.914 ms  57.309 ms  56.248 ms
13  ae2-0.boanqe10.dk.ip.tdc.net (83.88.28.3)  134.172 ms  134.206 ms  134.065 ms
14  cpe.xe-3-0-0-126.boanqe10.dk.customer.tdc.net (87.54.59.194)  143.282 ms  143.142 ms *

And it times out at that last hope and never goes past it. traceroute from my home shows that there should be two more hops after that. One to something that doesn't respond to icmp packets and the last to:

Code: Select all

x1-6-30-46-9a-70-8d-e8.k1111.webspeed.dk [2.104.152.51]

[clange]

Hi

AJ:

Thanks for taking time to help me. I have checked with Spamhaus and my IP is not on the SBL or XBL. It is on the PBL though - my understanding is that this just indicates sthat it is a dynamic IP.

Chase:

Thanks also for helping. First a little bit about my setup: I have a router running OpenWRT (192.168.1.1) which is bridged with a switch (10.43.0.1) that connects to the cable TV stuff that provides internet.

I can't ping the server. I tried tracing the route, but without success - it can't even trace from my router to the switch it is bridged with! When I try to connect directly to the switch and doing a trace route the result is the same! I sniffed the traffic and made sure that packets was leaving my router.

I have tried tracing 173.255.206.38 and 173.255.206.40 from my router too to check if it was a simple routing problem, but both works perfect!

Code: Select all

traceroute to 173.255.206.38 (173.255.206.38), 30 hops max, 38 byte packets
 1  10.43.0.1 (10.43.0.1)  48.530 ms  100.692 ms  49.465 ms
 2  10.250.20.1 (10.250.20.1)  90.630 ms  72.285 ms  95.013 ms
 3  xe-3-0-0-126.boanqe10.dk.ip.tdc.net (87.54.59.193)  102.385 ms  xe-0-1-0-125.boanqe10.dk.ip.tdc.net (62.242.37.97)  113.659 ms  71.982 ms
 4  ae1-0.alb2nqp7.dk.ip.tdc.net (83.88.21.83)  110.828 ms  93.850 ms  60.512 ms
 5  telia.xe-4-0-0-0.alb2nqp7.dk.ip.tdc.net (195.215.109.2)  77.288 ms  57.231 ms  93.849 ms
 6  kbn-bb2-link.telia.net (80.91.249.50)  106.671 ms  36.201 ms  33.975 ms
 7  nyk-bb1-link.telia.net (213.155.134.50)  127.668 ms  nyk-bb1-link.telia.net (80.91.254.89)  182.949 ms  nyk-bb2-link.telia.net (80.91.247.121)  126.737 ms
 8  nyk-b6-link.telia.net (213.155.130.241)  93.177 ms  nyk-b6-link.telia.net (80.91.253.95)  102.143 ms  nyk-b6-link.telia.net (213.155.130.241)  97.656 ms
 9  xe-0-0-1.bbr02.tl01.nyc01.networklayer.com (213.248.72.174)  116.738 ms  136.430 ms  109.718 ms
10  ae1.bbr01.eq01.chi01.networklayer.com (173.192.18.132)  229.309 ms  246.416 ms  254.872 ms
11  ae20.bbr01.eq01.dal03.networklayer.com (173.192.18.136)  253.489 ms  241.361 ms  199.929 ms
12  po31.dsr02.dllstx3.networklayer.com (173.192.18.227)  248.582 ms  181.821 ms  177.114 ms
13  po32.dsr02.dllstx2.networklayer.com (70.87.255.70)  159.808 ms  po31.dsr01.dllstx2.networklayer.com (70.87.255.66)  175.571 ms  po32.dsr02.dllstx2.networklayer.com (70.87.255.70)  142.396 ms
14  po1.car02.dllstx2.networklayer.com (70.87.254.82)  143.691 ms  po2.car02.dllstx2.networklayer.com (70.87.254.86)  154.025 ms  218.516 ms
15  router2-dal.linode.com (67.18.7.94)  193.360 ms  199.454 ms  152.399 ms
16  li216-38.members.linode.com (173.255.206.38)  140.574 ms  189.193 ms  155.985 ms

This matches your route very well except for the last part where the ISP is routing the packages on their internal 10.* subnet, which is expected.

So from what I can see there is no problem in your end or in my end. But as soon as I try to access 173.255.206.39 through my ISP it mysteriously stops working. I have to call their support tomorrow and get a technician to help me fix the problem.

Thanks a lot both of you for helping me.

Christian

[Brynet-Inc]

2/8 is one of those previously "IANA Reserved" ranges that were released a few years back.

It wouldn't surprise me if it ended up in someone's bogons list.

[clange]

Hi

2/8 is one of those previously "IANA Reserved" ranges that were released a few years back.

It wouldn't surprise me if it ended up in someone's bogons list.

Good idea - I haven't though about that. But I don't think this is the problem in this case. I have no problems with 173.255.206.38 or 173.255.206.40.

I talked to my ISP support friday and was able to get them to reproduce the problem with 173.255.206.39. Unfortunatly all their technicians was gone for the weekend and they were unable to help me. So I have repported the error along with relevant traces etc. and hope that it will be fixed

Christian