LinuxQuestions.org - pppoe/rp-pppoe on Debian

- Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)

- - pppoe/rp-pppoe on Debian (https://www.linuxquestions.org/questions/linux-networking-3/pppoe-rp-pppoe-on-debian-471856/)

pppoe/rp-pppoe on Debian

Hi guys,
Moving from a Mandrake server to a Debian server.

With mandrake I simply did 'urpmi rp-pppoe'. Then ran adsl-config,
answered some questions and then adsl-start and its away.

With Debian I first tried the pppoe package (apt-get install pppoe
pppoeconf) and then ran pppoeconf. This fails, as it says it can't find
and Access Communicator (?) on either eth0 or eth1. So I tried to
manually edit the dsl-provider file and add my details. Then ran
'pppoe'. After a wait, it returns "timeout waiting for PADO". So then
grabbed the rp-pppoe source and compiled it and installed. Did the
pppoe-config, answered the question (much the same as on Mandrake) and
then attempted to start up again, this time with pppoe-start. Same
problem as before "timeout waiting for PADO".

I am suspecting this NIC isn't Linux compatible. But it is
detecting enough to be labeled eth1. There is no entries in
/etc/network/interfaces for eth1. I think thats right; there shouldn't
be any settings for the NIC used to initiate the pppoe connection.

Advice ?

I had a similar problem on UBUNTU! I solved it by changing the ADSL cable to the other NIC and on that on it found the access concentrator.

Was the NIC faulty or just not Linux compatible or just not ADSL compatible ?

To be honest I didnt check if the NIC was Linux compatible as I thought I got myself down to only having Linux compatible NIC's in my house (+ the fact the system registered it as eth1)

But I will try another NIC, thanks.

Well in my case I had 2indentical NICs in the computer. Both were working great on UBUNTU BREEZY! But after I did a clean install of UBUNTU DAPPER the NIC that was responsible for ADSL connection didnt find the ACCESS CONCENTRATOR! So then I put the UTP cable to the other NIC and ADSL started working.

ps. Did U try doing:

Code:

ifup eth1 ##where eth1 is you NIC for ADSL##

ifconfig eth1 192.168.0.1

At least in my case I have the NIC resposible for ADSL assigned an IP number

Hmmm interesting...

I was always told not to bring up the NIC connected to the ADSL modem...

Maybe you should check the pppoe options in /etc/ppp/options and /etc/ppp/peers/dsl-provider. Activate the debug option! Check plog.
I do not think it is a problem with the nic, however you can try nictools or ethtool to check it.
devas

deVas,
I did check those files, mainly dsl-providers (because the pppoeconf 'wizard' didn't work.

I didn't notice the debug option in options though, I will try that next..

Quote:

Originally Posted by DaveQB

Hmmm interesting...

I was always told not to bring up the NIC connected to the ADSL modem...

If I dont bring up the NIC connected to ADSL it definetly wont connect. Have the same behavior on 2computers

Hmmm that is odd. I have never brought up the ADSL nic on my server and I have re-installed a few versions of Mandrake on it over the years..

Must be a distro thing.

Tried this again last night.

I brought up eth1 before the adsl-start command, but it seems to no want to stay up

Code:

Oct 12 23:38:39 localhost kernel: eth1: link up, 10Mbps, half-duplex, lpa 0x0000

Oct 12 23:38:39 localhost kernel: eth1: link down

Oct 12 23:38:39 localhost kernel: eth1: link up, 10Mbps, half-duplex, lpa 0x0000

Oct 12 23:38:45 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed out

Oct 12 23:38:45 localhost kernel: eth1: link up, 10Mbps, half-duplex, lpa 0x0000

Oct 12 23:38:56 localhost kernel: eth1: link up, 10Mbps, half-duplex, lpa 0x0000

Oct 12 23:39:03 localhost pppd[28425]: pppd 2.4.3 started by root, uid 0

Oct 12 23:39:03 localhost pppd[28425]: Using interface ppp0

Oct 12 23:39:03 localhost pppd[28425]: Connect: ppp0 <--> /dev/pts/0

Oct 12 23:39:08 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed out

Oct 12 23:39:08 localhost kernel: eth1: link up, 10Mbps, half-duplex, lpa 0x0000

Oct 12 23:39:26 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed out

Oct 12 23:39:26 localhost kernel: eth1: link up, 10Mbps, half-duplex, lpa 0x0000

Oct 12 23:39:34 localhost pppd[28425]: LCP: timeout sending Config-Requests

Oct 12 23:39:34 localhost pppd[28425]: Connection terminated.

Oct 12 23:39:35 localhost pppd[28425]: Using interface ppp0

Oct 12 23:39:35 localhost pppd[28425]: Connect: ppp0 <--> /dev/pts/1

Oct 12 23:39:40 localhost pppd[28425]: tcflush failed: Bad file descriptor

Oct 12 23:39:40 localhost pppd[28425]: Exit.

NB: I have nothing for eth1 in /etc/network/interfaces

Anyone have a clue for this ?

I might try Ubuntu Server edition, might work easier for PPPoE perhaps.

Quote:

Originally Posted by Ashrack

If I dont bring up the NIC connected to ADSL it definetly wont connect. Have the same behavior on 2computers

I think this is where I got that idea from.

http://www.linuxquestions.org/questi...423#post589423

As for bringing up your Ethernet card for PPPoE:

What you want to do is bring the card UP, but do NOT give it an IP address.

Let's say your Ethernet is eth0.

When you run PPPoE, it will create a new interface ppp0.

The ppp0 interface will have your real public IP address, via PPPoE.

The eth0 interface will just be up, and not have an IP address at all, even though it will be carrying packets.

This makes sense when you look at eth0 with Wireshark or another packet sniffer. What you will see is a lot of packets going back and forth, that are not IP at all. PPPoE is its own separate protocol, not IP. This is why eth0 must be up, in order to carry this protocol, but not have an IP address, since it is not IP at all.

Once you get this configuration working, then you can try giving eth0 an IP address anyway. Do not use eth0 for routing, but continue to use ppp0 as your gateway for your broadband connection. What this will allow you to do is talk to your modem on eth0, and use its Telnet or Web interface to gather statistics from it. This IP address on eth0 won't be used for your broadband connection, since that's the job of ppp0. Rather, this is just a convenient shortcut to accessing your modem for diagnostic purposes. This is somewhat advanced usage and not recommended until you are comfortable getting ppp0 set up and working.