Hi list,
I'm using a PPPoE connection to connect to my ISP - worldnet. (it's what's commonly referred to as "cablewalla ka net"). Under Windows I use the RASPPPOE protocol. I've been able to connect to it under Fedora using the nice "system-config-networking" tool. Under Debian I couldn't find any GUI tool. There is a command-line tool called "pppoeconf". I've performed the steps given on this site: http://users.pandora.be/Asterisk-PBX/PPPoE.htm
The strange thing is that although this utility prompts for username and password, it doesn't give an option to select the Access-Concentrator and Service-Provider name. (The list of service-providers and access-concentrators can be obtained using pppoe-discovery).
This is what I get in the system log: Sep 8 11:06:50 localhost pppd[3973]: Plugin rp-pppoe.so loaded. Sep 8 11:06:50 localhost pppd[3974]: pppd 2.4.4 started by root, uid 0 Sep 8 11:06:51 localhost pppd[3974]: PPP session is 43360 Sep 8 11:06:51 localhost pppd[3974]: Using interface ppp0 Sep 8 11:06:51 localhost pppd[3974]: Connect: ppp0 <--> eth0 Sep 8 11:06:52 localhost pppd[3974]: Remote message: Login incorrect Sep 8 11:06:52 localhost pppd[3974]: PAP authentication failed Sep 8 11:06:52 localhost pppd[3974]: Connection terminated. Sep 8 11:07:22 localhost pppd[3974]: PPP session is 152 Sep 8 11:07:22 localhost pppd[3974]: Using interface ppp0 Sep 8 11:07:22 localhost pppd[3974]: Connect: ppp0 <--> eth0 Sep 8 11:07:27 localhost pppd[3974]: CHAP authentication failed: I don't like you. Go 'way. Sep 8 11:07:27 localhost pppd[3974]: CHAP authentication failed Sep 8 11:07:27 localhost pppd[3974]: Connection terminated.
The username and password were correctly entered. I have checked that multiple times. Are those authentication failures generated because it is attempting to connect to other access-providers? Any suggestions to get me connected?
The strange thing is that although this utility prompts for username and password, it doesn't give an option to select the Access-Concentrator and Service-Provider name. (The list of service-providers and access-concentrators can be obtained using pppoe-discovery).
Use rp-pppoe. I compiled it from source, but you can get its deb package. Configure it using pppoe-setup. You can specify which access concentrator to use by editing file /etc/ppp/pppoe.conf .The two fields you will need to change are ACNAME and SERICENAME Then connect using ppppoe-start command.
-omkar.
On 9/9/07, Omkar Raut wrote:
The strange thing is that although this utility prompts for username and password, it doesn't give an option to select the Access-Concentrator and Service-Provider name. (The list of service-providers and access-concentrators can be obtained using pppoe-discovery).
Use rp-pppoe. I compiled it from source, but you can get its deb package. Configure it using pppoe-setup. You can specify which access concentrator to use by editing file /etc/ppp/pppoe.conf .The two fields you will need to change are ACNAME and SERICENAME Then connect using ppppoe-start command.
-omkar.
Thanks, it worked! Here's the details TWIMC: I did not need of installing rp-pppoe from source, debian includes the package "pppoe" which is different from the package "pppoeconf". When I ran pppoe-setup, I got:
# pppoe-setup Welcome to the Roaring Penguin PPPoE client setup. First, I will run some checks on your system to make sure the PPPoE client is installed properly...
Oh, dear, I don't see the file '/etc/ppp/pppoe.conf' anywhere. Please re-install the PPPoE client.
Reinstalling pppoe didn't work, so I downloaded the rp-pppoe tarball from www.roaringpenguin.com/pppoe/ extracted it and copied the pppoe.conf file to /etc/ppp
pppoe-setup now worked fine. I tried running pppoe-start without adding the service-name & access-provider to pppoe.conf. I started giving authentication errors, but after a few attempts it did connect. Now, I added the service-name & access-provider details to pppoe.conf and reconnected, it worked on the first attempt.
Also, I had to remove the default gateway ip address from my eth0 configuration, so that the pppoe connection would be set as the default gateway.
osric fernandes wrote:
The strange thing is that although this utility prompts for username and password, it doesn't give an option to select the Access-Concentrator and Service-Provider name. (The list of service-providers and access-concentrators can be obtained using pppoe-discovery).
Pppoeconf should work out of the box and one has to simply enter data as it is asked on screen. It does not require any AC identity. I just tried it out yesterday using Kubuntu 6.10 live at a client's place. If you have any *buntu 5.10 and above CD then test pppoeconf out using a live session before getting inside your system. However the latest Feisty ( 7.04 ) does not have complete packages.
On 9/9/07, Rony wrote:
Pppoeconf should work out of the box and one has to simply enter data as it is asked on screen. It does not require any AC identity. I just tried it out yesterday using Kubuntu 6.10 live at a client's place. If you have any *buntu 5.10 and above CD then test pppoeconf out using a live session before getting inside your system. However the latest Feisty ( 7.04 ) does not have complete packages.
Well, I had tried pppoeconf using Fiesty a few months back, couldn't get it to work and switched back to Fedora. Maybe the reason why pppoeconf is not working on my machine is because on my LAN there are multiple ACs and I have an account on 2 of them with the same username. I need to connect to "worldnet001" to use Internet but LAN sharing doesn't work here. I need to connect to "zone.net" to be able to use LAN sharing (DC++), but Internet doesn't work here. I don't know the reason for this strange setup at my LAN. Anyways, the rp-pppoe package does the work.
-
Omkar Raut -
osric fernandes -
Rony