[Babel-users] breaking the ath9k in adhoc mode with the new fq_codel implementation

[Dave Taht]

ok, so I got a bee in my bonnet and nuked the IFF_RUNNING check from
babeld for rpi2 when talking to the usb stick in ad-hoc mode.

SUCCESS!

I had to manually add a fe80::4/64 address also.

for future reference the stick that I just got to work was this one:

http://www.amazon.com/Panda-300Mbps-Wireless-USB-Adapter/dp/B00EQT0YK2?ie=UTF8&psc=1&redirect=true&ref_=oh_aui_detailpage_o04_s00

usb device type is:

Bus 001 Device 004: ID 148f:5372 Ralink Technology, Corp. RT5372
Wireless Adapter

in the face of multiple driver writers missing the subtleties of
IFF_RUNNING, what to do?

...
it did not fix my ath9k (no tx but that's probably my problem)
...
it did not fix another stick I tried

Bus 001 Device 005: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un
802.11n Wireless Adapter [Realtek RTL8188CUS]