Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Two things you can do now (Score 1) 312

by whitelabrat (#48707527) Attached to: Ask Slashdot: What Should We Do About the DDoS Problem?

If you're a home user not much you can do aside from releasing and renewing your IP. I work for supporting a fast growing SaaS product and I've had to do my homework on this.

Two things:

1. Make sure your edge firewall / router has a high Packets Per Second capability. A DDoS attack may not involve a lot of bandwidth but rather send a boatload of packets at you. Your edge network will need to process it all, and if it can't you start dropping packets for things you want and don't want.

2. Out bandwidth 'em. I've not tried it, but I'm interested in Akamai PLXrouted service. In a nutshell if you get a bandwidth attack you adjust your BGP routes to push traffic though Akamai, who can provide Terabits of shitfilter for you. DDoS zero, you win. Or cloud it, using Amazon EC2 as a filter with a bunch of proxy instances that self heal if they get knocked out.

Comment: Re:IPv6 Addresses (Score 2) 305

by whitelabrat (#47222663) Attached to: When will large-scale IPv6 deployment happen?

IPv6 sort of demands that you forget everything you know about IPv4. Once you get IPv6, you'll ask yourself why anybody still uses IPv4. For example.

There are more /48 networks in IPv6 space than there are IPv4 addresses. Everybody ought to get a /48 network which include 18 quintillion addresses. The first part of the a global unicast address is often referred to as a prefix and all your IP's will have that. The second part may be derived from you NIC's MAC. So there is some good sense to it.

You'll really want to use DNS.

I'm using IPv6 at home and work now and think its time is way overdue.

Comment: Re:Teamwork (Score 1) 455

by whitelabrat (#42998913) Attached to: Why Working Remotely Needs To Make a Comeback

I absolutely agree. In a work environment where collaboration and communication are needed to reach an end goal, telework sucks. The latency and opportunity for misunderstanding are strong. I've been able to hash out more in an hour over a few pints than in several week over email or chat. Just saying. There's a lot to be said for hearing your peer's ideas and for being able to challenge each other in person. Email totally sucks ass, because it's not a conversation. It's one way.

Not to say that being the office is always awesome either. In an undisciplined office environment, constant interrupts can ruin productivity. If everyone respects each other and trusts them to get the job done then it can be cool.

Theory is gray, but the golden tree of life is green. -- Goethe