SuSE 10.0 with LinkSys - DHCP or Static
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 I edit the Network Card entry (in this SuSE box) back to dhcp, then as soon as I save, I immediately regain browser and e-mail access. WHY? Would this be the SuSE box refusing to play with the LinkSys, or would it be the LinkSys, pissed off that the SuSE box no longer wants to use the dhcp addresses that the LinkSys doles out? On the LinkSys, the mask is 255.255.255.0. The LinkSys box itself is at 192.168.1.1. I've tried giving this SuSE box static addresses all up and down the 192.168.1.10-though-253 range (not every possible address in the space, but a selection , widely scattered in that space) with the same result every time. If the SuSE box is not using a dynamically assigned address, then it's not getting access to the internet. I have tried switching the LinkSys' dhcp server off. It still does not wish to recognize an attached computer that has the effrontery to specify its own address. Browsing and mail work fine when I let the LinkSys dhcp specify everybody's address. What am I overlooking? See these bruises on my forehead? That's from slapping myself for not recognizing stupidly-obvious things. There'll be another, fresh bruise when somebody points out the blindingly obvious thing that I'm overlooking here. But please don't let that stop you. :-) SUMMARY I want to assign static addresses to at least one (this PC that I'm writing from) computer on my network, and have my LinkSys router accept that address and not ignore it. What needs to be done here? Both ends. Thank you, Kevin
Did you check your default gateway was set to 192.168.1.1? On Mon, 10 Oct 2005 12:00:23 -0400, 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 I edit the Network Card entry (in this SuSE box) back to dhcp, then as soon as I save, I immediately regain browser and e-mail access.
WHY? Would this be the SuSE box refusing to play with the LinkSys, or would it be the LinkSys, pissed off that the SuSE box no longer wants to use the dhcp addresses that the LinkSys doles out?
On the LinkSys, the mask is 255.255.255.0. The LinkSys box itself is at 192.168.1.1. I've tried giving this SuSE box static addresses all up and down the 192.168.1.10-though-253 range (not every possible address in the space, but a selection , widely scattered in that space) with the same result every time. If the SuSE box is not using a dynamically assigned address, then it's not getting access to the internet.
I have tried switching the LinkSys' dhcp server off. It still does not wish to recognize an attached computer that has the effrontery to specify its own address.
Browsing and mail work fine when I let the LinkSys dhcp specify everybody's address. What am I overlooking?
See these bruises on my forehead? That's from slapping myself for not recognizing stupidly-obvious things. There'll be another, fresh bruise when somebody points out the blindingly obvious thing that I'm overlooking here. But please don't let that stop you. :-)
SUMMARY I want to assign static addresses to at least one (this PC that I'm writing from) computer on my network, and have my LinkSys router accept that address and not ignore it. What needs to be done here? Both ends.
Thank you,
Kevin
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
El Lunes, 10 de Octubre de 2005 10:00, elefino escribió:
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.
Check if your LinkSys will let you assign "Static DHCP" addresses. My D-Link has a configuration option under DHCP that does that: Static DHCP Static DHCP is used to allow DHCP server to assign same IP address to specific MAC address. You need to let your router assign the addresses for IP Masquerading to work, which is needed for accessing the Internet. Also. make sure your GW is assigned your router's IP address. In my case, that's 192.168.0.1. In your case, it should be 192.168.1.1. HTH. Regards. -- Alfredo J. Cole Grupo ACyC
On Monday 10 October 2005 12:50 pm, Alfredo Cole wrote:
Check if your LinkSys will let you assign "Static DHCP" addresses. My D-Link has a configuration option under DHCP that does that:
Static DHCP Static DHCP is used to allow DHCP server to assign same IP address to specific MAC address.
You need to let your router assign the addresses for IP Masquerading to work, which is needed for accessing the Internet.
I don't believe this is a requirement. As long as all the machines talking to the router are on the same subnet as the router, masquerading should be in effect for them. Works for me on my Dlink router.
Also. make sure your GW is assigned your router's IP address. In my case, that's 192.168.0.1. In your case, it should be 192.168.1.1.
On Mon, 2005-10-10 at 10:50 -0600, Alfredo Cole wrote:
El Lunes, 10 de Octubre de 2005 10:00, elefino escribió:
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.
Check if your LinkSys will let you assign "Static DHCP" addresses. My D-Link has a configuration option under DHCP that does that:
Static DHCP Static DHCP is used to allow DHCP server to assign same IP address to specific MAC address.
Yes it will, I have the same model. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Alfredo Cole wrote:
You need to let your router assign the addresses for IP Masquerading to work, which is needed for accessing the Internet.
Why??? What difference is there between a static address and a DHCP address that would make a difference to IP Masquerading?
El Lunes, 10 de Octubre de 2005 11:38, James Knott escribió:
Alfredo Cole wrote:
You need to let your router assign the addresses for IP Masquerading to work, which is needed for accessing the Internet.
Why???
What difference is there between a static address and a DHCP address that would make a difference to IP Masquerading?
Nothing, actually, but that way you don't have to specify DNS servers. The DHCP server takes care of that. Regards. -- Alfredo J. Cole Grupo ACyC
On Monday 10 October 2005 03:53 pm, Alfredo Cole wrote:
Nothing, actually, but that way you don't have to specify DNS servers. The DHCP server takes care of that.
If you point your /etc/resolv.conf to your router..... with no dhcp involved, the router will also take care of DNS.
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.
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
On Monday, October 10, 2005 @ 9:33 AM, 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.
I point to the router (192.168.1.1) for both of these. By the way, If all of your machines are using static routing and you haven't somehow got an entry for the machine in the router's configuration table with a different IP address, you shouldn't have to worry. If you start with a clear table in the router and nothing ever asks it for an address, it won't matter if you have the router assigning addresses. However, if you ever add a machine and it asks the router for and address and the router gives it one that you are already using on one of your other machines, you'll have problems. If you want to go strictly with fixed addresses, best to just disable DHCP in the router so you'll never have that problem. Of course, on most routers you can have a combo of the two by setting an exclude range for the machines you have assigned the fixed addresses to so that it never hands those addresses out. Then you could work with a mixed bag of some machines with fixed addresses and some getting their addresses from the router. Greg Wallace Greg Wallace
On Monday 10 October 2005 19:42, Greg Wallace wrote: [...]
I point to the router (192.168.1.1) for both of these. By the way, If all of your machines are using static routing and you haven't somehow got an entry for the machine in the router's configuration table with a different IP address, you shouldn't have to worry. If you start with a clear table in the router and nothing ever asks it for an address, it won't matter if you have the router assigning addresses. However, if you ever add a machine and it asks the router for and address and the router gives it one that you are already using on one of your other machines, you'll have problems. If you want to go strictly with fixed addresses, best to just disable DHCP in the router so you'll never have that problem. Of course, on most routers you can have a combo of the two by setting an exclude range for the machines you have assigned the fixed addresses to so that it never hands those addresses out. Then you could work with a mixed bag of some machines with fixed addresses and some getting their addresses from the router.
In the LinkSys config there's a setting to allow just specific MAC addresses (thus excluding anything that doesn't match), and there IS a setting for "mixed" dhcp and static on the network, but for what you are talking about.... hmmm... ok, there's the option to enable the DHCP server, and a starting IP address, and a "Maximum Number of DHCP Users" setting. That would probably do it. I had my static addresses inside that range. I'll fix that and see what happens. Kevin
On Monday, October 10, 2005 @ 4:14 PM, Kevin wrote:
On Monday 10 October 2005 19:42, Greg Wallace wrote: [...]
I point to the router (192.168.1.1) for both of these. By the way, If all of your machines are using static routing and you haven't somehow got an entry for the machine in the router's configuration table with a different IP address, you shouldn't have to worry. If you start with a clear table in the router and nothing ever asks it for an address, it won't matter if you have the router assigning addresses. However, if you ever add a machine and it asks the router for and address and the router gives it one that you are already using on one of your other machines, you'll have problems. If you want to go strictly with fixed addresses, best to just disable DHCP in the router so you'll never have that problem. Of course, on most routers you can have a combo of the two by setting an exclude range for the machines you have assigned the fixed addresses to so that it never hands those addresses out. Then you could work with a mixed bag of some machines with fixed addresses and some getting their addresses from the router.
In the LinkSys config there's a setting to allow just specific MAC addresses (thus excluding anything that doesn't match), and there IS a setting for "mixed" dhcp and static on the network, but for what you are talking about.... hmmm... ok, there's the option to enable the DHCP server, and a starting IP address, and a "Maximum Number of DHCP Users" setting. That would probably do it. I had my static addresses inside that range. I'll fix that and see what happens.
Kevin
Not sure about what you're saying. You don't want to have your machines set up as static and then have your router handing out addresses in the range that the machines use. It might hand out the address for machine 1 to machine 2, for example. Then again, if all of your machines are set up as static, none of them would be asking for an address from the router anyway, so I guess that wouldn't hurt. Bottom line. If you want to use strictly fixed addresses, you really should just turn off DHCP in your router. Greg Wallace
participants (8)
-
Alfredo Cole -
Bruce Marshall -
Doug Curey -
elefino -
Greg Wallace -
James Knott -
Ken Schneider -
Tom Peters