God hasn't responded to a single one of my issues or merged a pull request since I started on this earth. Slacker.
starkzarn
joined 2 years ago
Great question, I've asked myself the same thing.
First, in my opinion they serve to achieve different things. While openwrt is a firewall, it'd a simple zone based firewall and it designed primarily as router firmware, not firewall software.
Opnsense is BSD based, openwrt is Linux based. Those both haves pros and cons. BSD has serious pedigree in the networking world. Juniper switches are still based on BSD even. Openwrt gets the Linux traffic shaping goodies like cake though.
I chose openwrt because it's more suited to my environment, where I have 10 VLANs, a 10G fiber core, and want IDS/IPS. Openwrt is meant to be lighter weight, but is less feature-full.
That's not how that works.
network_mode: host
shares the network namespace with the container host, so it doesn't do any NAT, it only exists on the host's IP. It would be akin to running a natively installed app, rather than in a container.macvlan
networking is what gives a container its own IP on the logical network, without the layer of NAT that the defaultbridge
mode networking that docker typically does.