:: Re: [DNG] netman: support for wlan1…
Pàgina inicial
Delete this message
Reply to this message
Autor: Edward Bartolo
Data:  
A: fsmithred
CC: dng
Assumpte: Re: [DNG] netman: support for wlan1, wlan2, ... and eth1, eth2, .... and new systemd's naming scheme
Hi,

I removed the icon and used text instead.

It is important to note that normal users who have only one wifi card
and one ethernet connector do not absolutely need to use that option,
as it doesn't make sense to talk about default devices where there is
no choice other than the one device provided. Such an option will
certainly be only used by users having uncommon systems, implying they
should be able to handle the situation. Providing automatic filling of
device names complicates the GUI unnecessarily. Please keep in mind,
the more automation we include, the heavier the processing burden,
which is something we want to avoid. In fact, I removed some code
which updated the active device name every five seconds. If a user
wants to know which network device is UP, he/she can always click the
Connected/Disconnected button.

In case where there are multiple devices of the same kind, users can
also opt to manually edit a text file under
~/.config/netman/netman.default.devices. The syntax is:
wlanX=wldevice
ethX=ethdevice

Edward

On 05/10/2015, fsmithred <fsmithred@???> wrote:
> I can't tell from the pictures exactly what the flow is from one window to
> another, but if it works out such that you can select the interface from a
> list and have it auto-fill the interface name in the window that asks for
> it, then you'll have one-up on wicd, which makes you type the interface
> name.
>
> It would be bad if the user has to remember something like wlx78e7d1ea46da
> and type it into the next window. (Or even have to remember to
> copy/paste). If the auto-fill isn't possible, then I'd suggest having both
> windows open so the user can look at it while they're typing.
>
> For reference, in wicd, you can manually enter the default interface in
> the gui or in a config file. Putting it into either one will automatically
> add it to the other.
>
> RE: "gnome foot' icon:
> I thought the same thing, until I saw it enlarged. I think it's really a
> wolverine or maybe a wolf.
>
> -fsr
>
>
> On 10/04/2015 10:41 AM, Edward Bartolo wrote:
>> Hi All,
>>
>> These are more screenshots of the evolution of the frontend.
>>
>> http://postimg.org/image/enimq62sh
>> http://postimg.org/image/y6n7zj1k1
>> http://postimg.org/image/4g03drgkh
>>
>> Edward
>>
>> On 04/10/2015, Edward Bartolo <edbarx@???> wrote:
>>> Hi David,
>>>
>>> The new device naming scheme will be supported. Regarding listing
>>> 'lo', I was told to filter it off the list of devices. At the moment I
>>> am concentrating on the frontend before I start to code support for
>>> enp**** and wl****. The reason is to have a clear view of what I
>>> should code in the backend.
>>>
>>> Edward
>>>
>>>
>>>
>>> On 04/10/2015, David Hare <davidahare@???> wrote:
>>>> Some observations, testing netman.
>>>>
>>>> I have a (devuan-based) installation running eudev. The (usb) wireless
>>>> device shows as wlan0 and netman works fine. As this machine is a fixed
>>>> tower it doesn't normally need netman gui so my autostart calls this,
>>>> and it works:
>>>>
>>>> xterm -title "Connecting to network..." -e "/usr/lib/netman/bin/backend
>>>> 10"
>>>>
>>>> I would like to do similar before user login, maybe with an initscript.
>>>>
>>>> WICD and its ******* dbus reliance is now sacked for this machine.
>>>>
>>>> I have also live-images with eudev, unfortunately they can't use netman
>>>> so far because:
>>>>
>>>> root@exefce:/home/user# iwconfig
>>>> lo        no wireless extensions.

>>>>
>>>> enp5s4    no wireless extensions.

>>>>
>>>> enp2s0    no wireless extensions.

>>>>
>>>> wlp0s29f7u3  IEEE 802.11bg  ESSID:off/any
>>>>            Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
>>>>            Retry short limit:7   RTS thr:off   Fragment thr:off
>>>>            Encryption key:off
>>>>            Power Management:on

>>>>
>>>> Those interfaces (except "lo") do show in netman's main window.
>>>> However:
>>>>
>>>> wlan0: ERROR while getting interface flags: No such device
>>>>
>>>> ERROR: power_scan(): "/sbin/ifconfig wlan0 up" did not exit
>>>> successfully
>>>> (status=255).
>>>>
>>>> I hope this can be fixed soon. I built from latest git with
>>>> dpkg-buildpackage, using the debian.tar.xz available with the netman
>>>> deb
>>>> package. BTW the build-deps list don't include build-essential, which
>>>> was necessary although everything else was straightforward. I was a bit
>>>> disturbed that they were around 900MB to install.
>>>>
>>>> (minor irritation) the "gnome foot" icon!
>>>>
>>>> David
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Dng mailing list
>>>> Dng@???
>>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>>>>
>>>
>
>