Comment 0 for bug 31379

Package: knockd
Version: 0.4-1
Severity: important
Tags: patch

Short brief: my provider changes my IP every 24h. I use knockd listning
on ppp0. After IP change (I suppose it's down ppp0 then up ppp0) knockd
isn't working (ps aux | grep knock returns nothing). It may make ones
machine not accessible (when all ports are blocked and SSH is avaliable
only after knocking).
My knockd settings:
cat /etc/default/knockd
START_KNOCKD=1
KNOCKD_OPTS="-i ppp0"

Sample IP change in knockd.log:
cat /var/log/knockd.log
[2005-06-24 00:52] waiting for child processes...
[2005-06-24 00:52] shutting down

The solution seems to be restarting knockd every time the interface goes
up. I've created a script knockd and located it in /etc/ppp/ip-up.d/:
cat /etc/ppp/ip-up.d/knockd

#!/bin/sh
/etc/init.d/knockd restart

It seems to work OK now.
Haven't tested, but the same may be requied for ethx interfaces
(file knockd in /etc/network/if-up.d that restarts knockd).

-- System Information:
Debian Release: 3.1
   APT prefers testing
   APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.29
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages knockd depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libpcap0.8 0.8.3-5 System interface for user-level pa

--
No sig today.