How is it possible to fake the ip of a server? I don't get it. If the A record resolves to the Korean IP, but the server isn't there, how does it reply?
The Pirate Bay – North Korean hosting? No, it’s fake
11–20 of 66 posts
Re: The Pirate Bay – North Korean hosting? No, it’s fake
#12I think this comment on the article is worth reading:
blumentopf am 04. March 2013 um 22:06: "Note that 175.45.176.0/22 is visible behind China Unicom in the global routing table (shortest AS path ends with 4837 131279), whereas 194.71.107.0/24 is only visible behind Intelsat (22351 131279 51040). It should therefore not come as a surprise that you see a different route when you’re doing a traceroute directly to 175.45.177.217.
While you could be right it’s also conceivable that there’s a link between Cambodia and North Korea and that the next hop behind 202.72.96.6 is indeed 175.45.177.217 (in North Korea, not just a transit net for BGP handoff). So I don’t see this as conclusive evidence that it’s a fake."
Re: The Pirate Bay – North Korean hosting? No, it’s fake
#13Dude, this was a (really well executed) joke! It should be our responsibility to help keep this shit going.
Yes, let's make internet freedom a joke. But we already have anonymous for that.
Edit: The real tragedy is the people excusing NK so they can have their way. I'm not saying they are dumb, just unlucky at thinking.
Edit2: No defense of hackivists making a mockery of themselves? How much does TPB make?
Re: The Pirate Bay – North Korean hosting? No, it’s fake
#14Now it seems they have also added fake lag to TCP port 80.
hlds@machine:~$ tcptraceroute -f 128 -m 128 thepiratebay.se 80
Selected device venet0, address 5.9.249.8, port 41774 for outgoing packets
Tracing the path to thepiratebay.se (194.71.107.15) on TCP port 80 (www), 128 hops max
128 thepiratebay.org (194.71.107.15) [open] 751.198 ms 735.700 ms 767.937 ms
This wasn't the case an hour ago. I was able to get 50ms RTT from TCP port 80 but now they probably added fake lag with tc(linux traffic shaping tool)
Re: The Pirate Bay – North Korean hosting? No, it’s fake
#15Re: The Pirate Bay – North Korean hosting? No, it’s fake
#16How is it possible to fake the ip of a server? I don't get it. If the A record resolves to the Korean IP, but the server isn't there, how does it reply?
WHOIS tells you where an IP is supposed to be located, but BGP determines where the IP is actually located. They don't have to agree and both can be hacked/spoofed.
Re: The Pirate Bay – North Korean hosting? No, it’s fake
#17Now it seems they have also added fake lag to TCP port 80. hlds@machine:~$ tcptraceroute -f 128 -m 128 thepiratebay.se 80 Selected device venet0, address 5.9.249.8, port 41774 for outgoing packets Tracing the path to thepiratebay.se (194.71.107.15) on TCP port 80 (www), 128 hops max 128 thepiratebay.org (194.71.107.15) [open] 751.198 ms 735.700 ms 767.937 ms This wasn't the case an hour ago. I was able to get 50ms RT…
[deleted]
Re: The Pirate Bay – North Korean hosting? No, it’s fake
#18The link is resulting in a 404 for me
Re: The Pirate Bay – North Korean hosting? No, it’s fake
#19Now it seems they have also added fake lag to TCP port 80. hlds@machine:~$ tcptraceroute -f 128 -m 128 thepiratebay.se 80 Selected device venet0, address 5.9.249.8, port 41774 for outgoing packets Tracing the path to thepiratebay.se (194.71.107.15) on TCP port 80 (www), 128 hops max 128 thepiratebay.org (194.71.107.15) [open] 751.198 ms 735.700 ms 767.937 ms This wasn't the case an hour ago. I was able to get 50ms RT…
I can still get a fast response:
# tcptraceroute -f 128 -m 128 thepiratebay.se
traceroute to thepiratebay.se (194.71.107.15), 128 hops max, 60 byte packets
128 thepiratebay.org (194.71.107.15) 38.726 ms 39.877 ms 39.333 msRe: The Pirate Bay – North Korean hosting? No, it’s fake
#20How is it possible to fake the ip of a server? I don't get it. If the A record resolves to the Korean IP, but the server isn't there, how does it reply?
WHOIS tells you where an IP is supposed to be located, but BGP determines where the IP is actually located. They don't have to agree and both can be hacked/spoofed.
Hmm, isn't the Korean subnet allocation fixed? If an IP falls in that range, doesn't it belong to the Korean ISP? How can someone be assigned that IP by someone other than the ISP who owns it?