IPv6's hierarchical routing was dead about 4 hours after the first real world deployment. That's what IPv4 used to call "classful routing". Anyone attempting to push that crud today is a documented idiot. IPv6 routing tables will be (and are) larger -- much larger. Count up the number of PI/48's and ISP/32's... each of those is an independant entry in the global routing table.
They are a business just like everyone else. They are most certainly not going to do anything to make their content cheaper -- produce content cheaper, yes... but reducing the sold price? Absolutely not. They want the same (lame) metrics everyone else wants, so they do everything possible to inflact them -- esp. if the schools are charged based on "usage" (i.e. hit counts, not necessarily the amount of content actually moved.) If the content has been locally cached, accesses will be completely "hidden" from the supplier.
I've always tended to stay at the "cheaper" hotels. The internet (wifi) there has always been free and perfectly usable. Yes, it's a bit slow, but I never expect them to truck in a gig-e line for us to mooch. (for free)
In the Big Name Hotels(tm), they charge for internet access (wired and wifi), so I would expect them to have exceptional bandwidth -- of course, they never do. (I know the insides of a several of those networks, and have heard from patrons -- and used their laptop to see it myself.) For them, it's a profit/cost center; for the "budget" hotels, it's a perk that brings people in.
Somehow I doubt that story. They'd have to file charges and arrest him to seize any property. Or are we talking about another "lost" Apple iPhone prototype?
I've only worked one place that had such insane network security measures. Password requirements that ultimately meant no one used a good password -- they have to change it every 30 days, and cannot reuse it for 6 months [the system remembers the last four passwords, but it didn't have a minimum password age... so you could change your password 5 times in 5 minutes and be back to the same one. But no one did that.] Your account would be locked after 60 days of inactivity. If you failed to change your password after 30 days, your account would be locked. Account names were of the format XXX##### and had nothing to do with anything; the helpdesk had to keep an access db of who had what account, just to know who the f*** did anything.
Physical security was more of a joke... the control boxes tended to be in closets next to the elevators where anyone could get to them -- and the doors don't have locks. If you manage to get into the interior stairwell, you could get anywhere in the 9 story building. (except the basement; it opened into the parking deck at the ground level.) There was only maned (unarmed) security from 7-7(?) -- nothing after business hours.
It's my understanding of the system (from dealing with one years ago)... the server can recover the seed used by a hardware token given it's serial number, and two sequential tokens. Perhaps the serial number is the "seed" and it's figuring out the tokens clock. However, it's perfectly clear the server can generate the same numbers as the token. The strength of the system is keyed to protecting that algorithm. Soft-tokens are a bad joke and only slightly better than a password, but are themselves based on a "password".
Perfectly "clean" rainwater should have a pH close to 7.0 -- being pure water. 5.6 is bordering on "acid rain". (I'll check my rainwater sisterns, but they've had a long time to settle.)
Yes, sea water is highly buffered. However, that buffer is not instant. Look at the small scale in my (freshwater) aquariums... they have carbonate buffers in there (a lot of it, in fact -- aragonite and commerical buffers) and the pH can still dip below 6.6. If I draw a sample for testing, sealed in the tube, the pH will slowly recover to 8.4 as the disolved buffer does it's job. A great deal of the buffer capacity of the oceans are the coral in them.
But yes, I agree, CO2 is not what's going to destroy our oceans. We've been doing far, far worse things to them for a long time now.
Yes, their requirements were wack, and they bought orders of magnatude more than they'll ever need. (and paid though the nose for all of it... $1k T1 modules??? I have a box of WIC-1T's... at best worth $50 each.)
Like hell it is. Midspan power inserters are dirt cheap, esp. compared to the cost of PoE integrated switches. (I paid $50 each for a pair of PowerDsine 24port units --.gov surplus; even the new gige capable systems are far less than the insane markup for PoE vs. non-PoE. The PoE "upgrade" for my office took less than an hour.)
Actually it did. Microsoft was not interested in remote desktop / terminal systems. That's why a number of companies created their own versions. There were other display-the-desktop-remotely systems (like VNC these days), but Citrix was the only one that created a multiuser environment -- and the only one that worked extremely well. (they also had a version for Solaris, which I still have. It beats the holy crap out of remote X11.) Microsoft still wasn't interested, but they were *very* interested in the money flowing into Citrix pockets that wasn't instead going in their's. (what has become a standard practice for Microsoft)
RDP was never designed to be a graphical terminal server protocol. It's a remote administrator tool because everything in windows had to have a (local) GUI to do just about anything. That's less true today, but Microsoft and 3rd party software on Windows is still designed for a GUI admin interface. Yes, some things have a CLI, but they're cumbersome, poorly documented (if at all), and usually far too complicated vs. a few clicks in a GUI. [powershell was supposed to change all that, but even M$ doesn't use the thing.] The only real difference to a modern windows environment boils down to the GUI management consoles being able to control non-local machines. mostly... not everything has an DCE/RPC/etc. binding. (and you still need a windows machine to host all those msc's.)
If you can live with Mircosoft virtualization technology, AND have state-of-the-art terminals that support RDP 7.1 (RemoteFX), then maybe. If you already have a setup -- and even if you don't, you've always been better off not using RDP. Wyse has apparently had additional software (TCX) to deal with Microsoft's shortcomings for MANY YEARS. And there have been alternatives to RDP since, well, long before RDP existed. (Citrix, for one... which pre-dates Windows Terminal Server Edition (NT).)
RDP (like everything M$) sucks badly. They couldn't even steal Citrix technology correctly. Video playback (eg.youtube) will require massive CPU processing in the VM. VMWare's remote console protocols use very little. This was the subject of conversation a few weeks ago with a friend having this exact problem -- sales people demanding video playback ability from windows terminal server sessions... it completely kills the server.
(I tested a youtube playback via RDP (70% CPU) and vsphere client console (7%). It made no difference to my XP desktop which protocol was used. note: vcc won't transport sound and technically, vm's on esx/esxi don't support sound hardware -- to be fair, rdp wasn't sending sound either.)
In most (all?) office settings, the studs are sheet metal beams. Unless you've cut a hole to put a washer and nut on the inside, screws, lag bolts, etc. will pull free. Toggle bolts against the drywall work better, but they're pulling on the drywall -- and it does have a burst strength rating. Even a properly engineered and mounted panel will have a weight limit; and it will be far, FAR, less than a free standing rack. (ps: the manufacturer also lists a max. weight rating... the APW wiring rack I have (20U? 18" depth) has a limit of 300lbs, the other 14U-24" is 100lbs. also, I pulled that APW rack off the wall by standing on the bottom rung, and it was lag bolted to the metal studs through a panel.)
Read the instructions that come with any rack... the wheels are for moving the rack itself. NEVER attempt to roll a loaded rack. That much mass (about the same as a small car) is hard to control once it's moving; if a wheel snags something, it'll take the wheel off, bend the shit out of the rack, break the bearing, notch the wheel, tip the rack over, or any combination of those. (it'll also go through a bog standard sheet rock wall like it's not there. and as a bonus, if your hand is on that side, it's going through the wall, too.)
[Trust me. I've seen it go wrong far too many times...]
No. If you use them for what they are designed -- WIRING -- then there's no problem with them. The problems start when people try to hang routers, pbx's, and *servers* in them. The added weigh of all that junk will pull the rack out of the wall. (the deaper the rack the less weigh it can hold.) I've seen walls bowed due to the weigh of a rack pulling on it. (and yes, there was a gap forming at the wall.)
Please review those cases. They did not present their bomb to TSA for inspection prior to getting on the plane. (And this is also not the only time this sort of stupid has occured.)
This isn't fear, it's pure stupid. They got it through airport security, on to a plane, flew to their destination, and *now*, suddenly, it's a f***ing danger to the entire state of Texas. Those TSA morons just showed stupid they are and how much they can over react. There used to be this thing called "Lost and Found", but today, if you leave anything anywhere around an airport, you're a Terrorist(tm).
In full race gear, you really cannot turn your head to see behind you. (or right beside you for that matter.) That's why there's a guy at the end of the pit wall looking up the track... when he signals "go", you f'ing GO.
(etc. at CMP where you exit pit road directly into turn 1. you cannot do that with any speed at all. I watched many cars end up "badly" there at the last Lemons race.)
If your hands are on the wheel, they're "in the way". While the MythBusters are quacks when it comes to real science, they do a passable job of showing how stupid some beliefs are. (the air bag isn't going to rip your thumbs off, or in this case, break your arms.) It will be unpleasant, but will not cause serious injury. The NTSB (and manufacturers) do actually test all of this.
And for the record, the 9+3 vs 10+2 is about car control not the f'ing air bags. (the recommendation from professional driving instructors predates airbags.)
That would break any cached lookups (which most OSes and applications have done for eons), local host file records (granted, they could be compromised), and access by direct IP address.
It's not a half bad idea for systems in hostile environments. The problem is... no firewall in existance can do this out of the box. (it could be rigged up for a few of them.)
Indeed. In the US, the.gov set aside $400m(?) from which telcos could request funds for upgrades to be CALEA compliant. Many telco's, having never been ordered for a tap, ignored the requirement. The telco I worked for was gambling on a) never getting an order, and b) being able to milk the 60day(?) provisioning process to add CALEA support when and where necessary. They got zero financial assistance from the.gov. (CALEA was an add-on to other hardware/software upgrades.) [That would've been an expensive mistake as it took ~6 months to actually do the upgrades. If they did get an order, they'd have to call me to remind them how to do it -- noone access those screens often enough to remember the proceedures]
Pretty much any telco gear on the market today will have CALEA support built into it. Even Cisco IOS has CALEA facilities in it -- for network and VoIP taps. (I've never played with it, 'tho. AT&T 5ESS's were enough of a headache.)
Factory refurbs are 99% automated... it only takes a human to load/unload the test module. If it passes, it's relabeled and sold. Fails get thrown in a bin for recycling.
Slashdot Mirror
And RISC was supposed to change the world...
IPv6's hierarchical routing was dead about 4 hours after the first real world deployment. That's what IPv4 used to call "classful routing". Anyone attempting to push that crud today is a documented idiot. IPv6 routing tables will be (and are) larger -- much larger. Count up the number of PI /48's and ISP /32's... each of those is an independant entry in the global routing table.
They are a business just like everyone else. They are most certainly not going to do anything to make their content cheaper -- produce content cheaper, yes... but reducing the sold price? Absolutely not. They want the same (lame) metrics everyone else wants, so they do everything possible to inflact them -- esp. if the schools are charged based on "usage" (i.e. hit counts, not necessarily the amount of content actually moved.) If the content has been locally cached, accesses will be completely "hidden" from the supplier.
I've always tended to stay at the "cheaper" hotels. The internet (wifi) there has always been free and perfectly usable. Yes, it's a bit slow, but I never expect them to truck in a gig-e line for us to mooch. (for free)
In the Big Name Hotels(tm), they charge for internet access (wired and wifi), so I would expect them to have exceptional bandwidth -- of course, they never do. (I know the insides of a several of those networks, and have heard from patrons -- and used their laptop to see it myself.) For them, it's a profit/cost center; for the "budget" hotels, it's a perk that brings people in.
Somehow I doubt that story. They'd have to file charges and arrest him to seize any property. Or are we talking about another "lost" Apple iPhone prototype?
I've only worked one place that had such insane network security measures. Password requirements that ultimately meant no one used a good password -- they have to change it every 30 days, and cannot reuse it for 6 months [the system remembers the last four passwords, but it didn't have a minimum password age... so you could change your password 5 times in 5 minutes and be back to the same one. But no one did that.] Your account would be locked after 60 days of inactivity. If you failed to change your password after 30 days, your account would be locked. Account names were of the format XXX##### and had nothing to do with anything; the helpdesk had to keep an access db of who had what account, just to know who the f*** did anything.
Physical security was more of a joke... the control boxes tended to be in closets next to the elevators where anyone could get to them -- and the doors don't have locks. If you manage to get into the interior stairwell, you could get anywhere in the 9 story building. (except the basement; it opened into the parking deck at the ground level.) There was only maned (unarmed) security from 7-7(?) -- nothing after business hours.
It's my understanding of the system (from dealing with one years ago)... the server can recover the seed used by a hardware token given it's serial number, and two sequential tokens. Perhaps the serial number is the "seed" and it's figuring out the tokens clock. However, it's perfectly clear the server can generate the same numbers as the token. The strength of the system is keyed to protecting that algorithm. Soft-tokens are a bad joke and only slightly better than a password, but are themselves based on a "password".
Perfectly "clean" rainwater should have a pH close to 7.0 -- being pure water. 5.6 is bordering on "acid rain". (I'll check my rainwater sisterns, but they've had a long time to settle.)
Yes, sea water is highly buffered. However, that buffer is not instant. Look at the small scale in my (freshwater) aquariums... they have carbonate buffers in there (a lot of it, in fact -- aragonite and commerical buffers) and the pH can still dip below 6.6. If I draw a sample for testing, sealed in the tube, the pH will slowly recover to 8.4 as the disolved buffer does it's job. A great deal of the buffer capacity of the oceans are the coral in them.
But yes, I agree, CO2 is not what's going to destroy our oceans. We've been doing far, far worse things to them for a long time now.
That's the key... Humans. Aren't. Random. Knowing a little about the person can often significantly reduce your search.
The 1800 line (except the 1861 -- small office voip/call manager) is EOL. You cannot buy them new. (in fact most of the [123]800 line is EOL)
Really? There are T1 modules for ASA's?
Yes, their requirements were wack, and they bought orders of magnatude more than they'll ever need. (and paid though the nose for all of it... $1k T1 modules??? I have a box of WIC-1T's... at best worth $50 each.)
Like hell it is. Midspan power inserters are dirt cheap, esp. compared to the cost of PoE integrated switches. (I paid $50 each for a pair of PowerDsine 24port units -- .gov surplus; even the new gige capable systems are far less than the insane markup for PoE vs. non-PoE. The PoE "upgrade" for my office took less than an hour.)
http://en.wikipedia.org/wiki/Citrix_WinFrame
Actually it did. Microsoft was not interested in remote desktop / terminal systems. That's why a number of companies created their own versions. There were other display-the-desktop-remotely systems (like VNC these days), but Citrix was the only one that created a multiuser environment -- and the only one that worked extremely well. (they also had a version for Solaris, which I still have. It beats the holy crap out of remote X11.) Microsoft still wasn't interested, but they were *very* interested in the money flowing into Citrix pockets that wasn't instead going in their's. (what has become a standard practice for Microsoft)
RDP was never designed to be a graphical terminal server protocol. It's a remote administrator tool because everything in windows had to have a (local) GUI to do just about anything. That's less true today, but Microsoft and 3rd party software on Windows is still designed for a GUI admin interface. Yes, some things have a CLI, but they're cumbersome, poorly documented (if at all), and usually far too complicated vs. a few clicks in a GUI. [powershell was supposed to change all that, but even M$ doesn't use the thing.] The only real difference to a modern windows environment boils down to the GUI management consoles being able to control non-local machines. mostly... not everything has an DCE/RPC/etc. binding. (and you still need a windows machine to host all those msc's.)
If you can live with Mircosoft virtualization technology, AND have state-of-the-art terminals that support RDP 7.1 (RemoteFX), then maybe. If you already have a setup -- and even if you don't, you've always been better off not using RDP. Wyse has apparently had additional software (TCX) to deal with Microsoft's shortcomings for MANY YEARS. And there have been alternatives to RDP since, well, long before RDP existed. (Citrix, for one... which pre-dates Windows Terminal Server Edition (NT).)
RDP (like everything M$) sucks badly. They couldn't even steal Citrix technology correctly. Video playback (eg.youtube) will require massive CPU processing in the VM. VMWare's remote console protocols use very little. This was the subject of conversation a few weeks ago with a friend having this exact problem -- sales people demanding video playback ability from windows terminal server sessions... it completely kills the server.
(I tested a youtube playback via RDP (70% CPU) and vsphere client console (7%). It made no difference to my XP desktop which protocol was used. note: vcc won't transport sound and technically, vm's on esx/esxi don't support sound hardware -- to be fair, rdp wasn't sending sound either.)
In most (all?) office settings, the studs are sheet metal beams. Unless you've cut a hole to put a washer and nut on the inside, screws, lag bolts, etc. will pull free. Toggle bolts against the drywall work better, but they're pulling on the drywall -- and it does have a burst strength rating. Even a properly engineered and mounted panel will have a weight limit; and it will be far, FAR, less than a free standing rack. (ps: the manufacturer also lists a max. weight rating... the APW wiring rack I have (20U? 18" depth) has a limit of 300lbs, the other 14U-24" is 100lbs. also, I pulled that APW rack off the wall by standing on the bottom rung, and it was lag bolted to the metal studs through a panel.)
Read the instructions that come with any rack... the wheels are for moving the rack itself. NEVER attempt to roll a loaded rack. That much mass (about the same as a small car) is hard to control once it's moving; if a wheel snags something, it'll take the wheel off, bend the shit out of the rack, break the bearing, notch the wheel, tip the rack over, or any combination of those. (it'll also go through a bog standard sheet rock wall like it's not there. and as a bonus, if your hand is on that side, it's going through the wall, too.)
[Trust me. I've seen it go wrong far too many times...]
No. If you use them for what they are designed -- WIRING -- then there's no problem with them. The problems start when people try to hang routers, pbx's, and *servers* in them. The added weigh of all that junk will pull the rack out of the wall. (the deaper the rack the less weigh it can hold.) I've seen walls bowed due to the weigh of a rack pulling on it. (and yes, there was a gap forming at the wall.)
Please review those cases. They did not present their bomb to TSA for inspection prior to getting on the plane. (And this is also not the only time this sort of stupid has occured.)
This isn't fear, it's pure stupid. They got it through airport security, on to a plane, flew to their destination, and *now*, suddenly, it's a f***ing danger to the entire state of Texas. Those TSA morons just showed stupid they are and how much they can over react. There used to be this thing called "Lost and Found", but today, if you leave anything anywhere around an airport, you're a Terrorist(tm).
In full race gear, you really cannot turn your head to see behind you. (or right beside you for that matter.) That's why there's a guy at the end of the pit wall looking up the track... when he signals "go", you f'ing GO.
(etc. at CMP where you exit pit road directly into turn 1. you cannot do that with any speed at all. I watched many cars end up "badly" there at the last Lemons race.)
If your hands are on the wheel, they're "in the way". While the MythBusters are quacks when it comes to real science, they do a passable job of showing how stupid some beliefs are. (the air bag isn't going to rip your thumbs off, or in this case, break your arms.) It will be unpleasant, but will not cause serious injury. The NTSB (and manufacturers) do actually test all of this.
And for the record, the 9+3 vs 10+2 is about car control not the f'ing air bags. (the recommendation from professional driving instructors predates airbags.)
That would break any cached lookups (which most OSes and applications have done for eons), local host file records (granted, they could be compromised), and access by direct IP address.
It's not a half bad idea for systems in hostile environments. The problem is... no firewall in existance can do this out of the box. (it could be rigged up for a few of them.)
Indeed. In the US, the .gov set aside $400m(?) from which telcos could request funds for upgrades to be CALEA compliant. Many telco's, having never been ordered for a tap, ignored the requirement. The telco I worked for was gambling on a) never getting an order, and b) being able to milk the 60day(?) provisioning process to add CALEA support when and where necessary. They got zero financial assistance from the .gov. (CALEA was an add-on to other hardware/software upgrades.) [That would've been an expensive mistake as it took ~6 months to actually do the upgrades. If they did get an order, they'd have to call me to remind them how to do it -- noone access those screens often enough to remember the proceedures]
Pretty much any telco gear on the market today will have CALEA support built into it. Even Cisco IOS has CALEA facilities in it -- for network and VoIP taps. (I've never played with it, 'tho. AT&T 5ESS's were enough of a headache.)
Factory refurbs are 99% automated... it only takes a human to load/unload the test module. If it passes, it's relabeled and sold. Fails get thrown in a bin for recycling.
Nope... that's an "open(ed) box" item.