Question : 1 to 1 Nat

My network settings:
I have Time Warner Business Class Cable (one static IP) connected to a ClarkConnect linux box.
ClarkConnect is connected to a Linksys WRT54gs wireless router.
I just added a 1 to 1 nat rule on the ClarkConnect box which is passing my public ip traffic to a wireless router (in order to have multiple wired and wireless servers to be on the same subnet for development purposes)
This seemed to work like a charm... all of my computers are on the same subnet but I am now bypassing ClarkConnects pop and imap email services (I assume as well as VPN, FTP, etc).

Thanks

Answer : 1 to 1 Nat

Was your SMTP address in your mail client 66.79.00.00?  Or a DNS translation to this address?  If so, your 1-to-1 nat is sending it to your Wireless gateway.

If all of this is true, I believe we can overcome this problem by doing the following:

1.  Create a port forwarding rule of tcp 110 to destination 192.168.0.1 (ClarkConnect)
2.  Create a port forwarding rule of tcp 25 to destination 192.168.0.1 (ClarkConnect)

#2 (above) may or may not have to be done, depending on your SMTP address...does it also translate or is the ip address of your 1 public IP?  If so, add line #2
....
What's going on here, along with the last question you posted is we're getting heavy into the traffic directing part of network design.  For this particular problem, we've natted your public ip (66.79.00.00) to your private wireless router (192.168.0.2).  Since the port 25 service packet is coming from the internet into your Clarkconnect to be sent to your wireless router, we need a way to send it back to ClarkConnect...only because you have only 1 IP available.  OK, now that your wireless router's got the packet, we've created a port forwarding rule of POP and SMTP (subject to inclusion based on your mail client's smtp settings) services to point to 192.168.0.1 (ClarkConnect).  Since that IP address (from the port forwarding), from the perspective of your wireless router does not belong to its LAN subnet (192.168.1.x/24), it sends the packet the other direction toward the default gateway, which happens to be on the same subnet...192.168.0.x/24.

Services should work now, because your client sends a request to it's pop server (address 66.79.00.00).  The ClarkConnect is bouncing it to wireless router via 1-to-1 nat, then the port forward (tcp 110) on wireless is bouncing it back to ClarkConnect.

ClarkConnect has a path to send the reply back because of the source portion of the IP header (192.168.1.100 mac) because you setup a static route in your previous question posting on Experts-Exchange...all should work..please let me know

good luck
rc