At 01:32 PM 10/10/2005 -0400, James Knott wrote:
elefino wrote:
Hello list.
I don't know how much info is "enough" (versus too much, or not enough).
To make my current SuSE box serve a few things on my little home network (files and mail) I was advised to set the SuSE box up with a static address, rather than whatever my LinkSys WRT54G router hands out via dhcp.
I use YaST Control Center > Network Devices > Network Card dialog to edit the entry for "AOPEN RTL-8139/8139C/8139CC+ DHCP" to set a static address, instead of looking for a dhcp handout.
When I save the changes, and YaST updates whatever it updates, I am immediately unable to reach the internet. Apparently, I can still reach the configuration HTTP server inside the LinkSys, but nothing beyond it.
When you use static configuration, you also have to specify a default route and DNS server. Those are normally provided by a DHCP server. Incidentally, with some routers, you can lock a computer to a specific address, even though you're using DHCP. I don't know if yours supports that.
Static addressing and router-assigned "static" addressing are two different animal, which you guys are mixing up willy-nilly here. It's not dependent on what router you have (or only on what router you have) its dependent on what mode your choose. Classic static addresses are used 1. where there is no DHCP service available. DHCP services can run on a server, or a buncha servers, like I'm used to un a corporate environment, or on a little tiny router, like we have in the home or SOHO setting. Or 2. you may see static addresses on devices say for example in the corporate environment such as printers, or servers, for which that address must always be the same and never change. For routers, the IP can't CAn't CAN'T change. Do we all understand that the IP address you get handed when you boot your machine in a DHCP environment is DYNAMIC, meaning it can change? That's what the D in DHCP is for. Just because you all use DLINK, LinkSys, and other small routers intended for the home market, on relatively small subnets, with long DHCP lease times, and rarely see the IP address change, doesn't mean it can't. When a DHCP enabled machine boots up, it has no IP, subnet mask, default gateway, perhaps no DNS servers. It asks if there's a DHCP server around and if it could please have an IP assigned. Most of them will try to give it the one it had most recently. But this is not a requirement. If it's been off the network for much longer than the lease period, it may get a different one. SO if you use a static address, you MUST make sure you choose one that's 1. Not used by anyone else and 2. NOT in the DHCP pool used by the DHCP server to hand out addresses. Some DHCP servers (on little routers) come out of the box handing out 192.168.0.100 through .254 as the DHCP pool. This means that you can use 192.168.0.2 through 99 for your static addresses, if you 1. keep a list and don't duplicate any and 2. set the router up as 192.168.0.1 THE THIRD TYPE of address under discussion here isn't static, or DHCP. It's kind of a hybrid. The device (workstation, etc) is set to get an address from the DHCP service, just like any other machine. In Winders, you tell it "Obtain an IP address automatically." BUT, the DHCP server is told that "WHENEVER a device with mac (physical) address aabbcc-ddeeff asks for an DHCP lease (IP address, etc) ALWAYS give it this one: zzz.yyy.xxx.www" This is a way of configuring all machines the same way, yet making sure that a machine you have to be able to find by IP address always has the same one. And yes, the DHCP server (router, in this case) has to be able to support it. Typically, it's in an advanced services menu. Hope this helps. -T [Risk] To do an evil act is base. To do a good one without incurring danger, is common enough. But it is part of a good man to do great and noble deeds though he risks everything in doing them. --Plutarch --... ...-- -.. . -. ----. --.- --.- -... tpeters@nospam.mixcom.com (remove "nospam") N9QQB (amateur radio) "HEY YOU" (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2" N by 88° 6' 28.9" W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531