Guarddog Dropping Samba Connections

beartooth91 · 02-02-2009, 09:39 PM

I could use some help from an iptables guru on this.

I have a home network with 2 desktops and a laptop. One desktop is running Slackware 12.2 and I have a couple of shares and printer set up with Samba. The other desktop is running XP and the laptop is running Slackware 12.1. I have Guarddog set up on both Slack boxes. The Slack 12.2 desktop is connected via eth0 to a Linksys wireless router. I have Guarddog on both Slack boxes set up with a subnet of 192.168.1.0/24 and have permitted Samba, ftp, netbios, and printer spooling between the "Local" and "Subnet" zones on Guarddog. File sharing and printing work fine for awhile. After a period of time (an hour or more; maybe less), file sharing and printing via Samba cease to work. I get time out errors on the clients. Bringing up Guarddog on both Slack boxes and clicking on "Apply" (without changing the firewall config) fixes it for another short period of time. I'm going to guess that it works temporarily because iptables is restarted each time I re-apply the firewall. I'm also going to guess I need to hand modify 1 or more rules in the /etc/rc.firewall script. Any ideas on what exactly I need to look for and/or rewrite ?

Thanks

mRgOBLIN · 02-02-2009, 10:57 PM

Right after you start the firewall do

Code:

iptables -L -n >/tmp/start.txt

Then once you run into problems

Code:

iptables -L -n >/tmp/problem.txt

Then do a diff of the two files and see what rules are being modified by guarddog.

beartooth91 · 02-03-2009, 09:00 AM

Here it is. The "f2to1" chain allows traffic from my subnet to local. I'm wondering if adding a ",Established" to the f2to1 netbios, smb, and ftp chain entries in rc.firewall might solve the problem ?

beartooth91 · 02-05-2009, 09:06 AM

Folks, I gave some misinfo in my 1st post. The problem is only associated with the laptop and not my Slack desktop. And, reapplying the Guarddog firewall on the laptop fixes everything until next boot.
Now, it occurs to me that maybe whats going on here is that iptables is started via rc.firewall before my wlan0 wireless interface is started via wicd. I wonder if starting wlan0 at boot via rc.inet1 would solve the problem ? The problem with that is I've never been able to get it to work. I can configure the interface with ifconfig, iwconfig, and dhcpcd; but, when I set it up in rc.inet1.conf, it has some kind of problem with getting an assigned address. I get some messages about "polling for dhcp server" and "no carrier detected on wlan0". Setting it up in rc.inet1.conf with a static ip address makes no difference. And I've got wireless security (WPA, WEP) disabled on the router.