[rds-devel] [BUG] Confirmation on RDS Namespace Behavior
Santosh Shilimkar
santosh.shilimkar at oracle.com
Thu Dec 16 01:36:33 UTC 2021
> On Dec 14, 2021, at 7:18 PM, Liu, Congyu <liu3101 at purdue.edu> wrote:
>
> Hi,
>
> I am writing to ask about the behavior of rds socket binding behaviour in multiple network namespaces.
>
> In the test I recently performed there is a confusing case. Let's say 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 process creates a rds socket and binds it to namespace A's tun device. It works. But then in namespace B a process creates a rds socket and binds it to namespace B's tun device, it fails with error code EADDRINUSE. Is this the expected behavior?
>
> In other words, can rds sockets from different network namespaces bind to the same address?
>
Its not a BUG but missing RDS namespace support. There was some effort done to add network
namespace support but wasn’t completed and developer doing it moved on.
Regards,
Santosh
More information about the rds-devel
mailing list