SpaceBattles' Demise

[Stormbringer]

Somehow, I doubt it would be that simple.

When you've got mods with a backbone and an admin with a willingness to ban it'd be that simple.

[XaLEv]

***Shhhh.****

'Borrowing' an open proxy is technically a form of hacking. Talk of hacking is a bannable offense.

What about using anonymizer proxies? They're there for public use.

[Alyeska]

Relax, guys. While I disagree with their moderating policies and there's a few morons who have made it their home, there's no reason to wish harm on the whole board.

Besides, if it went down for good, there are certain morons who would simply come here instead, and none of us want that.

Be that as it may, Alyeska is still an opponent of the glorious dictatorship of the Warsie Proletariat. He must die.

Happy hunting

[Kuja]

No Civil Wars, please.

[weemadando]

No Civil Wars, please.

Hey, cmon, the ASVS vs SB war was fun... Lets have another! [/sarcasm]

[Enlightenment]

What about using anonymizer proxies? They're there for public use.

With the demise of Safeweb are there any of those left that will do form posts and don't require paid subscriptions?

[XaLEv]

With the demise of Safeweb are there any of those left that will do form posts and don't require paid subscriptions?

Dunno. The one I've been using doesn't require subscription but hasn't let me sign in. That's alright, though. Haven't seen anything I've wanted to respond to.

[Steve]

SB is still up from what I can see, and I haven't gotten any e-mails on the issue.

Relax, guys. While I disagree with their moderating policies and there's a few morons who have made it their home, there's no reason to wish harm on the whole board.

Which moderating policies do you disagree with now? You should've brought 'em up back when you were one of the vs. forum mods.

Besides, if it went down for good, there are certain morons who would simply come here instead, and none of us want that.

And don't you forget it!

[phongn]

SB's been up for me.

Code: Select all

  1    27 ms    34 ms    40 ms  gte-gw2.tbi.net [207.204.243.254]
  2    32 ms    60 ms    31 ms  webnet-gw.tampa.winstar.net [209.141.166.165]
  3    37 ms    37 ms    39 ms  miamfl2wct1-atm.wcg.net [64.200.118.77]
  4    78 ms    75 ms    75 ms  maimfl2wcx2-oc3.wcg.net [64.200.119.26]
  5    73 ms    90 ms    89 ms  dllstx1wcx3-oc48.wcg.net [64.200.210.53]
  6    91 ms    80 ms    72 ms  dllstx1wcx2-pos10-0.wcg.net [64.200.110.133]
  7    68 ms    68 ms    68 ms  dllstx9lce1-oc48.wcg.net [64.200.110.82]
  8    79 ms    89 ms   141 ms  eqix.dlfw.twtelecom.net [206.223.118.36]
  9    70 ms   119 ms    69 ms  core-02-so-2-1-0-0.dlfw.twtelecom.net [66.192.246.57]
 10    90 ms    88 ms   111 ms  core-01-so-2-0-0-0.dnvr.twtelecom.net [168.215.53.70]
 11    88 ms    93 ms   114 ms  sagg-01-rif-1.dnvr.twtelecom.net [66.192.245.90]
 12     *        *        *     Request timed out.
 13    89 ms    96 ms    91 ms  209.197.238.148

[Enlightenment]

SB is still up

For you perhaps but certainly not for everyone. Read the traceroute if you don't believe me:

Code: Select all

Tracing route to kier.3dfrontier.com [209.197.238.148]
over a maximum of 30 hops:

  1   <10 ms   <10 ms   <10 ms  celeron400 [192.168.0.1] 
  2    10 ms    10 ms    20 ms  ---------------------sympatico.ca [64.229.---.---] 
  3    10 ms    10 ms    20 ms  dis26-toronto63-Vlan100.in.bellnexxia.net [64.230.244.65] 
  4    10 ms    10 ms    20 ms  core3-toronto63-Gigabite4-0.in.bellnexxia.net [206.108.107.169] 
  5    20 ms    30 ms    20 ms  core2-chicago23-pos0-0.in.bellnexxia.net [206.108.103.114] 
  6    20 ms    30 ms    20 ms  bx1-chicago23-pos11-0.in.bellnexxia.net [206.108.103.125] 
  7    20 ms    30 ms    20 ms  sl-gw33-chi-4-1.sprintlink.net [144.228.58.193] 
  8    20 ms    30 ms    20 ms  sl-bb24-chi-6-3.sprintlink.net [144.232.26.41] 
  9    20 ms    31 ms    20 ms  sl-bb21-chi-8-0.sprintlink.net [144.232.26.78] 
 10    20 ms    30 ms    30 ms  sl-gw32-chi-10-0.sprintlink.net [144.232.26.34] 
 11    21 ms    30 ms    20 ms  sl-timewarner-5-0.sprintlink.net [144.223.73.202] 
 12    20 ms    30 ms    20 ms  core-01-ge-0-3-0-0.chcg.twtelecom.net [168.215.54.29] 
 13    40 ms    50 ms    50 ms  core-02-so-1-0-0-0.dnvr.twtelecom.net [168.215.53.14] 
 14    40 ms    50 ms    50 ms  sagg-01-rif-2.dnvr.twtelecom.net [66.192.245.94] 
 15    90 ms   100 ms   100 ms  66.162.99.2 
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.

[The Yosemite Bear]

"At last we shall reveal our selves to the Ess Bee, at last we shall have our revenge"

Yo!, Darth Ray when we said reveal our selves to the Ess Bee we did not mean flash Rocket Girl.

[Hyperion]

there's nothing wrong with SB, it's been working fine, even thru the affected days you mentioned... the servers must not like you or you've got cable gnomes in the line.

[Shinova]

