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?

Similar Messages

  • [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

  • Network Manager Dispatcher returns error code 1 on tested scripts

    I'm trying to write a simple script to test the network manager dispatcher but while it's working when I manually launch the script, the nm dispatcher print "nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/start_dropbox.sh' exited with error status 1" into the logs.
    #!/bin/sh
    IF=$1
    STATUS=$2
    /bin/su USERNAME -c "/usr/bin/notify-send lol woot"
    exit $?
    I tried using absolute paths, just the commands, running with sudo(although the scripts should be run as root) and without su. I tested the script as root and as a simple user using a terminal and it works just fine every time.
    echo seems to work fine as I don't get any errors in the logs, but that way I can't see what's inside $1 and $2 when the dispatcher calls the script and I can't think of any way to debug the script which doesn't involve notify-send.
    I'm sure I'm missing something very simple here, but I can't see it myself and searching google and the arch forums hasn't helped me any.

    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 dispatcher.d

    I've created a script that I'd like Network Manager to run after the network is up.  I can run the script as root manually if I pass or set the $status variable and everything works, however I can't seem to get the script to run when I start NetworkManager service.  Where does NetworkManager log since there is no daemon.log file in /var/log?
    Following script is within /etc/NetworkManager/dispatcher.d/ with permissions of 711.
    Here is the script (very similar to what was posted in Arch Wiki):
    #!/bin/bash
    USER='xxxx'
    REMOTE='[email protected]:/home/xxxx'
    LOCAL='/home/xxxx/mnt_sshfs'
    OPTIONS="-o idmap=user -o follow_symlinks -C -p 22"
    interface=$1 status=$2
    case $status in
    up)
    sleep 5
    #expect fwknop daemon call (Which is run as 49_fwknopcall)
    su "$USER" -c "sshfs $OPTIONS $LOCAL $REMOTE"
    down)
    fusermount -u "$LOCAL"
    esac

    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?

  • Network Manager Dispatcher???

    Can someone point me to a document that explains just how the hell to set this up....the wiki is very vague and confusing.  I find some posts here saying to load networkmanager-dispatcher in the DAEMONS in rc.conf...but t.hat just causes an error message to the effect of "can't find this daemon" when I boot up...  Please help.  I'm trying to get my cifs mounts in fstab to mount up AFTER the network is connected.  Thanks

    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?

  • Oracle BPM for Network Management Projects

    Has anybody used Oracle BPM for network management projects with millions of events?
    Can Oracle BPM handle it?

    Please follow this step may this solve your problem.
    please modify any thing in process "ExpenseReporting" for example any transition or any activity to place some where else or any other modification and then save that process. Then clean the project and build and deploy it.
    if this also not solve the problem then export that project to and import it again in your workspace (Create new workspace or change the project name in same workspace ) and then again clean, build and deploy the application then test in work space.
    Thanks,
    Brijesh Kumar Singh

  • [SOLVED] network-manager-applet not found

    Hi, I'm quite noob here, and I'm trying to install network-manager-applet with no luck;
    So far I've done
    # pacman -S network-manager-applet
    and I got
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): network-manager-applet-0.8-1
    Total Download Size: 1.01 MB
    Total Installed Size: 4.35 MB
    Proceed with installation? [Y/n] y
    :: Retrieving packages from extra...
    error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from mi.mirror.garr.it : Not Found
    error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from ftp.nluug.nl : Not Found
    error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from ftp.hosteurope.de : Not Found
    error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from ftp-stud.hs-esslingen.de : Not Found
    error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from archlinux.puzzle.ch : Not Found
    error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from ftp.surfnet.nl : Not Found
    warning: failed to retrieve some files from extra
    error: failed to commit transaction (Not Found)
    Errors occurred, no packages were upgraded.
    so I tried to download the package itself and install it with
    pacman -U network-manager-applet-0.8-2-x86_64.pkg.tar.xz
    and the answer was
    loading package data...
    checking dependencies...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: network-manager-applet: requires mobile-broadband-provider-info
    what to do?
    i cannot find in the repos the package mobile-broadband-provider-info
    thank you in advance
    Last edited by lsk (2010-03-10 10:15:21)

    Update your system - "pacman -Syu".  The clue is that the file you manually downloaded is different to the one pacman is trying to get.

  • Help needed with using network disk with iMovie with NFS or AFP

    Hi,
    I have iMac with iMovie08 that talks to a remote disk hosted under Linux over a gigabit network using SMB (Samba). It all works ok and I have done a few movies.
    Now, I have done some tests with NFS and AFP (AppleTalk) and it seems that these are much faster than SMB.
    I then stopped the Samba server and proceeded to setup NFS and also AFP
    First NFS,
    So I then exported my directory using NFS and I can see everything from my Mac (correct permissions too since I made both user and group IDs the same...). The problem is that when I launch iMovie it shows me the Volume for my external networked disk but it shows it with a little triangle with yellow exclamation and it does not show any of the events (>500GB of events).
    If I stop NFS and then switch to AFP I get the same behavior. That is, everything from the Mac works on the AFS mounted disk (copying files back and forth, etc....) but I can't see the contents of the disk from within iMovie
    I changed permissions so that anybody can read/write/execute (although there are files that have an '@' sign at the end when I do ls -l on them and I can't remember what that means....)
    If I stop NFS and then go back to SMB (Samba) then I am back to a working configuration.
    Can I use NFS or AFP with iMovie? What exactly does the yellow triangle mean?
    Thanks
    Dazed and confused at 330am EST...

    More timings on smb vs nfs. Note that the big diffs is when sending single large files. The dd cmd was used to simulate 1 hour of DV video which is about 12GB
    1.27GB dvd project (twice each, note the variability... I guess because the project has multiple files?):
    MEiMac:Movies me$ time cp -r LS2000Berlin.dvdproj /Volumes/bigsmb/
    real 0m37.114s
    user 0m0.008s
    sys 0m4.164s
    MEiMac:Movies me$ time cp -r LS2000Berlin.dvdproj /Volumes/bignfs/
    real 0m59.351s
    user 0m0.009s
    sys 0m8.336s
    MEiMac:Movies me$ time cp -r LS2000Berlin.dvdproj /Volumes/bignfs/
    real 0m40.671s
    user 0m0.009s
    sys 0m8.205s
    MEiMac:Movies me$ time cp -r LS2000Berlin.dvdproj /Volumes/bigsmb/
    real 0m41.680s
    user 0m0.008s
    sys 0m4.094s
    Simulated 1 hour video single file:
    MEiMac:Movies me$ time dd if=/dev/zero of=/Volumes/bigsmb/1hour bs=16k count=786432
    786432+0 records in
    786432+0 records out
    12884901888 bytes transferred in 443.960166 secs (29022653 bytes/sec)
    real 7m23.994s
    user 0m3.434s
    sys 1m18.900s
    MEiMac:Movies me$ time dd if=/dev/zero of=/Volumes/bignfs/1hournfs bs=16k count=786432
    786432+0 records in
    786432+0 records out
    12884901888 bytes transferred in 235.887283 secs (54623131 bytes/sec)
    real 3m56.271s
    user 0m1.666s
    sys 1m56.995s

  • Problem with NFS file adapter using a network share as source of files

    Hello,
    I have set up a sender cc with NFS format file adapter, with at the source directory a network share (
    server\sharename ). The share is on another system and not mapped to a local drivename, but it is open for everybody.
    The problem is, the adapter seems to not pick up the files in the directory, so there must be something I'm overlooking.
    - Both servers run on Windows
    - Share is available normally and open for everybody for all actions (including the SAPServiceSID user)
    - Files themselves are okay. If I put a file on a local drive and make the source directory the local drive instead of the network path, the file gets processed correctly
    - Because of the need for a file completion check, FTP is not an option
    Does anybody know what is going wrong, or what I could check for trace / logging info on possible cause of the problem?

    Hi,
    While using NFS mode you are supposed to put the file on XI server directory NOT to a common share directory of any other machine. And this is the reason your adapter in not picking the file.
    You can upload the file on XI server directory by using the tcode "SXDA_TOOLS", morevere you can check the file on the same directory with tcode "AL11". It is otherway-around, you can first select or chose the dir by AL11 and then put the file in the same dir by tcode SXDA_TOOLS.
    If you need more info about SXDA_TOOLS, let me know.
    Regards,
    Sarvesh

  • Trying to use wireless N with iwlwifi & network manager

    Have all the h/w necessary to use wireless N:
    Intel Centrino-N 1030
    Linksys E3200 running Tomato 1.28
    Linksys E4200 running dd-wrt 21286
    Also updated everything today (pacman -Syu):
    >uname -a
    Linux hostname 3.12.9-2-ARCH #1 SMP PREEMPT Fri Jan 31 10:22:54 CET 2014 x86_64 GNU/Linux
    So, with either router set up with as an AP at 2.4GHz and N-Only (the centrino 1030 doesn't support 5GHz), and the module defaults loaded, I see odd behavior.  First, once connected to either AP, Network Manager still reports the connection to be at B/G.
    I checked the module config, and this part is relevant:
    >modinfo iwlwifi | grep 11n
    parm: 11n_disable:disable 11n functionality, bitmap: 1: full, 2: agg TX, 4: agg RX (uint)
    There's a lot of chatter on the forums about earlier kernels not supporting N w/ iwlwifi, and recommending to disable it with '11n_disable=1' in /etc/modprobe.d/iwlwifi.conf.  So I tried explicitly enabling it, and assuming it's a binary value:
    >cat /etc/modprobe.d/iwlwifi.conf
    options iwlwifi 11n_disable=0
    After reloading the module(s) (and restarting wpa_supplicant & networkmanager), the thing I'm finding confusing is that I can see evidence of this change take effect:
    >cat /sys/module/iwlwifi/parameters/11n_disable
    0
    ...but it doesn't affect the output of modinfo (same as above), nor am I able to connect to either router at N (NM still reports B/G).  Also confused how it connects at all when the routers are set to N-Only?

    modinfo iwlwifi
    That is not supposed to change. It just shows you the parameters and their valid configurations.
    options iwlwifi 11n_disable=0
    >cat /sys/module/iwlwifi/parameters/11n_disable
    0
    Did you check that it was not already 0?
    ...but it doesn't affect the output of modinfo (same as above), nor am I able to connect to either router at N (NM still reports B/G).  Also confused how it connects at all when the routers are set to N-Only?
    If the card connects with the routers set to n only, then the card is capable of working with n. I usually check with nm-tools and look at the speed indicated.
    Here is the thing: Routers and cards sometimes negotiate a lower speed to prevent intereference with other devices. I usually 'get' N-speed only once I start to saturate the link.

  • [SOLVED] Network Manager with iPhone 3G S

    OK, so work got me a shiny new iPhone 3G S today. When I'm being paid to play with it, I'll give it a shot
    Anyway, I've successfully paired the iPhone over bluetooth with Arch on my laptop, which creates the bnep0 network interface. If I run dhcpcd on this interface, the iPhone gives me a DHCP lease in the 192.168.20.x subnet, and after configuring the opendns nameservers, I'm successfully tethered to the iPhone with full network connectivity
    Is there a way I can get Network Manager to do the 'dhcp' and 'nameserver' parts for me? In the nm-applet GUI, there's no option for specifying interfaces or anything just "wired" (eth0) and "wireless" (wlan0) as well as the VPN, 3G etc tabs.
    Also (I know someone wants to mention this), I am already aware that bluetooth is going to be speed limiting, but this connection will generally only be used for SSH sessions back to the office, so I don't really care about that. I'm happy to use bluetooth to reduce the number of cables required - already have external mouse, external hard drive, power supply and serial cable when I'm at a client site, I don't really want a USB cable to the iPhone as well. Unless Network Manager can't do this over bluetooth, but it can over USB, then I'll concede on the extra cable.
    Last edited by fukawi2 (2009-10-01 02:38:02)

    Here's instructions for Ubuntu, I doubt there will be many discrepancies between Ubuntu and Arch though. Just translate the apt-get crap with the appropriate yaourt or pacman command.
    http://undulynoted.net/2009/06/tether-i … -required/
    Ubuntu:
    Why oh why does apple hardware suck so hard with linux. You will get constant disconnects if your phone is more than a few feet away from the computer. But alas, it is still faster than pdanet or iphonemodem2.
    If you are not on a mac congratulations, you have had fewer headaches.
    Open the terminal and type:
    sudo apt-get install blueman bluez-compat
    This will remove wcid which hopefully isn't a problem for most of you.
    It will ask you to restart, please do.
    Once Ubuntu is back up click on your bluetooth icon in the upper right (which is now managed by blueman)
    IMPORTANT: Right click on the bluetooth icon and choose local services. Make sure to click the radio box that says "Network manager" instead of "blueman" under the network pane. This will allow Network Manager to take over the controlling of your connection (which is good). REBOOT AFTER THIS STEP!
    Go to the bluetooth settings in your iphone (Settings > General > Bluetooth) and make sure they are on.
    Hit the search button in blueman and you should see your iphone after a few seconds.
    WARNING: This is where it gets flaky on the macbook pro. Best results I have has is to highlight the phone in blueman and hit "Bond"
    Choose to auto generate a pass on the next option. Next. Now wait for the iPhone to ask you to type in the passphrase. Type in the 4 digit one that blueman gives you. VERY IMPORTANT. While they are joining eachother keep you eye on the computer. It will ask you if you always want to trust the iPhone (device name). Hit Always or else you will have trouble.
    Always initiate the connection from the iPhone. In the bluetooth settings on the iphone you will now see your computer name listed and the words "not conencted" next to it. Click it. Wait a few and it will hopefully say connected. Look back to blueman and you will now see status bars on the iphone. Right click on your iphone in blueman. Choose "Setup". Network access point is click by default so just hit "Next".
    Now head over to Network Manager and you should see "Auto benp0″. Click it to connect and give it a few to generate an IP. DONE enjoy surfing the internet through your data plan without jailbreaking. I have noticed quite a few speed gains over pdanet. Also, i noticed I got better results when i used openDNS's servers (208.67.220.220 and 208.67.222.222).
    If you have done everything correctly and Network Manager won't take over the connection of you can see it and it says "not managed" or something of the sort you need to check out the following:
    Open terminal and type: sudo gedit /etc/network/interfaces
    see if you have bnep0 located there. if you do, comment out or delete that line. and reboot your machine.

  • I need a keyring (that works with network-manager)

    Hi there,
    I'm new to Arch linux (coming from Ubuntu) and I'm wondering how to set up a keyring that works with that gnome-network-manager applet and ssh(fs). I previously used GNOME and the gnome keyring, and all out of the box.
    I couldn't find any manuals on how to set up the gnome-keyring in Arch linux, neither regarding ssh(fs) nor network-manager. I read people are complaining about network-manager asking for the keyring-unlocking-password, but this doesn't happen for me.
    How do I set up the gnome-keyring propertly?

    siriusb wrote:moljac024:
    https://bugs.launchpad.net/wicd/+bug/377471
    From this bug page:
    The /etc/wicd/wireless-settings.conf file is made root-readable only. This means that any malicious users must have root access or physical access to the machine. In either of these cases, you have far more problems than worrying about the wireless network key.
    Please see http://developer.pidgin.im/wiki/PlainTextPasswords for a very good explanation as to why the passwords are not encrypted.
    It may be plain text, but only root can read/write.

  • Network Manager fails to connect with Huawei E3276 modem after upgrade

    Hi,
    I have Huawei E3276 (lsusb: Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard).
    I wasn't updating the system for a long time (since KDE 4.14.3), but after upgrade Network Manager can't connect anymore.
    I also tried on the fresh install on different machine (KDE + Plasma 5.3), but I get the same error...
    Error: failed to connect modem: Only IPv4 is supported by this modem.
    I realize that this problem has nothing to do with KDE, but with new version of NM + MM, systemd, dhcpcd or dhclient?
    Why now Network Manager don't use ppp like before upgrade (different connection type "cdc-wdm0")?
    I would be grateful for any advice.
    After upgrade (KDE 4.14.3 -> 15.04 apps/5.2 plasma):
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now CONNECTING
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> need-auth (reason 'none') [40 60 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect started...
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (5/8): Register
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (6/8): Bearer
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (7/8): Connect
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0) failed to connect modem: Only IPv4 is supported by this modem
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> failed (reason '(null)') [40 120 1]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now DISCONNECTED
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> Disabling autoconnect for connection 'Orange'.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0): Activation: failed for connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): deactivating device (reason 'none') [0]
    Before upgrade (KDE 4.14)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) starting connection 'Orange'
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> NetworkManager state is now CONNECTING
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect started...
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (4/8): Wait to get fully enabled
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (5/8): Register
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (6/8): Bearer
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (7/8): Connect
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <warn> (ttyUSB0): port attributes not fully set
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (8/8): All done
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> (ttyUSB0): failed to look up interface index
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> using modem-specified IP timeout: 20 seconds
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> starting PPP connection
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> pppd started with pid 780
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    mar 23 19:31:33 AsusN56VZ pppd[780]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ kernel: PPP generic driver version 2.4.2
    mar 23 19:31:33 AsusN56VZ pppd[780]: pppd 2.4.6 started by root, uid 0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ kernel: PPP BSD Compression module registered
    mar 23 19:31:33 AsusN56VZ kernel: PPP Deflate Compression module registered
    mar 23 19:31:35 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (umts -> hspa-plus)
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> PPP manager(IP Config Get) reply received.
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    Linux Mint 17.1 KDE (works the same like Arch before update)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) starting connection 'Orange Standard access - with image compression'
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTING
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect started...
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect state (3/8): Enable
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
    May 7 20:06:33 mint17-vm ModemManager[781]: <warn> (ttyUSB1): port attributes not fully set
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    May 7 20:06:34 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (80)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (4/8): Wait to get fully enabled
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (5/8): Register
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (6/8): Bearer
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> WWAN now enabled by management service
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (7/8): Connect
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (77)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown -> lte)
    May 7 20:06:35 mint17-vm ModemManager[781]: <warn> (ttyUSB0): port attributes not fully set
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (8/8): All done
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> (ttyUSB0): failed to look up interface index
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> using modem-specified IP timeout: 20 seconds
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> starting PPP connection
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> pppd started with pid 2468
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    May 7 20:06:35 mint17-vm pppd[2468]: Plugin /usr/lib/i386-linux-gnu/pppd/2.4.5/nm-pppd-plugin.so loaded.
    May 7 20:06:35 mint17-vm pppd[2468]: pppd 2.4.5 started by root, uid 0
    May 7 20:06:35 mint17-vm pppd[2468]: Using interface ppp0
    May 7 20:06:35 mint17-vm pppd[2468]: Connect: ppp0 <--> /dev/ttyUSB0
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded: Welcome!!
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded
    May 7 20:06:35 mint17-vm kernel: [ 82.363825] PPP BSD Compression module registered
    May 7 20:06:35 mint17-vm kernel: [ 82.368188] PPP Deflate Compression module registered
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> PPP manager(IP Config Get) reply received.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) complete.
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: secondaries -> activated (reason 'none') [90 100 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTED_GLOBAL
    Last edited by Shocker (2015-05-07 19:18:43)

    This week, after update, modem works again.
    However, there's a new bug in the kernel, which was not there before:
    kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    but the modem works and connects to the network.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> Auto-activating connection 'Orange'.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTING
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect state (1/8): Unlock check
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (2/8): Wait to get fully initialized
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (locked -> initializing)
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ ModemManager[338]: Invalid mobile equipment error code: 50
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (initializing -> disabled)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (3/8): Enable
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <warn> (ttyUSB1): port attributes not fully set
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'locked' --> 'disabled' (reason: unknown)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <warn> (cdc-wdm0) failed to enable modem: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.InProgress: Cannot enable modem: already being enabled
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    may 24 09:32:48 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (8/8): All done
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) starting...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: prepare -> config (reason 'none') [40 50 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) successful.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) started...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: config -> ip-config (reason 'none') [50 70 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Activation (wwp0s20u2i2) Beginning DHCPv4 transaction (timeout in 15 seconds)
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> dhclient started with pid 3624
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): IPv6 configuration disabled
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) complete.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPDISCOVER on wwp0s20u2i2 to 255.255.255.255 port 67 interval 7
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPREQUEST on wwp0s20u2i2 to 255.255.255.255 port 67
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPOFFER from 10.X.X.X
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPACK from 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> address 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> plen 30 (255.255.255.252)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> gateway 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> server identifier 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> lease time 518400
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (wwp0s20u2i2): DHCPv4 state changed unknown -> bound
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) started...
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Joining mDNS multicast group on interface wwp0s20u2i2.IPv4 with address 10.X.X.X.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: New relevant interface wwp0s20u2i2.IPv4 for mDNS.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Registering new address record for 10.X.X.X on wwp0s20u2i2.IPv4.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: bound to 10.X.X.X -- renewal in 252436 seconds.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_LOCAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_GLOBAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Policy set 'Orange' (wwp0s20u2i2) as default for IPv4 routing and DNS.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Writing DNS information to /usr/bin/resolvconf
    may 24 09:33:09 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: successful, device activated.

  • Need getting network list with Network Manager

    I have not been able to get the list of networks to show up in Network Manager. I tried the NM wiki but still no luck. Help would be greatly appreciated.
    Wireless Card:
    06:00.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
    rc.conf
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(e100 mii slhc !bcm43xx b43 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="myhost"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # DHCP: Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    eth0="dhcp"
    INTERFACES=(!eth0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.1.1"
    ROUTES=(gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng !network hal dhcdbd networkmanager fam !netfs crond alsa gdm)
    Last edited by 449 (2008-08-28 22:42:39)

    I cannot get the LED light on. The card works fine because I am using XP right now.
    I installed both the bcm43xx and the bm43 firmware in an attempt to get it working. Could one or the other be causing a conflict?
    When I tried to modprobe either of the two I get something like "invalid operation."
    When I do
    b43-fwcutter -w "/lib/firmware/" wl_apsta_mimo.o
    it gives me an error saying the input doesn't exist.
    edit: Could I get this moved to the wireless section?
    Last edited by 449 (2008-09-05 17:07:51)

Maybe you are looking for