Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Basically, I have an IP Gateway that brings the connection in. From here I have two hardwired connections. The first runs to a wireless router, and the second runs to my personal computer.
Hardwired to the wireless router is a server offering up http and ssh accesss.
What I want is remote access from my computer to the server.
What I am getting is http access without ssh access.
The Gateway leases IPs of the 10.1.10.* variety and the router leases out 192.168.11.*.
That means my personal computer has an IP of 10.1.10.17, and the server has an IP of 192.168.11.13, and the router has an IP of 10.1.10.109.
The Gateway has no special configuration as per this interest. I assumed internal business like this would not require it since there is no need for access outside of the network itself.
The Router has Port Forwarding of port 80,8000,and 22 set to the 192.168.11.13 address.
There appears to be no firewall settings activated on the Gateway or the Router.
From my computer if I type http://192.168.11.13 I get my Apache2 server just fine, but when I try to ssh into the same IP I get a connection timed out error.
I want to resolve the ssh issue, but also what I am confused on is why http would work and ssh would fail.
Theoretically I thought I'd have to send my requests to the router's IP,10.1.10.109, and the router would forward me through to the necessary local IP,192.168.11.13, but instead I just send out the local IP and I get the server I want.
Hows am I missing...?
From my computer if I type http://192.168.11.13 I get my Apache2 server just fine
For this exact reason:
Quote:
Originally Posted by cin_
Theoretically I thought I'd have to send my requests to the router's IP,10.1.10.109, and the router would forward me through to the necessary local IP,192.168.11.13, but instead I just send out the local IP and I get the server I want.
What happens if you try to connect to the router address at 10.1.10.109 via both http and ssh?
Last edited by suicidaleggroll; 08-27-2012 at 04:36 PM.
pix9
(i) Yes, I have access to it if I have a computer hard wired to the router or on the router's wireless network. That is to say within the 192.168.11.* range.
(ii) Not that I know of. Everything seems set to be as open as possible... unless there is something I am missing.
(iii)
Code:
Port Forwarding Registration Information
Group,Internet Side IP Address,LAN Side IP Address,Protocol,LAN Side Port
http2, AirStation’s Internet IP Address, 192.168.11.13, TCP Port:8000, TCP Port:8000
http1, AirStation’s Internet IP Address, 192.168.11.13, HTTP (TCP Port: 80), HTTP (TCP Port: 80)
ssh, AirStation’s Internet IP Address, 192.168.11.13, SSH (TCP Port:22), SSH (TCP Port:22)
Last edited by cin_; 08-27-2012 at 04:53 PM.
Reason: gramm`err
suicidaleggroll, I agree completely. This is what is so troubling.
If I try to connect to the routers 10.1.10.109 address I get server not found in the browser, http, and port 22: connection timed out with ssh. Very strange.
Again, allow me to reiterate:
From within the router's network, ie the 192.168.11.*, I can use both http and ssh.
From without the router's network but within the gateway's I can somehow use the router's local address for the server, ie 192.168.11.13 to see the http, but it fails to work on the ssh as well as the router's IP address failing for both http and ssh.
Last edited by cin_; 08-27-2012 at 04:49 PM.
Reason: gramm`err
Okay the strange functionality seems to have stopped, but the problems persist.
Now when I type in the local IP outside of the router's network I am greeted with a server not found.
suicidaleggroll, if I type the 10.1.10.109 into the router's local network then I get the router's configuration page. The same as it's 192.168.11.1 IP.
Last edited by cin_; 08-28-2012 at 03:02 AM.
Reason: gramm`err
Sorry I didn't reply sooner - wasn't sure if you want to do what you're doing ! ...
You have a nested network - the router is an isolated network of its own. Since both routers are doing DHCP (giving out IP addresses), it is safe to assume they have a firewall on.
You will make your life simpler by making "the router" a bridge. That means only the "IP gateway" will be providing IP addresses, (DHCP service) and all computers/devices will be in the same subnet.
Different brand routers have differing ways to do this (read the manual) -
some will have a clear setup option for bridge mode; some will require you to turn off DHCP and connect your ethernet input to one of the LAN (normally output) jacks and not use the WAN (normally input) jack.
Of course, if I've misunderstood the purpose of what you're doing - let us know!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.