[WLANware] Problem with static routes 1.2.5

[Ramon Navarro Bosch]

Hey ! :)

For the catalan translation we are waiting an stable version of
freifunk. We will be glad to use it ! :) :) and if you need more
translations we can do it.

We use 10.224.0.0/16 as the OLSR areas joined with 10.224.254.0/24
tunnels. For the trunk we use 10.225.0.0/16. So that routes aren't from
olsr network.

On our problem our routes have been defined using metric 1 ... so we are
going to change metric from 1 to 0 :)

Thanks a lot and great job !

/Ramon

Sven-Ola Tuecke wrote:
> Ramon,
>
> the only vanishing static route should be a faulty default route. They are 
> maintained in /usr/sbin/cron.minutely and pushed to a background routing 
> table named "dyngw" if they do not function properly. Some annotations from 
> my side:
>
> - Does those static routes are in the same network segment as Wifi/OLSR? For 
> example: You use 10.1.2.3/8 on Wifi and with OLSR and set a static route 
> e.g. "ip route add 10.222.0.0/24 via 10.1.2.4". In this case, olsrd will 
> stumble eventually over this route and remove it while working. Routes in 
> the Wifi/OLSR range do not need to be "pushed" (aka configured statically), 
> they can be "pulled" from the gateway device by using HNA4. That's where 
> HNA4's are for.
>
> - Does those static routes have a metric > 0? If yes, the will be removed 
> from the olsrd-clearroutes script. Linux do not really support metric > 0, 
> but OLSR routes always have metric > 0 to mark the number of hops. If olsrd 
> does not run (e.g. Segfault), the "/etc/init.d/S53olsrd restart" triggered 
> by cron.minutely will automaticall remove them. This may explain the "some 
> hours" observation.
>
> - If both is not true I'am clueless. You can work around by using another 
> routing table. E.g. "ip route table add 123" and "ip route add 1.2.3.4/8 via 
> 1.2.3.5 table 123". Such things are described in the "Linux Advance Routing 
> Howto" http://lartc.org/.
>
> - Did you know, that a special Catalan Freifunk Version exists? Currently 
> testing, download here: http://styx.commando.de/sven-ola/testing/ 
> Web-UI-Preview here: http://styx.commando.de/sven-ola/ffca/
>
> HTH
> // Sven-Ola
>
> "Ramon Navarro Bosch" <ramon at epsem.upc.edu> schrieb im Newsbeitrag 
> news:4523B800.4060507 at epsem.upc.edu...
> Hi !
>
> I'm Ramon Navarro from GuifiBages catalonian group. We have been
> deploying a freifunk OLSR network arround our city ( Manresa 70000
> inhabitants ) and we have decided to use OLSR over a OSPF ad-hoc
> wireless network. We have installed a trunk network arround the city
> and a OLSR network over it connected using openvpn and bridge tunnels.
> With that solutions we can have roaming between all the points inside
> the city and we can join on piece of network from one side of the city
> to the other side by a good trunk connection.
>
> But after connecting the first nodes and configuring the freifunks we
> had one problem: the static routes on freifunk disapear after some
> hours of working. We don't understand why... when we execute
> /etc/init.d/S40network script static routes from nvram static_route
> appear again, but after some hours they desapear again. For us is
> really important that static routes because allow freifunks to go
> throw trunk to other freifunks and make tunnels work properly.
>
> Do you know why this routes may desapear ? maybe is olsr deamon that
> remove them ?
>
> Ramon
>
>
> _______________________________________________
> WLANware mailing list
> WLANware at freifunk.net
> Abonnement abbestellen? -> https://freifunk.net/mailman/listinfo/wlanware
>
> Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung 
> unter http://freifunk.net/mailinglisten 
>
> _______________________________________________
> WLANware mailing list
> WLANware at freifunk.net
> Abonnement abbestellen? -> https://freifunk.net/mailman/listinfo/wlanware
>
> Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten
>