I work at a sort of small ISP and we've done testing, implementation, published our website with an AAAA record and put some information on the site for everyone to see.

We've gotten exactly one call (this morning) on IPv6 that I can remember. We published information and started doing some obvious IPv6 things, but no one cares. The group of dual-stack test accounts is pretty small, but they have not even seemed to care or notice. I'd put anyone that asks on a list for testing so they can use IPv6 at home. No one has asked. I guess I could put a big(er) banner on the page.. but really I don't think it would matter much.. and probably scare people.

All in all I will say the experience has been pretty anti-climatic. It was not that difficult to implement. There were bugs of course, (Fedora 13+14 blocking DHCPv6 client traffic, and other NetworkManager bugs) the Cisco CMTS and it's weird detection of static IPv4 only clients... duplicate address detection madness, incomplete support of DHCPv6 + SLAAC in routers (D-Link DIR-615..) but it was just me working on it and I did not have that difficult a time getting our network to route, connect and answer to IPv6. Most of the problems I dealt with were incomparable hardware. Routers and DOCSIS 2.0 + IPv6 modems which are pretty much non existent with the exception of one EMTA I've tested. You have to shell out the bucks for a DOCSIS 3.0 modem evidentially.

Of the D-Link routers I've tested the DIR-825 is the star. It was dead easy to configure. DD-WRT and Open-WRT are not easy and probably there is no build for your router if it only has 4Mb of flash.

This sounds like a tall order. I'd be scared. Buying equipment is not going to fix anything. You've got to learn the existing network before you can make educated purchases. From the scope of the network you describe, here are the basic things I think you'll need to learn about.

Learn about routing. Subnets, CIDR, the differenec between a subnet mask and a wildcard, the difference between static routing protocols and dynamic routing protocols. Default routes. Policy based routing. Observe and document the different subnets you see in your network, figure out their purpose. Look at the default gateway of the clients and the servers. Figure out what device that represents. If you have only one subnet, your network is probabbly to flat. I'm guessing you have at least 2 or 3. Make a diagram.

Learn about VLANS. Tagged VLANS (802.1q), Cisco VLAN discovery (if applicable). I prefer Brocade equipment for switching / layer 2. But I digress. What VLANS are in each switch and how do the physical wires correlate? What subnets run on what VLANS? If you have fiber, you have another heap of things to learn about. Learn how to make an ethernet cable.

Learn about firewalls. iptables (if Linux), ASA / PIX if Cisco etc.. Learn the difference between access-lists and statefull firewalls. Learn how to add rules to whatever firewall you use. What networks route where and what firewalls are between the networks?

What are the single points of failure? Learn to deal with those single points of failure. What are the entry points? What software is everything running? What are the link speeds, where does traffic go, aggregate and split up?

Gather all the contract information for your equipment. Make a printed list of numbers for who to call about what. Seek consultation to fill any uncovered gaps.

Look into graphing software with auto discover. PRTG is wonderful and not that expensive.

In my experience, things don't usually break. When they do it's because:

A.) Someone touched something.
B.) The power went out.
C.) Someone touched something they were not supposed to.
D. ) You ran out of capacity (in a hard drive, on a link.)
E.) A server got overwhelmed.

Lastly, make sure everyone does their Windows updates :-)

1.) If it's not broke, don't fix it. Why does this network need "rebuilt?" What's not working?
2.) Make sure you can put it back exactally how you found it before trying anything.
3.) Never, ever, make a change at the end of the day, or on a Friday. Come in early, real early, for big stuff.
4.) Listen to your users. If they say somethings different, it probabbly is. Take everything seriously.

Rumor has it that Star Trek IV was to originally use an Amiga in the transparent aluminum scene, but Commodore would not loan the studio a computer. Apple, however was happy to. As you all know, the Amiga was a superior, less expensive product, just marketed much more poorly. :-)

There were several real, appropriate examples of UNIX in the movie. Things like "ps -ef | grep badprocess" and "kill -9 badprocessid". I caught that as it went by very quickly and was surprised at the accuracy.

One of the displays showed a very Solairs looking version of top and login. I doubt this circa 1983 teminal had Solaris on it however.

I also thought it was cool that the son looked to see what the father was up to by starting a bash shell and running something like /usr/bin/history to see what his last commands were. That whole sequence was pretty accurate. Overall though, I left the movie feeling a bit uninspired. Not that it was bad movie... it was just felt rushed with no real sense of drama.

Price out dedicated bandwith in a big city sometime. There's plenty of competition and the best you can do in a big city is 2-8 dollars a Mb.

$195/Month for 150Mbs is $1.3 a Mb. Assuming that you can get those speeds reliably, and from all accounts you can, that's ridiculous cheap.

At the most populous carrier hotels in NYC (60 Hudson and 111 8th) the cheapest you can get from all 15 or 20 Tier 1 and Tier 2 providers that tangle those places with their fiber is $2 / Mb. And this not having it conveniently delivered to your door step. It's off some switch in a co-located rack in a crowded data center in the city that you pay for transit to.

And since were are talking a data center that shares ports owned by Google, Limelight, Akamai, Level 3, Verizon, you name it, money changing hands and bidding happen on circuits by the hour. There's plenty of competition for the bandwith provider in NYC, and the best they can do is roughly $2.00/Mb.

Verizon is UNDENIABLY underselling their FiOS bandwidth. They own the 2nd biggest Tier 1 network so they can. Another thing you should know is that Verizon put the breaks on new fios rollouts because they were taking huge hits for each new installation.

http://jeremyreimer.com/totalshare5.gif

Dominant? Hardly.

The C64 had almost 50% market share and the Amiga was very even with the Macintosh until the early 90's.
The world was Commodore's oyster. They became misguided in the late 80's and really screwed it up by the early 90's, well after the GUI boat had sailed.

http://slashdot.org/comments.pl?sid=61425&cid=5772514

This is the slashdot discussion about Mark Zuckerberg's Synapse Media Player in 2003, referencing what I can only imagine he wrote on the project's homepage.

College freshmen are very motivated when it comes to sex.

I work for an ISP. I came up with this.

We have a dial in clapper that activates power to a cheap switch connected to a public facing SSH relay host. So, I call a number. It turns on the switch for 1 hour. I then log into this relay host on some port other than 22 with a pretty strong password. From there, I can ssh to our other servers. It's one point of access for most everything.

My boss is fully briefed on the system. If I leave, unplug the phone line, switch it to another number change the password and watch the logs.