Open Source Telephony
 help / color / mirror / Atom feed
From: Guillaume Zajac <guillaume.zajac@linux.intel.com>
To: ofono@ofono.org
Subject: Re: [PATCH_v2 1/4] gatppp: Add new contructor to use external fd
Date: Thu, 28 Apr 2011 17:17:49 +0200	[thread overview]
Message-ID: <4DB9851D.5080803@linux.intel.com> (raw)
In-Reply-To: <4DB97D43.4050404@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2232 bytes --]

Hi Denis,

On 28/04/2011 16:44, Denis Kenzior wrote:
> Hi Guillaume,
>
>>>> -    if (ppp_net_set_mtu(ppp->net, ppp->mtu) == FALSE)
>>>> -        DBG(ppp, "Unable to set MTU");
>>>> +    /*
>>>> +     * If we have opened the tun interface locally,
>>>> +     * we have to set a MTU value.
>>>> +     */
>>> So I don't agree with this.  The MTU is negotiated during LCP phase, so
>>> unless I'm missing something, this value should still be set to the
>>> negotiated one.
>>>
>> Right , I thought that as I was setting a MTU value for ConnMan tun
>> interface I didn't need to set the MTU value into oFono.
>> Obviously I was wrong :)
>>
> I assume the MTU is set to the default 1500 in Connman?

Exactly

>>>> +        net->if_name = strdup("Server ppp");
>>> This looks wrong.  You do actually want to return a proper network
>>> interface here, not make something up.
>> In fact, only ConnMan needs to know each name of its interfaces,
>> so do we need to fill this field in when ConnMan creates the interface?
>>
> Remember that we're writing a library, so things must be consistent.
> Besides, isn't this is a matter of running a TUNGETIFF ioctl?

Yes with TUNGETIFF I can get the name of the interface created by ConnMan

>>>> +        /* create a channel for reading and writing to this
>>>> interface */
>>>> +        channel = g_io_channel_unix_new(fd);
>>>> +    }
>>> There's a small problem of symmetry here.  If IPCP is established
>>> correctly, then the fd will eventually be closed by ppp_net.  However,
>>> if we never properly establish IPCP, then fd will not be closed.  What
>>> is actually expected by ConnMan?
>>>
>> In the case we don't properly establish the IPCP, ppp_disconnect CB of
>> emulator will be called.
>> Then, we will call the release_private_network DBus method. This method
>> will close the fd if it is opened.
>>
> Again, we're writing a library.  We cannot assume some behavior external
> to the library is going to save us.  So I really suggest we make closing
> of the fd symmetric.
So I will close the fd into g_at_ppp_unref() if it is >=0.
I have also to close it if we fail to create the PPP server.


Kind regards,
Guillaume



  reply	other threads:[~2011-04-28 15:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-22 12:06 [PATCH_v2 0/4] Request private petwork creation to ConnMan Guillaume Zajac
2011-04-22 12:06 ` [PATCH_v2 1/4] gatppp: Add new contructor to use external fd Guillaume Zajac
2011-04-27  3:20   ` Denis Kenzior
2011-04-28 13:06     ` Guillaume Zajac
2011-04-28 14:44       ` Denis Kenzior
2011-04-28 15:17         ` Guillaume Zajac [this message]
2011-04-28 19:41           ` Denis Kenzior
2011-04-29 13:12             ` Guillaume Zajac
2011-04-29  8:52               ` Denis Kenzior
2011-04-29 13:39               ` Guillaume Zajac
2011-04-22 12:06 ` [PATCH_v2 2/4] emulator: add routine to request/release private network from ConnMan Guillaume Zajac
2011-04-27  3:25   ` Denis Kenzior
2011-04-28 13:29     ` Guillaume Zajac
2011-04-28 19:39       ` Denis Kenzior
2011-04-29 10:06         ` Guillaume Zajac
2011-04-29  8:59           ` Denis Kenzior
2011-04-29 14:35             ` Guillaume Zajac
2011-04-22 12:06 ` [PATCH_v2 3/4] connman: add plugin in oFono to request request/release private network Guillaume Zajac
2011-04-22 12:06 ` [PATCH_v2 4/4] Makefile: add connman plugin build Guillaume Zajac
2011-04-27  3:27   ` Denis Kenzior

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=4DB9851D.5080803@linux.intel.com \
    --to=guillaume.zajac@linux.intel.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