On Friday 26 Feb 2010 23:00:21 David Paleino wrote:
Yes. And $PATH isn't involved here :)
I'm curious to know how this worked in 1.6.2.*, since that particular piece
of code didn't change -- or maybe I just remember wrong.
Hmm!! It did work with 1.6.x. That is why I asked to keep a copy of
On Monday 01 March 2010 11:18:49, Ritesh Raj Sarraf wrote:
[..]
You should be able to fix this problem by putting a full path to a script
-- those fields are not meant to contain any command, just something
like /home/ritesh/my-wicd-preconnect.sh (it could also be something
different
On Monday 01 Mar 2010 16:59:19 David Paleino wrote:
Ok, maybe I didn't explain myself clearly enough :).
Don't put any whitespace in those fields; they're supposed to executed ONE
command, with no arguments.
Try making a vpnc-wicd-postconnect.sh and vpnc-wicd-postdisconnect.sh, and
see if
David,
This looks an odd behavior.
2010/03/01 21:19:19 :: ifconfig wlan0
2010/03/01 21:19:21 :: Connecting to wireless network rrs
2010/03/01 21:19:21 :: iwconfig wlan0
2010/03/01 21:19:21 :: Running pre-disconnect script
2010/03/01 21:19:23 :: ifconfig eth0
I initiated a connect while wicd
There seems to be problem with scripts that are executed from within wicd.
This is what I am getting:
2010/02/26 21:29:16 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67
interval 5
2010/02/26 21:29:17 :: DHCPOFFER from 192.168.2.1
unmerge 565483 567472
severity 567472 normal
retitle 567472 document that *-connection scripts should contain the path to an
external script
thanks
Hello Ritesh,
ok, this seems a different bug, un-merging.
On Friday 26 February 2010 17:04:49, Ritesh Raj Sarraf wrote:
There seems to be problem
unmerge 567472
retitle 565483 wicd: completely unusable with hidden SSID
severity 565483 important
thanks
On Friday 26 February 2010 18:33:11, Debian Bug Tracking System wrote:
Processing commands for cont...@bugs.debian.org:
unmerge 565483 567472
Unknown command or malformed arguments to
On Friday 29 Jan 2010 18:28:25 David Paleino wrote:
wicd (1.6.2) was able to auto-connect to my hidden network. But with
1.7.0, that is not the case.
Can you post your /var/log/wicd/wicd.log, after enabling debugging mode (in
wicd-gtk) and stripping private information?
Hello david,
I
Package: wicd
Version: 1.7.0-2
Severity: important
The recent upgrade to 1.7.0 has broken hidden wifi support completely.
I specify the hidden essid but wicd never connect to the network.
wireless-tools confirms that the association to the hidden essid is in
place. But wicd never initiates a
forcemerge 565483 567472
thanks
Hello,
On Friday 29 January 2010 11:14:42, Ritesh Raj Sarraf wrote:
Package: wicd
Version: 1.7.0-2
Severity: important
The recent upgrade to 1.7.0 has broken hidden wifi support completely.
I specify the hidden essid but wicd never connect to the network.
Hi david,
On Friday 29 Jan 2010 15:55:54 David Paleino wrote:
The recent upgrade to 1.7.0 has broken hidden wifi support completely.
I specify the hidden essid but wicd never connect to the network.
This has already been followed-up to #565483. Please reply there, no need
to open a
Hello,
no need to CC me, thanks :)
On Friday 29 January 2010 13:44:50, Ritesh Raj Sarraf wrote:
My problem might be slightly different. With wicd 1.6.2, I was very well
able to connect to my hidden network (with the exception of this bug
http://bugzilla.kernel.org/show_bug.cgi?id=14206
but
12 matches
Mail list logo
