headers
ZioPRoTo (Saverio Proto | 4 Sep 2009 00:00
Picon
Gravatar

Ninux Day 2009

http://blog.ninux.org/2009/09/03/ninux-day-2009/

The Ninux.org team is glad to announce the first “Ninux Day”, the only
day that lasts a weekend ;)

A weekend surreal time slot on topics about wireless communities.
Under the same roof for the first time you’ll find hackers, geeks,
nerds, engineers, artists, curious and academics.

Presentations on technical and social topics will be faced with the
most expert people in the area of the wireless community networks,
that will come to Rome from all Europe.

Regards, Saverio Proto

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 0 comments |
headers
Michael Rack | 5 Sep 2009 21:47
Picon
Gravatar

Problem with Route-Distribution... dont know where the problem

Hi List,

i had never problems with OLSR. But now, i dont get rid of this problem 
and hope one of you can help me.

First: My Network-Setup:

#1 i386 Linux Router NIC <---> OSBridge 5GXi in Master-Mode <---> 
OSBridge 5GXi Slave-Mode <---> #2 i386 Linux-Router

On both i386 routers running the same binary:

	*** olsr.org - 0.5.6-r5 ***
	Build date: 2009-07-24 03:47:55 on saaldorf-surheim-r03
	http://www.olsr.org

#1 i386 Router is connected to an ISP and have OLSR running over a 
VPN-Tunnel. The Route-Distribution works as expected. I get all routes 
distributed to this router, including the default gateway.

My Problem is located at #2. Router #2 adds only HNA Broadcasts and the 
direct NIC-Interface-Addresses of Router #1.

Routing-Table managed by #1 (all routes are pushed by vpn-router 
xxx.205.12.0):

   router1 # ip route show table rsmconnect-networks
   xxx.205.12.9 via xxx.205.12.0 dev uplink  metric 2
   xxx.95.14.114 via xxx.205.12.0 dev uplink  metric 2
   xxx.95.14.17 via xxx.205.12.0 dev uplink  metric 2
(Continue reading)

Permalink | Reply | 0 comments |
headers
Henning Rogge | 6 Sep 2009 10:24

Re: Update on new stable version of OLSRd (0.5.6-r6)

Hello everyone,

here is another status update about the coming 0.5.6-r6 release.

We had four other patches this week, which fixed several small problems with 
Olsrd:
- John Hay found a bug in the dotdraw plugin which prevented normal usage
- Markus Kittenberg found a bug in his linux kernel cleanup patch, that 
exchanged "flat" and "non-flat" metric settings
- Yesterday we had a discussion that created two patches that fixed bugs with 
lq-multiplier and configurations with same IP on several interfaces. I don't 
like these two things, but at the moment we need them.

There are still two things in the pipeline for 0.5.6-r6 and I hope they will 
be available in the next two weeks, so we are delaying 0.5.6-r6 a little bit 
more:
- we are close to supporting Debian/FreeBSD for Olsrd. With the help of the 
debian team I integrated a new platform into our makefile system and it 
compiled well. There are still a few small issues with makefile configuration 
and placement of config variables, but I'm sure they will be easy to solve.
- Markus Kittenberg is working on a netlink patch for linux that will allow 
Olsrd to get a notification when an interface goes down. At the moment if you 
switch an interface off and on very fast Olsrd will not notice and don't reset 
the routes.

The current stable code is changeset 1861, you will find it at
http://gredler.at/hg/olsrd-0.5.6/rev/65d92f1e857a

Feel free to test it. :)
(Continue reading)

Permalink | Reply | 0 comments |
headers
shakkeera liaquath ali khan | 6 Sep 2009 13:43
Picon

which is the best simulator to do project by using olsr?????

hi all,
 
    tell me,which is the best simulator to do the project by using olsr....and also suggest the way to implement that protocol function....(MPR selection)...thank you
--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 1 comment |
headers
Henning Rogge | 6 Sep 2009 16:52

Re: which is the best simulator to do project by using olsr?????

Am Sonntag 06 September 2009 13:43:03 schrieb shakkeera liaquath ali khan:
> hi all,
> 
>     tell me,which is the best simulator to do the project by using
> olsr....and also suggest the way to implement that protocol
>  function....(MPR selection)...thank you
I don't think simulation of OLSR is a really good idea (unless you have a real 
routing agent which can also run in simulation mode), because you will never 
be sure if the implementation of OLSR in the simulation is comparable to a 
true OLSR routing daemon.

I would suggest using an emulation where you can use the same routing daemon 
software.

