RDS: Can RDS sockets from different network namespace bind to the same address?

Hi,

(Resend this email in plain text in case the previous one was spammed. Sorry for the trouble caused.)

I am writing to ask about if two RDS sockets from different network namespaces can bind to the same address.

I am doing research on container security. Recently our tool produced a simple test case with confusing test result: there are two network namespaces A and B. Both A and B has a tun device, and these two tun devices have the same IPv4 address. In namespace A a RDS socket is created and binds it to namespace A's tun device. It works. But then in namespace B the other RDS socket is created and binds it to namespace B's tun device, it fails with error code EADDRINUSE. Is this considered as expected behavior? 


Thanks,
Congyu

+mark

On 16 Dec 2021, at 02:32, Liu, Congyu [off-list ref] wrote:

Hi,

(Resend this email in plain text in case the previous one was spammed. Sorry for the trouble caused.)

I am writing to ask about if two RDS sockets from different network namespaces can bind to the same address.

I am doing research on container security. Recently our tool produced a simple test case with confusing test result: there are two network namespaces A and B. Both A and B has a tun device, and these two tun devices have the same IPv4 address. In namespace A a RDS socket is created and binds it to namespace A's tun device. It works. But then in namespace B the other RDS socket is created and binds it to namespace B's tun device, it fails with error code EADDRINUSE. Is this considered as expected behavior? 


Thanks,
Congyu