On Thursday 23 April 2015 10:19:31 Rick Lair wrote: > Interference more than distance, its only about 60 ft away, but in > between that is a 60,000lb horizontal boring mill, 3 VMC's, and a 12 > ft wide, 10ft tall finished parts rack, and it is inside the office, > inside the server closet.
Thats pretty close to a description of being dead in the water. :( Even a local flea powered wireless mouse might give it fits. > I have been thinking about slaving another wireless router centrally > in the shop itself, off of the main wireless router in the office, we > have 5 or 6 PC's randomly throughout the shop for programming, that > all run off the wireless. > > Rick If you must have wireless, then that is the way to go, but I'd hard wire it to the central router/switch, and operate it on a higher channel number, and the one in the office on a lower channel number, like 11 and 1 to cut down on the crosstalk confusion. Both on channel 6 would probably have latency problems as they sort it out. That is why there is a once bright blue cat5 strung across my backyard to the shop. I say once bright because its been there, blowing in the wind, which once topped 100 mph, for much of a decade now & its getting sunbleached. 100Mb circuit, solid as a rock yet today. But setup a security model the WPS button on a neighbors rig can't auto-hack. 2 kilobit key phrases would be a good start as it would build a high wall around you the script kiddies probably can't climb. Since router makers don't brag about the key phrase buffer size, I'd separate the men from the boys by trying that size of key. If you cannot reconnect with that keysize, try 1024. If that doesn't work, try 512. IMO if it works at 1024 but not at 2048, I'd be tempted to change the brand name & model on the label, its not as secure as the propaganda on the box claims. If it can be reflashed with dd-wrt, do it, no known backdoors & every router I've ever done that to has been bulletproof.. Factory stuff usually has several backdoors. I would also throw away anything that uses dhcp to get its address, hard code that stuff in an /etc/hosts file common to all machines. Ditto for /etc/resolv.conf, it only needs one line, "nameserver $ipv4_addr_of_router". The interfaces file is also common to all machines except for that machines address, same as hard coded into the hosts file for that machines hostname. That way if the radio connection exists, it just works, there should not be any complex dhcp negotiations to muck it up. And just to make sure, sudo apt-get purge Network-Manager. You do not need it mucking around in your network, constantly tearing a working connection down because it thinks it can find a better one. I hope this helps. Gives you a target to work for I hope. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
