[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ADSL using pppoe & pppoeconfig



* Ricardo Diz <op6001@mail.telepac.pt> [04-10-2002 22:50]:
> Here is the log:
> 
> Oct  4 17:29:02 (none) pppd[1074]: Connect: ppp0 <--> /dev/pts/0
> Oct  4 17:29:02 (none) pppd[1074]: not replacing existing default route
> to eth0 [193.136.238.1]
> Oct  4 17:29:02 (none) pppd[1074]: Cannot determine ethernet address for
> proxy ARP
> Oct  4 17:29:02 (none) pppd[1074]: local  IP address 213.13.230.110
> Oct  4 17:29:02 (none) pppd[1074]: remote IP address 213.13.200.1
> Oct  4 17:29:02 (none) pppd[1074]: primary   DNS address 194.65.5.2
> Oct  4 17:29:02 (none) pppd[1074]: secondary DNS address 194.65.3.21
> 
> So it appears to be connected since I'm assigned a IP, but I can't ping
> nothing but the remote address (or my own, of course). 
> 
> There are in fact 3 things that amazed me: In the first line I was
> expecting eth0 instead of pts/0

That's normal. You can forget about eth0 when you use pppoe.

> I don't know why the second line

I am guessing but look at /etc/network/interfaces. Remove or comment
out any interfaces you don't need. That includes eth0.

> appear; the third line looks really bad.

Not sure again, but to me it doesn't. I don't think this is your
problem.

> "route -n" seems normal

If normal means eth0 as default route, this explains your problem.

You need to think of ppp0 as your interface to the "internet". So
default route should go through ppp0.

Do you run a firewall? I use Shorewall. At one time, I am not sure
if my suggestion was accepted and included, the sample files
suggested that you should specify eth0 when you were using a cable
modem. With DHCP this is true, not so with pppoe.

Bob




Reply to: