On 1/10/11 9:49 PM, Marcus Limosani wrote: > The machine is a virtual machine running on a VMWare system. > > It had previously been accessible from inside and outside of the internal > network. > > I could ping the IP address, which is 203.36.75.209 from within the internal > network, and access the services operating on the server from outside. > > Presently, there is no access to this internally or externally, and the > virtual machine itself can not reach any IP's outside itself. > > I am unsure what else to tell you.
You can start by telling where the virtual machine is. Is it running on the firewall system? On a local node? Somewhere else??? If it is running on a local system, then you need to add a route to the machine out of eth1. That has nothing to do with Shorewall. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
