Johannes Graumann wrote: >One of my interfaces depends on dhcp and the IP it fetches changes more >often then I would like ... causing my half way complex shorewall setup to >get hickups. I was wondering what other people use in these situation - I'm >basically looking for a demon that watches the interfaces and upon IP >change runs "shorewall restart" which includes params lines fetching the >current IP addresses via python. I'm on debian and would prefer a solution >from the repository ... is arpwatch an option?
Debian uses the ISC DHCP client, and this runs a shell script to manage the interface. The simplest thing to do is probably to modify the script to automatically restart shorewall whenever it leases a new address. I'm not really that familiar with the client (most of my work is with the server), but if you get stuck then you'll find the DHCP Users list quite friendly. I imagine it probably only requires adding a "shorewall restart" to one or two places in the client script. DHCP Users can be found at : List-help: <mailto:[EMAIL PROTECTED]> List-unsubscribe: <mailto:[EMAIL PROTECTED]> List-Id: <dhcp-users.isc.org> List-subscribe: <mailto:[EMAIL PROTECTED]> List-owner: <mailto:[EMAIL PROTECTED]> List-post: <mailto:[EMAIL PROTECTED]> ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
