All of lore.kernel.org
 help / color / mirror / Atom feed
* nf_nat not running in a netns
@ 2020-01-04 15:51 Jon Masters
  2020-01-05 18:58 ` Jon Masters
  0 siblings, 1 reply; 2+ messages in thread
From: Jon Masters @ 2020-01-04 15:51 UTC (permalink / raw)
  To: linux-kernel

Hi there,

Can anyone offer any reasons why the nat table chains for a netns wouldn’t be running?

Longer detail:

I’ve be playing with Kolla (containerized OpenStack) and the way they implement (virtual) routers for tenant networks is to create network namespaces with interfaces representing the ports plugged into the router. To translate addresses from internal to external networks, they apply D/SNAT rules within that netns. All of these are created and the interfaces are pingable, but the nat rules aren’t being run and the untranslated addresses are ultimately seen on the physical network once packets traverse out of the containers and to the external neutron interface.

Jon.

-- 
Computer Architect


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: nf_nat not running in a netns
  2020-01-04 15:51 nf_nat not running in a netns Jon Masters
@ 2020-01-05 18:58 ` Jon Masters
  0 siblings, 0 replies; 2+ messages in thread
From: Jon Masters @ 2020-01-05 18:58 UTC (permalink / raw)
  To: linux-kernel

Ignore. The below was exactly the problem.

It was broken. netns nat rules in CentOS7.7 kernel were exactly not working due to a bug. Sigh.

-- 
Computer Architect


> On Jan 4, 2020, at 10:51, Jon Masters <jcm@jonmasters.org> wrote:
> 
> Hi there,
> 
> Can anyone offer any reasons why the nat table chains for a netns wouldn’t be running?
> 
> Longer detail:
> 
> I’ve be playing with Kolla (containerized OpenStack) and the way they implement (virtual) routers for tenant networks is to create network namespaces with interfaces representing the ports plugged into the router. To translate addresses from internal to external networks, they apply D/SNAT rules within that netns. All of these are created and the interfaces are pingable, but the nat rules aren’t being run and the untranslated addresses are ultimately seen on the physical network once packets traverse out of the containers and to the external neutron interface.
> 
> Jon.
> 
> -- 
> Computer Architect
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-01-05 18:58 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-04 15:51 nf_nat not running in a netns Jon Masters
2020-01-05 18:58 ` Jon Masters

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.