Killer Network Manager literally 'killing' my network

I've recently bought the Z97M Gaming motherboard and installed the network driver that came with it.
Unfortunately the Killer Network Manager's "Bandwidth Control" setting seems to 'kill' my whole network. With that feature enabled you are unable to access the internet via ethernet or wireless regardless of device. It seemingly also stops access to the router via the default gateway IP however I haven't tried that from a device that isn't this computer. The only way to regain access is to reboot the router.
After spending several hours trying to diagnose the issue I finally discovered that it was the "Bandwidth Control" setting that I mentioned above so I naturally just disabled that. Unfortunately I've now found out that, despite the fact I've applied the changes with the "Bandwidth Control" setting turned off, it seems to re-enable itself when I put my computer to sleep and then power it up again.
I can't really go forward with continually rebooting the router in order to resolve the issue, I need a fix that I can perform locally. Ideally I'd like to be able to just install the network driver without installing the Killer Network Manager but it doesn't seem like MSI offer that option. The only other option that I can think of is to change something on my computer or on the router. The router is the Super Hub 2 / 2ac from Virgin Media.
Thanks in advance and please let me know if you require any further information.

Quote from: Svet on 14-January-15, 11:59:51
do you use latest killer suite drivers 1.1.49.1068 ?
Sorry probably should've included that in my original post.
Yes I'm on 1.1.49.1068 on Windows 7 64bit.
Quote from: TZBC on 14-January-15, 13:19:38
MSI website provide the Killer Network Driver without KNM
check this out
removed because I can't post links...
I did look on MSI's site and, for some reason, that driver isn't listed on the UK site (can't post links but just append uk. before msi.com).
I assume there's not going to be any locality issues with installing that driver and it's just an oversight that it isn't on the UK site?

Similar Messages

Network Management: Question about calculating network,host and broadcast a

I would like to say i am new to this forum and I do not know if this is the right place to post this but i am currently in a cisco academy for CCNA and if anyone else is in this class i am stuck @ 6.2.2 in the online cisco material.....
given the following address/prefix of 141.124.88.174/30
enter the last octet in binary of the network,
I am totally lost @ how to find the network octet i know /30 means the first 30bits are network and the last 2 are host i also know the last octet is 10101100 or 172
my question how do you get .174 to .172??? if you are wondering how i know the answer --it is in the book i just dont know how to do it on my own :)
thanks much

Eric
My sense is that you may have skipped a step (or maybe I skipped in understanding your post). The best way to explain this is to refer to binary - which you have started to do.
For address ...174 the last octet is 101011 10 (in which 101011 represent the network bits and 10 represent the host bits). To find the network bits make the host bits all binary 0 - which means that the subnet address is 101011 00 or 172.
So the answer to your question is that you get from 174 (host address ) to 172 (network address) by changing all host bits to binary zero.
HTH
Rick

Network Manager and Wireless

I have a Broadcom 1390 mini wireless on a Compaq v3000 series laptop with AMD Turion64 processor.
I have been trying to activate it for some time now. bcm43xx did not work. i compiled ndiswrapper, blacklisted bcm43xx and managed to get wireless detected. I used wifi-radar to connect, but strangely the gnome network applet and wireless network manager showed as no network though wireless was connected and working. I had enabled wlan0 in rc.conf and all details entered as per the wiki.
I removed networkmanager from rc.conf daemons and added network. Now wireless connects at boot without a hitch. No need for wifi-radar. This is after so many reboots that this occurred to me, so I thought i should share this and perhaps find out if there is something wrong in my approach. I am new to Arch (about a few months) though I have been with Ubuntu, CentOS etc for a few years now

Coinago:
Your enc idea did not work...
How does one enter WEP key 10 digit hexadecimal in rc.conf etc. I tried it straight, then XXXX-XXXX-XX both as key and as enc. It did not work. Do I have to insert an "=" somewhere. I am a bit at sea. I got the wireless going thru wifi-radar. I use gnome, no KDE for me.
I would like to crack this so i have wireless at boot in my office. It was working fine with entries in rc.conf when there was no key. So it is obviously about entering the WEP key in the right format and place..

Network manager issues on Laptop

