Bug 105488 - Port ranges in yast's Firewall are not recognized.
Summary: Port ranges in yast's Firewall are not recognized.
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 1
Hardware: x86 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Lukas Ocilka
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-18 13:03 UTC by Menno Z
Modified: 2005-08-18 19:51 UTC (History)
0 users

See Also:
Found By: Beta-Customer
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 Menno Z 2005-08-18 13:03:48 UTC 
Since SUSE 9.3 port ranges are not a valid option in the Advanced tab of allowed
services/ports, in 9.2 a range could be entered like 1024:2048 but in 9.3 and
10.0 beta 1 it just gives the error "Port name '1024:2048' is unknown in your
current system. It probably would not work at all." It then asks if you really
want to continue, when saying continue it will add a bunch of services in the
list of allowed services (and those services are not even close to the port
range entered)
Comment 1 Menno Z 2005-08-18 16:07:11 UTC 
I should have waited 2 hours more so i could test this with Beta 2, it is fixed
in there.
Comment 2 Lukas Ocilka 2005-08-18 19:51:40 UTC 
You couldn't have know that before Beta2 has been released. Port ranges are
supported but there's no mention about it neither in the help nor in the manual.
So you, at least, need to know the SuSEfirewall2's syntax (or iptables). That's
why it is [Advanced...].

Documentation will be added into the next release, probably SUSE Linux 10.1.

Nevertheless thanks for resolving and testing this bug by yourself.