2
2
Main Problem
I have 2 networks and can only connect to LuCI from hosts on one of those networks. I can't figure out why I can't connect to LuCI from hosts in the other network. I'm having the exact same problem with SSH access as well. What confuses me is that I can ping the Rπ from both networks. I'm suspicious that it's a firewall config issue or something. I don't think it's a routing issue because I can ping Rπ from both networks (but it could be as I'm a noob).
Physical Setup
I have a modem connected to a Netgear router (router1) via WAN port. One of the Netgear's LAN ports is connected to a WAN interface on my Rπ1B (router2) and another Netgear LAN port is connected to a computer (computer1). There's another computer (computer2) connected to the LAN interface on the Rπ1B. Here's a summary and diagram of the setup:
Network 1: 192.168.0.0/25
- Netgear (router1) LAN interface: 192.168.0.1
- Rπ1B (router2) WAN interface 192.168.0.5
- computer1 192.168.0.50
Network 2: 192.168.0.128/25
- Rπ1B (router2) LAN interface 192.168.0.129
- computer2 192.168.0.150
More Details
Computer1
From network1 (192.168.0.0/25), computer1 (192.168.0.50/25) can successfully ping 192.168.0.1 and 192.168.0.5 on network1 but not 192.168.0.129 on network2. Using Google Chrome, computer1 successfully reaches the web interface for the Netgear at http://192.168.0.1 but gets ERR_CONNECTION_REFUSED when trying to connect to LuCI at http://192.168.0.5 and gets ERR_CONNECTION_TIMED_OUT when trying to connect to LuCI at http://192.168.0.129. Computer1 cannot connect to 192.168.0.5 or 192.168.0.129 via SSH.
Computer2
From network2(192.168.0.128/25), computer2 (192.168.0.150/25) can successfully ping 192.168.0.1 and 192.168.0.5 on network 1, and 192.168.0.129 on network 2. Computer2 can connect to all these routers' Web interfaces via Google Chrome (192.168.0.1, 192.168.0.5, and 192.168.0.129). And computer2 can connect to 192.168.0.5 and 192.168.0.129 via SSH.
Ultimately, I'm trying to use Google Chrome on computer1 to access LuCI via http://192.168.0.5, since it's technically on the same network as the Rπ's WAN interface.
1such as:
iptables -I INPUT -p tcp --dport 80 -j ACCEPT
which is handy if you don't have a connection to the LAN side, like if it was running in a vm or something. – Segfault – 2017-10-30T21:21:53.613