<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;D0IMQng4fCp7ImA9WhdRFUs.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544</id><updated>2011-08-05T13:33:03.634-04:00</updated><category term="roaming" /><category term="mounting assets" /><category term="Vista" /><category term="attenuation" /><category term="benefits" /><category term="signal coverage" /><category term="interference" /><category term="access point" /><category term="certifications" /><category term="WiBro" /><category term="latency" /><category term="mesh" /><category term="troubleshooting" /><category term="applications" /><category term="issues" /><category term="municipal Wi-Fi" /><category term="video" /><category term="WiMAX" /><category term="firmware" /><category term="FHSS" /><category term="performance" /><category term="802.11n" /><category term="rf shielding" /><category term="SNR" /><category term="basics" /><category term="ROI" /><category term="site survey" /><category term="authentication" /><category term="data rate" /><category term="WireShark" /><category term="webinar" /><category term="security" /><category term="robots" /><category term="client devices" /><category term="802.1x" /><category term="802.16" /><category term="automobile" /><category term="products" /><category term="general technology" /><category term="WEP" /><category term="beacon interval" /><category term="software" /><category term="range boundary" /><category term="battery life" /><category term="newsletter" /><category term="cordless phones" /><category term="Colubris" /><category term="VoWLAN" /><category term="standards" /><category term="components" /><category term="middleware" /><category term="range extension" /><category term="requirements" /><category term="multicast" /><category term="Meraki" /><title>Wireless Network Implementation Tips</title><subtitle type="html">Jim Geier, Principal Consultant of Wireless-Nets, Ltd., shares his tips and opinions on developing and deploying wireless networks.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://wireless-nets.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>66</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/WirelessNetworkImplementationTips" /><feedburner:info uri="wirelessnetworkimplementationtips" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>WirelessNetworkImplementationTips</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><entry gd:etag="W/&quot;A0MEQXw6cSp7ImA9WxNRGEk.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-7572690426406034561</id><published>2009-09-13T09:37:00.001-04:00</published><updated>2009-09-13T09:43:20.219-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-13T09:43:20.219-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="802.11n" /><category scheme="http://www.blogger.com/atom/ns#" term="standards" /><title>802.11n now ratified!</title><content type="html">The IEEE Standards Board recently ratified the 802.11n amendment to the 802.11 standard. This marks the final approval of a fairly long process. Of course many companies have been deploying 802.11n networks over the past couple years, and the Wi-Fi Alliance has already certified numerous products based on Draft 2 of 802.11n. You can likely upgrade products previously certified by Wi-Fi (802.11n, Draft 2) products to the ratified version.&lt;br /&gt;&lt;br /&gt;By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-7572690426406034561?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/PEzlMKu8Oik" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/7572690426406034561/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=7572690426406034561" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7572690426406034561?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7572690426406034561?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/PEzlMKu8Oik/80211n-now-ratified.html" title="802.11n now ratified!" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2009/09/80211n-now-ratified.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEUCQX0zfyp7ImA9WxRbE0Q.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-7866812796550514996</id><published>2008-12-04T08:11:00.000-05:00</published><updated>2008-12-04T08:11:00.387-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-04T08:11:00.387-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="troubleshooting" /><category scheme="http://www.blogger.com/atom/ns#" term="firmware" /><category scheme="http://www.blogger.com/atom/ns#" term="client devices" /><category scheme="http://www.blogger.com/atom/ns#" term="access point" /><category scheme="http://www.blogger.com/atom/ns#" term="Vista" /><title>Solving Vista wireless connection problems</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;When beginning to use Vista, you may have troubles connecting to wireless / Wi-Fi networks. A problem is that Vista implements special functions that some access points don’t recognize. Sometimes connectivity will drop intermittently, especially if a Vista-based computer is connecting to a wireless access point that is not fully Vista compatible. If you’re having connection problems, check with the access point vendor, and see if newer firmware versions for the access point include Vista support.&lt;br /&gt;&lt;br /&gt;If updating the access point firmware doesn’t solve the problem, try disabling Vista’s autotuning (which isn’t supported by some access points):&lt;br /&gt;1. Click Start.&lt;br /&gt;2. Type cmd in the search box.&lt;br /&gt;3. Type CTR+SHIFT+ENTER. This opens the command prompt with elevated privileges.&lt;br /&gt;4. The command prompt window will appear. You’ll know this is the correct privilege level if system32 shows up in the directory path&lt;br /&gt;5.      Type netsh int tcp set global autotuninglevel=disable, and hit Enter&lt;br /&gt;6.      After the command prompt window displays OK, restart your computer, and autotuning will be disabled.  &lt;br /&gt;&lt;br /&gt;If this doesn’t help, reactivate autotuning by following the same steps as above, but type netsh int tcp set global autotuninglevel=normal in the command window.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-7866812796550514996?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/OHvWI1UH72w" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/7866812796550514996/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=7866812796550514996" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7866812796550514996?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7866812796550514996?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/OHvWI1UH72w/solving-vista-wireless-connection.html" title="Solving Vista wireless connection problems" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/12/solving-vista-wireless-connection.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0ECQXcyeyp7ImA9WxRbEks.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-1687382566354189381</id><published>2008-12-02T21:01:00.000-05:00</published><updated>2008-12-02T21:01:00.993-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-02T21:01:00.993-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="performance" /><category scheme="http://www.blogger.com/atom/ns#" term="troubleshooting" /><category scheme="http://www.blogger.com/atom/ns#" term="multicast" /><title>How to: Get the most from 802.11 multicasting</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Multicasting over wireless LANs can make better use of capacity for some applications, but beware of the potential issues! Learn how to best satisfy performance and battery life when using multicast applications referring to a tutorial I just posted at &lt;a href="http://www.wireless-nets.com/resources/tutorials/802.11_multicasting.html"&gt;http://www.wireless-nets.com/resources/tutorials/802.11_multicasting.html&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-1687382566354189381?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/ehZrcIRfQ6g" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/1687382566354189381/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=1687382566354189381" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/1687382566354189381?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/1687382566354189381?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/ehZrcIRfQ6g/how-to-get-most-from-80211-multicasting.html" title="How to: Get the most from 802.11 multicasting" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/12/how-to-get-most-from-80211-multicasting.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE4ERXk8cCp7ImA9WxRUFkk.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-8391566740279446419</id><published>2008-11-25T14:55:00.000-05:00</published><updated>2008-11-25T14:55:04.778-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-11-25T14:55:04.778-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="security" /><title>How to: Define wireless network security policies</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Because of the use of radio waves, a wireless network is not secure unless you take special precautions. Learn what you need to consider when defining the wireless network security policies for your company by referring to a tutorial I just posted at &lt;a href="http://www.wireless-nets.com/resources/tutorials/define_wireless_security_policies.html"&gt;http://www.wireless-nets.com/resources/tutorials/define_wireless_security_policies.html&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-8391566740279446419?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/zBNrGxiO3oo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/8391566740279446419/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=8391566740279446419" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/8391566740279446419?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/8391566740279446419?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/zBNrGxiO3oo/how-to-define-wireless-network-security.html" title="How to: Define wireless network security policies" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/11/how-to-define-wireless-network-security.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0MEQXs8eip7ImA9WxRUEU0.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-667407295007639</id><published>2008-11-19T08:30:00.000-05:00</published><updated>2008-11-19T08:30:00.572-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-11-19T08:30:00.572-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="interference" /><category scheme="http://www.blogger.com/atom/ns#" term="range boundary" /><category scheme="http://www.blogger.com/atom/ns#" term="access point" /><category scheme="http://www.blogger.com/atom/ns#" term="802.11n" /><category scheme="http://www.blogger.com/atom/ns#" term="webinar" /><category scheme="http://www.blogger.com/atom/ns#" term="signal coverage" /><category scheme="http://www.blogger.com/atom/ns#" term="SNR" /><category scheme="http://www.blogger.com/atom/ns#" term="roaming" /><category scheme="http://www.blogger.com/atom/ns#" term="site survey" /><title>Wireless site survey tips</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I recently completed a webinar titled “Wireless Site Survey Tips,” and you can view its audio/visual recording on my website at &lt;a href="http://www.wireless-nets.com/training/wireless_survey_tips.html"&gt;http://www.wireless-nets.com/training/wireless_survey_tips.html&lt;/a&gt;. In the webinar, I explain tips on preparing for a survey, performing testing, choosing tools, and determining optimum installation locations for access points (including coverage for elevators and multiple floors).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-667407295007639?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/9CpY9JI7o9k" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/667407295007639/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=667407295007639" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/667407295007639?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/667407295007639?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/9CpY9JI7o9k/wireless-site-survey-tips.html" title="Wireless site survey tips" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/11/wireless-site-survey-tips.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU4MQ3Y6fyp7ImA9WxRUEE4.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-5163723463982237611</id><published>2008-11-12T14:51:00.000-05:00</published><updated>2008-11-18T14:53:02.817-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-11-18T14:53:02.817-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="access point" /><category scheme="http://www.blogger.com/atom/ns#" term="802.11n" /><title>How to: Choose the right spectrum for 802.11n deployments</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;With 802.11n, you have a choice of using 2.4 GHz or 5 GHz spectrum. Gain a better understanding of what you should take into account when deciding which spectrum to deploy by referring to a tutorial I just posted at &lt;a href="http://www.wireless-nets.com/resources/tutorials/choose_802.11n_spectrum.html"&gt;http://www.wireless-nets.com/resources/tutorials/choose_802.11n_spectrum.html&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-5163723463982237611?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/noECHfO_Lk8" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/5163723463982237611/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=5163723463982237611" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/5163723463982237611?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/5163723463982237611?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/noECHfO_Lk8/how-to-choose-right-spectrum-for-80211n.html" title="How to: Choose the right spectrum for 802.11n deployments" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/11/how-to-choose-right-spectrum-for-80211n.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU8CRX08cSp7ImA9WxRUEE4.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-3258158181977556082</id><published>2008-11-05T14:47:00.000-05:00</published><updated>2008-11-18T14:51:04.379-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-11-18T14:51:04.379-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="troubleshooting" /><category scheme="http://www.blogger.com/atom/ns#" term="WireShark" /><title>How to: Sniff wireless packets with WireShark</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;WireShark is free software that sniffs packets on wireless networks. You can learn tips on configuring and using this tool when analyzing and troubleshooting 802.11 wireless networks by referring to a tutorial that I just posted at &lt;a href="http://www.wireless-nets.com/resources/tutorials/sniff_packets_wireshark.html"&gt;http://www.wireless-nets.com/resources/tutorials/sniff_packets_wireshark.html&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-3258158181977556082?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/xZ_ukTCafgs" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/3258158181977556082/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=3258158181977556082" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/3258158181977556082?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/3258158181977556082?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/xZ_ukTCafgs/how-to-sniff-wireless-packets-with.html" title="How to: Sniff wireless packets with WireShark" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/11/how-to-sniff-wireless-packets-with.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0QMQX88fSp7ImA9WxRWE0s.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-5080633714279774410</id><published>2008-10-30T08:23:00.000-04:00</published><updated>2008-10-30T08:23:00.175-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-30T08:23:00.175-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="WiMAX" /><category scheme="http://www.blogger.com/atom/ns#" term="certifications" /><title>Looking for certified WiMAX products?</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Many of my clients often ask which companies are offering WiMAX products that have actually gone through certification testing and have valid WiMAX certificates. The best place to find this information is on the WiMAX Forum website at &lt;a href="http://www.wimaxforum.org/kshowcase/view"&gt;http://www.wimaxforum.org/kshowcase/view&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-5080633714279774410?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/VpDYIetyAo0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/5080633714279774410/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=5080633714279774410" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/5080633714279774410?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/5080633714279774410?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/VpDYIetyAo0/looking-for-certified-wimax-products.html" title="Looking for certified WiMAX products?" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/10/looking-for-certified-wimax-products.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkcEQH84eip7ImA9WxRWEk0.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-7398147929455643949</id><published>2008-10-28T09:20:00.000-04:00</published><updated>2008-10-28T09:20:01.132-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-28T09:20:01.132-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="WiMAX" /><category scheme="http://www.blogger.com/atom/ns#" term="WiBro" /><category scheme="http://www.blogger.com/atom/ns#" term="802.16" /><title>WiBro and mobile WiMAX confusion</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Based on conversations with some of my associates, there seems to be some confusion between WiBro, the wireless network being deployed in Korea, and mobile WiMAX. Some think that WiBro is something completely different than WiMAX. Actually, WiBro is based on the same IEEE 802.16e-2005 standard as Mobile WiMAX. WiBro has functionality defined by the Mobile WiMAX system profile, with identical PHY, MAC and Power Classes to Mobile WiMAX. Also, WiBro will be certified using the Mobile WiMAX certification processes and laboratories. For more details on relationship between WiBro and mobile WiMAX, refer to the following document: &lt;a href="http://www.wimaxforum.org/news/WiBro_and_Mobile_WiMAX_Backgrounder.pdf"&gt;http://www.wimaxforum.org/news/WiBro_and_Mobile_WiMAX_Backgrounder.pdf&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-7398147929455643949?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/5lpRi144PS4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/7398147929455643949/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=7398147929455643949" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7398147929455643949?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7398147929455643949?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/5lpRi144PS4/wibro-and-mobile-wimax-confusion.html" title="WiBro and mobile WiMAX confusion" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/10/wibro-and-mobile-wimax-confusion.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUABQX85fSp7ImA9WxRXGEs.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-4712635748648384328</id><published>2008-10-24T09:02:00.000-04:00</published><updated>2008-10-24T13:02:30.125-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-24T13:02:30.125-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="middleware" /><category scheme="http://www.blogger.com/atom/ns#" term="roaming" /><title>Wireless middleware important for mobile systems</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Wireless middleware software resides between client software and the application server or databases and offers intermediate communications that elevate wireless issues, such as coverage holes. The middleware, which generally runs on a dedicated gateway platform attached to the wired network, processes the packets that pass between the wireless client and the server. As a result, middleware offers efficient and reliable communications over the wireless network, while maintaining appropriate connections to application software and databases on the server via the more reliable wired network.&lt;br /&gt;&lt;br /&gt;For example, wireless middleware has store-and-forward messaging that queues traffic to ensure delivery to client devices that lose connections with the network. This is often referred to as session persistence. The middleware is able to act as a proxy of the client. In fact, most applications have no idea that the middleware server is maintaining the connection with the host. Once the client gains wireless connectivity again, the middleware lets the client resume communications. This is especially beneficial when servers and applications can’t tolerate the loss of connectivity, such as with public safety applications in municipalities.&lt;br /&gt;&lt;br /&gt;If transmissions are unexpectedly cut at midstream, “intelligent restart” is a middleware recovery mechanism that detects the premature end of a transmission. When the connection is reestablished, the middleware resumes transmission from the break point instead of at the beginning. This not only enables wireless clients to easily reestablish connectivity, it also helps with improving performance and reducing battery drain due to fewer packet retransmissions.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-4712635748648384328?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/IoxQv3sTM-k" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/4712635748648384328/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=4712635748648384328" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/4712635748648384328?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/4712635748648384328?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/IoxQv3sTM-k/wireless-middleware-important-for.html" title="Wireless middleware important for mobile systems" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/10/wireless-middleware-important-for.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0IMQXY6fip7ImA9WxRXGEs.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-4846252088622773314</id><published>2008-10-21T13:50:00.000-04:00</published><updated>2008-10-24T12:26:20.816-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-24T12:26:20.816-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="requirements" /><category scheme="http://www.blogger.com/atom/ns#" term="interference" /><category scheme="http://www.blogger.com/atom/ns#" term="security" /><category scheme="http://www.blogger.com/atom/ns#" term="issues" /><title>Common wireless network deployment risks</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;In the past years, I’ve been involved with wireless networks for many different venues, including hospitals, airports, universities, and enterprises. I’ve been seeing a trend of mistakes that companies deploying wireless networks make. Unclear requirements, RF interference, security weaknesses and non-optimal application interfaces are leading problems. You can view more details about these types of deployment risks in a tutorial I just posted at the following URL: http://www.wireless-nets.com/resources/tutorials/identify_wireless_lan_deployment_risks.html&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-4846252088622773314?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/VT_9LVJXLcA" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/4846252088622773314/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=4846252088622773314" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/4846252088622773314?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/4846252088622773314?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/VT_9LVJXLcA/common-wireless-network-deployment.html" title="Common wireless network deployment risks" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/10/common-wireless-network-deployment.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0MER305fip7ImA9WxRXGEs.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-7809459591213173649</id><published>2008-10-16T12:21:00.000-04:00</published><updated>2008-10-24T12:23:26.326-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-24T12:23:26.326-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="range extension" /><category scheme="http://www.blogger.com/atom/ns#" term="signal coverage" /><title>Beacon transmission rate impacts range</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I’ve been testing the range of various radio cards in a laptop against an 802.11b/g access point. I found that the access point vendor (Proxim) changes the beacon transmission rate, depending on whether the access point is configured for mixed b/g mode or b-only mode. In mixed b/g mode, the beacon transmission rate is 2Mbps. In b-only mode, the transmission rate is 1Mbps. I consistently found that b-only mode offered better range (about 20%) compared to mixed b/g mode. This occurs because the lower beacon data rate allows the radio cards to maintain connections at greater ranges (receive sensitivity at 1Mbps is about 3dB better than at 2Mbps). When deploying wireless LANs for greater range, consider operating in b-only mode. Of course this will keep b/g radio cards from operating above 11Mbps.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-7809459591213173649?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/uugROeWSKy4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/7809459591213173649/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=7809459591213173649" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7809459591213173649?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7809459591213173649?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/uugROeWSKy4/beacon-transmission-rate-impacts-range.html" title="Beacon transmission rate impacts range" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/10/beacon-transmission-rate-impacts-range.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0UAQ38_fyp7ImA9WxRXGEs.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-5462583893159998832</id><published>2008-10-14T12:17:00.002-04:00</published><updated>2008-10-24T12:20:42.147-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-24T12:20:42.147-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="802.1x" /><category scheme="http://www.blogger.com/atom/ns#" term="security" /><title>Defining security policies for wireless networks</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Security of wireless networks is certainly important. I’ve recently posted an updated tutorial that gives an overview of wireless network security policies that you should take into consideration when deploying and managing a wireless network. You can view the tutorial at the following URL: &lt;a href="http://www.wireless-nets.com/resources/tutorials/define_wireless_security_policies.html"&gt;http://www.wireless-nets.com/resources/tutorials/define_wireless_security_policies.html&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-5462583893159998832?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/l2kwb8pb1Mk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/5462583893159998832/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=5462583893159998832" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/5462583893159998832?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/5462583893159998832?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/l2kwb8pb1Mk/defining-security-policies-for-wireless.html" title="Defining security policies for wireless networks" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/10/defining-security-policies-for-wireless.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUIEQXo6fSp7ImA9WxRQFUs.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-7673233570134440142</id><published>2008-10-09T10:45:00.000-04:00</published><updated>2008-10-09T10:45:00.415-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-09T10:45:00.415-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="client devices" /><title>Choosing the right mobile user device</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The selection of the right mobile devices significantly impacts the usability of the application and the corresponding ROI. You need to think about application requirements and choose devices having the optimum weight, keypad, screen, battery longevity, and ruggedness. User devices in warehouses, for example, will probably undergo more physical abuse than one in use in a typical office setting. Thus, in this scenario, you’d need rugged user devices that will withstand an industrial environment. Before rolling out hundreds of mobile devices to users, undergo testing of pilot sites with a reprehensive group of users. That way, you’ll be sure that the device you propose to use will best fit requirements and maximize ROI. Also, involve upper management in the trials to receive adequate levels of buy-in, which of course is sometimes necessary to continue funding for the project.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-7673233570134440142?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/P_RA1Im6thk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/7673233570134440142/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=7673233570134440142" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7673233570134440142?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7673233570134440142?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/P_RA1Im6thk/choosing-right-mobile-user-device.html" title="Choosing the right mobile user device" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/10/choosing-right-mobile-user-device.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUcAQX88eip7ImA9WxRQE0U.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-9125791663976777655</id><published>2008-10-07T09:44:00.000-04:00</published><updated>2008-10-07T09:44:00.172-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-07T09:44:00.172-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="software" /><title>Tips for developing wireless software</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Whether you’re starting from scratch with a wireless mobile application development project or converting an off-line application to operate in the wireless world, keep the following points in mind:&lt;br /&gt;1. Always consider what will happen if wireless connectivity is lost, and have appropriate recovery mechanisms in place.&lt;br /&gt;2. Look at your application from the viewpoint of a hacker, and design-in security elements, such as encryption and authentication, that significantly reduces or eliminates the security threat.&lt;br /&gt;3. Minimize the transmission of data and overhead packets in order to increase battery longevity.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-9125791663976777655?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/e3akgLNGR7g" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/9125791663976777655/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=9125791663976777655" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/9125791663976777655?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/9125791663976777655?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/e3akgLNGR7g/tips-for-developing-wireless-software.html" title="Tips for developing wireless software" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/10/tips-for-developing-wireless-software.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkEASH84fip7ImA9WxRRGUg.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-1301349296974036494</id><published>2008-10-02T10:43:00.001-04:00</published><updated>2008-10-02T10:44:09.136-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-02T10:44:09.136-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="issues" /><title>Wireless nay sayers</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;In past wireless LAN deployments, I've encountered some people in companies who are totally against the implementation of mobile wireless solutions. The trouble is that these "nay sayers" can cause other users to become negative regarding the implementation. This often deteriorates the benefits of the system. As a result, I highly recommend, early in the deployment project, to promptly handle those against the deployment. One counter measure is to try including these people in the early phases of the project, such as when defining requirements and when considering design alternatives. If they're left out of the deployment process, negative feelings will intensify.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-1301349296974036494?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/lsLaOD2bqJg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/1301349296974036494/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=1301349296974036494" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/1301349296974036494?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/1301349296974036494?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/lsLaOD2bqJg/wireless-nay-sayers.html" title="Wireless nay sayers" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/10/wireless-nay-sayers.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ak8ESXw9eCp7ImA9WxRRGUg.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-6462657019395792252</id><published>2008-09-30T10:41:00.001-04:00</published><updated>2008-10-02T10:46:48.260-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-02T10:46:48.260-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="troubleshooting" /><category scheme="http://www.blogger.com/atom/ns#" term="firmware" /><category scheme="http://www.blogger.com/atom/ns#" term="security" /><title>Keep firmware up-to-date</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I've been seeing a lot of companies with access point firmware that's not up-to-date. This means that these companies are not taking advantages of security and performance patches offered by the vendor. Take a look at your firmware and download updates as needed. Be certain to read over the vendor's notes, however, to ensure that installing the new firmware will not introduce any known issues that will adversely impact your network.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-6462657019395792252?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/Q1CuQjxZZ2g" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/6462657019395792252/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=6462657019395792252" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/6462657019395792252?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/6462657019395792252?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/Q1CuQjxZZ2g/keep-firmware-up-to-date.html" title="Keep firmware up-to-date" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/09/keep-firmware-up-to-date.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkMMR3c4eCp7ImA9WxRRGUg.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-3696280946170018542</id><published>2008-09-25T10:39:00.001-04:00</published><updated>2008-10-02T10:41:26.930-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-02T10:41:26.930-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="troubleshooting" /><category scheme="http://www.blogger.com/atom/ns#" term="WireShark" /><title>Use WireShark instead of Ethereal</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Many of you may be still using Ethereal for obtaining packet traces of Wi-Fi networks. About a year or so ago, Gerald Combs, Ethereal's lead developer, left his company and couldn’t keep the name "Ethereal." As a result, Gerald renamed the software "WireShark" and has been supporting WireShark since then. Instead of using Ethereal, which I don't believe is being supported anymore, I recommend downloading the latest version of WireShark at &lt;a href="http://www.wireshark.org/"&gt;www.wireshark.org&lt;/a&gt;. WireShark is still free and provides the same (and better) functionality as Ethereal.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-3696280946170018542?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/jIR3btTRzYw" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/3696280946170018542/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=3696280946170018542" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/3696280946170018542?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/3696280946170018542?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/jIR3btTRzYw/use-wireshark-instead-of-ethereal.html" title="Use WireShark instead of Ethereal" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/09/use-wireshark-instead-of-ethereal.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0YCQXs-fyp7ImA9WxRREUQ.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-7352725363725982891</id><published>2008-09-23T15:46:00.002-04:00</published><updated>2008-09-23T15:46:00.557-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-09-23T15:46:00.557-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="security" /><title>Watch your back!</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;You can implement the most effective encryption and authentication in the World, but someone can easily look over your shoulder and read your emails along with you. Airports are fairly open, making it easy for a hacker to also see your passwords as you type them in. So, keep this in mind as you utilize public Wi-Fi hotspots.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-7352725363725982891?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/3Ipzynax7rg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/7352725363725982891/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=7352725363725982891" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7352725363725982891?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7352725363725982891?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/3Ipzynax7rg/watch-your-back.html" title="Watch your back!" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/09/watch-your-back.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUYEQXo9fyp7ImA9WxRSF0s.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-498448644819432400</id><published>2008-09-18T15:45:00.001-04:00</published><updated>2008-09-18T15:45:00.467-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-09-18T15:45:00.467-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="security" /><title>Wipe those mobile devices</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;I've found that more and more companies are beginning to deploy device wipe functions to ensure that wireless hand held devices are secure in case they are lost or stolen. For example, an employee who's lost their device can inform a system administrator that the device is gone, and the administrator can issue a command to the device to wipe the memory and applications from the device. In case the device is out of range of the wireless network, functions on the device itself will automatically perform the wiping if someone mistakenly enters the wrong user name / password too many times. I don't believe that Windows natively supports the wiping functions, but I think that it's under development. Regardless, the device wiping seems to be a good security mechanism. Just be sure to do a good job of replicating data on a server!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-498448644819432400?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/4SsfNOc-G00" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/498448644819432400/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=498448644819432400" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/498448644819432400?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/498448644819432400?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/4SsfNOc-G00/wipe-those-mobile-devices.html" title="Wipe those mobile devices" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/09/wipe-those-mobile-devices.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkYMQXc8fCp7ImA9WxRSFUQ.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-5962469234914696456</id><published>2008-09-16T15:43:00.001-04:00</published><updated>2008-09-16T15:43:00.974-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-09-16T15:43:00.974-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="mounting assets" /><category scheme="http://www.blogger.com/atom/ns#" term="range extension" /><category scheme="http://www.blogger.com/atom/ns#" term="signal coverage" /><category scheme="http://www.blogger.com/atom/ns#" term="attenuation" /><category scheme="http://www.blogger.com/atom/ns#" term="site survey" /><category scheme="http://www.blogger.com/atom/ns#" term="issues" /><title>Elevation makes a difference</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;I've found that many Wi-Fi hotspots in outdoor areas have very poor signal strength because the access point antennas are mounted relatively low to the ground, such as near the edge of roofs. The antennas propagate radio waves that must slice through people, buildings, and other obstacles to reach the users. Because of the resulting attenuation, it's generally better to install the access points (or just the antennas) higher up on light poles if they are available. The problem, however, is that it's difficult to run cabling to these higher mounting places. That’s when mesh network technology comes in handy.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-5962469234914696456?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/1BR5gDfwqhQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/5962469234914696456/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=5962469234914696456" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/5962469234914696456?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/5962469234914696456?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/1BR5gDfwqhQ/elevation-makes-difference.html" title="Elevation makes a difference" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/09/elevation-makes-difference.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEcCQXk5fyp7ImA9WxRSEUs.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-3296659102244609240</id><published>2008-09-11T15:41:00.001-04:00</published><updated>2008-09-11T15:41:00.727-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-09-11T15:41:00.727-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="interference" /><category scheme="http://www.blogger.com/atom/ns#" term="troubleshooting" /><category scheme="http://www.blogger.com/atom/ns#" term="access point" /><category scheme="http://www.blogger.com/atom/ns#" term="issues" /><title>Inter-access point interference sometimes not a problem</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The common design rule for installing 802.11b/g access points is to set adjacent ones to non-overlapping channels (1, 6, and 11). This avoids the access points from competing for the same part of the spectrum, such as when transmitting beacons, data frames, and acknowledgements. When analyzing existing wireless LANs, however, I often find adjacent access points set to the same channel. In addition, it's common to have neighboring wireless LANs set to the same channels as yours. For example, a quick scan of my residential area shows several homes having access points all set to channel 6, the typical vendor default channel.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;I've been analyzing various wireless LAN issues recently and ran some throughput tests between a wireless client and a particular access point - with and without the presence of another nearby ("interfering") access point set to the same channel. In fact, I measured degradation of a few percent in throughput when the interfering access point was active as compared to when it was not. This indicates that there's not much impact from the beacons of a neighboring access point set to the same channel. The problem, however, is when multiple clients are utilizing the interfering access point. That can take away a large portion of the bandwidth on your network.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-3296659102244609240?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/WnUBNnPXb-0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/3296659102244609240/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=3296659102244609240" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/3296659102244609240?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/3296659102244609240?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/WnUBNnPXb-0/inter-access-point-interference.html" title="Inter-access point interference sometimes not a problem" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/09/inter-access-point-interference.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0YAQXw5cSp7ImA9WxRTGUU.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-7066997437564340404</id><published>2008-09-09T15:39:00.004-04:00</published><updated>2008-09-09T15:39:00.229-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-09-09T15:39:00.229-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="802.11n" /><category scheme="http://www.blogger.com/atom/ns#" term="newsletter" /><title>Wireless Network Implementation Guide</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I just started a newsletter titled the Wireless Network Implementation Guide. I focus each edition of the newsletter on a particular aspect of wireless networking. For example, the August edition of the newsletter discusses migration to 802.11n networks in enterprises. You can view past editions of the newsletter and subscribe to receive future editions at the following link: &lt;a href="http://www.wireless-nets.com/resources/newsletter.html"&gt;http://www.wireless-nets.com/resources/newsletter.html&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-7066997437564340404?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/agmWGX1-rRg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/7066997437564340404/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=7066997437564340404" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7066997437564340404?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7066997437564340404?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/agmWGX1-rRg/wireless-network-implementation-guide.html" title="Wireless Network Implementation Guide" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/09/wireless-network-implementation-guide.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU8HQHg6fSp7ImA9WxRTGU0.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-7510756027379120818</id><published>2008-09-04T15:38:00.001-04:00</published><updated>2008-09-08T15:57:11.615-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-09-08T15:57:11.615-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="robots" /><category scheme="http://www.blogger.com/atom/ns#" term="applications" /><title>Wi-Fi robots on the run</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;As part of some research I'm doing, I came across a website (&lt;a href="http://www.drrobot.com/"&gt;Dr. Robot&lt;/a&gt;) advertising Wi-Fi robots. You can develop some pretty interesting systems with these devices. I've seen rather extensive use of Wi-Fi for robot communications in hospitals, but you have to ensure good coverage, or the robot gets lost!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-7510756027379120818?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/BdOZRRm7GrM" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/7510756027379120818/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=7510756027379120818" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7510756027379120818?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/7510756027379120818?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/BdOZRRm7GrM/wi-fi-robots-on-run.html" title="Wi-Fi robots on the run" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/09/wi-fi-robots-on-run.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8EQ3w-fCp7ImA9WxRTE0g.&quot;"><id>tag:blogger.com,1999:blog-7248544574159306544.post-3631041123234303294</id><published>2008-09-02T08:00:00.001-04:00</published><updated>2008-09-02T08:00:02.254-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-09-02T08:00:02.254-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="requirements" /><title>Defining requirements for wireless networking critical</title><content type="html">By Jim Geier, &lt;a href="http://www.wireless-nets.com/"&gt;Wireless-Nets, Ltd.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Before implementing a wireless network, you must define requirements to ensure what you’re deploying is based on the right things. Understand what constitutes valid requirements and learn about requirements that you might have overlooked by reading my &lt;a href="http://www.wireless-nets.com/resources/tutorials/define_network_requirements.html"&gt;latest tutorial&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7248544574159306544-3631041123234303294?l=wireless-nets.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/WirelessNetworkImplementationTips/~4/7HpSr6x3eZc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://wireless-nets.blogspot.com/feeds/3631041123234303294/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=7248544574159306544&amp;postID=3631041123234303294" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/3631041123234303294?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7248544574159306544/posts/default/3631041123234303294?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/WirelessNetworkImplementationTips/~3/7HpSr6x3eZc/defining-requirements-for-wireless.html" title="Defining requirements for wireless networking critical" /><author><name>Wireless-Nets' Blog</name><uri>http://www.blogger.com/profile/00920436985754263305</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://wireless-nets.blogspot.com/2008/09/defining-requirements-for-wireless.html</feedburner:origLink></entry></feed>

