RE: Serious NAT problem

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

 



W liście z pon, 29-03-2004, godz. 21:59, Daniel Chemko pisze: 
> Karol Tomala wrote:
> > Hello!
> > I have a question regarding netfilter. I have been looking for an
> > answer for two days and I'm hopeless. That's why I have decided to
> > ask for help here.

[cut]

> 1. If the default gateway on the 172 network is not your firewall, then
> this will break, because replies to the 10 network will trickle through
> your default router, not this firewall.

Network 172.18. shouldn't be obviously visible from network 10.128. Only
particular hosts should be transparently mapped to the 10.128. network
IP addresses. Unfortunatelly this firewall is not default gateway for
172.18. network. 

> 2. The DNAT rule is all you need if you just want to establishe
> conntections TO the 172 network. The SNAT rule is all you need to
> establishe connections TO the 10 network.

How should proper rule look like? Something like:

iptables -t nat -A PREROUTING -i eth2 -s 10.128.2.64/255.255.255.224 -d
10.128.2.70 -j SNAT --to-destination 172.18.5.2


> 3. You must either bind the .70 address to your eth2, or you have to
> proxy arp the address to the interface. Otherwise, requests for .70 in
> the 10 network will return failure. EG:
> ip addr add 10.128.2.70/16 dev eth2

I don't want to bind additional addresses for eth2. I have done a:
echo 1 > /proc/sys/net/ipv4/conf/eth2/proxy_arp
But still pinging 10.128.2.70 gives nothing but "arp who-has 10.128.2.70
tell 10.128.2.66" on tcpdump -i eth2 output. Could you help me a little
with setting proxy-arp properly?

Greetings,
--
Karol Tomala




[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