in reply to Net::Ping not working right

Root permissions are required in order to successfully use the ICMP protocol, hence most firewalls will block all ICMP packets. I'd suggest the first step is, if at all possible, to establish just what protocols are allowed thro' your firewall(s) ... it may be that e.g. telnet _is_ allowed, in which case, you could use Net::Telnet in order to detect a login string.

You don't say which OS you're using, but in my (admittedly limited) experience, on a multiple interface system, the interface is selected by virtue of the address, hence (starts to cringe) you might be able to utilise modifications to the packet routing on your m/c in order to 'select' a WAN interface.

BTW, it frequently helps readability to use <p> tags to split your posting...

A user level that continues to overstate my experience :-))

Replies are listed 'Best First'.
Re^2: Net::Ping not working right
by aweber1nj (Initiate) on Dec 09, 2008 at 15:23 UTC
    The firewall is linux-based, the script runs as root, and since the script is actually ON the firewall, the icmp is allowed to the WAN. Especially given that the other WAN interface has no problem with the ICMP packets.

    The problem is with the ISP allowing the traffic, not my local LAN/Firewall.

    I don't think a telnet session can be directed to a specific interface, similar to what I was thinking with the HTTP-HEAD request.

[reply]
      As you so rightly say, the telnet connection can't, of itself, be 'directed', but temporarily modifying the routing tables c/w specifying the ip address of a known target host (assuming that each iface is connected to a separate network), should, IMHO, be capable of emulating the capability you seek...

      A user level that continues to overstate my experience :-))
[reply]

In Section Seekers of Perl Wisdom