[Bug 547309] New: VPN ports cannot be opened when enabling remote management (VNC) during installation
http://bugzilla.novell.com/show_bug.cgi?id=547309
Summary: VPN ports cannot be opened when enabling remote management (VNC) during installation Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 8 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: nice@titanic.nyme.hu QAContact: jsrain@novell.com Found By: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; hu-HU; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-2.1 Firefox/3.5.3
The nework services section is unable to open the firewall ports until network interfaces aren't assigned to any firewall zone (i.e. during installation). I either have to open VPN ports manually in the firewall section of YaST, or I have to assign the ports before trying to open VPN ports from the network services section of YaST.
Reproducible: Always
Steps to Reproduce: 1. Start openSUSE 11.2 installation 2. Try to enable remote management on the main settings screen
http://bugzilla.novell.com/show_bug.cgi?id=547309
zhu rensheng rszhu@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rszhu@novell.com AssignedTo|bnc-team-screening@forge.pr |mzugec@novell.com |ovo.novell.com |
http://bugzilla.novell.com/show_bug.cgi?id=547309
User kmachalkova@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=547309#c1
Katarina Machalkova kmachalkova@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nice@titanic.nyme.hu
--- Comment #1 from Katarina Machalkova kmachalkova@novell.com 2009-10-16 02:24:23 MDT --- *confused* How is VPN service related to VNC (remote management)? These are two distinct services, aren't they? Further, it is somehow reasonable that you have to go to firewall configuration if you want to punch a hole in firewall.
Please clarify, what is it exactly that you would expect. Is it something like "enabling remote administration (VNC) should also open VPN ports in firewall"?
http://bugzilla.novell.com/show_bug.cgi?id=547309
User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=547309#c2
Tamás Németh nice@titanic.nyme.hu changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|VPN ports cannot be opened |VNC ports cannot be opened |when enabling remote |when enabling remote |management (VNC) during |management during |installation |installation
--- Comment #2 from Tamás Németh nice@titanic.nyme.hu 2009-10-16 02:44:33 MDT --- Sorry, that was a typo :)
It's not related to VPN. It's only about VNC.
http://bugzilla.novell.com/show_bug.cgi?id=547309
User kmachalkova@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=547309#c3
--- Comment #3 from Katarina Machalkova kmachalkova@novell.com 2009-10-16 02:49:45 MDT --- I see. Did you choose to use NetworkManager?
http://bugzilla.novell.com/show_bug.cgi?id=547309
User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=547309#c4
Tamás Németh nice@titanic.nyme.hu changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu |
--- Comment #4 from Tamás Németh nice@titanic.nyme.hu 2009-10-16 03:26:36 MDT --- (In reply to comment #3)
I see. Did you choose to use NetworkManager?
Yes.
http://bugzilla.novell.com/show_bug.cgi?id=547309
User mzugec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=547309#c5
Michal Zugec mzugec@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nice@titanic.nyme.hu
--- Comment #5 from Michal Zugec mzugec@novell.com 2009-10-20 07:29:06 MDT --- But it should work by default: - on my machine, all devices are configured with dhcp and assigned to external firewall zone
What's proposal on your machine? Please attach also yast logs
http://bugzilla.novell.com/show_bug.cgi?id=547309
User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=547309#c6
Tamás Németh nice@titanic.nyme.hu changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu |
--- Comment #6 from Tamás Németh nice@titanic.nyme.hu 2009-10-20 13:14:47 MDT --- Created an attachment (id=323314) --> (http://bugzilla.novell.com/attachment.cgi?id=323314) YaST logs
When selecting a zone for the interfaces, the machine's first proposal was external, indeed. But during the installation, the cards had no zone (I used NetworkManager configuration).
http://bugzilla.novell.com/show_bug.cgi?id=547309
User mzugec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=547309#c7
Michal Zugec mzugec@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nice@titanic.nyme.hu
--- Comment #7 from Michal Zugec mzugec@novell.com 2009-10-21 07:26:58 MDT --- Still couldn't reproduce. Also in your log it seems that each interface is associated to external zone ("FW_DEV_EXT":"eth0 wlan0") all the time. Please explain "during the installation, the cards had no zone" - when and how you discovered this?
http://bugzilla.novell.com/show_bug.cgi?id=547309
User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=547309#c8
Tamás Németh nice@titanic.nyme.hu changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu |
--- Comment #8 from Tamás Németh nice@titanic.nyme.hu 2009-10-21 07:40:08 MDT --- (In reply to comment #7)
Still couldn't reproduce. Also in your log it seems that each interface is associated to external zone ("FW_DEV_EXT":"eth0 wlan0") all the time. Please explain "during the installation, the cards had no zone" - when and how you discovered this?
During the installation (before the first normal startup when kdm appears) there is a point when you can enable VNP remote management. Start to install openSUSE 11.2 RC1 into VirtualBox or something like that, and configure it to use NetworkManager instead of ifup/ifdown.
http://bugzilla.novell.com/show_bug.cgi?id=547309
User mzugec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=547309#c9
Michal Zugec mzugec@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nice@titanic.nyme.hu
--- Comment #9 from Michal Zugec mzugec@novell.com 2009-10-21 07:55:36 MDT --- Yes, I did it the same way (without sucess to found reported problem). Did you found that interfaces are not assigned to any zone in Network Dialog or later? On my side proposed interfaces are assigned to EXT zone by default no matter if it's ifup or NM
http://bugzilla.novell.com/show_bug.cgi?id=547309
User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=547309#c10
Tamás Németh nice@titanic.nyme.hu changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu |
--- Comment #10 from Tamás Németh nice@titanic.nyme.hu 2009-10-26 11:37:37 MDT --- (In reply to comment #9)
Yes, I did it the same way (without sucess to found reported problem). Did you found that interfaces are not assigned to any zone in Network Dialog or later? On my side proposed interfaces are assigned to EXT zone by default no matter if it's ifup or NM
Sorry, I've tried to reproduce it during installing RC1, but I was unable. Maybe it's fixed. We can close this report, I will reopen if necessary.
http://bugzilla.novell.com/show_bug.cgi?id=547309
User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=547309#c11
Tamás Németh nice@titanic.nyme.hu changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME
--- Comment #11 from Tamás Németh nice@titanic.nyme.hu 2009-10-26 11:38:18 MDT --- Maybe fixed?
http://bugzilla.novell.com/show_bug.cgi?id=547309
User mzugec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=547309#c12
--- Comment #12 from Michal Zugec mzugec@novell.com 2009-10-27 02:03:22 MDT --- Sometimes it happend ;-)
http://bugzilla.novell.com/show_bug.cgi?id=547309
http://bugzilla.novell.com/show_bug.cgi?id=547309#c13
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |malv_star@hotmail.com
--- Comment #13 from Malvern Star malv_star@hotmail.com 2010-03-27 15:57:05 UTC --- For what it's worth, I have the same problem. I'll test against 11.3M4 and update if necessary.
http://bugzilla.novell.com/show_bug.cgi?id=547309
http://bugzilla.novell.com/show_bug.cgi?id=547309#c14
--- Comment #14 from Malvern Star malv_star@hotmail.com 2010-04-15 14:00:32 UTC --- Created an attachment (id=354675) --> (http://bugzilla.novell.com/attachment.cgi?id=354675) YaST2 Logs For Malvern Star
YaST2 installation logs.
http://bugzilla.novell.com/show_bug.cgi?id=547309
http://bugzilla.novell.com/show_bug.cgi?id=547309#c15
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Version|Milestone 8 |Milestone 5 Component|YaST2 |YaST2 Platform|Other |PC AssignedTo|mzugec@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com Resolution|WORKSFORME | Product|openSUSE 11.2 |openSUSE 11.3 OS/Version|Other |openSUSE 11.3
--- Comment #15 from Malvern Star malv_star@hotmail.com 2010-04-15 14:01:38 UTC --- This problem is definitely still present in 11.3 Milestone 5. The network interface was not assigned to a firewall zone on installation. Attempting to enable VNC during install gave a message indicating that VNC could not be enabled because the firewall was not in a state that permitted it. Cancelling this and checking the default firewall zone for my interface showed the firewall as "disabled". Changing the interface to the external zone allowed me to then turn on the VNC service.
Attached are my YaST logs.
http://bugzilla.novell.com/show_bug.cgi?id=547309
http://bugzilla.novell.com/show_bug.cgi?id=547309#c
yang xiaoyu xyyang@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com |
http://bugzilla.novell.com/show_bug.cgi?id=547309
http://bugzilla.novell.com/show_bug.cgi?id=547309#c
Michael Calmer mc@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |mzugec@novell.com
http://bugzilla.novell.com/show_bug.cgi?id=547309
http://bugzilla.novell.com/show_bug.cgi?id=547309#c16
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 5 |Milestone 6
--- Comment #16 from Malvern Star malv_star@hotmail.com 2010-05-02 10:16:35 UTC --- Alright, the bug appears to now only occur if the user enabled SSH and opened firewall ports prior to the actual install phase (that is, at the install summary screen). Leaving these options alone prevents this problem from occurring later. Tested against openSuSE 11.3 Milestone 6.
http://bugzilla.novell.com/show_bug.cgi?id=547309
http://bugzilla.novell.com/show_bug.cgi?id=547309#c17
Michal Zugec mzugec@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW CC| |mzugec@novell.com AssignedTo|mzugec@novell.com |locilka@novell.com
--- Comment #17 from Michal Zugec mzugec@novell.com 2010-05-11 09:00:20 UTC --- This is because of new feature: simple network (in fact firewall) cfg in 1st stage - fate#303859 which doesn't work as expected - reported problem is caused by not running firewall. Reassigned to installation&firewall maintainer.
http://bugzilla.novell.com/show_bug.cgi?id=547309
http://bugzilla.novell.com/show_bug.cgi?id=547309#c18
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 6 |RC 2
--- Comment #18 from Malvern Star malv_star@hotmail.com 2010-07-05 13:40:57 UTC --- OK, I've confirmed the bug is still in RC2, and I can confirm that what triggers the problem is the user "enabling and opening ports" for SSH during the first phase of the install. As a result, the network interface is not assigned a zone during the second phase of the installation, and attempting to enable VNC produces an error. Manually setting the firewall zone at this time "fixes" the issue. Any chance of a fix prior to release? Otherwise, perhaps the SSH option should be removed from the installer.
http://bugzilla.novell.com/show_bug.cgi?id=547309
http://bugzilla.novell.com/show_bug.cgi?id=547309#c19
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|RC 2 |Final
--- Comment #19 from Malvern Star malv_star@hotmail.com 2010-08-07 08:47:04 UTC --- Bug is still in Final, but there has been a slight change. The firewall is now listed as "disabled" when editing the network interface. Changing the interface to "External Zone" on the Network Configuration screen and THEN enabling VNC works as expected. This problem has been in the last two openSuSE releases. It really should be fixed prior to the next release.
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c
Lukas Ocilka locilka@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c20
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |Installation Version|Final |Milestone 3 of 6 AssignedTo|locilka@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE 11.3 |openSUSE 11.4 OS/Version|openSUSE 11.3 |SuSE Other
--- Comment #20 from Malvern Star malv_star@hotmail.com 2010-11-18 16:34:17 UTC --- Tested against 11.4 Milestone 3. Bug is still present. Really hoping to get this sorted for 11.4 release, as it's been present in both 11.2 and 11.3.
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c21
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 3 of 6 |Milestone 4 of 6
--- Comment #21 from Malvern Star malv_star@hotmail.com 2010-12-13 12:52:35 UTC --- Same again for 11.4 Milestone 4. No progress as yet.
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c22
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 4 of 6 |Milestone 5 of 6
--- Comment #22 from Malvern Star malv_star@hotmail.com 2010-12-30 17:36:14 UTC --- Checked against 11.4 Milestone 5. Problem persists. Firewall is still set to "Disabled" for the network adapter if "Open and Enable" was selected for SSH during the first stage of install.
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c23
--- Comment #23 from Malvern Star malv_star@hotmail.com 2011-01-30 16:41:59 UTC --- This problem is *still* present in 11.4 Milestone 6. Suggested workaround: disable this install feature from appearing as a clickable option in the install summary since it does not work. Though a fix would be nice, it does not appear to be forthcoming.
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 5 of 6 |Milestone 6 of 6
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c24
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 6 of 6 |RC 1
--- Comment #24 from Malvern Star malv_star@hotmail.com 2011-02-22 16:21:28 UTC --- After testing with RC1, I have noticed another problem connected to the enabling of SSH during the first phase of install. Ignoring enabling VNC Remote Administration during the second phase, if the user completes the install, adapter eth0 is NOT ASSIGNED TO A FIREWALL ZONE. Surely this is of serious concern? It is not assigned to zone "external" as it normally would be, which appears to at least break DHCP when using the "ifup" method of connection (an address is not assigned unless the network is restarted from the command line). Surely this issue warrants more attention now?
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c
zj jia zjjia@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com |
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c25
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Installation Version|RC 1 |Milestone 2 AssignedTo|yast2-maintainers@suse.de |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE 11.4 |openSUSE 12.1 Target Milestone|--- |Milestone 3
--- Comment #25 from Malvern Star malv_star@hotmail.com 2011-07-20 08:35:04 UTC --- This bug is still present in openSUSE 12.1 Milestone 3. Why am I bothering? Nobody except me has commented on this bug in more than 12 months.
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c
zj jia zjjia@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |jsuchome@novell.com |ovo.novell.com |
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 2 |Milestone 3
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c27
Lukas Ocilka locilka@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |FIXED Target Milestone|Milestone 3 |Milestone 4
--- Comment #27 from Lukas Ocilka locilka@novell.com 2011-07-21 13:23:27 UTC --- - Fixed SuSEfirewall2 config library: By default any unassigned network interface is automatically assigned to the external firewall zone (bnc#547309). - Fixed CWM library for opening ports in firewall not to list any empty strings returned by network module, just interface names (bnc#547309).
- yast2.rpm in version 2.21.5
So, right now, every interface that is unassigned is automatically assigned to the external zone and ... YaST firewall (open-port-in-firewall) knows that.
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c28
--- Comment #28 from Malvern Star malv_star@hotmail.com 2011-07-21 17:04:55 UTC --- Thankyou Lukas! So I should test this against Milestone 4 when it comes out?
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c29
--- Comment #29 from Lukas Ocilka locilka@novell.com 2011-07-22 07:48:28 UTC --- Yes, please, if you could :) ;)
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c30
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Version|Milestone 3 |Milestone 5 Resolution|FIXED | Target Milestone|Milestone 4 |---
--- Comment #30 from Malvern Star malv_star@hotmail.com 2011-09-15 22:13:18 UTC --- Lukas, I tested your fix against 12.1 Milestone 5. It is now possible to open the requested ports during install, and the requested services (VNC, SSH) showed up as being allowed from the "External Zone" on first boot. However, I found that my network interface had "Firewall Disabled" showing during phase 2 of the installer, and "Automatically Assigned Zone" on first boot. I was not actually able to connect via VNC or SSH until I manually set my NIC to "External Zone".
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c31
Lukas Ocilka locilka@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |malv_star@hotmail.com
--- Comment #31 from Lukas Ocilka locilka@suse.com 2011-09-16 07:38:17 UTC --- I'll need your YaST logs, please.
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c32
--- Comment #32 from Malvern Star malv_star@hotmail.com 2011-09-27 19:55:12 UTC --- Created an attachment (id=453347) --> (http://bugzilla.novell.com/attachment.cgi?id=453347) First part of Yast2 Logs
OK Lukas, I'm attaching the YaST2 logs from a fresh install. Two files were generated. There is file y2log-1 which looks like it grew to a certain size so the system renamed it and continued in a fresh file. I've attached both, but I think the install log actually starts in the larger one.
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c33
Malvern Star malv_star@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|malv_star@hotmail.com |
--- Comment #33 from Malvern Star malv_star@hotmail.com 2011-09-27 19:58:35 UTC --- Created an attachment (id=453349) --> (http://bugzilla.novell.com/attachment.cgi?id=453349) Second part of Yast2 Logs
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c34
--- Comment #34 from Malvern Star malv_star@hotmail.com 2011-10-08 09:18:48 UTC --- Strange. Lukas, did you fix this prior to the release of Beta1? Because it seems to work correctly now. The firewall is set to "Automatically Assigned Zone" still, but I am able to connect remotely now.
Can anybody else confirm?
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c35
Lukas Ocilka locilka@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CLOSED Resolution| |FIXED
--- Comment #35 from Lukas Ocilka locilka@suse.com 2011-10-13 09:43:00 UTC --- So it must have been a different issue. Maybe with firewall itself. YaST is just a configuration tool, not the firewall itself.
If it works, it's fixed.
https://bugzilla.novell.com/show_bug.cgi?id=547309
https://bugzilla.novell.com/show_bug.cgi?id=547309#c36
--- Comment #36 from Malvern Star malv_star@hotmail.com 2011-11-07 07:26:17 UTC --- Lukas, I figured out what was going on and why I was unable to connect. Basically, network connectivity is fine during the second phase of install, but on first loading the desktop, this is no longer the case. A reboot solves this, and the network functions normally after that.
-
bugzilla_noreply＠novell.com