aboutgitcodebugslistschat
path: root/tcp_vu.c
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2024-11-06 12:44:15 +1100
committerStefano Brivio <sbrivio@redhat.com>2024-11-07 12:47:37 +0100
commit9a0e544f05bf93609921f988b22f0680e143b4ad (patch)
treeb925e10cf2fdf63182b22907eb6337eef0a12f6d /tcp_vu.c
parent910f4f91030141b7e2e65644dc9fe678cc57f640 (diff)
downloadpasst-9a0e544f05bf93609921f988b22f0680e143b4ad.tar
passt-9a0e544f05bf93609921f988b22f0680e143b4ad.tar.gz
passt-9a0e544f05bf93609921f988b22f0680e143b4ad.tar.bz2
passt-9a0e544f05bf93609921f988b22f0680e143b4ad.tar.lz
passt-9a0e544f05bf93609921f988b22f0680e143b4ad.tar.xz
passt-9a0e544f05bf93609921f988b22f0680e143b4ad.tar.zst
passt-9a0e544f05bf93609921f988b22f0680e143b4ad.zip
test: Improve test for NDP assigned prefix
In the NDP tests we search explicitly for a guest address with prefix length 64. AFAICT this is an attempt to specifically find the SLAAC assigned address, rather than something assigned by other means. We can do that more explicitly by checking for .protocol == "kernel_ra". however. The SLAAC prefixes we assigned *will* always be 64-bit, that's hard-coded into our NDP implementation. RFC4862 doesn't really allow anything else since the interface identifiers for an Ethernet-like link are 64-bits. Let's actually verify that, rather than just assuming it, by extracting the prefix length assigned in the guest and checking it as well. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'tcp_vu.c')
0 files changed, 0 insertions, 0 deletions