Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On 12/12/2008 10:22 AM, David Hummel wrote: > On Fri, Dec 12, 2008 at 9:23 AM, Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org> wrote: > =20 >> On 12/12/2008 09:18 AM, Matthew Gillen wrote: >> =20 >>> I use it on all my systems nowadays. It used to have issues with sta= tic >>> IPs, but that seems better now. >>> >>> One of the reasons I'd recommend it is the ifplug functionality: if y= ou >>> unplug the cable, it "does the right thing" by bringing the interface= down >>> (so network operations return failure immediately instead of timing o= ut, >>> etc). Likewise when you plug it back in, it will immediately >>> reactivate/renew-DHCP. >>> =20 >> What about static IPs. I use a static IP so I can allow for ssh connec= tions. >> This is the main reason I disabled Network Manager. I certainly use it= on my >> laptop, and it has worked very well. >> =20 > > If your DHCP server supports fixed IPs based on MAC address, this is > one work-around. Otherwise, I don't see the point of using NM for a > system that isn't physically moving around ... > _______________________________________________ > > =20 Most DHCP servers will try to retain the same IP address based on the=20 MAC address, but this is not guaranteed with most. I certainly know that = mine does not have the capability to assign an IP address to a specific=20 MAC address. Turning off Network manager seems to be the best solution=20 for using a static IP. Or, possibly tying port forwarding to a MAC=20 address. My router only forwards on an IP address. --=20 Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |