From: Liam Helmer (linuxlists_at_thevenue.org)
Date: Wed 28 Apr 2004 - 19:22:50 BST
OK, it was worth a check.
Policy routing could potentially help, I haven't tested this setup, but:
add the table <vservername> to /etc/iproute2/rt_tables as table 200 or
something
ip rule add from <vserverip> to <destnet> table <vservername>
ip route add table <vservername> <destnet> [ via <router> ] src
<vserverip>
Might help you out. Only use the via router part if there's an
intervening router. I'm not 100% sure it'll catch the packets correctly
though, but it might be worth a shot.
Cheers,
Liam
On Wed, 2004-04-28 at 18:00, ryanmh_at_comcast.net wrote:
> Liam Helmer wrote:
> > Did you check those to make sure that packets coming from
> > your vserver addresses aren't being SNAT-ed to something?
> >
> > Just thought I'd check.
>
> Yeah, I saw that thread too. But in my case I'm using routable addresses so I'm not using SNAT.
>
> Thanks though,
> Ryan
>
>
> _______________________________________________
> Vserver mailing list
> Vserver_at_list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
>
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver