Netgear 834 port forwarding to different internal port?

Discussion in 'Home Networking' started by Ric, Dec 5, 2008.

  1. Ric

    Ric Guest

    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, Dec 5, 2008
    1. Advertisements

  2. Ric

    Ric Guest update: I'm talking about public/private ports. I'm sure my
    crappy old Conexants allowed this, the Netgear doesn't seem to.
    Ric, Dec 5, 2008
    1. Advertisements

  3. 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
    Jaimie Vandenbergh, Dec 5, 2008
  4. Ric

    Ric Guest

    bloody netgear. i'd just assumed it was in there, buried in the menus
    <googles> no thirdparty firmware for them, either.
    Ric, Dec 5, 2008
  5. Ric

    Rob Morley Guest

    Why not just run the service on the port that the router forwards to?
    Rob Morley, Dec 5, 2008
  6. Ric

    Ric Guest

    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.
    Ric, Dec 5, 2008
  7. Ric

    Rob Morley Guest

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

    ipfw add 2 fwd, 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
    Rob Morley, Dec 5, 2008
  8. Ric

    Jim Price Guest

    Some clues here:
    Should work if you can telnet to the Netgear box.
    Jim Price, Dec 5, 2008
  9. Ric

    Jamin Davis Guest

    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?
    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 Davis, Dec 7, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.