
Q: When I configure uid and gid to further restrict ipcad run-time environment,
   the rsh requests are failing with the following diagnostics:
	select: protocol failure in circuit setup
A: The RSH protocol employs two (2) TCP channels, one from client reserved port 
   to the server (ipcad) reserved port, and another one (though optional)
   from the reserved server port back to the one specified by client.
   The reserved port (<1024) may be opened only by privileged processes.
   The backward connection is created dynamically and cannot be pre-established
   and reused (like most of other resources can). Thus, RSH will not work
   in presence of uid restrictions, because these privileges are required
   each time client opens a new rsh connection to ipcad.
     It is believed that chroot and rsh ttl settings are enough to protect
   running ipcad from malicious clients, so uid restriction is not really
   such important. Do not use it.

Q: How can I configure multiple PPP interfaces without having to specify
   each one explicitly?
A: Use dynamic interfaces naming, where star character denotes a variable part:
	interface ppp*;
   This will monitor system's interfaces and listen on newly created ones
   when they become available.

Q: When dynamic interface is configured, ipcad throws something like this:
	Opening ... [/.../dev/bpf0] Can't initialize: No such file or directory
A: Your chroot environment does not have [enough] BPF devices inside,
   please make sure you have appropriate quantity of bpf devices.
   man bpf, man mknod, ls /dev/bpf*.
   NOTE: This comment is relevant only for *BSD systems or other systems
   where traffic snooping employs BPF devices.

Q: The rsh `show ip accounting` times out!
A: Read the ipcad.conf.default or the ipcad.conf(5) manual page; look for
   `rsh ttl` option.

