This issue may or may not be because of how I configured m0n0wall, but I wasn't sure where else to post the question. I figured with all the network gurus around this forum someone might be able to help me figure out the issue.
Background: We used to have a central server connected directly to the DSL modem with two interfaces. interface eth1 was setup to respond to three of our external IPs, I'll call them ext54, ext55, and ext56. The internal interface, eth0, was setup as a gateway for the LAN on IP 192.168.0.1.
We wanted to install a hardware firewall and virtualize the existing server. So now it's setup so that the WAN interface of m0n0wall is connected directly to the DSL modem and responds to ext54, ext55, and ext56 and its LAN interface is the gateway for the 192.168.2.0 network. The server was virtualized and it's eth1 configuration was changed to be 192.168.2.2 with a gateway of 192.168.2.1. Everything seemed to be working fine.
Problem: The server runs apache for our webmail system, which works fine from the outside (since I have m0n0wall NAT port 80 through to 192.168.2.2), but inside it fails.
As best as I can figure the server (which is linux Centos 4.3), thinks that it should still respond to IP ext54 instead of forwarding it on to m0n0wall to figure out where it should go. I've looked through all the config files I can think of on the linux server (ifconfig, route table, hosts file) and I can't see anything that would make the server think it is ext54. I've also checked the logs and config of m0n0wall to see if the packets are getting dropped, and again, I don't see anything.
I guess I should say that our DSL provider gives us the IPs ext54, ext55, ext56, ext57, and ext58. When I tracert the IPs on the server ext54, ext55, and ext56 don't hop at all as if the server itself serves that IP, but ext57 and ext58 tracerts hop to the m0n0wall gateway correctly...which makes this even crazier in my opnion.
Any help you can provide in tracking down this issue would be greatly appreciated.
|
Topic: Weird IP issue