From: Guillaume Nault <gnault@redhat.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
James Chapman <jchapman@katalix.com>,
tparkin@katalix.com, edumazet@google.com, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, corbet@lwn.net,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PPPoL2TP: Add more code snippets
Date: Tue, 18 Apr 2023 11:06:51 +0200 [thread overview]
Message-ID: <ZD5dqwPblo4FOex1@debian> (raw)
In-Reply-To: <20230418085323.h6xij7w6d2o4kxxi@begin>
On Tue, Apr 18, 2023 at 10:53:23AM +0200, Samuel Thibault wrote:
> Guillaume Nault, le mar. 18 avril 2023 10:34:03 +0200, a ecrit:
> > On Mon, Apr 17, 2023 at 12:07:04AM +0200, Samuel Thibault wrote:
> > > sax.sa_family = AF_PPPOX;
> > > sax.sa_protocol = PX_PROTO_OL2TP;
> > > sax.pppol2tp.fd = tunnel_fd;
> > > @@ -406,12 +407,64 @@ Sample userspace code:
> > > /* session_fd is the fd of the session's PPPoL2TP socket.
> > > * tunnel_fd is the fd of the tunnel UDP / L2TPIP socket.
> > > */
> > > - fd = connect(session_fd, (struct sockaddr *)&sax, sizeof(sax));
> > > - if (fd < 0 ) {
> > > + ret = connect(session_fd, (struct sockaddr *)&sax, sizeof(sax));
> > > + if (ret < 0 ) {
> >
> > Now you also need to close session_fd.
>
> ? No, we need it for PPPIOCGCHAN, and also PPPIOCGL2TPSTATS.
connect() failed. You can't do anything with this socket.
> I'll put return session_fd instead.
What's the point of returning session_fd if connect() failed?
How will the caller know if session_fd is connected or not?
Why would it even be interested in a half-created session fd?
> > > +The ppp<ifunit> interface can then be configured as usual with SIOCSIFMTU,
> > > +SIOCSIFADDR, SIOCSIFDSTADDR, SIOCSIFNETMASK, and activated by setting IFF_UP
> > > +with SIOCSIFFLAGS
> > > +
> > > + - Tunnel switching is supported by bridging channels::
> >
> > This is a PPP feature not an L2TP one.
> >
> > PPPIOCBRIDGECHAN's description
> > belongs to Documentation/networking/ppp_generic.rst, where it's already
> > documented.
>
> Yes but that's hard to find out when you're looking from the L2TP end.
That's why I proposed linking to ppp_generic.rst.
> > If necessary, you can link to ppp_generic.rst here.
> >
> > Also, calling this feature 'tunnel switching' is misleading.
>
> That's how I have seen it is called in L2TP jargon.
That still doesn't describe the kernel feature. We can add a 'so called
"tunnel switching" in L2TP jargon' into parenthesis to give a hint to
the people using this terminology.
> Samuel
>
next prev parent reply other threads:[~2023-04-18 9:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 22:07 [PATCH] PPPoL2TP: Add more code snippets Samuel Thibault
2023-04-16 22:26 ` Dominique Martinet
2023-04-16 22:43 ` Samuel Thibault
2023-04-18 8:03 ` Guillaume Nault
2023-04-18 8:14 ` Guillaume Nault
2023-04-18 8:34 ` Guillaume Nault
2023-04-18 8:53 ` Samuel Thibault
2023-04-18 9:06 ` Guillaume Nault [this message]
2023-04-18 9:11 ` Samuel Thibault
2023-04-18 10:17 ` Guillaume Nault
2023-04-18 10:31 ` Samuel Thibault
2023-04-18 11:25 ` Guillaume Nault
2023-04-18 11:54 ` Samuel Thibault
2023-04-18 13:38 ` Guillaume Nault
2023-04-18 14:18 ` Samuel Thibault
2023-04-19 10:49 ` Tom Parkin
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=ZD5dqwPblo4FOex1@debian \
--to=gnault@redhat.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jchapman@katalix.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=tparkin@katalix.com \
/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 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.