[Olsr-dev] Olsr-dev Digest, Vol 28, Issue 11

[(spam-protected)]

Mitar... It Looks very interesting image generator as shown
(http://nodes.wlan-lj.net/)
We also have the same idea to setup the nodes with free community.

Are you using the free open source code for the web page image generator
or this is your own legacy development??
If this is open source Can you please share it (the setup details and
source) with the OLSR community so that all can also make the community
setup to test OLSR....:)

-----Original Message-----
From: (spam-protected)
[mailto:(spam-protected)] On Behalf Of
(spam-protected)
Sent: Sunday, September 13, 2009 3:30 PM
To: (spam-protected)
Subject: Olsr-dev Digest, Vol 28, Issue 11

Send Olsr-dev mailing list submissions to
	(spam-protected)

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.olsr.org/mailman/listinfo/olsr-dev
or, via email, send a message with subject or body 'help' to
	(spam-protected)

You can reach the person managing the list at
	(spam-protected)

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Olsr-dev digest..."


Today's Topics:

   1. Re: LinkQualityMult problems in 0.5.6-r5 (Mitar)
   2. Re: LinkQualityMult problems in 0.5.6-r5 (Henning Rogge)
   3. Re: LinkQualityMult problems in 0.5.6-r5 (Mitar)
   4. Re: LinkQualityMult problems in 0.5.6-r5 (Henning Rogge)


----------------------------------------------------------------------

Message: 1
Date: Sun, 13 Sep 2009 10:03:01 +0200
From: Mitar <(spam-protected)>
Subject: Re: [Olsr-dev] LinkQualityMult problems in 0.5.6-r5
To: Henning Rogge <(spam-protected)>
Cc: (spam-protected)
Message-ID:
	<(spam-protected)>
Content-Type: text/plain; charset=UTF-8

Hi!

> We have a working patch that every node only has one "routable" IP, so

> you can (most times) just use IPv6 linklocal IPs for your interfaces. 
> The only IPs propagated beyond your neighborhood will be your "global"

> IP and your attached networks (HNAs).

And how stable is this patch? Would you recommend using it for a
deployment? Where can we get it?

For IPv4 we could probably use IPv4 link-local 169.254.0.0/16 range?


Mitar



------------------------------

Message: 2
Date: Sun, 13 Sep 2009 10:25:37 +0200
From: Henning Rogge <(spam-protected)>
Subject: Re: [Olsr-dev] LinkQualityMult problems in 0.5.6-r5
To: Mitar <(spam-protected)>
Cc: (spam-protected)
Message-ID: <(spam-protected)>
Content-Type: text/plain; charset="utf-8"

Am Sonntag 13 September 2009 10:03:01 schrieb Mitar:
> Hi!
> 
> > We have a working patch that every node only has one "routable" IP, 
> > so you can (most times) just use IPv6 linklocal IPs for your 
> > interfaces. The only IPs propagated beyond your neighborhood will be

> > your "global" IP and your attached networks (HNAs).
> 
> And how stable is this patch?
I think it's pretty stable Markus Kittenberg has used it for months in
the Vienna Funkfeuer network for his overlay testing network.

> Would you recommend using it for a deployment?
I think it's ready for deployment, especially if you want to built a new
network. All nodes should have the sourceip mode active.

If you want to do a deployment with it we would be glad to support you.
What kind of deployment do you have in mind ?

> Where can we get it?
It's already in the 0.5.6 tip. In the file src/olsr_cfg.h you have to
set #define SOURCE_IP_ROUTES 1 in line 49. That's all.
 
The next stable OLSRd will have it as a config parameter setting.

> For IPv4 we could probably use IPv4 link-local 169.254.0.0/16 range?
Yes, just make sure that you don't have the same interface IP within
two-hop range.

Henning Rogge
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url :
http://lists.olsr.org/pipermail/olsr-dev/attachments/20090913/16018268/a
ttachment-0001.pgp 

------------------------------

Message: 3
Date: Sun, 13 Sep 2009 10:59:52 +0200
From: Mitar <(spam-protected)>
Subject: Re: [Olsr-dev] LinkQualityMult problems in 0.5.6-r5
To: Henning Rogge <(spam-protected)>
Cc: (spam-protected)
Message-ID:
	<(spam-protected)>
Content-Type: text/plain; charset=UTF-8

Hi!

On Sun, Sep 13, 2009 at 10:25 AM, Henning Rogge <(spam-protected)>
wrote:
> If you want to do a deployment with it we would be glad to support 
> you. What kind of deployment do you have in mind ?

