It's certainly better to block the server by having the ISP take it down, but there are other ways to do it.
Other ISPs can block IP addresses or address ranges from accessing their users, and getting the few big cable modem and DSL providers to block the botnet's servers doesn't require cooperation of the ISP hosting the servers. (The inefficient way to do blocking is to use Access Control Lists; it's simpler to just route the addresses to a blackhole.)
If the botnet servers' ISP's upstream provider will cooperate with you about blocking those addresses, that's even more efficient, but harder to get cooperation - the miscreant ISPs probably have multiple upstreams, at least some of whom aren't very attentive about security (either through malice or incompetence.)
The evil way to do it is to use BGP to advertise the servers' addresses yourselves, if your ISP is willing to allow it. If applied often, this leads to chaos, so it's much cleaner to have ISPs block the addresses to protect their users.
Unfortunately, it's probably harder for these things to detect boredom vs. interest than simpler emotions, but it would be cool if you could set it so your player runs faster when you're bored and slower when you're interested (and there are already sound-adjuster programs out there so you can run faster or slower without distorting the sound pitch badly.)
You want to use this in interactive mode, not batch, so it's reacting to what you're interested in or bored about now, not what you felt about it last time. WAIT! WHAT? BACKUP! No, not that far - Yeah, there!
There have been a couple of products like this out there on the market, with varying numbers and locations of sensors. Some of them are doing EEG type detection to try to see what your brain is doing, while others are mostly sensing facial muscles. It's hard to keep track of which products are which, especially when they're initially marketed toward gamers because they think that's a potential market.
If this is the one doing actual brain behaviour detection, and if the SDK weren't so expensive*, it'd be fun to use for things like neurofeedback experimentation. On the other hand, if it's yet another facial muscle detector, that's less interesting to me, but probably easier to program to do useful things for gamers.
As far as I can tell from the UK press, binge drinking is actually much more of a problem in the UK than in the US - over here it's most college students that do it, while in the UK it's common for actual grown-up adults to go get rat-arsed on a frequent basis.
If you happen to find one of these devices on your car, since the cops didn't need any legal authority to put it there, it must be an unsolicited gift -and there are laws about those already. You're not legally obligated to pay for it, or return it if you don't want it, but it's yours anyway.
So regift it to somebody deserving, like your mayor, or your town garbage truck. Or you could disassemble it and find out how it works, maybe modify it to transmit different data?
Thanks - the LGV Mediterranee hadn't opened when I last took TGV:-) 400 miles / 650 km is a reasonable car route distance, but the railroads have some slightly weird existing routes that make the actual distance somewhat longer.
The objective in boxing is to cause sufficient brain trauma to your opponent that he loses consciousness or can no longer stand up. That's not a sport, that's barbarism, and has no business in a civilized society. the short term, it's highly dangerous, and in the long term it can turn you into what's left of Muhammad Ali.
By contrast, wrestling is a real sport, in spite of the fact that professional boxing is for real and professional wrestling is as much fake showmanship as sport. (And yes, just because it's fake doesn't mean than any of those guys can't throw my ass out of the ring, and look good doing it.)
California voters approved a high-speed rail ballot initiative recently that would build really high-speed trains from San Francisco to LA to San Diego, and also to points in between and Sacramento. The initiative approved $10Billion in bonds for construction - but the official estimated cost was about $30B, and the followup Oops-you-mean-the-WHOLE-Cost cost was about $40B, so they're depending on $30B of Federal money to magically fall from the sky. They've gotten approval for something like $2B of that $8B the Feds want to spend in the whole country, but they'll need a lot more. So the finances have been a total crock from the beginning.
By the way, the route from San Francisco to LA alone is longer than the TGV from Paris to Bordeaux, which is about the longest of the French TGV routes. (The highway distance would be a bit shorter, but the existing train routes across the mountains make the actual route zig-zag for a longer distance.)
I don't think you mean Marin County NIMBYs, though -that's across the Golden Gate Bridge from San Francisco, and there's no obvious way to get a train across the bridge. There are lots of NIMBYs around Atherton and Menlo Park who don't want the train going down the Peninsula, or at least not near them, or hidden in underground tunnels. There have also been arguments about whether the route from San Jose should go south first, or should go up the East Bay and east before heading south, but that's been people who want the train to go near them, not people who don't want it.
Maybe the cellphone carriers or other specialized environments will limit you to one IP address per service, but that battle was long since abandoned by major broadband ISPs, even the really anal-retentive ones that don't let you run home web servers, as people started having networked printers and NAT routers so they could have their kids' computers or their Wifi devices at home.
IPv6 isn't going to bring that back. Some ISPs may only give you a/64 prefix, as opposed to a/56 or some ugliness like a/60, but nobody serious is going to restrict what happens inside the/64.
If ISPs see spam, they'll probably block your whole/64 or/56 rather than individual IPv6 addresses (and if they don't, the spammers will start using IPv6 privacy options so each piece of spam has a different host address, so they'll have to do it soon enough anyway.)
The original goal of stateless autoconfiguration looked so nice and clean back the early 1990s - it was one of the really nice features of Novell Netware IPX. You just plug in your box, it sees a router announcement so it knows the network and subnet portion of its address, and the host portion was a padded version of the MAC address (and sorry about the ugliness when they switched from 48-bit MAC to 64-bit EUI-64, because it made the subnet length part of the ISP's problem, rather than the end users, but it's still close enough.) IP didn't have that, but we got that same level of convenience when DHCP came out, plus or minus some nitpicking.
But you don't need to use the simple stateless auto-config - there are privacy-protecting variations that let your PC pick a new 64-bit host portion for every connection it initiates instead of always using the MAC-based EUI-64. So Google can't track how many machines you've got at home simply by counting the MAC addresses in your/64 block.
The main benefit of assigning dynamic IP addresses to consumer-like end users is that it's a lot easier to administer them - you don't have to explain to the user how to configure the static IP address into their router, or deal with the help desk call when they change something in their Windows 98 box or networked laser printer or 68030 Macintosh or Linux machine that's using KDE instead of GNOME or whatever. You tell them "Plug it on, watch the lights blink, DHCP magic happens, you're done."
There's also the benefit that people only use as many IP addresses as they need, as opposed to configuring as many as they think they *might* need in the future. (So yeah,. I'm not using all 8 of my static addresses, but it was only $5/month more than dynamic addressing.)
The problem isn't just your SOHO router, though that's actually a very big problem for ISPs. And the problem isn't just ISP and enterprise routers that are much slower at routing IPv6 than IPv4 (the longer address space is a problem even if you weren't using ASICs to do the routing, which you were.) And the problem isn't just application systems like MySQL that don't have native IPv6 address handling APIs.
Think about every application you've ever written that stores IPv4 addresses in a 32-bit integer, either in working variables or in databases, or displays them to a user as a 15-character dotted-quad string, or sends an A-record query to a DNS server to get an IP address, and every application your ISP might be using to keep track of what equipment is where with what addresses on it, and every network management application your company or ISP is using to monitor equipment health or configuration. Now go fix them all to store both IPv4 and IPv6 addresses. Preferably before the people who want to access your website only have IPv6 at home.
Right now if you're paying too much money to get static IP addresses, it's because your ISP wants lower administrative costs or simply thinks you can be conned into paying more for perceived value, not because you're using fewer IP addresses than if you had dynamic addressing. (Unless you're using dialup connectivity, of course, but really, it's not 1995 any more.)
If you have to start paying through the nose to get N IPv4 addresses, where N>=1, that'll be because unassigned IPv4 addresses will have run out. They'll be no more, they'll have ceased to be, they'll have shuffled off this mortal coil, they'll be ex-addresses, they'll not only have been pinging for the fjords, but they'll have sailed so far off into the sunset that they've crashed into the "Here Be Dragons" sign and fallen off the Edge where they can see the elephants and the giant space turtle. Of course, just because there aren't any more unassigned addresses, that doesn't mean you won't be able to rent them from people who have spares, in spite of whatever restrictions are thought to exist on official ownership of the space, because the things are fungible, and companies will find ways to funge the ones that aren't, and will charge money for doing so.
And yeah, IPv4 internal-use addresses are going to stick around for decades - there are probably still people using Netware IPX in production systems. But they'll have to support IPv6 on the edges, because there will be ISPs that are only giving their end users IPv6 addresses, and aren't necessarily using 6to4 NATs to reach the IPv4 world, and you may want to let some of those eyeballs reach your servers.
You're confused about both VPNs and SIP. VPNs are for privacy, not just for carrying your own RFC1918 address space around. Ostensibly you could get the privacy with IPv6's security features, but VPNs make it much cleaner and provide fine-grained access control.
SIP is a connection setup and management protocol. You need that even if everybody's in the same IPv4 address space, like back in the days before NAT and RFC1918, to provide connection management functions, name and number translation, and access management. It's a lot more complex than just DNS. My PBX at work knows where the phones are, knows how to translate between phone numbers I dial on my phone and IP addresses for other PBXs in my company, knows that if somebody calls me and I'm busy that it should redirect my call to voice mail, knows how to translate to public telephone network numbering, knows how to negotiate codecs, and knows how to do things like not put 500 phone calls on a single T1 phone line at the same time, and does all of this using SIP (or earlier VOIP protocols such as H.323 or vendor proprietary protocols like SCCP.) SIP also knows how to negotiate with other SIP servers, so my company's PBX can talk to some other company's PBX even though they're not managed by the same people.
When you said SIP, were you thinking of SKYPE instead? Their claim to fame was that they did NAT and firewall traversal very well and very aggressively. But just getting rid of NAT because you've got IPv6 doesn't change 90% of its functionality.
Also, IPv6 doesn't provide a universal global address space. Ok, it does provide one of those, but it also provides several kinds of local address spaces, so if you want a private network for privacy reasons, or if you just want to hook a couple of boxes together without getting IPv6 addresses from ICANN and routing them to the public Internet, you can do that too.
The Internet lets everybody in the world talk to each other, faster and more flexibly than before. So yes, that's going to change language, because people who would have never talked to each other are doing so, and people who had obscure things to talk about can find other people to talk about them with that they wouldn't have before.
Yes, there's been a movie named that out since 1981, and that's made it very hard to get the actual movie "Star Wars" any more. Han shot first, Jabba looked different, various other scenes were later "improved", etc.
I don't remember exactly what the sign said, but it did use both terms, and probably on purpose - you have to expect that somewhere in the world there's somebody with the skill to do that, even if it's sadly rare. Probably somebody who even reads books...
It's the parking meters in San Francisco getting that one wrong that really irk me (especially since you know you couldn't fight a parking ticket by claiming that you didn't violate what the sign actually said the rules were.)
Slashdot Mirror
It'll go back to being named Candlestick\\\\\\\\\\ Sears Point...
It's certainly better to block the server by having the ISP take it down, but there are other ways to do it.
Teh Intertubes aren't blocked, they're just connected up differently. Kind of like if it were trucks and you put up detour signs.
Unfortunately, it's probably harder for these things to detect boredom vs. interest than simpler emotions, but it would be cool if you could set it so your player runs faster when you're bored and slower when you're interested (and there are already sound-adjuster programs out there so you can run faster or slower without distorting the sound pitch badly.)
You want to use this in interactive mode, not batch, so it's reacting to what you're interested in or bored about now, not what you felt about it last time. WAIT! WHAT? BACKUP! No, not that far - Yeah, there!
There have been a couple of products like this out there on the market, with varying numbers and locations of sensors. Some of them are doing EEG type detection to try to see what your brain is doing, while others are mostly sensing facial muscles. It's hard to keep track of which products are which, especially when they're initially marketed toward gamers because they think that's a potential market.
If this is the one doing actual brain behaviour detection, and if the SDK weren't so expensive*, it'd be fun to use for things like neurofeedback experimentation. On the other hand, if it's yet another facial muscle detector, that's less interesting to me, but probably easier to program to do useful things for gamers.
As far as I can tell from the UK press, binge drinking is actually much more of a problem in the UK than in the US - over here it's most college students that do it, while in the UK it's common for actual grown-up adults to go get rat-arsed on a frequent basis.
Hmmm, something botched when I first posted this...
Yeah, those crazy liberals in the 9th circuit - next thing you know they'll be mandating gay marriage for everybody and webcams in the bedroom.
First it's this, and next thing you know they'll be mandating gay marriage or something.
Legally, it's an unsolicited gift, and if the spammers just hand-delivered it instead of snail-mailing it, well, fine.
If you happen to find one of these devices on your car, since the cops didn't need any legal authority to put it there, it must be an unsolicited gift -and there are laws about those already. You're not legally obligated to pay for it, or return it if you don't want it, but it's yours anyway.
So regift it to somebody deserving, like your mayor, or your town garbage truck. Or you could disassemble it and find out how it works, maybe modify it to transmit different data?
Thanks - the LGV Mediterranee hadn't opened when I last took TGV :-) 400 miles / 650 km is a reasonable car route distance, but the railroads have some slightly weird existing routes that make the actual distance somewhat longer.
Yes, but it makes a huge difference to ISPs, which is the point.
The objective in boxing is to cause sufficient brain trauma to your opponent that he loses consciousness or can no longer stand up. That's not a sport, that's barbarism, and has no business in a civilized society. the short term, it's highly dangerous, and in the long term it can turn you into what's left of Muhammad Ali.
By contrast, wrestling is a real sport, in spite of the fact that professional boxing is for real and professional wrestling is as much fake showmanship as sport. (And yes, just because it's fake doesn't mean than any of those guys can't throw my ass out of the ring, and look good doing it.)
California voters approved a high-speed rail ballot initiative recently that would build really high-speed trains from San Francisco to LA to San Diego, and also to points in between and Sacramento. The initiative approved $10Billion in bonds for construction - but the official estimated cost was about $30B, and the followup Oops-you-mean-the-WHOLE-Cost cost was about $40B, so they're depending on $30B of Federal money to magically fall from the sky. They've gotten approval for something like $2B of that $8B the Feds want to spend in the whole country, but they'll need a lot more. So the finances have been a total crock from the beginning.
By the way, the route from San Francisco to LA alone is longer than the TGV from Paris to Bordeaux, which is about the longest of the French TGV routes. (The highway distance would be a bit shorter, but the existing train routes across the mountains make the actual route zig-zag for a longer distance.)
I don't think you mean Marin County NIMBYs, though -that's across the Golden Gate Bridge from San Francisco, and there's no obvious way to get a train across the bridge. There are lots of NIMBYs around Atherton and Menlo Park who don't want the train going down the Peninsula, or at least not near them, or hidden in underground tunnels.
There have also been arguments about whether the route from San Jose should go south first, or should go up the East Bay and east before heading south, but that's been people who want the train to go near them, not people who don't want it.
Maybe the cellphone carriers or other specialized environments will limit you to one IP address per service, but that battle was long since abandoned by major broadband ISPs, even the really anal-retentive ones that don't let you run home web servers, as people started having networked printers and NAT routers so they could have their kids' computers or their Wifi devices at home.
IPv6 isn't going to bring that back. Some ISPs may only give you a /64 prefix, as opposed to a /56 or some ugliness like a /60, but nobody serious is going to restrict what happens inside the /64.
If ISPs see spam, they'll probably block your whole /64 or /56 rather than individual IPv6 addresses (and if they don't, the spammers will start using IPv6 privacy options so each piece of spam has a different host address, so they'll have to do it soon enough anyway.)
The original goal of stateless autoconfiguration looked so nice and clean back the early 1990s - it was one of the really nice features of Novell Netware IPX. You just plug in your box, it sees a router announcement so it knows the network and subnet portion of its address, and the host portion was a padded version of the MAC address (and sorry about the ugliness when they switched from 48-bit MAC to 64-bit EUI-64, because it made the subnet length part of the ISP's problem, rather than the end users, but it's still close enough.) IP didn't have that, but we got that same level of convenience when DHCP came out, plus or minus some nitpicking.
But you don't need to use the simple stateless auto-config - there are privacy-protecting variations that let your PC pick a new 64-bit host portion for every connection it initiates instead of always using the MAC-based EUI-64. So Google can't track how many machines you've got at home simply by counting the MAC addresses in your /64 block.
The main benefit of assigning dynamic IP addresses to consumer-like end users is that it's a lot easier to administer them - you don't have to explain to the user how to configure the static IP address into their router, or deal with the help desk call when they change something in their Windows 98 box or networked laser printer or 68030 Macintosh or Linux machine that's using KDE instead of GNOME or whatever. You tell them "Plug it on, watch the lights blink, DHCP magic happens, you're done."
There's also the benefit that people only use as many IP addresses as they need, as opposed to configuring as many as they think they *might* need in the future. (So yeah,. I'm not using all 8 of my static addresses, but it was only $5/month more than dynamic addressing.)
The problem isn't just your SOHO router, though that's actually a very big problem for ISPs.
And the problem isn't just ISP and enterprise routers that are much slower at routing IPv6 than IPv4 (the longer address space is a problem even if you weren't using ASICs to do the routing, which you were.)
And the problem isn't just application systems like MySQL that don't have native IPv6 address handling APIs.
Think about every application you've ever written that stores IPv4 addresses in a 32-bit integer, either in working variables or in databases, or displays them to a user as a 15-character dotted-quad string, or sends an A-record query to a DNS server to get an IP address, and every application your ISP might be using to keep track of what equipment is where with what addresses on it, and every network management application your company or ISP is using to monitor equipment health or configuration. Now go fix them all to store both IPv4 and IPv6 addresses. Preferably before the people who want to access your website only have IPv6 at home.
Right now if you're paying too much money to get static IP addresses, it's because your ISP wants lower administrative costs or simply thinks you can be conned into paying more for perceived value, not because you're using fewer IP addresses than if you had dynamic addressing. (Unless you're using dialup connectivity, of course, but really, it's not 1995 any more.)
If you have to start paying through the nose to get N IPv4 addresses, where N>=1, that'll be because unassigned IPv4 addresses will have run out. They'll be no more, they'll have ceased to be, they'll have shuffled off this mortal coil, they'll be ex-addresses, they'll not only have been pinging for the fjords, but they'll have sailed so far off into the sunset that they've crashed into the "Here Be Dragons" sign and fallen off the Edge where they can see the elephants and the giant space turtle. Of course, just because there aren't any more unassigned addresses, that doesn't mean you won't be able to rent them from people who have spares, in spite of whatever restrictions are thought to exist on official ownership of the space, because the things are fungible, and companies will find ways to funge the ones that aren't, and will charge money for doing so.
And yeah, IPv4 internal-use addresses are going to stick around for decades - there are probably still people using Netware IPX in production systems. But they'll have to support IPv6 on the edges, because there will be ISPs that are only giving their end users IPv6 addresses, and aren't necessarily using 6to4 NATs to reach the IPv4 world, and you may want to let some of those eyeballs reach your servers.
You're confused about both VPNs and SIP. VPNs are for privacy, not just for carrying your own RFC1918 address space around. Ostensibly you could get the privacy with IPv6's security features, but VPNs make it much cleaner and provide fine-grained access control.
SIP is a connection setup and management protocol. You need that even if everybody's in the same IPv4 address space, like back in the days before NAT and RFC1918, to provide connection management functions, name and number translation, and access management. It's a lot more complex than just DNS. My PBX at work knows where the phones are, knows how to translate between phone numbers I dial on my phone and IP addresses for other PBXs in my company, knows that if somebody calls me and I'm busy that it should redirect my call to voice mail, knows how to translate to public telephone network numbering, knows how to negotiate codecs, and knows how to do things like not put 500 phone calls on a single T1 phone line at the same time, and does all of this using SIP (or earlier VOIP protocols such as H.323 or vendor proprietary protocols like SCCP.) SIP also knows how to negotiate with other SIP servers, so my company's PBX can talk to some other company's PBX even though they're not managed by the same people.
When you said SIP, were you thinking of SKYPE instead? Their claim to fame was that they did NAT and firewall traversal very well and very aggressively. But just getting rid of NAT because you've got IPv6 doesn't change 90% of its functionality.
Also, IPv6 doesn't provide a universal global address space. Ok, it does provide one of those, but it also provides several kinds of local address spaces, so if you want a private network for privacy reasons, or if you just want to hook a couple of boxes together without getting IPv6 addresses from ICANN and routing them to the public Internet, you can do that too.
The Internet lets everybody in the world talk to each other, faster and more flexibly than before. So yes, that's going to change language, because people who would have never talked to each other are doing so, and people who had obscure things to talk about can find other people to talk about them with that they wouldn't have before.
Yes, there's been a movie named that out since 1981, and that's made it very hard to get the actual movie "Star Wars" any more.
Han shot first, Jabba looked different, various other scenes were later "improved", etc.
I don't remember exactly what the sign said, but it did use both terms, and probably on purpose - you have to expect that somewhere in the world there's somebody with the skill to do that, even if it's sadly rare. Probably somebody who even reads books...
It's the parking meters in San Francisco getting that one wrong that really irk me (especially since you know you couldn't fight a parking ticket by claiming that you didn't violate what the sign actually said the rules were.)
I see that one done wrong way too often.
They usually do stuff that's more delicate than Klingon opera, but with a couple of extra percussion players they should be up for the job.