Open Source Telephony
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: ofono@ofono.org
Subject: Re: [RFC] gatchat: Print error message if opening tun failes
Date: Tue, 21 Aug 2012 17:09:09 +0200	[thread overview]
Message-ID: <5033A495.70509@monom.org> (raw)
In-Reply-To: <1345554014.13726.85.camel@aeonflux>

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

Hi Marcel,

[sorry, a resend, ofono doesn't like non subscriber to post]

On 21.08.2012 15:00, Marcel Holtmann wrote:
>> This is a very common misstake. Let's help the users to
>> configure their system correctly.
>> ---
>>   gatchat/ppp_net.c | 6 +++++-
>>   1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/gatchat/ppp_net.c b/gatchat/ppp_net.c
>> index 1609b99..7082de7 100644
>> --- a/gatchat/ppp_net.c
>> +++ b/gatchat/ppp_net.c
>> @@ -155,8 +155,12 @@ struct ppp_net *ppp_net_new(GAtPPP *ppp, int fd)
>>   	if (fd < 0) {
>>   		/* open a tun interface */
>>   		fd = open("/dev/net/tun", O_RDWR);
>> -		if (fd < 0)
>> +		if (fd < 0) {
>> +			fprintf(stderr, "Couldn't open tun device. "
>> +					"Do you run oFono as root and do you "
>> +					"have the TUN module loaded?");
>
> really, stderr?

I was not sure what 'channel' to use to report something from gatchat. 
Would g_print() be the right choice?

>>   			goto error;
>> +		}
>>
>>   		ifr.ifr_flags = IFF_TUN | IFF_NO_PI;
>>   		strcpy(ifr.ifr_name, "ppp%d");
>
> Aren't the atom drivers checking this case for you?

I don't know, but I had the exactly the same problem and I am pretty 
sure that there was not log entry in any kind. If there is better place 
to add such a log entry, I happy to send a patch.

cheers,
daniel

  parent reply	other threads:[~2012-08-21 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21  6:00 [RFC] gatchat: Print error message if opening tun failes Daniel Wagner
2012-08-21 13:00 ` Marcel Holtmann
2012-08-21 15:06   ` Daniel Wagner
2012-08-21 15:09   ` Daniel Wagner [this message]
2012-08-21 19:34     ` 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=5033A495.70509@monom.org \
    --to=wagi@monom.org \
    --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