Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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)
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
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
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.