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

[Dave Taht]

So, thank you for exposing a bug in my code today. The new ath9k
fq_codel code at the 802.11 mac layer bypasses the qdisc...


root@dancer:~/Pictures# tc -s qdisc show dev wlp2s0
qdisc noqueue 0: root refcnt 2
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0

and somewhere IFF_RUNNING is no longer being set when iwconfig is in
adhoc mode... so I ended up with the infinit txcost

root@dancer:~/Pictures# ifconfig wlp2s0
wlp2s0Link encap:Ethernet  HWaddr 00:21:63:2f:f2:f4
  inet addr:172.26.17.246  Bcast:255.255.255.255  Mask:255.255.255.255
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:41177 errors:0 dropped:0 overruns:0 frame:0
  TX packets:27218 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:13436569 (13.4 MB)  TX bytes:11838910 (11.8 MB)

root@dancer:~/Pictures# iwconfig wlp2s0
wlp2s0IEEE 802.11abgn  ESSID:"babel"
  Mode:Ad-Hoc  Frequency:2.437 GHz  Cell: 32:DD:4C:C7:F8:87
  Tx-Power=16 dBm
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Encryption key:off
  Power Management:off

and after I unwedge the darn thing out of adhoc and back into sta...
life is much better.

UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

http://www.taht.net/~d/unwedged.png
http://www.taht.net/~d/unwedged_eth0down.png

Checking around, I am seeing no "running" field on the rpi2 which
might explain why it's wifi doesn't work with babel - that's running
the base OS and a "panda" usb stick in adhoc.

I AM seeing the running field on the rpi3, but that has kernel issues...

I can try to sum up everything that broke on every machine, but my
head hurts, and I'm going back to what I was doing in the first place.


Dave Täht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi

___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

Re: [Babel-users] babelweb "time to dump"

[Gabriel Kerneis]

On Mon, Mar 28, 2016, at 19:16, Dave Taht wrote:
> Another useful stat in babel web would be for it to time how long
> it takes to get a dump
> 

It uses the streaming interface, not the dump one. 

-- 
Gabriel

___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

Re: [Babel-users] Control socket language [wass Babel on itty bitty boxes]

[Dave Taht]

On Mon, Mar 28, 2016 at 9:27 AM, Gabriel Kerneis  wrote:
>
>
> On Mon, Mar 28, 2016, at 17:53, Juliusz Chroboczek wrote:
>> > PS: I am loving the new "dump" functionality. Tons easier to read than
>> > a logfile. echo 'dump' | nc ::1 33123.
>>
>> Thanks for the kind words.
>>
>> Folks -- I've had little feedback on the new control socket command
>> language.  If you wish to complain, please try to do it before the third
>> week of April, which is when I plan to release 1.8.0.
>
> What about dumping the configuration options too?

+1

> That would solve the
> question of "was subtrees enabled during this test?" and the like.

heh. yep. I wouldn't mind seeing filters also.

is babelweb using "dump" yet? Seems saner to do a poll/response
on a busy network...

(I'll go pull it. if you can't tell this is the first time I've mucked
with babel in a long while)

>
> --
> Gabriel
>
> ___
> Babel-users mailing list
> Babel-users@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

Re: [Babel-users] Babel on itty bitty boxes

[Dave Taht]

On Mon, Mar 28, 2016 at 8:35 AM, Matthieu Boutier
 wrote:
>> Why don't you write to the netdev list to ask what's a reliable way to
>> detect IPv6_SUBTREES?
>
> Yes, I'm asking myself if the Dave's "invalid argument" are for 
> source-specific routes.  In which case it answers the question.  Will test it.

Yea, a failure to insert these would be a good test for falling back
to non-subtrees.

...

I uploading to: http://www.taht.net/~d/

babeld.dump-ipv6-subtrees-false babeld_2_wlans.log
babled-ipv6-subtrees-false.log

I see the invalid argument go by in the subtrees-false case.

It was a real joy to be able to just compile stuff directly on these
itty bitty boxes, which saved much time vs openwrt. too much time.

I do crazy things so others don't have to.

...

