It seems like those who are trying to have him tarred and feathered constantly want...
This is common practice when any company fires any employee "for cause". They always paint the ex-employee in the worst possible light to the other employees, but for legal reasons say little to nothing to anyone outside the company. I've seen it more times than I care to count.
Childs is, no doubt, a nut, however, I've been there and understand his reluctance to see something he's worked hard to build and maintain be mismanged and ruined by those "less driven" than himself. But I'm also certain his coworkers were/are morons by any business/professional standard. (which explains why they work for city government. I could work for any number of.gov jobs, but most wouldn't come close to paying me half what I make in the private sector, or even what I can (and have) made as self-employed.)
To access it remotely, it has to be connected to something. Even a wireless device's position can be triangulated. A physically cabled device is absolutely trivial to trace. (might be a bit of work following cables through walls and floors, 'tho)
And the fact that you parrot this means you haven't a g** d*** clue how networks and networked devices actually work. If you can talk to it (ping, telnet, etc.), it doesn't matter what MAC address it uses. If it's using the same MAC as another device in the same network, then neither device will work correctly - PERIOD. They say the cannot login because they don't have a username and password, which means they can talk to it via some remote method -- if they were on the console, they wouldn't be searching for it; it'd be right in front of them.
We aren't using the MAC to blame a vendor. It's used to find the correct switch port. As long as you are able to talk to it, it most f'ing certainly can be found. The notion that these clowns are too lazy and/or incompotent to find one or more of the cables attached to the thing and follow them back to the machine is beyond belief. (Hell, I've traced down machines on HUBS where there are no per-port MAC tables. Hint: look at the blinking lights.)
When was the last time you heard of anyone buying an airplane ticket based on anything other than price and time?
ME. Every time I've flown in the last few years. Yes, price and time come into it. But what type of plane I'll be riding in, the servicing airline (which isn't always the one selling you the ticket), number of layovers/transfers, which airports I'll be passing through, how much time I'll have to make my connections, (lame) bagage fees... So, there's a lot more to it than mere price and time from point A to point B.
If you booked early enough, there used to be $68 one-way flights on Southwest. Of course, NO ONE includes SWA in their flight selection systems -- because SWA won't pay places like priceline, expedia, et. al. to list them. (and there-in is the real problem... the flights you see are from those who have made kickbacks to the travel agent.)
True, but it's not a dedicated 20A socket. It's a 20A LINE with several 20A sockets on it. Large capacity (over 9k BTU) A/C "window units" use significant power, to the point they pretty much need to be on their own circuit.
The problem with those things is the left-right airflow. Go ask PSI what happens when you put several rows of these things in a room. The air gets hotter and hotter as you go down the line; their solution... a piece of cardboard between the racks.
Enclosed server racks are engineered for front-back airflow.
Pure plate glass, yes. Modern energy efficient glass, no. They reflect RF energy pretty well. And, wood and plaster absorb RF better than you might think. Simply taking his DB8 outside the walled in confines of his apartment might make a huge difference. But he's likely running into out ground level interference -- trees, other houses, hills, traffic, etc. Don't assume your best reception will be on a direct line to the transmitter. You may find reflections much stronger than a direct line. (I know I do.)
There's works and then there's works well. 300ohm cable is not shielded and thus is part of the receiving antenna. It also has much higher impedance which means higher signal loss. A fuzzy, washed out, ghosted NTSC signal is still watchable. ATSC either works or it doesn't; there's very little watchable middle ground.
That's due to the difference in ATSC chipsets. The Series3/Tivo HD have great multipath rejection which means they will be able to receive a clean signal where older system have trouble. I also have an HR10 -- the first ATSC receiver Tivo ever built; it's reception is horrible due entirely to it's lack of multipath rejection.
Hah. You've never rented an apartment, have you? I've never seen a single apartment/condo/townhome complex that didn't do everything in their power (and more) to prevent antennas and dishes -- "the building is wired for cable, end of discussion". I know of a half dozen HOA's that out-right ban them as well -- which is 100% illegal.
That said, there are a few places around the country where DISH, DirecTV, and cable all live happily together in one massive (expensive) distribution network. But those are rare (vs. the number of apartments and condo's.)
You're going to run into that limit pretty much anywhere you share walls. To be 100% fair, the landlord isn't barring "any" external antenna; it simply has to be within your rented property ("exclusive use area".) He's on the ground floor, so he's screwed. It could be worse... he could be on the wrong side of the building. He needs an antenna on the roof (or 2nd/3rd floor apartment), but he has no legal rights to the roof ("common area") or apartments he's not renting. One option might be ask the upstairs neighbor if you can set this (huge, ugly, etc.) DB8 on their balcony for a few days (weeks?)
a) There are no "US equivalents". b) HD streams (even MP4) are huge bandwidth eaters that will exceed most "broadband high-speed" connections. [a good quality MPEG2 SD stream needs 5Mbps.] They will pretty much always exceed a US user's upstream connection speed. Even at 512k, the slingbox output looks like crap. (1.5-1.8M is needed for a good picture and that's still 15fps.)
He's in a ground floor apartment. Where do you think he's going to put any receiving station? He isn't likely to have (legal) access to any property within range of his apartment.
It's not misleding at all. If you are on an IPv4 network, you cannot talk to anything on an IPv6 network. They must both talk IPv4 or IPv6. They are two different things, that form two different networks. We might as well be talking appletalk and vines -- again two completely seperate networks.
NAT is a horrible, hackish problem pretending to be a solution.
Horrible is a matter of opinion; I think it's clever. Hack? Sure. But it is most definately a solution. The only problems with NAT, aside from a very few complicated edge cases, can be attributed to poor protocol design and even poorer implementation... if you bind INADDR_ANY, you don't know what your address is until the connection is established, and you ask the kernel. getipnodebyname(gethostname()...) is just as wrong in today's world of NAT as it was in the years before NAT.
Also, any references on the claim that ISPs use NAT in any major capacity?
Many cellphone networks provide NAT'd private addresses unless you ask for "vpn service", etc. (and sometimes pay extra.) But it's rather rare these days -- you may not even know your phone is using a private address. I don't know of any commercial ISPs doing this today, but PSINet had some horrible windows only PoS that was NAT'd service. (it failed for many reasons.)
This doesn't matter AT ALL since IPv4 systems cannot talk to IPv6 systems, and v.v. They. Are. Completely. Alien. Networks. It just makes it easier to transport IPv4 across IPv6. Without a proxy/translator/etc. IPv6 and IPv4 hosts cannot talk to each other. This is why IPv6 will take decades to be openly adopted -- if ever. (It's already been a decade, btw.)
That's exactly it. When gmail fails, you don't know if it's going to be 3min, 3hrs, or 3days. Or if it will ever be fixed. You are left with no information and no control. When (if) it does come back, you don't know what state it's going to be in... how much of your data is now screwed up and completely gone? What choice(s) do you have in the matter? (none.) With a local server, everything is right there in front of you. You have people you can talk to. You have people to make it right again. You have control, and you are part of the information loop.
For starters, linux is not a "Microsoft enterprise-level software" -- it is something completely, and entirely different.
It's easy to find thousands of people who call themselves "exchange admins", and it's very likely they'll all come waving a peice of paper saying they're "certified". The problem is, more often than not, they're worth less than that paper. The linux camp is similar without the thoundands of paper wavers, as there aren't that many certifications -- and most real linux people won't touch them. (certs are for people who want decorations.)
Bottom line: It's often very difficult to find someone truly qualified for what you need done.
You missed the point... on the wireless network, one must login to get an address. Thus, there should be records of who logged in and was given a specific address. So, they should have one and only one name for the two wireless addresses.
Of course, if they expire those logs as fast as the dhcp logs, there's nothing to search.
You don't have to register MACs or any of that crap. And you don't need web page authentication redirects for "unregistered" systems. With 802.1X, you either present the required authentication materials or you get no/limited network access. Granted this is only effective per port which means you couldn't plug in a switch in your dorm room to connect several machines. (in theory you could, but I don't know any switches that will do upstream 1x auth; or at least none kids can afford.)
Most of what Universities are using are very old, hastily cobbled together systems. Better methods have been around for a long time, but they don't have the time or money to mess with building a better system given the current system does actually get the job done. Having worked in that world, there are usually very few people to get a lot of things done. (I was lucky. I only had one lab (~2 dozen PCs) and a maybe a dozen more research systems (some PCs some VMEs) to manage.)
Actually, what they said (and I did read the PDF) is they don't keep logs for more than 10 days and the arp table snapshots are inconclusive. And I'd say their DHCP system is broken as well since the example they give shows an overlaping lease -- presumablly to the same machine, but still an overlap.
Slashdot Mirror
This is common practice when any company fires any employee "for cause". They always paint the ex-employee in the worst possible light to the other employees, but for legal reasons say little to nothing to anyone outside the company. I've seen it more times than I care to count.
Childs is, no doubt, a nut, however, I've been there and understand his reluctance to see something he's worked hard to build and maintain be mismanged and ruined by those "less driven" than himself. But I'm also certain his coworkers were/are morons by any business/professional standard. (which explains why they work for city government. I could work for any number of .gov jobs, but most wouldn't come close to paying me half what I make in the private sector, or even what I can (and have) made as self-employed.)
To access it remotely, it has to be connected to something. Even a wireless device's position can be triangulated. A physically cabled device is absolutely trivial to trace. (might be a bit of work following cables through walls and floors, 'tho)
And the fact that you parrot this means you haven't a g** d*** clue how networks and networked devices actually work. If you can talk to it (ping, telnet, etc.), it doesn't matter what MAC address it uses. If it's using the same MAC as another device in the same network, then neither device will work correctly - PERIOD. They say the cannot login because they don't have a username and password, which means they can talk to it via some remote method -- if they were on the console, they wouldn't be searching for it; it'd be right in front of them.
We aren't using the MAC to blame a vendor. It's used to find the correct switch port. As long as you are able to talk to it, it most f'ing certainly can be found. The notion that these clowns are too lazy and/or incompotent to find one or more of the cables attached to the thing and follow them back to the machine is beyond belief. (Hell, I've traced down machines on HUBS where there are no per-port MAC tables. Hint: look at the blinking lights.)
ME. Every time I've flown in the last few years. Yes, price and time come into it. But what type of plane I'll be riding in, the servicing airline (which isn't always the one selling you the ticket), number of layovers/transfers, which airports I'll be passing through, how much time I'll have to make my connections, (lame) bagage fees... So, there's a lot more to it than mere price and time from point A to point B.
If you booked early enough, there used to be $68 one-way flights on Southwest. Of course, NO ONE includes SWA in their flight selection systems -- because SWA won't pay places like priceline, expedia, et. al. to list them. (and there-in is the real problem... the flights you see are from those who have made kickbacks to the travel agent.)
True, but it's not a dedicated 20A socket. It's a 20A LINE with several 20A sockets on it. Large capacity (over 9k BTU) A/C "window units" use significant power, to the point they pretty much need to be on their own circuit.
The problem with those things is the left-right airflow. Go ask PSI what happens when you put several rows of these things in a room. The air gets hotter and hotter as you go down the line; their solution... a piece of cardboard between the racks.
Enclosed server racks are engineered for front-back airflow.
Pure plate glass, yes. Modern energy efficient glass, no. They reflect RF energy pretty well. And, wood and plaster absorb RF better than you might think. Simply taking his DB8 outside the walled in confines of his apartment might make a huge difference. But he's likely running into out ground level interference -- trees, other houses, hills, traffic, etc. Don't assume your best reception will be on a direct line to the transmitter. You may find reflections much stronger than a direct line. (I know I do.)
There's works and then there's works well. 300ohm cable is not shielded and thus is part of the receiving antenna. It also has much higher impedance which means higher signal loss. A fuzzy, washed out, ghosted NTSC signal is still watchable. ATSC either works or it doesn't; there's very little watchable middle ground.
That's due to the difference in ATSC chipsets. The Series3/Tivo HD have great multipath rejection which means they will be able to receive a clean signal where older system have trouble. I also have an HR10 -- the first ATSC receiver Tivo ever built; it's reception is horrible due entirely to it's lack of multipath rejection.
Hah. You've never rented an apartment, have you? I've never seen a single apartment/condo/townhome complex that didn't do everything in their power (and more) to prevent antennas and dishes -- "the building is wired for cable, end of discussion". I know of a half dozen HOA's that out-right ban them as well -- which is 100% illegal.
That said, there are a few places around the country where DISH, DirecTV, and cable all live happily together in one massive (expensive) distribution network. But those are rare (vs. the number of apartments and condo's.)
You're going to run into that limit pretty much anywhere you share walls. To be 100% fair, the landlord isn't barring "any" external antenna; it simply has to be within your rented property ("exclusive use area".) He's on the ground floor, so he's screwed. It could be worse... he could be on the wrong side of the building. He needs an antenna on the roof (or 2nd/3rd floor apartment), but he has no legal rights to the roof ("common area") or apartments he's not renting. One option might be ask the upstairs neighbor if you can set this (huge, ugly, etc.) DB8 on their balcony for a few days (weeks?)
Can you say "installation fees"? I knew that you could.
a) There are no "US equivalents".
b) HD streams (even MP4) are huge bandwidth eaters that will exceed most "broadband high-speed" connections. [a good quality MPEG2 SD stream needs 5Mbps.] They will pretty much always exceed a US user's upstream connection speed. Even at 512k, the slingbox output looks like crap. (1.5-1.8M is needed for a good picture and that's still 15fps.)
He's in a ground floor apartment. Where do you think he's going to put any receiving station? He isn't likely to have (legal) access to any property within range of his apartment.
It's not misleding at all. If you are on an IPv4 network, you cannot talk to anything on an IPv6 network. They must both talk IPv4 or IPv6. They are two different things, that form two different networks. We might as well be talking appletalk and vines -- again two completely seperate networks.
Horrible is a matter of opinion; I think it's clever. Hack? Sure. But it is most definately a solution. The only problems with NAT, aside from a very few complicated edge cases, can be attributed to poor protocol design and even poorer implementation... if you bind INADDR_ANY, you don't know what your address is until the connection is established, and you ask the kernel. getipnodebyname(gethostname()...) is just as wrong in today's world of NAT as it was in the years before NAT.
Many cellphone networks provide NAT'd private addresses unless you ask for "vpn service", etc. (and sometimes pay extra.) But it's rather rare these days -- you may not even know your phone is using a private address. I don't know of any commercial ISPs doing this today, but PSINet had some horrible windows only PoS that was NAT'd service. (it failed for many reasons.)
Not anymore. Modern SSL versions provide a hostname hint in the (unencrypted) clienthello so single IP ssl virutal hosting is possible.
This doesn't matter AT ALL since IPv4 systems cannot talk to IPv6 systems, and v.v. They. Are. Completely. Alien. Networks. It just makes it easier to transport IPv4 across IPv6. Without a proxy/translator/etc. IPv6 and IPv4 hosts cannot talk to each other. This is why IPv6 will take decades to be openly adopted -- if ever. (It's already been a decade, btw.)
That's exactly it. When gmail fails, you don't know if it's going to be 3min, 3hrs, or 3days. Or if it will ever be fixed. You are left with no information and no control. When (if) it does come back, you don't know what state it's going to be in... how much of your data is now screwed up and completely gone? What choice(s) do you have in the matter? (none.) With a local server, everything is right there in front of you. You have people you can talk to. You have people to make it right again. You have control, and you are part of the information loop.
For starters, linux is not a "Microsoft enterprise-level software" -- it is something completely, and entirely different.
It's easy to find thousands of people who call themselves "exchange admins", and it's very likely they'll all come waving a peice of paper saying they're "certified". The problem is, more often than not, they're worth less than that paper. The linux camp is similar without the thoundands of paper wavers, as there aren't that many certifications -- and most real linux people won't touch them. (certs are for people who want decorations.)
Bottom line: It's often very difficult to find someone truly qualified for what you need done.
"that's classified, sir." :-)
You missed the point... on the wireless network, one must login to get an address. Thus, there should be records of who logged in and was given a specific address. So, they should have one and only one name for the two wireless addresses.
Of course, if they expire those logs as fast as the dhcp logs, there's nothing to search.
Then why can they nail down the hardwired to one likely suspect but the 2 wireless addresses to dozens of people?
I hate the **AA's as much as anyone, but this sounds like Tufts is simply lying. There are details they aren't telling the courts.
802.1X. Next question.
You don't have to register MACs or any of that crap. And you don't need web page authentication redirects for "unregistered" systems. With 802.1X, you either present the required authentication materials or you get no/limited network access. Granted this is only effective per port which means you couldn't plug in a switch in your dorm room to connect several machines. (in theory you could, but I don't know any switches that will do upstream 1x auth; or at least none kids can afford.)
Most of what Universities are using are very old, hastily cobbled together systems. Better methods have been around for a long time, but they don't have the time or money to mess with building a better system given the current system does actually get the job done. Having worked in that world, there are usually very few people to get a lot of things done. (I was lucky. I only had one lab (~2 dozen PCs) and a maybe a dozen more research systems (some PCs some VMEs) to manage.)
Actually, what they said (and I did read the PDF) is they don't keep logs for more than 10 days and the arp table snapshots are inconclusive. And I'd say their DHCP system is broken as well since the example they give shows an overlaping lease -- presumablly to the same machine, but still an overlap.