Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Eric Wood" <eric@interplas.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Forwarding Help
Date: Thu, 20 Nov 2003 16:20:10 -0500	[thread overview]
Message-ID: <000301c3afad$eefa7420$9100000a@intgrp.com> (raw)
In-Reply-To: SEA2-DAV257n6Hj1yNr000056bb@hotmail.com

Glacier----- Original Message ----- 
>From: Michael Menges
>I wish to have my gateway/firewall using iptables to forward incoming
internet traffic destined to port 443 (https) to another machine on my
localnet
>(192.168.0.10) keeping the same port number, obviously.  I'm on a cable
connection with a dynamic IP address, of course. I've read the FAQ's and man
>page but yet unable to come up with the proper syntax.  Any generic command
structures would be most helpful.


As far as your dynamic ip address is concerned, I seen where a US Robotics
wireless router will actually update your DynDNS account for you
automatically without needing the software on your server.  I guess other
routers are coming with this feature built in now-a-days.

-eric wood



  parent reply	other threads:[~2003-11-20 21:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 20:26 Forwarding Help Michael Menges
2003-11-20 20:40 ` Antony Stone
2003-11-20 21:23   ` Jeffrey Laramie
2003-11-20 21:37     ` Antony Stone
2003-11-20 21:20 ` Eric Wood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-26 22:03 Forwarding help sc2
2003-11-26 22:30 ` zechim
2003-11-26 22:30 ` Antony Stone
2003-11-27 11:07   ` sc2
2003-11-27 11:34     ` Antony Stone
2003-11-27 12:48       ` sc2
2003-11-27 12:58         ` Antony Stone
2003-11-27 13:14           ` Ray Leach
2003-11-27 13:21             ` Antony Stone

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='000301c3afad$eefa7420$9100000a@intgrp.com' \
    --to=eric@interplas.com \
    --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