From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: tun interface name conflicts with ppp driver
Date: Thu, 06 Dec 2012 16:59:47 +0100 [thread overview]
Message-ID: <1354809587.1815.27.camel@aeonflux> (raw)
In-Reply-To: <CABvLYuBcciGaMBvJK0ss1PiufW2=bMFsonEnmyT+Q2HeshzBtw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
Hi Cedric,
> > actually we are using ppp%d syntax to assign the network interfaces. So
> > the kernel does the numbering. This is a bug in pppd and not ours.
> >
> > Looking at the pppd code, it seems to hardcodes ppp0. So please complain
> > to them for assuming that a certain device name is owned by them.
> >
>
> pppd requests the ppp driver to create a network interface with the ioctl
> PPPIOCNEWUNIT. If the parameter passed to the ioctl is -1, the ppp driver
> will allocate the unit itself. Because it's the first network interface
> created by the ppp driver, and the ppp driver doesn't know about the tun
> interface, it's choosing 0. Check ppp_create_interface() in ppp_generic.c
> in the kernel to see how this is done.
>
> So it seems the ppp driver reserves the ppp%d interface names.
that is not how the kernel works. It is global and tun interface will
not interfere with ppp interface. In case ppp driver and pppd would do
it right, then there would be no conflict.
Regards
Marcel
prev parent reply other threads:[~2012-12-06 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 11:13 tun interface name conflicts with ppp driver Cedric Jehasse
2012-12-06 11:50 ` Marcel Holtmann
2012-12-06 14:58 ` Cedric Jehasse
2012-12-06 15:59 ` Marcel Holtmann [this message]
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=1354809587.1815.27.camel@aeonflux \
--to=marcel@holtmann.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