Now is the time if you care to have everyone you know stand-up for *decreased* regulation in the last mile and locally, not more. The cost of building high speed access to your location is not in the long-haul but the local access network. Long-haul costs are at their lowest point ever, but getting to the major locations is always the expensive part. Labor costs, including engineering and permits make the cost of installing fiber or other technology insignificant.
Fiber and media converters are suitably cheap. You can get the TP-LINK MC220-L for around $20-30, and the optic for as low as $35 depending on your source and type/distance. This works well as you don't have to worry about shielded cabling if you ran something like cat5/6. You can also reach much further distances than with copper wire. You don't necessarily need permits, but you do need to call MISS-DIG, or whatever the local version of that is. When the guy comes out, tell him exactly what you are planning on doing, route, possible routes, etc. Most places require a hand dig within a few feet of any marked utility. The rest you can use a rented trencher to do. Running conduit will make a lot of sense, you typically need schedule-80 which you won't find at lowes/home depot. You can also call a contractor to do this work, depending on the distance it may only cost a few thousand dollars at most. If your goal is to keep things super-low cost, then wifi or other networking may be your ideal solution. Look at the hardware from ubnt.com and see what works. If you don't have line of sight, you will need to run a cable to make this work. If cost doesn't come into the equation, you can also get SFP+ PCIe cards and do this at 10Gb/s vs 1Gb/s much easier. Make sure you run single model fiber, otherwise you may have troubles if you encounter older OM1/OM2 and try to launch 10G signals.
Hope it works out!
If you saw this problem, your NTP time sources were not properly configured and diverse.
Consider using the NTP pool and not relying on so few sources to properly sync your time. Read 5.3.3 and 5.3.4 from http://support.ntp.org/bin/view/Support/SelectingOffsiteNTPServers for help to correct your NTP setup.
You're talking about small routers. I'm talking about stuff like t1600 where everything is done entirely in hardware. If you look at the QFP in the ASR1k (cisco) you will see where it can do the nat, etc in hardware. that's more sensible than a lot of the devices where things are just pure slow-path (ie: punted to cpu for the fib lookup based on the various ribs your device may have).
We're talking about entirely different classes [and engineered uses] of equipment, and that's obvious to me. Hope you understand that as well.
You are talking about a Firewall device that performs NAT, (and appears as a "router" on the lan. Most of what you see at the store/online is not a "real" router IMHO. Then again, I'm biased as I deal with n*10G all day in a large network. When people call those devices at their home a 'modem' or 'router' i generally wince. I think of them more along the lines of a media converter (dsl, cable to rj45/802.3)
Real routers don't have 'state tables'.
Ask your ISP for IPv6 access. Enable your web server/site for IPv6 day. Use a 'web bug' tracker item to identify broken thins.
visit places like http://test-ipv6.com/ to try to understand how ready you are.
Make sure if you have a tunnel, or use one, you do not add too much latency to your connection. The CDNs won't send your traffic over IPv6 if your IPv6 goes to some other continent or geographical region.