Re: [expert] dhcpcd weirdness
lo is a loopback device which is not an actual device but allows your machine to see your machine, you should have an eth* if you want to see more than just your computer. "Corbett J. Klempay" wrote: > On Wed, 29 Sep 1999, Steve Philp wrote: > > > "Corbett J. Klempay" wrote: > > > > > I don't know if MandrakeSoft included the updated pump in their 6.1 > > release or not, but I recall seeing 6.0-era messages about the original > > pump not working with MS-DHCP. Might want to check for updated > > packages. > > > > Thanks, I will check. A related question...I went into linuxconf and told > it to set my network device (it is named lo in this case, not > eth0...anyone able to explain when it's lo and when it's eth0? I'm > guessing it has to do with this being an pcmcia card vs. a regular NIC, > right?) so that it uses DHCP on boot to get its IP. However, it will > always fail on boot (even when I am on my cable modem, where manual > works), since it tries to acquire via DHCP *before* the pcmcia stuff is > loaded...it obviously must be the other way around in order for the NIC to > even be available to get the IP. How do I fix this? > > > Oh, and dhcpd has been deprecated by the use of pump for address > > reception. > > > > Ah ok...I remembered seeing pump in RH as well. Anyone know why pump > > dhcpcd? > > Thanks! > > --- > Corbett J. Klempay > Trilogy Software, Inc. > 512.685.4193 (W) | 512.750.1372 (C) > [EMAIL PROTECTED]
RE: [expert] dhcpcd weirdness
I think lo is the loopback interface (a virtual interface for the machine to talk to itself) and not a physical device eth0 is the first ethernet device. ppp0 the first ppp device and so on. > -Original Message- > From: Corbett J. Klempay [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 29, 1999 12:45 AM > To: [EMAIL PROTECTED] > Subject: Re: [expert] dhcpcd weirdness > > > On Wed, 29 Sep 1999, Steve Philp wrote: > > > "Corbett J. Klempay" wrote: > > > > > I don't know if MandrakeSoft included the updated pump in their 6.1 > > release or not, but I recall seeing 6.0-era messages about > the original > > pump not working with MS-DHCP. Might want to check for updated > > packages. > > > > Thanks, I will check. A related question...I went into > linuxconf and told > it to set my network device (it is named lo in this case, not > eth0...anyone able to explain when it's lo and when it's eth0? I'm > guessing it has to do with this being an pcmcia card vs. a > regular NIC, > right?) so that it uses DHCP on boot to get its IP. However, it will > always fail on boot (even when I am on my cable modem, where manual > works), since it tries to acquire via DHCP *before* the > pcmcia stuff is > loaded...it obviously must be the other way around in order > for the NIC to > even be available to get the IP. How do I fix this? > > > Oh, and dhcpd has been deprecated by the use of pump for address > > reception. > > > > Ah ok...I remembered seeing pump in RH as well. Anyone know > why pump > > dhcpcd? > > Thanks! > > --- > Corbett J. Klempay > Trilogy Software, Inc. > 512.685.4193 (W) | 512.750.1372 (C) > [EMAIL PROTECTED] >
Re: [expert] dhcpcd weirdness
On Tue, 28 Sep 1999, Corbett J. Klempay wrote: > On Tue, 28 Sep 1999, Tom Berger wrote: > > > On Tue, 28 Sep 1999, you wrote: > > > Hey all...I just installed 6.1 (switching from RH 6.0). It's pretty > > > slick, btw. Anyway, my problem is this: I can plug this machine (Dell > > > Latitude CPt 333, 3c574 nic) in at home to my cable modem (Time Warner > > > Roadrunner), and have it get networking going just by typing 'dhcpcd'. > > > That's it. (I didn't try setting it to do it on boot; I just did that > > > since I've been here at work). However, at work, if I get out of NT and > > > into Linux, typing 'dhcpcd' will simply time out after a while. I have it > > > set to acquire via DHCP on boot now, and it fails when it tries then as > > > well. At first I might think it is something with the way the network is > > > set up here at work, but I don't think that should be it; when I still had > > > RH 6.0 on this machine, I could get an IP at work just fine. Any > > > suggestions? > > > > > > > Could you please see if this URL helps you? > > > > http://www.mandrakeuser.org/connect/ccable.html > > I think you may have misread my above message; I can get an IP via DHCP > when I am connected to my cable modem...it's at work on the regular > network here that I cannot get an IP. (while I used to be able to get an > IP at work when I had Red Hat 6.0) > Ok, i know whats going on here now. Redhat defaults to pump for dhcp, We default to dhcpcd. set your BOOTPROTO="pump" in /etc/sysconfig/network-scripts/ifcfg-ethX. You may have to switch between dhcpcd and pump, linuxconf should facilitate that easily. -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
Re: [expert] dhcpcd weirdness
From: Corbett J. Klempay <[EMAIL PROTECTED]> > Thanks, I will check. A related question...I went into linuxconf and told > it to set my network device (it is named lo in this case, not > eth0...anyone able to explain when it's lo and when it's eth0? I'm lo and eth0 are completely different devices. lo should always be set to 127.0.0.1, and would be unable to get an address via dhcp, since there isn't a dhcp server attached to it.
Re: [expert] dhcpcd weirdness
On Wed, 29 Sep 1999, Steve Philp wrote: > "Corbett J. Klempay" wrote: > > > I don't know if MandrakeSoft included the updated pump in their 6.1 > release or not, but I recall seeing 6.0-era messages about the original > pump not working with MS-DHCP. Might want to check for updated > packages. > Thanks, I will check. A related question...I went into linuxconf and told it to set my network device (it is named lo in this case, not eth0...anyone able to explain when it's lo and when it's eth0? I'm guessing it has to do with this being an pcmcia card vs. a regular NIC, right?) so that it uses DHCP on boot to get its IP. However, it will always fail on boot (even when I am on my cable modem, where manual works), since it tries to acquire via DHCP *before* the pcmcia stuff is loaded...it obviously must be the other way around in order for the NIC to even be available to get the IP. How do I fix this? > Oh, and dhcpd has been deprecated by the use of pump for address > reception. > Ah ok...I remembered seeing pump in RH as well. Anyone know why pump > dhcpcd? Thanks! --- Corbett J. Klempay Trilogy Software, Inc. 512.685.4193 (W) | 512.750.1372 (C) [EMAIL PROTECTED]
Re: [expert] dhcpcd weirdness
"Corbett J. Klempay" wrote: > > On Tue, 28 Sep 1999, Fred Frigerio wrote: > > > Are u using MS DHCP Server to serve out the IP's? I tried to implement > > it about 3-4 years ago and it would not follow the RFC so it would only > > work with Win95 and NT machines It couldn't serve Win3.1/Trumpet clients > > or anything else. Ended up using a Linux Machine to dish out IP's. > > I actually do not know for certain what the company is using to dish out > its IPs (UNIX vs. NT). I'm just a regular user on the network, and don't > admin anything. I would say it is very likely that the DHCP server *is* > NT based, however, given that it seems most everything else running the > network is NT-based. This would be a valid answer, however, except that > like I said, I had no problems getting an IP by manually running dhcpcd > when I was running Red Hat 6.0. (so in other words, the only thing that > has changed from when it used to work until now is that I'm now running > Mandrake 6.1) I don't know if MandrakeSoft included the updated pump in their 6.1 release or not, but I recall seeing 6.0-era messages about the original pump not working with MS-DHCP. Might want to check for updated packages. Oh, and dhcpd has been deprecated by the use of pump for address reception. -- Steve Philp "The Internet is like crack Network Administratorfor smart people..." Advance Packaging Corporation --Arsenio Hall [EMAIL PROTECTED]
Re: [expert] dhcpcd weirdness
On Tue, 28 Sep 1999, Tom Berger wrote: > On Tue, 28 Sep 1999, you wrote: > > Hey all...I just installed 6.1 (switching from RH 6.0). It's pretty > > slick, btw. Anyway, my problem is this: I can plug this machine (Dell > > Latitude CPt 333, 3c574 nic) in at home to my cable modem (Time Warner > > Roadrunner), and have it get networking going just by typing 'dhcpcd'. > > That's it. (I didn't try setting it to do it on boot; I just did that > > since I've been here at work). However, at work, if I get out of NT and > > into Linux, typing 'dhcpcd' will simply time out after a while. I have it > > set to acquire via DHCP on boot now, and it fails when it tries then as > > well. At first I might think it is something with the way the network is > > set up here at work, but I don't think that should be it; when I still had > > RH 6.0 on this machine, I could get an IP at work just fine. Any > > suggestions? > > > > Could you please see if this URL helps you? > > http://www.mandrakeuser.org/connect/ccable.html I think you may have misread my above message; I can get an IP via DHCP when I am connected to my cable modem...it's at work on the regular network here that I cannot get an IP. (while I used to be able to get an IP at work when I had Red Hat 6.0) --- Corbett J. Klempay Trilogy Software, Inc. 512.685.4193 (W) | 512.750.1372 (C) [EMAIL PROTECTED]
RE: [expert] dhcpcd weirdness
On Tue, 28 Sep 1999, Fred Frigerio wrote: > Are u using MS DHCP Server to serve out the IP's? I tried to implement > it about 3-4 years ago and it would not follow the RFC so it would only > work with Win95 and NT machines It couldn't serve Win3.1/Trumpet clients > or anything else. Ended up using a Linux Machine to dish out IP's. I actually do not know for certain what the company is using to dish out its IPs (UNIX vs. NT). I'm just a regular user on the network, and don't admin anything. I would say it is very likely that the DHCP server *is* NT based, however, given that it seems most everything else running the network is NT-based. This would be a valid answer, however, except that like I said, I had no problems getting an IP by manually running dhcpcd when I was running Red Hat 6.0. (so in other words, the only thing that has changed from when it used to work until now is that I'm now running Mandrake 6.1) --- Corbett J. Klempay Trilogy Software, Inc. 512.685.4193 (W) | 512.750.1372 (C) [EMAIL PROTECTED]
Re: [expert] dhcpcd weirdness
On Tue, 28 Sep 1999, you wrote: > Hey all...I just installed 6.1 (switching from RH 6.0). It's pretty > slick, btw. Anyway, my problem is this: I can plug this machine (Dell > Latitude CPt 333, 3c574 nic) in at home to my cable modem (Time Warner > Roadrunner), and have it get networking going just by typing 'dhcpcd'. > That's it. (I didn't try setting it to do it on boot; I just did that > since I've been here at work). However, at work, if I get out of NT and > into Linux, typing 'dhcpcd' will simply time out after a while. I have it > set to acquire via DHCP on boot now, and it fails when it tries then as > well. At first I might think it is something with the way the network is > set up here at work, but I don't think that should be it; when I still had > RH 6.0 on this machine, I could get an IP at work just fine. Any > suggestions? > > --- > Corbett J. Klempay > Trilogy Software, Inc. > 512.685.4193 (W) | 512.750.1372 (C) > [EMAIL PROTECTED] Could you please see if this URL helps you? http://www.mandrakeuser.org/connect/ccable.html Regards tom -- "Never trust a Shoggoth!" Thomas 'tom' Berger, [EMAIL PROTECTED] MandrakeUser.Org-Webservant UMS: +49-(0)89-1488-208756 fon: +49-(0)30-45809013
RE: [expert] dhcpcd weirdness
Are u using MS DHCP Server to serve out the IP's? I tried to implement it about 3-4 years ago and it would not follow the RFC so it would only work with Win95 and NT machines It couldn't serve Win3.1/Trumpet clients or anything else. Ended up using a Linux Machine to dish out IP's. > -Original Message- > From: Corbett J. Klempay [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 28, 1999 3:20 PM > To: [EMAIL PROTECTED] > Subject: [expert] dhcpcd weirdness > > > Hey all...I just installed 6.1 (switching from RH 6.0). It's pretty > slick, btw. Anyway, my problem is this: I can plug this machine (Dell > Latitude CPt 333, 3c574 nic) in at home to my cable modem (Time Warner > Roadrunner), and have it get networking going just by typing 'dhcpcd'. > That's it. (I didn't try setting it to do it on boot; I just did that > since I've been here at work). However, at work, if I get > out of NT and > into Linux, typing 'dhcpcd' will simply time out after a > while. I have it > set to acquire via DHCP on boot now, and it fails when it > tries then as > well. At first I might think it is something with the way > the network is > set up here at work, but I don't think that should be it; > when I still had > RH 6.0 on this machine, I could get an IP at work just fine. Any > suggestions? > > --- > Corbett J. Klempay > Trilogy Software, Inc. > 512.685.4193 (W) | 512.750.1372 (C) > [EMAIL PROTECTED] >