another possible bug is that I would have assumed the bridged ap box
would have detected the bridge and supplied a different metric or
cost.
I think it is (256) according to the logs, so that is right...

The topology there is:

pi3 - AP br-lan  sw10 (fe80::120d:7fff:fe64:c992)
 (cerowrt connecting as a sta rather than adhoc).

Admittedly that connection measures at 80mbits and is probably a great
deal less flaky than the pi is.

IF you are bored and want access to these boxes let me know.

___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

Re: [Babel-users] Babel on itty bitty boxes

[Dave Taht]

On Mon, Mar 28, 2016 at 8:26 AM, Matthieu Boutier
 wrote:
>> I put a babel debug 3 log up at:
>>
>> http://www.taht.net/~d/babeld_pi3.log
>
> Strange, there is no more "kernel_route(ADD): invalid argument" lines.  Is it 
> really the same node, with the same options ?

yes. Perhaps, however, I had earlier had ipv6-subtrees true.

And although I seem to have connectivity over the wifi link now (I did
not on that test), it does not choose it.

>
> So you should have all the right routes in the FIB, no ?

Meh. The source of all my issues was that I volunteered to try out 1.8
on a whole bunch of machines at once that I'd never tried it on. :)
Compiling 1.8 on all of them was easy... tracking down each individual
bug was not.

I kind of expected the local wlan connection also to the other side of
the pi's link to go direct inside of 2 minutes. It's not and damned if
I know why, besides the kernel errors... For example, right now, to
connect the two networks is a babel running on a bridged wifi AP/sta
(not adhoc)/ethernet. Which remains for all routes on the pi, despite
it too having 2 direct links.

I know, one step at a time, but it was just a quick test... I thought
delusion-ally that everything on every platform would "just work" by
now.

>
> Matthieu
>
> PS: sorry for your flash !! ;-)
>

PS: I am loving the new "dump" functionality. Tons easier to read than
a logfile. echo 'dump' | nc ::1 33123.

http://www.taht.net/~d/ has a dump and a much bigger log, with eth0,
wlan1,wlan2 enabled.

___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

Re: [Babel-users] Babel on itty bitty boxes

[Matthieu Boutier]

> Why don't you write to the netdev list to ask what's a reliable way to
> detect IPv6_SUBTREES?

Yes, I'm asking myself if the Dave's "invalid argument" are for source-specific 
routes.  In which case it answers the question.  Will test it.

Matthieu


___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

Re: [Babel-users] Babel on itty bitty boxes

[Matthieu Boutier]

> I put a babel debug 3 log up at:
> 
> http://www.taht.net/~d/babeld_pi3.log

Strange, there is no more "kernel_route(ADD): invalid argument" lines.  Is it 
really the same node, with the same options ?

So you should have all the right routes in the FIB, no ?

Matthieu

PS: sorry for your flash !! ;-)


___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

Re: [Babel-users] Babel on itty bitty boxes

[Juliusz Chroboczek]

> "Autodetection" is just based on the kernel version (via uname).  So
> it's normal it doesn't change anything on c1 (3.10 < 3.11).  And it's
> normal too that you need to use it on c2 (3.14 > 3.11, but compiled
> without IPv6_SUBTREES).

Matthieu,

Why don't you write to the netdev list to ask what's a reliable way to
detect IPv6_SUBTREES?

-- Juliusz



___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

Re: [Babel-users] Babel on itty bitty boxes

[Matthieu Boutier]

> It did not fix the 3.10 kernel based c1.
> 
> So autodetection is broken on the c2 & c1 kernels

"Autodetection" is just based on the kernel version (via uname).  So it's 
normal it doesn't change anything on c1 (3.10 < 3.11).  And it's normal too 
that you need to use it on c2 (3.14 > 3.11, but compiled without IPv6_SUBTREES).

>> Ah ok, so what's in the babel RIB on rpi?
>> (killall -USR1 babeld; cat /var/log/babeld.log)
> 
> Attached. I note that while the pi3 had had ip -6 rules showing, this
> log dump is after a fresh restart

Very interesting.  Could you make that again, this time with "debug 3"?

Matthieu


___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users