LinuxQuestions.org
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   How do I get NetworkManager to coexist with rc.inet1 (https://www.linuxquestions.org/questions/slackware-14/how-do-i-get-networkmanager-to-coexist-with-rc-inet1-4175553928/)

tux_dude 09-19-2015 02:07 AM
How do I get NetworkManager to coexist with rc.inet1
 
Just switch to NM because of this wicd issue, but can't get NM to connect if rc.inet1.conf is enabled. With rc.inet1.conf enabled, NM will not connect to the wifi network and keep asking for the wifi password. With rc.inet1.conf disabled, I can connect with NM. Is is possible to get NM working with rc.inet1.conf? If not, how can I get NM to connect and stay connected without logging into the desktop?

Drakeo 09-19-2015 02:57 AM
scroll down to networkmanager http://docs.slackware.com/slackware:beginners_guide.
assume root and run this in a terminal chmod +x /etc/rc.d/rc.networkmanager then reboot. uninstall wicd first.
if your wifi router has a encrypted wifi like all I know. then you need that password and select auto dhcp.
you may have to create a new profile. and make sure that user has netdevice in their groups selected.
if you want to configure your inet1.conf to use the wifi device read the link.

kikinovak 09-19-2015 04:03 AM
Quote:
Originally Posted by tux_dude (Post 5422613)
Just switch to NM because of this wicd issue, but can't get NM to connect if rc.inet1.conf is enabled. With rc.inet1.conf enabled, NM will not connect to the wifi network and keep asking for the wifi password. With rc.inet1.conf disabled, I can connect with NM. Is is possible to get NM working with rc.inet1.conf? If not, how can I get NM to connect and stay connected without logging into the desktop?
All fields in rc.inet1.conf must be empty if you activate NetworkManager. As simple as that.

tux_dude 09-19-2015 08:31 AM
Quote:
Originally Posted by Drakeo (Post 5422636)
scroll down to networkmanager http://docs.slackware.com/slackware:beginners_guide.
assume root and run this in a terminal chmod +x /etc/rc.d/rc.networkmanager then reboot. uninstall wicd first.
if your wifi router has a encrypted wifi like all I know. then you need that password and select auto dhcp.
you may have to create a new profile. and make sure that user has netdevice in their groups selected.
if you want to configure your inet1.conf to use the wifi device read the link.
All these setting are already done. It is not an issue of getting NM to start on boot. It simply will not setup the wireless interface without logging into the desktop. I even have "All users may connect to this network" option checked.

tux_dude 09-19-2015 08:32 AM
Quote:
Originally Posted by kikinovak (Post 5422650)
All fields in rc.inet1.conf must be empty if you activate NetworkManager. As simple as that.
Well, that is a problem because I can only getting the wireless interface configured at boot through rc.inet1.conf. Is there an option to have NM bring up the wireless interface without logging into the DE?

kikinovak 09-19-2015 09:00 AM
Quote:
Originally Posted by tux_dude (Post 5422705)
Well, that is a problem because I can only getting the wireless interface configured at boot through rc.inet1.conf. Is there an option to have NM bring up the wireless interface without logging into the DE?
You connect either using NetworkManager or rc.inet1.conf. The two methods are mutually exclusive. If you have to connect your wireless card on boot time, just don't use NM (chmod -x /etc/rc.d/rc.networkmanager) and edit rc.inet1.conf. Scroll down a bit and check out the various wireless stuff examples.

atelszewski 09-19-2015 09:05 AM
Hi,

Quote:
Is there an option to have NM bring up the wireless interface without logging into the DE?
Yes, actually it's harder not to make NM bring up the wireless at boot time;)

NM is a system daemon + different frontends. When started from /etc/rc.d/rc.networkmanager it works in background and manages your connection and it doesn't matter if you're logged in or not. Just configure your connections the way they should be and then let the daemon manage them.

--
Best regards,
Andrzej Telszewski

tux_dude 09-19-2015 09:17 AM
Quote:
Originally Posted by kikinovak (Post 5422712)
You connect either using NetworkManager or rc.inet1.conf. The two methods are mutually exclusive. If you have to connect your wireless card on boot time, just don't use NM (chmod -x /etc/rc.d/rc.networkmanager) and edit rc.inet1.conf. Scroll down a bit and check out the various wireless stuff examples.
Well, I need to have my wireless card connect on boot and also have the ability to manage the wireless connection when on my desktop. This works in wicd. Looks like I will have to switch back to wicd and figure out the wireless scanning issue when on the road.


With this info, I will focus on getting the wicd fix. Leaving the post open for now for any other input if available.

tux_dude 09-19-2015 09:30 AM
Quote:
Originally Posted by atelszewski (Post 5422714)
Hi,


Yes, indeed it's harder not to make NM bring up the wireless at boot time;)
Base on kikinovak comment and my testing, this doesn't just seem harder, but practically impossible.

Quote:
Originally Posted by atelszewski (Post 5422714)
NM is a system daemon + different frontends. When started from /etc/rc.d/rc.networkmanager it works in background and manages your connection and it doesn't matter if you're logged in or not. Just configure your connections the way they should be and then let the daemon manage them.
I do not get that expected result. When boot, NM daemon is running in the background, by my wireless interface is not configured. I have to log into the desktop for the wireless interface to become available. This is a major step backwards for me as I would also remote connect after booting. Also, with this limitation, I will have to do so sort of a hack to manage my box remotely after a scheduled boot.

atelszewski 09-19-2015 09:33 AM
Hi,

I don't exactly understand what is the problem here.
Providing that your wifi is supported you can do with NM all the things you want.
You leave rc.inet1.conf empty and you configure everything in NM.
When the system boots, NM daemon will start managing your network, if so configured, it'll connect to the wireless network.

It doesn't matter if you're logged in or not.

--
Best regards,
Andrzej Telszewski

atelszewski 09-19-2015 09:38 AM
Hi,

Quote:
I do not get that expected result. When boot, NM daemon is running in the background, by my wireless interface is not configured. I have to log into the desktop for the wireless interface to become available. This is a major step backwards for me as I would also remote connect after booting. Also, with this limitation, I will have to do so sort of a hack to manage my box remotely after a scheduled boot.
Then either you have flaky hardware or misconfiguration somewhere.
Make sure "Automatically connect to this network when it is available" is ticked on.

--
Best regards,
Andrzej Telszewski

tty13 09-19-2015 09:44 AM
you can run:
Quote:
netconfig
and choose NetworkManager, it should set everything up for you as it should be.

tux_dude 09-19-2015 09:46 AM
Can you give me some pointers on what I'm doing wrong. Here are my configs:

NetworkManager.conf
Code:
# /etc/NetworkManager/NetworkManager.conf
#
# See NetworkManager.conf(5) for more information on this file

[main]
plugins=keyfile
# Choose a DHCP client below.  Upstream recommends dhclient, but results may vary.
# dhcpcd is the DHCP client usually used by Slackware:
dhcp=dhcpcd
# dhclient is the ISC reference DHCP client, part of the dhcp package:
#dhcp=dhclient
# This is a simple DHCP client that is built into NetworkManager:
#dhcp=internal

[keyfile]
hostname=laptop
keyfile info
Code:
[connection]
id=<redacted>
uuid=<redacted>
type=wifi
permissions=
secondaries=

[wifi]
mac-address=<redacted>
mac-address-blacklist=
mode=infrastructure
seen-bssids=
ssid=<redacted>

[wifi-security]
group=
key-mgmt=wpa-psk
pairwise=
proto=
psk=<redacted>

[ipv4]
dns-search=
method=auto

[ipv6]
dns-search=
ip6-privacy=1
method=auto
After booting, and switching tty to console and run ifconfig I get:
Code:
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether <redacted>  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
As you can see, I am not getting the expected result.

atelszewski 09-19-2015 09:48 AM
Hi,

Another option might be that you have some problem with software stack.
I'm running Slackware 14.1 and I have no problems with WiFi going up on boot without DE.

So either you have problem with software stack or hardware or NM configuration.

--
Best regards,
Andrzej Telszewski

atelszewski 09-19-2015 09:50 AM
Hi,

Which Slackware are you running?

--
Best regards,
Andrzej Telszewski


All times are GMT -5. The time now is 10:28 PM.
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page