[Bug 78043] Re: udev stops pppd persist working

Alan 78043 at bugs.launchpad.net
Sat Aug 18 01:13:56 UTC 2012


Stéphane, the following is an extract from my /etc/network/interfaces:

auto eth0
iface eth0 inet static
        address 10.0.0.251
        netmask 255.255.255.0
        ...

auto ppp0
iface ppp0 inet ppp
        pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf
        provider internode

as you can see, I do have it named "ppp0".

Is the reason why the problem doesn't  occur with other names that the
$INTERFACES argument passed to /etc/init/network-interface.conf will
always be "ppp0" and so if you have a name other than ppp0 in interfaces
then it will ignore the unknown interface?

In my opinion, it is more consistent to configure ppp (especially pppoe)
interfaces to always use the same pppX interface and also be configured
as such in /etc/network/interfaces. That way if you "ifup ppp0" you know
you're bringing up "ppp0". Running "ifup myprovider" or such and having
the next available pppX interface come up isn't ideal for several
reasons, the first being that it makes firewall configuration difficult
if there is a chance that an interface will come up differently each
time (imagine the case where you have to ppp interfaces and you want to
firewall them differently).

Also, in your suggestion, you don't include "auto ppp0" which as far as I know is required to bring the interface up on boot and is how pppoe-conf will set up the interface if you request it to automatically come up on boot.
An alternative would be to have a post-up command as Teemu proposes, however this is not how pppoe-conf sets up the interface.

If the solution is to set up ppp interfaces as proposed by Teemu then I
would suggest pppoe-conf needs to be changed to configure interfaces in
the same way.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/78043

Title:
  udev stops pppd persist working

Status in “ifupdown” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: udev

  Product: Ubuntu Server
  Version: 6.10
  Component:udev
  Severity: High
  Priority: High
  URL: http://rants.atmurray.net/2007/01/pppd-persist-not-so-persist-with-udev.html
  Summary: udev stops pppd persist working
  Description:
  When a pppd session is disconnected it triggers the udev script /etc/udev/rules.d/85-ifupdown.rules to ifdown the ppp link which kills pppd and stopping a reconnection. 

  Steps to Reproduce:
  1) Create a persistent ppp connection and have it set to auto in /etc/network/interfaces
  2) Cause it to disconnect

  Actual Results: udev runs ifdown on the interface causing pppd to be sent the TERM signal
  Expected Results: As it is a ppp link udev should not touch it.
  Additional Builds and Platforms: 
  I believe this bug occurred and was fixed when hutplug was implemented.
  SUSE linux has fixed this bug by explicitly skipping the udev actions for some link types

  Additional Information:
  I suggest the following two lines in /etc/udev/rules.d/85-ifupdown.rules be changed accordingly:

  ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup --allow=hotplug $env{INTERFACE}"
  ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown --allow=hotplug $env{INTERFACE}"

  and then allow-hotplug be added to /etc/network/interfaces for
  interfaces to be controlled by udev.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/78043/+subscriptions




More information about the foundations-bugs mailing list