Re: Does anyone understand NetworkManager?
- From: David Abrahams <dave boost-consulting com>
- To: networkmanager-list gnome org
- Subject: Re: Does anyone understand NetworkManager?
- Date: Tue, 15 Aug 2006 12:32:35 -0400
"Darren Albers" <dalbers gmail com> writes:
> Also you need to make sure Network-Manager is stopped, if this is Ubuntu do:
> sudo /etc/dbus-1/event.d/25NetworkManager stop
Done
> Then bring up the interface with ifup eth1 (or eth0 etc..)
dave pereiro:~$ sudo ifup eth1
Ignoring unknown interface eth1=eth1.
dave pereiro:~$ sudo gedit /etc/network/interfaces
# insert lines for eth1 using dhcp
dave pereiro:~$ sudo ifup eth1
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
Listening on LPF/eth1/00:13:02:87:6a:e5
Sending on LPF/eth1/00:13:02:87:6a:e5
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
>> Here is the wpa_supplicant.conf that I used in the past for WPA_PSK:
>>
>> ctrl_interface=/var/run/wpa_supplicant
>> ctrl_interface_group=0
>> eapol_version=1
>> ap_scan=2
>> fast_reauth=1
>> network={
>> ssid="Enteryour SSID Here"
>> proto=WPA
>> key_mgmt=WPA-PSK
>> pairwise=TKIP
>> group=TKIP
>> psk=enteryourkeyhere
>> }
>>
>>
>> Then to bring up wpa do this:
>> wpa_supplicant -d -c/path/to/wpa_supplicant.conf -ieth1 -Dwext
>>
>> You need to change to enter the path to wpa_supplicant.conf above and
>> make sure that -i points to the right interface eth1 or eth0 etc...
Once I realized that for DHCP to work, I needed to start
wpa_supplicant *while* ifup was trying to do its thing, everything
worked. Connecting to the wireless LAN that way is essentially
instantaneous (maybe 1-2 seconds) and reliable AFAICT.
So what next?
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]