Once upon a time Ricardo Diz said... > > I've installed the lastest pppoe and pppoeconfig (I'm running unstable) > and it all promised to be quite simple. I used pppoeconfig for setting > things up and it seemed to work fine until it started the connection. > 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;
Assuming that your dsl modem is plugged into eth0, then eth0 is used only as a physical connection to the modem. Its not an IP layer connection, so eth0 does not get or need an IP address. pppoe will just stick the ppp packets on the wire for the modem to receive. The IP layer is encapsulated in the ppp packets. > I don't know why the second line appear; This looks like the problem. You need your default route to be going to the ppp interface, but its currently going to eth0. You can ping the remote end of the link because there should be a direct route to that IP address. Anything else is going via eth0, which is not your IP layer interface to the internet. To fix this, put the line 'defaultroute' in /etc/ppp/peers/dsl-provider. > the third line looks really bad. No, it wont be a problem. You can get rid of the error message by adding 'noproxyarp' to /etc/ppp/peers/dsl-provider. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
