is it possible to remove external network manipulation?

[towc]

I've been trying to create a dockerized AP for a while, in a way that can fit a docker-compose workflow. I didn't get anywhere close, without ssh-ing into the host or mounting just about everything, but your approach seems promising.

It was trivial to fill the templates from within the container and similar, but I can't seem to be able to configure the networking completely from within the container (and docker-cli arguments / docker-compose.yml params)

I'm trying on arm.

Do you think this is even possible? It would be great to have an example of that somewhere on the web

[fgg89]

Hi @towc;

DockerAP already configures the minimum network related config such as IP forwarding, masquerading, etc. Could you please provide more details about what you're trying to achieve?

Thanks!

[towc]

Hi, thanks for your time

DockerAP still uses external scripts to link a netns-ed network to the container's. Is there a way to avoid that?

What I'm trying to achieve is being able to do docker-compose up hotspot and the AP would be up, then when I bring the container down, the AP would go down with it, without external scripts

[fgg89]

Hi @towc

I believe a systemd script would better suit your purposes, right? It would call the docker_ap script with the necessary arguments and you would have the functionality integrated as a service and hence be able to start/stop it as you want.

If you need one let me know and I'll try to add it shortly.

Regards.