All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Brill <kiowa@project23.no>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems with routes
Date: Thu, 06 Jun 2002 07:45:51 +0000	[thread overview]
Message-ID: <marc-lartc-102334959200566@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102327976303588@msgid-missing>

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

On Thu, 2002-06-06 at 01:42, Julian Anastasov wrote:
> 
> 	Hello,
> 
> On 5 Jun 2002, Alexander Brill wrote:
> 
> > Whenever I try to 'readd' a route I receive an error and I can't figure
> > out why...
> >
> > # Add some routes
> > ip route add $EXT via $INT
> > ip route add prio 320 from $INT nat $EXT
> 
> ip rule add prio 320 from $INT nat $EXT
> 
> > # Delete them
> > ip route del from $INT nat $EXT
> 
> ip route del prio 320 from $INT nat $EXT
> 
> > ip route del $EXT via $INT
> > # Add again
> > ip route add $EXT via $INT
> > ip route add prio 320 from $INT nat $EXT
> 
> ip rule add prio 320 from $INT nat $EXT
> 
> > The last command exits with exit-code '2' and the message:
> > RTNETLINK answers: Invalid argument
> 
> 	May be not only the last one :)
> 
> > What am I doing wrong?
> 
> 	Use ip rules for SNAT and ip routes for DNAT
> 

Thanks alot. Rather typical that you can't see your own typos ;)

-- 
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: 189 bytes --]

      parent reply	other threads:[~2002-06-06  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05 12:21 [LARTC] Problems with routes Alexander Brill
2002-06-05 20:43 ` Julian Anastasov
2002-06-06  7:45 ` Alexander Brill [this message]

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-102334959200566@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 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.