Re: DHCP client setup for @Home
Sorry to reply to my own mail, but hey, I finally got my cable connection working and I'm willing to share what I've learnt. ;-) The problems I experienced were with the method my cable provider uses to get their clients authenticated / initialized / connected. This is what happens: o First, you connect with some DHCP client program. You get an IP in the 10.x range. Then, you start your browser (lynx here) and you immediately jump onto a CISCO page where you are prompted to identify yourself with ID / password. o Having done that, it says that you are registered. The web page tells you to log off / restart your computer. Now here is where the problem lied. What I did was killall dhcpcd. That's *wrong*. I later found out about dhcpcd -k. (- wasn't documented anywhere!) Thing is, if I just kill the dhcpcd process, I don't correctly get logged off their system. And that led to the situation that I kept on getting DHCP_NAK in the logs the next time I tried to re-connect. Now that I am finally up and running here, I just need to configure some scripts, tweak some settings until I'm all set. :) I hope these infos are of some help to someone experiencing similar problems sometime later. :) (Cable speed rocks. Throughput averages at ~15 to 20KB/s) Regards Sven -- The best way to escape from a problem is to solve it.
Re: DHCP client setup for @Home
On Sat, 9 Sep 2000, S.Salman Ahmed wrote: I just tried installing Potato using the latest boot floppies (compact set) and had the same result - pump failed to get configuration info using DHCP. I ended up statically configuring the ethernet card in my system using the same values as would/should have been obtained through DHCP. With Rogers I use dhcpcd. It allows you to specify a username, which Rogers requires. Works great for me. Mike
Re: DHCP client setup for @Home
A long time ago, in a galaxy far, far way, someone said... So, does this mean that if I try and install potato on my home system using the boot floppies (to avoid having to burn 1 or more CDs) and I select the DHCP net configuration option for doing a network/internet install that the installation will fail ? In my experience it does: pump fails to correctly configure /etc/resolv.conf which kinda makes installing off a network kinda hard. Is this a bug in pump ? If it fails to work (for an @Home setup like mine) then why is pump allowed into potato or debian at all ? Bug in pump: unknown to me. the code is in the executable, but it doesn't seem to work. My experience: I've tried a couple times to install pump on a SPARC classic, and used DHCP to configure the interface. When it came time to install the base system (there's no CD and it's a blank HD) I had to use the NFS server's IP number rather than the hostname: DNS lookups were failing. After the system was installed and running, trying to fix /etc/resolv.conf showed me the file didn't exist. pump in potato: I dunno. Lack of disk space? I plan to reinstall potato on my home system using the boot floppies over the weekend and will see how well the DHCP configuration works then. Let me know, you might have better luck on a PC. -- -- Phil Brutsche [EMAIL PROTECTED] There are two things that are infinite; Human stupidity and the universe. And I'm not sure about the universe. - Albert Einstien
Re: DHCP client setup for @Home
I used the boot floppies, and it worked with my cable modem. I guess I didn't know it was using pump, it just worked by magic. I went ahead and installed dhcpcd when I was done. BTW, make sure you get root.bin, resc.bin, plus all three driver floppies BEFORE you start the installation and blow away your hard drive. I'll leave it as an exercise to the reader why I wanted to stress this point. ;-) John Is this a bug in pump ? If it fails to work (for an @Home setup like mine) then why is pump allowed into potato or debian at all ? I plan to reinstall potato on my home system using the boot floppies over the weekend and will see how well the DHCP configuration works then. -- Salman Ahmed ssahmed AT pathcom DOT com
Re: DHCP client setup for @Home
I'm on @home as well, and pump just failed badly for me. However, dhcpcd worked out of the box, so to say: dhcpcd -h XXX did the job right then. Andrei -- First there was Explorer... Then came Expedition. This summer Coming to a street near you.. Ford Exterminator. -- Andrei Ivanov http://arshes.dyndns.org [EMAIL PROTECTED] 12402354 --
Re: DHCP client setup for @Home
A long time ago, in a galaxy far, far way, someone said... I was able to figure out the problem myself. For some reason, I was unable to get Pump to work with the [EMAIL PROTECTED] DHCP servers. I then remembered that there was another DHCP client, dhcp-client, which I have used earlier on one of our office machines. dhclient (that's the name of the executable in the dhcp-client package) is the best (imo) dhcp client for unix-type systems. That would explain why NetBSD, OpenBSD, and FreeBSD use dhclient in their bootup sequence when you select automatic interface configuration (or something like that). IMO the only reason pump is being used is lack of space on the root floppy. I installed dhcp-client and added a couple of lines to /etc/dhclient.conf and voila! I have a fast cable-modem connection. Not sure what I was doing wrong with Pump. You weren't doing anything wrong. pump simply doesn't work very well. -- -- Phil Brutsche [EMAIL PROTECTED] There are two things that are infinite; Human stupidity and the universe. And I'm not sure about the universe. - Albert Einstien
Re: DHCP client setup for @Home
On Wed, Sep 06, 2000 at 11:30:13AM -0500, Phil Brutsche wrote: dhclient (that's the name of the executable in the dhcp-client package) is the best (imo) dhcp client for unix-type systems. That would explain why NetBSD, OpenBSD, and FreeBSD use dhclient in their bootup sequence when you select automatic interface configuration (or something like that). How about dhcpcd? **--**--** Package: dhcpcd Priority: optional Section: net Installed-Size: 102 Maintainer: Dennis Kelly [EMAIL PROTECTED] Architecture: i386 Version: 1:1.3.17pl2-8 Replaces: dhcpcd-sv Depends: libc6 (= 2.1.2) Conflicts: dhcpcd-sv Filename: dists/stable/main/binary-i386/net/dhcpcd_1.3.17pl2-8.deb Size: 37178 MD5sum: c843acf777bf739206ccfca1769de412 Description: DHCP client for automatically configuring IPv4 networking This package contains both the 0.70 and 1.3.x version of dhcpcd and should work with any Linux kernel. **--**--** Thing is, I am having trouble with getting my cable connection working. I can use dhcpcd eth0 to get connected. I get an IP address, my default route gets set, and my /etc/resolv.conf is changed. So far so good, all *seems* well. Now, what I can do is ping the default gateway, but not the DHCP server. Also, I cannot resolve DNS names. Can anyone judge to say what *could* be the problem? Thing is exactly the same situation occurs under WinDos. (Them stupid support folks first told me to use WinDos instead of Linux - they don't support Linux!) Anyway, I am waiting for the cable company to respond / fix the problems. My guess is that their network is somewhat fsck'ed. You weren't doing anything wrong. pump simply doesn't work very well. Has anyone ever had any problems when using dhcpcd instead of dhclient? I never tried dhclient. Thanks Sven -- The program required me to install Windows 95 or better ... ... so I installed Linux.
Re: DHCP client setup for @Home
Oh, no, dhcpd is the server software. That won't work at all, unless you are on contract with @home to provide this service:^) In fact, you might be handing out addresses to @home customers who wonder why it doesn't work. What they don't tell you about @home is that they use static ip addresses, they just make you get it with dhcp. If you have the information, you can just set it up normally and not dink around with all this dhcp junk. I think it's supposed to make it easier on tech support if they tell you all the addresses through dhcp. I've been running two boxen for about 4 months without a problem--all using static IP. If you have the work order that they gave you with the other goodies, you can look on it and it will have all the info you need, or if you have another working setup, you can look to see what the settings are. Then set up a normal network with /etc/network/interfaces and resolv.conf. Sven Burgener wrote: On Wed, Sep 06, 2000 at 11:30:13AM -0500, Phil Brutsche wrote: dhclient (that's the name of the executable in the dhcp-client package) is the best (imo) dhcp client for unix-type systems. That would explain why NetBSD, OpenBSD, and FreeBSD use dhclient in their bootup sequence when you select automatic interface configuration (or something like that). How about dhcpcd? **--**--** Package: dhcpcd Priority: optional Section: net Installed-Size: 102 Maintainer: Dennis Kelly [EMAIL PROTECTED] Architecture: i386 Version: 1:1.3.17pl2-8 Replaces: dhcpcd-sv Depends: libc6 (= 2.1.2) Conflicts: dhcpcd-sv Filename: dists/stable/main/binary-i386/net/dhcpcd_1.3.17pl2-8.deb Size: 37178 MD5sum: c843acf777bf739206ccfca1769de412 Description: DHCP client for automatically configuring IPv4 networking This package contains both the 0.70 and 1.3.x version of dhcpcd and should work with any Linux kernel. **--**--** Thing is, I am having trouble with getting my cable connection working. I can use dhcpcd eth0 to get connected. I get an IP address, my default route gets set, and my /etc/resolv.conf is changed. So far so good, all *seems* well. Now, what I can do is ping the default gateway, but not the DHCP server. Also, I cannot resolve DNS names. Can anyone judge to say what *could* be the problem? Thing is exactly the same situation occurs under WinDos. (Them stupid support folks first told me to use WinDos instead of Linux - they don't support Linux!) Anyway, I am waiting for the cable company to respond / fix the problems. My guess is that their network is somewhat fsck'ed. You weren't doing anything wrong. pump simply doesn't work very well. Has anyone ever had any problems when using dhcpcd instead of dhclient? I never tried dhclient. Thanks Sven -- The program required me to install Windows 95 or better ... ... so I installed Linux. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: DHCP client setup for @Home
Read Sven's message below again - dhcpcd - this is not server software. This is what I use for my cable modem connection. It worked for me before I even had a clue what I was doing! It automatically is assigned the DNS servers, etc, so all you need to do is turn it on and it works (even easier than static IP), unless @home doesn't do pure DHCP. Also, just because DHCP is used, doesn't mean that the IP address assigned to a MAC address WILL change, just don't assume it will never change, or things might be very broken when they do. John On Wed, 6 Sep 2000, Michael Smith wrote: Oh, no, dhcpd is the server software. That won't work at all, unless you are on contract with @home to provide this service:^) In fact, you might be handing out addresses to @home customers who wonder why it doesn't work. What they don't tell you about @home is that they use static ip addresses, they just make you get it with dhcp. If you have the information, you can just set it up normally and not dink around with all this dhcp junk. I think it's supposed to make it easier on tech support if they tell you all the addresses through dhcp. I've been running two boxen for about 4 months without a problem--all using static IP. If you have the work order that they gave you with the other goodies, you can look on it and it will have all the info you need, or if you have another working setup, you can look to see what the settings are. Then set up a normal network with /etc/network/interfaces and resolv.conf. Sven Burgener wrote: On Wed, Sep 06, 2000 at 11:30:13AM -0500, Phil Brutsche wrote: dhclient (that's the name of the executable in the dhcp-client package) is the best (imo) dhcp client for unix-type systems. That would explain why NetBSD, OpenBSD, and FreeBSD use dhclient in their bootup sequence when you select automatic interface configuration (or something like that). How about dhcpcd? **--**--** Package: dhcpcd Priority: optional Section: net Installed-Size: 102 Maintainer: Dennis Kelly [EMAIL PROTECTED] Architecture: i386 Version: 1:1.3.17pl2-8 Replaces: dhcpcd-sv Depends: libc6 (= 2.1.2) Conflicts: dhcpcd-sv Filename: dists/stable/main/binary-i386/net/dhcpcd_1.3.17pl2-8.deb Size: 37178 MD5sum: c843acf777bf739206ccfca1769de412 Description: DHCP client for automatically configuring IPv4 networking This package contains both the 0.70 and 1.3.x version of dhcpcd and should work with any Linux kernel. **--**--** Thing is, I am having trouble with getting my cable connection working. I can use dhcpcd eth0 to get connected. I get an IP address, my default route gets set, and my /etc/resolv.conf is changed. So far so good, all *seems* well. Now, what I can do is ping the default gateway, but not the DHCP server. Also, I cannot resolve DNS names. Can anyone judge to say what *could* be the problem? Thing is exactly the same situation occurs under WinDos. (Them stupid support folks first told me to use WinDos instead of Linux - they don't support Linux!) Anyway, I am waiting for the cable company to respond / fix the problems. My guess is that their network is somewhat fsck'ed. You weren't doing anything wrong. pump simply doesn't work very well. Has anyone ever had any problems when using dhcpcd instead of dhclient? I never tried dhclient. Thanks Sven -- The program required me to install Windows 95 or better ... ... so I installed Linux. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: DHCP client setup for @Home
Yeah, there's that, but from all the inquiring I have done, that address is pretty much unchanging. The problem I've found with @home, at least in Eugene, OR, is that they use alot of mystique to describe what they do, like it's magic or something, when all they really do is pass packets and run DNS and mail servers, maybe occassionally probe you on port 119 to see if you're running a news server. Trust us, it's faster is about all the tech data you get around here. Maybe they aren't used to talking to people who actually do networking for a living. Oh, well, that's life. John Reinke wrote: Also, just because DHCP is used, doesn't mean that the IP address assigned to a MAC address WILL change, just don't assume it will never change, or things might be very broken when they do.
Re: DHCP client setup for @Home
On Wed, Sep 06, 2000 at 01:53:19PM -0500, John Reinke wrote: Read Sven's message below again - dhcpcd - this is not server software. Yup, note the 'c' in dhcpcd. Stands for client. And the binary behaves like a daemon in the way that it disconnects from the terminal and keeps running the way usual daemons do - in the background. That's why there's also a 'd' in it. # sudo dhcpcd --help DHCP Client Daemon v.1.3 [snip] It worked for me before I even had a clue what I was doing! Same here. With the exception of not being able to actually do much more than signing on. (Just as I explained in my original mail) It automatically is assigned the DNS servers, etc, so all you need to do is turn it on and it works (even easier than static IP), unless @home doesn't do pure DHCP. Oops, perhaps I should have stated that I do *not* use @home. I am not located in the United States, but in Switzerland, Europe. Oh, incase it matters: I'm running potato. Regards Sven -- The program required me to install Windows 95 or better ... ... so I installed Linux.