Henning

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 0 comments |
headers
VbaT S. | 6 Sep 2009 18:16
Picon
Favicon

OLSRD Mobility problem


I have installed olsrd on 6 Linksys Routers with OpenWrt firmware on each rooms. The dynamic routing table was working pretty well. I was successfully transfer file between 2 labtops(also running olsrd) while both of them were moving  but for video or audio conference (using RIP) I have a problem while routing table change, the conference freeze for almost 1 minute until it came back to normal state. Dose someone has any idea if I miss some configuration? 

This is my olsrd.conf that installed on all node

Interface "wlan1"
{
        HelloInterval           0.5
        HelloValidityTime       24.0
        TcInterval              2.0
        TcValidityTime          20.0
        MidInterval             18.0
        MidValidityTime         324.0
        HnaInterval             18.0
        HnaValidityTime         108.0
}
LoadPlugin "olsrd_httpinfo.so.0.1"
{
    PlParam     "port"   "80"
    PlParam     "Host"   "127.0.0.1"
    PlParam     "Net"    "192.168.0.0 255.255.0.0"
}
LoadPlugin "olsrd_dot_draw.so.0.3"
{
# accept connection from IP:
# default 127.0.0.1 (localhost)
PlParam     "accept" "127.0.0.1"
PlParam     "port" "2004"
}
LoadPlugin "olsrd_txtinfo.so.0.1"
{
        PlParam "accept" "127.0.0.1"
}

yours sincerely,
Vichao Saenghiranwathana



Windows Live: Make it easier for your friends to see what you’re up to on Facebook. Find out more.
Windows Live: Make it easier for your friends to see what you’re up to on Facebook. Find out more.
With Windows Live, you can organize, edit, and share your photos. Click here. 
--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 0 comments |
headers
VbaT S. | 7 Sep 2009 02:51
Picon
Favicon

Re: OLSRD Mobility problem

Its not really freeze but the transmission  speed drop for a couple seconds.

Date: Sun, 6 Sep 2009 22:45:15 +0200
Subject: Re: [Olsr-users] OLSRD Mobility problem
From: Markus.Kittenberger <at> gmx.at
To: v_bat <at> hotmail.com

and file transfers did freeze/stall also, or only for some seconds?
regards Markus

On Sun, Sep 6, 2009 at 6:16 PM, VbaT S. <v_bat <at> hotmail.com> wrote:

I have installed olsrd on 6 Linksys Routers with OpenWrt firmware on each rooms. The dynamic routing table was working pretty well. I was successfully transfer file between 2 labtops(also running olsrd) while both of them were moving  but for video or audio conference (using RIP) I have a problem while routing table change, the conference freeze for almost 1 minute until it came back to normal state. Dose someone has any idea if I miss some configuration? 

This is my olsrd.conf that installed on all node

Interface "wlan1"
{
        HelloInterval           0.5
        HelloValidityTime       24.0
        TcInterval              2.0
        TcValidityTime          20.0
        MidInterval             18.0
        MidValidityTime         324.0
        HnaInterval             18.0
        HnaValidityTime         108.0
}
LoadPlugin "olsrd_httpinfo.so.0.1"
{
    PlParam     "port"   "80"
    PlParam     "Host"   "127.0.0.1"
    PlParam     "Net"    "192.168.0.0 255.255.0.0"
}
LoadPlugin "olsrd_dot_draw.so.0.3"
{
# accept connection from IP:
# default 127.0.0.1 (localhost)
PlParam     "accept" "127.0.0.1"
PlParam     "port" "2004"
}
LoadPlugin "olsrd_txtinfo.so.0.1"
{
        PlParam "accept" "127.0.0.1"
}

yours sincerely,
Vichao Saenghiranwathana



Windows Live: Make it easier for your friends to see what you’re up to on Facebook. Find out more.
Windows Live: Make it easier for your friends to see what you’re up to on Facebook. Find out more.
With Windows Live, you can organize, edit, and share your photos. Click here.

--
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users


Windows Live: Make it easier for your friends to see what you’re up to on Facebook. Find out more. 
--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 0 comments |
headers
Markus Kittenberger | 7 Sep 2009 13:55
Picon
Picon

Survey about fib_metric usage

