[Olsr-users] Configuration of an ad-hoc mesh networks

[Henning Rogge]

"weight" is the outgoing cost of the link (numeric)... "weight_txt" is
the text representation of the same.

"in" is the incoming cost of the link, "in_txt" its text representation.

"outgoing_tree : true" means the link is part of a route from the
local router to a destination.

Henning

On Tue, Oct 13, 2015 at 3:07 PM, Charles Lesire-Cabaniols
<(spam-protected)> wrote:
> Actually it's working :p
> I was calling netjsoninfo on the telnet console instead of "netjsoninfo
> graph"
>
> On the link attribute, I have the following:
> "links":
> [{"source":"169.254.244.81","target":"169.254.244.82","weight":37,"properties":
> {"weight_txt":"55.351 Mbit/s","in":37,"in_txt":"55.351
> Mbit/s","outgoing_tree":"false"}},{"source":"169.254.244.82","target":"169.254.244.81","weight":37,"properties":
> {"weight_txt":"55.351 Mbit/s","in":37,"in_txt":"55.351
> Mbit/s","outgoing_tree":"false"}}]
>
> What does weight, in, weight_txt and in_txt represent?
>
> 2015-10-13 14:14 GMT+02:00 Charles Lesire-Cabaniols
> <(spam-protected)>:
>>
>> Here is my current configuration: both RaspPI have Ubuntu 14.04 LTS with
>> oonf compiled from git master. They are both connected on eth0 to my office
>> network (so that I can ssh to them), and I try to connect them together
>> using wlan0.
>>
>> On RaspPI 1 :
>> # The loopback network interface
>> auto lo
>> iface lo inet loopback
>>
>> # The primary network interface
>> auto eth0
>> iface eth0 inet static
>>   address 134.212.244.81
>>   netmask 255.255.0.0
>>   gateway 134.212.90.100
>>   dns-nameservers 134.212.90.3 134.212.90.6
>>
>> # WLAN
>> auto wlan0
>> iface wlan0 inet static
>>   wireless-mode ad-hoc
>>   wireless-essid MAMBO
>>   address 169.254.244.81
>>   netmask 255.255.0.0
>>
>> On RaspPI 2 : idem with 82 instead of 81 at end of IP addresses
>>
>> On RaspPI 1:
>> $ iwconfig wlan0
>> wlan0     IEEE 802.11bgn  ESSID:"MAMBO"
>>           Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: BE:F9:B2:61:7E:59
>>           Tx-Power=20 dBm
>>           Retry short limit:7   RTS thr:off   Fragment thr:off
>>           Power Management:off
>> $ ifconfig wlan0
>> wlan0     Link encap:Ethernet  HWaddr f8:1a:67:23:f7:14
>>           inet addr:169.254.244.81  Bcast:169.254.255.255
>> Mask:255.255.0.0
>>           inet6 addr: fe80::fa1a:67ff:fe23:f714/64 Scope:Link
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:1196 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:1180 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:480375 (480.3 KB)  TX bytes:499834 (499.8 KB)
>>
>> On RaspPI 2:
>> $ iwconfig wlan0
>> wlan0     IEEE 802.11bgn  ESSID:"MAMBO"
>>           Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: BE:F9:B2:61:7E:59
>>           Tx-Power=20 dBm
>>           Retry short limit:7   RTS thr:off   Fragment thr:off
>>           Power Management:off
>> $ ifconfig wlan0
>> wlan0     Link encap:Ethernet  HWaddr a0:f3:c1:2f:dd:ad
>>           inet addr:169.254.244.82  Bcast:169.254.255.255
>> Mask:255.255.0.0
>>           inet6 addr: fe80::a2f3:c1ff:fe2f:ddad/64 Scope:Link
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:1241 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:1264 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:533113 (533.1 KB)  TX bytes:561624 (561.6 KB)
>>
>> Both can ping using their 169.254.244.{81,82} addresses.
>>
>> Then I have launched on both './oslrd2_static wlan0'.
>>
>> I don't know how to test except using the telnet interface and calling
>> some OONF functions.
>> netjsoninfo returns an empty graph...
>>
>> 2015-10-13 10:30 GMT+02:00 Henning Rogge <(spam-protected)>:
>>>
>>> On Tue, Oct 13, 2015 at 10:22 AM, Charles Lesire-Cabaniols
>>> <(spam-protected)> wrote:
>>> > Ok, thanks for the answer... but you're talking to a newb, so please be
>>> > more
>>> > precise ;).
>>> > Here are my questions:
>>> >
>>> > 2015-10-12 19:05 GMT+02:00 Henning Rogge <(spam-protected)>:
>>> >>
>>> >> On Mon, Oct 12, 2015 at 1:36 PM, Charles Lesire-Cabaniols
>>> >> <(spam-protected)> wrote:
>>> >> > Question: Looks like setting up the IP is not necessary with olsrd2
>>> >> > (according to the doc), but without I could ping my nodes; what is
>>> >> > the
>>> >> > good
>>> >> > configuration to set?
>>> >>
>>> >> If you want to run your interfaces with linklocal addresses, olsrd2
>>> >> (in dualstack mode with IPv6) can do this for you.
>>> >>
>>> >> BUT you need at least one routable (not linklocal) address on one
>>> >> interfaced used by olsrd2... in a multi-interface scenario this can be
>>> >> the loopback interface.
>>> >
>>> >
>>> > And so? I tried to set a static address for my loopback in
>>> > network/interfaces, but it is not taken into account.
>>>
>>> have a look at the "typical OLSR deployments" page of our wiki (its
>>> linked in the User FAQ)
>>> http://www.olsr.org/mediawiki/index.php/OLSR_network_deployments
>>>
>>> when you want to use the "loopback" to store your routable IP, you
>>> need to add it to the list of interfaces for olsrd2:
>>>
>>> But this doesn't make much sense with a single Wifi interface...
>>>
>>> just set the routable address of each node to wlan0 for now and start
>>> just with "olsrd2_static wlan0".
>>>
>>> > And when I launch "olsrd2_static wlan0 lo", nothing specific happens in
>>> > "route -n"
>>>
>>> what is your output of "ip addr" ?
>>>
>>> > Ok, I got it... but the netjsoninfo is empty (collectionrs = []) when
>>> > my two
>>> > nodes look connected
>>>
>>> It does not look like your two OLSR instances can see each other.
>>>
>>> Do you had a look at the "Troubleshooting" page of our wiki (also
>>> linked in the User FAQ)?
>>>
>>> http://www.olsr.org/mediawiki/index.php/Troubleshooting
>>>
>>> Henning
>>
>>
>