Skip to content

IPv6 tempaddr and RA does not work anymore #348

@alphanet72

Description

@alphanet72

Operating System

Debian GNU/Linux 11.0

Kathará Version

3.7.8

Bug Description

It is no longer possible to specify some sysctl pertaining to specific ifaces of machines in lab.conf.

For example:

Privacy Extensions

pc2[sysctl]="net.ipv6.conf.eth0.use_tempaddr=2"

fails with:
result: CRITICAL (APIError) 500 Server Error for
http+docker://localhost/v1.48/containers/create?name=kathara_schaefer-g
7n5o3v4zlyft1rvnxiw_pc2_UF77bGPn6UDWI1E28rGSHg: Internal Server Error
("interface specific sysctl setting "net.ipv6.conf.eth0.use_tempaddr"
must be supplied using driver option
'com.docker.network.endpoint.sysctls'")

I would guess this behaviour started either with the kathara image pushed two months ago or with recent docker-ce.

In addition, if replacing the above by conf.default and conf.all, it does not work either. In addition, it does not seem the machines use the Router Advertisement anymore.

On an older setup created a few months ago, it works like a charm (both tempaddr and Router Advertisement):

Current Manager is: Docker (Kathara)
Manager version is: 27.5.1
Python version is: 3.11.11 (main, Dec 4 2024, 08:55:08) [GCC
9.4.0]
Kathara version is: 3.7.8
Operating System version is: Linux-5.10.0-33-amd64-x86_64

PS: is there somewhere an archive of all kathara/base docker images? However here, a Docker version could be the problem.

Steps To Reproduce

/kathara/labos/ipv6$ dpkg -s docker-ce-cli | grep Version
Version: 5:28.0.1-1debian.11bullseye

Put
pc2[sysctl]="net.ipv6.conf.eth0.use_tempaddr=2" in lab.conf

result: CRITICAL (APIError) 500 Server Error for
http+docker://localhost/v1.48/containers/create?name=kathara_schaefer-g
7n5o3v4zlyft1rvnxiw_pc2_UF77bGPn6UDWI1E28rGSHg: Internal Server Error
("interface specific sysctl setting "net.ipv6.conf.eth0.use_tempaddr"
must be supplied using driver option
'com.docker.network.endpoint.sysctls'")

It however works with s/eth0/all/, and adding .default.- too, but then there is an issue with RA messages not being handled upon (no public address is obtained).

Is it maybe linked to the bug you had that Docker was starting ifaces too late for Kathara to be able to act on them?

Expected Behavior

ability to set tempaddr=2
RA working

Check Command Output

$ kathara check
┌──────────────────────────────────────────────────────────────────────────────┐
│                                 System Check                                 │
└──────────────────────────────────────────────────────────────────────────────┘
Current Manager is:             Docker (Kathara)
Manager version is:             28.0.1
Python version is:              3.11.11 (main, Dec  4 2024, 08:55:08) [GCC 
9.4.0]
Kathara version is:             3.7.8
Operating System version is:    Linux-5.10.0-34-amd64-x86_64
[Deploying devices]   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1/1
[Deleting devices]   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1/1
✓ Container run successfully.

Metadata

Metadata

Labels

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions