[OLSR-users] Re: OLSR Network Dying

[Andrew Hodel]

Below is output from iwconfig, ifconfig, and contents of olsrd.conf. 
All is the same on every node.

I changed every nodes netmask over to 255.0.0.0 although that should
not be the problem because of host routes.  This still did not fix it.

The problem with wrt54g that I was having, and hence stopped using
them, was bssid partitioning.  Now that I have an all prism network I
no longer have that problem.

The most interesting thing is that olsr continues to run and all nodes
have all nodes in the topology, you just can't do anything over the
network.



Andrew

mnode1:~# iwconfig
lo        no wireless extensions.

wifi0     IEEE 802.11b  ESSID:"test"
          Mode:Ad-Hoc  Frequency:2.412GHz  Cell: 02:02:C8:2C:0A:CE
          Bit Rate:2Mb/s   Sensitivity=1/3
          Retry min limit:8   RTS thr=64 B   Fragment thr=256 B
          Encryption key:off
          Power Management:off
          Link Quality:0/70  Signal level:-73 dBm  Noise level:-73 dBm
          Rx invalid nwid:0  Rx invalid crypt:237  Rx invalid frag:0
          Tx excessive retries:23903  Invalid misc:603122   Missed beacon:0

wlan0     IEEE 802.11b  ESSID:"test"
          Mode:Ad-Hoc  Frequency:2.412GHz  Cell: 02:02:C8:2C:0A:CE
          Bit Rate:2Mb/s   Sensitivity=1/3
          Retry min limit:8   RTS thr=64 B   Fragment thr=256 B
          Encryption key:off
          Power Management:off
          Link Quality:0/70  Signal level:-73 dBm  Noise level:-73 dBm
          Rx invalid nwid:0  Rx invalid crypt:237  Rx invalid frag:0
          Tx excessive retries:23903  Invalid misc:603122   Missed beacon:0

eth0      no wireless extensions.

mnode1:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:00:24:C3:FD:FC
          inet addr:63.98.170.222  Bcast:63.255.255.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:724556 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16640 errors:4 dropped:0 overruns:4 carrier:4
          collisions:0 txqueuelen:1000
          RX bytes:49976760 (47.6 MiB)  TX bytes:1992417 (1.9 MiB)
          Interrupt:11 Base address:0xf000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:78 errors:0 dropped:0 overruns:0 frame:0
          TX packets:78 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11308 (11.0 KiB)  TX bytes:11308 (11.0 KiB)

wifi0     Link encap:UNSPEC  HWaddr
00-02-6F-36-9E-83-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:987791 errors:0 dropped:0 overruns:0 frame:0
          TX packets:109386 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:194372235 (185.3 MiB)  TX bytes:29264115 (27.9 MiB)
          Interrupt:10 Memory:c4827000-c4828000

wlan0     Link encap:Ethernet  HWaddr 00:02:6F:36:9E:83
          inet addr:10.54.158.131  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:987791 errors:0 dropped:0 overruns:0 frame:0
          TX packets:109386 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:176591997 (168.4 MiB)  TX bytes:29264115 (27.9 MiB)
          Interrupt:10 Memory:c4827000-c4828000

mnode1:~# cat /etc/olsrd.conf
DebugLevel      0
IpVersion       4
Hna4
{
0.0.0.0 0.0.0.0
}
AllowNoInt      yes
Willingness     6
UseHysteresis   no
LinkQualityLevel        2
LoadPlugin "olsrd_nameservice.so.0.2"
{
        PlParam "name"  "mnode1"
        PlParam "hosts-file"    "/var/run/hosts_olsr"
}
Pollrate        0.05
Interface "wlan0"
{
    Ip4Broadcast                255.255.255.255
}
mnode1:~#


On 6/29/05, John Gorkos <(spam-protected)> wrote:
> On Tuesday 28 June 2005 10:52 pm, Andrew Hodel wrote:
> > Any ideas what is wrong, entire network is down...
> >
> > Andrew
> >
> Are you using any plugins?  Does every node have an identical olsrd.conf?  I
> had some similar problems until I took out all of the plugins, got everyone
> on the same version of olsrd, and used identical olsrd.conf files across the
> entire network.  I also had two "key" nodes (one was an HNA, one was not)
> that would do exactly what you're describing, so I set up a cron for them to
> reboot every night at 0200.  That was the final solution, and my network
> reliability has skyrocketed (save for the fact that I would _NEVER_ use
> WRT54Gs in a commercial environment again).
> 
> I'm attaching my "common" olsrd.conf from one of my nodes.  I use hysterisis,
> not LQ.  Nothing against LQ or Thomas' work, it's just what I started with
> and I was having enough success to not mess with it.  The olsrd.conf below is
> in place on every node in my network, save for the two HNAs, which use the
> dyn-gw plugin.  My network addressing scheme is the 192.168.7.0/24 subnet:
> i.e. inet addr:192.168.7.43  Bcast:192.168.7.255  Mask:255.255.255.0
> 
> #
> # olsr.org OLSR daemon config file
> #
> DebugLevel      0
> IpVersion       4
> 
> Hna4
> {
> }
> 
> Hna6
> {
> }
> 
> AllowNoInt      yes
> 
> IpcConnect
> {
>      MaxConnections  1
>      Host            127.0.0.1
> }
> 
> UseHysteresis   yes
> HystScaling     0.10
> HystThrHigh     0.60
> HystThrLow      0.20
> Pollrate        0.15
> 
> Interface "eth1"
> {
>   HelloValidityTime       20.0
>   TcValidityTime 40.0
> }
> 
> 
> > On 6/28/05, Andrew Hodel <(spam-protected)> wrote:
> > > In our network with 27 nodes, the network will simply die.
> > > Interesting is that olsr continues to run on each node, and each node
> > > is recieving packets from all other nodes.  Every node shows every
> > > other node in the topology and all routes are in place.  Whenever I
> > > try to do anything over the network however, ping tcp whatever,
> > > nothing works.
> > >
> _______________________________________________
> olsr-users mailing list
> (spam-protected)
> https://www.olsr.org/mailman/listinfo/olsr-users
>