I'm using gnome shell from the testing and gnome-unstable repositories (the Arch way).
I'm having a lot of issues (wireless) with network manager:
1/ Shows home networks at work and work networks at home
2/ Keeps asking for key even though I'm entering the correct one while the same connection through 'nmcli' works just fine
3/ Doesn't show my saved networks and doesn't connect to them automatically. Again, I have to use 'nmcli'
I don't know if these are bugs with network manager or whether I did something wrong in the configuration files. In any case, I've decided to switch to 'wicd'.
However, I used to use 'wicd' on Ubuntu a few years ago and a problem was that I couldn't connect to VPN (which I need at work). This was the only reason I was hanging on to Network Manager. I looked online and this doesn't seem to have changed.
Are there solutions to connect to VPN (PPTP) without network manager. I remember trying the pptpd and kvpnc without much success. There was a plan on the wicd project page to implement PPTP VPN in 2008..does anyone know if this has been done already?

Well you could use wicd to connect to the access points then use vpnc for vpn. You just need to create a config file for vpnc or from the command line. I just did a quick search looks like the gentoo wiki page has a pretty good explanation for vpnc.
http://www.gentoo.org/doc/en/vpnc-howto.xml

How do I install individual driver of Killer LAN without its Network Management application?

I found sometimes the Network Management application would conflict with other online application, and in other forum an user provided a pure driver package that can solve the problem.
Here is the steps:
First you can download MSI pure Killer LAN driver from this link:
http://pan.baidu.com/s/1mgwZs96
Please uninstall old Killer LAN driver package from control panel if you already have the driver in OS.
Download and extract the RAR file to windows desktop. Double click “dpinst.exe” to install the killer driver.
It is normal if you see the message of “No device for update present” in the last step, that’ s because the driver package includes all kinds of killer LAN chip drivers, some don’t exist in your system.
Just click “Finish” to complete the driver installation. Restart system and you can start to enjoy the web surfing.
And if you encounter problem when you uninstall Killer LAN driver, you can use Killer official uninstall utility to completely remove the driver.
32 bit:
https://www.qca.qualcomm.com/drivers/KillerCleaner_32bit.exe
64 bit:
https://www.qca.qualcomm.com/drivers/KillerCleaner_64bit.exe

Just install the Killer LAN driver from MSI website, the manager is always installed with the driver.

Killer network manager cant enter accurate number

killer network manager on network tab asks to enter values for, in my case, dsl connection speed.
my speed is 10mbits down and 0,5 up
if i enter 0,5 for up and press apply then it rounds on 5 mbit
i can also use arrow keys, to adjust to 0.5 but same thing happens. i can manually enter 1 mbit for upload but thats 2x my speed.
killer network manager asks to enter accurate numbers for best result
mb is gaming 3 h97
my numbers are now 10,00 and 1,00
if i enter 0.50 then it rounds it on 5,00

Hi
i have antivirus but its disabled when installing, as sugested by installer.
i just uninstalled, so i dont have screenshots, but can attach them later.
when entering numbers for upload and download speed in network manager, it is in format 10,00 for 10 mbits, 100,00 for 100mbits etc.
i upgraded killer network software and now i have much bigger problem. if bandwith control is enabled, i cant connect to internet. i saw similar topics on msi forum allready.
i downgraded killer software to 1.1.39.1040 and bandwith control is working normally.
new 1.1.50 and 51 are not working.
right now i have just drivers, with no software.
so, there are two problems.
1) 1.1.50 and later not working at all with bandwith control enabled
2) cant enter 0.50 mbits in upload speed -- looks like software is accepting only 1, 2, 3 mbits values, and not 0.50, 1.50 -- which is weird because software is obviusly designed for that because you dont enter 10 mbits as 10, but as 10,00, so its logically to assume that 0.50 should work
please tell me do you still need those screenshots, i will upload them later today...
please, prepare drivers only (without killer software) for windows 10

How do I get rid ofl the "Killer Network Manager"?

I'm never on a wired LAN, always on WiFI, so I don't need this useless "network manager" starting whenever I start Windows. How can I get it to stop starting itself?
My laptop is a GE70 2PE 010US Apache Pro.

Uninstall the Killer LAN driver, then follow runningman's post to install only Killer driver.
http://dragonarmy.msi.com/forum/showthread.php?t=64228#.U3HJz4GSwuw

