Bug 105434 - SUSE Firewall: Simple option to let smb browsing information pass
Summary: SUSE Firewall: Simple option to let smb browsing information pass
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Beta 2
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Ludwig Nussel
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-18 09:15 UTC by Tobias Burnus
Modified: 2005-08-18 10:13 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Burnus 2005-08-18 09:15:37 UTC 
I think this frequently occures: One is in a LAN which one not completely
trusts, does not want to offer any resources to the network, but would like to
browse in Konquorer using smb:/.

Currently, one has to dig deep to find this information - or one "simply"
disables the firewall. (If one already knows the name of the remote computer,
one can simply enter that one, but for browsing - ie seeing which Windows shares
are available - the default firewall blocks those.)

Expected: A simple option to accept those broadcasts. It increases the Desktop
feeling a lot, especially if most packages are still blocked ;)
Comment 1 Ludwig Nussel 2005-08-18 10:13:12 UTC 
client side smb browsing happens on arbitrary ports. You'd have to open udp  
1024: for that. broadcast replies are neither considered ESTABLISHED nor  
RELATED by netfilter so you'd really open the ports completely. see also  
#81254, I can't do anything about it atm. Broadcasts and untrusted networks 
just don't fit.