Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Alexander Brill <kiowa@project23.no>
To: lartc@vger.kernel.org
Subject: [LARTC] nat
Date: Tue, 28 May 2002 11:03:11 +0000	[thread overview]
Message-ID: <marc-lartc-102258388103339@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 613 bytes --]

I'm trying to set up a nat here to forward traffic directed to
193.212.64.52 to 192.168.0.7 by using
`ip route add nat 193.212.64.52 via 192.168.0.7`

Doing a traceroute on that shows me it works fine.
But when I try to do it the other way around I seem to be banging my
head against the wall. I follow the instructions per ip-cref:
`ip route add prio 320 from 192.168.0.7 nat 193.212.64.53`. But this
only gives me "RTNETLINK answers: Invalid argument"

Any pointers on what might be wrong?

-- 
Alexander Brill <kiowa@project23.no>
http://www.project23.no
PGP-key: http://alexb.egil.org/key.pub

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2002-05-28 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 11:03 Alexander Brill [this message]
2002-05-30 12:27 ` [LARTC] nat Alexander Brill
2003-01-20 10:55 ` [LARTC] NAT maco heco

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-102258388103339@msgid-missing \
    --to=kiowa@project23.no \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox