Comment # 8 on bug 943691 from Dominique Leuenberger

(In reply to Lars M�ller from comment #7)
> (In reply to Dominique Leuenberger from comment #6)
> > (In reply to Malvern Star from comment #5)
> > > Forgive my likely ignorance, but should the Firewall simply be set during
> > > install to allow outgoing connections on the relevant ports? This would not
> > > only allow KDE to browse shares by default but other desktop environments
> > > too.
> > 
> > I actually agree: the FW change is something that samba-client should take
> > care off... I could be using any DE (GNOME, KDE, XFCE) and even CLI tools to
> > browse shares.
> > 
> > the only common denominator would be samba libraries / client to actually
> > handle that.
> 
> This might open the ports in too many cases.  The goal is to modify the
> firewall setting if one of the desktop patterns gets selected.  But not
> in general if one of libsmbclient or samba-clients gets installed.

We're talking about poutgoing connections that need a crazy connection tracking
handler to be able to receive a reply (which is the purpose of the
FW_LOAD_MODULES="nf_conntrack_netbios_ns" statement)..

incoming connections (not initiated from the client) are of course a different
ballgame