I've been using, with RH 5.2, ipchains rules and scripts as written by Robert Zeigler: http://rlz.ne.mediaone.net/linux/faq/index3.html Unfortunately, under 6.0, the dhcpcd interface information file is no longer created, so ipchains rules use the IP address I had months ago when I was still at 5.2 and thus don't work. The directory /etc/dhcpc exists and is writable: [root@stimpy network-scripts]# ls -ld /etc/dhcpc drwxrwxr-x 2 root root 1024 Jun 6 17:41 /etc/dhcpc This is not the problem. It is not the same issue as bug #3097, and bug #3132 (which I can't seem to reopen as it is marked a duplicate) does not address the matter (and asking me to code back in the use of dhcpcd is *not* an adequate solution if I intend to produce default ipchains rules to be used by others on the UW campus. If the solution involves that level of hacking, it isn't general enough. If pump is to replace dhcpcd, it should provide the same mechanisms for ease of integration with scripts that need the resulting addresses, etc. (as dhcpcd provided). Please have the engineer(s) who wrote pump address this. Thanks very much. -- Dave Dittrich dittrich.edu
The issues regarding pump are being addressed (read: pump is primitive) but there is no solution as of today (or probably for the next month). Meanwhile, dhcpcd is distributed with Red Hat 6.0 and there is an update that includes the directory in which the file needed by ipchains exists. I'd think seriously abou using dhcpcd if you need a solution today and are unable and/or unwilling to help fix pump.
Is using 'pump -s' from your scripts not a good enough way of getting the status information you need? I intended that to include everything your type of application might need. Please let me know what else pump -s should include. ------- Email Received From Dave Dittrich <dittrich.edu> 06/24/99 10:29 ------- ------- Email Received From Erik Troan <ewt> 06/24/99 11:04 ------- ------- Email Received From Dave Dittrich <dittrich.edu> 06/24/99 14:48 -------
If pump -s does not address your needs, please let me know. It should contain the proper information, and we believe it is a reasonable alternative to /etc/dhcpc