All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dave Warchol" <Warchol@harthosp.org>
To: netfilter@lists.netfilter.org
Subject: RE: iptables and device aliases
Date: Wed, 18 Aug 2004 15:20:20 -0400	[thread overview]
Message-ID: <s12373bc.050@hcnwgwds01.hh.chs> (raw)

I will still need to define the device alias, correct?
Thanks
Dave

>>> "Jason Opperisano" <Jopperisano@alphanumeric.com> 08/18/04 09:25AM
>>>
> Hello:
>          I am new to the list.  I am currently using iptables to
> redirect traffic on eth0 for ports 80 and 443,  to ports 8080 and
8443,
> respectively.  I have request to set up another DNS name for this
server
> and to redirect entries coming to port 443 for this new DNS name to
port
> 8444.  I think that one way of doing this would be to define a
device
> alias, say eth0:1, assign it a new IP address and associate the new
DNS
> name with that new IP.  I could then use iptables to redirect traffic
on
> eth0:1, port 443 to port 8444.  I was just wondering if iptables
> recognizes/supports device aliases or if there is a better way of
> accomplishing the same thing.

iptables does not recognise the "eth0:1" syntax.  use ip aliases:

	ip address add x.x.x.x dev eth0

and then filter on "-i eth0" and ip address "x.x.x.x"

-j



             reply	other threads:[~2004-08-18 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 19:20 Dave Warchol [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-18 19:41 iptables and device aliases Jason Opperisano
2004-08-18 19:33 Daniel Chemko
2004-08-18 13:25 Jason Opperisano
2004-08-18 13:18 Dave Warchol

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=s12373bc.050@hcnwgwds01.hh.chs \
    --to=warchol@harthosp.org \
    --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 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.