Killer Network Manager Keeps Saying To Install Flash.

I just put to together my rig and im slowly updating and running it through its paces, I have a MSI Z87-GD65 Gaming I have the latest drivers so far the only thing I haven't updated is the bios. Flash is installed but the MSI Killer Network Manager keeps saying that I need to install flash when I try to test the networks speed. Anyone else had this issue in the past?

Quote from: Maja199 on 11-April-14, 02:33:05
If you install the flash player through the internet explorer it should work.
That's right.
http://get.adobe.com/flashplayer/otherversions/
There are 2 Flash player installation packages:
1) for Internet Explorer (and Google Chrome)
2) for other browsers (Firefox, Opera, etc).
This amazing piece of software called "Killer Network Manager" needs the IE flash plugin.
Otherwise its outstanding interface does not work.

Ndiswrapper literally killed my laptop: story time

Just wanted to let everyone know what happened to my dell m1330 this week in case someone else notices the same behavior on their own system.
Despite the fact that I have an iwl4965, I've been using ndiswrapper for the better part of the year on this laptop just because I was so use to broadcom chipsets, I didn't care to try out the native driver ("if it's not broke" mentality). It's worked just fine for quite some time...until recently. For the last week or so, I've noticed that ntos_wq would, on occasion, start taking up a considerable amount of cpu time. But as long as I restarted my networking when it started acting up, it would fall back in line. But back on sunday, I left it running on the table while I was out to the rink for a few hours. When I returned, the fans were at full blast, and top was reporting a load of 4.7 something. Upon seeing this, I immediately turned it off.
A few hours later, I turned it back on to see if everything was alright. The random character corruptions made me believe otherwise. And as the final nail in the coffin, running glxgears hardlocked it. I would have liked to test this again to make sure it wasn't a fluke, but since then the only thing the laptop would do on boot-up was produce a white screen then slowly fade to randomly-colored vertical stripes.
Thankfully, I still had a couple months left on my warranty, and Dell didn't ask how I managed to give this thing a load so heavy the fans couldn't save it. They just sent a guy over and put a new motherboard in.
...also I'm now using the iwl4965 driver. Lesson learned.
Edit: And by literally killed, I mean it literally worked it to a fiery death, figuratively... wait wat?
Last edited by jb (2008-04-22 01:43:52)

Damn - also: Hooray for warranty!
But looking at it from a different angle, I cannot stop thinking it is Dell's fault. If you want to use your laptop to compile some large packages, then the laptop would be loaded 100% for several hours or days. The laptop should still be equipped with sufficient fans, no?
Or did Dell sell this laptop with a warning that you cannot use this laptop at full speed for several hours? I don't think so...
Zl.

[SOLVED]Network Manager dispatcher unexpected unmounting davfs folders

I have used Network Manager dispatcher to configure automatic mount of cloud storage using webdav. i have used davfs2 to perform mounting and wrote a script for NM dispatcher.
If i run /etc/NetworkManager/dispatcher.d/10-YandexDisk.sh manualy all works perfect.
If this script will be executed by NM-dispatcher all will fine(YandexDisk mounts successfully, sycronization - successfully), but after ~10 seconds mount.davfs gets signal 15.
sudo systemctl status NetworkManager-dispatcher
NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled)
Active: inactive (dead) since Wed 2013-07-31 23:12:55 EEST; 11s ago
Process: 12132 ExecStart=/usr/lib/networkmanager/nm-dispatcher.action (code=exited, status=0/SUCCESS)
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: --- yandex.ru ping statistics ---
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: rtt min/avg/max/mdev = 36.570/37.776/38.983/1.222 ms
Jul 31 23:12:44 DellLaptop mount.davfs[12138]: davfs2 1.4.7
Jul 31 23:12:44 DellLaptop mount.davfs[12138]: mount.davfs -o auto,nodev,dir_mode=755,exec,file_mode=755,gid=users,_netdev,rw,uid=lexa https://webdav.yandex.ru/ /home/lexa/.../YandexDisk
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: >mounted https://webdav.yandex.ru/ to /home/lexa/Data/YandexDisk
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: >exiting!!
Jul 31 23:12:55 DellLaptop mount.davfs[12140]: pid 12140, got signal 15
Jul 31 23:12:55 DellLaptop mount.davfs[12140]: unmounting /home/lexa/Data/YandexDisk
Jul 31 23:12:55 DellLaptop mount.davfs[12140]: unmounting failed
Why does this happen? Who send this signal ?
/etc/NetworkManager/dispatcher.d/10-YandexDisk.sh
#!/bin/bash
#this script will mount WebDav folder
# by pirat9600q
#given arguments are
#$1 is interface name
#$2 is state "up" or "down"
eth="enp7s0" #ethernet interface
wlan="wlp8s0" #wireless interface
ignore_connections="Pirat9600q" #WiFi SSIDs that must be ignored
mount_dir="/home/lexa/Data/YandexDisk" #mount point directory
remote_server="https://webdav.yandex.ru/" #server address
#local acces options
local_user="lexa" #files owner user
local_group="users" #files owner group
echo "<<<started with '$1' and '$2' arguments>>>"
echo "> our mount dir is '$mount_dir'"
echo "> and remote server is '$remote_server'"
case "$2" in
up)
#first of all we need to check internet connection
if (ping -c 2 -q yandex.ru); then
#we are online
if [ "$1" = "$wlan" ]; then
#Does this network is ignored ?
SSID=$(iwgetid -r)
for x in $ignore_connections; do
if [ "$x" = "$SSID" ]; then
echo "> WiFi SSID '$SSID' is in ignore list, exiting"
exit
fi
done
fi
if [ ! -d "$mount_dir" ]; then
fusermount -u "$mount_dir"
fi
if(mount.davfs -o auto,nodev,dir_mode=755,exec,file_mode=755,gid=$local_group,_netdev,rw,uid=$local_user "$remote_server" "$mount_dir"); then
echo ">mounted $remote_server to $mount_dir"
echo ">invoking syncronization script"
/home/lexa/.scripts/SyncYandexDisk.sh
else
echo ">error mounting $remote_server to $mount_dir !!!"
fi
else
echo ">network down";
exit
fi;;
down)
echo ">unmounting '$mount_dir'"
fusermount -u "$mount_dir"
echo ">removing $mount_dir"
rmdir $mount_dir
echo ">finished";;
esac
echo ">exiting!!"
exit
/home/lexa/.scripts/SyncYandexDisk.sh
#!/bin/bash
#this script will synchronize local storage
#with mounted Yandex Disk folder
# by pirat9600q
source_dir="/home/lexa/Data/YandexDisk/" #mount point directory
dest_dir="/home/lexa/Data/ARC/CloudSync/" #local storage location
echo "<<<started with:"
echo " source folder '$source_dir'"
echo " and destination folder '$dest_dir'"
if [ ! -L ${source_dir}Foto ]; then #if not link
echo ">invoking syncronization from '$source_dir' to '$dest_dir'"
echo ">syncronizing 'Foto' folder"
if !(rsync --quiet --recursive --update --executability --owner --group --delete-before ${source_dir}Foto/ ${dest_dir}Foto/); then
echo ">>error"
else
echo ">>success"
fi
echo ">syncronizing 'Documents' folder"
if !(rsync --quiet --recursive --update --executability --owner --group --delete-before ${source_dir}Documents/ ${dest_dir}Documents/); then
echo ">>error"
else
echo ">>success"
fi
else
echo ">syncronization will not be made, because source is fake"
fi
echo ">exiting"
exit 0
P.S. sorry for my English
Last edited by pirat9600q (2013-08-02 08:14:44)