Hello
Does anyone really needs fib_metric, i mean requires another value than "flat"?
Background:
if kernel routing metrics are applied (e.g. fib_metric="approx" -> kernel routing metric = hopcount) to olsr routes,
this makes managing kernel routes more complex, 
and bloats the code of olsrd.
Furthermore many of my improvements to the routing code (to ensure that all olsr routes are correctly applied to the kernel (and stay there)), only work partly, or not effcient with fib_metrics != "flat",..
for example if olsr crashes and starts again, with fib_metric flat, the old routes will not be able to cause problems, they will get overwritten as soon as olsr has new routes again.
if not they may stay and may even interfere badly with routing if their metric (hopcount) is lower, than current best routes hopcount,..
also routes with an "flat" metric can get replaced directly in kernel, if they get different nexthop, and olsr does not need to make an delete && add like now in this case
So if u need this feature, please let me now, including for what u use it, beause there may even better/less_problmatic ways
regards Markus
--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 0 comments |
headers
kumar.vijai | 8 Sep 2009 08:42

Re: 3 PCs setup for OLSR

Hi Markus,
   thanks Markus.....:)
   You were right as I was getting some other outputs in #ip rule
command as I was having some force entries for routing table select.
   I changed the olsrd/conf file and commented the RtTable entries to
select kernel default table by olsrd.
   Now in setup PC1<-------->(eth0)PC2(eth1)<----------->PC3, We are
able to ping PC1 frpm PC3 and vice-versa.
   Now I have to run a vedio streaming from PC1 to PC3. Do you have any
idea to do it?
Vijai

-----Original Message-----
From: Markus Kittenberger [mailto:markus.kittenberger <at> gmail.com] On
Behalf Of Markus Kittenberger
Sent: Monday, August 24, 2009 6:12 PM
To: Vijai Kumar (WT01 - Joint CEO Office)
Subject: Re: [Olsr-users] 3 PCs setup for OLSR

Am 24.08.2009, 14:05 Uhr, schrieb <kumar.vijai <at> wipro.com>:

> Thanks again Markus for help.
> I tried your suggestions ann now I am able to ping pc1 and pc2 from
pc2.
> but even after running I am not able to ping PC1 from PC3 and 
> vice-versa.
> I have the setup as follows with bmf plugin running with olsrd. I 
> disabled the firewall at all the PCs.I attached the below output from 
> olsrd.
>
> I hope to get any clue from you...:)
>
> PC1<-------->(eth0)PC2(eth1)<----------->PC3
>
> PC1:Eth0:
> IP Address: 10.105.12.200
> Bcast Address: 10.105.12.255
> Subnet mask: 255.255.255.0
> Def Gateway: 10.105.12.1
> Default route: 10.105.12.1
> Primary DNS: 10.105.51.100
> Primary DNS: 10.105.50.100
>
> PC2:Eth0:
> IP Address: 10.105.12.201
> Bcast Address: 10.105.12.255
> Subnet mask: 255.255.255.0
> Def Gateway: 10.105.12.1
> Default route: 10.105.12.1
> Primary DNS: 10.105.51.100
> Primary DNS: 10.105.50.100
>
> Other subnet:
> PC2:Eth1:
> IP Address: 10.105.10.202
> Bcast Address: 10.105.10.255
> Subnet mask: 255.255.255.0
> Def Gateway: 10.105.12.1
> Default route: 10.105.12.1
> Primary DNS: 10.105.51.100
> Primary DNS: 10.105.50.100
>
> PC3:Eth0:
> IP Address: 10.105.10.203
> Bcast Address: 10.105.10.255
> Subnet mask: 255.255.255.0
> Def Gateway: 10.105.12.1
> Default route: 10.105.12.1
> Primary DNS: 10.105.51.100
> Primary DNS: 10.105.50.100
>
> While I ping PC1 from PC3 I am getting the follwing message in 
> wireshark at PC1----
> Source: 10.105.10.203 Dest: 10.105.10.200, protocol: ICMP, msg: Echo
> (ping) request.
> Source: MAC address of PC3  Dest: broadcast, protocol: ARP, msg: who 
> has 10.105.12.1? Tell 10.105.10.200

this means that pc3 searches for its (possible wrong) Default gateway
which it only does if there no olsr routes which mach better than the
default route

