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