[OLSR-users] Re: OLSR Network Dying

Sven-Ola Tuecke (spam-protected)
Sun Jul 3 19:02:42 CEST 2005 

Andrew,

you may need to cleanup your network first. Kill all olsrd daemons and enter 
the routing manually. If all works fine, continue with the next step. Your 
recent mails do not sound to me like OLSR problems rather than simple "wrong 
wireless, firewall, routing, ip, channel, mode, [insert favorite wlan config 
stuff here]" problems.

Manual routes also overwrite routes generated by olsrd, so after all is 
running fine with the manual setup, you may start olsrd on the nodes to 
check if the olsr signaling really disturbs your setup. The additional olsr 
routes should not interfere with your manual setup. After this, try deleting 
the manual routes.

Yes, this is work. I know. Too bad. Happy hacking :)

Rgds, Sven->Ola

"Andrew Hodel" <(spam-protected)> schrieb im Newsbeitrag 
news:(spam-protected)
I just switched the layer 2 network from the main olsr network and
everything is working fine on another essid/channel with olsr running.
 This means olsr is not the problem.  It must be something with noise
and too many nodes on the same channel?

I don't understand why large packets would never get through on any
nodes yet small packets would always get through on all nodes if the
problem is noise.

Any ideas?


Andrew

On 7/3/05, Andrew Hodel <(spam-protected)> wrote:
> It seems olsr may be causing this problem, I am not sure but here is
> the scenario.
>
> If I kill olsrd on a node that is still on the olsr network (layer 2)
> I have the same problem with large packets.  However, on this network
> this host is still getting olsr packets even though olsr is not
> running.
>
> When I switch the essid and channel to another network without olsr
> nodes on it, everything works fine.  Could the olsr packets be causing
> something?
>
> Could it also be the noise because of the olsr nodes on the other network?
>
>
>
> Andrew
>
>
> On 7/2/05, Bruno Randolf <(spam-protected)> wrote:
> > hello andrew!
> >
> > attached i send you the firmware versions which work for me. you can 
> > flash
> > them to the card permanently when you enable this option before 
> > compiling the
> > the hostap driver (define PRISM2_NON_VOLATILE_DOWNLOAD).
> >
> > the command to write them to the flash memory of the cards is
> >
> > prism2_srec -f $IF /tmp/sf010704.hex /tmp/pk010101.hex
> >
> > for mor infos about flashing firmware, check:
> > http://linux.junsun.net/intersil-prism/
> >
> > good luck!
> >
> > bruno
> >
> > On Saturday 02 July 2005 00:11, Andrew Hodel wrote:
> > > Well,
> > >
> > > I tried all the firmware down to version 1.4.9, still has this problem
> > > on packets > 100 bytes.  However, on all the versions if I set frag
> > > off rts off it works fine.  Since this is the only thing I can do, all
> > > nodes are like this for the time being.
> > >
> > > If I was to find a working firmware, would I have to load it to ram on
> > > every node reboot?
> > >
> > > If you have any suggestions I will try them, but thanks for your help
> > > to this point.
> > >
> > > For the list it seems the problem is the wireless interface (prism
> > > hostap) not allowing packets greater then 100 bytes.  It seems this is
> > > a frag/rts problem not mtu.
> > >
> > >
> > >
> > > Andrew
> > >
> > > On 7/1/05, Andrew Hodel <(spam-protected)> wrote:
> > > > I have updated it, the ram way.  Still not working from what I can
> > > > tell.  I guess there is no way to update to the card without 
> > > > windows?
> > > >
> > > > Considering these cards are all up on roofs in soekris boards 
> > > > running
> > > > linux....
> > > >
> > > > Any other suggestions.
> > > >
> > > >
> > > >
> > > > Andrew
> > > >
> > > >
> > > > mnode1:~# prism2_srec -r wlan0 1.7.4/rf010704.hex
> > > > srec summary for rf010704.hex
> > > > Included file name: RF010704.HEX
> > > > Component: 0x001f 1.7.4 (station firmware)
> > > >
> > > >
> > > > Verifying update compatibility and combining data:
> > > > OK.
> > > >
> > > > Downloading to volatile memory (RAM).
> > > > OK.
> > > > Components after download:
> > > >   NICID: 0x8013 v1.0.0
> > > >   PRIID: 0x0015 v1.1.1
> > > >   STAID: 0x001f v1.7.4
> > > > mnode1:~# ifconfig wlan0 down
> > > > mnode1:~# ifconfig wlan0 up
> > > > mnode1:~# hostap_diag wlan0
> > > > Host AP driver diagnostics information for 'wlan0'
> > > >
> > > > NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel 
> > > > flash))
> > > > PRIID: id=0x0015 v1.1.1
> > > > STAID: id=0x001f v1.7.4 (station firmware)
> > > > mnode1:~#
> > > >
> > > > On 7/1/05, Bruno Randolf <(spam-protected)> wrote:
> > > > > On Friday 01 July 2005 22:27, Andrew Hodel wrote:
> > > > > > On another subject, do you have any suggestions for frag/rts 
> > > > > > values?
> > > > >
> > > > > what we use over here in berlin (http://olsrexperiment.de) is frag 
> > > > > 500
> > > > > rts 250 - this seemed a good compromise between performance and
> > > > > stability, but we have not done real tests or research on it.
> > > > >
> > > > > bruno
> > > > >
> > > > > > Thanks,
> > > > > > Andrew
> > > > > >
> > > > > > On 7/1/05, Andrew Hodel <(spam-protected)> wrote:
> > > > > > > also want to note:
> > > > > > >
> > > > > > > On 7/1/05, Andrew Hodel <(spam-protected)> wrote:
> > > > > > > > This is what I have:mnode1:~/1.8.4# prism2_srec wlan0 s
> > > > > > >
> > > > > > > sf010804.hex  su010804.hex
> > > > > > > mnode1:~/1.8.4# prism2_srec wlan0 su010804.hex
> > > > > > > srec summary for su010804.hex
> > > > > > > Component: 0x001f 1.8.4 (station firmware)
> > > > > > >
> > > > > > >
> > > > > > > Verifying update compatibility and combining data:
> > > > > > > NICID was not found from the list of supported platforms.
> > > > > > > Incompatible update data.
> > > > > > > mnode1:~/1.8.4# prism2_srec wlan0 sf010804.hex
> > > > > > > srec summary for sf010804.hex
> > > > > > > Component: 0x001f 1.8.4 (station firmware)
> > > > > > >
> > > > > > >
> > > > > > > Verifying update compatibility and combining data:
> > > > > > > Could not find data position for plugging PDR 0x0413 at 
> > > > > > > 0x0000118a
> > > > > > > (len=2) PDR 0x0413 is not in wlan card PDA and there is no 
> > > > > > > default
> > > > > > > data. Ignoring plug record.
> > > > > > > OK.
> > > > > > > mnode1:~/1.8.4#
> > > > > > >
> > > > > > >
> > > > > > > it seems 1.8.4 is the latest version, not compatible??
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Andrew
> > > > > > >
> > > > > > > > mnode1:~# hostap_diag wlan0
> > > > > > > > Host AP driver diagnostics information for 'wlan0'
> > > > > > > >
> > > > > > > > NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST 
> > > > > > > > parallel
> > > > > > > > flash)) PRIID: id=0x0015 v1.1.1
> > > > > > > > STAID: id=0x001f v1.8.0 (station firmware)
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Andrew
> > > > > > > >
> > > > > > > > On 7/1/05, Bruno Randolf <(spam-protected)> 
> > > > > > > > wrote:
> > > > > > > > > On Friday 01 July 2005 20:37, Andrew Hodel wrote:
> > > > > > > > > > All prism cards, all hostap same version
> > > > > > > > >
> > > > > > > > > ok, thats what i have made the best experiences with.
> > > > > > > > > which firmware versions? i recommend:
> > > > > > > > >
> > > > > > > > > PRIID: id=0x0015 v1.1.1
> > > > > > > > > STAID: id=0x001f v1.7.4 (station firmware)
> > > > > > > > >
> > > > > > > > > bruno
> > > > > > > > >
> > > > > > > > > > Andrew
> > > > > > > > > >
> > > > > > > > > > On 7/1/05, Bruno Randolf <(spam-protected)> 
> > > > > > > > > > wrote:
> > > > > > > > > > > hello!
> > > > > > > > > > >
> > > > > > > > > > > this looks more like a layer 2 problem than a olsr 
> > > > > > > > > > > problem.
> > > > > > > > > > > do you use different types of wlan cards / drivers in 
> > > > > > > > > > > the
> > > > > > > > > > > network? i have seen problems like this when 
> > > > > > > > > > > different,
> > > > > > > > > > > buggy wlan drivers and firmware versions have been 
> > > > > > > > > > > used to
> > > > > > > > > > > form the ad-hoc network. unfortunately ad-hoc mode is
> > > > > > > > > > > implemented poorly in most drivers.
> > > > > > > > > > >
> > > > > > > > > > > bruno
> > > > > > > > > > >
> > > > > > > > > > > On Friday 01 July 2005 19:06, Andrew Hodel wrote:
> > > > > > > > > > > > This seems to be the problem.
> > > > > > > > > > > >
> > > > > > > > > > > > `ping -s 300 host` doesn't work, normal ping packets 
> > > > > > > > > > > > do.
> > > > > > > > > > > >
> > > > > > > > > > > > The mtu on all nodes is set to 1500, I don't know 
> > > > > > > > > > > > what
> > > > > > > > > > > > would be causing this.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Andrew
> > > > > > > > > > > >
> > > > > > > > > > > > On 7/1/05, Benoit PAPILLAULT 
> > > > > > > > > > > > <(spam-protected)>
> > wrote:
> > > > > > > > > > > > > Andrew Hodel a écrit :
> > > > > > > > > > > > > > Today I have extremely wierd problems, it seems 
> > > > > > > > > > > > > > I can
> > > > > > > > > > > > > > ping and telnet to hosts but when I try ssh or 
> > > > > > > > > > > > > > http
> > > > > > > > > > > > > > nothing works?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Could this be something with frag and rts being 
> > > > > > > > > > > > > > too
> > > > > > > > > > > > > > low?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Any ideas?
> > > > > > > > > > > > >
> > > > > > > > > > > > > It can be related to wrong MTU. I have a USB 
> > > > > > > > > > > > > adapter
> > > > > > > > > > > > > that says "MTU : 1500". However, if i send a 
> > > > > > > > > > > > > packet >
> > > > > > > > > > > > > 200 bytes, it fails and i got the same symptoms as 
> > > > > > > > > > > > > you.
> > > > > > > > > > > > > You can try ping with larger size to see if this 
> > > > > > > > > > > > > is
> > > > > > > > > > > > > your problem.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Benoit
> > > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > > olsr-users mailing list
> > > > > > > > > > > > > (spam-protected)
> > > > > > > > > > > > > https://www.olsr.org/mailman/listinfo/olsr-users
> > > > > > > > > > > >
> > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > olsr-users mailing list
> > > > > > > > > > > > (spam-protected)
> > > > > > > > > > > > https://www.olsr.org/mailman/listinfo/olsr-users
> >
> >
> >
>
_______________________________________________
olsr-users mailing list
(spam-protected)
https://www.olsr.org/mailman/listinfo/olsr-users

More information about the Olsr-users mailing list