|
Posted by Ben Morrow on May 6, 2009, 12:18 am
> I submitted some firewall rules today which will be implemented before
> all the destination hosts are live on the network. In the past I put
> a perl script on each source server and controlled them from a central
> location to initiate a connection to each of the destinations to check
> the connectivity. In this case that will not work.
>
> Is there any scriptable way to know why a connection failed from the
> source? For example when a failure occurs...to know whether the
> connection was blocked by the firewall or it made it through but the
> remote host was not listening.
That depends on what your firewall does when it blocks a connection, and
whether it rewrites packets that do get through. If you can identify
from (say) a tcpdump log whether a connection was firewalled or not, you
can do it from Perl; otherwise, you can't.
Ben
| 
XML Sitemap
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
> all the destination hosts are live on the network. In the past I put
> a perl script on each source server and controlled them from a central
> location to initiate a connection to each of the destinations to check
> the connectivity. In this case that will not work.
>
> Is there any scriptable way to know why a connection failed from the
> source? For example when a failure occurs...to know whether the
> connection was blocked by the firewall or it made it through but the
> remote host was not listening.