dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2937
share rss forum feed


pso2fan

@68.183.147.x

Dslextreme blocking access to phantasy star online 2

Recently there was a DDoS attack and most ISPs have for some reason started refusing any connections with pso2.jp [210.189.209.8]

I currently am a subscriber (do not know the package details) of dslextreme, and aside from this everything is working fine.

I have run a tracert on pso2.jp and it bounced from me to a "netblock-68-183-137-1.dslextreme.com" and the rest of the jumps timed out.

If one of the staff could look into this that would be great, I really don't want to call support and be told its a problem on my end.

3


geonap
lolatidiots

join:2005-12-14
Los Angeles, CA
kudos:1

this doesn't mean they're blocking it.

210.189.209.8 isn't being announced.

this is likely a decision of the ISP to stop the DDoS.

it isn't working from anywhere.



NormanS
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:11
Reviews:
·SONIC.NET
·Pacific Bell - SBC
reply to pso2fan

said by pso2fan :

I have run a tracert on pso2.jp and it bounced from me to a "netblock-68-183-137-1.dslextreme.com" and the rest of the jumps timed out.

»ISP-level block of Phantasy Star Online 2 servers?
»[Connectivity] Comcast blocked access to website?
Tracing route to pso2.jp [210.189.209.8]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  Chihiro [192.168.102.1]
  2    21 ms    21 ms    23 ms  173-228-7-1.dsl.static.sonic.net [173.228.7.1]
  3    21 ms    20 ms    20 ms  gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
  4    37 ms    42 ms    31 ms  ae2.cr2.lsatca11.sonic.net [50.0.79.178]
  5    21 ms    20 ms    21 ms  50.ae4.gw.pao1.sonic.net [69.12.211.165]
  6    21 ms    20 ms    21 ms  199.127.107.189
  7    24 ms    23 ms    22 ms  193.159.165.73
  8   131 ms   130 ms   131 ms  tyo-sa3-i.TYO.JP.NET.DTAG.DE [62.154.5.210]
  9   130 ms   130 ms   139 ms  as4725.ix.jpix.ad.jp [210.171.224.48]
 10   127 ms   127 ms   127 ms  STOrc-01Te0-4-0-2.nw.odn.ad.jp [143.90.149.45]
 11   134 ms   130 ms   131 ms  STOrs-01Te0-0-0-0.nw.odn.ad.jp [143.90.47.2]
 12   126 ms   123 ms   123 ms  230.210252167.odn.ne.jp [210.252.167.230]
 13     *        *        *     Request timed out.
 14   130 ms   130 ms   130 ms  61.202.251.198
 15   130 ms   131 ms   130 ms  po14.ta1ag01.idc.jp [158.205.192.102]
 16   129 ms   129 ms   129 ms  lag3.l303.ta1.eg.idc.jp [158.205.188.250]
 17   131 ms   131 ms   131 ms  158.205.104.60
 18   123 ms   123 ms   123 ms  210.189.209.8
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
 
Trace complete.
 

It would appear that "they" (being not U.S. ISPs) are still attempting to mitigate the DDoS. But the main site loads, for me.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum


dslx_nick
Premium,VIP
join:2011-12-24
Chatsworth, CA
kudos:27

I played PSO2 on console back in the day, but just local games with friends, not actually online... this is the first I've heard of any sort of block against PSO2 on our end.

IF there were such a block on our end, it's not something we would have done on a whim. Logically, the only reasons for us to do so would have been:

1) In response to an official request from Sega,
2) In response to automated trouble reports generated by the DDoS,
3) In response to whatever corrective measures Sega was taking in order to handle the DDoS.

Now, if it were #1... well, requests of that nature don't pass through my hands, so I'd be unaware. So I'll investigate and see if there's anything of the sort.

#2? If that's the case, then generally just need to wait for the dust to settle before attempting to clear any related blacklists. I can poke around and if this is the case, see if we can get a head-start on the whitelist process, but if the issue is still ongoing then it might just backfire and get put on the blacklist again.

#3? Similar to #2.

FAR more likely is that we're not initiating any sort of block on our end - in other words, it's not a problem with you nor with us, but rather something on Sega's end.

If Sega was taking actions which would break connectivity rather than actually initiating bans or filters - for example, if Sega was changing its IPs faster than DNS's could keep up - then usual maintenance actions would normally restore connectivity on a routine basis (eg. the DNS's would eventually catch up and reflect the latest IPs, typically within 48 hours or so).

I'll investigate further, but at this point I'm doubting it's anything directly on our end. Will let you know either way.



pso2fan

@68.183.147.x

Thank you for your reply, I thought it was an isp thing since some people using different isps or vpns are having little to no trouble accessing the game.

There has been no announcement from Sega regarding the EU/US players having trouble accessing the Japanese servers as of yet, and I'm baffled as to why I didn't think it could be a problem on their end.

Anyway thanks for your reply, I do appreciate it.


reaper527

join:2014-07-07
Woburn, MA
reply to dslx_nick

found this thread while searching on the game (as i'm experiencing similar issues with my isp) and wanted to clear a few things up hoping that it could help you with your customers.

said by geonap:

it isn't working from anywhere.

this isn't accurate. time warner cable customers can connect to the servers without issue, and last week verizon customers were able to connect while some other isp's were experiencing the exact behavior the OP describes.

to say that "it isn't working form anywhere" is inaccurate.

said by dslx_nick:

I played PSO2 on console back in the day, but just local games with friends, not actually online.

just a heads up, there is a good chance you are confused about what the game in question is. this is phantasy star online 2, a game which was released 2 years ago (july 4th, 2012), and it has no offline mode, and only was released on the pc and the playstation vita. what i suspect you are talking about is either phantasy star online 1 episode 2 (which was released on gamecube and xbox and featured offline play) or phantasy star universe (released on pc and xbox360, with an offline story campaign).

just figured getting everyone on the same page would be a good start.

said by dslx_nick:

If Sega was taking actions which would break connectivity rather than actually initiating bans or filters - for example, if Sega was changing its IPs faster than DNS's could keep up

just want to add that the ip's in question have remained the same through the entire process. the people who are able to connect and those who aren't are still going to 210.189.209.8 (pso2.jp) and 210.189.208.16 (gs016.pso2gs.net).


dslx_nick
Premium,VIP
join:2011-12-24
Chatsworth, CA
kudos:27

Lo, I have returned, bearing DATA! (courtesy of friendly local network engineer)

"It isn't working from anywhere" = not *quite* accurate... but almost (explained further below).

"PSO1 Ep. II" = good call! In my defense, it's been over a decade since I played, so my memory was a bit fuzzy on it (Gamecube, in my case).

"IPs in question have remained the same" = related to the "it's not working from anywhere" point.

Very simply, this IS Sega's fault - or at least, their responsibility. See, Sega's not properly advertising their IP and routes to the appropriate backbone carriers. I'm sure anyone who's spent enough time here on BBR has at least heard of names like Level3 and Cogent? Sega is SUPPOSED to be in communication with those carriers, and several others... but it isn't. So the 'big boys' like Level3 and Cogent don't know that Sega's PSO2 exists nor how to reach it. Even if you know what the (unchanged) destination IP is, if you don't know the *route* necessary to reach it, it doesn't do you much good.

Right now, testing is indicating that exactly two carriers are aware of PSO2: Asia Pacific Network Information Centre (APNIC) and Hurricane Electric (HE). Two, out of dozens.

As you can see, it's not a problem with ISPs refusing to grant access... it's a problem with Sega not making its presence known. Now, as a short-term work-around, it IS possible for our network engineers to manually set a route to the destination IP... but that's generally not recommended. It'd be a band-aid that might actually cause more problems in the long run, and besides - even if we did that, that would only 'fix' it for customers on DSL Extreme connections (which, while nice for us, wouldn't help you play with friends online if your friends aren't using DSL Extreme too). The REAL solution is for Sega to step it up and publish with the carriers.



Napsterbater
Meh
Premium,MVM
join:2002-12-28
Milledgeville, GA
Reviews:
·Windstream

Props to dslx_nick See Profile for checking on the problem and posting.

I love ISP's that speak out on technical issues like this.
--
IPv6 Sage - ipv6.he.net/certification/scoresheet.php?pass_name=Napsterbater
www.napshome.net



xSphinx

@97.113.182.x
reply to dslx_nick

Speaking of Level3, after being told by centurylink there was nothing they could do, I decided I'd figure out who their backbone was and called Level3. They're unable to even access pso2.jp main site.
At the very least though, they're now aware of the issue and I hope it at least helps to get something started towards a solution with SOJ.



Napsterbater
Meh
Premium,MVM
join:2002-12-28
Milledgeville, GA

But as we have said Its not Level3's problem, so they couldn't care less most likely. It is Sega/pso2's problem.
--
IPv6 Sage - ipv6.he.net/certification/scoresheet.php?pass_name=Napsterbater
www.napshome.net