Thanks Michael for your answer!<br>
I finally did it in a way simillar as you described. Marking pakets and
using nat. BUT everything start working great when I found a
little detail:<br>
<br>
echo "0" > /proc/sys/net/ipv4/conf/eth1
<div id="mb_4">/rp_filter<br>
echo "0" > /proc/sys/net/ipv4/conf/eth2/rp_filter<br>
<br>
Without this, things were confused.<br>
<br>
Where this come from? I found this trick in a HowTo from a Spain site:<br>
<br>
<a href="http://bulma.net/body.phtml?nIdNoticia=1615" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://bulma.net/body.phtml?nIdNoticia=1615</a><br>
<br>
Nowhere else!<br>
So, what I did, is a common mistake? Is this assumed by default in
every configuration and because of this, there is no comments about
this in any other tutorial or howto?<br>
<br>
Anyway, ones again Mike, thank you!!<br>
<br>
Best regards<br>
<br>
J.D.Bistevins</div>
<br><br><div><span class="gmail_quote">On 12/20/05, <b class="gmail_sendername">Michael Davidson</b> <<a href="mailto:michael@bbd.co.za">michael@bbd.co.za</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br> There is another way to do this, but I doubt that it is anymore<br>elegant than what you have right now. I have just completed this same<br>task and I can say that if I could have used your method - overlaying<br>
another subnet -I would have done so since it's a cleaner solution in my<br>view.<br><br>I used iptables to "mark" the packets of the flows that where generated<br>by the server ( WWW).<br>I created a second routing table with it's own default route.
<br>I created an "ip rule" which looks for a "mark" on the packets and<br>directs those packets to the new routing table.<br><br>Keep in mind, for this to work correctly you need to be using NAT or<br>
Masquerade on at least one of your ISP ports.<br><br>Regards Mike<br><br><br></blockquote></div><br>