Integration bypassing Docker networking ?!?

[thefunkygibbon]

Not sure where to go with this one to be honest.
I see that this integration is no longer being maintained. so likely not going to get much in terms of answers here.

anyway, I'll post it here anyway in the hope that someone might point me in the right direction.

So looking at my firewall logs, I am seeing a bunch of dropped traffic (due to anti-spoofing) which appear to come from the private docker bridge network which is on the same docker bridge as dozens of other containers. lots of the other containers also access the internet but I do not see anything in the firewall logs for those, only really just this one container (which by all accounts appears to be working ok)

Looking at the destination address for the majority of the dropped packets is 154.51.163.100 which , googling that IP address shows that its something to do with hildebrand. hence me looking here as the first port of call.

Any ideas on this? Why would a specific integration within HA within a docker container somehow bypass the standard NAT'ing of the docker networking bridge????