Open Trackers blocked - Erakis

[panicmode 0]

I suddenly am unable to connect to the public open trackers including:

 

udp://open.demonii.com:80

udp://trackercoppersurfker.tk:80

udp://tracker.istoleit:80

udp://tracker.openbittorrent.com:80

udp://tracker.publicbt.com:80

 

I think they must be blocking the vpn exit in some sort of cooperation since my private tracker is working just fine.

[OpenSourcerer 1441]

Yes, we know that, anything else? No offense, mate.

[athelstan 11]

Nicht so schnell, giganerd!

 

In this case it looks like AirVPN themselves are blackholing the traffic.

 

Tracing route to open.demonii.com [62.210.137.203]
over a maximum of 30 hops:

 

  1   272 ms   119 ms   132 ms  10.5.0.1
  2   135 ms   115 ms    47 ms  10.112.0.1
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.

[panicmode 0]

Yes, we know that, anything else? No offense, mate.

Duh, thanks. Search is my friend.

[panicmode 0]

DHT seems to be working fine for me, however curiosity is getting the better of me...

 

Nicht so schnell, giganerd!

 

In this case it looks like AirVPN themselves are blackholing the traffic.

 

Tracing route to open.demonii.com [62.210.137.203]

over a maximum of 30 hops:

 

1 272 ms 119 ms 132 ms 10.5.0.1

2 135 ms 115 ms 47 ms 10.112.0.1

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

So follow up question to this. I thought about this a bit and at first dismissed it since traceroute can be kind of unreliable sometimes. But after comparing traceroute of one of the sites I listed and say www.google.com, I noticed they routed differently internally with airvpn. Why the difference?

 

see attached.

[panicmode 0]

<snip>

see attached.

Second one didn't attach for some reason

[OpenSourcerer 1441]

 

DHT seems to be working fine for me, however curiosity is getting the better of me...

 

Nicht so schnell, giganerd!

 

In this case it looks like AirVPN themselves are blackholing the traffic.

 

Tracing route to open.demonii.com [62.210.137.203]

over a maximum of 30 hops:

 

1 272 ms 119 ms 132 ms 10.5.0.1

2 135 ms 115 ms 47 ms 10.112.0.1

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

So follow up question to this. I thought about this a bit and at first dismissed it since traceroute can be kind of unreliable sometimes. But after comparing traceroute of one of the sites I listed and say www.google.com, I noticed they routed differently internally with airvpn. Why the difference?

 

see attached.

 

Don't compare google with a tracker actively blocking access from certain IPs. According to the Check routes feature traffic from the Netherlands and America to tracker.istole.it gets rerouted through internal routing server NL2, generating your traceroute results. You could try to connect with servers in Canada, Germany or Great Britain.

[panicmode 0]

Don't compare google with a tracker actively blocking access from certain IPs. According to the Check routes feature traffic from the Netherlands and America to tracker.istole.it gets rerouted through internal routing server NL2, generating your traceroute results. You could try to connect with servers in Canada, Germany or Great Britain.

 

Thanks! Didn't know about that feature.