From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] ppp: implement MRU option
Date: Thu, 22 Apr 2010 15:51:26 -0500 [thread overview]
Message-ID: <201004221551.26311.denkenz@gmail.com> (raw)
In-Reply-To: <20100422134007.0c9b2cf6@kcaccard-MOBL3>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
Hi Kristen,
> On Thu, 22 Apr 2010 15:16:58 -0500
>
> Denis Kenzior <denkenz@gmail.com> wrote:
> > Hi Kristen,
> >
> > > @@ -80,7 +88,7 @@ static gboolean ppp_net_callback(GIOChannel *channel,
> > > GIOCondition cond,
> > >
> > > if (cond & G_IO_IN) {
> > > /* leave space to add PPP protocol field */
> > > - status = g_io_channel_read_chars(channel, buf + 2, MAX_PACKET,
> > > + status = g_io_channel_read_chars(channel, buf + 2, net->mtu,
> > > &bytes_read, &error);
> > > if (bytes_read > 0) {
> > > ppp->proto = htons(PPP_IP_PROTO);
> >
> > So I actually have a concern here. Quoting RFC 1332 Section 2.1:
> > "Exactly one IP packet is encapsulated in the Information field of PPP
> > Data Link Layer frames where the Protocol field indicates type hex
> > 0021 (Internet Protocol)."
> >
> > However, you're not changing the physical MTU of the TUN/TAP interface,
> > so in effect you are mangling the packets that are larger than net->mtu.
> > These packets will most likely simply be discarded leading to lots of
> > fun.
>
> We can add an ioctl to change the MTU during ppp_net_set_mtu(), which
> should hopefully resolve this.
>
Yep, my thinking as well. Can you send a patch?
Thanks,
-Denis
next prev parent reply other threads:[~2010-04-22 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 22:26 [PATCH] ppp: implement MRU option Kristen Carlson Accardi
2010-04-22 5:01 ` Marcel Holtmann
2010-04-22 15:12 ` Marcel Holtmann
2010-04-22 20:16 ` Denis Kenzior
2010-04-22 20:40 ` Kristen Carlson Accardi
2010-04-22 20:51 ` Denis Kenzior [this message]
2010-04-22 20:51 ` Kristen Carlson Accardi
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=201004221551.26311.denkenz@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.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