netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexis <alexis@attla.net.ar>
To: netfilter@lists.netfilter.org
Subject: Re: IPTables, Linksys BEFSR41 and PCAnywhere
Date: Thu, 15 Jan 2004 15:18:43 -0300	[thread overview]
Message-ID: <1074190723.1570.10.camel@pepelui.baicom> (raw)
In-Reply-To: <000a01c3db92$465416d0$0f00a8c0@tandem>

youre right, just dont forget that pc anywhere uses 2 ports, that i
think they are 5631 and 5631 tcp

the linksys is with nat enabled? (its just to know, forwarding the ports
is enough to work)


On Thu, 2004-01-15 at 15:06, A. Clausen wrote:
> We are using netfilter to run a broadband wireless network.  For customers
> wanting a public IP, we simply forward a public IP to an internal NAT IP.
> 
> We have one customer who wants to use PCAnywhere remotely to contact his
> machine on the inside.  As usual, I simply forwarded a public IP to the
> private IP.  On the private IP they have a Linksys BEFSR41 router.
> 
> Basically it looks like this:
> 
> public ip ---> Linux netfilter router ---> private ip ---> Linksys
> router ---> customer's network
> 
> He is insisting that he needs to actually have a public IP, rather than just
> having our Linux router forward a public IP to a private.  We have other
> customers doing similiar things, one even opening up ports for MS-SQL
> server, without a problem, so I'm presuming that this customer is coming
> from a position of ignorance.  But before I start digging deeper, I need
> confirmation that this Linksys router is not some bizarre piece of hardware.
-- 
Alexis <alexis@attla.net.ar>



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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 18:06 IPTables, Linksys BEFSR41 and PCAnywhere A. Clausen
2004-01-15 18:18 ` Alexis [this message]
2004-01-15 18:30   ` A. Clausen
2004-01-15 18:52     ` Alexis
2004-01-15 22:07       ` Unknown, Alistair Tonner
2004-01-17  9:37     ` AW: " misiu_
2004-01-15 18:31   ` Caracal - G. Hostettler

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=1074190723.1570.10.camel@pepelui.baicom \
    --to=alexis@attla.net.ar \
    --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;
as well as URLs for NNTP newsgroup(s).