[Leaf-user] Dachstein, Bearing, and DHCP
Greetings, For three years I used an old 486 running RH 5.2 as a router box. It was hooked to a cable modem one side and my local network on the other. It also ran as a file server under Samba, and used Apache to provide a web site for the local network only. Recently I graduated to Dachstein on a floppy because of hard disk failure on the old 486. Besides, I did not get that much use out of the web site or the file server. I have run Dachstein for several weeks. Very happy with it. I setup all my local network machines to work off DHCP. Last week I tried Bearing. It worked fine for about a day, then (when the previous lease expired?) my windows98 machine was assigned a local network address in the 169.-.-. range. The standard Bearing release evidently does not support DHCP for the local network. I forgot to go back and reconfigure the win machine not to use DHCP. Evidently, if windows is configured for DHCP and does not find a DHCP server, it auto assigns IP addresses. Just another of those 'special' features that is not well documented and causes confusion. So now I have a question. What is the advantage of using DHCP on a small local network? I only have five computers on the network. Would I be better off to manually assign IP numbers? The only reason I used DHCP on the local network was because Dachstein provided it. I did not select DHCP because I thought I needed it. However, it did work and was convenient. Are there better reasons to use DHCP on a local network? Thanks in advance, Frank Kamp ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Dachstein, Bearing, and DHCP
On Mon, 2002-04-08 at 15:24, [EMAIL PROTECTED] wrote: Greetings, Last week I tried Bearing. It worked fine for about a day, then (when the previous lease expired?) my windows98 machine was assigned a local network address in the 169.-.-. range. The standard Bearing release evidently does not support DHCP for the local network. I forgot to go back and reconfigure the win machine not to use DHCP. Evidently, if windows is configured for DHCP and does not find a DHCP server, it auto assigns IP addresses. Just another of those 'special' features that is not well documented and causes confusion. Actually, that 169.x.x.x address is part of the DHCP RFC. So it's not windows being stupid again, it's just doing what it should. Thanks in advance, Frank Kamp DHCP is nice because you can update your DNS cache servers or whatever and not have to go and log into 5 different machines to change the settings. Makes it easy when a friend comes over and wants to plug in their laptop. Z signature.asc Description: This is a digitally signed message part
Re: [Leaf-user] Dachstein, Bearing, and DHCP
Last week I tried Bearing. It worked fine for about a day, then (when the previous lease expired?) my windows98 machine was assigned a local network address in the 169.-.-. range. The standard Bearing release evidently does not support DHCP for the local network. I forgot to go back and reconfigure the win machine not to use DHCP. Evidently, if windows is configured for DHCP and does not find a DHCP server, it auto assigns IP addresses. Just another of those 'special' features that is not well documented and causes confusion. There is nothing special in Bering dhcpd (I guess you are talking about dhcpD -emphasis on the D-) since apparently you want to serve addresses to your internal network. In fact it is exactly the one used by Dachstein. It is on Bering disk but not activated by default since I think that it is useless for small networks. If you want to activate it just add it to the LRP= list in syslinux.cfg (by the way there is a doc on Bering and there is none on dhcpd since the one provided on Charles site is excellent) and you will be done. Jacques ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] Dachstein, Bearing, and DHCP
Frank, The primary reason a Network Administrator uses DHCP is LAZYness, ;-) instead of having to go around and hard set every client on a network, when you have 200+ clients it's a whole lot easier to allow the client to gain their IP address automatically. There are a few other reasons too... If you make configuration changes to the network ie new gateway IP or new DNS's these changes can happen dynamically at the client machine. It is mostly just a tool to make life easier, it is not required and in somecases ( like yours ) assigning 5 IP's to 5 machines and walking away is easier than going through the trouble of getting DHCP set up ( which really isn't too hard ). Either way you want to go is the right answer for you. Take care, Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Monday, April 08, 2002 1:24 PM To: [EMAIL PROTECTED] Subject: [Leaf-user] Dachstein, Bearing, and DHCP Greetings, For three years I used an old 486 running RH 5.2 as a router box. It was hooked to a cable modem one side and my local network on the other. It also ran as a file server under Samba, and used Apache to provide a web site for the local network only. Recently I graduated to Dachstein on a floppy because of hard disk failure on the old 486. Besides, I did not get that much use out of the web site or the file server. I have run Dachstein for several weeks. Very happy with it. I setup all my local network machines to work off DHCP. Last week I tried Bearing. It worked fine for about a day, then (when the previous lease expired?) my windows98 machine was assigned a local network address in the 169.-.-. range. The standard Bearing release evidently does not support DHCP for the local network. I forgot to go back and reconfigure the win machine not to use DHCP. Evidently, if windows is configured for DHCP and does not find a DHCP server, it auto assigns IP addresses. Just another of those 'special' features that is not well documented and causes confusion. So now I have a question. What is the advantage of using DHCP on a small local network? I only have five computers on the network. Would I be better off to manually assign IP numbers? The only reason I used DHCP on the local network was because Dachstein provided it. I did not select DHCP because I thought I needed it. However, it did work and was convenient. Are there better reasons to use DHCP on a local network? Thanks in advance, Frank Kamp ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user Sponsored by http://www.ThinkGeek.com/
Re: [Leaf-user] Dachstein, Bearing, and DHCP
At 08:26 PM 4/8/02 +, [EMAIL PROTECTED] wrote: it might help to set the 98 machines with the gateway of the router then do renew of address. This is simply wrong. When a system (any system) looks for a DHCP lease, it sends out a broadcast packet that any DHCP server on the same LAN should be able to see and respond to. Gateway address is normally part of a DHCP lease, and offhand I don't even know that it is possible to set a gateway address by hand on a machine that you are NOT also assigning an IP address to by hand. If the original poster has not been forcing a lease renewal, though, that is something he should do. Windows out of the box is designed to talk, thats why if it cant get an ip from dhcp server ..it will assign itself a number. It is well documented in windows 2000. This is correct. At others have noted, the 169.something-or-other addresses are a standard part of IP address standards. (A practical use for them, BTW, is direct connection of two laptops via a crossover cable.) -- Never tell me the odds!--- Ray Olszewski-- Han Solo Palo Alto, CA[EMAIL PROTECTED] ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user Sponsored by http://www.ThinkGeek.com/
