yeah, approximately 3 feet from my pillow is my rack with 4 computers on it, and 2 3com 24 port switches. next to that is my main computer with 5 case fans, 4 SCSI 10k rpm drives, and 2 40GB IDE drives.
That thing is loud as hell (I'm told), but I have trouble sleeping without the fan noise. The fans in the switches alone were enough to bug my ex. I work in the CSL at University of Wisconsin, so I guess I'm accustomed to hearing the fan noise of about 400 computers in the platform, not to mention all the Liebert temp/humidity control devices. I don't even notice anymore.
That's about as ironic as every event in the alanis morrisette song. Perhaps you meant coincidence?
irony ( P ) Pronunciation Key (r-n, r-) n. pl. ironies
1.
1. The use of words to express something different from and often opposite to their literal meaning.
2. An expression or utterance marked by a deliberate contrast between apparent and intended meaning.
3. A literary style employing such contrasts for humorous or rhetorical effect. See Synonyms at wit1.
2.
1. Incongruity between what might be expected and what actually occurs: "Hyde noted the irony of Ireland's copying the nation she most hated" (Richard Kain).
2. An occurrence, result, or circumstance notable for such incongruity. See Usage Note at ironic.
3. Dramatic irony.
4. Socratic irony.
peshtigo is MUCH farther from chicago. It's in northeastern wisconsin. 130 miles of chicago is still south of green bay (approximately plymouth or sheboygan)
peshtigo is actually about 240 miles north.
A bit nitpicky, I know, but I live in Wisconsin, heh.
I suppose I should mention that it's not always that easy. We have a fair amount of homebrew software, and one of the programs is the console app we made which checks the postgres servers and automatically connects you to the port. I suppose otherwise you need to connect to whichever digi/cyclades box and then from there connect to whichever port the computer you want is on. So, it's not that simple by default, but the software to do it is not all that hard to write.
We use them where I work (Computer Systems Lab at the University of Wisconsin CS department) and it is very easy to set up. 95% of the motherboards in all of our sun/red hat boxes have a RS232 connection, and we use a serial-RJ45 convertor (about 2 inches long, connects to the serial port) to connect the ethernet cable from the digi/cyclades console server to the machine.
The computers all connect to one of the digi/cyclades console servers, which in turn are connected to a few computers which handle which computers are on which ports of the digi/cyclades box. So, to console over to a selected server, simply type "console p23" or whatever in a shell. Can't get any simpler than that. Running the wires is simple because you're already running ethernet, and you keep a digi/cyclades "hub" in each rack. Very little extra wiring.
We live by these things. Very useful if sshd dies or whatever. And, you can send breaks to Sun machines!
I would like to think that all the CS admins at UW are pretty good, hehe
DoIT I can't speak for, but some of them do know what they're doing, and some of them don't. In case you're curious at all what our comp sci department is like, there's more info at the CSL Homepage.
There's a lot of info there about the CS department, like all of the instructional labs and stuff like that. It's how a university CS department should be run, hehe.
Actually, that's DoIT (Division of Information Technology)'s job, as they do campus. We just are in charge of computer science. Dave Plonka, the guy who did the write up, actually works for DoIT, not CS. He just decided to host on our server, hehe. They get to deal with the virii from returnign students in the dorms, not us, thank god. We had enough trouble from 1 infected laptop that got onto the wireless. We had already patched everything, though, so didn't really affect much.
Why didn't your organization simply shut down the IP address in question?
That would presumably break all the firmware and would remind the users in no uncertain terms that they need to upgraded to fixed software NOW.
Alternately, it could have told netgear "pick up our bandwidth charges or all that model of router will have to be fixed or replaced."
I see no particular reason to be nice about this, bandwidth costs and netgear is a commercial company that can be expected to pay for its mistakes.
As for anyone else using your server, there are lots of NTP servers out there and changing if yours go down isn't that difficult.
THe problem is, the "DDoS" only occurred when, for whatever unknown reason, the routers weren't getting a time back quickly enough, in which case they would start sending a request a second. Therefore, this would only increase the problem.
Another thing, it wasn't the issue of the machine being overloaded, it was the issue of paying for the bandwith over the pipe. Since the IP address is still owned by UW CS, the data will still come in *plenty* far enough to cost us for bandwith, and then just compound the problem by insuring that the routers won't get valid time responses.
yeah, thinking about it i probably should have just saved the image and hosted it somewhere else, but might as well stress test the cgi server before classes start when it really matters, hehe
Slashdot Mirror
err, informative, which is even funnier.
I'm stupid when I don't get enough sleep...
I think the funniest thing about your retort is it got modded +1, insightful, haha
It's not like the government is infringing on your right to wear short sleeve t-shirts.
Or did you mean to _bear_ arms?
wahahaha!
I'm here every night folks. Be sure to tip your waitress.
Great, now we can have a new slashdot troll...
"FAT is dead anyways!"
Wasn't that Dell?
I might have given it one of my current mod points if you had gotten the quote right, you tool.
Sheesh.
yeah, approximately 3 feet from my pillow is my rack with 4 computers on it, and 2 3com 24 port switches. next to that is my main computer with 5 case fans, 4 SCSI 10k rpm drives, and 2 40GB IDE drives.
That thing is loud as hell (I'm told), but I have trouble sleeping without the fan noise. The fans in the switches alone were enough to bug my ex. I work in the CSL at University of Wisconsin, so I guess I'm accustomed to hearing the fan noise of about 400 computers in the platform, not to mention all the Liebert temp/humidity control devices. I don't even notice anymore.
hmm, perhaps. I still think it's more of a coincidence that you had a verisign ad up rather than irony, but it doesnt really matter.
I'll leave the semantics games to my english major mother, heh.
That's about as ironic as every event in the alanis morrisette song. Perhaps you meant coincidence?
irony ( P ) Pronunciation Key (r-n, r-)
n. pl. ironies
1.
1. The use of words to express something different from and often opposite to their literal meaning.
2. An expression or utterance marked by a deliberate contrast between apparent and intended meaning.
3. A literary style employing such contrasts for humorous or rhetorical effect. See Synonyms at wit1.
2.
1. Incongruity between what might be expected and what actually occurs: "Hyde noted the irony of Ireland's copying the nation she most hated" (Richard Kain).
2. An occurrence, result, or circumstance notable for such incongruity. See Usage Note at ironic.
3. Dramatic irony.
4. Socratic irony.
well, nothing, except that the grandparent post said that 18 year olds could BUY beer.
Yeah. If you don't put a heatsink on it that thing will burn out way too quickly.
peshtigo is MUCH farther from chicago. It's in northeastern wisconsin. 130 miles of chicago is still south of green bay (approximately plymouth or sheboygan)
peshtigo is actually about 240 miles north.
A bit nitpicky, I know, but I live in Wisconsin, heh.
or enjoy things.
I suppose I should mention that it's not always that easy. We have a fair amount of homebrew software, and one of the programs is the console app we made which checks the postgres servers and automatically connects you to the port. I suppose otherwise you need to connect to whichever digi/cyclades box and then from there connect to whichever port the computer you want is on. So, it's not that simple by default, but the software to do it is not all that hard to write.
Check out these Digi Console Servers and also these Cyclades console servers
We use them where I work (Computer Systems Lab at the University of Wisconsin CS department) and it is very easy to set up. 95% of the motherboards in all of our sun/red hat boxes have a RS232 connection, and we use a serial-RJ45 convertor (about 2 inches long, connects to the serial port) to connect the ethernet cable from the digi/cyclades console server to the machine.
The computers all connect to one of the digi/cyclades console servers, which in turn are connected to a few computers which handle which computers are on which ports of the digi/cyclades box. So, to console over to a selected server, simply type "console p23" or whatever in a shell. Can't get any simpler than that. Running the wires is simple because you're already running ethernet, and you keep a digi/cyclades "hub" in each rack. Very little extra wiring.
We live by these things. Very useful if sshd dies or whatever. And, you can send breaks to Sun machines!
I believe those are the meta keys, which do have many functions in emacs and the like.
Thanks for spelling that out, Captain Obvious.....
I hadn't noticed as you hav for sure seen........
I hav looked the picture over and I havn't noticed any typos.
Hav i missed something?
whoa!
she spelled fhqwhgads right!
I would like to think that all the CS admins at UW are pretty good, hehe
DoIT I can't speak for, but some of them do know what they're doing, and some of them don't.
In case you're curious at all what our comp sci department is like, there's more info at the CSL Homepage.
There's a lot of info there about the CS department, like all of the instructional labs and stuff like that. It's how a university CS department should be run, hehe.
Actually, that's DoIT (Division of Information Technology)'s job, as they do campus. We just are in charge of computer science. Dave Plonka, the guy who did the write up, actually works for DoIT, not CS. He just decided to host on our server, hehe. They get to deal with the virii from returnign students in the dorms, not us, thank god. We had enough trouble from 1 infected laptop that got onto the wireless. We had already patched everything, though, so didn't really affect much.
THe problem is, the "DDoS" only occurred when, for whatever unknown reason, the routers weren't getting a time back quickly enough, in which case they would start sending a request a second. Therefore, this would only increase the problem.
Another thing, it wasn't the issue of the machine being overloaded, it was the issue of paying for the bandwith over the pipe. Since the IP address is still owned by UW CS, the data will still come in *plenty* far enough to cost us for bandwith, and then just compound the problem by insuring that the routers won't get valid time responses.
yeah, thinking about it i probably should have just saved the image and hosted it somewhere else, but might as well stress test the cgi server before classes start when it really matters, hehe
I am a network admin, heh.
The load is fine. It's already subsiding. We can handle slashdottings, heh.
Look at the weekly graph, we had 2 this week already!
Just slows down for a while, but doesn't break anything.