LARTC
[Top] [All Lists]

[LARTC] source policy routing and SNAT - wrong hardware adress

To: LARTC@mailman.ds9a.nl
Subject: [LARTC] source policy routing and SNAT - wrong hardware adress
From: Markus <lartc@ethen.de>
Date: Sat, 24 Feb 2007 03:05:59 +0100
Delivered-to: sp-com-lists@consult.net
Delivered-to: lartc-list@securepoint.com
Delivered-to: lartc@outpost.ds9a.nl
List-archive: <http://mailman.ds9a.nl/pipermail/lartc>
List-help: <mailto:lartc-request@mailman.ds9a.nl?subject=help>
List-id: "Mailinglist of the Linux Advanced Routing &amp; Traffic Control project" <lartc.mailman.ds9a.nl>
List-post: <mailto:lartc@mailman.ds9a.nl>
List-subscribe: <http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc>, <mailto:lartc-request@mailman.ds9a.nl?subject=subscribe>
List-unsubscribe: <http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc>, <mailto:lartc-request@mailman.ds9a.nl?subject=unsubscribe>
Sender: lartc-bounces@mailman.ds9a.nl
User-agent: KMail/1.9.4
Hi,

when using diffrent routing tables, outgoing packets after SNAT always have 
hw-adresses as if the packed was coming from my machine. So a forwarded 
packet to default gw x on eth0 gets hw-adresses as if the same packet with 
origin loopback was routed to default gw y on network wlan0 which is 
diffrent.
I do "ip rule add iif lo table mine" and some "ip route add ... table mine" 
for local generated traffic. My "main" rt is configured for forwared traffic. 
"iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to 192.168.1.10" for NAT. 
(eth1 <-> [NAT] <-> eth0,  [local]<->[wlan0]).

Thanks for your help

Markus

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

<Prev in Thread] Current Thread [Next in Thread>
  • [LARTC] source policy routing and SNAT - wrong hardware adress, Markus <=