SmokePing
Smokeping::probes::WebProxyFilterOverviewThis probe tests if your filtering webproxy is working properly. Drawing from a list of forbidden websites, it tries to establish a connection to each one of them and registers a 'loss' when it suceeeds. If you want to test availability of a website, use the EchoPingHttp probe. Synopsis*** Probes *** +WebProxyFilter forks = 5 maxsize = 2000 min_interval = 0.1 offset = 50% step = 300 timeout = 15 useragent = SmokePing/2.x (WebProxyFilter Probe) # The following variables can be overridden in each target section deny_re = Access Prohibited more_hosts = www.playboy.com, www.our-competition.com pings = 5 timeout = 2 # [...] *** Targets *** probe = WebProxyFilter # if this should be the default probe # [...] + mytarget # probe = WebProxyFilter # if the default probe is something else host = my.host deny_re = Access Prohibited more_hosts = www.playboy.com, www.our-competition.com pings = 5 timeout = 2 DescriptionThe probe uses the LWP::UserAgent module to retreive a series of wepages. It expects to get the firewalls 'site-prohibited' page. Any other response (or a real loss) gets logged as a loss and can be used to trigger an alarm. The probe tries to be nice to the firewall and waits at least X seconds between starting filetransfers, where X is the value of the probe specific `min_interval' variable (1 by default). Many variables can be specified either in the probe or in the target definition, the target-specific variable will override the prove-specific variable. VariablesSupported probe-specific variables:
Supported target-specific variables:
AuthorsTobias Oetiker <tobi@oetiker.ch> sponsored by Virtela BugsThis probe is somewhat unortodox, since it regards the sucessful retrieval of a banned webpage as a loss. |
|
04/29/2007 | Tobias Oetikersponsored by Virtela | OETIKER+PARTNER AG
|
NOTE: The content of this website is accessible with any browser. The graphical design though relies completely on CSS2 styles. If you see this text, this means that your browser does not support CSS2. Consider upgrading to a standard conformant browser like Mozilla Firefox or Opera but also Apple's Safari or KDE's Konqueror for example. It may also be that you are looking at a mirror page which did not copy the CSS for this page.