Get short, timely messages from Trent Cutler.

Twitter is a rich source of instantly updated information. It's easy to stay updated on an incredibly wide variety of topics. Join today and follow @firemywires.

Get updates via SMS by texting follow firemywires to 40404 in the United States
Codes for other countries

Two-way (sending and receiving) short codes:
Country Code For customers of
Australia
  • 0198089488 Telstra
Canada
  • 21212 (any)
United Kingdom
  • 86444 Vodafone, Orange, 3, O2
Indonesia
  • 89887 AXIS, 3, Telkomsel
Ireland
  • 51210 O2
India
  • 53000 Bharti Airtel, Videocon
Jordan
  • 90903 Zain
New Zealand
  • 8987 Vodafone, Telecom NZ
United States
  • 40404 (any)

firemywires

  1. @blong1 As it is in the code at this moment, we will just no longer use CF-Ends for conversation aggregation because they lie. 10:47 AM May 24th via TweetDeck in reply to blong1
  2. @blong1 so even though everyone tells me they are corrupt frames, I can consistently get them with valid FCS and flip-flopped addresses. 10:45 AM May 24th via TweetDeck in reply to blong1
  3. @blong1 CF-End should always come from the AP but what we find is the Tx addr is always the client which should be bssid 10:44 AM May 24th via TweetDeck in reply to blong1
  4. @blong1 We can give the user the ability to filter them out. But we we build our structure of bssids and clients, CF-ends throw it off. 10:43 AM May 24th via TweetDeck in reply to blong1
  5. @blong1 Yeah, those throw Eye P.A. off pretty bad. the FCS is good on all of them and consistent too. So weird. 10:29 AM May 24th via TweetDeck in reply to blong1
  6. Anyone have 5-10 minutes they can spare to talk about CF-end CF-Ack frames? The more I read the more I am confused by what I am seeing. 8:09 AM May 24th via TweetDeck
  7. "RF Interference: When Things Go Bump in the Air" nojitter.com/post/240000795… 8:48 AM May 22nd via Tweet Button
  8. Hey 5 GHz! Wireless headsets are coming and they're taking your channels. twitter.com/firemywires/st… 11:42 AM May 16th via web
  9. @CraigTNichols @TamoSoft I liked the part that told people to hide their big jars of water. 8:17 PM May 15th via TweetDeck in reply to CraigTNichols
  10. @DevinAkin @TamoSoft it happened a lot with the netbooks. But yeah I think he is wrong in this article :P 4:14 PM May 15th via TweetDeck in reply to DevinAkin
  11. @DevinAkin @TamoSoft Actually, the Wi-Spy will show it, however the noise appears at about 2490, which is out of the range of most Wi-Fi. 4:13 PM May 15th via TweetDeck in reply to DevinAkin
  12. 10 Reasons Your Wi-Fi Speed stinks. Includes free tools to use too! lnkd.in/qCfuWD 2:53 PM May 15th via LinkedIn
  13. Here's a great explanation of why the iPhone Wi-Fi wouldn't work well at INTEROP 2012. lnkd.in/5E6kFm 8:03 AM May 14th via LinkedIn
  14. Interesting idea. Sometimes Wi-Fi design could use some intentional attenuation: technologytell.com/hometech/85760… 11:38 AM May 11th via TweetDeck
  15. @wispycanada wow that is awesome! Good for @WLANBook! 7:24 PM May 10th via Twitter for Android in reply to wispycanada
  16. Throughput analysis of the 2.4 ghz at #interop2012 using tamosoft throughput test and eye p.a. cc @metageek twitter.com/firemywires/st… 9:57 AM May 10th via Twitter for Android
  17. Old vegas. Interop 2012 instagr.am/p/KbcVVVPuES/ 7:08 PM May 9th via Instagram
  18. "@TamoSoft: Another TamoGraph 3.0 Beta screen shot illustrating virtual AP properties & antenna configuration. twitter.com/TamoSoft/statu…" awesome 10:09 AM May 4th via Twitter for Android