Netgear 834 port forwarding to different internal port?

Hi All,
Is it possible on a Netgear 834 to port forward to a different port on
the internal IP?
E.g. If I've got something that's running internally on port 8080, and
I want to access it from outside on port 80, I'd like to setup a port
forward to send external IP port 80 to my internal IP port 8080.
Anyone know if this is doable?

Ric

On 5 Dec, 08:52, Ric <infobub...@gmail.com> wrote:
> Hi All,
> Is it possible on a Netgear 834 to port forward to a different port on
> the internal IP?
> E.g. If I've got something that's running internally on port 8080, and
> I want to access it from outside on port 80, I'd like to setup a port
> forward to send external IP port 80 to my internal IP port 8080.
> Anyone know if this is doable?
>
> Ric

....to update: I'm talking about public/private ports. I'm sure my
crappy old Conexants allowed this, the Netgear doesn't seem to.

On Fri, 5 Dec 2008 03:42:49 -0800 (PST), Ric <(E-Mail Removed)>
wrote:

>On 5 Dec, 08:52, Ric <infobub...@gmail.com> wrote:
>> Hi All,
>> Is it possible on a Netgear 834 to port forward to a different port on
>> the internal IP?
>> E.g. If I've got something that's running internally on port 8080, and
>> I want to access it from outside on port 80, I'd like to setup a port
>> forward to send external IP port 80 to my internal IP port 8080.
>> Anyone know if this is doable?
>>
>> Ric
>
>...to update: I'm talking about public/private ports. I'm sure my
>crappy old Conexants allowed this, the Netgear doesn't seem to.

No, it doesn't. Annoying, eh?

Time to get a router that runs Tomato, I suppose. What other routers
do proper port-forwarding OOtB, folks?

Cheers - Jaimie
--
Sufficiently advanced incompetence is indistinguishable from malice.

On 5 Dec, 12:14, Jaimie Vandenbergh <jai...@sometimes.sessile.org>
wrote:
> On Fri, 5 Dec 2008 03:42:49 -0800 (PST), Ric <infobub...@gmail.com>
> wrote:
>
> >On 5 Dec, 08:52, Ric <infobub...@gmail.com> wrote:
> >> Hi All,
> >> Is it possible on a Netgear 834 to port forward to a different port on
> >> the internal IP?
> >> E.g. If I've got something that's running internally on port 8080, and
> >> I want to access it from outside on port 80, I'd like to setup a port
> >> forward to send external IP port 80 to my internal IP port 8080.
> >> Anyone know if this is doable?
>
> >> Ric
>
> >...to update: I'm talking about public/private ports. *I'm sure my
> >crappy old Conexants allowed this, the Netgear doesn't seem to.
>
> No, it doesn't. Annoying, eh?
>
> Time to get a router that runs Tomato, I suppose. What other routers
> do proper port-forwarding OOtB, folks?
>
> * * * * Cheers - Jaimie
> --
> Sufficiently advanced incompetence is indistinguishable from malice.

AAAAAAAAAAAAAAAAAAAAAAAARGH. <pause for breath>
AAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRGH.
bloody netgear. i'd just assumed it was in there, buried in the menus
somewhere.
<googles> no thirdparty firmware for them, either.

On Fri, 5 Dec 2008 05:37:01 -0800 (PST)
Ric <(E-Mail Removed)> wrote:

> AAAAAAAAAAAAAAAAAAAAAAAARGH. <pause for breath>
> AAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRGH.
> bloody netgear. i'd just assumed it was in there, buried in the menus
> somewhere.
> <googles> no thirdparty firmware for them, either.

Why not just run the service on the port that the router forwards to?

On Dec 5, 1:49*pm, Rob Morley <nos...@ntlworld.com> wrote:
> On Fri, 5 Dec 2008 05:37:01 -0800 (PST)
>
> Ric <infobub...@gmail.com> wrote:
> > AAAAAAAAAAAAAAAAAAAAAAAARGH. *<pause for breath>
> > AAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRGH.
> > bloody netgear. *i'd just assumed it was in there, buried in the menus
> > somewhere.
> > <googles> *no thirdparty firmware for them, either.
>
> Why not just run the service on the port that the router forwards to?

Because it's Apache on OS X and Unix doesn't seem to let you run
anything on ports <1024 unless you're running as root. Apart from the
built in services, anyway. I have only just discovered this.
Going to have to use Apache rewright in httpd.conf to get the Apache
server to forward to the app's server, I think.

On Fri, 5 Dec 2008 06:35:28 -0800 (PST)
Ric <(E-Mail Removed)> wrote:

> On Dec 5, 1:49Â*pm, Rob Morley <nos...@ntlworld.com> wrote:
> > On Fri, 5 Dec 2008 05:37:01 -0800 (PST)
> >
> > Ric <infobub...@gmail.com> wrote:
> > > AAAAAAAAAAAAAAAAAAAAAAAARGH. Â*<pause for breath>
> > > AAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRGH.
> > > bloody netgear. Â*i'd just assumed it was in there, buried in the
> > > menus somewhere.
> > > <googles> Â*no thirdparty firmware for them, either.
> >
> > Why not just run the service on the port that the router forwards
> > to?
>
> Because it's Apache on OS X and Unix doesn't seem to let you run
> anything on ports <1024 unless you're running as root. Apart from the
> built in services, anyway. I have only just discovered this.
> Going to have to use Apache rewright in httpd.conf to get the Apache
> server to forward to the app's server, I think.

Can't you just forward port 80 using ipfw? I found this:

//
ipfw add 2 fwd 127.0.0.1, 3128 tcp from any to any 80 in recv en1


this says , any traffic incoming on ethernet interface en1 destined for
port 80 redirect to port 3128
//

http://www.mail-archive.com/intermap.../msg01375.html

Ric wrote:
> Hi All,
> Is it possible on a Netgear 834 to port forward to a different port on
> the internal IP?
> E.g. If I've got something that's running internally on port 8080, and
> I want to access it from outside on port 80, I'd like to setup a port
> forward to send external IP port 80 to my internal IP port 8080.
> Anyone know if this is doable?

Some clues here:
http://www.plug.org/pipermail/plug/2...il/005962.html
Should work if you can telnet to the Netgear box.

--
JimP

<(E-Mail Removed)> wrote:

>> Why not just run the service on the port that the router forwards to?
> Because it's Apache on OS X and Unix doesn't seem to let you run
> anything on ports <1024 unless you're running as root. Apart from the
> built in services, anyway. I have only just discovered this.

Most Unix services will start as root to bind to a port <1024 and then
drop root privileges, forking as a regular system user. Like Apache
will start from init as root and then carry on as www-user/apache or
something similar. Perhaps your app will do that?

> Going to have to use Apache rewright in httpd.conf to get the Apache
> server to forward to the app's server, I think.

Could be messy, what about ipfw? I'm no OSX guru - but probably
something like:

ipfw add <rule_no.> fwd <ip>,80 tcp from any to any <dest_port> \
in via <interface>

I don't know where OSX stores it's firewall rules tho'.

--
Jamin @ Home @ Chester UK