Comment 23 for bug 129608

In the time it ook em to cut and paste this it rescanned 3 times

at the bottom it says connected to sage_htc 0db with an ip listed.
The connect button is lit available. I have attached a screen shot.

root@sage-laptop:~# ifconfig -a wlan0
wlan0 Link encap:Ethernet HWaddr 00:1f:3c:b6:91:f2
          inet6 addr: fe80::21f:3cff:feb6:91f2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1550 (1.5 KB) TX bytes:1296 (1.2 KB)

root@sage-laptop:~# iwconfig wlan0
wlan0 IEEE 802.11abg ESSID:"sage_htc"
          Mode:Ad-Hoc Frequency:2.412 GHz Cell: 02:21:E8:47:1A:0C
          Tx-Power=15 dBm
          Retry min limit:7 RTS thr:off Fragment thr=2352 B
          Encryption key:off
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

On Fri, May 15, 2009 at 9:19 AM, Dan O'Reilly <email address hidden> wrote:
> @Sage Major
>
> What does the output of iwconfig and ifconfig look like after you get
> connected?
>
> --
> Unable to connect to ad-hoc network
> https://bugs.launchpad.net/bugs/129608
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in wicd: In Progress
>
> Bug description:
> Running on Feisty.
>
> I am unable to connect to a ad-hoc network as Wicd appears to set the interface up in managed mode, even though it recognised that the network is ad-hoc.
>
> This causes the whole application to get stuck in the connecting stage, the only solution is to quit the gui and stop/start the deamon.
> Simon.
>