[jboss-jira] [JBoss JIRA] Commented: (JGRP-544) IPv6: mcast_addr needs to be defined with backslashes
Bela Ban (JIRA)
jira-events at lists.jboss.org
Tue Jul 3 08:28:07 EDT 2007
[ http://jira.jboss.com/jira/browse/JGRP-544?page=comments#action_12367532 ]
Bela Ban commented on JGRP-544:
-------------------------------
Fixed, waiting for testsuite to pass until resolving it.
Now backslashes are not needed for protocol attribute values, e.g. to define an IPv6 mcast_addr, the following works:
<UDP mcast_addr="ff18:eb72:479f::2:3" mcast_port="2553" ... />
The colons in mcast_addr do not need to be escaped with a backslash any longer. Note that '(', ')' and '=' are still reserved characters and cannot be used as part of an attribute name or value.
> IPv6: mcast_addr needs to be defined with backslashes
> -----------------------------------------------------
>
> Key: JGRP-544
> URL: http://jira.jboss.com/jira/browse/JGRP-544
> Project: JGroups
> Issue Type: Task
> Reporter: Bela Ban
> Assigned To: Bela Ban
> Priority: Minor
> Fix For: 2.5
>
>
> - Investigate use of IPv6 in a non-dual stack environment (only IPv6 stack available): an mcast_addr like "228.8.8.8" is not recognized then
> - mcast_addr needs to be IPv6 and escaped with back slashes, e.g. "mcast_addr=ff18\:eb72\:479f\:\:2\:3". Change parsing for mcast_addr and bind_addr so we don't need backslashes
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list