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 |
What I do at my house is to run dhcpd and bind on a server, and completely shut off the wireless router's dhcp server. Then in dhcpd.conf, I assign fixed ip addresses to specific mac addresses, e.g. # palmtx - Palm T|X pda host palmtx { hardware ethernet 00:0B:6C:xx:xx:xx ; fixed-address palmtx.abreau.net ; } # nokia770 - Nokia M770 internet tablet host nokia770 { hardware ethernet 00:14:A7:xx:xx:xx ; fixed-address nokia770.abreau.net ; } # garbagescow - Dell XPS M1210 laptop host garbagescow { hardware ethernet 00:18:8B:xx:xx:xx ; fixed-address garbagescow.abreau.net ; } # garbagescow-wlan - Dell XPS M1210 laptop (wlan) host garbagescow { hardware ethernet 00:1B:77:xx:xx:xx ; fixed-address garbagescow.abreau.net ; } This way, I can set my laptop to use DHCP everywhere. It works correctly when I'm on the road, and it still gets a static address when I'm at home. The, the only devices in my house that are configured with static addresses are the LAN port of the wireless router, and the CentOS file server that also provides DNS and DHCP. And if I ever want to renumber my network, I only have to change the configs on two devices and then update DNS for all others. Of course, if you don't want to run your own internal DNS, you can always hardwire ip addresses into dhcpd.conf: host garbagescow { hardware ethernet 00:1B:77:xx:xx:xx ; fixed-address 192.168.0.3 ; } On Wed, Nov 3, 2010 at 11:38 AM, j. daniel moylan <moylan at alioth> wrote: > wireless connection > > i've been running ubuntu 10.04 on an asus eee pc 1005ha, and > two panasonic cf-50s, with wireless connections to a netgear > mr814 -- 802.11b -- old, running without wep or wpa, just > requiring the mac addresses be listed in the router (and > yes, you have told me that's poor security). > > i set up the wireless interconnection using the > nm-connection-editor, set to manual, specifying the address, > and this worked fine. ?i put the addresses of my local > computers in /etc/hosts and could scp, ssh etc back in forth > at will by name -- all fine. > > i decided to upgrade for more speed/range to a dlink > dir-655, 802.11n, with wpa security. > > naturally i needed to add the key, but was unable to make > connection, even with reboot. ?backing off to dhcp protocol, > it still wouldn't connect, but on reboot it did. > > with the proper values in /etc/network/interfaces, > sudo /etc/init.d/networking restart switched the address > from 192.168.0.101 to 192.168.0.3 (e.g.) which is where i > leave it, but on reboot, it still comes up 192.168.0.101. > even when i'm happily chugging away with 192.168.0.3, it > occasionaly switches back to 192.168.0.101 all by itself. > > i get similar performance on all three computers. > > something i'm doing isn't right, but i have no idea what. > > any suggestions? > > tia. > > ole dan > _______________________________________________ > Discuss mailing list > Discuss-mNDKBlG2WHs at public.gmane.org > http://lists.blu.org/mailman/listinfo/discuss > -- John Abreau / Executive Director, Boston Linux & Unix AIM abreauj / JABBER jabr-iMZfmuK6BGBxLiRVyXs8+g at public.gmane.org / YAHOO abreauj / SKYPE zusa_it_mgr Email jabr-mNDKBlG2WHs at public.gmane.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |