Re: command line wirelss config [was: How to speed up your Mac.]

2007-12-10 Thread P Kapat
On 12/9/07, Bin Zhang <[EMAIL PROTECTED]> wrote:
> On Dec 9, 2007 8:34 AM, P Kapat <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Sorry for not getting back early. Work is keeping things busy.. Thanks
> > to Bin, Jörg, and Yannick for the details. I am able to connect to the
> > wireless networks now :) I am providing the two files
> > /etc/network/interfaces and /etc/wpa_suppliant.conf for reference and
> > may be someone else will find it helpful.
> >
> > After booting, I do a 'ifup  eth2' to get a a wireless connection. Now
> > how do I change the network (say from 'home' to 'neighbor')?
>
> See /usr/share/doc/wpasupplicant/README.modes.gz.
>
> After "ifup eth2", you can use
> # wpa_gui -ieth2
> (install package wpagui)
> or
> # wpa_cli list_networks
> # wpa_cli select_network <
> ( see wpa_cli -h )

Thanks Bin, both of them work!

>
> Best regards,
> Bin

-- 
Regards
PK
--
http://counter.li.org  #402424



Re: command line wirelss config [was: How to speed up your Mac.]

2007-12-09 Thread Bin Zhang
On Dec 9, 2007 8:34 AM, P Kapat <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Sorry for not getting back early. Work is keeping things busy.. Thanks
> to Bin, Jörg, and Yannick for the details. I am able to connect to the
> wireless networks now :) I am providing the two files
> /etc/network/interfaces and /etc/wpa_suppliant.conf for reference and
> may be someone else will find it helpful.
>
> After booting, I do a 'ifup  eth2' to get a a wireless connection. Now
> how do I change the network (say from 'home' to 'neighbor')?

See /usr/share/doc/wpasupplicant/README.modes.gz.

After "ifup eth2", you can use
# wpa_gui -ieth2
(install package wpagui)
or
# wpa_cli list_networks
# wpa_cli select_network <
( see wpa_cli -h )

Best regards,
Bin


> ### /etc/network/interfaces  ###
> auto lo
> iface lo inet loopback
>
> allow-hotplug eth1
> iface eth1 inet dhcp
>
> iface eth2 inet manual
> wpa_driver wext
> wpa_roam /etc/wpa_supplicant.conf
>
> iface default inet dhcp
>
> iface work inet dhcp
>
> iface home inet dhcp
>
> iface neighbor inet dhcp
>
> ### /etc/wpa_supplicant.conf ###
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> eapol_version=1
> ap_scan=1
> fast_reauth=1
>
> # EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the old 
> peaplabel
> network={
> ssid="workwireless"
> id_str="work"
> scan_ssid=1
> proto=WPA
> key_mgmt=WPA-EAP
> eap=PEAP
> identity="user"
> password="mypassword"
> phase1="peaplabel=0"
> phase2="auth=MSCHAPV2"
> priority=1
> }
>
> network={
> ssid="me"
> id_str="home"
> key_mgmt=WPA-PSK
> proto=WPA
> pairwise=TKIP
> group=TKIP
> psk="abcd"
> }
>
> network={
> ssid="other"
> id_str="neighbor"
> key_mgmt=NONE
> }
>
> network={
> key_mgmt=NONE
> }
>
> #
>
>
> ---
>
> Regards,
> PK
> --
> http://counter.li.org  #402424
>
>


Re: command line wirelss config [was: How to speed up your Mac.]

2007-12-08 Thread P Kapat
Hi,

Sorry for not getting back early. Work is keeping things busy.. Thanks
to Bin, Jörg, and Yannick for the details. I am able to connect to the
wireless networks now :) I am providing the two files
/etc/network/interfaces and /etc/wpa_suppliant.conf for reference and
may be someone else will find it helpful.

After booting, I do a 'ifup  eth2' to get a a wireless connection. Now
how do I change the network (say from 'home' to 'neighbor')?

### /etc/network/interfaces  ###
auto lo
iface lo inet loopback

allow-hotplug eth1
iface eth1 inet dhcp

iface eth2 inet manual
wpa_driver wext
wpa_roam /etc/wpa_supplicant.conf

iface default inet dhcp

iface work inet dhcp

iface home inet dhcp

iface neighbor inet dhcp

### /etc/wpa_supplicant.conf ###
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1

# EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the old peaplabel
network={
ssid="workwireless"
id_str="work"
scan_ssid=1
proto=WPA
key_mgmt=WPA-EAP
eap=PEAP
identity="user"
password="mypassword"
phase1="peaplabel=0"
phase2="auth=MSCHAPV2"
priority=1
}

network={
ssid="me"
id_str="home"
key_mgmt=WPA-PSK
proto=WPA
pairwise=TKIP
group=TKIP
psk="abcd"
}

network={
ssid="other"
id_str="neighbor"
key_mgmt=NONE
}

network={
key_mgmt=NONE
}

#


---
Regards,
PK
--
http://counter.li.org  #402424



Re: command line wirelss config [was: How to speed up your Mac.]

2007-12-06 Thread Yannick Roehlly
P Kapat wrote:

> ok, i need more help... has anyone successfully used  ifup / ifdown /
> wpa_supplicant method to access wireless network from the command
> line??

Hi,

A simpler configuration than Jörg's (if you have a simple WPA) is to put
this in your /etc/network/interfaces:

auto eth1   <- you may want it to auto connect
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid your_ssid
wpa-key-mgmt WPA-PSK
wpa-psk your_wpa_psk<- or wpa-psk "your_ascii_passphrase"

I don't know if there is a difference between the use of the WPA PSK
(obtained with wpa_passphrase) and the use of the ASCII passphrase.

Note that the name of your wireless interface may change (for instance with
the new 2.6.24(-rc) b43 driver. You can have a stable interface name using
the ifrename package.

Note also that you won't be able to use network-manager as enabling an
interface in /etc/network/interfaces disables its management by
network-manager.
That's why I agree with your first post, it would be good to have a console
client for network-manager. ;-)

Yannick




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: command line wirelss config [was: How to speed up your Mac.]

2007-12-06 Thread Jörg Sommer
Hello P,

P Kapat <[EMAIL PROTECTED]> wrote:
> ok, i need more help... has anyone successfully used  ifup / ifdown /
> wpa_supplicant method to access wireless network from the command
> line??

Yes. I use ifup eth1 and some seconds later I get the interface up.

> On 12/5/07, Bin Zhang <[EMAIL PROTECTED]> wrote:
>> On Dec 5, 2007 4:18 PM, P Kapat <[EMAIL PROTECTED]> wrote:
>> > i think it is better to start a new thread...
>> >
>> > On 12/1/07, Bin Zhang <[EMAIL PROTECTED]> wrote:
>> > > On Dec 1, 2007 5:15 PM, P Kapat <[EMAIL PROTECTED]> wrote:
>> > > >  How about the wireless? Is there any command
>> > > > line version for NetworkManger? In Gnome, KDE we have either nm-applet
>> > > > or network-manager-kde I have been playing around with iwconfig
>> > > > and iwlist but didn't meet with any success.
>> > >
>> > > You can configure it in /etc/network/interfaces and use
>> > > # ifup "interface_name"
>> > > and
>> > > # ifdown "interface_name"
>> >
>> > noting that I need to access WPA encrypted wireless networks, do I
>> > need the wpa_supplicant after this? Some more details on the whole
>> > process will be very much appreciated...
>>
>> You can Install package wpasupplicant and read
>> /usr/share/doc/wpasupplicant/README.modes.gz and
>> /usr/share/doc/wpasupplicant/examples/
>
> i currently have the following in /etc/network/interfaces
> ##
> auto lo
> iface lo inet loopback
> allow-hotplug eth1 eth2
> iface eth1 inet dhcp
>
> # my wirelss interface is eth2; and what is this wpa-driver???
> iface eth2 inet manual
> wpa-driver wext

wext is correct.

