linux-kernel - Re: [RFC 3/4] net: pppol2tp - introduce net-namespace functionality

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4968E589.2020904@katalix.com>
Date:	Sat, 10 Jan 2009 18:14:33 +0000
From:	James Chapman <jchapman@...alix.com>
To:	Cyrill Gorcunov <gorcunov@...il.com>
CC:	davem@...emloft.net, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, devel@...nvz.org, xemul@...nvz.org
Subject: Re: [RFC 3/4] net: pppol2tp - introduce net-namespace functionality

Cyrill Gorcunov wrote:
> [Cyrill Gorcunov - Sat, Jan 10, 2009 at 06:19:58PM +0300]
> | [James Chapman - Sat, Jan 10, 2009 at 03:05:13PM +0000]
> | | Cyrill Gorcunov wrote:
> | | > [Cyrill Gorcunov - Sat, Jan 10, 2009 at 02:13:59PM +0300]
> | | > | [James Chapman - Sat, Jan 10, 2009 at 11:06:08AM +0000]
> | | > | | Cyrill Gorcunov wrote:
> | | > | | > - Each tunnel and appropriate lock are inside own namespace now.
> | | > | | > - pppox code allows to create per-namespace sockets for
> | | > | | >   both PX_PROTO_OE and PX_PROTO_OL2TP protocols. Actually since
> | | > | | >   now pppox_create support net-namespaces new PPPo... protocols
> | | > | | >   (if they ever will be) should support net-namespace too otherwise
> | | > | | >   explicit check for &init_net would be needed.
> | | 
> | | Ok, I tested this in my L2TP setup. The first ppp session setup fails
> | | because the PPPIOCNEWUNIT ioctl returns -EEXIST. I think the problem is
> | |  the logic in ppp_create_interface(), which does the following to create
> | | a new ppp interface:
> | | 
> | |         /* Initialize the new ppp unit */
> | |         ppp->file.index = unit;
> | |         sprintf(dev->name, "ppp%d", unit);
> | | 
> | |         ret = register_netdev(dev);
> | | 
> | | Looks like there is more work to do in the ppp changes.
> | | 
> | |
> ...
> 
> Btw James did connection work without these patches? On
> pure net-next-2.6 tree? I've some bad feeling that this
> fail is related to different patch. Just to be sure.

If you mean, does pppol2tp work with the patches applied when no
namespace is configured, yes it does.

But to test this patch, I ran two l2tp daemons (in different namespaces
on the same box) and used the veth device to connect them. The failure
happened on the first l2tp session create because each side tried to
create a ppp interface called ppp0.

Should all interface names be unique across the system even when netns
is used? If so, then ppp_generic needs to assign system-wide unique ppp
unit numbers.


-- 
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/