Lynksys Wireless Router/Modem
in [Wireless Internet]
|
Prev: NEWS: FCC boss stumps for free and open internet
Next: Downloading only a particular page/selective pages of a document from the internet or other file server - Free Tool
From: Aaron Leonard on 25 Jan 2010 13:08 On Fri, 22 Jan 2010 14:00:27 -0600, ibuprofin(a)painkiller.example.tld.invalid (Moe Trin) wrote: ~ >The easiest thing for me is to have all my systems use DHCP, but have ~ >my DHCP server assign fixed IP addresses to each client (based upon ~ >the client ID / MAC address.) ~ ~ And you assign the 'client ID' and 'MAC address' from the DHCP server? ~ I don't think so. So you had to fire up each client system, figure ~ out where the magic information is hidden, copy it EXACTLY, and then ~ transfer this data to the DHCP server without typ0s (assuming you ~ also know where this information needs to go in the server config). ~ And of course your networks are physically isolated and secured so ~ that no one can be spoofing/setting their MAC address. Exactly so, for the case at hand: i.e. my home network, which consists of 3 Macs, 1 PC, 1 iTouch, 1 AP, plus my work PC, all behind my router. ~ >That way I don't have to run around configuring all my end systems ~ ~ How often are you changing / re-configuring your systems? Other than ~ lap-tops, most people aren't playing musical computers and moving ~ things. It's a one-time deal, and it's done. But nowadays (in home networks) it's ALL laptops. ~ >and also if I move a system from network to network, it picks up the ~ >right addresses automatically. And I have a central place (the DHCP ~ >server) that provides all the MAC-address mappings. ~ You have one DHCP server for all of your networks? No, I have one DHCP server for my home network. Then when I move a laptop to some OTHER network, they have some OTHER DHCP server set up. So: if the laptop is configured for DHCP, it will automatically pick up a valid address. If I statically configure the laptop ... then I have to do something different when I move it to some other network. ~ Must have been ~ fun to set up - something the average home user isn't going to be ~ doing. Yes, if your computer is moving from network to network, ~ a DHCP client is probably the way to go, but unless you are using ~ a cryptographic signiture scheme, you may be a bit to trusting. My ~ laptops only move between three different networks, and they have ~ (selectable) fixed setups for each. ~ >Of course I cheat and use a Cisco IOS router as the DHCP server, but ~ >lots of other DHCP servers could do this too. ~ ~ As you work for Cisco, I'm sure the company expects that. As for the ~ other DHCP servers, most users have no knowledge of how to set them ~ up and are expecting that what-ever defaults were used are enough to ~ allow connections. That's why RFC3927 addresses are so necessary. ~ "The Internet must be b0rk3n - I can connect to the router OK." The great majority of users ... should never need to know what a MAC or IP address is. In the thread at hand, it appears that the O.P. does care about the IP addresses in (what I infered to be) his home network. So I offered a suggestion for a good way to manage these things in such a scenario. Of course, other sitations may call for different measures. ~ Old guy Probably Even Older Guy
From: Peter Pan on 25 Jan 2010 17:52 "Aaron Leonard" <Aaron(a)Cisco.COM> wrote in message news:rjlrl5to53vhjuvugaacd1mi543o9iehg2(a)4ax.com... > On Fri, 22 Jan 2010 14:00:27 -0600, > ibuprofin(a)painkiller.example.tld.invalid (Moe Trin) wrote: > > ~ >The easiest thing for me is to have all my systems use DHCP, but have > ~ >my DHCP server assign fixed IP addresses to each client (based upon > ~ >the client ID / MAC address.) > ~ > ~ And you assign the 'client ID' and 'MAC address' from the DHCP server? > ~ I don't think so. So you had to fire up each client system, figure > ~ out where the magic information is hidden, copy it EXACTLY, and then > ~ transfer this data to the DHCP server without typ0s (assuming you > ~ also know where this information needs to go in the server config). > ~ And of course your networks are physically isolated and secured so > ~ that no one can be spoofing/setting their MAC address. > > Exactly so, for the case at hand: i.e. my home network, which > consists of 3 Macs, 1 PC, 1 iTouch, 1 AP, plus my work PC, all behind > my router. > > ~ >That way I don't have to run around configuring all my end systems > ~ > ~ How often are you changing / re-configuring your systems? Other than > ~ lap-tops, most people aren't playing musical computers and moving > ~ things. It's a one-time deal, and it's done. > > But nowadays (in home networks) it's ALL laptops. > > ~ >and also if I move a system from network to network, it picks up the > ~ >right addresses automatically. And I have a central place (the DHCP > ~ >server) that provides all the MAC-address mappings. > > ~ You have one DHCP server for all of your networks? > > No, I have one DHCP server for my home network. Then when I move > a laptop to some OTHER network, they have some OTHER DHCP server > set up. So: if the laptop is configured for DHCP, it will > automatically pick up a valid address. If I statically configure > the laptop ... then I have to do something different when I move > it to some other network. > > ~ Must have been > ~ fun to set up - something the average home user isn't going to be > ~ doing. Yes, if your computer is moving from network to network, > ~ a DHCP client is probably the way to go, but unless you are using > ~ a cryptographic signiture scheme, you may be a bit to trusting. My > ~ laptops only move between three different networks, and they have > ~ (selectable) fixed setups for each. > > ~ >Of course I cheat and use a Cisco IOS router as the DHCP server, but > ~ >lots of other DHCP servers could do this too. > ~ > ~ As you work for Cisco, I'm sure the company expects that. As for the > ~ other DHCP servers, most users have no knowledge of how to set them > ~ up and are expecting that what-ever defaults were used are enough to > ~ allow connections. That's why RFC3927 addresses are so necessary. > ~ "The Internet must be b0rk3n - I can connect to the router OK." > > The great majority of users ... should never need to know what a MAC > or IP address is. In the thread at hand, it appears that the O.P. > does care about the IP addresses in (what I infered to be) his home > network. So I offered a suggestion for a good way to manage these > things in such a scenario. Of course, other sitations may call for > different measures. > > ~ Old guy > > Probably Even Older Guy > don't know if it will work for you or not, but i use a lookup in a table/program that gives a constant ip address to the programs based on mac and client id, and translates it to a dhcp assigned address for actual internet use (ie program thinks it has a static address, but in reality its translated to dynamic address).... (reverse of the same sort of thing used by static to dynamic stuff, to allow internet access to static ip's, that in reality are dynamic ip's but lookedup/translated)
From: Char Jackson on 26 Jan 2010 12:16 On Tue, 26 Jan 2010 08:39:21 -0800, Jeff Liebermann <jeffl(a)cruzio.com> wrote: >On Fri, 22 Jan 2010 14:00:27 -0600, >ibuprofin(a)painkiller.example.tld.invalid (Moe Trin) wrote: > >>How often are you changing / re-configuring your systems? Other than >>lap-tops, most people aren't playing musical computers and moving >>things. It's a one-time deal, and it's done. > >Nope. Both my neighbors, customers, and my own systems are in a near >constant state of change. That might be the norm for you, but it's not even close to my experience out here in the Midwest. The people I deal with will typically add or replace a PC every 2-3 years. Desktop systems are still far more common than laptops, so mobility isn't a big deal. Most people I know with a laptop wouldn't dream of taking it out of the house. If I were dealing with a "near constant state of change" I might look more favorably to DHCP myself, but that's so not the case here.
From: Christopher A. Lee on 26 Jan 2010 13:34 On Tue, 26 Jan 2010 11:16:18 -0600, Char Jackson <none(a)none.invalid> wrote: >On Tue, 26 Jan 2010 08:39:21 -0800, Jeff Liebermann <jeffl(a)cruzio.com> >wrote: > >>On Fri, 22 Jan 2010 14:00:27 -0600, >>ibuprofin(a)painkiller.example.tld.invalid (Moe Trin) wrote: >> >>>How often are you changing / re-configuring your systems? Other than >>>lap-tops, most people aren't playing musical computers and moving >>>things. It's a one-time deal, and it's done. >> >>Nope. Both my neighbors, customers, and my own systems are in a near >>constant state of change. > >That might be the norm for you, but it's not even close to my >experience out here in the Midwest. The people I deal with will >typically add or replace a PC every 2-3 years. Desktop systems are >still far more common than laptops, so mobility isn't a big deal. Most >people I know with a laptop wouldn't dream of taking it out of the >house. If I were dealing with a "near constant state of change" I >might look more favorably to DHCP myself, but that's so not the case >here. It's a disadvantage for home networks For example unless Microsoft have changed the way network attached printers are handled in Windows 7, they are configured by a wizard that searches the network for printers and remembers the IP address instead of a URL. I've got a Brother Laser and an HP Photosmart both of which include their own print server and wired ethernet connection to the Router. If you don't give the printers fixed IP address it won't find them if devices are powered up in a different order. Which they always are. Torrent handling wants port forwarding otherwise many remote servers throttle downloads because fairness means ther people download from you the stuff you've just downloaded from somebody else. This is done by IP address not URL. So more fixed IP addresses apart from one machine which never runs torrent software. The PCs won't automatically reconnect to my D-Link network attached RAID disk box if its IP address changes because that's what the D-Link utility uses. All of which I found out the hard way. I don't need to deinstall and reinstall devices on several machines when they're powered on in a different order. End result: everything apart from one elderly PC needs fixed IP addresses. I suspect business networks have PCs for dedicated printer and disk servers with rather more sophisticated software than comes built into the sort of kit we have at home. And they probably don't run torrent software so the result is different.
From: Char Jackson on 26 Jan 2010 15:10
On Tue, 26 Jan 2010 13:34:22 -0500, Christopher A. Lee <calee(a)optonline.net> wrote: >On Tue, 26 Jan 2010 11:16:18 -0600, Char Jackson <none(a)none.invalid> >wrote: > >>That might be the norm for you, but it's not even close to my >>experience out here in the Midwest. The people I deal with will >>typically add or replace a PC every 2-3 years. Desktop systems are >>still far more common than laptops, so mobility isn't a big deal. Most >>people I know with a laptop wouldn't dream of taking it out of the >>house. If I were dealing with a "near constant state of change" I >>might look more favorably to DHCP myself, but that's so not the case >>here. > >It's a disadvantage for home networks I don't know, I see advantages for some situations, like very small networks or Jeff's constant change scenario, or perhaps situations where the network owner would rather put up with the hassles you identified in this post instead of the hassles of static assignments. Sometimes it's almost an even trade-off. In the end, I suppose it's a personal choice as much as anything else. For me in my situation and I think you in yours as well, static assignments make the most sense. >I've got a Brother Laser and an HP Photosmart both of which include >their own print server and wired ethernet connection to the Router. > >If you don't give the printers fixed IP address it won't find them if >devices are powered up in a different order. Which they always are. I don't power down anything except a laptop, so I don't have a reason to power things up in any specific order. Actually, I'm surprised that you power cycle things like print servers and NAS devices. I don't do that here. |