[Bug 829706] New: YaST2 firewall masquerading creates too many arguments in /etc/sysconfig/SuSEfirewall2
https://bugzilla.novell.com/show_bug.cgi?id=829706 https://bugzilla.novell.com/show_bug.cgi?id=829706#c0 Summary: YaST2 firewall masquerading creates too many arguments in /etc/sysconfig/SuSEfirewall2 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dave@pds-uk.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 When using YaST2 firewall configuration GUI to enable masquerading the resulting configuration that is written to "/etc/sysconfig/SuSEfirewall2" has too many arguments and masquerading (for at least UDP) does not work. Running /sbin/SuSEfirewall2 from the command line gives: SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... SuSEfirewall2: Error: too many arguments in FW_FORWARD_MASQ -> 0/0,192.168.100.137,udp,47976,47976,* SuSEfirewall2: Firewall rules successfully set By removing the last two arguments the problem goes away... FW_FORWARD_MASQ="0/0,192.168.100.137,udp,47976" Now running /sbin/SuSEfirewall2 the firewall starts successfully without errors and masquerading works. I have never manually edited the firewall configuration file before by hand and this is a clean install with no other software installed that should change it. Reproducible: Couldn't Reproduce Steps to Reproduce: 1.Go to YaST2 firewall configuration 2.Created a new masquerading entry to a different address/port 3.Checked the generated file: /etc/sysconfig/SuSEfirewall2 Actual Results: After manually altering the first entry, subsequent entries seem to have the correct number of arguments. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=829706 https://bugzilla.novell.com/show_bug.cgi?id=829706#c Ye Yuan <yyuan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@suse.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=829706 https://bugzilla.novell.com/show_bug.cgi?id=829706#c1 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |locilka@suse.com --- Comment #1 from Thomas Fehr <fehr@suse.com> 2013-07-17 09:13:26 UTC --- Reassigned to maintainer of yast2-firewall -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=829706 https://bugzilla.novell.com/show_bug.cgi?id=829706#c2 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |lnussel@suse.com --- Comment #2 from Lukas Ocilka <locilka@suse.com> 2013-07-18 10:04:42 UTC --- Sounds like to format of FW_FORWARD_MASQ. I've never seen such issue before and this piece of code hasn't been changed for years. Maybe it was just incorrectly coded and nobody used that ever. Ludwig, any hints? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=829706 https://bugzilla.novell.com/show_bug.cgi?id=829706#c3 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|lnussel@suse.com | --- Comment #3 from Lukas Ocilka <locilka@suse.com> 2013-07-24 09:15:31 UTC --- Found out the cause: There is a "Requested IP" entry that you should leave empty instead of using "*" there. Firewall needs to be fixed to - state that this entry is optional - check that whatever is entered there is an IP(4/6) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=829706 https://bugzilla.novell.com/show_bug.cgi?id=829706#c4 --- Comment #4 from Lukas Ocilka <locilka@suse.com> 2013-08-02 13:02:38 UTC --- Fixed in yast2-firewall-2.24.2 It will appear in Factory in yast2-firewall-3.0.0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=829706 https://bugzilla.novell.com/show_bug.cgi?id=829706#c5 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #5 from Lukas Ocilka <locilka@suse.com> 2013-08-02 13:03:00 UTC --- According to comment(s) above: Fixed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com