> wpa-roam /etc/wpa_supplicant.conf
>
> iface default inet dhcp
>
> iface work inet dhcp
> 
>
> and the following in /etc/wpa_supplicant.conf
>
> ctrl_interface=/var/run/wpa_supplicant
> network={
> ssid="workssid"
> id_str="work"

Your interfaces misses a rule for work.

This is my wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant

eapol_version=1
ap_scan=1
# fast_reauth=1

### Associate with any open access point
###  Scans/ESSID changes can be done with wpa_cli
network={
ssid="802.1X"
id_str="fsu_dhcp"  # this is passed to ifup eth1=fsu_dhcp
proto=WPA
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=TKIP
eap=TTLS
anonymous_identity="[EMAIL PROTECTED]"
identity=""
password=""
ca_cert="/etc/ssl/certs/FSU.pem"
phase2="auth=PAP"
priority=4
}

And this is my /etc/network/interfaces:

iface eth1 inet manual
wpa_roam /home/joerg/.etc/wpa_supplicant.conf
wpa_driver wext

iface fsu_dhcp inet dhcp
down env interface=eth1 /etc/udhcpc/default.deconfig


Bye, Jörg.
-- 
Mancher Hahn meint, dass die Sonne seinetwegen aufgeht.
   (Theodor Fontane)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: command line wirelss config [was: How to speed up your Mac.]

2007-12-05 Thread P Kapat
ok, i need more help... has anyone successfully used  ifup / ifdown /
wpa_supplicant method to access wireless network from the command
line??

my idea is to start icewm and connect to one of available networks,
without resorting to network-manager-kde...

On 12/5/07, Bin Zhang <[EMAIL PROTECTED]> wrote:
> On Dec 5, 2007 4:18 PM, P Kapat <[EMAIL PROTECTED]> wrote:
> > i think it is better to start a new thread...
> >
> > On 12/1/07, Bin Zhang <[EMAIL PROTECTED]> wrote:
> > > On Dec 1, 2007 5:15 PM, P Kapat <[EMAIL PROTECTED]> wrote:
> > > >  How about the wireless? Is there any command
> > > > line version for NetworkManger? In Gnome, KDE we have either nm-applet
> > > > or network-manager-kde I have been playing around with iwconfig
> > > > and iwlist but didn't meet with any success.
> > >
> > > You can configure it in /etc/network/interfaces and use
> > > # ifup "interface_name"
> > > and
> > > # ifdown "interface_name"
> >
> > noting that I need to access WPA encrypted wireless networks, do I
> > need the wpa_supplicant after this? Some more details on the whole
> > process will be very much appreciated...
>
> You can Install package wpasupplicant and read
> /usr/share/doc/wpasupplicant/README.modes.gz and
> /usr/share/doc/wpasupplicant/examples/

Bin,
blame me for being thick, but i couldn't get my wireless working after
reading these help files need some more help...

i currently have the following in /etc/network/interfaces
##
auto lo
iface lo inet loopback
allow-hotplug eth1 eth2
iface eth1 inet dhcp

# my wirelss interface is eth2; and what is this wpa-driver???
iface eth2 inet manual
wpa-driver wext
wpa-roam /etc/wpa_supplicant.conf

iface default inet dhcp

iface work inet dhcp


and the following in /etc/wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant
network={
ssid="workssid"
id_str="work"
scan_ssid=1
key_mgmt=WPA-EAP
eap=PEAP
identity="username"
password="password"
phase1="peaplabel=0"
phase2="auth=MSCHAPV2"
priority=1
}

network={
key_mgmt=NONE
}


the network details are as required by the concerned network... having
created/modified these files, i rebooted. wpa_action eth2 reload
didnot help, the log file /var/log/wpa_action.log is prctically
useless.

ifconfig and iwconfig is able to identify the interface. iwlist
scanning is showing the available networks. now what???

-- 
Regards
PK
--
http://counter.li.org  #402424


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: command line wirelss config [was: How to speed up your Mac.]

2007-12-05 Thread Bin Zhang
On Dec 5, 2007 4:18 PM, P Kapat <[EMAIL PROTECTED]> wrote:
> i think it is better to start a new thread...
>
> On 12/1/07, Bin Zhang <[EMAIL PROTECTED]> wrote:
> > On Dec 1, 2007 5:15 PM, P Kapat <[EMAIL PROTECTED]> wrote:
> > >  How about the wireless? Is there any command
> > > line version for NetworkManger? In Gnome, KDE we have either nm-applet
> > > or network-manager-kde I have been playing around with iwconfig
> > > and iwlist but didn't meet with any success.
> >
> > You can configure it in /etc/network/interfaces and use
> > # ifup "interface_name"
> > and
> > # ifdown "interface_name"
>
> noting that I need to access WPA encrypted wireless networks, do I
> need the wpa_supplicant after this? Some more details on the whole
> process will be very much appreciated...

You can Install package wpasupplicant and read
/usr/share/doc/wpasupplicant/README.modes.gz and
/usr/share/doc/wpasupplicant/examples/

Regards,
Bin
>
> --
> Regards
> PK
> --
> http://counter.li.org  #402424
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]