Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

wireless connection



john abreau writes: 
> 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 ;
>        }

i can't seem to find dhcpd.conf anywhere, probably not an
ubuntu thing, but i did find /etc/dhcp3/dhclient.conf

i looked at the man page for that and tried fiddling the
alias and lease terms, fully expecting progress, but got
nowhere.  it just keeps on coming up with 192.168.0.100

i've either got the wrong file, or i've entered the wrong
stuff.

fwiw this is the file i tried:

------------------------------------------------------------

# Configuration file for /sbin/dhclient

option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;

#send host-name "<hostname>";

send host-name "alioth";
send dhcp-client-identifier 00:1e:2a:xx:xx:xx;

#send dhcp-lease-time 3600;
#supersede domain-name "fugue.com home.vix.com";
#prepend domain-name-servers 127.0.0.1;

request subnet-mask, broadcast-address, time-offset, routers,
	domain-name, domain-name-servers, domain-search, host-name,
	netbios-name-servers, netbios-scope, interface-mtu,
	rfc3442-classless-static-routes, ntp-servers;

#require subnet-mask, domain-name-servers;
#timeout 60;
#retry 60;
#reboot 10;
#select-timeout 5;
#initial-interval 2;
#script "/etc/dhcp3/dhclient-script";
#media "-link0 -link1 -link2", "link0 link1";
#reject 192.33.137.209;

alias {
interface "wlan0";
fixed-address 192.168.0.3;
option subnet-mask 255.255.255.0;
}

lease {
interface "wlan0";
fixed-address 192.168.0.3;
medium "link0 link1";
option host-name "alioth.localdomain";
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
option domain-name-servers 127.0.0.1;
renew  2 2000/1/12 00:00:01;
rebind 2 2012/1/12 00:00:01;
expire 2 2012/1/12 00:00:01;
}

-------------------------------------------------------------

> 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. =A0i 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. =A0backing 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.

tia,
ole dan






BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org