[
https://issues.jboss.org/browse/AS7-3041?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-3041:
---------------------------------------
An interface binding configuration can include more than one criteria, including <nic
name="eth0"/> and a regular-expression based nic-match criteria. So users
wishing to avoid ambiguity should use that to make their choice explicit.
We'll look into having the address resolution algorithm fail if more than one possible
address matches the criteria.
IPv6: Invalid binding to IPv6 address when zone id identifier is
specified
--------------------------------------------------------------------------
Key: AS7-3041
URL:
https://issues.jboss.org/browse/AS7-3041
Project: Application Server 7
Issue Type: Bug
Components: Server
Affects Versions: 7.1.0.Beta1b
Reporter: Pavel Janousek
Assignee: Jason Greene
Priority: Blocker
AS7 binds incorrectly in several cases when IPv6 address setting includes _zone id_
identifier. For ex. _::1%lo_ produces correct binding at all (_::1:3528_ too), but
_fe80::200:ff:fe00:1%p2p1_ (link-local IPv6 address of network interface p2p1) produces
binding to _:::3528_ (it's an issue).
Warning: In multiple homed servers (= server with several physical network
interfaces/network cards) it is possible to have more than one network interface with the
*same* IPv6 address (compare it to IPv4 world where this case isn't possible) - IPv6
link local address is unique only on link and so the setting needs to include network
identifier (network interface name or its index) - every networked AS7 component has to
accommodate this setting and produces correct binding.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira