Summary: Hey what’s up everyone. In today’s episode we talk about TP-Link discovering what it’s like to ignore DFS, Google Fiber going Wireless?, Data frame slicing with Airtool, and CWAP exam gets updated and so does the study guide.<br> TP-Link Settles $200k with FCC for ignoring DFS and power limits<br> FCC reaches <a href="https://build.slashdot.org/story/16/08/01/1855206/fcc-requires-tp-link-to-support-open-source-router-firmware" target="_blank" rel="nofollow">settlement</a> of $200k with TP-Link for selling Wifi routers that ignore DFS requirements and power limits. This sounds very careless for a networking company. Is this what we accept now as hardware from these companies. Maybe TP-Link thought they could get away from it, or maybe an engineer wasn’t aware of the FCC regulations. But is this what we expect with inexpensive hardware? I don’t think so. Along with the fine, TP-Link has agreed to work with the open-source community to allow consumers to install third-party firmware on TP-Link routers.<br> This is a good move in my opinion but unprecedented from the FCC. This is a great way to move our wireless industry into embracing open-source.<br> Google Plans to Extend Fiber Into Wireless<br> CFO, Ruth Porat, said that Google Fiber would be <a href="http://buff.ly/2akvFoQ" target="_blank">exploring wireless</a> due to the acquisition of Webpass. This was mentioned in Alphabet’s 2nd quarter earnings call. Why in the world would Google Fiber go into wireless? The main obvious reason I can think of is cost. It’s <a href="http://www.bloomberg.com/news/articles/2016-07-28/google-plots-cheaper-wireless-future-to-expand-fiber-project" target="_blank">much cheaper</a> to use hardware that costs a fraction of the cost of digging up fiber. Not to mention the labor costs of doing the work.<br> I think this is an interesting turn of events as Google Fiber now becomes fiber over the air. I can see the marketing lingo now….<br> Latest Airtool Update Gives Us Data Frame Slicing<br> Airtool is one of my favorite apps on OSX. It allows me to capture wireless frames using my built-in wireless adapter. But in doing so, some of these captures can take up precious hard disk space.<br> What Adrian Granados has done is enabled a feature to just grab the beginning of the frame and discarding the rest. What you have left is the 802.11 MAC headers.<br> Check out the <a href="https://www.adriangranados.com/blog/frame-slicing" target="_blank">latest update</a>.<br> CWAP-402 Exam Released<br> The latest update to CWAP from CWNP is <a href="https://www.cwnp.com/certifications/cwap" target="_blank">CWAP-402</a>. It is 90 minutes and contains 60 questions. It is available now to test and has been available since June 28 2016.<br> <br> CWAP-402 brings changes to 5 subject areas.<br> Tom Carpenter has hinted that Troubleshooting is a big part of the exam from the CWAP update webinar.<br> These are the objectives.<br> 5% – Troubleshooting Processes<br> 25% – 802.11 Communications<br> 15% – WLAN hardware<br> 35% – Protocol and Spectrum Analysis<br> 20% – Troubleshooting Common Problems<br> Troubleshooting processes is a very small chunk of the exam at 5%.<br> Focuses on a troubleshooting methodology. Mentions of industry and vendor recommended processes. Not sure how vendor neutral this sounds.<br> But with any troubleshooting process, OSI Model is mentioned. Just remember that Wireless is at the Data Link and Physical Layer.<br> May mention of Wireshark and Omnipeek as well as the tools baked into OS such as command line using ping and traceroute.<br> At 25% is 802.11 Communications.<br> This sounds like the MAC Layer Frame Formats and Technologies AND 802.11 Operation and Frame Exchanges from the previous exam. Looking at 802.11 communications from a troubleshooting perspective. Understand the frame exchanges when a device tries to join a BSS....
