Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: IPTables error
Date: Thu, 15 Jan 2004 00:17:23 +0000	[thread overview]
Message-ID: <200401150017.23259.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <217D777D3789FC4591199BA41FB0617A0101EB@nemo.scriptthis.net>

On Thursday 15 January 2004 12:08 am, Jerry Rasmussen wrote:

> When I try to add a command with eth1:1 get this error 'iptables -t nat
> -A PREROUTING -p tcp -i $ex_dev -d 216.27.xxx.xx --dport 3389 -j DNAT
> --to 192.168.xx.xxx
> Warning: wierd character in interface `eth1:1' (No aliases, :, ! or *)."
>
> I have done a good bit of Googleing I am sure there is an easy answer
> that I am missing

You are correct.   The easy answer is: "leave out the :1 on the interface 
name".

Multiple IPs are still bound to one real interface (this is more obvious if 
you use the recommended ip addr command instead of ifconfig eth1:1), and your 
netfilter rules should simply refer to the real interface which the packets 
come in on.

Antony

-- 
This email was created using 100% recycled electrons.

                                                     Please reply to the list;
                                                           please don't CC me.



  reply	other threads:[~2004-01-15  0:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15  0:08 IPTables error Jerry Rasmussen
2004-01-15  0:17 ` Antony Stone [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-25 12:56 iptables ERROR Ritesh Majumdar
2009-06-25 13:39 ` Richard Horton
2009-06-25 14:00 ` Ritesh Majumdar
2009-06-25 15:11   ` Jan Engelhardt
2009-06-25 18:08     ` Jozsef Kadlecsik
2004-08-25 12:56 Iptables error Jason Opperisano
2004-08-25 19:25 ` Jose Maria Lopez
2004-08-25  8:19 Paulo Andre
2002-11-12  0:07 iptables error jelenkovic

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=200401150017.23259.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.co.uk \
    --cc=netfilter@lists.netfilter.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