I solved the problem. Here is a little explanation.
After NetworkManager establishes network connection, NetworkManager-dispatcher service is started( for ~10 seconds). This service execute /usr/lib/networkmanager/nm-dispatcher.action, which execute scripts in /etc/NetworkManager/dispatcher.d. After exiting nm-dispatcher.action mount.davfs process appears in NetworkManager-dispatcher`s CGroup. By default all processes in CGroup must be killed when service stops. To change this behavior I have added KillMode=process to [Service] section of NetworkManager-dispatcher.service file.
sudo nano /usr/lib/systemd/system/NetworkManager-dispatcher.service
Here is it`s code now.
[Unit]
Description=Network Manager Script Dispatcher Service
[Service]
Type=dbus
BusName=org.freedesktop.nm_dispatcher
ExecStart=/usr/lib/networkmanager/nm-dispatcher.action
KillMode=process
[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.nm-dispatcher.service

How to create a persistent network manager profile with openvpn?

After installing networkmanager and openvpn everything works fine except that the networkmanager profile is not persistent and nm creates and selects a new profile with every boot. I followed Persistent configuration on boot using systemd which creates a persistent profile and cuts out the creation of a new profile, but when I build a openvpn connection it won't change the i.p. any longer. I've been searching for a week, read and learned a lot, but without a solution.
My main question is what's creating and selecting a new network profile after booting? I've 2 fresh installations of Arch and Archbang on 2 pc's and with both the same issue/problem.
systemctl --type=service
UNIT LOAD ACTIVE SUB DESCRIPTION
avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack
clamd.service loaded active running clamav daemon
colord.service loaded active running Manage, Install and Generate
cups-browsed.service loaded active running Make remote CUPS printers av
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running Getty on tty1
kmod-static-nodes.service loaded active exited Create list of required stat
lvm2-lvmetad.service loaded active running LVM2 metadata daemon
lvm2-pvscan@254:0.service loaded active exited LVM2 PV scan on device 254:0
NetworkManager.service loaded active running Network Manager
nmbd.service loaded active running Samba NetBIOS name server
org.cups.cupsd.service loaded active running CUPS Scheduler
polkit.service loaded active running Authorization Manager
privoxy.service loaded active running Privoxy Web Proxy With Advan
rpcbind.service loaded active running RPC bind service
rtkit-daemon.service loaded active running RealtimeKit Scheduling Polic
smbd.service loaded active running Samba SMB/CIFS server
systemd-fsck-root.service loaded active exited File System Check on Root De
systemd-fsck@dev-disk-by\x2duuid-0e5d72a0\x2de09b\x2d4d0b\x2dba6f\x2d29a25ce04
systemd-fsck@dev-disk-by\x2duuid-567d8960\x2d0ab5\x2d4e3a\x2d8565\x2d32d725fee
systemd-journal-flush.service loaded active exited Trigger Flushing of Journa
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File
[email protected] loaded active exited Load/Save RF Kill Switch
[email protected] loaded active exited Load/Save RF Kill Switch
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-update-utmp.service loaded active exited Update UTMP about System Boo
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
tor.service loaded active running Anonymizing Overlay Network
udisks2.service loaded active running Disk Manager
[email protected] loaded active running User Manager for UID 1000
systemctl list-unit-files | grep -i network
dbus-org.freedesktop.NetworkManager.service enabled
[email protected] disabled
NetworkManager-dispatcher.service disabled
NetworkManager-wait-online.service disabled
NetworkManager.service enabled
systemd-networkd-wait-online.service disabled
systemd-networkd.service disabled
network-online.target static
network-pre.target static
network.target static
Last edited by 2arch (2014-12-10 22:54:18)

Open the Sharing pane of System Preferences and enable Internet Sharing over AirPort.
(59391)

Network manager in xfce doesn't connect but wifi-menu does?

I may be misunderstanding how to use this since I've never done wireless from the command line before, but here is my situation:
I just installed arch on my Acer Aspire One and used both the wired and wireless from the command line. I had never done wireless from the command line before and just followed the Beginners Guide and used wifi-menu to select the network to connect to. It was very very smooth and connected me in seconds. After installing xfce I decided I wanted a tray icon for selecting wireless stuff and so I installed networkmanager and network-manager-applet. After starting nm-applet it reported my wireless as disconnected (even though it was connected) and when I asked it to connect to my network it was unable to connect. I restarted the computer and still no success. While I can get by with wifi-menu, it would be awfully nice if I could get network manager to work with xfce. Does anyone have any thoughts on this?
Thanks in advance.

I switched to using wicd and after a little while of using it it seems to work pretty well. It works significantly better than NetworkManager and doesn't drop connections very often so long as the signal is good.
My one complaint is that every so often a process called wicd-monitor likes to start using 100% cpu on one of my cores. Since this is a netbook and power is critical, I usually end up killing the process or restarting wicd so that it stops draining my battery.

Network Manager driving me crazy (3 issues)

Hey guys I'm new here, hope you can help me
nm-applet is driving me crazy!
First issue: when I boot nm-applet doesn't appear in my tint2 eventhough I'm connected. This don't appear all the time, it's random. I have to kill it and restart it to be able to see it.
I use openbox and I have this in .config/openbox/autostart
(sleep 3 && /usr/bin/nm-applet --sm-disable) &
Second issue:
I selected the save option for the password of my vpn but it won't save it... Or wait, yes it will.. But not all the time. It asks me for the pass sometimes, and sometimes not
Third issue:
I thicked the "automatically connect to vpn for this connection" but guess what... It won't
Any idea about how to troubleshot this. I'm seriously considering pacman -R network-manager and pacman -S something else
Thank you
Last edited by Truc (2014-03-06 21:17:51)

1st issue: run nm-applet from the command line (take it out of openbox's start file wherever that is) after you log in to see what's going on.
2nd issue: do you have gnome-keyring installed? I believe it should be started with by networkmanager when it's needed, but you may need to figure out how to start it on your own. I don't know how.
3rd issue: I believe the automatic connection to vpn on a specific network is triggered by networkmanager-dispatcher which is just part of the networkmanager package, but is its own separate service. When you enable/start NetworkManager via systemctl, it should enable/start 3 services - the dispatcher is one of them. Do you have that running?
I may be wrong about some of this; it's been a while since i've used NetworkManager.

[SOLVED]Network Manager Applet and nmcli failing after GCC upgrade

Hi All,
So I went to update my system today and there were only like 8 or 9 updates. Like many other people I had an issue with gcc and pacman. To fix this I ran
pacman -S gcc
Then I ran:
pacman -Su
which updated pacman itself. On reboot though I noticed network manager applet was unable to find any of my network devices despite the fact that network manager was running and I had an IP address. I killed nm-applet and re-ran it and it spewed errors about not being able to connect to network manager. I tried running nmcli and it did the same thing. However, when I run nmcli as root it works. Looking at the arch wiki they suggest you be a part of the wheel and network group which I made sure I was. Everything was working up until I ran those two updates though. Anyone else have this happen or have any idea what is wrong?
Thanks,
Hemmar
EDIT: Never mind - a patch was released for consolekit which fixes the problem.
Last edited by hemmar (2012-04-13 00:36:49)

Hi guz46
I have already tried removing the ! and the same thing happened ... but I realised today that I was being automatically connected to "Auto eth0" despite there being no cable present. When automatic connection was disabled on "Auto eth0" my 3G connection (ppp0) connected fine.
Could you clarify that the preferred set-up in the /etc/rc.conf for the interfaces is without the !. The Wiki for networkmanager says to disable them, but then states that some may need to be reenabled with no explanation. The purpose of this confuses me!
Thanks for you help anyways,
Scott
EDIT:
I appear to have fixed my problem with the auto connection on the various interfaces by updating my /etc/rc.conf file to:
#Static IP example
#eth0="dhcp"
ppp0="dhcp"
wlan0="dhcp"
eth0="dhcp"
INTERFACES=(ppp0 wlan0 eth0)
Thus ensuring that I can connect in order of preference.
Last edited by ScottArch (2009-11-03 18:48:47)

Network Manager Dispatcher with NFS/Autofs

I'm looking to see what is the most recommended method of starting automounted nfs shares after network manager has brought up a wireless connection.
Currently, I'm using the network manager dispatcher and I have dispatch files for:
netfs
autofs
In rc.conf DAEMONS I still have
rpcbind
nfs-common
Should I make dispatcher files for rpcbind and nfs-common as well? What do people around here consider the proper way to do this?

Thanks for tip about journalctl!! Made a big difference.
Here is what the script is telling me:
Apr 03 11:45:08 orphan nm-dispatcher.action[553]: Script '/etc/NetworkManager/dispatcher.d/50-mount_sshfs_share_gohilton_2223.sh' took too long; killing it.
I'm guessing the ssh part where it attempts to connect to the remote server and mount the remote ssh is taking to long however even using journalctl in verbose mode really doesn't confirm this assumption.
I'm wondering if this would best be done with systemd unit files?

Killer Network Manager literally 'killing' my network

Similar Messages

Maybe you are looking for