pppoeconf and interfaces(5) don't play properly

Bug #65906 reported by Stéphane Marguet
4
Affects Status Importance Assigned to Milestone
ppp (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

On startup the ppp0 interface is set up, but is not working.

There is nothing in plog X and ping google.com doesn't show anything.
The dsl connection was created using pppoeconf.

/etc/network/interfaces :

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.1.2
netmask 255.255.255.0

auto dsl-provider
iface dsl-provider inet ppp
provider dsl-provider

    pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf

 After using sudo poff and sudo pon dsl-provider, evrything is setup properly.

Revision history for this message
Stéphane Marguet (stemp) wrote : Re: Auto PPP0 not fonctionnal

Same on Feisty using the network-manager applet.

Changed in ppp:
status: New → Fix Committed
Changed in ppp:
status: Fix Committed → New
Revision history for this message
RJ Clay (rjclay) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in ppp:
status: New → Incomplete
Revision history for this message
Stéphane Marguet (stemp) wrote :

It is still an issue with Intrepid, exactly the same problem.

Daniel T Chen (crimsun)
Changed in ppp:
importance: Undecided → Medium
status: Incomplete → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :

not really a bug ...rather a question i guess.

Changed in ppp:
status: Confirmed → Invalid
Revision history for this message
Stéphane Marguet (stemp) wrote :

Not really a bug ?
Where is the question ?

Anyway you can close this bug. I'm using a router now and I'm not anymore affected by it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.