LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   pppoe error for adsl setup in slackware (https://www.linuxquestions.org/questions/linux-networking-3/pppoe-error-for-adsl-setup-in-slackware-177584/)

lamine 05-03-2004 10:57 PM

pppoe error for adsl setup in slackware
 
Hi, Please somebody help in setting up adsl for a router verizon dsl modem.
We have two laptops at home and a desktop. The laptops are using wireless connections and they are accessing the router and the internet just fine.
I had a Windoze XP in the desktop connected to the linksys router; and it was working fine. However, since I am gradually getting myself away from windoz, I reformated the desktop and put Slack 9.1 on it. I run the adsl-setup and answered all the question but I always get this error (as root of course).
# adsl-start
....................TIMED OUT
/usr/sbin/adsl-start: line 193: 2657 Terminated $CONNECT "$@" >/dev/null 2>&1


# adsl-status
adsl-status: Link is down (can't read pppoe PID file /var/run/pppoe.conf-adsl.pid.pppoe)


also I can't access the router through a browser with it's address (192.168.1.1) as I would in window even if I am offline?

I am writing this message from my laptop running Slack 9.1, I am still online from the old settup in the windoze days.

Your help is greatly appreciated, I amreally getting frustrated :mad:

Thank ya all

adz 05-04-2004 12:26 AM

So it's an ethernet (not USB) DSL modem it take it? Try doing a dhclient eth0 as root. Report the ouptut. Then try to ping yourself, your gateway and a website. Report your results.

lamine 05-04-2004 05:29 AM

I just did the dhclient etho (yes it is an ethernet DSL modem)
First I get the following:
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
NO DHCPOFFERS received
NO workink leases in persistent database-sleeping

I then tried to ckeck my router's connections and accidently unpluged the power to the router. When I put it back up I noticed no light on any of the ports, not even port 1 linked to the PC. In the same token, no light at the network card as usuall to indicate activities. I repeated the dhclient etho and this time it says:
eth0: not found.

If I do ifconfig, I do get eth0 with the HWaddr.
Any suggestion please.

adz 05-04-2004 06:14 AM

OK just give me a general idea of what your network looks like. Your desktop computer is connected straight to the DSL modem or to the router which is then connected to the modem? Your router acts as both a wired and wireless router? Also, is there a DHCP server on your network somewhere? EIther in the router or the modem? I'm assuming your router and modem are two separate entities.

lamine 05-04-2004 06:28 AM

My network connects to the router (a linksys BEFw11S4, both wired and wireless router "this is why my laptop still works")the router is then connected to the dsl modem (westell from verizon in New York). I belief there is a DHCP in the router (I will try to confirm that)
There still no light on my NIC indicating any link betw the router and the PC.
If I transfer the cable to my laptop, I get activities (lights are on )
How do I detrmine whether my network card is still OK?

adz 05-04-2004 08:57 AM

Well first you have to make sure the interface is up. Do an ifconfig and make sure there is an "eth0" section there. If there isn't you have to do an ifconfig eth0 up. Then do an ifconfig again just to confirm eth0's presence. If ifconfig fails then you probably need to load a driver for you card (if this is the case, post the output of lspci). Once you have the eth0 interface up you can then ping yourself (ping localhost or ping 127.0.0.1) to see if you get a reply. The output should look like this:
Code:

adz@hades:~$ ping localhost
PING hades (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.1 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.0 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.0 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.0 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.0 ms

--- hades ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.0/0.0/0.1 ms

If you get that then your card and driver are OK.

To determine if there is a DHCP server, check your windows network status. Go through the little network icon next to the time display and then to "status" I think. Somewhere in there it will tell you whether the IP was assigned statically or via DHCP.

lamine 05-04-2004 10:23 AM

The ping localhost worked fine. for the DHCP server, I don't have window anymore. But the setup was to obtain IP via DHCP. It also connect using PPPoE. Now I have the light back in the card connection, I tried dhclient eth0 and I get an error saying: eth0: not found.
at thesame time ifconfig is listing eth0!!

michaelk 05-04-2004 10:34 AM

If the computer is connected to the router then you do not need PPPoE running on the PC itself. PPPoE will be handled by the router. All you need to do is configure eth0 (assuming 1 NIC) for DHCP. Now you should be able to ping the router (192.168.1.1).

BTW pinging localhost just verifies that TCP/IP is working but does not verify the network card.

lamine 05-04-2004 11:09 AM

I still can't ping the router (192.168.1.1)
I tried configuring eth0 for DHCP (using netconfig) but still nothing.

michaelk 05-04-2004 11:46 AM

Make sure pppoe is down i.e. you do not have a ppp0 connection. Verify nothing for:
/sbin/ifconfig ppp0

Do you have a valid IP address for eth0
/sbin/ifconfig eth0

Configure your eth0 for a static IP address. (log in as root)
ifconfig eth0 192.168.1.5 netmask 255.255.255.0 up

I believe that the router starts the DHCP address @ 100. Now look at the output of ifconfig again. Verify the IP address for eth0. Can you ping the router?

Monch 05-04-2004 04:33 PM

Hi, I have the same setup and problem as lamine, except that I'm using a D-Link DI-614+ router.

I have followed your instructions so far and I think I've made progress. The problem right now is that when I ping the router it just hangs there, I have to stop by Ctrl+C... everything else works as you guys described it should be working. I would greatly appreciate further input.

adz 05-04-2004 06:46 PM

Could you both show me the output of the route -n? The static idea looks like it could be the way to go for now.

robert_edwards 05-04-2004 07:33 PM

Well I recently also had tried slack9.1 with a linksys router. What I had to do is in the initial install, where it asks for a host name I named it slack in the domain name I put comcast.net
This worked although it would look something like slack.pcp*****.comcast.net turn nothing else on in the networking setup on the slack box just enter the host name (could be any name) and the domain (verizion.net or whatever) other than that check back with the GURU,s.

lamine 05-04-2004 07:37 PM

Sorry, I steped out.
I tried the suggestions above (Michaelk), and still I can't ping my router (the router addr 192.168.1.1).eth0 takes the given addr (shown by ifconfig)
the output of route -n:
Destination(192.168.1.0) Gateway(0.0.0.0) Genmask(255.255.255.0) Flags(U) Metric(0) Ref(0) Use(0) Iface(eth0)
Destination(127.0.0.0) Gateway(0.0.0.0) Genmask(255.0.0.0) Flags(U) Metric(0) Ref(0) Use(0) Iface(lo)

Also as requested by adz, dhclient gives me this output:
no Broadcast interface found- exiting

On all that my card reads as:
eth0: Digital DS21143 Tulip rev 65 at 0x1000, 00:08:C7:8F:B3:1B IRQ 11

if this could mean anything.12Destination

Monch 05-04-2004 07:59 PM

OK...

route -n gives me the exact same thing as lamine. I also can't ping my router (192.168.0.1 in my case).

I chequed in my router configuration and it detects that a connection is at the IP I set my slackware box to.

So far I've given up searching for more info. I think I'll stick with your help...

Thanks a lot!


All times are GMT -5. The time now is 12:16 AM.