[Babel-users] Fwd: Specify router-id explicitly

[sp2ong at wp.pl]

ifconfig radio port on router neighbour :

mesh0     Link encap:Ethernet  HWaddr CE:C0:48:BC:B8:9F
          inet addr:44.128.100.2  Bcast:255.255.255.255
Mask:255.255.255.255
          inet6 addr: fe80::2c80:6402:2c80:6402/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1532  Metric:1
          RX packets:166 errors:0 dropped:0 overruns:0 frame:0
          TX packets:191 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16379 (15.9 KiB)  TX bytes:22958 (22.4 KiB)

When connect to babeld 'nc :: 33123' show

BABEL 0.0
add self SP2ONG-3.ampr.org id 2c:80:64:03:2c:80:64:03
add neighbour 8cd250 address fe80::2c80:6402:2c80:6402 if mesh0 reach ffff
rxcost 256 txcost 256 cost 256
add xroute 44.128.100.3/32-::/0 prefix 44.128.100.3/32 from ::/0 metric 128
add route 44.128.100.2/32-8cd250-::/0 prefix 44.128.100.2/32 from ::/0
installed yes id 02:0e:8e:ff:fe:23:e9:40 metric 384 refmetric 128 via
fe80::2c80:6402:2c80:6402 if mesh0
done

It maybe useful will be instead:

add neighbour 8cd250 address fe80::2c80:6402:2c80:6402 if mesh0 reach ffff
rxcost 256 txcost 256 cost 256

add ipv4 address neighbour:

add neighbour 8cd250 address fe80::2c80:6402:2c80:6402 44.128.100.2 if
mesh0 reach ffff rxcost 256 txcost 256 cost 256

the address ipv6 fe80::2c80:6402:2c80:6402 is local and generate by system
ipv4 is unique and assign by user but more useful to identifier node






2015-07-11 16:47 GMT+02:00 Juliusz Chroboczek <jch at pps.univ-paris-diderot.fr
>:

> > Ok but how to do table with neighbours where will be more for me and
> > other identifier of node (like name, or better ipv4 address) instead
> > local IPv6 address which is generate by kernel for radio port
>
> Babel is a routing protocol, and it is carefully designed to not carry any
> extraneous information -- just the strict minimum that is needed for
> routing.  Since Babel doesn't need to associate neighbour interfaces to
> nodes, it doesn't.
>
> There are many solutions to what you want to do.  The simplest would
> probably be to have a dedicated protocol that periodically multicasts its
> Babel router-id.
>
> You could also send the router-id as a sub-TLV of Babel's Hello TLV.
> Sub-TLVs 224 through 254 are reserved for non-standard extensions, and the
> place in the code is the function send_hello_noupdate in message.c.
>
> -- Juliusz
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/babel-users/attachments/20150711/2dec8774/attachment.html>