Re: wireless gui configuration utility
On Mon, 19 Jan 2009 21:06:00 +0800
"Umarzuki Mochlis" <umarzuki@gmail.com> wrote:
> 2009/1/18 Micha Feigin <michf@post.tau.ac.il>:
> > On Sat, 17 Jan 2009 07:53:50 +0800
> > "Umarzuki Mochlis" <umarzuki@gmail.com> wrote:
> >
> >> sadly, wicd currently won't work with my wireless: broadcomm 4315 on
> >> presario CQ40-115AU. Perhaps i need a little tweaking or something,
> >> any idea?
> >>
> >
> > One thing that needs to be done with wicd is point it at the right
> wireless
> > interface. It changes between modules so check what yours creates
> (ifconfig -a)
> > and point wicd to the right place (in the gui configuration)
> >
> > For example for my atheros card the ath5k modules creates wlan0 and
> madwifi
> > creates ath0
> >
>
Looks like it's pointing in the right direction. Does it see you wireless when
you open the window (under available wireless connections)
If so, you need to choose your ap click that little triangle by the name, check
automatically connect to this network if you wish and click advanced settings
to setup things like wep password and such.
Some public access points also have a transparent proxy that requires you to
authenticate when you start browsing (my uni is that way, you need to enter a
wpa key and then enter your username/password in the browser before you can
access outside connections).
> My *ifconfig -a*
>
> eth0 Link encap:Ethernet HWaddr 00:1e:ec:b1:5a:76
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:280307241202 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> Interrupt:251 Base address:0xc000
>
> eth1 Link encap:Ethernet HWaddr 00:21:00:68:1d:b4
> inet6 addr: fe80::221:ff:fe68:1db4/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> Interrupt:18
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)
>
>
> *iwconfig* output:
>
> eth1 IEEE 802.11bg ESSID:"" Nickname:""
> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
> Bit Rate:54 Mb/s Tx-Power:off
> Retry min limit:7 RTS thr:off Fragment thr:off
> Power Managementmode:All packets received
> Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> *wicd settings*
>
> http://img443.imageshack.us/my.php?image=wicdoe1.png
> http://img105.imageshack.us/my.php?image=wicd2aq2.png
>
> Hope anyone can tell me what I had missed in terms of getting dhcp lease
> from a access point (it gives ip when connected but needs to input id and
> password on web browser) and any wireless network with wep.
>
> >> 2009/1/17 Osamu Aoki <osamu@debian.org>::
> >> > On Thu, Jan 15, 2009 at 02:56:03PM +0000, thveillon.debian wrote:
> >> >> +1 for wicd, with atheros chips (and ath5k driver) and wpa it has
> >> >> performed very well. During the past release of *buntu 8.10
> >> >> *NetworkManager has gone crazy on many wireless chips, especially
> >> >> atheros, and since then wicd has gained a good reputation there too.
> >> >>
> >> >> It's in Sid/Unstable.
> >> >
> >> > OK. Interesting.
> >> >
> >> > I will mention this in Debian Reference...
> >> >
> >> >
> >> > --
> >> > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> >> > with a subject of "unsubscribe". Trouble? Contact
> >> > listmaster@lists.debian.org
> >> >
> >> >
> >>
> >>
> >>
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> >
> >
>
>
>
Reply to: