wicd does not allow eth and wlan being up

igadoter · 04-20-2017, 11:46 AM

It is true. When I rising up wired interface wicd is putting down wifi interface. And vice versa. No idea what to do. I tried to manage with wicd client applet, but I can not figure out configuration for both eth and wlan being up.

Alien Bob · 04-20-2017, 01:41 PM

Works as designed...

Gerard Lally · 04-20-2017, 03:40 PM

Quote:

Originally Posted by igadoter

It is true. When I rising up wired interface wicd is putting down wifi interface. And vice versa. No idea what to do. I tried to manage with wicd client applet, but I can not figure out configuration for both eth and wlan being up.

I would disable wicd and configure the two interfaces in rc.inet1.conf instead.

See here to configure your wireless network in rc.inet1.conf. Don't use the old method - rc.wireless.conf.

I've been following a thread on the Scientific Linux forum about Network Manager, specifically its command-line interface nmcli. It seems to have been giving these enterprise Linux admins numerous headaches. (Not the fault of Scientific Linux, of course.)

I doubt that the wicd developer is as useless as the Red Hat developers who put NM together but sometimes it's much easier to do things the way they were intended to be done, without all the garbage on top. That's why Slackware lets you configure your system the hard way, which nearly always ends up the easy way.

igadoter · 04-21-2017, 07:41 AM

Quote:

Originally Posted by Alien Bob

Works as designed...

Had no idea. But Network Manager can keep both interfaces, does it?

igadoter · 04-21-2017, 08:22 AM

Quote:

Originally Posted by Gerard Lally

That's why Slackware lets you configure your system the hard way, which nearly always ends up the easy way.

Well said. Great motto for Slackware. Maybe we should ask Volkerdi to put in some visible place. Let good news spread all the world. I think so. I am as husband (or wife) which always come back.

Alien Bob · 04-21-2017, 05:06 PM

Quote:

Originally Posted by igadoter

Had no idea. But Network Manager can keep both interfaces, does it?

Yep.

igadoter · 04-22-2017, 07:10 AM

I configured network vi /etc/rc.d/rc.inet1.conf there is issue however. Computer always boots with hardware lock for wifi, I managed this by setting in rc.local

Code:

rfkill unblock all

but it does not work with script /etc/rc.d/rc.inet1 cause this script is executed earlier than rc.local, so during execution wifi is locked by hardware and cannot be raised by rc.inet1. What is elegant solution? I mean something different than hacking rc.inet1. What comes to my mind is to set in rc.local

Code:

rfkill unblock all
/etc/rc.d/rc.inet2 wlan2_restart

but is inot very elegant. I mean to start twice the same interface during boot. It should be enough only one attempt.
Wicd is also causing troubles. Even if I changed /etc/rc.d/rc.wicd to non-executable wicd anyway starts.

The last issue solved. It was due to desktop settings.

bassmadrigal · 04-22-2017, 09:57 AM

You could add the rfkill command before rc.inet1 is called in /etc/rc.d/rc.M

In 14.2, you'd want to add it before line 97. Or, actually, you could add it in the if/then statement for rc.inet1 so it is run only when rc.inet1 is run (not that it likely matters).

GazL · 04-26-2017, 12:17 PM

Although not ideal, sometimes replacing rc.inet1 with an implementation of your own is the cleanest approach.

I'm currently trying this out on a wifi only laptop:
/etc/rc.d/rc.inet1:

Code:

#!/bin/sh

case "${1:-start}" in
        start)  ip -batch - <<-EOF
                        address flush dev lo
                        address add 127.0.0.1 dev lo
                        link set lo up
                EOF

                if [ ! -e /var/run/wpa_supplicant/wlan0 ]; then
                        iw reg set GB
                        wpa_supplicant -B -c /etc/wpa_supplicant/wlan0.conf -i wlan0 >/dev/null
                fi
                dhcpcd -q -b -L -M wlan0
                ;;
        stop)   dhcpcd -q -k
                ip link set wlan0 down
                if [ -e /var/run/wpa_supplicant/wlan0 ]; then 
                        /usr/sbin/wpa_cli -i wlan0 terminate >/dev/null
                        # Note: PATH doesn't contain /usr/sbin/ when invoked from rc.6
                        # so we have to use the fullpath to wpa_cli here.
                fi
                ;;
esac

If you were to try something like this you could stick your rfkill command in where I've got the 'iw reg set'.

Before this, I was using a wpa_cli "action" script to run dhclient when supplicant connected, which also seemed to be working well, but I wanted to try out dhcpcd's 'master' mode to see if it worked any better this way.

I've never had need of a front end like wicd or network-mangler. The underlying components seem to work just fine without them once you learn to use them, but maybe that's because my needs are pretty simple.