> #setup eth1 as a router > iface eth1 inet static > address 192.168.0.2 > network 192.168.0.1 > netmask 255.255.255.0
eth1 is not a "router"; however, that's irrelevant as that is just a comment. Remove the line starting 'network' - it is incorrect above, and isn't necessary anyway. > I can > partially ping 'www.google.com'. It'll resolve 'www.google.com' to the > correct IP address and domain name, but the packets keep timing out Thus you cannot ping www.google.com at all. Get things working from your system without Shorewall fist (do a 'shorewall clear'). Make sure you can ping external names/addresses. Then follow http://www.shorewall.net/two-interface.htm -- "You can have everything in life you want if you help enough other people get what they want" - Zig Ziglar. Who did you help today? ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