> The same message is displayed in wireshark at PC2:eth0 interface
>
> The fillowings are the output of olsrd at 3 PCs--->
>
> Setup:
> PC1:0.105.12.200<-------->0.105.12.201:(eth0)PC2(eth1):0.105.10.202<--
> --
> ------->10.105.10.203:PC3
> ############################ PC1 OLSR out put 
> #######################################################
> --- 15:58:18.761360 
> ----------------------------------------------------
> LINKS
>
> IP address       hyst         LQ       ETX
> 10.105.12.201    0.000  0.988/0.988    1.024
>
> --- 15:58:18.761408 ----------------------- TWO-HOP NEIGHBORS
>
> IP addr (2-hop)  IP addr (1-hop)  Total cost
> 10.105.10.203    10.105.12.201    2.048
>
> --- 15:58:18.761445 -------------------------------------------------
> TOPOLOGY
>
> Source IP addr  Dest IP addr          LQ        ETX
> 10.105.12.200   10.105.12.201   0.988/0.988    1.024
> 10.105.12.201   10.105.12.200   0.988/0.988    1.024
> 10.105.12.201   10.105.10.203   0.988/0.988    1.024
> 10.105.10.203   10.105.12.201   0.988/0.988    1.024
> ######################################################################
> ##
> ###############################
>
> PC1:0.105.12.200<-------->0.105.12.201:(eth0)PC2(eth1):0.105.10.202<--
> --
> ------->10.105.10.203:PC3
> ############################ PC2 OLSR out put 
> ###########################################################
> --- 15:58:46.944567 
> ----------------------------------------------------
> LINKS
>
> IP address       hyst         LQ       ETX
> 10.105.10.203    0.000  0.988/0.988    1.024
> 10.105.12.200    0.000  0.988/0.988    1.024
>
> --- 15:58:46.944622 ----------------------- TWO-HOP NEIGHBORS
>
> IP addr (2-hop)  IP addr (1-hop)  Total cost
>
> --- 15:58:46.944641 -------------------------------------------------
> TOPOLOGY
>
> Source IP addr  Dest IP addr          LQ        ETX
> 10.105.12.200   10.105.12.201   0.988/0.988    1.024
> 10.105.12.201   10.105.12.200   0.988/0.988    1.024
> 10.105.12.201   10.105.10.203   0.988/0.988    1.024
> 10.105.10.203   10.105.12.201   0.988/0.988    1.024
looks correct, but as it doens`t work,...

check (for exampl eon pc3) what
#ip route
(should contain routes to the other olsr routers) and #ip rule (should
be only 3 lines) print out

and pls leave the bmf plugin away (at least for the moment)

if ip route doen`s print the expected routes configure httpinfo (or
txtinfo), and check there if the links get symmetric, and if the olsr
wants to create routes (i mean if it list routes there)

lg Markus

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

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 4 comments |
headers
Markus Kittenberger | 8 Sep 2009 14:31
Picon
Picon

Re: 3 PCs setup for OLSR



On Tue, Sep 8, 2009 at 8:42 AM, <kumar.vijai <at> wipro.com> wrote:
Hi Markus,
  thanks Markus.....:)
thanks for the feedback *G 
  You were right as I was getting some other outputs in #ip rule
command as I was having some force entries for routing table select.
 you can also change them, so that the table olsrd uses gets used fo this parts of your routing you want him to get used for *G
  I changed the olsrd/conf file and commented the RtTable entries to
select kernel default table by olsrd.
  Now in setup PC1<-------->(eth0)PC2(eth1)<----------->PC3, We are
able to ping PC1 frpm PC3 and vice-versa.
  Now I have to run a vedio streaming from PC1 to PC3. Do you have any
idea to do it? 
use any software you like,.. 
.
or the maybe easiest solution:
attach an ip webcam (with its own http server) on one olsr node, and announce the ip of the webcam via hna (olsr config-option) to the other nodes
Markus
Vijai


-----Original Message-----
From: Markus Kittenberger [mailto:markus.kittenberger <at> gmail.com] On
Behalf Of Markus Kittenberger
Sent: Monday, August 24, 2009 6:12 PM
To: Vijai Kumar (WT01 - Joint CEO Office)
Subject: Re: [Olsr-users] 3 PCs setup for OLSR

Am 24.08.2009, 14:05 Uhr, schrieb <kumar.vijai <at> wipro.com>:

