BGP not establishing between devices when running locally in Ubuntu/wsl environment. Md5 protocol not supported

[joshniec]

Just wanted to document an issue I had with spinning up the lab - when first initializing the lab with sudo make start and logging into nodes with ssh admin@HOSTNAME, I noticed that bgp was not establishing even though there was layer 3 connectivity between the nodes.

During my troubleshooting I checked the Bgp-main$PID.qt file and noticed the following logs:

2024-11-03 18:38:49.041067 8 00640.858115666, +12601594621 "Set Md5Auth: sd=531 192.168.0.32/32"
2024-11-03 18:38:49.041071 2 00640.858118896, +11038 "Md5Auth error: Protocol not available"
2024-11-03 18:38:50.737427 8 00642.554475108, +5797179986 "Set Md5Auth: sd=532 192.0.0.1/32"
2024-11-03 18:38:50.737431 2 00642.554479483, +14950 "Md5Auth error: Protocol not available"
2024-11-03 18:38:59.041967 8 00650.859015233, +28380176335 "Set Md5Auth: sd=531 192.168.0.32/32"
2024-11-03 18:38:59.041972 2 00650.859020338, +17446 "Md5Auth error: Protocol not available"
2024-11-03 18:39:00.737708 8 00652.554756022, +5795059373 "Set Md5Auth: sd=532 192.0.0.1/32"
2024-11-03 18:39:00.737711 2 00652.554758971, +10077 "Md5Auth error: Protocol not available"
2024-11-03 18:39:09.042943 8 00660.859991168, +28382556398 "Set Md5Auth: sd=531 192.168.0.32/32"
2024-11-03 18:39:09.042947 2 00660.859995065, +13318 "Md5Auth error: Protocol not available"
2024-11-03 18:39:10.737984 8 00662.555032376, +5792672730 "Set Md5Auth: sd=532 192.0.0.1/32"
2024-11-03 18:39:10.737987 2 00662.555035582, +10956 "Md5Auth error: Protocol not available"

I then stopped the lab (sudo make stop), and cd'd into $ROOT/labs/techlib-vxlan-domain-a/clab/init-configs and ran

sed -i '/neighbor.*password/d' *cfg

This removed the neighbor password statement for all the peer groups.

I re-started the lab with sudo make start and then all my BGP sessions came up.

Thanks,

[ankudinov]

@joshniec I assume that you are running that on Docker desktop? Recent Docker Desktop is using Linuxkit 6.10 with CONFIG_TCP_MD5SIG disabled in kernel. The easiest fix for that right now is switching to Podman Desktop.
I'll close this issue once we add it to known issues in docs.

[joshniec]

I was using WSL, but I was not using docker desktop, I was using native docker within WSL (there are some issues with container lab and WSL, see https://containerlab.dev/windows/, when trying to use regular docker desktop, the docker network doesn't work and you cannot establish network connectivity between nodes in the topology).

Thanks! I just wanted to document this here incase other windows users ran into issues