On Mon, Oct 2, 2017 at 11:32 AM, Nicolas Dichtel <nicolas.dich...@6wind.com> wrote: > 1. Move the process to netns B, open the netlink socket and move back the > process to netns A. The socket will remain in netns B and you will receive all > netlink messages related to netns B. > > 2. Assign a nsid to netns B in netns A and use NETLINK_LISTEN_ALL_NSID on your > netlink socket (see iproute2).
Both of these seem to rely on the process knowing where the device is being moved and having access to that namespace. I don't think these two things are a given though. Unless I'm missing something? Jason
