Find the answer to your Linux question:
Results 1 to 5 of 5
I've been trying for the past 3 days to setup outside access to my development server. Here's the specs: I have one cable line coming into a Compaq iPaq Connection ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jul 2003
    Location
    Erie, Pennsylvania
    Posts
    3

    Outside access/networking problem


    I've been trying for the past 3 days to setup outside access to my development server.

    Here's the specs:

    I have one cable line coming into a Compaq iPaq Connection Point CP-2E router, aka, a cheapo. It has DHCP enabled, and Virtual Server enabled (which pretty much is port forwarding.) The settings onthe Virtual Server take incoming requests to the Connection Point on port 80 and transfer them to 192.168.1.11 port 80 (the development server).

    The WAN IP is 24.49.56.109. The dev server (also the computer that I'm on at the moment) is set as the DMZ, so that the WAN IP is mapped to its network IP of 192.168.1.11

    On the Linux side, I'm running RedHat 7.1 with kernal 2.4.20. The eth0 is set as normal, and access to the internet is fine. The other computer on this network can access the web directory on the dev server just fine by typing in http://192.168.1.11/ or http://technologyx.homelinux.net.
    The etc/hosts file contains (aside from the defaults):
    192.168.1.11 technologyx.homelinux.net localhost

    The ServerName directive in httpd.conf is set to technologyx.homelinux.net
    BindAddress is set to *

    netstat -r shows:
    Destination: technologyx.homelinux.net Gateway: 192.168.1.1 Genmask 255.255.255.255 Flags: UGH MSS: 0 Window: 0 irtt:0 Iface: eth0
    Destination: 192.168.1.0 Gateway: * Genmask: 255.255.255.0 Flags: U Iface: eth0
    Destination: default Gateway: 192.168.1.1 Genmask: 0.0.0.0 Flags: UG IFace: eth0

    It should also be noted that I signed up for technologyx.homelinux.net at Dyndns.org, and its set to 24.49.56.109.
    Anyone on the network can type in http://technologyx.homelinux.net/ and access the server. Also by the 192.168.1.11 IP address.
    The problem is when I ask someone to type in the address from the outside (either 24.49.56.109 or technologyx.homelinux.net), netstat will show them as connecting to technologyx.homelinux.net:http with "SYN_RECV" under "Status". They say it says "Connecting" in the status bar of the browser, but then times out.

    I've read a hundred different web pages, read my book cover to cover, and used google so many times they're probably going to block my IP :P

    I figure its something small that Im overlooking, or Ive set something up wrong, any help would be greatly appreciated.

  2. #2
    Linux Guru
    Join Date
    Apr 2003
    Location
    London, UK
    Posts
    3,284
    first thought...

    iptables on the output chain

    EDIT:

    its not that. second thought,

    ive just given you a quick nmap, 80 is showing up as filtered. What i want to do is rule out any possibility of your ISP doing something stupid like blocking some of your ports.

    Can you restart apache on port 81, (edit httpd.conf, change "#port 80" to "port 80". then run "apachectrl restart".)

    then setup port forwarding on that port on your router if necessary.

    let me know when done.

    Jason

  3. #3
    Just Joined!
    Join Date
    Jul 2003
    Location
    Erie, Pennsylvania
    Posts
    3
    Done. Apache is listening on port 81 now, and any requests that come into the router at port 81 are served to my machine on 81.

    EDIT:

    It worked! Damn Adelphia I guess is blocking requests to 80, or maybe my machine is doing something its not supposed to.

  4. #4
    Linux Guru
    Join Date
    Apr 2003
    Location
    London, UK
    Posts
    3,284
    theres your answer. your isp is blocking port 80 to prevent you running a webserver. on port 81 i got:

    Technology-X Development Server
    This is a development and staging server. The sites and products contained here are either in early BETA stages or are in the process of being worked on. General public access is restricted.
    If you need to report a bug concerning one of our products or production websites, follow the link below (requires a BugZilla account):

    BugZilla



    akinder@technology-x.com
    Jason

  5. #5
    Just Joined!
    Join Date
    Jul 2003
    Location
    Erie, Pennsylvania
    Posts
    3
    Yeah, I just now figured that out from their site, that whole "We can change the TOS without telling anyone" clause.

    It also prohibits remapping ports, but I say, screw em, this is mostly for internal use, and a whole 5 people a month might go to the bugzilla install.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •