Yes, I'm bringing up the interfaces prior to running the scripts. If you haven't noticed this is a bridged firewall application. Using brctl I bring up the bridge interface then add the ethernet interfaces to it. Thinking that the interfaces needed more time to get active. I at one time put a sleep in the rc.firewall script right after the modules where loaded. Alas, same results. > -----Original Message----- > From: netfilter-admin@xxxxxxxxxxxxxxxxxxx > [mailto:netfilter-admin@xxxxxxxxxxxxxxxxxxx] On Behalf Of > David Canni > Sent: Friday, April 16, 2004 12:02 PM > To: netfilter@xxxxxxxxxxxxxxxxxxx > Subject: Re: Proof Read > > > > Can anyone proof over the following rc.firewall script and > throw some > > light as to why I get an 'Invalid Argument' on the two -m > physdev upon > > bootup. Yet, once the system is active the modules are > loaded and I can > > execute the script and, aside from the error that the modules are > > already loaded, it will not error out on the -m physdev statements. > > I assume you have already checked this but are you sure the > interfaces have > been configured and brought up by the point the script is > run? If you're > running it in rcX.d, make sure the iptables script comes > after the one that > configures network interfaces. > > David > >
