Le 20/07/2018 à 03:39, Haines Brown a écrit :
So I wrote the stanza manually:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="",
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
I put this interface stanza in /etc/network/interfaces:
auto wlx
I long struggled getting a wireness connection to Internet and now
seem to have resolved the problem. I could get eth0 running, but not
wireless. I'm runing devuan ASCII on a desktop with a ThinkPenguin USB
dongle.
The problem was that
/etc/udev/rules/0-persistent-net.rules␕70-persistent-net.r
On Tue, Jul 10, 2018 at 04:38:42PM -0700, Gregory Nowak wrote:
> On Tue, Jul 10, 2018 at 02:34:52PM -0400, Haines Brown wrote:
> > allow hotplug eth0
>
> I believe that should be allow-hotplug but since I'm still running
> jessie, it's possible this has changed in Ascii.
Greg, thanks for your r
Le 10/07/2018 à 20:34, Haines Brown a écrit :
I've still not got things working.
# iwconfig shows my USB network dongle to have the value: wlx2824ff1a1794
So in /etc/network/interfaces I have:
auto lo
iface lo inet loopback
allow hotplug eth0
iface inet eth0 dhcp
auto
On Tue, Jul 10, 2018 at 02:34:52PM -0400, Haines Brown wrote:
> allow hotplug eth0
I believe that should be allow-hotplug but since I'm still running
jessie, it's possible this has changed in Ascii.
> iface inet eth0 dhcp
>
> auto wlx2824ff1a1794
You might want to replace that auto with
I've still not got things working.
# iwconfig shows my USB network dongle to have the value: wlx2824ff1a1794
So in /etc/network/interfaces I have:
auto lo
iface lo inet loopback
allow hotplug eth0
iface inet eth0 dhcp
auto wlx2824ff1a1794
iface wlx2824ff1a1794 inet dhcp
wp
On Wed, Jul 04, 2018 at 12:19:57PM +0200, Didier Kryn wrote:
> On laptops, I have wifi roaming
> with many different wifi stations recorded, and automatic connection to the
> present station, with priority to Ethernet when plugged in.
This sounds like exactly what I want.
> Everything
> simple,
El 04/07/18 a las 09:54, Jimmy Johnson escribió:
I've never heard of wicd doing anything wrong, it's certainly not part
of systemd or married to systemd in any way.
But it depends on dbus.
Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https
On Wed, 4 Jul 2018 at 02:53:05 -0700
Jimmy Johnson wrote:
> On 07/04/2018 02:28 AM, KatolaZ wrote:
>> On Wed, Jul 04, 2018 at 02:15:46AM -0700, Jimmy Johnson wrote:
>>
>> [cut]
>>
I used wicd for several years, and I had always to swear against the
gods of three or four religio
Le 04/07/2018 à 11:33, John Hughes a écrit :
On 04/07/18 11:04, Didier Kryn wrote:
3) network-manager, which is a replacement for the previous,
decides of everything, and cannot be configured.
?
man nmcli
No manual entry for nmcli
But this is just because I haven't network-man
On 07/04/2018 02:28 AM, KatolaZ wrote:
On Wed, Jul 04, 2018 at 02:15:46AM -0700, Jimmy Johnson wrote:
[cut]
I used wicd for several years, and I had always to swear against the
gods of three or four religions to have it do what I wanted. The
hardest thing was to convince wicd that I wanted a
On Wed, Jul 04, 2018 at 02:15:46AM -0700, Jimmy Johnson wrote:
[cut]
> >
> > I used wicd for several years, and I had always to swear against the
> > gods of three or four religions to have it do what I wanted. The
> > hardest thing was to convince wicd that I wanted a *specific* wi-fi
> > conne
On 07/04/2018 02:04 AM, Didier Kryn wrote:
Le 04/07/2018 à 09:54, Jimmy Johnson a écrit :
On 07/03/2018 11:04 PM, Didier Kryn wrote:
Le 04/07/2018 à 05:10, Jimmy Johnson a écrit :
On 07/03/2018 09:35 AM, Didier Kryn wrote:
Le 02/07/2018 à 10:49, Jimmy Johnson a écrit :
There is another option
On 07/04/2018 01:25 AM, KatolaZ wrote:
On Wed, Jul 04, 2018 at 12:54:28AM -0700, Jimmy Johnson wrote:
[cut]
It sounds like you are talking about network manager. I don't believe wicd
has the traits you are talking about. As for me it's handy to connect and
disconnect, mostly disconnect whil
Le 04/07/2018 à 09:54, Jimmy Johnson a écrit :
On 07/03/2018 11:04 PM, Didier Kryn wrote:
Le 04/07/2018 à 05:10, Jimmy Johnson a écrit :
On 07/03/2018 09:35 AM, Didier Kryn wrote:
Le 02/07/2018 à 10:49, Jimmy Johnson a écrit :
There is another option I do not see mentioned in this thread and
On Wed, Jul 04, 2018 at 12:54:28AM -0700, Jimmy Johnson wrote:
[cut]
>
> It sounds like you are talking about network manager. I don't believe wicd
> has the traits you are talking about. As for me it's handy to connect and
> disconnect, mostly disconnect while using multimedia. I've never hea
On 07/03/2018 11:04 PM, Didier Kryn wrote:
Le 04/07/2018 à 05:10, Jimmy Johnson a écrit :
On 07/03/2018 09:35 AM, Didier Kryn wrote:
Le 02/07/2018 à 10:49, Jimmy Johnson a écrit :
There is another option I do not see mentioned in this thread and
that is to purge network manager and use wicd ex
Le 04/07/2018 à 05:10, Jimmy Johnson a écrit :
On 07/03/2018 09:35 AM, Didier Kryn wrote:
Le 02/07/2018 à 10:49, Jimmy Johnson a écrit :
There is another option I do not see mentioned in this thread and
that is to purge network manager and use wicd exclusively, I have
done that and it works sw
On 07/03/2018 09:35 AM, Didier Kryn wrote:
Le 02/07/2018 à 10:49, Jimmy Johnson a écrit :
There is another option I do not see mentioned in this thread and that
is to purge network manager and use wicd exclusively, I have done that
and it works swell.
Better purge both.
Didier
Le 02/07/2018 à 10:49, Jimmy Johnson a écrit :
There is another option I do not see mentioned in this thread and that
is to purge network manager and use wicd exclusively, I have done that
and it works swell.
Better purge both.
Didier
On 06/30/2018 02:06 PM, Haines Brown wrote:
I've long struggled with a problem with a new installation of ascii. I
can get an ethernet connection, but with a usb WiFi dongle using an
Atheros chip, my wlan0 interface gets automatically changed to wl, and so cannot communicate with DHCP.
This can
Hi ,
El 01/07/18 a las 16:38, aitor_czr escribió:
I'll send you a video in a few minutes showing a bug in the netstat
icon of wicd using non renamed devices (I have not been able to
reproduce this bug in the case of renamed devices).
Here you are the video (low quality):
gnuinos.org/wicd.mpg
Hi again,
El 01/07/18 a las 16:20, Haines Brown escribió:
On Sun, Jul 01, 2018 at 07:30:30AM -0400, Haines Brown wrote:
Stefan, sorry to be dense.
With the help of ThinkPenguin I finally resolved the problem and wlan0
is now my interface name, not wlx. In any case, simply
modifying /etc/networ
Hi Steve,
El 01/07/18 a las 00:50, Steve Litt escribió:
On Sat, 30 Jun 2018 17:06:09 -0400
Haines Brown wrote:
I've long struggled with a problem with a new installation of ascii. I
can get an ethernet connection, but with a usb WiFi dongle using an
Atheros chip, my wlan0 interface gets autom
On Sun, 1 Jul 2018 10:20:10 -0400, Haines wrote in message
<20180701142010.gt1...@engels.historicalmaterialism.info>:
> On Sun, Jul 01, 2018 at 07:30:30AM -0400, Haines Brown wrote:
> > Stefan, sorry to be dense.
>
> With the help of ThinkPenguin I finally resolved the problem and wlan0
> is n
On Sun, Jul 01, 2018 at 07:30:30AM -0400, Haines Brown wrote:
> Stefan, sorry to be dense.
With the help of ThinkPenguin I finally resolved the problem and wlan0
is now my interface name, not wlx. In any case, simply
modifying /etc/network/interfaces to use that address didn't work (I
replaced all
On Sun, 1 Jul 2018 15:59:18 +0200, Stefan wrote in message
<201807011559.18028.li...@stefan-krusche.de>:
> I think, you are on the right track here. Check how your interfaces
> are named with
>
> ip addr
>
> or
>
> sudo ifconfig
..if that fails, append " -a " to see "the other interfaces.
El 01/07/18 a las 13:30, Haines Brown escribió:
If on the other hand I change the interface file on the ascii machine to
use the wireless dongle's mac address, such as wlx2123ff1a1794, by making
the first two lines of the interface read:
auto wlx2123ff1a1794
iface wlx2123ff1a1794 inet d
Am Sonntag 01 Juli 2018 schrieb Stefan Krusche:
> Hello Haines,
>
> I certainly am no expert on this, but I'll try to help.
>
> Am Sonntag 01 Juli 2018 schrieb Haines Brown:
> > Does not a /etc/udev/rules.d/70-persistent-net-rules file with the
> > following content not force udev to assign wlan0 t
Hello Haines,
I certainly am no expert on this, but I'll try to help.
Am Sonntag 01 Juli 2018 schrieb Haines Brown:
> Does not a /etc/udev/rules.d/70-persistent-net-rules file with the
> following content not force udev to assign wlan0 to the interface rather
> than use wlx?
>
> # PCI device 0x1
On Sun, Jul 01, 2018 at 11:30:46AM +0200, Stefan Krusche wrote:
> Am Samstag 30 Juni 2018 schrieb Haines Brown:
> > c) alter the default policy for picking a different naming
> > scheme by copying /lib/udev/rules.d/80-net-link-setup.rules to
> > /etc/udev/rules.d/ and then edit it appropriately.
>
Am Samstag 30 Juni 2018 schrieb Haines Brown:
> c) alter the default policy for picking a different naming
> scheme by copying /lib/udev/rules.d/80-net-link-setup.rules to
> /etc/udev/rules.d/ and then edit it appropriately.
>
> In my devuan jessie machine, there is such a file and it has
> two lin
On 06/30/2018 03:50 PM, Steve Litt wrote:
On Sat, 30 Jun 2018 17:06:09 -0400
Haines Brown wrote:
I've long struggled with a problem with a new installation of ascii. I
can get an ethernet connection, but with a usb WiFi dongle using an
Atheros chip, my wlan0 interface gets automatically change
On Sat, 30 Jun 2018 17:06:09 -0400
Haines Brown wrote:
> I've long struggled with a problem with a new installation of ascii. I
> can get an ethernet connection, but with a usb WiFi dongle using an
> Atheros chip, my wlan0 interface gets automatically changed to wl address>, and so cannot communi
I've long struggled with a problem with a new installation of ascii. I
can get an ethernet connection, but with a usb WiFi dongle using an
Atheros chip, my wlan0 interface gets automatically changed to wl, and so cannot communicate with DHCP.
This can tie into a bug in Network Manager, but I use w
35 matches
Mail list logo
