Yo. This is what you said earlier: Tom Eastep > On 09/26/2012 01:10 PM, Tom Eastep wrote: >> On 09/26/2012 10:05 AM, Scott Ruckh wrote: >> >>> I was wondering if this is a solution I should pursue, and if so, what >>> is the correct way to add the iptables command using shorewall. >>> Thank you for reading. >> >> Is there a direct route to 172.19.73.31 out of eth2? >> > > And remember to take policy routing into account (look at the output of > 'shorewall show routing' rather than 'ip route ls' or 'netstat -nr'). > no results are returned when running;
$ sudo shorewall show routing | grep 172.19 The web article mentioned the ISP not accepting unicast messages -- This has not always happened, but I don't really have a timeline when it did start. Like if it happened after dhclient upgrade, an ISP change, or some other change. My network configuration has been static for quite some time, more then a year. I probably should have mentioned this earlier: $ shorewall version 4.5.6.2 $ lsb_release -a LSB Version: :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch Distributor ID: CentOS Description: CentOS release 5.8 (Final) Release: 5.8 Codename: Final $ rpm -q iptables iptables-1.3.5-9.1.el5 $ rpm -qf /sbin/dhclient dhclient-3.0.5-31.el5_8.1 ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
