Avi, This is normal and standard operation. I also run an NAT and while it is possible to configure your system to route the stuff to your outside interfrace, the easier, cleaner, safer solution is to setup either an named server (if you have more than 2 computers) or setup your hosts file so as it points the name of the server to the internal ip address. Of course you still have to remember to tell your applications to listen both on the external and internal ports, but most applications (both sendmail and postfix) come configured this way already. If you would like some more help with this feel free to e-mail me off list and you can post a summary of what worked for you when you get it all worked out. Austin Morgan On Wed, Apr 10, 2002 at 09:43:41AM -0500, Avi Schwartz wrote:

I currently have a problem where an I cannot access my external network interface from inside my NATed home lan. For example, I have an email account pointing to my external IP address. It is only accessible from outside the network (i.e. from work). If I try to use the same email account from inside my network, I fail to connect. I ended up creating a second account in my email program pointing this time to my non-public IP of the same server in order to access mail from inside my network.

I know that the firewall2 script is blocking it (I can see it in the logs), but I am not sure what do I have to change in firewall2.rc.config in order to fix this.

Thanks, Avi -- Avi Schwartz avi@CFFtechnologies.com

-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here

-- __ __ ____ ____ | \/ |/ ___/ ___| Austin Morgan | |\/| | | \___ \ Morgan Computer Services | | | | |___ ___) | 479-857-1189 |_| |_|\____|____/ www.morgancomputers.net