We are putting up a community WiFi network in Ljubljana, Slovenia. We
have been testing and developing it for some time now and now we are
getting ready for some larger deployment. So we are stabilizing codebase
and testing last unknowns.

You can check our network monitor and status here:

http://nodes.wlan-lj.net/

We have a web based firmware image generator so every user can get a
preconfigured image tailored for a particular node and also all nodes
status data is being collected centrally so users can monitor their
multiple nodes through this web page.

We use VPN to this central server for redundancy and easier deployment
on locations where there are no neighboring nodes (yet). And so many of
our nodes have WiFi and VPN interface.

But I have done some testing and I think that in our setup having the
same IP on multiple interfaces is not a problem because they are
interfaces of different physical mediums which are separated by their
nature and we just have to keep them separate. Because we do not bridge
all connections on a VPN server (but run OLSR there) nodes cannot
directly see each other at the same time over VPN server and WiFi. So LQ
calculations stay correct.

So we just have to take care not to bridge anything, don't we?

I understand that things would break if we would have for example a node
with two radios which would use same IP address. Then OLSR would not be
able to differ which LQ belongs to which radio it this node would see
some other node with both radios. (But even here you could take care
with using separate channels but it would get more complicated than in
our case of WiFi/VPN separation.)

>> For IPv4 we could probably use IPv4 link-local 169.254.0.0/16 range?
> Yes, just make sure that you don't have the same interface IP within 
> two-hop range.

That will not be a problem as we can give/allocate nodes unique
link-local IP addresses the same as we are giving/allocate nodes
"global" IP addresses.

But how will this show up in OLSR topology? Will those link-local IP
addresses be seen? Or will just "global" IP addresses will be used from
a viewpoint of a network?


Mitar



------------------------------

Message: 4
Date: Sun, 13 Sep 2009 11:17:20 +0200
From: Henning Rogge <(spam-protected)>
Subject: Re: [Olsr-dev] LinkQualityMult problems in 0.5.6-r5
To: Mitar <(spam-protected)>
Cc: (spam-protected)
Message-ID: <(spam-protected)>
Content-Type: text/plain; charset="utf-8"

Am Sonntag 13 September 2009 10:59:52 schrieb Mitar:
> > If you want to do a deployment with it we would be glad to support
you.
> > What kind of deployment do you have in mind ?
> 
> We are putting up a community WiFi network in Ljubljana, Slovenia. We 
> have been testing and developing it for some time now and now we are 
> getting ready for some larger deployment. So we are stabilizing 
> codebase and testing last unknowns.
> 
> You can check our network monitor and status here:
> 
> http://nodes.wlan-lj.net/
> 
> We have a web based firmware image generator so every user can get a 
> preconfigured image tailored for a particular node and also all nodes 
> status data is being collected centrally so users can monitor their 
> multiple nodes through this web page.
Wow, that looks nice. :)
I think that's the first time I see such a image generator.

> We use VPN to this central server for redundancy and easier deployment

> on locations where there are no neighboring nodes (yet). And so many 
> of our nodes have WiFi and VPN interface.
okay. :)
 
> But I have done some testing and I think that in our setup having the 
> same IP on multiple interfaces is not a problem because they are 
> interfaces of different physical mediums which are separated by their 
> nature and we just have to keep them separate. Because we do not 
> bridge all connections on a VPN server (but run OLSR there) nodes 
> cannot directly see each other at the same time over VPN server and 
> WiFi. So LQ calculations stay correct.
> 
> So we just have to take care not to bridge anything, don't we?
Arg... I just remember some shortcomings of the current patch. Hope I
did not promise too much to you.

The current patch is a step towards a "linklocal-interface" OLSR
network, but I remember (now) there were some problems why we did not
made the full step in 0.5.6. If you deploy the patch in a mixed setup
(some with sourceip, some without them), you cannot kill the MID
messages because this will break legacy support. If you have a pure
sourceip-patch, you could (I think) just set the TTL of the MIDs to 2,
that would be enough.

At the moment the patch is just a modification in the set-route code to
force linux to use the originator-IP for outgoing IP-packages. This
allows you to run multiple OLSR networks on the same interfaces
side-by-side.

(I have set Markus Kittenberg as CC, because he has written the
source-ip patch and can tell you more about it).

Henning Rogge
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url :
http://lists.olsr.org/pipermail/olsr-dev/attachments/20090913/582de6db/a
ttachment-0001.pgp 

------------------------------

--
Olsr-dev mailing list
(spam-protected)
http://lists.olsr.org/mailman/listinfo/olsr-dev

End of Olsr-dev Digest, Vol 28, Issue 11
****************************************

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com