VRRP and dual-stack
Damien Clabaut <[email protected]>
| Newsgroups | gmane.linux.keepalived.devel |
|---|---|
| Message-ID | <[email protected]> |
Hello,
I am trying to setup VRRP on dual-stack (IPv4 + IPv6 on the same vlan).
I am using Keepalived 1.2.23 on debian 7.11 (kernel 3.18.11).
To be compatible with Cisco devices (which I do not use in this specific
case but will use in production), I use VRRPv2 for IPv4 and VRRPv3 for
IPv6. Thus, my configuration looks like this:
global_defs {
}
vrrp_instance 61100 {
version 3
native_ipv6
state BACKUP
interface bond0.1100
use_vmac vrrp.35100.1
virtual_router_id 1
priority 150
advert_int 1
virtual_ipaddress {
fe80:b100::1/64
2001:41d0:b100::1/128
}
}
vrrp_instance 41100 {
interface bond0.1100
use_vmac vrrp.35100.1
virtual_router_id 1
priority 100
advert_int 1
authentication {
auth_type PASS
auth_pass kpl35100
}
virtual_ipaddress {
10.242.100.254/32
}
mcast_src_ip 10.242.100.254
unicast_src_ip 10.242.100.254
}
Configuration is identical on peer router except the priorities are
opposite (100 for IPv6 and 150 for IPv4).
The machine named bz-perflab-5-vr is master on IPv6, bz-perflab-2-vr is
master on IPv4.
When loading / reloading the configuration, I get these logs:
Nov 14 16:39:25 bz-perflab-5-vr Keepalived_vrrp[10024]:
VRRP_Instance(61100) Transition to MASTER STATE
Nov 14 16:39:26 bz-perflab-5-vr Keepalived_vrrp[10024]:
VRRP_Instance(61100) Entering MASTER STATE
Nov 14 16:39:26 bz-perflab-5-vr Keepalived_vrrp[10024]:
VRRP_Instance(61100) using locally configured advertisement interval
(1000 milli-sec)
Nov 14 16:39:26 bz-perflab-5-vr Keepalived_vrrp[10024]: Netlink: error:
Permission denied, type=(20), seq=1479137970, pid=0
Nov 14 16:39:26 bz-perflab-5-vr Keepalived_vrrp[10024]:
2001:41d0:b100::1 has a prefix length of 128, setting preferred_lft to 0
Nov 14 16:39:26 bz-perflab-5-vr Keepalived_vrrp[10024]: Netlink: error:
Permission denied, type=(20), seq=1479137971, pid=0
In which case bz-perflab-2-vr gets the VIPv4 but none of the routers get
the VIPv6.
Each router also gets its link-local address (same as underlying VLAN
interface bond0.1100).
If I reload keepalived again on bz-perflab-5-vr, then I get the same
logs, and all IP addresses are removed from the VRRP interface (even
link-local). And bz-perflab-2-vr gets both the VIPv4 and the VIPv6.
Is this a known issue ? Am I doing anything wrong ?
Regards,
--
Damien Clabaut
Network Engineer
OVH.pl
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Keepalived-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/keepalived-devel
signature.asc
(application/pgp-signature, 836 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJYKd5PAAoJEH4l99mSZky/POkP/RsjbRsU8HPXBjb7iju02xFL ChFEYZOzP6gxSZOJC08PTAb0XfkRTpMappEspz4Kg1BQ/N/MdMZ5qNUCr/CB3Ybc vG8dxVYC60dyM9dLFMOlYe2JibV22aCtRjN+epXBMYM1rOy+KEJN+FOZhLpkbmzM ilKh7zu1HBR7oIvUaA7G5vjwjiPI6ybWj0+wJw2acJcx7/SM3HZ7Bh72zSZdLuQn VgUZufB968TjO2VUv3YFHz+4PwV9SxxGVZ0QsImMC+ej6pAfkjTdWOg8UsK8asrs /QgIajWY343h3Gw95AXUJb8P3+xlPK5P5wFjCq1qZNJUUh+tYSRZ1i7NWAWxTtem GGS7Ot4JierqLGW7B6itl0P1wdEgs/Jdk+yNkC/qcH3NMY0p5KGjLKqw0p0k+Ssr Bgcg5cSM9Z15BGynOsj/4xmA1gnmRddDoPTbqFm+g1qVQorl6wagJ/McaYlq0qqp pkgukXF84WGambriSyfSzCDcUr5aVC/YWKQdmOCfah6guaQYHAqzoUNIFwK4IbcK vNTo0GjquBE3HKDiOAj6bhZlX0GKMMgTtUxYxJyCjfL/fzNpmLLktKGEcFLYeNff FoTX2A4r+LZ5ox0gimWSQYhB4sA8gqCqKLLx/OT2U+JWNxjXd7LzsKAA6ycxcYZ7 owZ4UYqprP6BmfXnKT8W =JdWG -----END PGP SIGNATURE-----