> Thanks again Markus for help.
> I tried your suggestions ann now I am able to ping pc1 and pc2 from
pc2.
> but even after running I am not able to ping PC1 from PC3 and
> vice-versa.
> I have the setup as follows with bmf plugin running with olsrd. I
> disabled the firewall at all the PCs.I attached the below output from
> olsrd.
>
> I hope to get any clue from you...:)
>
> PC1<-------->(eth0)PC2(eth1)<----------->PC3
>
> PC1:Eth0:
> IP Address: 10.105.12.200
> Bcast Address: 10.105.12.255
> Subnet mask: 255.255.255.0
> Def Gateway: 10.105.12.1
> Default route: 10.105.12.1
> Primary DNS: 10.105.51.100
> Primary DNS: 10.105.50.100
>
> PC2:Eth0:
> IP Address: 10.105.12.201
> Bcast Address: 10.105.12.255
> Subnet mask: 255.255.255.0
> Def Gateway: 10.105.12.1
> Default route: 10.105.12.1
> Primary DNS: 10.105.51.100
> Primary DNS: 10.105.50.100
>
> Other subnet:
> PC2:Eth1:
> IP Address: 10.105.10.202
> Bcast Address: 10.105.10.255
> Subnet mask: 255.255.255.0
> Def Gateway: 10.105.12.1
> Default route: 10.105.12.1
> Primary DNS: 10.105.51.100
> Primary DNS: 10.105.50.100
>
> PC3:Eth0:
> IP Address: 10.105.10.203
> Bcast Address: 10.105.10.255
> Subnet mask: 255.255.255.0
> Def Gateway: 10.105.12.1
> Default route: 10.105.12.1
> Primary DNS: 10.105.51.100
> Primary DNS: 10.105.50.100
>
> While I ping PC1 from PC3 I am getting the follwing message in
> wireshark at PC1----
> Source: 10.105.10.203 Dest: 10.105.10.200, protocol: ICMP, msg: Echo
> (ping) request.
> Source: MAC address of PC3  Dest: broadcast, protocol: ARP, msg: who
> has 10.105.12.1? Tell 10.105.10.200

this means that pc3 searches for its (possible wrong) Default gateway
which it only does if there no olsr routes which mach better than the
default route

> The same message is displayed in wireshark at PC2:eth0 interface
>
> The fillowings are the output of olsrd at 3 PCs--->
>
> Setup:
> PC1:0.105.12.200<-------->0.105.12.201:(eth0)PC2(eth1):0.105.10.202<--
> --
> ------->10.105.10.203:PC3
> ############################ PC1 OLSR out put
> #######################################################
> --- 15:58:18.761360
> ----------------------------------------------------
> LINKS
>
> IP address       hyst         LQ       ETX
> 10.105.12.201    0.000  0.988/0.988    1.024
>
> --- 15:58:18.761408 ----------------------- TWO-HOP NEIGHBORS
>
> IP addr (2-hop)  IP addr (1-hop)  Total cost
> 10.105.10.203    10.105.12.201    2.048
>
> --- 15:58:18.761445 -------------------------------------------------
> TOPOLOGY
>
> Source IP addr  Dest IP addr          LQ        ETX
> 10.105.12.200   10.105.12.201   0.988/0.988    1.024
> 10.105.12.201   10.105.12.200   0.988/0.988    1.024
> 10.105.12.201   10.105.10.203   0.988/0.988    1.024
> 10.105.10.203   10.105.12.201   0.988/0.988    1.024
> ######################################################################
> ##
> ###############################
>
> PC1:0.105.12.200<-------->0.105.12.201:(eth0)PC2(eth1):0.105.10.202<--
> --
> ------->10.105.10.203:PC3
> ############################ PC2 OLSR out put
> ###########################################################
> --- 15:58:46.944567
> ----------------------------------------------------
> LINKS
>
> IP address       hyst         LQ       ETX
> 10.105.10.203    0.000  0.988/0.988    1.024
> 10.105.12.200    0.000  0.988/0.988    1.024
>
> --- 15:58:46.944622 ----------------------- TWO-HOP NEIGHBORS
>
> IP addr (2-hop)  IP addr (1-hop)  Total cost
>
> --- 15:58:46.944641 -------------------------------------------------
> TOPOLOGY
>
> Source IP addr  Dest IP addr          LQ        ETX
> 10.105.12.200   10.105.12.201   0.988/0.988    1.024
> 10.105.12.201   10.105.12.200   0.988/0.988    1.024
> 10.105.12.201   10.105.10.203   0.988/0.988    1.024
> 10.105.10.203   10.105.12.201   0.988/0.988    1.024
looks correct, but as it doens`t work,...

check (for exampl eon pc3) what
#ip route
(should contain routes to the other olsr routers) and #ip rule (should
be only 3 lines) print out


and pls leave the bmf plugin away (at least for the moment)


if ip route doen`s print the expected routes configure httpinfo (or
txtinfo), and check there if the links get symmetric, and if the olsr
wants to create routes (i mean if it list routes there)

lg Markus

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


--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Permalink | Reply | 3 comments |

Gmane