From: Ray B. <rj_...@rj...> - 2006-04-28 10:02:18
|
Bernhard Fr=C3=BChmesser wrote: > Tom Eastep wrote: >> Bernhard Fr=C3=BChmesser wrote: >> >> >>>> If I had to guess, I would suggest that the default route on the=20 >>>> systems >>>> in the local network is probably wrong but with so little to go on=20 >>>> that >>>> is only a wild guess. >> >> >> This still looks like it is the problem. Can you ping 194.166.207.200 >> from any of the local hosts? I doubt it. There was NO TRAFFIC FROM THE >> LOCAL NET TO BE FORWARDED BY THE FIREWALL -- NONE! Your Shorewall >> gateway cannot forward packets that aren't sent to it. >> >> So check the default gateway on the local system that you are trying t= o >> ping from -- its default gateway should be set to 192.168.0.122. > > On all local clients i have set the default gateway to 192.168.0.122. > From all local clients i can ping 192.168.0.122. > Tom asked to ping 194.166.207.200 not the gateway. > Bernhard > >> -Tom > > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, securit= y? > Get stuff done quickly with pre-integrated technology to make your job=20 > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache=20 > Geronimo > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=120709&bid&3057&dat=121642 > _______________________________________________ > Shorewall-users mailing list > Sho...@li... > https://lists.sourceforge.net/lists/listinfo/shorewall-users --=20 Ray Booysen rj_...@rj... |