[quote]LIFTICVSMAXIMVS wrote:
Vegita wrote:
LIFTICVSMAXIMVS wrote:
jawara, no I am not familiar with it but I assume it has something to do with electronic warfare…?
Wait are you saying you are an ex US military member? Dude the governmnent told me you’re a terrorist, or at least could be. Get off our website for we start torturin ya!
V
On kinda a funny and related note, I have some friends who are former military intelligence friends (now working as civilians in Defense Intelligence Agency) that keep a facebook page and even joke about using it to gather “hum-int”. Some of the stuff they tell me really scares me…they are some real whack jobs that get off on a power trip, but I love the dumb fuckers.[/quote]
To answer your question I am not sure what the limitations would be. I guess it would depend on the power of the receivers and transmitters. In densely populated areas we would not need something so powerful being able to piggyback off of other closely placed devices. Out in the country maybe one would need a satellite like device…
[quote]LIFTICVSMAXIMVS wrote:
I don’t think the infrastructure will ever be able to be controlled by one entity especially as technology improves.
Eventually we won’t even need an ISP to go online because every computer will be its own provider negotiating multiple HF radio waves to resolve internet addresses via onboard routers, switches, and bridges. In this respect the “internet” would be completely open. There would however still need to be an addressing registry whether it is IP like or based on something completely different…I am thinking if all computers eventually become stand alone routers addresses could just be resolved to the MAC without an IP standard.
Any ideas out there…[/quote]
someone will always control the flow of data. you will have to have some sort of provider and transverse a routed network. pier to pier stuff may be capable of passing the sniff test but this would be extremely limited. CALEA is catching up to data networks pretty fast. as long as someone controls routing infomation they can manipulate where the date going out or coming into your computer goes. With addresses and routes changing constantly there is just no way to navigate the WWW without routing.
[quote]LIFTICVSMAXIMVS wrote:
A switch, bridge, and router are for all intents and purposes the same piece of equipment. They are just devises that are used to send packets of data. In the old days of the internet – like 10 years ago – they were separate pieces of hardware. Routers can do the work of the two other devices.
To answer your question I am not sure what the limitations would be. I guess it would depend on the power of the receivers and transmitters. In densely populated areas we would not need something so powerful being able to piggyback off of other closely placed devices. Out in the country maybe one would need a satellite like device…
[/quote]
Just not possible in large networks. Tiered routing is absolutly essential in all but relatively small networks. In order to do this you would need enourmous static routing tables that would need to be updated everytime there was a topology change. You not have to know where you destination is, but every single point or devise you use to get there. Just not feasable without some sort of automated routing protocol. If you are reling on routing updates via OSP, RIP, BGP, or any other routing protocol, you data can easily be rerouted to a device that will duplicate the information to a mirror site.
[quote]
This is the idea I have: The router will reside on our PC just like an ethernet card. The difference is it would have to work as a stand alone device from the PC to relay 3rd party data – i.e., data that we did not request for ourselves. Our PC would still have to go thru the TCP/IP protocol stack to request a service, though we would probably by default get the highest priority for service.
I am also thinking that as memory becomes cheaper, larger, and faster there will be huge data caches that we will be able to access as a failover. For example, I request a http service from T-Nation but the service is temporarily busy so it goes to one of the many various data caches until the real time service becomes available. Data caches would have to update on a load available basis. This obviously gets difficult to do with high volumes of real time data updates but nothing that some solidly designed software cannot handle.
The real difficulty would be engineering the sending and receiving device and designing a protocol to resolve addressing.[/quote]
It’s not addressing that is the problem, it is resolving the route to get between devices.