[Bug 46260] Re: pppoe broken in dapper

2007-06-29 Thread Marco Rodrigues
** Changed in: rp-pppoe (Ubuntu)
   Status: New = Invalid

-- 
pppoe broken in dapper
https://bugs.launchpad.net/bugs/46260
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 46260] Re: pppoe broken in dapper

2006-11-29 Thread Ivailo Stoyanov
Well, my previous comment turned out to be a result of a
misconfiguration, rather than a bug.

I had to put the following line in my /etc/ppp/peers/dsl-provider:

plugin rp-pppoe.so rp_pppoe_service the_service_name eth0

NOTE: actually, it was only the rp_pppoe_service ... part that was
necessary to be inserted.

Afterwards, I was able to connect to the ISP at wish, without any
problems.

-- 
pppoe broken in dapper
https://launchpad.net/bugs/46260

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 46260] Re: pppoe broken in dapper

2006-11-28 Thread Ivailo Stoyanov
I have experienced exactly the same problem as David, and I *suggest*
that it could be somehow connected with the absence of an option
equivalent to SERVICENAME=xxx in rp-pppoe. I've got this idea while
triggering my connection numerous times with pon dsl-provider -d, and
during these attepmts I have noticed that the service name in PADS:
Service-name: 'XXX' (as visible in the log) has been predominantly
LAN (connection *failed*), a few times empty (i.e. ' '; connection
*failed* again), and only two times until now it has been equivalent to
the service name required by the ISP in order to connect (connection
*successful*). Therefore I wonder if there is a way to specify the
service name explicitly somewhere in the configuration files to test my
hypothesis. Or could this be interpreted as a misconfiguration of the
ISP infrastructure?

Thank you in advance!

-- 
pppoe broken in dapper
https://launchpad.net/bugs/46260

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 46260] Re: pppoe broken in dapper

2006-11-06 Thread Kai Kasurinen
** Changed in: Ubuntu
Sourcepackagename: None = rp-pppoe

-- 
pppoe broken in dapper
https://launchpad.net/bugs/46260

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 46260] Re: pppoe broken in dapper

2006-09-04 Thread David K
- running an HP lappie with D-link pcmcia ethernet card recognized as eth0
- ran pppoeconf ok from root
-first time internet connection worked and thought all was fine
- after computer re-booted, no internet connection
- ran pon dsl-provider, no internet
- ran plog and got:

Plugin roe.so loaded.
pppd 2.4.4b1 started by root, uid 0
PPP session is 3182
Using interface ppp1
Connect: ppp1  eth0
PAP authentication failed

- repeatedly used pon and poff dsl-provider to toggle the connection
- interface changed from ppp1 to ppp2 to ppp3 to ppp4 (not sequentially, 
though). I have only one ethernet installed (the d-link)
- finally, internet connection was established when interface toggled to ppp0, 
which seems to match with the same number designation for my ethernet:

PPP session is 3234
Using interface ppp0
Connect: ppp0  eth0
PAP authentication succeeded

My internet connection CONSISTENTLY works when ppp0  eth0. Under this 
situation, PAP authentication always succeeds. Is there a way to force Ubuntu 
Dapper to use only ppp0? I think this would solve my problem.  Furthermore, I 
tried the fixes found on https://help.ubuntu.com/commuunity/adslpppoe
involved changing interfaces file under /etc/network
added lines as was suggested. still a no-go.

so.any ideas?

Presently, my interfaces file reads as follows:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp


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

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

perhaps someone can help me...my only ethernet card is eth0. do i need
lines like auto eth1 and auto ath0 and auto wlan0? Are these lines
buggering my connection? Also, should my iface eth0 inet dhcp line
read iface eth0 inet manual, and if so, what's the diff?  I have given
this Ubuntu thing one more week, after which I will return to (egads)
windows.  All I need is a bloody INTERNET connection!

-- 
pppoe broken in dapper
https://launchpad.net/bugs/46260

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 46260] Re: pppoe broken in dapper

2006-06-23 Thread Medya
why this bug is not confirmed, I am in pain I have to run these commands
everytime I start up to connect to internet... thats painfull .

sudo poff -a
sudo pppoeconf


why u cant solve this problem...

-- 
pppoe broken in dapper
https://launchpad.net/bugs/46260

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs