. (at least
it works for me)
Alternatively, as of 3.9.5, you can also use IPaddr2 for managing a
virtual IPv6 address, which is brand new and I would prefer this
because it uses the standard ip command.
Thanks,
2013/3/25 Nick Walke tubaguy50...@gmail.com:
This the correct place to report bugs
That works. Thanks!
Nick
On Mon, Mar 25, 2013 at 4:22 AM, Keisuke MORI keisuke.mori...@gmail.comwrote:
2013/3/25 Nick Walke tubaguy50...@gmail.com:
Looks like 3.9.2-5. So I need to statically assign the address I want to
use before using it with IPv6addr?
Yes.
On Mar 25, 2013 3:44
Thanks for the tip, however, it did not work. That's actually a /116. So
I put in 2600:3c00::0034:c007/116 and am getting the same error. I
requested that it restart the resource as well, just to make sure it wasn't
the previous error.
Nick
On Sun, Mar 24, 2013 at 3:55 AM, Thomas
I don't know what I'm doing wrong then. I copied exactly what you put in
and now I'm getting these errors:
ipv6test_start_0 (node=tek-lin-lb1, call=25, rc=1, status=complete):
unknown error
ipv6test_start_0 (node=tek-lin-lb2, call=20, rc=1, status=complete):
unknown error
Looking in my syslog I
From the first node:
nick@tek-lin-lb1:~$ sudo ip -6 addr add 2600:3c00::34:c007/116 dev eth0
nick@tek-lin-lb1:~$ sudo ip -6 addr show dev eth0
3: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000
inet6 2600:3c00::34:c007/116 scope global
valid_lft forever preferred_lft forever
This the correct place to report bugs?
https://github.com/ClusterLabs/resource-agents
Nick
On Sun, Mar 24, 2013 at 10:45 PM, Thomas Glanzmann tho...@glanzmann.dewrote:
Hello Nick,
I shouldn't be able to do that if the IPv6 module wasn't loaded,
correct?
that is correct. I tried
