I receive some emails about the current status of the network namespace.
I tried to synthesize this information and I uploaded it at:
http://lxc.sourceforge.net/network_status.php
I hope that can help.
-- Daniel
--
To unsubscribe from this list: send the line "unsubscribe netdev" i
David Miller <[EMAIL PROTECTED]> writes:
> From: [EMAIL PROTECTED] (Eric W. Biederman)
> Date: Thu, 13 Esp 2007 13:12:08 -0600
>
>> The final blocker to having multiple useful instances of network
>> namespaces is the loopback device. We recognize the network namespace
>> of incoming packets by l
From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: Thu, 13 Sep 2007 13:12:08 -0600
> The final blocker to having multiple useful instances of network
> namespaces is the loopback device. We recognize the network namespace
> of incoming packets by looking at dev->nd_net. Which means for
> packets
Oliver Hartkopp <[EMAIL PROTECTED]> writes:
> can you send me your current AF_PACKET patch? I just want to update our
> recent post of the CAN (controller area network) subsystem (AF_CAN)
> which is (in some parts) similar to AF_PACKET. So i can take a look on
> it to provide the latest technique
Eric W. Biederman wrote:
> Looking into my patch queue I have:
> 5 patches for cleaning up and making a per network namespace loopback device.
> 4 patches for making rtnetlink message processing per network namespace
> 1 patch for making AF_UNIX per network namespace
> 1 patch for making AF_PACKET
Now that the network namespace work is partly merged I figure
a short status summary of where everything is at is in order.
David Miller has merged the core of the network namespace work
and that probably needs to sit just a little while to make certain
we don't have unexpected breakage.
Before
