[Commotion-dev] olsrd plugin config for GNU/Linux and Mac OS X

[Teco Boot]

The dyn_gw plugin is for Internet border routers. Limitation for Android/Linux looks OK to me. Or would iMac/macBook act as gateway? (run Linux in virtual box…)

The (extended) SmartGateway is far more important. 0.6.6 can set up multiple tunnels, where for new connections the best gateway is pinpointed. Moving nodes keep the selected gateway for existing connections. Does ipip tunnels work on OSX? (hmm, typing on Macbook, few meters from my Linux olsrd gateway _with WiFi AP_, no time to verify...).

We have built the PUD plugin for position update distribution. It distributes dynamic (GPS) positions and ID (type&ID) field in compact messages. DNS names is one of the supported ID types. An extended version could update name server resolve cache.

On p2pd, I use the lo interface for forwarding local host multicast/broadcast packages. Tested on Android only, with BMF. It should work on p2pd and mdns also.

On dynamic config: when I need such, I usually use a start script that copies template to a /var/run (or whatever rw folder) and update it as needed before starting the daemon. 

Teco

Op 19 feb. 2013, om 17:32 heeft Hans-Christoph Steiner <hans at guardianproject.info> het volgende geschreven:

> 
> For the Mac OS X and GNU/Linux clients, I'm wondering how the olsrd.conf
> should be configured for the default commotionwireless.net profile.  dyn_gw
> only works on the Linux kernel, so that's out on Mac OS X.  arprefresh,
> nameservice, and p2pd seem to only be built on GNU/Linux and Android, so I
> guess they also only work with the Linux kernel.
> 
> For GNU/Linux, there is then the question of how to configure nameservice and
> p2pd.  It looks like 'name' should be unique per-host:
> 
> LoadPlugin "olsrd_nameservice.so.0.3"
> {
>        PlParam "name" "commotion-7814921"
>        PlParam "sighup-pid-file" "/var/run/dnsmasq.pid"
>        PlParam "suffix" ".mesh"
> }
> 
> And with p2pd, it looks like NonOlsrIf needs to be updated based on the
> interface names of the machine that it is currently running on.  Is there a
> way to handle that in the olsrd.conf?  Otherwise I guess that the conf file
> will have to be rewritten based on the network devices on the installed machine.
> 
> LoadPlugin "olsrd_p2pd.so.0.1.0"
> {
>        PlParam "NonOlsrIf" "eth0"
>        PlParam "P2pdTtl" "5"
>        PlParam "UdpDestPort" "224.0.0.251 5353"
> }
> 
> .hc
> 
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-dev
>