Jump to content
Come try out the Arcade, Link at the top of the website ×

djMot

*** Clan Members
  • Posts

    5257
  • Joined

  • Last visited

  • Days Won

    114
  • Donations

    90.00 USD 
  • Points

    2,159,900 [ Donate ]

Everything posted by djMot

  1. Right? But don't look at mine either, Labob. But even I can't match Dean's upload rate. That's just sick, Dean.
  2. Here are some graphs taken over roughly the same period of time. One is using the new utility I mentioned I would be using. It's called PingPlotter, and it gathers ping data over time, displaying it in an easily interpreted graphiocal and tabular manner. So the piano was back this morning: And this is what the PingPlotter graph was showing: Note that the destination address is shown as "Unavailable" as is the hop right before it. This does not surprise me, but it is disappointing nonetheless. It is most likely that SoftLayer is actively denying a response to a ping request (or a request of the type the "freeware" PingPlotter is sending - the "standard" or "pro" versions of PingPlotter might have better luck.) What IS telling to me is the high pings (really long hi/low bars) to a couple of the nodes on the "networklayer" peering network. Specifically, it's at the Dallas end of of the route which you should be able to discern by the node addresses. The highest ping is at the hand-off to SoftLayer where the IP addresses change from 173.whatever to 50.whatever. I think if you add intermittently high peering network pings to those of the already high international players (Panzergirl in Germany was playing with a ping just shy of 300 this morning) and the game server may be having fits trying to mitigate the high ping differentials. Yes, the server does try to account for these differences from what I'm seeing in the server config files. All that can really be done about the peering network faults is request that SoftLayer talk to networklayer to see if they can clean up the connection. This would seemingly benefit all SoftLayer customers. If you run PingPlotter, you may find you have an entirely different route to the server as there are many different peering networks out there. Obviously, I'm on Charter Internet and the first 13 hops on this graph are all within Charter-land. The peering network begins where Charter ends. SoftLayer, where the XI game servers live, is at the other end and reporting 100% packet loss, but again, I interpret this to mean SoftLayer is discarding ping requests of the type PingPlotter is sending. For those of you interested in PingPlotter, you can find it here (use the link at the bottom of the page for the freeware version): http://www.pingplotter.com/freeware.html
  3. It only uses Java for the packet loss statistic, not the ping test. Notice on mine where it says "Unable to test packet loss" (on Dean's too - good thing, Dean) - that is the only downside to not having Java running in the browser. And it shouldn't be. If you're seeing a packet loss statistic in your ping test, TURN JAVA OFF IN YOUR BROWSER !!! (Has the NSA not told you that? lol)
  4. Dean - you're only pinging to your local ISP. Click on the server down in Dallas for a ping that more closely reflects what you see in the game.
  5. Use Apache.
  6. Yeah, sorry... Here's using pingtest.net I chose the Dallas server as the destination. I will have to recheck this when I get the piano back, but in the meantime it's decent. Why didn't you run the test to Dallas, Labob?
  7. Yeah, no sly taken, Labob. But as you can see, all is good to my ISP. Believe me, this is the very first thing I checked.
  8. It's actually not my provider. I'm using a new utility to show this, but I have to wait till it goes all wonky again to capture it. Earlier today, what I was seeing is that it is on the Dallas end of the connection, but it may not be SoftLayer directly. Rather, I think it's their first lever peering network that's falling short. Now if you ultimately get to the server via another route, then you may see something more like what Johnny's seeing, but if you hit the wrong inbound route, you get what I'm seeing. And btw, just because my ping graph looks like a piano keyboard doesn't necessarily mean the game plays like shit for me. In most cases it's just fine despite the piano. I cannot explain that, but that's the way it is. And sometimes, it seems that it all clears up when I go into the game. I have a laptop running alongside me here, and although I may get a piano when I'm just monitoring, it might just clear up when I start playing. This is all rather perplexing.
  9. This is what I'm seeing currently and I took my screenshot when Johnny did.
  10. Looks like you're Legal In The Backseat. Careful, now. And congratulations!
  11. Welcome !! What's that smell?
  12. The COD5 Server Admin Team is pleased to announcing the Grand Opening of a second Freeze Tag Server for your immediate gaming gratification. This new server decommissions and replaces the Black Ops Server at the same IP address This is a standard Open Warfare Freeze Tag server, (i.e., not a Vietnam Freeze Tag Server like the other one.) The Vietnam Freeze Tag Server will be set to redirect on server full to this new Freeze Tag Server. But why wait for that to happen before getting your game on in the new server, right? What are you waiting for? Get on in there and kill the other guys! Please feel free to comment or post initial problem reports here and, in the case of a problem, one of us will try to get the matter resolved as quickly as possible. Remember that, although you may already have the maps on your computer, you may still notice a brief download of the actual mod before playing on the server for the first time. The XI Downloader has been updated to include the current map rotation on this server, so you might want to check there first to see if you have all the maps. Thanks, and most of all ENJOY!
  13. First concert I ever went to was a triple-bill - Siegel Schwall, REO Speedwagon (pre-Kevin Cronin), and Wishbone Ash. 1973.
  14. I did not know Bryan did anything with Mel C. NICE. That rocked! Thanks for that one, KEG.
  15. I got to this passage (near the top)... ...and decided this was all a huge load of bullshit, bullshit reporting, or any combination thereof. Not worth the bandwidth to get it to me.
  16. LastPass user's rejoice! If you are a LastPass user, you probably already know this because you got the email, too, but for those of you who are not yet LastPass users, listen up! LastPass is one of the premier Password Security services that allow you to create massively cryptic passwords ( h&Z1%RxHLPVswR2CzyN! for instance) that you couldn't remember if you tried. Very handy if you're ever being interrogated by agents of HYDRA. But moreover, it makes it real difficult to crack your important accounts, like your banking and investment sites. You set up your "password vault" with a single password which is the Last Password you will ever have to remember. Then when you register at websites, or login at ones where you already have an account, your credentials, including those cryptic passwords, are stored away in the vault. The next time you visit the site, LastPass can auto-fill your login information. Simple. Android users, the Premium version of LastPass in now able to fill login information into apps on your smartphone - something that was basically worse than pulling teeth before. AND today, I got this message from LastPass: Come on - how fucking awesome is that ??? I ran it. It told me. No more guessing. Downside: Not already a LastPass user? Well you could quickly get on board, change all your passwords in the process, and run the security check. But that's a bit of work. Being already deeply entrenched in LastPass has its benefits. IMHO, everyone needs to get on board.
  17. Quick action when the exploit actually existed, what, two years ago? The public does not need or want to know about OpenSSL; it's Greek to them. For an open source project, I certainly would not suggest that the fork's author contact everyone using their flavor of OpenSSL. That burden falls to the end user - the server owner. It's the network administrators and their security teams that need to be monitoring all tech channels for news of security breaches. This did NOT need to instill panic in the general public due to blathering about it to the public media channels. Moreover, in this case, it comes down to a matter of why the tech community was clueless? - assuming that the exploit was known FAR earlier than it was disclosed to the public. All that said, there probably was containment within the tech community about this. Where it broke down is when it somehow leaked to the general press and it exploded virally. Not much that can be done once that happens. But again, administrators and security experts that were not on top of this long ago need to be eliminated. Tough stance, but if you snooze and your data gets breached, and your company is exposed to millions/billions in liability, you loose your job. Pretty cut and dry. By the time something like this leaks to the general public, it should be last-year's news to the admin/security team.
  18. Announcing to the media that there is a serious breach in SSL server operations is neither necessary, nor advisable. It instils fear in the general public and invites the stupider hackers to look into something they might otherwise not have bothered with. Rather, this type of information should be confined to the administrators who are responsible for maintaining the servers running the compromised code. I suspect the vast majority of servers were patched as soon as security updates were released. Nevertheless, many companies will now collectively spend millions of dollars defending their best practices against those who will simply assume they were irresponsible, all because someone thought it would be "responsible" to sensationalize the matter in the media. Is this a big deal? Yes. Not disputing that. But does the average Joe need to be in this loop? No. This information should be on a need-to-know basis, and server admins should know how to keep abreast of these matters. If a breach has been identified due to a failure to administer a server properly, then the burden of disclosure is on the breached company - as was the case with Target, for instance. IMHO.
  19. The biggest irresponsible act in all of this was leaking it to the media. Sorta like saying, "HEY HACKERS - LOOK, THE FRONT DOOR IS OPEN !! MIGHT AS WELL JUST WALK ON IN..."
  20. Dean, I'm sorry, but I feel the Corsair will disappoint you. I bought an M95 and sent it back. Had to pay the restocking fee, but just could not live with that mouse. Did not fit my hand well, weight was all wrong, cord was just in the way, and it was too slippery in my hand. Oh - and a HUGE dislike - the Corsair does not have a free-wheeling mode on the mouse wheel. I'm sorry, but I just hated it. I've long extolled the delight I have in the Logitech Performance MX mouse. It is simply the best. Fits my hand perfectly, is the perfect weight, is not slippery, free-wheels OR has click-stops on the wheel (wheel locks in/out of free-wheel mode with a button behind the wheel,) and has great configuration software... http://www.amazon.com/Logitech-Wireless-Performance-Mouse-Mac/dp/B002HWRJBM Sounds like you already ordered. Wish you'd have got with me first. I hope the Corsair works out for you.
  21. Aw crap. I'm late to the party. Happy (belated) Birthday!
  22. That totally cracked me up, Labob.
  23. Darwinism Fail.
  24. Go nitro! Hey, I'm a poet.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.