[ program, system ] [ Propose Tags ]

It supports both IPv4 and IPv6. It works by monitoring the routing table and pinging the gateway (next hop) of a network interface. When the link is up and functioning the ping time is displayed in a small gtk window, otherwise the link status is displayed. linkchk can also run in a tty.

#### Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

• No Candidates
Versions [RSS] 0.0.2 ChangeLog base, gtk, haskell98, popenhs, regex-compat, unix [details] LicenseRef-GPL Jens-Ulrik Petersen Jens-Ulrik Petersen System http://www.haskell.org/~petersen/haskell/linkchk/ by GwernBranwen at 2008-02-17T05:18:02Z NixOS:0.0.2 1 direct, 0 indirect [details] linkchk 999 total (1 in the last 30 days) (no votes yet) [estimated by Bayesian average] λ λ λ Docs not available All reported builds failed as of 2017-01-03

[back to package description]
linkchk is an active network link monitor
(c) 2001 Jens-Ulrik Petersen <juhp@01.246.ne.jp>

DESCRIPTION

By default it repeatedly pings the IPv4 (or IPv6) address of
the default gateway of a given interface appearing in the
routing table and shows the link status in a small gtk
window or in a tty.  With appropriate options it can be used
monitor any interface with a gateway or to ping any specific
host.  gtk+hs is currently required to build it.  The reason
for starting this project was to monitor an unreliable ppp
link at home with a tendency suddenly to start dropping
packets after a while.

Currently it uses some options of ping, ping6 and netstat
that are probably specific to Linux, but porting to most
unices should be straightforward I imagine.  If you get
linkchk working on another platform and can send me patches,
or can send me "ifconfig" and "netstat" output from your
platform, then I will be happy to try to fold them into the
distribution.

other contributions, I would be glad to hear from you.

BUILDING

In order to build linkchk you need to have installed

Once you have those in place, you should be able to build in
the standard way;  ie something like:

% ./configure
% make
% make install

should make and install the executable "linkchk", that
you can then test by running.  "linkchk --help" lists its
options.