This was fixed in snv_114. Unfortunately, this is not yet available via
the dev repository, so for now, I'd go with the workaround of adding the
::1 address through zonecfg.
Regards,
Brian
Brian Ruthven - Solaris Network Sustaining - Sun UK wrote:
Replies inline
solarg wrote:
Brian
Replies inline
solarg wrote:
Brian Ruthven - Solaris Network Sustaining - Sun UK wrote:
Can you try plumbing in the ::1 interface in the zone please? I don't
recall whether this can be done with ifconfig plumb or not within an
NGZ or whether it is a zonecfg re-configuration which is needed.
hello all,
i have this problem into a zone in os2008.11 (b101)
This seems to be related to bug:
http://bugs.opensolaris.org/view_bug.do;jsessionid=2461d3b92d92e9e23ef6f8e8ee?bug_id=6732084
but this bug talks only solaris 10.
Anybody else has this problem?
thanks in advance,
gerard
That bug (or rather the bug it was closed as a duplicate of) is
technically S10-only because nevada (and hence opensolaris) plumbs in an
IPv6 interface by default.
Do you have the ::1 interface plumbed in and up? Something like this:
lo0:
