The product is not working because it incorporates router(s) than runs
in containers. The containers are necessary to provide proper isolation
of the RIBs/FIBs, iptables, conntrack entries etc. Without the
container, no routers, & no product. So we need a kernel that provides
containers, as 2.6.32
I believe disabling CONFIG_NET_NS was the correct action for Lucid given
its impact on some widely used applications. According to policy
CONFIG_NET_NS should not have been enabled to begin with. Subsequent
config reviews have been more rigorous. If you have a product that is
dependent on this feat
** Summary changed:
- Removal of CONFIG_NS from 2.6.32-32 breaks applications
+ Removal of CONFIG_NET_NS from 2.6.32-32 breaks applications
** Description changed:
- LP #700295 removed CONFIG_NS from linux-image-2.6.32-32 which was
+ LP #700295 removed CONFIG_NET_NS from linux-image-2.6.32-32 wh
