[RE: marking in output mangle with route lookup]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Gerorge,

Tried ( and failed ) with ip assigning. bummer. :-(

Thanks for your sugesstions -- my actual iptables enrty will read:

iptables --append OUTPUT --table mangle --match owner \ 
  --uid-owner 500 --jump MARK --set-mark 0x2

(I reduced the entry for the post because I couldn't get the fwmark to 
do a routing table lookup)

In general terms, I am generating traffic on this local box on behalf of
a network behind it -- the network behind gets billed for their traffic.
The match owner directive seemed a decent way to assign an ip that will
be correctly accounted for.

Do you know of another technique yielding the same result?

Ciao

Charles





On Sun, 2003-07-13 at 23:59, George Vieira wrote:
> Try using iproute2 ip assigning and not ip aliasing as I find aliasing=evil for some things.
> 
> ip addr add 192.168.1.101/24 dev eth1
> 
> Also, have you tried using SNAT instead of iproute for a simple snat of the source address?
> 
> iptables -I POSTROUTING -o eth1 -t nat -s 192.168.1.1 -d 192.168.1.250 -j SNAT --to 192.168.1.101
> 
> Thanks,
> ____________________________________________
> George Vieira
> Systems Manager
> 
> Citadel Computer Systems Pty Ltd
> http://www.citadelcomputer.com.au
> 
> -----Original Message-----
> From: lartc@xxxxxxxxxxxxxxxxxxx [mailto:lartc@xxxxxxxxxxxxxxxxxxx]
> Sent: Sunday, July 13, 2003 5:40 PM
> To: netfilter
> Subject: marking in output mangle with route lookup
> 
> 
> hello all,
> 
> i posted this to the lartc forum, and received no response, so i am hopeful
> that someone here can advise.
> 
> i have come accross a curious issue:
> 
> +----------------------+            +---------------+
> | eth1   192.168.1.1   |------------| 192.168.1.250 |
> | eth1:1 192.168.1.101 |            |               |
> +----------------------+            +---------------+
> 
> 
> iptables --append OUTPUT --table mangle --jump MARK --set-mark 0x2
> ip rule add fwmark 0x2 table 2
> ip route add 192.168.1.0/24 dev eth1 src 192.168.1.101 table 2
> ip route flush cache
> 
> 
> telnet 192.168.1.250 ; and tcpdump gives src ip address as 192.168.1.1
> 
> 
> ip rule add to 192.168.1.250 table 2
> ip route flush cache
> 
> 
> telnet 192.168.1.250 ; and tcpdump gives src ip address as 192.168.1.101
> 
> 
> 
> are there issues concerning the marking of OUTPUT packets generated on
> the local box that i should be aware of?
> 
> 
> many, many thanks
> 
> charles
> 
> 
> 
> 






[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux