Or does it need a service or systemd to bring it up every boot? I want to manufacture, while learning, a whole NIC schematic virtually in my host to route packets with purpose and host some services on different internal IPs for sake of tracing packets and an IPS involved.
Is a dummy device reloaded on boot if created with ip link add device type dummy
? I know I need also to modprobe dummy
along with that but how to set that at boot too?
Such as I want to use nginx to reverse proxy from my static WAN IP to all the desired services on differing IPs and set in the services running them that that NIC is that's IP.. If using a dummy device will (for example) prosody xmpp server bring it up on it's own on it's reserved and configured IP address? I am using Debian 10 server and Arch Linux desktop.
dummy
, but fortun
ortap
interfaces, and they can be created and set up like you set up your "regular" interfaces. Actually, this even more sounds like a use case for Linux (network) namespaces; are you aware ofpodman
ordocker
?podman
or docker. (I prefer podman, no strange daemons, they have separate "pods" as concept, which really means "a shared network between these few containers" and you can export the whole network and container setup into a systemd service script, which you can have automatically run at boot. Docker on the other hand is older, more popular, and "strange daemon" also means "starts automatically and sets up the things you've configured".)