All of lore.kernel.org
 help / color / mirror / Atom feed
* owner based policy routing
@ 2002-10-11  4:04 Arindam Haldar
  2002-10-12  0:59 ` Julian Anastasov
  0 siblings, 1 reply; 4+ messages in thread
From: Arindam Haldar @ 2002-10-11  4:04 UTC (permalink / raw)
  To: LARTC; +Cc: NETFILTER

hi all,

THE SCENARIO:
we are connected to 2 isp, both having their large network.. isp A has 
gateway with ofc network while ispB has satellite gateway & hence there 
are advantages to take specific routes thru specific isp.

PRESENT IMPLEMENTATION:
the present linux box with kernel-2.4.19, julains multiroute patch, 
iproute-ss020116, htb3.6-020525 & iptables-1.2.7a... this box has 5 
ether ports & presently doing only **source** based policy routing for 
access to internet...at present no squid is implemented in this box... 
things are working good for last 40-45 days !

THE RULES DEFINED:
10: 
from all lookup main
50:     from <ipNetispA> lookup ispA
50:     from all fwmark       50 lookup ispA
75:     from <ipNetispB> lookup ispB
75:     from all fwmark       75 lookup GNFC
100:    from <localNetA> lookup balance
100:    from <localNetB> lookup balance
100:    from <localNetC> lookup balance
100:    from all fwmark      100 lookup balance
32766:  from all lookup main
32767:  from all lookup default

THE ROUTES:
[root@ICG surfNet]# ip route ls ta ispA
default via <gatewayISP-A> dev eth3  proto static  src <eth3ISP-A>
prohibit default  proto static  metric 1
[root@ICG surfNet]# ip route ls ta ispB
default via <gatewayISP-B> dev eth0  proto static  src <eth0ISP-B>
prohibit default  proto static  metric 1
[root@ICG surfNet]# ip route ls ta balance
default  proto static
         nexthop via <gatewayISP-A>  dev eth3 weight 3
         nexthop via <gatewayISP-B>  dev eth0 weight 1
prohibit default  proto static  metric 1
[root@ICG surfNet]# ip route ls ta default
default via <gatewayISP-B> dev eth0

THE GOAL:
we want policy routing based on owner of the packet, in perticular we 
want to handle squid to take the best path--best path according to 
us(pls no BGP here).

WHAT WE TRIED:
we tried using iptables owner based rules & marked packets( as one can 
see in rules above), but it didnt help.
iptables -I OUTPUT -t mangle -m owner --uid-owner <squid> -d 202.0.0.0/8 
  -j MARK --set-mark 50
iptables -I OUTPUT -t mangle -m owner --uid-owner <squid> -d 204.0.0.0/7 
  -j MARK --set-mark 50
iptables -I OUTPUT -t mangle -m owner --uid-owner <squid> -d 203.0.0.0/8 
-j MARK --set-mark 75
iptables -I OUTPUT -t mangle -m owner --uid-owner <squid> -d 216.0.0.0/8 
-j MARK --set-mark 75


but packets were not marked as seen by >> iptables -nvL -t mangle
& hence owner based pilicy routing not working

... hence now we turn to the list for help..
awaiting a reply ...
thanx to you all in advance...
A.H

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: owner based policy routing
  2002-10-11  4:04 owner based policy routing Arindam Haldar
@ 2002-10-12  0:59 ` Julian Anastasov
  2002-10-14 12:21   ` Arindam Haldar
  0 siblings, 1 reply; 4+ messages in thread
From: Julian Anastasov @ 2002-10-12  0:59 UTC (permalink / raw)
  To: Arindam Haldar; +Cc: LARTC, NETFILTER


	Hello,

On Fri, 11 Oct 2002, Arindam Haldar wrote:

> 50:     from all fwmark       50 lookup ispA

	fwmark in ip rule is 0x50 (it is defined and printed in hex)

> iptables -I OUTPUT -t mangle -m owner --uid-owner <squid> -d 202.0.0.0/8
>   -j MARK --set-mark 50

	and here 50 is 0x32 (not 0x50). Is that the problem?

Regards

--
Julian Anastasov <ja@ssi.bg>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: owner based policy routing
  2002-10-12  0:59 ` Julian Anastasov
@ 2002-10-14 12:21   ` Arindam Haldar
  2002-10-15  0:37     ` Julian Anastasov
  0 siblings, 1 reply; 4+ messages in thread
From: Arindam Haldar @ 2002-10-14 12:21 UTC (permalink / raw)
  To: Julian Anastasov; +Cc: LARTC, NETFILTER

ok, i have tried applying the ip rule fwmark in hex but dont see any 
difference !..

The routing decission is take be4 the packets comes to OUTPUT table, if 
thats true then it will be not possible to route **owner** as per policy 
routing--am i right ??
if ys then how can one achieve **owner** based policy routing in linux 
box ??

Julian Anastasov wrote:
> 	Hello,
> 
> On Fri, 11 Oct 2002, Arindam Haldar wrote:
> 
> 
>>50:     from all fwmark       50 lookup ispA
> 
> 
> 	fwmark in ip rule is 0x50 (it is defined and printed in hex)
> 
> 
>>iptables -I OUTPUT -t mangle -m owner --uid-owner <squid> -d 202.0.0.0/8
>>  -j MARK --set-mark 50
> 
> 
> 	and here 50 is 0x32 (not 0x50). Is that the problem?
> 
> Regards
> 
> --
> Julian Anastasov <ja@ssi.bg>
> 
> 
> 


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: owner based policy routing
  2002-10-14 12:21   ` Arindam Haldar
@ 2002-10-15  0:37     ` Julian Anastasov
  0 siblings, 0 replies; 4+ messages in thread
From: Julian Anastasov @ 2002-10-15  0:37 UTC (permalink / raw)
  To: Arindam Haldar; +Cc: LARTC, NETFILTER


	Hello,

On Mon, 14 Oct 2002, Arindam Haldar wrote:

> ok, i have tried applying the ip rule fwmark in hex but dont see any
> difference !..

	It is already in hex, use something like:

ip rule ... fwmark 50

iptables ... --set-mark 0x50

> The routing decission is take be4 the packets comes to OUTPUT table, if

	Right

> thats true then it will be not possible to route **owner** as per policy
> routing--am i right ??

	The sockets select route and when localout selects different
ISP may be the source should be changed too.

> if ys then how can one achieve **owner** based policy routing in linux
> box ??

	This is something that others should comment. NF is
supposed to do everything :)

Regards

--
Julian Anastasov <ja@ssi.bg>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-10-15  0:37 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-10-11  4:04 owner based policy routing Arindam Haldar
2002-10-12  0:59 ` Julian Anastasov
2002-10-14 12:21   ` Arindam Haldar
2002-10-15  0:37     ` Julian Anastasov

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.