The problem's for those people with certain ISPs that are affected by the DOS attack. Those people who have those ISPs can't get on SB or probably many other sites for that matter.

Other people whose pathways to SB have not been affected by the DOS attack can still get in. I, personally, have been able to get in continuously.

Yes, it's not for everyone, because some people over there have talked about having the same problem as well.

[Enlightenment]

there's nothing wrong with SB, it's been working fine, even thru the affected days you mentioned... the servers must not like you or you've got cable gnomes in the line.

Damn some of you people are thick. There's a router gnome in Denver that's routing packets into a black hole known as 66.162.99.2. In my case the gnome is 12 or 13 hops away from the edge of my LAN. Someone within no more than four hops of Kier's server either isn't propagating the correct routing tables or isn't routing packets properly. The most obvious fault is within Time Warner Telecom's network. TWT appears to be the connectivity provider for whichever ISP network Kier's webserver sits on. The problem is certainly not user error and is unlikely to get fixed unless one of TWT's customers pursuades them to clean up their act.

[Enlightenment]

The problem's for those people with certain ISPs that are affected by the DOS attack. Those people who have those ISPs can't get on SB or probably many other sites for that matter.

Unfortunately for your argument the DDoS against the DNS root servers started on the 23rd and only lasted two hours. Furthermore, DDoS attacks against the DNS infrastructure would disrupt domain name resolution rather than IP-level routing. The partial SB outage is an IP routing error rather than a domain name resolution problem.

[Shinova]

We can all still agree unanimously that the outage wasn't for everyone.

[Stormbringer]

We can all still agree unanimously that the outage wasn't for everyone.

Yeah, seeing as how it wasn't for everyone.






+1

[Howedar]

This is all news to me.

[Bob McDob]

Indeed.

[Vertigo1]

Guys, SB has NOT been down at all. I have had no trouble accessing both the main site and forums at any time for the past year. If you're having problems, its YOUR END. Bitch to your ISP to update their DNS.

However, if you insist on making fools of yourselves by acting like idiots, then download this. This contains IP entires for both the main site and the forums.

If you're running Win9x, extract the contents to X:\windows
If you're running WinNT/2k/XP, then extract the contents to X:\Windows\System32\drivers\etc or X:\WinNT\System32\drivers\etc

X = driveletter windows is installed onto. If you still have problems then its your own fault for not following directions.

Note: This hosts file also contains entires that block most web advertisements.

edit: To prove the host file works I just pinged both servers.

Microsoft Windows XP [Version 5.1]
(C) Copyright 1985-2001 Microsoft Corp.

F:\Documents and Settings\Chris Coleman>ping www.spacebattles.com

Pinging www.spacebattles.com [66.33.6.87] with 32 bytes of data:

Reply from 66.33.6.87: bytes=32 time=193ms TTL=247
Reply from 66.33.6.87: bytes=32 time=190ms TTL=247
Reply from 66.33.6.87: bytes=32 time=180ms TTL=247
Reply from 66.33.6.87: bytes=32 time=180ms TTL=247

Ping statistics for 66.33.6.87:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 193ms, Average = 185ms

F:\Documents and Settings\Chris Coleman>ping kier.3dfrontier.com

Pinging kier.3dfrontier.com [209.197.238.148] with 32 bytes of data:

Reply from 209.197.238.148: bytes=32 time=227ms TTL=240
Reply from 209.197.238.148: bytes=32 time=220ms TTL=240
Reply from 209.197.238.148: bytes=32 time=220ms TTL=240
Reply from 209.197.238.148: bytes=32 time=220ms TTL=240

Ping statistics for 209.197.238.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 220ms, Maximum = 227ms, Average = 221ms

[XaLEv]

Some people just can't pay attention.

The problem is NOT on our end. The problem is one of the routers between us and SB: 66.162.99.2. Nothing gets past it.

Now, please tell us how we are making idiots of ourselves. Then, tell us how you and the other people who have paid no attention to this thread are not making idiots of yourselves.

[Enlightenment]

F:\Documents and Settings\Chris Coleman>ping kier.3dfrontier.com

Pinging kier.3dfrontier.com [209.197.238.148] with 32 bytes of data:

Reply from 209.197.238.148: bytes=32 time=227ms TTL=240
Reply from 209.197.238.148: bytes=32 time=220ms TTL=240
Reply from 209.197.238.148: bytes=32 time=220ms TTL=240
Reply from 209.197.238.148: bytes=32 time=220ms TTL=240

Ping statistics for 209.197.238.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 220ms, Maximum = 227ms, Average = 221ms

PAY ATTENTION, FUCKWIT:

Code: Select all

[c:\documents\dirprofile]ping kier.3dfrontier.com

Pinging kier.3dfrontier.com [209.197.238.148] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 209.197.238.148:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum =  0ms, Average =  0ms

Your ISP's DNS resolves kier.3dfrontier.com as 209.197.238.148.
My ISP's DNS resolves kier.3dfrontier.com as 209.197.238.148.

Hosts DNS overrides are therefore unnecessary.

Your pings work.
Mine do not.


What part of this do you not understand?

[jegs2]

Well, with it being almost five days since SB went down, what are your thoughts on the matter?

I posted on there both yesterday and today...

[XaLEv]

Well, with it being almost five days since SB went down, what are your thoughts on the matter?

I posted on there both yesterday and today...

Let me guess...you posted before reading the thread?

[ArthurDent]

We aren't talking about it? I specifically mentioned it in the thread referenced below and Ixjac has been working on it. As for Kier, he's kind of busy readying the new VBulletin release, but he did check the server and found no problems.

http://kier.3dfrontier.com/forums/showt ... adid=38446[/url]