Re: Clé USB Wifi détectée mais pas par Wicd (résolu)

et qu'elle soit 802.11AC. Merci encore Didier de ton aide, qui a abouti à un succès, et de tes piqûres de rappel bien utiles sur la WiFi. Après la migration vers Bullseye, je devrais arrêter Wicd, (qui sera abandonné, SNIF !) et remplacé par Connman. Bonne fin de soirée. AJH Valmer

Re: Clé USB Wifi Ralink détecté mais pas par Wicd [RÉSOLU]

Bonsoir à tous, Mes 2 clés USB basées sur le chipset Ralink, ma carte PCI WiFi Realtek rtl8187 sont bien opérationnelles globalement ainsi qu'avec Wicd. Je vois maintenant toutes les wifi autour de moi. J'ai édité les 2 fichiers : /etc/wicd/wireless-settings.conf /etc/wicd/manager-settings.conf

Re: Clé USB Wifi détectée mais pas par Wicd

Le jeudi 4 novembre 2021 à 23:50:03 UTC+1, ajh-valmer a écrit : > Super merci ! Elle à l'air très bien, > sauf que je la trouve un peu chère :-) > > Je vois celle-ci (prix plus modeste) : > TP-Link TL-WN781ND Adaptateur PCI Express Wi-Fi N 150 Mbps > (bien compatible Linux). > > Le slot

Re: Clé USB Wifi détectée mais pas par Wicd

> Le jeudi 04 novembre 2021 à 18:19 +0100, ajh-valmer a écrit : > > Quelle clé USB WiFi est bien détectée et installable sous Linux, > > (de préférence sous Debian Buster et Bullseye) ? On Thursday 04 November 2021 19:47:34 didier gaumet wrote: > J'ai un Netgear AC1200 (famille de produits) A6210

Re: Clé USB Wifi détectée mais pas par Wicd

Le jeudi 04 novembre 2021 à 18:19 +0100, ajh-valmer a écrit : > Hello à tous, > > Quelle clé USB WiFi est bien détectée et installable sous Linux, > (de préférence sous Debian Buster et Bullseye) ? > > Merci d'avance. > > A. Valmer > > J'ai un Netgear AC1200 (famille de produits) A6210

Re: Clé USB Wifi détectée mais pas par Wicd

Hello à tous, Quelle clé USB WiFi est bien détectée et installable sous Linux, (de préférence sous Debian Buster et Bullseye) ? Merci d'avance. A. Valmer

Re: Clé USB Wifi Ralink détecté mais pas par Wicd

On Wednesday 03 November 2021 15:41:37 didier gaumet wrote: > Le mercredi 03 novembre 2021 à 15:24 +0100, ajh-valmer a écrit : > > Si, il est bien indiqué dans mon /etc/network/interfaces, > > et même si pas indiqué, Wicd n'en a pas besoin. > > (c'est le cas sur mes

Re: Clé USB Wifi Ralink détecté mais pas par Wicd

