Package: approx Version: 3.3.0 Severity: normal approx, both in stable and testing, does not let to specify an IP address where it should listen at. It accepts an interface name here ($interface parameter) but it's a relic for a long time, since there's no one-to-one correspondence between an IP address and an interface name anymore.
F.e. my single eth0 interface here on a machine in a DMZ has two addresses, one "external" visible from outside, and second in range 192.168.x.x, -- this last one should be used by approx to listen to. If I specify eth0, approx will listen on the external address instead. Almost any other network-aware program out there nowadays asks for the IP _address_ to bind to, not an interface name. And sure thing, approx fails to start when given an IP address, with misleading diagnostics "unable to obtain IP address for interface 192.168.1.4". Many programs allows to be run from inetd, which, in turn, lets one to configure IP address(es) to listen on, connection rates, allowed/denied networks and the like (nothing from that is implemented by approx). But approx does not run in one-shot mode either. So for me, in its current form approx is unusable. And I were tempted to mark this bug as grave, but using "normal" severity still. Thanks. -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (990, 'stable'), (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.27-i686smp Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
