IPv6 checking virtual server instead of real server

0

I have a lightly used guinea pig server configured and working with ipv4, but when I add an ipv6 virtual server and associated real server in direct return mode (as are the ipv4 servers), network captures show that it is doing a neighbor discovery for the virtual ipv6 address, not the real server ipv6 address. Since ND has to be disabled for the virtual addresses on the real servers for direct return to work properly, this fails, and the real server is marked down.

  • 19:31 is the kemp
  • 17:79 is the virtual server address
  • 17:91 is the real server address
<mailproxy-lb-01.peak.org> [248] # tshark -n -i eth0 host 2607:f678::19:31
Running as user "root" and group "root". This could be dangerous.
Capturing on eth0
0.000000000 2607:f678::19:31 -> ff02::1      ICMPv6 78 Neighbor Advertisement 2607:f678::19:31 (none)
1.575886430 2607:f678::19:31 -> ff02::1      ICMPv6 78 Neighbor Advertisement 2607:f678::19:31 (none)
342.333085088 2607:f678::19:31 -> ff02::1      ICMPv6 78 Neighbor Advertisement 2607:f678::19:31 (none)
343.082425822 2607:f678::19:31 -> ff02::1:ff17:79 ICMPv6 86 Neighbor Solicitation for 2607:f678::17:79 from 00:50:56:8c:45:b0
344.106352097 2607:f678::19:31 -> ff02::1:ff17:79 ICMPv6 86 Neighbor Solicitation for 2607:f678::17:79 from 00:50:56:8c:45:b0
345.130354625 2607:f678::19:31 -> ff02::1:ff17:79 ICMPv6 86 Neighbor Solicitation for 2607:f678::17:79 from 00:50:56:8c:45:b0
347.054705555 2607:f678::19:31 -> ff02::1      ICMPv6 78 Neighbor Advertisement 2607:f678::19:31 (none)
425.130553433 2607:f678::19:31 -> ff02::1      ICMPv6 78 Neighbor Advertisement 2607:f678::19:31 (none)
^C8 packets captured

 

2 comments

Avatar
0
Tony Vaughan

Hi Alan,

my colleague was testing another scenario with IPv6 and came across something similar,
in his test, he had the loopback adapter set correctly on the real server but on the LoadMaster configuration the real servers was added as NAT not DSR

Avatar
0
alan.batie

Mine is in DSR mode: