New government entity to take control over military and civilian networks

Tech 1984 ^ | 5/31/10 | Tech 1984

[oc-flyfish]

This is pretty scary stuff. The Federal government is ready to seize control of private company networks in order to "protect" us in the event of a hacker attack.

[markomalley]

Oh God, I really was a dork wasn’t I? LOL

Hey, I used to relay from TEN to CAN using a straight key.

And I enjoyed doing so!

[metmom]

Interesting thread.

Not nearly as interesting as your posting history.....

[Quix]

Extremely few posts over so many years, it seems to me.

Therefore what, I don’t know.

[Canadian Outrage]

I think they are Quix, I really do. You are in the midst of a complete takeover and unless and until the America peope RISE UP they will continue to do what they are doing. I’m very disappointed at the reaction to Obama. CO

[Still Thinking]

In my first novel (2003) a computer network guy posted the names and particulars of all of the federal agents in several states on a dispersed system somewhat analogous to gnutella and other music programs.

Oh, I thought he just used the normal interwebs and uploaded the list from a terminal at one of his customers where his identity couldn't be traced.

[Quix]

I must sadly thoroughly agree with you.

It grieves me a lot that so many FREEPERS—well known FREEPERS are mostly clueless about globalism and END TIMES STUFF escalating before our very eyes almost daily.

Sheesh. What does it take, the smell of dying brothers and sisters in the gas chambers around the corner?

It does make it slightly easier to understand Jews on the way to the death camps still believing they were going to a new job and a new life.

Willful blindness indeed.

[The Comedian]

My LDS stake in San Diego had ham radio ops, but also had an effective "phone tree" and "on the ground" connectivity via foot or bicycle. We could account for 5,000 people in the space of 30 minutes without phone or radio.

That's brilliant Quix.

AlarmAndMuster.com, same idea.

I'd be all in favor of trying to start something like that here.

Frowning takes 68 muscles.
Smiling takes 6.
Pulling this trigger takes 2.
I'm lazy.

[oc-flyfish]

Only problem with Wifi is the limited reach it has. You would literally need every other neighbor to be setup the same for it to work.

[oc-flyfish]

Yes, I have been absent from FR for a while... so what does that indicate to you? Am I a mole? Jeesh...

[thecodont]

My LDS stake in San Diego had ham radio ops, but also had an effective "phone tree" and "on the ground" connectivity via foot or bicycle. We could account for 5,000 people in the space of 30 minutes without phone or radio.

That's very impressive!

[nw_arizona_granny]

Ping.

[thecodont]

Oh man... nostalgia... http://www.fidonet.org/

"...only e-mail and USENET..."

USENET, the land of content!

[oc-flyfish]

Yup! :-)

[Myrddin]

Only problem with Wifi is the limited reach it has. You would literally need every other neighbor to be setup the same for it to work.

That's why you use mesh networking. Everybody participates in the mesh and provides a path to other nodes. I used an OLSR network to allow the locomotive on a long train to pass messages both ways down a long train...even if it was wrapped around a mountain. A line of sight 802.11b can pull off a 1 mile link with off the shelf hardware. I've used custom hardware with bigger power amps on a large airplane to achieve links over 50 miles.

[oc-flyfish]

Wow that is impressive! Would an amp that big (airplane) interfer with normal household electronics?

If not your mesh concept has serious legs.

[oc-flyfish]

It still would be difficult to implement though. You would need static routes defined to route traffic to the mesh network, assign IPs, etc. Most people would have no idea how to integrate into their existing network even if they wanted to.

[Gondring]

USENET, the land of content!

Yeah, and to look back at what I posted more than two decades ago...yikes!

You know, I was going to say we're dinosaurs, but I guess you have even that topped (with your FR screen name)!

[Quix]

THX FOR YOUR KIND WORDS.

My ideas were similar but the LDS pulled it off.

FREEPERS CAN DO

IF WE WILL DO.

[Myrddin]

You don't need static routes. OLSR has node discovery and sophisticated routing built in. That's why I chose it for my application. The user side can be accomplished with a common wireless access point with its own DHCP server. You would still need some form of DNS service or static host files for well known servers. My application was strictly peer to peer UDP. The set of IP addresses was a well known set. That isn't the case with the Freifunk network in Germany. There are over 40,000 nodes working there. It is used is 3rd world countries to share limited internet connectivity over a broad area

See OLSR research, OLSR code, English Wiki for Freifunk for actual working code, research papers and descriptions of networks currently in place. OLSR supports IPv6 and IPv4. If you use the version of the protocol that evaluates signal strength, that will be factored into the optimal routing. On the railcars, I had the routes updating at 10 times per second. I did that to ensure minimum latency as the packets contained control information for brakes, anglecock valves, cut levers as well as feedback on bearing temperatures, limit switches and control system status off each rail car.

[Myrddin]

The radio I used for the test is probably out of the price range that most of us would be willing to pay. It was part of a well funded project I supported a few years ago. You can purchase a more reasonably priced "pole mounted" bi-directional amp for 2.4 GHz that is commonly employed by wireless ISPs in rural areas. See 2.4 GHz 100 mW to 3 W Amps or 3W to 25W amps. You'll want to break out your FCC rules & regs before firing up the big amps. A directional antenna is a good idea with this gear.