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
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
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 envision, but you'll want to
coordinate with Gabriel, so that you
babeld -g 33123 ...
telnet ::1 33123
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 envision, but you'll want to
coordinate with Gabriel, so that you don't
Le 10.08.2012 00:38, Antoine Beaupré a écrit :
It would be useful if there was a socket that babeld would listen on
at
least to dump information about the routing table.
babeld -g 33123 ...
telnet ::1 33123
--
Gabriel
___
Babel-users mailing list
6 matches
Mail list logo
