All of lore.kernel.org
 help / color / mirror / Atom feed
* looking for rules for samba-related traffic
@ 2003-04-06 18:31 Robert P. J. Day
  2003-04-07  4:13 ` Anthony M. Rasat
  0 siblings, 1 reply; 3+ messages in thread
From: Robert P. J. Day @ 2003-04-06 18:31 UTC (permalink / raw)
  To: iptables mailing list


  (sorry if you already saw this -- due to the fact that i've
been messing with my iptables setup, i'm not sure this made
it out the first time.)

  i'm looking for the ruleset to filter all samba-related
traffic.  i realize that this involves ports 137-9, based
on what i see in /etc/services.  but i did a quick google
search and a couple sample sets i've seen refer to TCP 
traffic, when i've already confirmed that, for example,
nmblookup is UDP.

  so, anyone have a pointer to a nicely-annotated set of
rules for samba, mounting filesystems, printing, etc?
thanks.  

  in the meantime, i'll just keep experimenting and 
watching the packets.

rday



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: looking for rules for samba-related traffic
  2003-04-06 18:31 looking for rules for samba-related traffic Robert P. J. Day
@ 2003-04-07  4:13 ` Anthony M. Rasat
  2003-04-07 12:41   ` Robert P. J. Day
  0 siblings, 1 reply; 3+ messages in thread
From: Anthony M. Rasat @ 2003-04-07  4:13 UTC (permalink / raw)
  To: netfilter

Dear Robert,

Most times, when configuring a firewall, people blocked everything first
then allow any service required. This goes for any incoming traffic rule.
Now, outgoing rule may vary. Some people like to let any outgoing traffic
may pass unchanged, some are not. In your case, if you wish to do so, your
can set rules to block outgoing TCP and UDP port 137 - 139. This rules will
not affecting Samba (or Microsoft Windows Network Sharing Service)
communication inside your internal network.

Examples? I think
http://www.linuxguruz.org/iptables/scripts/rc.firewall_002.txt should
answered the question.

 Regards,

A.


----- Original Message -----
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: "iptables mailing list" <netfilter@lists.netfilter.org>
Sent: Monday, April 07, 2003 1:31 AM
Subject: looking for rules for samba-related traffic


>
>   (sorry if you already saw this -- due to the fact that i've
> been messing with my iptables setup, i'm not sure this made
> it out the first time.)
>
>   i'm looking for the ruleset to filter all samba-related
> traffic.  i realize that this involves ports 137-9, based
> on what i see in /etc/services.  but i did a quick google
> search and a couple sample sets i've seen refer to TCP
> traffic, when i've already confirmed that, for example,
> nmblookup is UDP.
>
>   so, anyone have a pointer to a nicely-annotated set of
> rules for samba, mounting filesystems, printing, etc?
> thanks.
>
>   in the meantime, i'll just keep experimenting and
> watching the packets.
>
> rday
>
>
>
>
>



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: looking for rules for samba-related traffic
  2003-04-07  4:13 ` Anthony M. Rasat
@ 2003-04-07 12:41   ` Robert P. J. Day
  0 siblings, 0 replies; 3+ messages in thread
From: Robert P. J. Day @ 2003-04-07 12:41 UTC (permalink / raw)
  To: Anthony M. Rasat; +Cc: netfilter

On Mon, 7 Apr 2003, Anthony M. Rasat wrote:

> Dear Robert,
> 
> Most times, when configuring a firewall, people blocked everything first
> then allow any service required. This goes for any incoming traffic rule.
> Now, outgoing rule may vary. Some people like to let any outgoing traffic
> may pass unchanged, some are not. In your case, if you wish to do so, your
> can set rules to block outgoing TCP and UDP port 137 - 139. This rules will
> not affecting Samba (or Microsoft Windows Network Sharing Service)
> communication inside your internal network.

no, you have it backwards.  i'm starting from a position of DROP on all
chains, and want to slowly *open up* my firewall.  what i was after
was a set of (ideally minimal) rules that would allow just what was
needed for samba-related traffic.

i'm aware that that traffic involves ports 137-9, but wanted to
know if there was a summary of *precisely* what ports were involved,
and what they were used for, so i could know exactly what i had
to allow and what i could leave closed.

rday



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-04-07 12:41 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-04-06 18:31 looking for rules for samba-related traffic Robert P. J. Day
2003-04-07  4:13 ` Anthony M. Rasat
2003-04-07 12:41   ` Robert P. J. Day

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.