configuring suse firewall to block outgoing SMB?
From: David Brower (sonicnews_at_browernet.org)
Date: 04/17/04
- Next message: Tim Ashman: "Re: Konqueror Pop Up Blocker"
- Previous message: It's New! It's Beige!: "A look at Suse 9.1"
- Next in thread: NeoSadist: "Re: configuring suse firewall to block outgoing SMB?"
- Reply: NeoSadist: "Re: configuring suse firewall to block outgoing SMB?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 17 Apr 2004 03:17:47 GMT
Sometimes I VPN to work, and my windows machines are hardwired to talk to
the WINS servers at work. When not connected via VPN, they still
try to send updates to the company WINS server, and these are leaking out
my SuSEFirewall2 machine.
I'd like to configure the firewall to block all outgoing packets on the public
interface directed to ports 135:139, without blocking traffic from the
firewall to the internal interface -- it has its own SMB exports and
needs to publish its own data locally.
Any ideas how to do this? I am an iptables n00b.
thanks,
-dB
- Next message: Tim Ashman: "Re: Konqueror Pop Up Blocker"
- Previous message: It's New! It's Beige!: "A look at Suse 9.1"
- Next in thread: NeoSadist: "Re: configuring suse firewall to block outgoing SMB?"
- Reply: NeoSadist: "Re: configuring suse firewall to block outgoing SMB?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|