LXC to LXC communication, firewall rules do not apply?

[Percy]

JUst finished setting up my firewall rules and i have everything working the way i want when testing from clients on the physical networks.

However it would seem that the firewall rules specified on a container does not apply when another container on the same host communicates.

Example:
I have a container running samba with file sharing, this has an IP on the network.
Another container is running Plex Media Server and is set up with another IP. Plex has all media stored on the file share served by the first container.

However, the container running samba has rule set up so that all traffic is dropped unless coming from a specified ip (my testing workstation for now). If that rule does not pass traffic is dropped. Disabling the rule does indeed drop traffic from my workstation.

However it would seem that my plex server has no issues accessing files on the network from the fileshare even though it has another IP.

I suspect this might be by design, but nonetheless - How do i control the "network traffic" between my containers on the same host?

 

[Alwin]

Well, it depends at which point you added the rules. If they are not on the firewall on the container, then try to place them there.

 

[Percy]

Indeed! Applying the firewall rule on the node does work, but you have to restart all the containers (or at least i had to).

Thanks!

 

[Alwin]

Indeed! Applying the firewall rule on the node does work, but you have to restart all the containers (or at least i had to).

Thanks!

When a firewall rule is created, we add a separate bridge to apply the rules to and the interfaces of CT/VM have to be reassigned to the new bridge. Best option is to shutdown and start the CT/VM to be sure.