Cannot determine ethernet address for proxy ARP
 

This is what syslog tells me when I try to call a site on the internet in Slack 10, and I have not the foggiest idea what it means. I have Slack 10 on an identical machine working fine but just put it on this one yesterday and this is what I get. Opera says it cannot connect to remote host and Links says No route to host.

I have installed everything in the n folder from the CD and cannot think of anything different here from the other set that works. ARP appears from the HOWTOs to be some sort of local network thing so it seems as if perhaps the machine is trying to look for perhaps eth0 instead of ppp0?? Can anyone help please. I use wvdial and definitely get a pppd connection.

Did you compare /etc/rc.d/rc.inet1.conf in both machines ?

Both the same - all null entries. However, I solved it. Tried telnet and gftp and the errors were both to do with failure in name resolution and inability to look up hostname. This rang a bell in the depths of my memory and I checked /etc/resolv.conf. Bingo!! No address. But why should that be?

normally the adress of your router or isp.
can't you look what's in it on the other machine ?

egag

Yes, that's just what I did - hence the Bingo!!. But I do not understand why it was not there - presumably something in the system should have put it there for me?

I had to install a special driver for my Winmodem; could that have affected things? How does the address get there normally? Presumably copying it from another machine is not the normally expected procedure.

those config-files are written by the " netconfig " script.
you can take a look at it to see what it does ( /sbin/netconfig )

egag

Cannot determine ethernet address for proxy ARP
 

I got this message from our pppd server when I set the proxyarp option, but the IP addresses I used for the pppd client and pppd server weren't on the same subnet as the ethernet port on the ppp server.

Buried deep inside the pppd man page under the "Routing" heading it says: "The proxyarp option causes pppd to look for a network interface on the same subnet as the remote host (an interface supporting broadcast and ARP, which is up and not a point-to-point or loopback interface)."

Once I switched to using IP addresses on the same subnet, everything worked.
("Cannot determine ethernet address for proxy ARP" error message)
ppp server$ sudo pppd /dev/ttyUSB0 921600 xonxoff nodetach ktune proxyarp lcp-echo-interval 30 lcp-echo-failure 4 remotename target-0 ms-dns 10.100.13.21 ms-dns 10.100.13.22 debug 192.168.20.64:192.168.20.65
ppp client $ sudo pppd /dev/ttyPS1 921600 xonxoff nodetach lock name target-0 password xyzpdq nodetach lcp-echo-interval 30 lcp-echo-failure 4 defaultroute usepeerdns debug &


(No error message. Use IP addresses on same subnet as the ethernet port of ppp server)
ppp server $ ip addr
.
.
.
2: ...
inet 10.100.92.51/23 brd 10.100.93.255 scope global dynamic enp1s0
...
ppp server $ sudo pppd /dev/ttyUSB0 921600 xonxoff nodetach ktune proxyarp lcp-echo-interval 30 lcp-echo-failure 4 remotename target-0 ms-dns 10.100.13.21 ms-dns 10.100.13.22 debug 10.100.92.64:10.100.92.65