Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TowerTalk\]\s+2\.4\s+GHz\s+interference\s+concerns\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TowerTalk\]\s+2\.4\s+GHz\s+interference\s+concerns\s*$/: 4 ]

Total 4 documents matching your query.

1. [TowerTalk] 2.4 GHz interference concerns (score: 1): Author: Charles Lind <cxl24@case.edu>; Date: Thu, 7 Mar 2013 22:44:18 +0000; Many thanks for the replies. Perhaps a bit more detail is in order: I have been looking into running my station fully remote at times, and in general it appears that good internet is a priority. Here; /archives//html/Towertalk/2013-03/msg00088.html (7,886 bytes)
2. Re: [TowerTalk] 2.4 GHz interference concerns (score: 1): Author: "Walter A. Carrington" <wc@mathmicro.com>; Date: Fri, 08 Mar 2013 18:48:21 -0500; It's easy to check for interference: find a ham who uses the bands, modes and power you use and see if it disrupts his wireless internet. Many people use wireless (802.11) to connect their logging co; /archives//html/Towertalk/2013-03/msg00097.html (7,855 bytes)
3. Re: [TowerTalk] 2.4 GHz interference concerns (score: 1): Author: Jim Miller <jim@jtmiller.com>; Date: Fri, 8 Mar 2013 18:52:51 -0500; Check with users of HSMM. They repurpose 2.4G routers to do mesh stuff with ham radio. Colocation there for sure and they'd easily see any interference. 73 jim ab3cv _________________________________; /archives//html/Towertalk/2013-03/msg00099.html (7,375 bytes)
4. Re: [TowerTalk] 2.4 GHz interference concerns (score: 1): Author: "Marlon K. Schafer $509-982-2181$" <ooe@odessaoffice.com>; Date: Fri, 8 Mar 2013 16:44:46 -0800; Hi Charles, Two suggestions for you. First look around the area and see if there is already a WISP in your neck of the woods (odds are normally very high that there is). That'll save you a lot of tro; /archives//html/Towertalk/2013-03/msg00100.html (10,095 bytes)

Current List: 1 - 4
Page: [1]