All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M.F. PSIkappa" <psi@platon.atlantis.sk>
To: lartc@vger.kernel.org
Subject: [LARTC] Problem with routing,NAT and proxy arp
Date: Wed, 28 Mar 2001 08:14:14 +0000	[thread overview]
Message-ID: <marc-lartc-98576730303413@msgid-missing> (raw)

Hello,
I'd like to NATed some friends boxes into our network.

[ISP Router]---(Corp. LAN)---[[MY BOX with NAT]]-----(lan with friends)
1.1.1.1/24                     1.1.1.4/24 eth0           172.18.1.0/24
			     172.18.1.254/24 eth1

My seting:
I use kernel 2.4.2, iptables version 1.2

root@pokus:~# iptables -t nat -L -n               
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination         
DNAT       all  --  0.0.0.0/0            1.1.1.17     to:172.18.1.4 

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination         
SNAT       all  --  172.18.1.4           0.0.0.0/0    to:1.1.1.17 

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination 

I add arp proxy on eth0 with
ip neigh add proxy 1.1.1.17 dev eth0
With command arp -a -n I see this arp proxy but with ip neigh show I don't
see this one.

I test connection with ping, in tcpdump output I see that 172.18.1.4 is
right NATed to 1.1.1.17 and icmp request go out to the Corp. LAN.
I think that something is wrong with proxy arp because ping from some box
on Corp. LAN don't reach 1.1.1.17

What's wrong on my setup ?

PSIkappa
psi@atlantis.sk


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

                 reply	other threads:[~2001-03-28  8:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-98576730303413@msgid-missing \
    --to=psi@platon.atlantis.sk \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.