Bug 24497 – Allow VNC over IPv6

Bug 24497 - Allow VNC over IPv6


Summary:	Allow VNC over IPv6

Status:	CLOSED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Virtualization - UVMM
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-11-10 11:20 CET by Sönke Schwardt-Krummrich
Modified:	2023-06-28 10:46 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	IPv6
Max CVSS v3 score:

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 Sönke Schwardt-Krummrich

2011-11-10 11:20:17 CET

So wie es aussieht, nimmt unsere Virtualisierung VNC-Verbindungen aktuell nur über IPv4 an:

<graphics autoport="yes" keymap="de" port="-1" type="vnc">
  <listen address="0.0.0.0" type="address" />

Es sollte geprüft werden, ob man das dauerhaft bzw. manuell auf IPv6-Sockets ändern kann.

Comment 1 Philipp Hahn

2017-05-02 14:57:13 CEST

'0.0.0.0' is hard-coded in several locations; using '::' instead would allow listening on both IPv4 and IPv6.

Current libvirt only allows to configure one address:
 <https://bugzilla.redhat.com/show_bug.cgi?id=1038963>

Comment 2 Ingo Steuwer

2020-07-03 20:51:33 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.