Package: ppp
Version: 2.4.3-20050321+2
Severity: normal

Hello,

the subject says it all. Currently, you forced most DSL users to
have an interfaces entry for getting the ethernet interface up (*).

So, by default pon is broken now, since the interface is down after the
reboot. IMO to fix that problem, either hooks in the config files needs
to be fixed for pppoe connections (to run ifconfig from them (**)), or
you should continue with the next logical step: throw away pon and make
symlink pon/poff to ifup/ifdown.

The transition should not be very complicated - first you make sure that
everything works well within ppp, then you pass this bug over to
ifupdown where some things need to be adopted (recognizing pon/poff as
command names).

Regards,
Eduard.

(*): just for cosmetics reasons which I still do not understand but
unfortunately "the maintainer is always right" rule applies
(**): which is a pain in the ass or just bloat, you need to run a
separate tool just to enable an interface that "belongs" to this
connection anyway

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-rc5
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages ppp depends on:
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libpam-modules              0.76-22      Pluggable Authentication Modules f
ii  libpam-runtime              0.76-22      Runtime support for the PAM librar
ii  libpam0g                    0.76-22      Pluggable Authentication Modules l
ii  libpcap0.7                  0.7.2-7      System interface for user-level pa
ii  makedev                     2.3.1-78     creates device files in /dev
ii  netbase                     4.21         Basic TCP/IP networking system
ii  procps                      1:3.2.5-1    /proc file system utilities
ii  zlib1g                      1:1.2.2-4    compression library - runtime

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to