Thanks for the quick response.
-Youngdo
# iptables -nvL
For future reference, /sbin/shorewall status is more useful. I've deleted
all of the iptables output since my mailer is folding it but it showed that
since you last restarted Shorewall, your firewall had ACCEPTed 14
One final suggestion -- you might consider checking the rulesets again
(either in this fashion or the one Tom suggested, though I don't know
if
I'll be able to interpret Shorewall-specific reports) after some time
has
elapsed, just to be sure that the Samba retransmit failures have
actually
In my experience, operation not permitted errors on LEAF routers
typically (not always) signal problems with the firewall ruleset. In this
context, I'd suspect that to mean not a problem with Shorewall's default
settings (they are quite well tested by now) but one in some change you
You have rulesets in place that will pass state NEW SMB packets both ways
between the firewall and the LAN. They are in these rule sequences:
14 2109
eth1_inah -- eth1 * 0.0.0.0/00.0.0.0/0
(in INPUT)
14 2109
loc2fw ah -- *
Hi!
Is shorewall configured by default to drop/reject udp broadcasts?
I'm trying to setup samba and my windows machines can't see the samba server
(which is also the firewall). I see the following errors in log.nmbd:
[2002/12/02 16:58:02, 0] nmbd/nmbd.c:main(794)
Netbios nameserver
Hi!
I am a Bering v1.0-stable user.
Is shorewall configured by default to drop/reject udp broadcasts?
I'm trying to setup samba and my windows machines can't see the samba server
(which is also the firewall). I see the following errors in log.nmbd:
[2002/12/02 16:58:02, 0]
On Tue, 03 Dec 2002 02:56:52 +0900 youngdo wrote:
PiA+IFsyMDAyLzEyLzAyIDE2OjU4OjAyLCAwXQ0KPiA+IG5tYmQvbm1iZF9iZWNvbWVfZG1iLmM6
YmVjb21lX2RvbWFpbl9tYXN0ZXJfYnJvd3Nlcl9iY2FzdCgyOTEpDQo+ID4gYmVjb21lX2RvbWFp
[Ick, another base64-encoded message. Grrr...]
[2002/12/02 16:58:02, 0]
In my experience, operation not permitted errors on LEAF routers
typically (not always) signal problems with the firewall ruleset. In this
context, I'd suspect that to mean not a problem with Shorewall's default
settings (they are quite well tested by now) but one in some change you
made. To
Try doing a search for the firewall in the windows find a computer
option. My Bering - Samba server does not show up in the browse list.
but works flawlessly. I have network drives mapped to it that reconnect
on boot. You need rules to open net to fw for UDP 137 and 138 as well as
tcp 139.
Kory
