On 2021-01-19 22:09:49 +0200, Andrei POPESCU wrote:
> While it might have had its toothing problems in the beginning
> NetworkManager has been reliable for me since switching from Wicd (some
> time around the wheezy release I believe).
I use Debian/unstable, and I've al
unless you are willing to resort to commandline tools.
Fully agreed.
While it might have had its toothing problems in the beginning
NetworkManager has been reliable for me since switching from Wicd (some
time around the wheezy release I believe).
Kind regards,
Andrei
--
http://
On 2021-01-19 10:16 +0200, Andrei POPESCU wrote:
> On Ma, 19 ian 21, 02:54:25, Gareth Evans wrote:
>> There is apparently a Python 3 fork of wicd (or two) but I can't
>> figure out what state they're in - are either of these likely to
>> become available in Buster
On Tue, 19 Jan 2021, at 08:16, Andrei POPESCU wrote:
> On Ma, 19 ian 21, 02:54:25, Gareth Evans wrote:
> > There is apparently a Python 3 fork of wicd (or two) but I can't
> > figure out what state they're in - are either of these likely to
> > become availa
On Ma, 19 ian 21, 02:54:25, Gareth Evans wrote:
> There is apparently a Python 3 fork of wicd (or two) but I can't
> figure out what state they're in - are either of these likely to
> become available in Buster repos? Backports?
Wicd is currently only available in experim
There is apparently a Python 3 fork of wicd (or two) but I can't figure out
what state they're in - are either of these likely to become available in
Buster repos? Backports?
https://github.com/PXke/wicd-reloaded
https://github.com/zeph/wicd
The latter is apparently "migrat
Heads-up for those using wicd from sid.
- Forwarded message from Axel Beckert -
Date: Fri, 07 Aug 2020 05:45:41 +0200
From: Axel Beckert
To: Debian Bug Tracking System
Subject: Bug#968033: RM: wicd -- ROM; Version in unstable depends on Python
2.x, Python3 version only in
e nics (there are 2 Ethernets in my
box),. But I'd forgotten to mention why I dumped wicd -- on Jessie and
Buster, at least, wicd won't allow more than a single active
connection at a time. I went to /etc/network/interfaces. Takes a
little more thought (and a lot less RAM), but everybody's happy now.
--
Glenn English
https://answers.launchpad.net/wicd/+faq/1868
Technically, the answer to your first post is the three files
/etc/wicd/*conf whose location emphasises that its effect is designed
to be system-wide: when you logout (or before you login), the
connections are left up for further use. (There
I can't find it but I suppose you mean several connections on the same
interface, since the official website says two interfaces won't be possible
before version 2.0 (last one is 1.7.5).
https://answers.launchpad.net/wicd/+faq/1868
On Tue, Feb 6, 2018 at 10:41 PM, RODARY Jacques wrote:
> Where are the interfaces declared?
Up near the top, in the menu for wired interfaces. If you click on it,
a menu comes down allowing you to define more wire.
That's what happens on Buster, anyway.
--
Glenn English
Hi
I got rid of network-manager: it endlessly came back to the config it got
when I installed Stretch, and couldn't even resolve the URL of the debian
repositories.
But I have a problem with wicd: it knows about my two wired interfaces, but
doesn't allow me to configure a connect
First, the change to nvidia drivers have completely eliminated the
screen lock-ups that required a reboot to get free and ALL of the log
errors from the video drivers are gone.
I've had time to work with Network Manager and Wicd over the weekend,
purging both, reinstalling one at a tim
On 06/19/17 05:14, Brian wrote:
The advice at
https://wiki.debian.org/WiFi/HowToUse#Wicd
... Outdated? Incorrect?
At the least, it hasn't been updated for systemd.
Rick
On Mon 19 Jun 2017 at 13:00:05 +0100, Lisi Reisz wrote:
> On Monday 19 June 2017 12:09:59 Brian wrote:
> > On Mon 19 Jun 2017 at 11:38:28 +0100, Lisi Reisz wrote:
> > > On Monday 19 June 2017 00:24:52 pplaw wrote:
> > > > Hi,
> > > >
> > > &
On Monday 19 June 2017 12:09:59 Brian wrote:
> On Mon 19 Jun 2017 at 11:38:28 +0100, Lisi Reisz wrote:
> > On Monday 19 June 2017 00:24:52 pplaw wrote:
> > > Hi,
> > >
> > > In Stretch, I'd like to use WICD to manage network interfaces,
> > > but
On Mon 19 Jun 2017 at 11:38:28 +0100, Lisi Reisz wrote:
> On Monday 19 June 2017 00:24:52 pplaw wrote:
> > Hi,
> >
> > In Stretch, I'd like to use WICD to manage network interfaces,
> > but when I go through what had been my usual menu with Jessie
> &
On Monday 19 June 2017 00:24:52 pplaw wrote:
> Hi,
>
> In Stretch, I'd like to use WICD to manage network interfaces,
> but when I go through what had been my usual menu with Jessie
> (Programs > Applications > network > Monitoring > WICD), there's
> no Mo
On Sun, Jun 18, 2017 at 05:24:52PM -0600, pplaw wrote:
>
> Hi,
>
> In Stretch, I'd like to use WICD to manage network interfaces,
> but when I go through what had been my usual menu with Jessie
> (Programs > Applications > network > Monitoring > WIC
Hi,
In Stretch, I'd like to use WICD to manage network interfaces,
but when I go through what had been my usual menu with Jessie
(Programs > Applications > network > Monitoring > WICD), there's
no Monitoring > WICD.
How do I access and, thus, launch WICD?
Thanks,
b.
7;t have a route to the internet. Which argues for users filling in
> netmask and gateway for themselves and having something they can trust,
> rather than relying on some iffy wicd method.
Yeah. Their gateway and netmask 'calculations' do leave a little to be desired,
even though
On Sat 30 Jul 2016 at 17:21:47 -0600, ghe wrote:
> Fixing ping made everything all better again -- wicd verifies only on static
> wireless configs. There's a question in my mind why anyone would do that,
> but I'm sure it seemed like a good idea to the programmer.
A su
On Sat 30 Jul 2016 at 12:45:50 +0100, Brian wrote:
> On Fri 29 Jul 2016 at 16:44:43 -0600, ghe wrote:
>
> > When I set up a static IP, wicd fills in the net mask and the default router
> > automatically. I don't know where it gets the info, but the values and the
> &
On Sat 30 Jul 2016 at 18:15:46 (-0600), Glenn English wrote:
>
> > On Jul 30, 2016, at 5:36 PM, David Wright wrote:
> >
> > I think you can have your cake and eat it if you put this as a
> > definition in ~/.bash_profile. That means you get it when you
> > personally login interactively, but not
> On Jul 30, 2016, at 5:36 PM, David Wright wrote:
>
> I think you can have your cake and eat it if you put this as a
> definition in ~/.bash_profile. That means you get it when you
> personally login interactively, but not otherwise (like running
> a script).
Yeah, but the way I did it, root d
On Sat 30 Jul 2016 at 17:21:47 (-0600), ghe wrote:
> I found it, and it was all my doing.
>
> Some time ago, I built a script that replaced "ping" with "ping.dist
> -c 3 $1" (and forgot that I had) so I wouldn't have to type -c 3 all
> the time. That broke ping for everybody else.
I think you can
I found it, and it was all my doing.
Some time ago, I built a script that replaced "ping" with "ping.dist -c
3 $1" (and forgot that I had) so I wouldn't have to type -c 3 all the
time. That broke ping for everybody else.
When I looked at the log of one of the st
On Thu 28 Jul 2016 at 15:15:52 -0600, Glenn English wrote:
>
> > On Jul 28, 2016, at 1:27 PM, David Wright wrote:
> >
> > 2016/07/28 07:35:36 :: Flushing the routing table...
>
> And that's when wicd deletes the routes. But if the table had been set
> up by
er.
Not much thought went into my remark! The routing is torn down and the
device disassociated from the AP because wicd cannot ping the static
gateway, not because the routing is wrong or association hasn't taken
place.
Wicd claims to be verifying access point association when it pings the
gatew
On Friday 29 July 2016 18:07:43 Glenn English wrote:
> > On Jul 29, 2016, at 5:18 AM, Lisi Reisz wrote:
> >
> > On Friday 29 July 2016 01:01:07 Glenn English wrote:
> >> But. When I tried again after telling wicd to use DHCP instead of a
> >> static IP, it suc
On 07/29/2016 07:22 AM, Brian wrote:
It obviously wasn't a reasonable routing table. :) The control socket in
/run probably disappeared too.
Yes it was. Same as I've been using on that net forever.
When I set up a static IP, wicd fills in the net mask and the default
router automa
> On Jul 29, 2016, at 12:19 PM, Brian wrote:
>
> You really intended to delete my perceptive and informative mail and not
> reply to it? I'm in a state of shock and will have to leave this
> conversation and have a lie down.
No, Brian. What I was trying to do was to delete my half-thought-out r
On Fri 29 Jul 2016 at 12:08:16 -0600, Glenn English wrote:
>
> > On Jul 29, 2016, at 12:04 PM, Glenn English wrote:
> >
> >
> >> On Jul 29, 2016, at 11:58 AM, Brian wrote:
> >>
> >> The client surely doesn't need an IP address to communicate with a dhcp
> >> server? With a wired connection a
> On Jul 29, 2016, at 12:04 PM, Glenn English wrote:
>
>
>> On Jul 29, 2016, at 11:58 AM, Brian wrote:
>>
>> The client surely doesn't need an IP address to communicate with a dhcp
>> server? With a wired connection association is automatically present and
>> I suspect the initial communicati
> On Jul 29, 2016, at 11:58 AM, Brian wrote:
>
> The client surely doesn't need an IP address to communicate with a dhcp
> server? With a wired connection association is automatically present and
> I suspect the initial communication involves a MAC and not an IP address.
>
> With WiFi the purpo
On Thu 28 Jul 2016 at 15:15:52 -0600, Glenn English wrote:
> > On Jul 28, 2016, at 1:27 PM, David Wright wrote:
> >
> > The answer may lie in the logs. Mine contains the lines
> >
> > 2016/07/28 07:35:36 :: Setting false IP... ←--
>
> Ah! They set an IP that will get to the
> On Jul 29, 2016, at 5:18 AM, Lisi Reisz wrote:
>
> On Friday 29 July 2016 01:01:07 Glenn English wrote:
>> But. When I tried again after telling wicd to use DHCP instead of a static
>> IP, it successfully connected. It even got the IP I'd set up for the laptop
&g
; an IP number. However, there does not appear to be routing between the
> > interface and the AP.
>
> When I turned on the laptop, the table was empty -- no default, no
> localnet.
>
> I asked wicd to connect to one of my wireless networks and watched the
> table. It was empty
On Friday 29 July 2016 01:01:07 Glenn English wrote:
> But. When I tried again after telling wicd to use DHCP instead of a static
> IP, it successfully connected. It even got the IP I'd set up for the laptop
> over on the DHCP server's config.
Ah! There's the clue,
and the AP.
When I turned on the laptop, the table was empty -- no default, no localnet.
I asked wicd to connect to one of my wireless networks and watched the table.
It was empty for a while, then was populated with what looked to me like a
reasonable routing table. The firewall downstairs (
t; Ah! They set an IP that will get to the DHCP server. I assume that the AP
> will send out something on the Ethernet that makes some sense to the DHCP
> server.
Here is a snippet from my routers log while wicd was trying - and failing to
connect.
[WLAN access allowed
On Thursday 28 July 2016 20:18:38 Brian wrote:
> And if they did it could just as well be wicd (NM) as NM (wicd).
Indeed. I take as much care not to have NM on the computer with wicd as vice
versa. In that saga you helped with so signally, you may have noticed that I
tried both several ti
omething on the Ethernet that makes some sense to the DHCP server.
Might be nice if the log said what the false IP was.
> 2016/07/28 07:35:36 :: Flushing the routing table...
And that's when wicd deletes the routes. But if the table had been set up by
wicd to use the eth0 interface, it wou
ich does the association and authentication. I
> > assume dhclient is used to get an IP and set up routing.
>
> Not here. There's no DHCP -- IPs are static. Wicd does the routing. I'll get
> DHCP running and see if that makes a difference.
>
> But the DHCP server&#
On Thu 28 Jul 2016 at 15:01:14 +0100, Lisi Reisz wrote:
> On Thursday 28 July 2016 14:35:09 Mike McGinn wrote:
> >
> > I had some trouble with wicd which I cured by making sure that network
> > manager was not running. Make sure NM is stopped and does not start.
>
>
> On Jul 28, 2016, at 12:56 PM, Jochen Spieker wrote:
>
>> Don't think so. NM, IIRC, implies Gnome, […]
>
> NACK
>
> I run NM without any of the big desktop environments.
OK. I remember incorrectly, or I got some bad info.
But I still think that's not the problem -- there's no NM around her
> On Jul 28, 2016, at 5:36 AM, Brian wrote:
>
> Indeed; presumably it has decided association and authentication with
> the access point has successfully taken place and the interface has got
> an IP number. However, there does not appear to be routing between the
> interface
Glenn English:
> > On Jul 28, 2016, at 7:35 AM, Mike McGinn
> > wrote:
> >
> > I had some trouble with wicd which I cured by making sure that
> > network manager was not running. Make sure NM is stopped and does
> > not start.
>
> Don't think s
> On Jul 28, 2016, at 7:35 AM, Mike McGinn wrote:
>
> I had some trouble with wicd which I cured by making sure that network
> manager was not running. Make sure NM is stopped and does not start.
Don't think so. NM, IIRC, implies Gnome, and my GUI is XFCD. There's a
ccess point association" mean
> >>
> >> After some looking around, I found that a failure in that phase of
> >> connecting means that wicd tried to ping the AP 10 times, and failed.
> >
> > Indeed; presumably it has decided association and authentication wit
means that wicd tried to ping the AP 10 times, and failed.
Indeed; presumably it has decided association and authentication with
the access point has successfully taken place and the interface has got
an IP number. However, there does not appear to be routing between the
interface and the AP.
Th
On Wed 27 Jul 2016 at 22:36:01 -0600, Glenn English wrote:
> > On Jul 25, 2016, at 5:53 PM, Glenn English wrote:
> >
> > What does "Verifying access point association" mean
>
> After some looking around, I found that a failure in that phase of
> connecting
> On Jul 25, 2016, at 5:53 PM, Glenn English wrote:
>
> What does "Verifying access point association" mean
After some looking around, I found that a failure in that phase of connecting
means that wicd tried to ping the AP 10 times, and failed.
> what do you do to mak
On 2016-07-25 18:53, Glenn English wrote:
What does "Verifying access point association" mean, and what do you
do to make it OK?
I have several Debian boxes, Wheezy and Jessie. Wired and wireless (3
wireless -- wicd manged). 2 of then are Raspberry Pi 3's the other is
a GoBook la
What does "Verifying access point association" mean, and what do you do to make
it OK?
I have several Debian boxes, Wheezy and Jessie. Wired and wireless (3 wireless
-- wicd manged). 2 of then are Raspberry Pi 3's the other is a GoBook laptop.
All 3 are Jessie. All are XFCE4.
On 07/09/2015 11:56 AM, Chris Bannister wrote:
On Thu, Jul 09, 2015 at 09:44:40AM -0400, James P. Wallen wrote:
Between the Debian and Archlinux documentation and a little pondering I was
able to use the OpenVPN client manually with wicd as the network manager.
Which you are going to keep a
On Thu, Jul 09, 2015 at 09:44:40AM -0400, James P. Wallen wrote:
>
> Between the Debian and Archlinux documentation and a little pondering I was
> able to use the OpenVPN client manually with wicd as the network manager.
Which you are going to keep a secret? People are going to see the
g
particular to wicd, but you could use what is there to
set up a script.
There are a few links at the bottom that might also be of
help.
Petter
Thank you, Petter.
I'll try following that document through to a conclusion. I
should always remember to look at the debian.org onlin
documenta
On 07/08/2015 03:17 AM, Petter Adsen wrote:
On Tue, 07 Jul 2015 13:20:35 -0400 "James P. Wallen"
wrote:
On 07/07/2015 08:34 AM, Petter Adsen wrote:
https://wiki.debian.org/OpenVPN
Have you seen this? It doesn't contain anything
particular to wicd, but you could use what is th
On Tue, 07 Jul 2015 13:20:35 -0400
"James P. Wallen" wrote:
> On 07/07/2015 08:34 AM, Petter Adsen wrote:
> > https://wiki.debian.org/OpenVPN
> >
> > Have you seen this? It doesn't contain anything particular to
> > wicd, but you could use what is the
On 07/07/2015 03:26 PM, to...@tuxteam.de wrote:
...
I suppose I could set up a server on the home network. That
would protect my traffic from prying eyes when I'm a
visitor on another network, but it wouldn't really keep my
home ISP from snooping on me. Or am I missing something?
There has to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jul 07, 2015 at 01:32:21PM -0400, James P. Wallen wrote:
> On 07/07/2015 09:23 AM, to...@tuxteam.de wrote:
[...]
> So -- if I understand -- you have control of a server out there on
> the Internet, and that's what makes this work for you.
Ri
nothing to do with corporate firewalls
[...]
Network-manager, as you're aware, has plugins for various
types of VPN software. It's easy to use, but it just seems
to be awfully large and, occasionally, a little
trouble-prone compared to wicd.
This was my impression too. Since I tend fo
of you has managed to do this in conjunction
with wicd, I'd really appreciate a pointer to
information to help me get started. The man pages are
kicking me in the boinloins.
FWIW -- I set up OpenVPN (don't like it much[1], but had
to) without either NetworkManager nor wicd. What
[...]
> Network-manager, as you're aware, has plugins for various types of
> VPN software. It's easy to use, but it just seems to be awfully
> large and, occasionally, a little trouble-prone compared to wicd.
This was my impression too. Since I tend for "simple", I try to
a
;
> > [...]
> >
> >> If any of you has managed to do this in conjunction with
> >> wicd, I'd really appreciate a pointer to information to
> >> help me get started. The man pages are kicking me in the
> >> boinloins.
> >
> > F
On 07/07/2015 04:25 AM, to...@tuxteam.de wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On Mon, Jul 06, 2015 at 04:23:28PM -0400, James P. Wallen
wrote:
[...]
If any of you has managed to do this in conjunction with
wicd, I'd really appreciate a pointer to information to
help m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jul 06, 2015 at 04:23:28PM -0400, James P. Wallen wrote:
[...]
> If any of you has managed to do this in conjunction with wicd, I'd
> really appreciate a pointer to information to help me get started.
> The man pages are kic
I loved wicd and used it for several years but finally gave up
and went with network-manager so that I could easily use a
private VPN when I'm out-and-about and connecting to access
points on the road.
I've never really been thrilled with network-manager, though at
least it w
On 2015-04-16 21:40, German wrote:
Ok, I installed realtek firmware, running modrpobe rtl8723be returns
no output, so I think my card is operational. But Wicd doesn't show
any wireless networks. Where to go from here? Thank you
In wicd-client, have you switched on WiFi and set Prefer
On 17 Apr 2015 11:04:02 GMT
Kruppt wrote:
> On 2015-04-16, German wrote:
> > Ok, I installed realtek firmware, running modrpobe
> > rtl8723be returns no output, so I think my card is
> > operational. But Wicd doesn't show any wireless networks.
> >
Hi!
Sometimes it makes sense, to deistall and purge network-manager when using
wicd.
Try this out.
Good luck!
Hans
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Arch
On 2015-04-16, German wrote:
> Ok, I installed realtek firmware, running modrpobe
> rtl8723be returns no output, so I think my card is
> operational. But Wicd doesn't show any wireless networks.
> Where to go from here? Thank you
>
> --
> German
>
>
>From
man (gentger...@gmail.com):
>> > > > Ok, I installed realtek firmware, running modrpobe rtl8723be
>> > > > returns
>> > no output, so I think my card is operational. But Wicd doesn't show
>> > any wireless networks. Where to go from here? Than
ing modrpobe rtl8723be
> > > > returns
> > no output, so I think my card is operational. But Wicd doesn't show
> > any wireless networks. Where to go from here? Thank you
> > >
> > > Does iwconfig show a wireless interface?
> > >
> >
2015-04-16 22:22 GMT+02:00 German :
> On Thu, 16 Apr 2015 15:12:30 -0500
> David Wright wrote:
>
> > Quoting German (gentger...@gmail.com):
> > > Ok, I installed realtek firmware, running modrpobe rtl8723be returns
> no output, so I think my card is operational
On Thu, 16 Apr 2015 15:12:30 -0500
David Wright wrote:
> Quoting German (gentger...@gmail.com):
> > Ok, I installed realtek firmware, running modrpobe rtl8723be returns no
> > output, so I think my card is operational. But Wicd doesn't show any
> > wireless netwo
Quoting German (gentger...@gmail.com):
> Ok, I installed realtek firmware, running modrpobe rtl8723be returns no
> output, so I think my card is operational. But Wicd doesn't show any wireless
> networks. Where to go from here? Thank you
Does iwconfig show a wireless inter
Ok, I installed realtek firmware, running modrpobe rtl8723be returns no output,
so I think my card is operational. But Wicd doesn't show any wireless networks.
Where to go from here? Thank you
--
German
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subje
On Wednesday 17 September 2014 14:12:27 Curt wrote:
> On 2014-09-16, tom arnall wrote:
> > root@debian:~#/home/tom/system/wireless# apt-get purge wicd
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Packag
On 2014-09-16, tom arnall wrote:
>
> root@debian:~#/home/tom/system/wireless# apt-get purge wicd
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Package 'wicd' is not installed, so not removed
On Wed, Sep 17, 2014 at 01:05:00AM -0400, Cindy-Sue Causey wrote:
> I tested "dpkg -s wicd" and received back the "Package `wicd' is not
> installed" error.
> Tried "which wicd" not expecting to find anything and instead was told
> "/usr/
On 9/15/14, tom arnall wrote:
> I want to get wicd off my system, but am having a problem. All the
> installer utilities say that it's not installed, but 'which' and other
> things tell a different story:
>
> root@debian:~# which wicd
> /usr/sbin/wicd
> root
On 9/16/14, Bob Holtzman wrote:
> On Mon, Sep 15, 2014 at 11:47:22PM -0400, Gary Dale wrote:
>
> ...snip...
>>
>> What the message is telling is that there is no package installed
>> called wicd. You need to find out (try searching
>> packages.
On Mon, Sep 15, 2014 at 11:47:22PM -0400, Gary Dale wrote:
...snip...
>
> What the message is telling is that there is no package installed
> called wicd. You need to find out (try searching
> packages.debian.org) which package wicd is part of.
Highly doubtful as sy
2014-09-16 05:37 keltezéssel, tom arnall írta:
> I want to get wicd off my system, but am having a problem. All the
> installer utilities say that it's not installed, but 'which' and other
> things tell a different story:
>
> root@debian:~# which wicd
> I want to get wicd off my system, but am having a problem. All the
> installer utilities say that it's not installed
As Gary Dale has pointed out, you should probably be looking at
packages names other than plain "wicd".
> root@debian:~# which wicd
> /usr/sbin/wic
On Mon, 15 Sep 2014 20:37:02 -0700
tom arnall wrote:
> How do I get rid of the stuff?
apt-get install wicd
apt-get purge wicd
--
Men94 : You've got MSN?
Aerendil : No, but I have a STD if you want.
Men94 : cool send it.
signature.asc
Description: PGP signature
On 15/09/14 11:37 PM, tom arnall wrote:
I want to get wicd off my system, but am having a problem. All the
installer utilities say that it's not installed, but 'which' and other
things tell a different story:
root@debian:~# which wicd
/usr/sbin/wicd
root@debian:~#
Also,
I want to get wicd off my system, but am having a problem. All the
installer utilities say that it's not installed, but 'which' and other
things tell a different story:
root@debian:~# which wicd
/usr/sbin/wicd
root@debian:~#
Also, in spite of the installer messages, there a
Joel Roth wrote at 2014-08-06 11:26 -0500:
> On Tue, Aug 05, 2014 at 04:54:42PM -1000, Joel Roth wrote:
> > In some airports, and today at a university
> > I've failed to join "unsecured" networks.
> >
> > I've been using wicd-gtk.
> >
> &
On Tue, Aug 05, 2014 at 04:54:42PM -1000, Joel Roth wrote:
> Hi all,
>
> In some airports, and today at a university
> I've failed to join "unsecured" networks.
>
> I've been using wicd-gtk.
>
> The failure takes the form of a time-out during the get
Hi all,
In some airports, and today at a university
I've failed to join "unsecured" networks.
I've been using wicd-gtk.
The failure takes the form of a time-out during the get IP
address stage.
I had a look at /var/log/wicd/wicd.log.
2014/08/05 09:51:29 :: Connecting to
the b43 module was the answer for at least most of the broadcom
wireless devices. HOWEVER the system out of the debian wheezy box
seems to want to make 'wl' the wireless module. wrong for broadcom
chips. but it's not enough to simply let the b43 installer do its
thing. you must also blacklist wl.
BTW, I DO NOT SEEM TO HAVE ANY OF THE B43 STUFF ON MY SYSTEM:
root@debian:/home/tom# apt-get install firmware-b43-installer
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
b43-fwcutter
The following NEW pack
;ya'll come" virus. It invites all the others
onto your computer.
On 5/18/14, tom arnall wrote:
> I'm trying to get my wifi set up under wheezy using wicd.
>
> I've followed all the instructions at:
>
> https://wiki.debian.org/WiFi/HowToUse#Wicd
>
&
Hmm,
Thought about it. Typed:
adrastea ~ 26 $ apt-cache search tigon
firmware-linux-nonfree - Binary firmware for various drivers in the Linux
kernel
Have you installed the non-free firmware? If not please do so and start again
from:
m-a a-i broadcom-sta
Mike
On Monday, May 26, 2014 19:45:24 t
@ Mike McGinn
I COPIED AND PASTED YOUR CODE INTO A BASH FILE AND RAN IT. THE INSTALL
MESSAGES SEEMED OK, EXCEPT THIS AT THE VERY END:
Update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3
W: Possible missing firmw
roadcom-sta-dkms
> This will also install the recommended wireless-tools package. DKMS
> will build the wl module for your system.
> Unload conflicting modules:
> # modprobe -r b44 b43 b43legacy ssb brcmsmac
> Load the wl module:
> # modprobe wl
> Configure your wireless interface
appropriate. See also known issues.
I REBOOTED AND DID THE LAST TWO COMMANDS.
I FIRED UP WICD AND GOT THE USUAL "No wireless networks found."
THEN I CHECKED TO SEE THE STATUS OF THE DEVICE. VOILA! IT'S NOT THERE, AS IN:
Root@debian:/home/tom# ifconfig -a
eth0 Link encap:Et
1 - 100 of 277 matches
Mail list logo
