All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] NATing problems
Date: Mon, 19 Mar 2001 03:17:57 +0000	[thread overview]
Message-ID: <marc-lartc-98497187706765@msgid-missing> (raw)

Hi,

I've looked in the archives, and I haven't found anything that deals with
what I'm seeing. :(

I have a briged dsl with 5 IPs.  I've been using one of them for over a year
without trouble.

Let me start with a diagram:

                 64.x.x.233
                NATing sdsl
                 10.1.1.1
                     \
      eth1:         eth2:
   63.x.x.202     10.1.1.2
             \   /
              \ /
          Linux 2.2.18
	       |
	      eth0:
	      /   \
	10.0.0.1  10.0.0.2

65.x.x.31 = outside comp
tcpdump version 3.4a6
libpcap version 0.4a6

ip ro add nat 63.x.x.203 via 10.0.0.3
#now it will respond to arps on eth1

ip ru add from 10.0.0.3 nat 63.x.x.203
#this is supposed to make the replies come back, but it doesn't

When I ping from outside host I can see the ARPs, and the incomming echo
requests, but no responses.  Also, if a ping comes in on eth1 to
63.x.x.203 it will show comming in but won't show going out on eth0.

Take a look at these cache lines:
63.x.x.203 from 65.x.x.31 via 10.0.0.3 dev eth0  src 63.x.x.202
\cache <dst-nat>  mtu 1500 rtt 375ms iif eth1


local 10.1.1.2 from 65.x.x.31 dev lo  src 10.1.1.2 \    cache <local>  iif
eth2


65.x.x.31 from 10.1.1.2 tos lowdelay via 10.1.1.1 dev eth2 \    cache  mtu
1500 rtt 375ms

Is linux router trying to send packets to 10.0.0.3 with src as 63.x.x.202?

I'm trying to get this working by monday, I home someone is watching today.

Mike

_______________________________________________
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-19  3:17 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-98497187706765@msgid-missing \
    --to=mfedyk@matchmail.com \
    --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.