Problem with DSL connection(PPPoE over eth0)

[vitormf]

Hello everyone.

I can't get my DSL(PPPoE over eth0) connection to start using net_applet in PCLinuxOS 2010. When I try to connect, it takes some time and says that
the network is inactive in interface ppp0. There seems to be no problem with eth0, as I can access my modem's configuration page.
However, I can connect using pppoe-start(after properly setting up with pppoe-setup) with the following steps:

activate eth0 in net_applet
ifdown eth0
pppoe-start

It's very similiar to the problem described in http://thetechie.co.za/?p=8.

Is there anyway to fix it?

Thanks.

****
ifup ppp0

Cannot find device "ppp0"
Using interface ppp0
Connect: ppp0 <--> /dev/pts/2
PADS: System-Error: no available PPP session
PADS: System-Error: no available PPP session
PADS: System-Error: no available PPP session
LCP: timeout sending Config-Requests
Connection terminated.
Modem hangup
pppoe: Timeout waiting for PADS packets
Using interface ppp0
Connect: ppp0 <--> /dev/pts/2
PADS: System-Error: no available PPP session
PADS: System-Error: no available PPP session
PADS: System-Error: no available PPP session
LCP: timeout sending Config-Requests
Connection terminated.
Modem hangup
pppoe: Timeout waiting for PADS packets
Using interface ppp0
Connect: ppp0 <--> /dev/pts/2
PADS: System-Error: no available PPP session
PADS: System-Error: no available PPP session
PADS: System-Error: no available PPP session
LCP: timeout sending Config-Requests
Connection terminated.
Modem hangup
pppoe: Timeout waiting for PADS packets
Using interface ppp0
Connect: ppp0 <--> /dev/pts/3
PADS: System-Error: no available PPP session
PADS: System-Error: no available PPP session
PADS: System-Error: no available PPP session
LCP: timeout sending Config-Requests
Connection terminated.
Modem hangup
pppoe: Timeout waiting for PADS packets
Using interface ppp0
Connect: ppp0 <--> /dev/pts/2
PADS: System-Error: no available PPP session
PADS: System-Error: no available PPP session
PADS: System-Error: no available PPP session
LCP: timeout sending Config-Requests
Connection terminated.
Modem hangup
pppoe: Timeout waiting for PADS packets

****
ifconfig

eth0      Link encap:Ethernet  Endereço de HW 00:14:0B:4F:DF:05 
          inet end.: 192.168.254.3  Bcast:192.168.254.255  Masc:255.255.255.0
          endereço inet6: fe80::214:bff:fe4f:df05/64 Escopo:Link
          UP BROADCASTRUNNING MULTICAST  MTU:1500  Métrica:1
          RX packets:209 errors:0 dropped:0 overruns:0 frame:0
          TX packets:278 errors:0 dropped:0 overruns:0 carrier:0
          colisões:2 txqueuelen:1000
          RX bytes:17031 (16.6 KiB)  TX bytes:44144 (43.1 KiB)
          IRQ:23 Endereço de E/S:0x4800

lo        Link encap:Loopback Local 
          inet end.: 127.0.0.1  Masc:255.0.0.0
          endereço inet6: ::1/128 Escopo:Máquina
          UP LOOPBACKRUNNING  MTU:16436  Métrica:1
          RX packets:132 errors:0 dropped:0 overruns:0 frame:0
          TX packets:132 errors:0 dropped:0 overruns:0 carrier:0
          colisões:0 txqueuelen:0
          RX bytes:6720 (6.5 KiB)  TX bytes:6720 (6.5 KiB)

[Xenaflux]

When I try to connect, it takes some time and says that
the network is inactive in interface ppp0.

Similar thing here, but after the message, I click on it again, fill in my password and then it connects.
 ( a royal p.i.t.a )

Xena

[Was_Just19]

Hello everyone.

I can't get my DSL(PPPoE over eth0) connection to start using net_applet in PCLinuxOS 2010. When I try to connect, it takes some time and says that
the network is inactive in interface ppp0. There seems to be no problem with eth0, as I can access my modem's configuration page.
However, I can connect using pppoe-start(after properly setting up with pppoe-setup) with the following steps:

activate eth0 in net_applet
ifdown eth0
pppoe-start

It's very similiar to the problem described in http://thetechie.co.za/?p=8.

Is there anyway to fix it?

Thanks.

Welcome to the forum!

Just to clarify .......  you are connecting directly to a modem with no NAT/router built in?

[vitormf]

Thank you!

Yes, the modem is in bridge mode and NAT is disabled.

Clicking on it again did nothing here.

[musonio]

I've had that problem for 5 years now. Many posts and no solution.
If you find out how to solve it, PLEASE let me know.

[Xenaflux]

've had that problem for 5 years now. Many posts and no solution

Have you tried enabling and disabling services in PCC/system/manage system services  ??

[musonio]

Do you mean network-up, pppoe, etc.? Yes. 

[Was_Just19]

Thank you!

Yes, the modem is in bridge mode and NAT is disabled.

Clicking on it again did nothing here.

I don't really wish to divert from the actual problem, but is there some reason to 'expose' the PC to the internet by giving it a WAN IP address instead of using the NAT of the router and getting a LAN IP address with the modem/router doing the PPoE connection?
I am using bridged mode on a router here (actually a combined bridge/NAT) to get a second router connected and registering with my ISP.
I have not connected a PC directly to the internet for many years now.

To relate that to the problem ......  if you do not need, for some specific reason, the PC to get a WAN IP address, the problem would be avoided.
I know .....  not a solution to the problem ....... but  ......

What is the make and model of the modem/router device?
Is it permanently powered and connected or does it get powered up with the PC?
Is the difficulty experienced at every boot, or does it change with cold-booting ?

regards.

[vitormf]

Thank you!

Yes, the modem is in bridge mode and NAT is disabled.

Clicking on it again did nothing here.

I don't really wish to divert from the actual problem, but is there some reason to 'expose' the PC to the internet by giving it a WAN IP address instead of using the NAT of the router and getting a LAN IP address with the modem/router doing the PPoE connection?
I am using bridged mode on a router here (actually a combined bridge/NAT) to get a second router connected and registering with my ISP.
I have not connected a PC directly to the internet for many years now.

To relate that to the problem ......  if you do not need, for some specific reason, the PC to get a WAN IP address, the problem would be avoided.
I know .....  not a solution to the problem ....... but  ......

What is the make and model of the modem/router device?
Is it permanently powered and connected or does it get powered up with the PC?
Is the difficulty experienced at every boot, or does it change with cold-booting ?

regards.

Really, there is no reason beyond pure laziness.

The modem is a Speedstream 5200 by Efficient Networks, it gets powered up with the PC
and it happens with every boot.
I don't think it is a modem issue, as I can connect on Windows XP/Vista/7 and Slackware(pppoe-start also, I don't have KDE on it).

[Was_Just19]

Thank you!

Yes, the modem is in bridge mode and NAT is disabled.

Clicking on it again did nothing here.

I don't really wish to divert from the actual problem, but is there some reason to 'expose' the PC to the internet by giving it a WAN IP address instead of using the NAT of the router and getting a LAN IP address with the modem/router doing the PPoE connection?
I am using bridged mode on a router here (actually a combined bridge/NAT) to get a second router connected and registering with my ISP.
I have not connected a PC directly to the internet for many years now.

To relate that to the problem ......  if you do not need, for some specific reason, the PC to get a WAN IP address, the problem would be avoided.
I know .....  not a solution to the problem ....... but  ......

What is the make and model of the modem/router device?
Is it permanently powered and connected or does it get powered up with the PC?
Is the difficulty experienced at every boot, or does it change with cold-booting ?

regards.

Really, there is no reason beyond pure laziness.

In which case I would seriously suggest you do the PPoE in the router .....  a one time set up ......  magic for us lazy guys 
Never have to set up PPoE again in a PC connected to that router.

The modem is a Speedstream 5200 by Efficient Networks, it gets powered up with the PC
and it happens with every boot.
I don't think it is a modem issue, as I can connect on Windows XP/Vista/7 and Slackware(pppoe-start also, I don't have KDE on it).

It may just be a timing issue so .....  try turning on the modem a couple of minutes before the PC.

The real solution IMO, is to take the modem out of bridged mode, make use of its inbuilt Firewall which is presently bypassed, make use of its NAT features, and connect any PC without having to put the PPoE information into the PC.
If it is ever needed to have more than one PC connected to the internet at the same time, or if you wish to share files between PCs, then the addition of a hub or switch between the PCs and the modem/router will give instant access.

There is not much point, IMO, in having comprehensive hardware firwalling and NAT in the device and not making use of it.   

So my advice is to enable the router in the device and use its functions to protect your PC/s.

regards.