Package: pppoeconf
Version: 1.17
Severity: normal

Problems:
pppoeconf created /etc/network/interface:
 * does not disable dhcp if it exists
 * uses virtual interface name after auto
 * may create both ppp and manual configuration
 * may have both "auto eth0" and "allow-hotplug eth0"

All these are not desirable.

I expect simple pppoe connection should have one of the following as
/etc/network/interfaces:

Option 1: (I think this is best)
|auto lo
|iface lo inet loopback
|
|auto eth0
|iface eth0 inet ppp
|pre-up    /sbin/ifconfig eth0 up
|post-down /sbin/ifconfig eth0 down
|# create ppp0 interface which connects via eth0 connection
|provider dsl-provider

Option 2: (If you insist using manual instead of ppp)
|auto lo
|iface lo inet loopback
|
|auto eth0
|iface eth0 inet manual
|pre-up    /sbin/ifconfig eth0 up
|# create ppp0 interface which connects via eth0 connection
|up        /usr/bin/pon   dsl-provider
|down      /usr/bin/poff  dsl-provider
|post-down /sbin/ifconfig eth0 down

-----
Here is where we are now.

If we start with typical DHCP configuration:

|auto lo
|iface lo inet loopback
|
|auto eth0
|iface eth0 inet dhcp
| hostname snoopy

After pppoeconf

|auto lo
|iface lo inet loopback
|
|auto eth0
|iface eth0 inet dhcp
| hostname snoopy
|
|auto dsl-provider
|iface dsl-provider inet ppp
|pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf
|provider dsl-provider

This is not right.

I think you should comment out following at least.
|auto eth0
|iface eth0 inet dhcp
| hostname snoopy

Then I reread created /e/n/i file and still feel strange though it created
working configuration.

The thing is after "auto" or "allow-hotplug", it should use Physical
iterface name.  eth0, ppp0, ... dsl-provider is not the one for sure.
If I start with "alow-hotplug eth0" version, "auto eth0" was added.  So
there were both "allow-hotplug eth0" and "auto eth0".  

These are not so nice.

Then I started with simpler:
|auto lo
|iface lo inet loopback
pppoeconf created:
|auto lo
|iface lo inet loopback
|
|auto dsl-provider
|iface dsl-provider inet ppp
|pre-up   /sbin/ifconfig eth0 up # line maintained by pppoeconf
|provider dsl-provider
|
|auto eth0
|iface eth0 inet manual
I expected this should create good configuration but what I got was
funny one.  Yes, I know it connects but this disregards how ifupdown
package is used.

It looks to me the current script tries to adress some special situation
where the machine is used as NAT for LAN while sharing single interface.
That is very special case and whoever makes such configuration should
edit /e/n/i by hand.  

The funny configuration created from DHCP works as is but if one
reorders contents, it may create situation here dhcp is run after pppoe
and erase resolv.conf etc.  I think problem I observed on debian-user ML
where user were really confused with /e/n/i file created by pppoeconf
and having problem connecting to the net.  Besides, I see no reason to
have bogus "iface eth0 inet manual" stanza.

If you want to have dsl-provider as virtual interface name, you should
use map script to map eth0 to dsl-provider.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages pppoeconf depends on:
ii  gettext-base                 0.17-2      GNU Internationalization utilities
ii  modconf                      0.3.6       Device Driver Configuration
ii  ppp                          2.4.4rel-9  Point-to-Point Protocol (PPP) daem
ii  pppoe                        3.8-3       PPP over Ethernet driver
ii  sed                          4.1.5-6     The GNU sed stream editor
ii  whiptail [whiptail-provider] 0.52.2-11.2 Displays user-friendly dialog boxe

Versions of packages pppoeconf recommends:
ii  locales                       2.7-10     GNU C Library: National Language (
ii  locales-all [locales]         2.7-10     GNU C Library: Precompiled locale 

-- no debconf information



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

Reply via email to