netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: James Chapman <jchapman@katalix.com>,
	davem@davemloft.net, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, devel@openvz.org, xemul@openvz.org
Subject: Re: [RFC 3/4] net: pppol2tp - introduce net-namespace functionality
Date: Sat, 10 Jan 2009 19:12:57 +0300	[thread overview]
Message-ID: <20090110161257.GD29349@localhost> (raw)
In-Reply-To: <20090110151958.GC29349@localhost>

[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.
| | 
| | -- 
| | James Chapman
| | Katalix Systems Ltd
| | http://www.katalix.com
| | Catalysts for your Embedded Linux software development
| |
...

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.
 
		- Cyrill -

  reply	other threads:[~2009-01-10 16:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090109195154.320495476@gmail.com>
2009-01-09 19:51 ` [RFC 1/4] net: pppoe - code cleanup and helpers Cyrill Gorcunov
2009-01-09 19:51 ` [RFC 2/4] net: pppoe - introduce net-namespace functionality Cyrill Gorcunov
2009-01-09 19:51 ` [RFC 3/4] net: pppol2tp " Cyrill Gorcunov
2009-01-10 11:06   ` James Chapman
2009-01-10 11:13     ` Cyrill Gorcunov
2009-01-10 12:54       ` Cyrill Gorcunov
2009-01-10 13:13         ` James Chapman
2009-01-10 15:05         ` James Chapman
2009-01-10 15:19           ` Cyrill Gorcunov
2009-01-10 16:12             ` Cyrill Gorcunov [this message]
2009-01-10 18:14               ` James Chapman
2009-01-10 18:51                 ` Cyrill Gorcunov
2009-01-11  7:36         ` David Miller
2009-01-09 19:51 ` [RFC 4/4] net: ppp_generic " Cyrill Gorcunov
2009-01-10  9:22   ` Cyrill Gorcunov
2009-01-10  9:28     ` Cyrill Gorcunov
2009-01-11  0:33       ` Paul Mackerras
2009-01-11  7:39         ` David Miller
2009-01-11  7:46         ` Cyrill Gorcunov
2009-01-11  8:25           ` Cyrill Gorcunov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090110161257.GD29349@localhost \
    --to=gorcunov@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devel@openvz.org \
    --cc=jchapman@katalix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=xemul@openvz.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).