Persistant Static Routes based on TCP ports

[ESGLinux]

Hi,

I agree with Ray,

I think you can do it tagging the traffic.

I do it to route my http traffic for a specific eth this way:

-A PREROUTING -i eth0 -p tcp -m tcp --dport 80 -j MARK --set-mark 0x2

Then with the routes (basically you must change to your needs):

echo 203 web >> /etc/iproute2/rt_tables
ip rule add fwmark 2 table web
ip route add default via 192.168.3.1 table web


All of this commands are from the reference that give you Ray,

HTH,


ESG




2010/11/29 Ray Van Dolson <rvandolson at esri.com>

> On Mon, Nov 29, 2010 at 09:55:39AM -0800, Matty Sarro wrote:
> > I appreciate the followup, however that's not going to help us. As for
> what
> > we're trying to receive, only certain ports will be open on each server.
> > Basically what I need is policy  based routing, where the policy is
> > determined by TCP/UDP ports.
>
> You might need to make use of iptables and NAT.  Tag traffic heading
> out on a certain port to go out another interface, rewrite the source
> address correctly, etc.
>
> I've never tried this, but imagine it would work in simple cases,
> though for connections implemented by the client you'd obviously need
> to build either some intelligence into the client or use DNS SRV
> records to help define where connections should travel to based on a
> service identifier.
>
> LARTC[1] is still probably your best starter resource.
>
> Ray
>
> [1] http://lartc.org/howto/
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>