|
Bugzilla – Full Text Bug Listing |
| Summary: | VNC installation blocks itsself when setting up the firewall | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Christian Boltz <suse-beta> |
| Component: | Installation | Assignee: | Lukas Ocilka <locilka> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
... or it should start with VNC port enabled. |
I installed (fresh installation, no update) a machine using VNC with the following boot parameters: vnc=1 vncpassword=secret usessh=1 sshpassword=secret install=nfs://10.12.80.30/media/cdrom It worked until the release notes should be displayed - VNC was simply blocked. I realized that I had setup the firewall as active (default!) some seconds before. When calling rcSuSEfirewall stop VNC was working again and I could finish the installation. Conclusion: The firewall should start _after_ the VNC installation is complete ;-) You can find the y2logs at https://bugzilla.novell.com/attachment.cgi?id=56560