[Discuss] Startup script stopped

[John Blomfield]

Lionel Widdifield wrote:
> On Tue, Oct 27, 2009 at 09:44:25PM -0700, John Blomfield wrote:
>   
>> Looks like its a bug associated with certain wireless network drivers. 
>> https://bugs.launchpad.net/ubuntu/+source/guarddog/+bug/368496
>>
>> My Netbook is a Broadcom sta driver and the one reported above is an 
>> ath5k.  I thought it might be due to the fact that the network is not 
>> connected wirelessly until after the guarddog script rc.firewall is run 
>> but that is not the case because my laptop that uses an Intel 2915 
>> wireless card works without a problem.
>>
>> So the fix is to rerun rc.firewall script later in say rc.local?
>>     
>
>  Browsing the bug I noticed an IP address.
>
> Can you run "iptables -vnL |less" and see if your IP address is visible
> after guarddog is run and functioning?
>
>   
Problem SOLVED!!!  Thanks Lionel for pointing me in the right 
direction.  First I ran iptables as you suggested on my Netbook and as 
you predicted there was no IP address before running guarddog after KDE 
boot but it showed up afterwards.  Then I remembered that my Laptop did 
not have this problem so I checked the /etc/network/interfaces files, 
for the Laptop

auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp

The Netbook was the same without allow-hotplug eth0.  Once I added this 
to my Netbook interface file the IP showed up and everything worked!  I 
don't know why the installations are different and I don't know how 
allow-hotplug eth0 was added to one and not the other.  I certainly did 
not manually edit the file and I am not sure how it could have been done 
via a configuration GUI.  Any ideas?

John




John

>  There are 2 scenarios that fit your description. 
>
>  When guarddog is run either the device doesn't for it to find or it is
> looking for an IP to use in the script which won't exist until you're connected.
>
>  
>
>