![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Eva_Unit_0
[H]ard|Gawd
- Joined
- Jun 1, 2005
- Messages
- 1,991
Okay, so I'm currently using an old box of mine as the router/firewall for my roommate and I in our dorm room. To start with, the network configuration is as such:
RIT Network--------->Router---------->16-port hub-----|--computers
Of course, the router has two NIC's in it--one receives an IP from the RIT network via DHCP while the other acts as a DHCP/DNS server for the rest of the network. Pretty typical home router setup. The router runs gentoo linux and was set up pretty much by this guide since, although linux is my strength, iptables most definitely is not.
Now, I'm having problems getting apache (and pure-ftpd, actually) to listen or respond on the WAN side IP address. I've configured them both to listen on all available IP's (and I've also tried forcibly setting them to just the WAN IP) and no matter what I do they only work on the local network. FTP and HTTP work fine as long as I'm at one of my computers on the LAN side of the router, even if I access it by WAN-side hostname. For example, let's say that my hostname on the WAN is computer.org and the WAN IP is 1.1.1.1 and the LAN side IP is 192.168.0.1. http://192.168.0.1 and http://computer.org both work just fine from the LAN side, however neither http://1.1.1.1 nor http://computer.org work if I'm on, say, a lab computer. The exact same also holds true for pure-ftpd. it is configured to listen on all IP's but it only works from LAN side.
Why would this be? Specifically, why does accessing it by hostname work on one side but not the other? I'm pretty clueless when it comes to iptables and I've been told that it might be an iptables issue but I honestly have no idea how I'd go about diagnosing that.
Oh, and I should mention that everything else works perfectly fine. I'm writing this post from this same network and it works for normal everyday use things without issues.
RIT Network--------->Router---------->16-port hub-----|--computers
Of course, the router has two NIC's in it--one receives an IP from the RIT network via DHCP while the other acts as a DHCP/DNS server for the rest of the network. Pretty typical home router setup. The router runs gentoo linux and was set up pretty much by this guide since, although linux is my strength, iptables most definitely is not.
Now, I'm having problems getting apache (and pure-ftpd, actually) to listen or respond on the WAN side IP address. I've configured them both to listen on all available IP's (and I've also tried forcibly setting them to just the WAN IP) and no matter what I do they only work on the local network. FTP and HTTP work fine as long as I'm at one of my computers on the LAN side of the router, even if I access it by WAN-side hostname. For example, let's say that my hostname on the WAN is computer.org and the WAN IP is 1.1.1.1 and the LAN side IP is 192.168.0.1. http://192.168.0.1 and http://computer.org both work just fine from the LAN side, however neither http://1.1.1.1 nor http://computer.org work if I'm on, say, a lab computer. The exact same also holds true for pure-ftpd. it is configured to listen on all IP's but it only works from LAN side.
Why would this be? Specifically, why does accessing it by hostname work on one side but not the other? I'm pretty clueless when it comes to iptables and I've been told that it might be an iptables issue but I honestly have no idea how I'd go about diagnosing that.
Oh, and I should mention that everything else works perfectly fine. I'm writing this post from this same network and it works for normal everyday use things without issues.