On Fri, Aug 31, 2012 at 12:23:11AM -0400, anarcat wrote:
On 2012-08-10, Juliusz Chroboczek wrote:
Yep, although that's not really meant for human consumption -- it's the
interface BabelDraw[1] and BabelWeb[2] listen on. I suppose it could be
extended for the kind of applications you
Well, for one thing it would be more reliable to have a unix socket
instead of a network port.
A Unix socket cannot easily be tunnelled using ssh or socat.
Also, the output is not easy to parse as it is right now. First off,
there is no delimitation that allows us to see when a listing is
Dear all
I play with babel 1.3.1-1 on debian.
I put babeld on some computers, and also in lxc containers.
two computers have both wired and wifi link.
I add on /etc/babeld.conf:
redistribute proto 3 allow
redistribute proto 11 allow
I modify /etc/sysctl.conf to enable ip forwarding on all
On Fri, Aug 31, 2012 at 8:14 AM, Antoine Beaupré anar...@anarcat.ath.cx wrote:
On 2012-08-31, Juliusz Chroboczek wrote:
Second, the fields display is inconsistent. The chan (255) field, for
example, is sometimes there, sometimes not...
The format is extensible, and in principle all fields
4 matches
Mail list logo
