Mailinglist Archive: opensuse-security (606 mails)
| < Previous | Next > |
Re: samba on firewall
- From: "office" <office@xxxxxxxxx>
- Date: Tue, 17 Apr 2001 12:57:54 +0200
- Message-id: <000d01c0c72d$413015e0$020101c8@workstation>
When setting samba=yes in firewall.rc.config, udp-port 137:138 is open
for the whole world. I want to close these ports. But when i set samba to "no" and
opening the tcp and upd ports for samba only for my internal network, it
doesn't work.
Need help.
>>i think tcp is missing for data-copying
>>IPCHAINS -A input -j "$ACCEPT" -p TCP -d 0/0 137:138 $LAA
----- Original Message -----
From: office
To: suse-security@xxxxxxx
Sent: Tuesday, April 17, 2001 12:03 PM
Subject: [suse-security] samba on firewall
Hello list!
Why does samba on the firewall don't work whitout this rule???
IPCHAINS -A input -j "$ACCEPT" -p udp -d 0/0 137:138 $LAA
When appending this rule, everybody can send UPD packets to 137:138.
I've tried to open tcp 135:139 and udp 135:139 only for internal network
but it doesn't work...clients cant use samba
any hints?
yours
B
for the whole world. I want to close these ports. But when i set samba to "no" and
opening the tcp and upd ports for samba only for my internal network, it
doesn't work.
Need help.
>>i think tcp is missing for data-copying
>>IPCHAINS -A input -j "$ACCEPT" -p TCP -d 0/0 137:138 $LAA
----- Original Message -----
From: office
To: suse-security@xxxxxxx
Sent: Tuesday, April 17, 2001 12:03 PM
Subject: [suse-security] samba on firewall
Hello list!
Why does samba on the firewall don't work whitout this rule???
IPCHAINS -A input -j "$ACCEPT" -p udp -d 0/0 137:138 $LAA
When appending this rule, everybody can send UPD packets to 137:138.
I've tried to open tcp 135:139 and udp 135:139 only for internal network
but it doesn't work...clients cant use samba
any hints?
yours
B
| < Previous | Next > |