IP Forwarding with IP tables
Gary Stainburn
gary.stainburn at ringways.co.uk
Fri Oct 14 09:24:04 UTC 2005
On Thursday 13 October 2005 7:04 pm, Rodolfo Alcazar wrote:
>
> ifconfig eth1:1 x.y.z.141 netmask 255.255.255.248
> ifconfig eth1:2 x.y.z.142 netmask 255.255.255.248
> ifconfig eth1:3 x.y.z.143 netmask 255.255.255.248
I already had this bit
>
> now, the incoming tables:
>
> -A PREROUTING -d x.y.z.141 -j DNAT --to-destination 10.1.1.141
> -A PREROUTING -d x.y.z.142 -j DNAT --to-destination 10.1.1.142
> -A PREROUTING -d x.y.z.143 -j DNAT --to-destination 10.1.1.143
and this bit
>
> same for outgoing,
>
> -A POSTROUTING -s 10.1.1.141 -j SNAT --to-source x.y.z.141
> -A POSTROUTING -s 10.1.1.142 -j SNAT --to-source x.y.z.142
> -A POSTROUTING -s 10.1.1.143 -j SNAT --to-source x.y.z.143
>
That'sthe bit that was missing, thanks
> cheers
This works perfectly when I have a Linux box on the outside and another
linux box on the inside - they both present and see the IP addresses as
I need.
However, this setup is for a remotely monitored CCTV system, which then
failed when I then tried it. Anyone any ideas how I can sort this.
I'm thinking of how I can add logging to the above rules to see what is
and therefore also what isn't happening.
--
Gary Stainburn
This email does not contain private or confidential material as it
may be snooped on by interested government parties for unknown
and undisclosed purposes - Regulation of Investigatory Powers Act, 2000
More information about the users
mailing list