Re: [Shorewall-users] Shorewall with DHCP: finding the subnet the host is on

[Niels P. <ni...@pe...>]

Hi Tom,

Thanks for the follow-up. I've specified 'required' in my interfaces
file. I've also made sure that the Shorewall init script won't be
started by the init system until the network is up. I believe this fixes
the problem/race without having to use a loop in the params file.

Niels

On 07/26/2014 11:44 PM, Tom Eastep wrote:
> On 7/26/2014 2:22 PM, Tom Eastep wrote:
>> On 7/26/2014 1:03 PM, Niels Penneman wrote:
>>> Thanks for the quick reply. It works flawlessly.
>>>
>>> Just one last question: why can I be sure though that shorewall runs the
>>> 'params' file after I've got an IP through DHCP?
>>
>> I suggest using 'wait=10' in the interface OPTIONS. That way, Shorewalll
>> startup can delay up to 10 seconds waiting for the interface to get an
>> IP address via DHCP.
> 
> I just realized that won't work right for you.
> 
> I suggest changing your params code after the function declaration
> 
> MYSUBNET=
> 
> while [ -z "$MYSUBNET" ]; do
>     MYSUBNET=$(find_interface_subnet eth0)
>     [ -n "$MYSUBNET" ] && break
>     sleep 1
> done
> 
> -Tom
> 
> 
> 
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> 
> 
> 
> _______________________________________________
> Shorewall-users mailing list
> Sho...@li...
> https://lists.sourceforge.net/lists/listinfo/shorewall-users
>