[edgy] pppd does not correctly work with pptpconfig

I am having a similar problem as well.

the ppp0 interface goes up and mppe is enabled, but routing is never setup.

-----

Using interface ppp0
pptpconfig: monitoring interface ppp0

Connect: ppp0 <--> /dev/pts/2
CHAP authentication succeeded
MPPE 128-bit stateless compression enabled
Cannot determine ethernet address for proxy ARP

I see the same error message: Cannot determine ethernet address for proxy ARP

I am using PPTP in kvpnc on edgy.

I am not sure if this is a bug or a feature (me doing a configuration bug). More browsing of FAQs is required.

On 11/5/06, Christian Haeberli <email address hidden> wrote:
> I see the same error message: Cannot determine ethernet address for
> proxy ARP
>
> I am using PPTP in kvpnc on edgy.
>
> I am not sure if this is a bug or a feature (me doing a configuration
> bug). More browsing of FAQs is required.

However, you will find that setting up the tunnel and running it with pon works.

--
Will Dyson

The result of some more investigation is:
The message "Cannot determine ethernet address for proxy ARP" does not point to the problem, but causes the problem.

In older Ubuntu releases (e.g. breezy) this message pops up as well, but the pptpconfig does not care. With edgy, it seems that pptpconfig suddenly get's confused by that. Probably because an error code is generated somewhere in the tool chain due to that message.

Getting closer - further investigation is needed.

Still does not work in feisty here. Everything is configured properly but hangs in pptpconfig.
Workaround for the desperate:
You can start the connection manually with "pon <name>" after you configured it in pptpconfig.
This should create an additional interface like "ppp1". You can check with "ifconfig".
I have written this script:

#!/bin/sh
echo Connecting...
sudo pon myoffice
echo Waiting 10 seconds...
sleep 10
echo Adding routes...
sudo route add -net 192.168.150.0 netmask 255.255.255.0 dev ppp1
sudo route add -net 192.168.3.0 netmask 255.255.255.0 dev ppp1
echo Changing nameserver...
sudo sh -c "echo 'nameserver 192.168.150.6' > /etc/resolv.conf"
echo OK

IMPORTANT: You need to save you current nameservers in /etc/resolv.conf as /etc/resolv.good before and use the following script to close the connection again:

#!/bin/sh
sudo cp /etc/resolv.good /etc/resolv.conf
sudo poff myoffice

Not very comfortable, but the only way to get a connection right now in feisty. KVpnc doesnt work either. I suppose for the same reasons. I even tried the somewhat new network-manager which didnt find any interface at all.

Is this bug still present in Hardy or Intrepid?

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

problem in ubuntu intrepid also

hey i have been facing the same problem with ubuntu intrepid also.....

my connection used to work properly but i changed the modem and did the pppoeconf thingy , its a different connection from the same isp (bsnl -india)

now i get the message "alienware pppd[17610]: Cannot determine ethernet address for proxy ARP"
in plog and my internet stops working after sometime................ sometimes in like 10mins if its left ideal.......

after the net stops working ppp0 is still connected........... i can ping the modem but not any www sites........ ping www.google.com returns "unknown host"

/etc/resolv.conf still has the valid nameservers............ only error i c is "alienware pppd[17610]: Cannot determine ethernet address for proxy ARP" could this be the problem...... reopening the bug.
also i have not been able to find any useful info else where after like a week of googling...

thnx

Dec 30 09:09:21 alienware pppd[17608]: Plugin rp-pppoe.so loaded.
Dec 30 09:09:21 alienware pppd[17610]: pppd 2.4.4 started by root, uid 0
Dec 30 09:09:21 alienware pppd[17610]: PPP session is 3835
Dec 30 09:09:21 alienware pppd[17610]: Using interface ppp0
Dec 30 09:09:21 alienware pppd[17610]: Connect: ppp0 <--> eth0
Dec 30 09:09:24 alienware pppd[17610]: CHAP authentication succeeded: Authentication success,Welcome!
Dec 30 09:09:24 alienware pppd[17610]: CHAP authentication succeeded
Dec 30 09:09:24 alienware pppd[17610]: peer from calling number 00:E0:FC:46:20:C7 authorized
Dec 30 09:09:27 alienware pppd[17610]: replacing old default route to eth0 [192.168.1.1]
Dec 30 09:09:27 alienware pppd[17610]: Cannot determine ethernet address for proxy ARP
Dec 30 09:09:27 alienware pppd[17610]: local IP address 59.93.207.188
Dec 30 09:09:27 alienware pppd[17610]: remote IP address 59.93.192.1
Dec 30 09:09:27 alienware pppd[17610]: primary DNS address 218.248.240.179
Dec 30 09:09:27 alienware pppd[17610]: secondary DNS address 218.248.240.79
Dec 30 09:17:01 alienware /USR/SBIN/CRON[18125]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 30 09:24:16 alienware dhclient: DHCPREQUEST of 192.168.1.2 on eth0 to 192.168.1.1 port 67
Dec 30 09:24:16 alienware dhclient: DHCPACK of 192.168.1.2 from 192.168.1.1
Dec 30 09:24:16 alienware dhclient: bound to 192.168.1.2 -- renewal in 1545 seconds.
Dec 30 09:27:55 alienware pppd[17610]: Terminating on signal 15
Dec 30 09:27:55 alienware pppd[17610]: Connect time 18.5 minutes.
Dec 30 09:27:55 alienware pppd[17610]: Sent 709521 bytes, received 1348422 bytes.
Dec 30 09:27:55 alienware pppd[17610]: restoring old default route to eth0 [192.168.1.1]
Dec 30 09:27:55 alienware pppd[17610]: Connection terminated.
Dec 30 09:27:55 alienware pppd[17610]: Exit.
Dec 30 09:28:01 alienware pppd[18962]: Plugin rp-pppoe.so loaded.
Dec 30 09:28:01 alienware pppd[18964]: pppd 2.4.4 started by root, uid 0
Dec 30 09:28:01 alienware pppd[18964]: PPP session is 1885
Dec 30 09:28:01 alienware pppd[18964]: Using interface ppp0
Dec 30 09:28:01 alienware pppd[18964]: Connect: ppp0 <--> eth0
Dec 30 09:28:04 alienware pppd[18964]: CHAP authentication succeeded: Authentication success,Welcome!
Dec 30 09:28:04 alienware pppd[18964]: CHAP authentication succeeded
Dec 30 09:28:04 alienware pppd[18964]: peer from calling number 00:E0:FC:46:20:C7 authorized
Dec 30 09:28:04 alienware pppd[18964]: replacing old default route to eth0 [192.168.1.1]
Dec 30 09:28:04 alienware pppd[18964]: Cannot determine ethernet address for proxy ARP
Dec 30 09:28:04 alienware pppd[18964]: local IP address 59.93.194.212
Dec 30 09:28:04 alienware pppd[18964]: remote IP address 59.93.192.1
Dec 30 09:28:04 alienware pppd[18964]: primary DNS address 218.248.240.179
Dec 30 09:28:04 alienware pppd[18964]: secondary DNS address 218.248.240.79
Dec 30 09:41:34 alienware -- MARK --
Dec 30 09:50:01 alienware dhclient: DHCPREQUEST of 192.168.1.2 on eth0 to 192.168.1.1 port 67
Dec 30 09:50:01 alienware dhclient: DHCPACK of 192.168.1.2 from 192.168.1.1
Dec 30 09:50:01 alienware dhclient: bound to 192.168.1.2 -- renewal in 1629 seconds.
Dec 30 09:53:57 alienware ke...

Four releases old

well i faced the problem in ubuntu intrepid 8.10....