[Olsr-users] Route desired destination-addresses alternatively

[Michael Rack]

To do it with HNA is a good idea, but is it able to configure 
HNA-Messages on interface-configuration?

Currently my HNA-Configuration look like the following:

Hna4
{
     91.205.xx.112  255.255.255.240
}

Interface "tun1" { weight: 1 }
Interface "tun2" { weight: 4 }
Interface "tun3" { weight: 7 }

Now, the remote machine reaches 91.205.xx.112  255.255.255.240 via tun3 
because the remote configuration like this:

Hna4
{
     0.0.0.0    0.0.0.0
}

Interface "tun1" { weight: 7 }
Interface "tun2" { weight: 4 }
Interface "tun3" { weight: 1 }

I like to route 91.205.xx.117 255.255.255.255 <http://255.255.255.255> 
over tun1 - not over tun3.

I think that is not able to do with olsr? :-)


Jacques _ schrieb:
> Ah, my bad ;-)
> I misunderstood what you meant by alternative.
>
> Have you tried the /32 Hna4 entry Aaron suggested ?
>
> Hna4
> {
>    91.205.xx.117 255.255.255.255 <http://255.255.255.255>
> }
>
> Jacques
>
> On Sat, Oct 18, 2008 at 7:24 PM, Michael Rack 
> <(spam-protected) 
> <mailto:(spam-protected)>> wrote:
>
>     Hi Jacques,
>
>     i think metric will only work when the device is going down
>     (mii-detect) ??
>
>     There is only UDP-Traffic, how should unix know about a link lost?
>
>     I think that is a not so good solution and olsr should do the job.
>
>     Cheers,
>     Michael.
>
>     Jacques _ schrieb:
>
>         Just add a backup for the other devices using metric:
>
>
>         ip route add 91.205.xx.117 via 91.205.xx.50 dev tap0
>         ip route add 91.205.xx.117 dev tap2 metric 30
>         ip route add 91.205.xx.117 dev tap1 metric 31
>
>         Jacques
>
>         On Fri, Oct 17, 2008 at 1:39 PM, Michael Rack
>         <(spam-protected)
>         <mailto:(spam-protected)>
>         <mailto:(spam-protected)
>         <mailto:(spam-protected)>>> wrote:
>
>            Hi List!
>
>            I have three Internet Service Providers. In expect two DSL
>            Providers and
>            one Wireless-Provider.
>
>            My Internet-Setup look as follow:
>            -------------------------------------------------------------
>            eth0 = Wirelees Provider (2048 down / 2048 up / 18ms Latency)
>            eth1 = DSL Provider (2048 down / 2048 up / 48ms Latency)
>            eth2 = DSL Provider (4096 down / 1024 up / 40ms Latency)
>
>            Over all three interfaces there run a vpn-tunnel from salzburg
>            (austria)
>            to nürnberg (germany) with fixed ip-addresses.
>
>            VPN-Tunnel look as follow:
>            -------------------------------------------------------------
>            TUNNEL  NÜRNBERG          SALZBURG          SPEED
>            -------------------------------------------------------------
>            tap0    91.205.xx.49/30   91.205.xx.50/30   2048 down /
>         2048 up / 18ms
>            Latency
>            tap1    91.205.xx.53/30   91.205.xx.54/30   2048 down /
>         2048 up / 48ms
>            Latency
>            tap2    91.205.xx.57/30   91.205.xx.58/30   4096 down /
>         1024 up / 40ms
>
>            In salzburg, OLSR will send traffic via vpn over tap0
>         (Wireless)
>            to get
>            2048k of upstream.
>            In nürnberg, OLSR will send traffic via vpn over tap2 (DSL)
>         to get
>            4096k
>            of downstream.
>
>            Now there is Voice-Over-IP on the traffic. 18ms is better then
>            40ms for
>            downstream.
>
>            The Asterisk-Server is located in salzburg and listen on
>            91.205.xx.117.
>            How can i route all traffic to this ip-address over tap0 to get
>            the 18ms
>            of latency for upstream reasons from Nürnberg to Salzburg?
>
>            When i do "ip route add 91.205.xx.117 via 91.205.xx.50 dev
>         tap0"
>            telephony will break if the interface goes down on the
>         remote side.
>
>            I like olsr do the job. If 91.205.xx.117 could not be
>         reached via
>            tap0,
>            olsr shoud route alternative to tap2 / tap1.
>
>            Is this setup to do with olsr?
>
>            Thanks in advance,
>            Michael Rack.
>
>            --
>            Olsr-users mailing list
>         (spam-protected) <mailto:(spam-protected)>
>         <mailto:(spam-protected)
>         <mailto:(spam-protected)>>
>
>         http://lists.olsr.org/mailman/listinfo/olsr-users
>
>
>
>