Markus Vahlenkamp

PR exists: https://github.com/srl-labs/containerlab/pull/1453

Does it make sense to at least have a $self reference for the containerlab binary? Otherwise if someone does not stick to the installer or uses a private build, the...

How do we now go about this? We have the https://containerlab.dev/rn/0.44/#link-impairments via `tools netem` command but thats not declaritive. So how to go about it? Close this issue or what...

I can not confirm this. The message `Creating lab directory: ...` is expected, we call the os.MakeAll functions, that takes a path and creates all the dirs along the path...

Hmm @hellt whats our definition of a startup-config? Is that the if no config already exists startup-config or is it the always and in any case startup-config?

ok, if a config is present in the nodes lab dir we should use that, if not e.g. --reconfigure we should download. I'll figure out how we do that best

Yes and the note says so... We do have the enforce-startup-config flag otherwise... This behavior got screwed when I implemented the http(s) download of the config... Mea culpa. Will fix...

should also contain "fortios" as the kind name.

Passthru: allows a single VM to be connected directly to the physical interface. I don't think this is what we want?! I exposed the `mode` in the extensive version of...

> **ADD1** as @steiler found, the registration part is missing -- example https://github.com/srl-labs/containerlab/blob/main/nodes/checkpoint_cloudguard/checkpoint_cloudguard.go#L21 This is where it would need to go. https://github.com/srl-labs/containerlab/blob/main/clab/register.go Add the import and call Register