eth0 fighting ppp0 (maybe)
Hi, I wrote a little while ago about which module to use for my NIC. Well, Brian Moore provided me with the answer, which, well, worked a little too well I think. g I'm using Potato, as I mentioned, and I loaded the module 3c59x for my NIC. I'm at home right now, but I plan to take the box I'm working on back to the office to stick on the LAN to replace an, ehem, Red Hat box. I'm using a modem to apt-get stuff that I need so that I can get the box ready to go, but I've ran into a small problem. I fired up my connection, /var/log/messages said my connection appeared fine (plus my modem lights told me as well :-P). I have my resolv.conf entries in tact and I have my network settings set up properly. I went to use apt to get a few things and it just sat there, trying to connect. I took a closer look at /var/log/messages, and I now see an entry I didn't see before: pppd[334]: Serial Connection established pppd[334]: Using interface ppp0 pppd[334]: Connect: ppp0 -- /dev/ttyS0 pppd[334]: Remote message: Login Succeeded pppd[334]: found interface eth0 for proxy arp pppd[334]: local IP address 206.107.101.119 pppd[334]: remote IP address 206.107.101.159 The line referring to `eth0 for proxy arp' looks like the problem, because it's never been there before on a normal dial-up machine, but I'm not a network person (*gasp*). I can ping myself, of course, but I can't reach the outside world. Essentially, I'm just trying to get this thing setup to be able to plug it in the network and go, but for now I just need to be able to use ppp to get the packages I need. Is there a simple solution for this? Thank you very much, Brian
Re: eth0 fighting ppp0 (maybe)
On Sun, Mar 26, 2000 at 11:14:32PM -0500, Brian Clark wrote: Hi, I wrote a little while ago about which module to use for my NIC. Well, Brian Moore provided me with the answer, which, well, worked a little too well I think. g I'm using Potato, as I mentioned, and I loaded the module 3c59x for my NIC. I'm at home right now, but I plan to take the box I'm working on back to the office to stick on the LAN to replace an, ehem, Red Hat box. I'm using a modem to apt-get stuff that I need so that I can get the box ready to go, but I've ran into a small problem. I fired up my connection, /var/log/messages said my connection appeared fine (plus my modem lights told me as well :-P). I have my resolv.conf entries in tact and I have my network settings set up properly. I went to use apt to get a few things and it just sat there, trying to connect. I took a closer look at /var/log/messages, and I now see an entry I didn't see before: pppd[334]: Serial Connection established pppd[334]: Using interface ppp0 pppd[334]: Connect: ppp0 -- /dev/ttyS0 pppd[334]: Remote message: Login Succeeded pppd[334]: found interface eth0 for proxy arp pppd[334]: local IP address 206.107.101.119 pppd[334]: remote IP address 206.107.101.159 The line referring to `eth0 for proxy arp' looks like the problem, because it's never been there before on a normal dial-up machine, but I'm not a network person (*gasp*). I can ping myself, of course, but I can't reach the outside world. Essentially, I'm just trying to get this thing setup to be able to plug it in the network and go, but for now I just need to be able to use ppp to get the packages I need. You probably don't need proxy arp for anything, so comment out the proxyarp line in /etc/ppp/options. But, I'd suspect the default route might not be set to ppp0, but instead to eth0 -- check it with ifconfig. AFAIK, proxyarp is only necessary for when your machine is accepting dial-ins. -- ++ | Eric G. Milleregm2@jps.net | | GnuPG public key: http://www.jps.net/egm2/gpg.asc | ++
Re: eth0 fighting ppp0 (maybe)
Brian Clark writes: I have my resolv.conf entries in tact and I have my network settings set up properly. Do you have a default route pointing to eth0? If so, remove it. I can ping myself, of course, but I can't reach the outside world. Can you get anywhere using IP numbers? The line referring to `eth0 for proxy arp' looks like the problem,... It isn't. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
Re: eth0 fighting ppp0 (maybe)
John Hasler said: Brian Clark writes: I have my resolv.conf entries in tact and I have my network settings set up properly. Do you have a default route pointing to eth0? If so, remove it. I can ping myself, of course, but I can't reach the outside world. Can you get anywhere using IP numbers? The line referring to `eth0 for proxy arp' looks like the problem,... It isn't. Eric G . Miller said: You probably don't need proxy arp for anything, so comment out the proxyarp line in /etc/ppp/options. But, I'd suspect the default route might not be set to ppp0, but instead to eth0 -- check it with ifconfig. AFAIK, proxyarp is only necessary for when your machine is accepting dial-ins. Yes, I checked it with ifconfig and the first listing is eth0, then local loopback, then ppp0. This is embarrassing, but how do I temporarily change that? (I CC'd the list so maybe this would help someone else one day.) I checked /etc/ppp/options and all of my chatscripts but didn't see anything allowing me to specify anything. I want to be able to change this back when I plug into the LAN, of course. Thanks, Brian
Re: eth0 fighting ppp0 (maybe)
On Mon, Mar 27, 2000 at 12:56:03AM -0500, Brian Clark wrote: Eric G . Miller said: You probably don't need proxy arp for anything, so comment out the proxyarp line in /etc/ppp/options. But, I'd suspect the default route might not be set to ppp0, but instead to eth0 -- check it with ifconfig. AFAIK, proxyarp is only necessary for when your machine is accepting dial-ins. Yes, I checked it with ifconfig and the first listing is eth0, then local loopback, then ppp0. This is embarrassing, but how do I temporarily change that? (I CC'd the list so maybe this would help someone else one day.) I checked /etc/ppp/options and all of my chatscripts but didn't see anything allowing me to specify anything. If you set up ppp with pppconfig, it should have given you the option to set default route -- this is what you want for the moment. Have a look at the route command. Your /etc/ppp/peers/provider file should have a line like: defaultroute#pppconfig_route If you execute route you'll get a listing of what the OS knows about. You can manually set the default route with the destination address of the ppp0 interface. route add default gw xxx.xxx.xxx.xxx Easier to let ppp do it for you :). -- ++ | Eric G. Milleregm2@jps.net | | GnuPG public key: http://www.jps.net/egm2/gpg.asc | ++
Re: eth0 fighting ppp0 (maybe)
Eric G . Miller said: On Mon, Mar 27, 2000 at 12:56:03AM -0500, Brian Clark wrote: Eric G . Miller said: You probably don't need proxy arp for anything, so comment out the proxyarp line in /etc/ppp/options. But, I'd suspect the default route might not be set to ppp0, but instead to eth0 -- check it with ifconfig. AFAIK, proxyarp is only necessary for when your machine is accepting dial-ins. Yes, I checked it with ifconfig and the first listing is eth0, then local loopback, then ppp0. This is embarrassing, but how do I temporarily change that? (I CC'd the list so maybe this would help someone else one day.) I checked /etc/ppp/options and all of my chatscripts but didn't see anything allowing me to specify anything. If you set up ppp with pppconfig, it should have given you the option to set default route -- this is what you want for the moment. Have a look at the route command. Your /etc/ppp/peers/provider file should have a line like: defaultroute#pppconfig_route Yes, after playing with this for a while, along with the info you guys gave me, I figured out that the options files add the entry I get from ifconfig; ppp/options uses `deafultroute' to add it `on demand' it appears, but I don't know what network/options uses. If you execute route you'll get a listing of what the OS knows about. You can manually set the default route with the destination address of the ppp0 interface. route add default gw xxx.xxx.xxx.xxx Good to know.. Easier to let ppp do it for you :). But ooops! Before I got your mail, I just commented out the card's entry in /etc/network/options, but left in lo, and it appears to let me out now. I can ping anywhere fine now.. haven't tried apt. Correct me if I'm wrong (!), but so far I haven't gotten any funky results.. Thanks for all of your help.. Brian
