Re: AW: Add new target in mangle table

["manuel scheub" <manuprivat@gmx.de>]

-------- Original-Nachricht --------
> Datum: Tue, 15 Apr 2008 10:46:35 +0200 (CEST)
> Von: Jan Engelhardt <jengelh@computergmbh.de>
> An: manuprivat@gmx.de
> CC: netfilter-devel@vger.kernel.org
> Betreff: Re: AW: Add new target in mangle table

> 
> On Tuesday 2008-04-15 10:35, manuprivat@gmx.de wrote:
> >> >> >># iptables -t mangle -I PREROUTING -i eth2 -s 192.168.0.168 -j
> SADDR
> >> >> >>--to-source 10.0.19.2
> >> >> >
> >> >> One question this throws up... how do you know the address is
> >> >> 192.168.0.168?
> >> >
> >> >Actually, I dont know that! It is only an example to show the
> different
> >> >IP-ranges. Excuse my improper representation.
> >> 
> >> The question is more of a technical one-- if you do not know the
> >> source address the client will be using, how can you reliably
> >> mangle the address?
> >
> >I modified the udhcpd from the busybox  - have a look in the attached
> >file.
> >To handle the different cases i wrote a shell script - also attached.
> 
> But if the client uses DHCP, why don't you hand out 10.0.x.x directly?

If the client uses DHCP, i do hand out 10.0.x.x directly! The modified dhcpd listens on all requests, it doesn't matter if it is not a dhcp-request. And for the internal use of the gateway it provides a dhcp-lease, even if the request came from a user with a fix-ip entry.


-- 
Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games! 
http://games.entertainment.gmx.net/de/entertainment/games/free