<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Michael H. Warfield" <mhw@WittsEnd.com><br><b>To: </b>"Atlanta Linux Enthusiasts" <ale@ale.org><br><b>Sent: </b>Tuesday, October 7, 2014 6:02:12 PM<br><b>Subject: </b>Re: [ale] Iptables based routing<br><div><br></div>> 192.168.42.100 would go down path A.<br>> 192.168.42.101 would go down path B.<br><div><br></div>If you are talking about the source addresses here, you are probably<br>going to need to resort to IP policy routing and the ip2 package and ip<br>command. That's not iptables. You'll probably have to set up some<br>policy routing tables and routing rules. The "ip" command is not the<br>best documented command but it's really at the heart of policy routing.<br>> </blockquote><div><br></div><div>That is fine. I can use ip2. On the OpenVPN server sites I can remove the push default gateway option. I then can use ip2 to route 0.0.0.0 from</div><div>192.68.42.100 down to the remote over tun?</div><div><br></div><div>Chris</div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><br></blockquote></div></body></html>