On Mon, 22 Jul 2002, David Pitts wrote: > This is exactly my problem with Bering and Dachstein (but not with > Eigerstein!). > > Is it too lazy of me to ask someone to offer a script line that will > allow packets from 10.96.4.1 for Shorewall and Dachstein?? >
I'm afraid so. For Bering, this is a variation of Shorewall FAQ #14 (http://www.shorewall.net/FAQ.htm#faq14). > I have a couple of questions though that might help my understanding of > this whole thing. One, how does this impact on my internal DHCP server? > I'm using the default 192.168.1.x subnet. On Bering, there is no impact unless you unwisely specify 'norfc1918' on your internal interface in /etc/shorewall/interfaces. > And two, does this mean the firewall loads before DHCLient runs? No, but the firewall had been loaded long before DHCLient renews its lease and that's what this thread has been about. > Might be a silly question because > I guess I wouldn't be getting this problem if the order was reverses? > See above. > And just one more thing. Is there a config file that controls the order > the packages boot in?? > It's controlled by the RCDLINKS line in each of the package init scripts. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
