bar.com has existed for a very long time. The owner used to read every email coming in to foo@bar.com, but gave it up long ago -- "The internet has no sense of humor."
Depends on the manufacturer. VW has been doing this for a long time. Based on the security tag for my bug, I don't think anyone is going to guess the immobilizer code in my lifetime.
And FTA, these guys aren't technically breaking in. They are using *your* key while it's still in your possesion by building a wireless bridge to make it look like the key is near the car. For cars that acutally track the key -- and thus know how far away it is, this trick doesn't work so well. For example, (back to my bug) I can lock the car from over 100ft away, however, I have to be within 30ft to unlock it. (and the "pill" has to stay within a few inches of the key because the immobilizer periodocly reverifies it.) In my lexus (completely keyless), the fob has to be *inside* the car at all times or it will not move -- it'll park and ignore the accelerator. (I don't know what it would do if I threw to key out the window going down the road.)
Nothing ever gets "trashed", esp. functioning network gear. So until those hubs fail, they continue to be used. 20 year old pix firewalls continue to get used. Cisco routers the 20-somethings have never heard of are still pushing packets. Even today, in the software dev world, I don't get to "trash" anything that isn't broken -- or in the case of desktops/servers, something so obsolete it's hindering productivity (and even then it's an uphill battle.)
"Just use a linux box" is not something upper management likes to hear. It's better received today, but still not the answer to everything. It's only appeal is the superior cheapness. Even a pure crap PC has a processor hundreds of times faster than Cisco's general purpose CPU (because it's not designed for heavy lifting.)
FWIW, network performance was not the horror you may think it was. It wasn't hubs plugged into hubs, or huge multi-hub stacks. It actually ran quite well -- even after they pushed multicast video into it. (*nod* really. yes a collision is a lost packet.)
Judging from your low UID, you should be aware of auto-negotiation. Even a modern day 1000bT card will happily link and run at 10M/half. (says the guy who looked at his laptop like it was broken when it linked to the Clearwire modem at 10/half. the asses actually built the damn thing with a 10bT port.)
In the end, devices that only support IPv4 and can only be managed via IPv4 will require me to continue running an IPv4 network / stack in order to talk to them. Just like with the IPX printer servers... desktops don't have to run or be aware of IPX, but there's still an IPX network and at least one multi-protocol host to act as a gateway. I'd rather not have to bother.
My point was more about the age of business infrastructure. Some people seem to be under the delusion that companies rip out all their gear every few years. I've never known one that did. eg. the 20 year old 3Com dual stack hubs all over the building. (at the time, they had plenty of spares and 3com would replace the dead ones. however, as we found out with cisco, eventually, the warehouse is going to be empty.) Companies replace things when they have to, and sometimes when they *need* to.
IPv6 in software on most router platforms is best avoided. Those packets are "process switched", which is the worst, slowest possible means of moving packets. In the Cisco world, you can make very expensive gear perform worse than junk if the packets are process switched.
Running a bunch of parallel networks for "legacy gear" is not a great situation. Right now, IPv6 still needs IPv4 to be effective. At some point, systems will be able to function completely on IPv6, and you'll want to remove IPv4 from your network -- entirely. It's not an issue of global reachability; it's an issue of having to run and support 2 networks just for the legacy devices that cannot handle IPv6. (and right now, that's a lot of things... printers, network scanner, network fax, switches, access points, our toshiba phone switch...)
It's a good thing I'm out of Dew or it would've flown out my nose.
Oh hell no they don't. ISPs run shit until it's completely dead. I don't want to think about all the times I've had to go to war to get $10k to upgrade a router -- even then it was someone else's used gear. While many large ISPs have the revenue to support such foolish spending, the people writing the checks aren't nearly as crazy. (besides, if they're spending millions on gear, that's millions not going in their pockets.)
Put another way: Unless the hardware is very new (within a few years), it will most likely handle IPv6 purely in software, with little if any hardware support. This is the slowest of all methods.
While the Cisco ASA lists IPv6 support on paper. Have you actually tried using it? It's a very bad joke. Maybe it's better in 8.3, but I refuse to run that brain damaged crap. Our checkpoint firewalls do not support IPv6, and would have to be completely reinstalled to do so. (the base secureOS -- running linux 2.4 -- has zero support for IPv6.)
Load balancers... some support IPv6, for various definitions. I've not played with any of them to gauge their level of suck.
Bottom line... the move to IPv6 will be expensive, and very messy. And will probablly take another 10 years.
Very few home routers support IPv6 out-of-the-box. And the millions in the field will almost certainly never see a firmware update to support IPv6. (it's more profitable to make you buy a new one.)
I know of no broadband ISP that is openly providing IPv6 service to residential customers (in the US.) Comcast has a "trial program", and at last report, it's closed to new participants. Earthlink had a pilot program that was abandoned after laying off the one engineer running it. Getting native IPv6 connectivity from *business* connections is still spotty.
Google is not the entire internet. While saying there are *no* websites in IPv6 is obviously wrong, most of the places people go everyday are not reachable via IPv6 only. (unless you're in china.)
Since when does a linksys router have any other interface than the web ui? There's no serial port on them (unless you make your own.) And they don't do telnet or ssh.
(Replacing the firmware with DD-WRT, OpenWRT, Tomato, etc. doesn't count.)
Really? I know at least one company that's still using 20 year old *hubs*. Yes, h.u.b.s.!!! And Cisco gear so old, Cisco refunded the support contracts after having to replace one. ("oh shit, we don't have any of those.") (this company still uses IPX print servers, btw. HP never made IP firmware for them.) I'm using gear that's been EOL/EOS for 5+ years now... don't break what's working. I'll have to replace it to support IPv6 at any realistic speeds. (IPv6 is handled entirely in software.)
Anything that has to be managed needs to support IPv6. Or your network becomes a huge f'ing mess. I've been there... appletalk, ipx, and IP on the same network.
"upgrade the software" is a fine thing to tell yourself. However, in the real world, there are devices that will never support IPv6 because the company that made it won't upgrade it, no longer exists, or was bought out and abandoned the thing. (I have stuff in all of those categories.)
Saying Windows XP (which a great many people and companies STILL RUN) supports IPv6 is laughable. It was and still is, EXPERIMENTAL. And does not meet any of the modern standards for IPv6. (IPv6 as an idea has been around for ~15 years. The protocol specifications (RFCs) systems follow today are only a few years old. And still changing.)
Anyway, there's a great deal more involved than just "the OS supports it." Applications have to support it. Numerous bits of hardware have to support it -- firewalls, routers, switches, print servers, printers, access points, ntp clocks, phones, etc, etc, etc. And yes, routers need to be REPLACED to fully support IPv6; the software switching performance of even uber routers is complete crap. And most importantly... your ISP(s) have to support it. (neither of my broadband connections (TWC and Bellsouth) support IPv6. Neither do clearwire or FiOS.)
Why, then, have Visa and MasterCard refused to do business with the (still completely legal, as far as I'm aware) website Because they do not want to be associated with actions of that website. (and releasing classified information is illegal.)
Why have bank accounts been frozen? His Swiss account(s) were "seized", not frozen. I would presume to make it harder for him to continue to elude arrest.
Why have PayPal cut off their account? Simple... they're paypal. In case you've never noticed, paypal will lock an account simply because you looked at them wrong.
Why have their web hosts and DNS provider given them the cold shoulder? Same reason as Visa and Mastercard... to get as far away from the poisoned fruit as possible.
Why do leading US politicians advocate cold blooded murder by government troops? There are many reasons. They should be obvious to you.
Why are US legislators promising to change the law to make his journalistic, first amendment protected actions retroactively against the law? Technically, what wikileaks is doing is not "journalism". Scanning documents into pdfs and placing them on a web site is not journalism.
And how the hell is that supposed to work? If it's jamming the signal, you have "zero bars" and cannot make any calls; thus nothing will know you're trying to call 911. It's not like E911 is on a different frequency. If the technology is "jamming" by intercepting your phone, then you're breaking several laws. Plus the device would have to be built to talk to every oddball proprietary cell technology licensed in the country -- at the same time. (and be precisely tuned to function over a distance of 2ft.) And then, the crap could (read: eventually WOULD) malfunction, usually as a result of a crash, not cut out in an accident/while parked/etc., or go nuts and jam everything within a half mile. (cell phones, police radios, radio and tv broadcasts,...)
Since when do they have DOCSIS 3 gear in Shelby? (answer THEY DON'T) Charlotte has limited D3 rollout. Gastonia is next down the line from CLT. THEN Shelby. Judging by their past record, don't expect D3 until 2015. (2 years ago they still didn't have SDV gear in Shelby and were still handing out single stream cablecards.)
It's a DATA CENTER. So, the only thing going on there will be network and system maintenance. I doubt there will be any "engineering" done there at all. Which means the few dozen jobs it creates will be for 30-40k/yr button pushers.
To be fair, there are a lot of IT professionals in NC. They just aren't in Forest City; and if they ever were, they left a long time ago when most of the businesses (i.e. mills) went bust.
According to several studies, NC ranks poorly in education. Not the worst, but near enough to count as "close to it." Your bonus is getting to keep your job. (trust me, if your students consistently test low, you will be out of a job.)
[NC public education is mostly about politics and personal agendas, not actually educating anyone. Many parents treat it as government daycare.]
I've seen it happen when Windows Update(tm) replaces the network driver and the system then thinks it's a new card. All sorts of odd/interesting things happen on the next reboot.
mDNS, et. al. are nice... if www.yahoo.com happens to be on the local link. mDNS is NOT a complete replacement for traditional (unicast) DNS. SLAAC is lightyears from what DHCP has provided for years.
Please, remove IPv4 from your network(s). Run 100% pure IPv6. You'll learn what many others have known for years... the "utopia" that IPv6 is supposed to be, *isn't*. Without something filling in your DNS servers -- for GLOBAL name resolution, you're not going to get very far.
DHCPv6 is certainly available for you to use, although you now have the option of not needing it.
Wrong. RA provides only a prefix (which MUST be/64 for SLAAC) and gateway (i.e. the thing sending the RA.) That is "all you need" today because IPv4 is filling in the rest of the equation... hostname, domain name, nameservers, etc. Turn off IPv4 and you quickly see how much is left out. Modern systems depend on a lot more than just an address to function productively.
The first gen AU9(?) was 35lbs. A single LNB oval dish (plus LNB) is a little more than 5lbs. The monster DISH Pro/1000 thing is 30-40lbs. (and a real pain in the ass to aim.)
It does have to be aimed in roughly the right direction. However, it does not require precise tuning. I've used a BGAN system that used a tiny, flat receiver... you just have to get it close for it to work.
Slashdot Mirror
There's a really big distinction here... you knew when you were dialing a long distance number because you had to enter 1 plus the area code.
(Today, not so much... 7 digit extended area dialing, 10 digit overlays, etc.)
bar.com has existed for a very long time. The owner used to read every email coming in to foo@bar.com, but gave it up long ago -- "The internet has no sense of humor."
Depends on the manufacturer. VW has been doing this for a long time. Based on the security tag for my bug, I don't think anyone is going to guess the immobilizer code in my lifetime.
And FTA, these guys aren't technically breaking in. They are using *your* key while it's still in your possesion by building a wireless bridge to make it look like the key is near the car. For cars that acutally track the key -- and thus know how far away it is, this trick doesn't work so well. For example, (back to my bug) I can lock the car from over 100ft away, however, I have to be within 30ft to unlock it. (and the "pill" has to stay within a few inches of the key because the immobilizer periodocly reverifies it.) In my lexus (completely keyless), the fob has to be *inside* the car at all times or it will not move -- it'll park and ignore the accelerator. (I don't know what it would do if I threw to key out the window going down the road.)
Nothing ever gets "trashed", esp. functioning network gear. So until those hubs fail, they continue to be used. 20 year old pix firewalls continue to get used. Cisco routers the 20-somethings have never heard of are still pushing packets. Even today, in the software dev world, I don't get to "trash" anything that isn't broken -- or in the case of desktops/servers, something so obsolete it's hindering productivity (and even then it's an uphill battle.)
"Just use a linux box" is not something upper management likes to hear. It's better received today, but still not the answer to everything. It's only appeal is the superior cheapness. Even a pure crap PC has a processor hundreds of times faster than Cisco's general purpose CPU (because it's not designed for heavy lifting.)
FWIW, network performance was not the horror you may think it was. It wasn't hubs plugged into hubs, or huge multi-hub stacks. It actually ran quite well -- even after they pushed multicast video into it. (*nod* really. yes a collision is a lost packet.)
Judging from your low UID, you should be aware of auto-negotiation. Even a modern day 1000bT card will happily link and run at 10M/half. (says the guy who looked at his laptop like it was broken when it linked to the Clearwire modem at 10/half. the asses actually built the damn thing with a 10bT port.)
In the end, devices that only support IPv4 and can only be managed via IPv4 will require me to continue running an IPv4 network / stack in order to talk to them. Just like with the IPX printer servers... desktops don't have to run or be aware of IPX, but there's still an IPX network and at least one multi-protocol host to act as a gateway. I'd rather not have to bother.
My point was more about the age of business infrastructure. Some people seem to be under the delusion that companies rip out all their gear every few years. I've never known one that did. eg. the 20 year old 3Com dual stack hubs all over the building. (at the time, they had plenty of spares and 3com would replace the dead ones. however, as we found out with cisco, eventually, the warehouse is going to be empty.) Companies replace things when they have to, and sometimes when they *need* to.
IPv6 in software on most router platforms is best avoided. Those packets are "process switched", which is the worst, slowest possible means of moving packets. In the Cisco world, you can make very expensive gear perform worse than junk if the packets are process switched.
Running a bunch of parallel networks for "legacy gear" is not a great situation. Right now, IPv6 still needs IPv4 to be effective. At some point, systems will be able to function completely on IPv6, and you'll want to remove IPv4 from your network -- entirely. It's not an issue of global reachability; it's an issue of having to run and support 2 networks just for the legacy devices that cannot handle IPv6. (and right now, that's a lot of things... printers, network scanner, network fax, switches, access points, our toshiba phone switch...)
It's a good thing I'm out of Dew or it would've flown out my nose.
Oh hell no they don't. ISPs run shit until it's completely dead. I don't want to think about all the times I've had to go to war to get $10k to upgrade a router -- even then it was someone else's used gear. While many large ISPs have the revenue to support such foolish spending, the people writing the checks aren't nearly as crazy. (besides, if they're spending millions on gear, that's millions not going in their pockets.)
Put another way:
Unless the hardware is very new (within a few years), it will most likely handle IPv6 purely in software, with little if any hardware support. This is the slowest of all methods.
While the Cisco ASA lists IPv6 support on paper. Have you actually tried using it? It's a very bad joke. Maybe it's better in 8.3, but I refuse to run that brain damaged crap. Our checkpoint firewalls do not support IPv6, and would have to be completely reinstalled to do so. (the base secureOS -- running linux 2.4 -- has zero support for IPv6.)
Load balancers... some support IPv6, for various definitions. I've not played with any of them to gauge their level of suck.
Bottom line... the move to IPv6 will be expensive, and very messy. And will probablly take another 10 years.
Very few home routers support IPv6 out-of-the-box. And the millions in the field will almost certainly never see a firmware update to support IPv6. (it's more profitable to make you buy a new one.)
I know of no broadband ISP that is openly providing IPv6 service to residential customers (in the US.) Comcast has a "trial program", and at last report, it's closed to new participants. Earthlink had a pilot program that was abandoned after laying off the one engineer running it. Getting native IPv6 connectivity from *business* connections is still spotty.
Google is not the entire internet. While saying there are *no* websites in IPv6 is obviously wrong, most of the places people go everyday are not reachable via IPv6 only. (unless you're in china.)
Since when does a linksys router have any other interface than the web ui? There's no serial port on them (unless you make your own.) And they don't do telnet or ssh.
(Replacing the firmware with DD-WRT, OpenWRT, Tomato, etc. doesn't count.)
Out of the box is what matters. If grandma cannot go to $BIG_BOX_STORE, buy something, come home and plug it in, it's useless.
(Plus, almost no broadband ISP supports IPv6 for end users.)
Really? I know at least one company that's still using 20 year old *hubs*. Yes, h.u.b.s.!!! And Cisco gear so old, Cisco refunded the support contracts after having to replace one. ("oh shit, we don't have any of those.") (this company still uses IPX print servers, btw. HP never made IP firmware for them.) I'm using gear that's been EOL/EOS for 5+ years now... don't break what's working. I'll have to replace it to support IPv6 at any realistic speeds. (IPv6 is handled entirely in software.)
Anything that has to be managed needs to support IPv6. Or your network becomes a huge f'ing mess. I've been there... appletalk, ipx, and IP on the same network.
"upgrade the software" is a fine thing to tell yourself. However, in the real world, there are devices that will never support IPv6 because the company that made it won't upgrade it, no longer exists, or was bought out and abandoned the thing. (I have stuff in all of those categories.)
Saying Windows XP (which a great many people and companies STILL RUN) supports IPv6 is laughable. It was and still is, EXPERIMENTAL. And does not meet any of the modern standards for IPv6. (IPv6 as an idea has been around for ~15 years. The protocol specifications (RFCs) systems follow today are only a few years old. And still changing.)
Anyway, there's a great deal more involved than just "the OS supports it." Applications have to support it. Numerous bits of hardware have to support it -- firewalls, routers, switches, print servers, printers, access points, ntp clocks, phones, etc, etc, etc. And yes, routers need to be REPLACED to fully support IPv6; the software switching performance of even uber routers is complete crap. And most importantly... your ISP(s) have to support it. (neither of my broadband connections (TWC and Bellsouth) support IPv6. Neither do clearwire or FiOS.)
Play along here! The media says he's been running from the law for months.
Why, then, have Visa and MasterCard refused to do business with the (still completely legal, as far as I'm aware) website
Because they do not want to be associated with actions of that website. (and releasing classified information is illegal.)
Why have bank accounts been frozen?
His Swiss account(s) were "seized", not frozen. I would presume to make it harder for him to continue to elude arrest.
Why have PayPal cut off their account?
Simple... they're paypal. In case you've never noticed, paypal will lock an account simply because you looked at them wrong.
Why have their web hosts and DNS provider given them the cold shoulder?
Same reason as Visa and Mastercard... to get as far away from the poisoned fruit as possible.
Why do leading US politicians advocate cold blooded murder by government troops?
There are many reasons. They should be obvious to you.
Why are US legislators promising to change the law to make his journalistic, first amendment protected actions retroactively against the law?
Technically, what wikileaks is doing is not "journalism". Scanning documents into pdfs and placing them on a web site is not journalism.
And how the hell is that supposed to work? If it's jamming the signal, you have "zero bars" and cannot make any calls; thus nothing will know you're trying to call 911. It's not like E911 is on a different frequency. If the technology is "jamming" by intercepting your phone, then you're breaking several laws. Plus the device would have to be built to talk to every oddball proprietary cell technology licensed in the country -- at the same time. (and be precisely tuned to function over a distance of 2ft.) And then, the crap could (read: eventually WOULD) malfunction, usually as a result of a crash, not cut out in an accident/while parked/etc., or go nuts and jam everything within a half mile. (cell phones, police radios, radio and tv broadcasts, ...)
Since when do they have DOCSIS 3 gear in Shelby? (answer THEY DON'T) Charlotte has limited D3 rollout. Gastonia is next down the line from CLT. THEN Shelby. Judging by their past record, don't expect D3 until 2015. (2 years ago they still didn't have SDV gear in Shelby and were still handing out single stream cablecards.)
It's a DATA CENTER. So, the only thing going on there will be network and system maintenance. I doubt there will be any "engineering" done there at all. Which means the few dozen jobs it creates will be for 30-40k/yr button pushers.
To be fair, there are a lot of IT professionals in NC. They just aren't in Forest City; and if they ever were, they left a long time ago when most of the businesses (i.e. mills) went bust.
According to several studies, NC ranks poorly in education. Not the worst, but near enough to count as "close to it." Your bonus is getting to keep your job. (trust me, if your students consistently test low, you will be out of a job.)
[NC public education is mostly about politics and personal agendas, not actually educating anyone. Many parents treat it as government daycare.]
s/moonshine/meth labs/
I've seen it happen when Windows Update(tm) replaces the network driver and the system then thinks it's a new card. All sorts of odd/interesting things happen on the next reboot.
mDNS, et. al. are nice... if www.yahoo.com happens to be on the local link . mDNS is NOT a complete replacement for traditional (unicast) DNS. SLAAC is lightyears from what DHCP has provided for years.
Please, remove IPv4 from your network(s). Run 100% pure IPv6. You'll learn what many others have known for years... the "utopia" that IPv6 is supposed to be, *isn't*. Without something filling in your DNS servers -- for GLOBAL name resolution, you're not going to get very far.
Wrong. RA provides only a prefix (which MUST be /64 for SLAAC) and gateway (i.e. the thing sending the RA.) That is "all you need" today because IPv4 is filling in the rest of the equation... hostname, domain name, nameservers, etc. Turn off IPv4 and you quickly see how much is left out. Modern systems depend on a lot more than just an address to function productively.
The first gen AU9(?) was 35lbs. A single LNB oval dish (plus LNB) is a little more than 5lbs. The monster DISH Pro/1000 thing is 30-40lbs. (and a real pain in the ass to aim.)
It does have to be aimed in roughly the right direction. However, it does not require precise tuning. I've used a BGAN system that used a tiny, flat receiver... you just have to get it close for it to work.