Le mercredi 03 novembre 2021 à 15:24 +0100, ajh-valmer a écrit : [...] > Si, il est bien indiqué dans mon /etc/network/interfaces, > et même si pas indiqué, Wicd n'en a pas besoin. > (c'est le cas sur mes 2 autres ordinateurs. > iwlist wlp0s26u1u3 scan > voit bien la clé WiFi [.

Re: Clé USB Wifi Ralink détecté mais pas par Wicd

On Wednesday 03 November 2021 14:53:13 didier gaumet wrote: > > Le mercredi 03 novembre 2021 à 12:47 +0100, ajh-valmer a écrit : > > - network-manager a t-il une interface graphique ? > > - Peut-on installer à la fois network-manager + Wicd ? > >   (ou faut-il désinstaller

Re: Clé USB Wifi Ralink détecté mais pas par Wicd

Le mercredi 03 novembre 2021 à 12:47 +0100, ajh-valmer a écrit : [...] > - network-manager a t-il une interface graphique ? > - Peut-on installer à la fois network-manager + Wicd ? >   (ou faut-il désinstaller Wicd ?) > - Qu'est ce que "nm-applet" ? Wicd a des interfac

Re: Clé USB Wifi Ralink détecté mais pas par Wicd

On Tuesday 02 November 2021 14:54:37 benoit wrote: > Idem pour ma clé 4G, c'est un grand mystère... > Je me suis aperçu par hasard que network-manager la détecte automatiquement. > Du coup quand j'installe une deb, je vire wicd et j'installe network-manager > et nm-applet. >

Re: Clé USB Wifi Ralink détecté mais pas par Wicd

Le mardi 02 novembre 2021 à 13:54 +, benoit a écrit : > Idem pour ma clé 4G, c'est un grand mystère... > Je me suis aperçu par hasard que network-manager la détecte > automatiquement. > Du coup quand j'installe une deb, je vire wicd et j'installe network- > manager et nm-a

Re: Clé USB Wifi Ralink détecté mais pas par Wicd

Le mardi 02 novembre 2021 à 14:31 +0100, ajh-valmer a écrit : > Hello à tous, > > Ma clé USB Wifi, modèle Ralink, est bien détecté et fonctionne > par le fichier "/etc/network/interfaces", > mais pas du tout par Wicd ainsi que toutes les connexions Wifi > des e

Re : Clé USB Wifi Ralink détecté mais pas par Wicd

Idem pour ma clé 4G, c'est un grand mystère... Je me suis aperçu par hasard que network-manager la détecte automatiquement. Du coup quand j'installe une deb, je vire wicd et j'installe network-manager et nm-applet. Si qlq trouve pourquoi nm la configure automatiquement et pas wicd, je suis

Clé USB Wifi Ralink détecté mais pas par Wicd

Hello à tous, Ma clé USB Wifi, modèle Ralink, est bien détecté et fonctionne par le fichier "/etc/network/interfaces", mais pas du tout par Wicd ainsi que toutes les connexions Wifi des environs. Rien. ifconfig : wlp0s26u1u3: flags=4163 mtu 1500 inet 192.168.1.21 netmask 255

Re: Python 3 wicd

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 also

Re: Python 3 wicd

one 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://

Re: Python 3 wicd

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 repos?

Re: Python 3 wicd

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 available in Bus

Re: Python 3 wicd

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 experimental (

Python 3 wicd

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 "migrated ups

Re: alternativa a wicd

El lun, 21-09-2020 a las 15:33 +0200, Camaleón escribió: > El 2020-09-21 a las 10:18 -0300, Gonzalo Rivero escribió: > > > actualicé mi sistema y vi que desapareció wicd de testing y > > unstable ( > > https://packages.debian.org/experimental/wicd-gtk ), pero está en >

Re: alternativa a wicd

El 2020-09-21 a las 10:18 -0300, Gonzalo Rivero escribió: > actualicé mi sistema y vi que desapareció wicd de testing y unstable ( > https://packages.debian.org/experimental/wicd-gtk ), pero está en > experimental, ¿que otra cosa puedo instalar para conectar 'fácil' > wifi/etherne

alternativa a wicd

Holas, actualicé mi sistema y vi que desapareció wicd de testing y unstable ( https://packages.debian.org/experimental/wicd-gtk ), pero está en experimental, ¿que otra cosa puedo instalar para conectar 'fácil' wifi/ethernet, además de networkmanager?

FW: Bug#968033: RM: wicd -- ROM; Version in unstable depends on Python 2.x, Python3 version only in experimental so far

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

Re: problème de connexion avec Wicd

; https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833929 > > Pourtant, il y a une case à cocher "Connexion automatique". > Chez moi, Wicd me connecte bien au boot sans action manuelle. > (Buster 32 bits). sauf que comme indiqué, il y a des conditions "not self.gui_open

Re: problème de connexion avec Wicd

y a une case à cocher "Connexion automatique". Chez moi, Wicd me connecte bien au boot sans action manuelle. (Buster 32 bits). Bonne soirée.

Re: problème de connexion avec Wicd

Bonjour, On 2020-04-23 15:58:46 +0200, MERLIN Philippe wrote: > Depuis quelque temps lors de mes connexions Wifi à un site j'ai ce > phénomène suivant Wicd émet le message "connexion effectuée" suivi > après un certain temps du message suivant "Non connecté" quand ce

Re: problème de connexion avec Wicd

Hmmm perso je ne réussis pas à utiliser wicd (gros problèmes lorsqu’il s’agit de configurer une connexion wifi pour la 1ère fois, suite à une installation par exemple). Du coup je le vire systématiquement et j’utilise connman à la place. Beaucoup plus simple d’utilisation à mon avis. Je ne

Re: problème de connexion avec Wicd

On parle de wicd donc de sa configuration. . on peut se connecter sans le fichier interfaces (ce que l'on fait généralement) qui n'est plus utilisé de nos jours . le paquet net-tools n'est plus installé automatiquement, on utilise ip en remplacement Bref, ce que je dis c'est que tant que

Re: problème de connexion avec Wicd

si la connexion est effectuée réellement je n'ai aucune > >> coupure de cette connexion c'est très stable. > > Avec ce mail additif, > > la connexion WiFi se fait-elle ou pas ? > > (wicd ou autres moyens). > > Peux tu envoyer le contenu de ton fichier : > > /etc/network/interfaces > > Merci, bonne fin de journée.

Re: problème de connexion avec Wicd

On Thursday 23 April 2020 17:25:59 MERLIN Philippe wrote: > Je me suis mal exprimé, je veux dire si la connexion est > considérée comme effective par wicd apparition d'une adresse IP > il n'y a pas d'interruption de la connexion durant toute la > session. Désolé, je comprends

Re: problème de connexion avec Wicd

connexion est effectuée réellement je n'ai aucune coupure de cette connexion c'est très stable. Bonjour, Avec ce mail additif, la connexion WiFi se fait-elle ou pas ? (wicd ou autres moyens). Peux tu envoyer le contenu de ton fichier : /etc/network/interfaces Merci, bonne fin de journée.

Re: problème de connexion avec Wicd

re de cette connexion c'est très stable. > > Bonjour, > > Avec ce mail additif, > la connexion WiFi se fait-elle ou pas ? > (wicd ou autres moyens). > > Peux tu envoyer le contenu de ton fichier : > /etc/network/interfaces > > Merci, bonne fin de journée. Je

Re: problème de connexion avec Wicd

connexion WiFi se fait-elle ou pas ? (wicd ou autres moyens). Peux tu envoyer le contenu de ton fichier : /etc/network/interfaces Merci, bonne fin de journée.

Re: problème de connexion avec Wicd

rlin > il n'y a pas network-manager ou autre chose qui "pique" la connexion à wicd ?

Re: problème de connexion avec Wicd

Bonjour, En relisant mon message je me suis rendu compte que j'avais oublié d'indiquer ceci si la connexion est effectuée réellement je n'ai aucune coupure de cette connexion c'est très stable. Philippe Merlin

problème de connexion avec Wicd

Bonjour, Depuis quelque temps lors de mes connexions Wifi à un site j'ai ce phénomène suivant Wicd émet le message "connexion effectuée" suivi après un certain temps du message suivant "Non connecté" quand cela arrive inutile d'essayer de se reconnecter j'y arrive jamais. L

Re: Re wicd vs network-manager

ing of multiple 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 everyb

Re: Re wicd vs network-manager

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's a ~/

Re:Re wicd vs network-manager

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

Re: wicd vs network-manager

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

wicd vs network-manager

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 connection on one

Nvidia, NetworkManager, Wicd and Mate-Panel

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 time

Re: Stretch--how to launch WICD, which isn't in the menu

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

Re: Stretch--how to launch WICD, which isn't in the menu

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, > > > > > > > &

Re: Stretch--how to launch WICD, which isn't in the menu

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

Re: Stretch--how to launch WICD, which isn't in the menu

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 > > (

Re: Stretch--how to launch WICD, which isn't in the menu

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 Monitori

Resolved [was Re: Stretch--how to launch WICD, which isn't in the menu]

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 > WICD), t

Stretch--how to launch WICD, which isn't in the menu

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.

Deux icônes wicd en bas barre des têches

Bonjour, Sous le bureau tde-trinity, j'ai toujours 2 icônes wicd en bas de la barre des tâches à droite, qui correspondent à ces 2 processus python : /usr/bin/python -O /usr/share/wicd/gtk/wicd-client.py --tray /usr/bin/python -O /usr/share/wicd/gtk/wicd-client.py Si je "kill" u

Re: Esquecer Rede WIFI Wicd

On 07-10-2016 09:25, JardelVdaS wrote: > Alguém saber como esquecer rede wifi Wicd? > Exemplo, clico com o direito do mouse, esquecer rede. > > Outro problema, marcando nunca se conectar mesmo assim conecta. > > lsb_release -a > No LSB modules are available. > D

Re: Esquecer Rede WIFI Wicd

ardeldasilva2...@gmail.com> escreveu: > Em 07-10-2016 10:01, Fred Maranhão escreveu: > > 2016-10-07 9:25 GMT-03:00 JardelVdaS <jardeldasilva2...@gmail.com>: > >> Alguém saber como esquecer rede wifi Wicd? >> > > um botão 'esquecer a rede' não conheço. mas se vo

Re: Esquecer Rede WIFI Wicd

Em 07-10-2016 10:01, Fred Maranhão escreveu: 2016-10-07 9:25 GMT-03:00 JardelVdaS <jardeldasilva2...@gmail.com <mailto:jardeldasilva2...@gmail.com>>: Alguém saber como esquecer rede wifi Wicd? um botão 'esquecer a rede' não conheço. mas se você clicar no botão 'propriedade

Re: Esquecer Rede WIFI Wicd

2016-10-07 9:25 GMT-03:00 JardelVdaS <jardeldasilva2...@gmail.com>: > Alguém saber como esquecer rede wifi Wicd? > um botão 'esquecer a rede' não conheço. mas se você clicar no botão 'propriedades' da rede e apagar a senha, deve ter um efeito parecido, não? > Exemplo, clico c

Esquecer Rede WIFI Wicd

Alguém saber como esquecer rede wifi Wicd? Exemplo, clico com o direito do mouse, esquecer rede. Outro problema, marcando nunca se conectar mesmo assim conecta. lsb_release -a No LSB modules are available. Distributor ID:Debian Description:Debian GNU/Linux 8.6 (jessie) Release:8.6

Re: wicd trouble [Solved]

eing pinged > needn'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,

Re: wicd trouble [Solved]

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 succes

Re: wicd trouble -- continued

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 >

Re: wicd trouble [Solved]

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

Re: wicd trouble [Solved]

> 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,

Re: wicd trouble [Solved]

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

Re: wicd trouble [Solved]

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 static

Re: wicd trouble -- continued

On Thu 28 Jul 2016 at 15:15:52 -0600, Glenn English wrote: > > > On Jul 28, 2016, at 1:27 PM, David Wright <deb...@lionunicorn.co.uk> wrote: > > > > 2016/07/28 07:35:36 :: Flushing the routing table... > > And that's when wicd deletes the routes. But if th

Re: wicd trouble -- continued

uch 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 gateway; it is d

Re: wicd trouble -- continued

On Friday 29 July 2016 18:07:43 Glenn English wrote: > > On Jul 29, 2016, at 5:18 AM, Lisi Reisz <lisi.re...@gmail.com> 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

Re: wicd trouble -- continued

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 automatically. I

Re: wicd trouble -- continued

> 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

Re: wicd trouble -- continued

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

Re: wicd trouble -- continued

> 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

Re: wicd trouble -- continued

> 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. >

Re: wicd trouble -- continued

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

Re: wicd trouble -- continued

> On Jul 29, 2016, at 5:18 AM, Lisi Reisz <lisi.re...@gmail.com> 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 se

Re: wicd trouble -- continued

he interface has got > > 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

Re: wicd trouble -- continued

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, I would guess.

Re: wicd trouble -- continued

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 for a while, then was populated with what looked to me like a reasonable routing table.

Re: wicd trouble -- continued

. ←-- > > 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.

Re: wicd trouble -- continued

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

Re: wicd trouble -- continued

hat the AP will send out something 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 t

Re: wicd trouble -- continued

t; > It is wpa_supplicant which 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. >

Re: wicd trouble -- continued

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. >

Re: wicd trouble -- continued

> 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 --

Re: wicd trouble -- continued

to be routing between the > interface and the AP. Wicd 'edits' the routing table. I can tell if the route exists either before or after wicd. Maybe I can bring up a terminal and examine the table while wicd's trying to ping. I've seen wicd create some peculiar routing tables. > The issue is whether it

Re: wicd trouble -- continued

Glenn English: > > On Jul 28, 2016, at 7:35 AM, Mike McGinn <mikemcg...@mcginnweb.net> > > 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 sta

Re: wicd trouble -- continued

> On Jul 28, 2016, at 7:35 AM, Mike McGinn <mikemcg...@mcginnweb.net> 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 GU

Re: wicd trouble -- continued

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. > > > > Indeed; presumably it has decided associa

Re: wicd trouble -- continued

re 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 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 inte

Re: wicd trouble -- continued

On Wed 27 Jul 2016 at 22:36:01 -0600, Glenn English wrote: > > On Jul 25, 2016, at 5:53 PM, Glenn English <g...@slsware.net> wrote: > > > > What does "Verifying access point association" mean > > After some looking around, I found that a failure in th

Re: wicd trouble -- continued

> On Jul 25, 2016, at 5:53 PM, Glenn English <g...@slsware.net> 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.

Re: wicd trouble

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 lap

wicd trouble

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. A fe

Re: Deux icônes wicd

r mes trois autres PC je n'ai qu'une seule icône wicd, > > avec exactement la même configuration que celui qui affiche > > deux icônes ? André > > > On Wednesday 11 November 2015 00:26:17 Bernard Schoenacker wrote: > ce n'est pas pareil, regarde en détail ton profil &quo

Re: Deux icônes wicd

On Wednesday 11 November 2015 00:26:17 Bernard Schoenacker wrote: > Le Tue, 10 Nov 2015 23:32:16 +0100, > andre_deb...@numericable.fr a écrit : > > Comment se fait-il que sous le bureau TDE (trinity), > > "wicd" semble lancé deux fois. > > Il y a deux icônes d

Re: Deux icônes wicd

Le Wed, 11 Nov 2015 10:59:25 +0100, andre_deb...@numericable.fr a écrit : > On Wednesday 11 November 2015 00:26:17 Bernard Schoenacker wrote: > > Le Tue, 10 Nov 2015 23:32:16 +0100, > > andre_deb...@numericable.fr a écrit : > > > Comment se fait-il que sous le bureau TD

Re: Mr Bernard (était Re: Deux icônes wicd

Le Wed, 11 Nov 2015 07:42:45 +0100, Georges a écrit : > Le Wed, 11 Nov 2015 00:26:17 +0100, > > BS a écrit : > > > Le Tue, 10 Nov 2015 23:32:16 +0100, > > andre_deb...@numericable.fr a écrit : > > > > > Bonsoir, > [couic ...] > > bonjour, > [couic ..] > >

Re: Deux icônes wicd

Le Tue, 10 Nov 2015 23:32:16 +0100, andre_deb...@numericable.fr a écrit : > Bonsoir, > > Comment se fait-il que sous le bureau TDE (trinity), > "wicd" semble lancé deux fois. > > Il y a deux icônes dans la barre des tâches, en bas, à droite. > > J'ai bien

Mr Bernard (était Re: Deux icônes wicd

Le Wed, 11 Nov 2015 00:26:17 +0100, BS a écrit : > Le Tue, 10 Nov 2015 23:32:16 +0100, > andre_deb...@numericable.fr a écrit : > > > Bonsoir, [couic ...] > bonjour, [couic ..] > réponse : > > tout simplement que tu emploie un réseau filaire et l'autre est prévu > pour le wifi ( adresse IP

Deux icônes wicd

Bonsoir, Comment se fait-il que sous le bureau TDE (trinity), "wicd" semble lancé deux fois. Il y a deux icônes dans la barre des tâches, en bas, à droite. J'ai bien un seul processus "wicd" dans /etc/init.d/ et /etc/rc2.d/ Merci. André

[Solved] Re: Using OpenVPN client with wicd

anything 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

  1   2   3   4   5   >