Pit

The CI-failures seem to be unrelated to this PR. Apparently it tries to build a version of lazy-static which the minimum supported version of Rust, 1.13.0, doesn‘t compile. It seems...

@cybermcm I just released 1.2.0-rc.5 (which you'll be able to retrieve via Docker Hub under `pitkley/dfw:1.2.0-rc.5` once it is done building). Maybe you can retest your use-case? :slightly_smiling_face: If your...

@cybermcm hm, while I can't directly confirm the DNS-issue, I can see that outgoing traffic overall seems to be a bit wonky. Sorry that I didn't catch that. I'll reopen...

@cybermcm just for your information: I have reverted the change and created `rc.6` (which is effectively identical to `rc.4`). For the time being the required workaround is to publish the...

Note: iptables can match `-m addrtype --dst-type local` where `local` identifies "destinations [...] assigned to this host". nftables seems [to have `fib`](https://wiki.nftables.org/wiki-nftables/index.php/Routing_information#fib) (with kernel >=4.10), which supposedly does the same...

Hi @airman604, thank you for reaching out! I have debugged your issue and identified that this is in an incompatibility between the library DFW uses to communicate with Docker, [shiplift](https://github.com/softprops/shiplift),...

bors r+

The reason this is happening is that DFW is setting up a rule that will allow related and already established traffic to flow unimpeded, regardless of whether there is any...

Hi @xepa, thank you for reaching out. I had never really thought about the use case of NATting traffic from the host itself to a container, mostly because I probably...

LDAP-support was included with PR #18, which was merged into the [`ldap` branch](https://github.com/pitkley/docker-netbox/tree/ldap) and for which the [Docker hub image/tag `pitkley/netbox:ldap`](https://hub.docker.com/r/pitkley/netbox/tags) exists. Looking at the [Netbox documentation regarding LDAP](https://netbox.readthedocs.io/en/stable/installation/4-ldap/#configuration), a...