Network.manage-offline-status ineffective in FF4.0.1 on OSX 10.6.7

After Firefox automatically updated itself to version 4.0.1, it always starts up in "Work Offline" mode. network.manage-offline-status was set to true on about:config, so I set it to false, and that made no difference. I tried running FF in "safe mode", and that also made no difference.
It's annoying to have to uncheck the "Work Offline" option every time Firefox starts up.

Greetings,
The log suggests there is something wrong with the media browser on the computer.
Download and install the 10.6.7 combo update: http://support.apple.com/kb/DL1361
If the issue persists after installing the combo update then reinstall iPhoto:
1.) Remove the following to the trash:
/Applications/iPhoto
/Library/ApplicationSupport/iPhoto
/Library/Receipts/iPhoto -- there may be many iPhoto files here there may be none. If you find any here remove them.
2.) Reinstall iPhoto from the iLife 11 install disk, or from the App store, or from the disks that came with your computer: http://support.apple.com/kb/HT3415
3.) Run all your software updates after reinstalling.
Cheers.

Similar Messages

Network Printers go to offline status

Windows 8.1 32bit
shared network printers go to offline status, but are not offline.
when I reboot it resolves the issue

Hi,
Please check if the printer spooler service is running when this issue occurs. I suspect it is corrupted somehow, you can check the event log to see if there is any clue.
Alex Zhao
TechNet Community Support

Offline status yet I can connect

I manage 40 machines across Canada. 10 (including one local to my network) show with a status of 'offline'. Yet I can double-click and take control of the machines. But, with the offline status, I can not copy files to or from my machine to any of the 10 machines.
So, how do I get it to show the proper status? I tried with a Mini running 10.6.3, fully updated OS and ARD, and the one machine I really need to copy documents from still shows offline even though I can control the machine.

I'm seeing this same thing here. I manage multiple locations but I'm only seeing this issue with one new installation. I've tired deleting and re-entering the entry for this system and still reads as OFFLINE but I'm able to connect and control. The 3283 and 5900 ports are open. Any other suggestions? Could it be something with the router/firewall not reporting the status correctly?
thanks in advance,
Rick

Gnome-network-manager

Hi Everybody
I just tried to play a little with gnome-network-manager from AUR, first of all the normal network manager was missing a few files, but I managed to find them(http://aur.archlinux.org/packages/networkmanager/networkmanager/).
But when i start up gnome, it is shown fine in the Status Area, and shows all the networks, but it won't connect to any...
When connecting to an unencrypted network it says it is waiting for the network, when connecting to an encrypted network, it is waiting for the key to be verified.
My assumption is, that it is waiting for DHCP, in both cases.
If I use wifi-radar it gets an IP perfectly, also if I use dhclient or dhpcd it works fine.
Any suggestions?

I tried to use the one from testing, along with the gnome GUI from testing, but with no luck...
As you can see here, it tells me it is waiting fr the key, http://gallery.timmy.dk/Screenshots/gno … anager.png
But in the consle, iwconfig says I'm already connected...
So I'm pretty sure there something wrong with the dhcp

[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

Connman - network manager

Hello,
I am using E17 windows manager and would like to use connman network manager, but unfortunately it does not work for me. Has anybody some tips?
PS: I do have working networkamanger (disabled now) and did had wicd (in previous install).
System boots without any errors (although it is just a bit longer in udev section, but still no errors), I can load connman module, but it is always in offline mode.
All other networking managers are disabled. My rc.conf has these daemons:
syslog-ng dbus !networkmanager crond connmand iptables slim
Recently discovered that there is connman applet, which after adding to start-up starts, takes ones icon place (white) and disappears after few second.
I tried install it from yaourt simple connman, connman git, connman-gnome-git ... they all had some results, susses-full install, but after reboot there are no internet.
Last edited by vaidotas203 (2012-04-14 18:39:00)

I switched to wicd, so this isn't an issue anymore, I guess... still not sure what was going wrong, though.

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

Network Manager keeps asking for WPA passphrase

Hi, I finally managed to install arch on my netbook, everything seems to be in working order apart from my wireless connection..
I've installed and configured the broadcom drivers for my card from the AUR and both the access points I usually connect to (under windows/ubuntu) are visible.
firstly I tried to connect to my access point using wicd, it appears to work until it trys to validate the connection and eventually returns the error:
'Connection Failed: Bad Password'
im 100% certain i have entered the passphrase correctly.
I googled around, to find some people are having similar problems - i couldnt find a complete solution to my problem but a lot of people were linking to wicd-bzr. I have the same problem using wicd-curses..
next i decided to try NetworkManager, I uninstalled wicd and installed networkmanager 'pacman -S network-manager-applet'
again, the manager displays all available access points, i try to connect to my router and it repeatedly asks for my passphrase and never manages to connect.
does anyone has any ideas?
im using xfce4 (i also tried in gnome), the broadcom device is B4312, and the network security is WPA. Cheers.

Same problem here, tested with Wicd (also wicd-bzr), Netcfg and NetworkManager.
Tried wpa_gui, the event history keep saying:
WPS-AP-AVAILABLE
Trying to associate with [MAC-ADDRESS] (SSID)
Authentication with [MAC-ADDRESS] timed out
CTRL-EVENT-SCAN-RESULTS
Edit: sorry, i forgot to paste wpa_supplicant output with -d flag:
[root@hydra log]# wpa_supplicant -ddd -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='network'
update_config=1
Line: 5 - start of a new network block
ssid - hexdump_ascii(len=21):
46 41 53 54 57 45 42 2d 31 2d 50 41 32 37 32 39 FASTWEB-1-PA2729
30 31 35 4d 41 015MA
PSK (ASCII passphrase) - hexdump_ascii(len=21): [REMOVED]
proto: 0x2
key_mgmt: 0x2
pairwise: 0x8
auth_alg: 0x1
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Line 12: removed CCMP from group cipher list since it was not allowed for pairwise cipher
Priority group 0
id=0 ssid='FASTWEB-1-PA2729015MA'
WEXT: cfg80211-based driver detected
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: 00:13:02:10:34:2e
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): a6 20 a7 e6 1e b5 58 c3 92 4f 1e 08 8d 27 ba 7a
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
ctrl_interface_group=90 (from group name 'network')
Added interface wlan0
Daemonize..
My wireless card is a Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Router is a Linksys WRT320N, configured with WPA2 Personal, Encryption AES or TKIP
Last edited by morgenstern (2010-11-19 18:41:58)

No Network Manager Applet

So I just installed Arch on my desktop, I am wireless, but I have made sure my wireless card is properly configured. I have gone into the settings menu and looked at my applets and it says the applet is there but it never works or shows up. For whatever reason, no matter how many desktop environments I try I never have a network manager. I've tried KDE, Gnome, XFCE, and Cinnamon and none of them have it. Ordinarily I wouldn't mind connecting to wifi through the terminal, but when I go back to school, the network there requires a username to log in which according to my experience is not possible through the terminal. If it is please correct me and/or offer me a suggestion. Thanks in advance

TheNeXus84 wrote:
I am using an Intel Centrino Advanced N6205 wireless card.
the output of my systemctl status NetworkManager command is as follows:
[root@ArchLinux cj]# systemctl status NetworkManager
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled)
Active: active (running) since Sun 2013-12-22 20:42:57 EST; 23s ago
Main PID: 645 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
└─645 /usr/bin/NetworkManager --no-daemon
Dec 22 20:43:11 ArchLinux NetworkManager[645]: <info> Config: set interface ...1
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <warn> Connection disconnecte...)
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <warn> Connection disconnecte...)
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...g
Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
Dec 22 20:43:14 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...g
Dec 22 20:43:17 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
Hint: Some lines were ellipsized, use -l to show in full.
UPDATE: I fixed the problem. I had to enable DHCPCD. sorry to be a bother to you all but thanks for the help and support.
EDIT: upon rebooting my previous problem has occurred again.
Make sure that you have done
systemctl enable NetworkManager
as well as
systemctl start NetworkManager
- also when you ran dhcpcd how did you do it? Your network interface is wlp5s0 so you need to have dhcp running for that interface -
systemctl start [email protected]
will start it if it is not started, and
systemctl enable [email protected]
will ensure it starts after booting up. However I never needed to start dhcpcd at all when using NetworkManager.
There are occasions when the relative timing of different services does not allow some services to start properly - and then occasionally you need to add in some items to the NetworkManager service file to tell it to wait until the network is up first, if there are delays in the network starting at boot time but that can be sorted out once the basic services are set to start at boot.
Last edited by mcloaked (2013-12-23 18:01:46)

CM 4.4.7 Online and End Devices 4.2.3c Offline status

Hallo all,
I am running WAE-512-K9 and the Central Manager was upgraded to 4.4.7 and the Some Application Accelerators are running 4.2.3c and they seem to be showing "offline status " but they are still optimizing save for the status being "offline"
What could be the Issue here ?

Hi Erasmus,
Are all accelerators running version 4.2.3c showing offline or just few? If all on same version are showing offline it could incompatibility issue between versions.
You can also go to the application accelerator CLI and execute the command:
show cms info
See what it shows. Check the connectivity between accelerator and CM. If it is fine and nothing has changed (like FW rules in between accelerator and CM) try doing the below and see if that resolves the issue.
cms deregister force.
Once deregistered go to config mode and do "cms enable".
Check the show cms info again.
Regards,
Kanwal

Networking? More like Notworking (Wicd and Network Manager Broken?)

Wicd won't run for me and NetworkManager never seems to be able to connect because of some errror.
$ sudo systemctl start wicd
Failed to issue method call: Unit wicd.service failed to load: No such file or directory. See system logs and 'systemctl status wicd.service' for details.
I see that systemctl doesn't see wicd yet, so I'll reboot in a second and try to start wicd again.
Here's what nm-applet prints out when I try to connect to my local network.
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
** (nm-applet:31344): WARNING **: Failed to register as an agent: (32) Session not found
** (nm-applet:31344): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/1: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
** (nm-applet:31344): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/1: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
** (nm-applet:31344): WARNING **: Connection activation failed: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/1' failed in libnm-glib.
** (nm-applet:31344): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/1: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
and a little error window pops up with the following message
(1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/1' failed in libnm-glib
Any ideas? So far I can only connect using netcfg, and even then I lose my connection every so often, and I can't connect to anything if the NetworkManager.service is running.

10PinkPanther wrote:Disabling or remowing netcfg worked for me with disconnecting problem.Once it was disabled network manager or wicd worked fine.
Netcfg isn't enabled, though. Nor have I been able to ever start netcfg successfully.
Here's what happens when I try to start it.
$ sudo systemctl start netcfg
Job for netcfg.service failed. See 'systemctl status netcfg.service' and 'journalctl -xn' for details.
Here's what systemctl status returns on netcfg.
$ sudo systemctl status netcfg
netcfg.service - Netcfg multi-profile daemon
Loaded: loaded (/usr/lib/systemd/system/netcfg.service; disabled)
Active: inactive (dead)
CGroup: name=systemd:/system/netcfg.service
Dec 01 15:48:11 Beleriand systemd[1]: Unit netcfg.service entered failed state
Dec 01 15:48:26 Beleriand systemd[1]: Starting Netcfg multi-profile daemon...
Dec 01 15:48:26 Beleriand netcfg-daemon[7446]: No recorded netcfg state to restore
Dec 01 15:48:26 Beleriand systemd[1]: netcfg.service: main process exited, code=exited, status=1/FAILURE
Dec 01 15:48:26 Beleriand systemd[1]: Failed to start Netcfg multi-profile daemon.
Dec 01 15:48:26 Beleriand systemd[1]: Unit netcfg.service entered failed state
Dec 01 19:08:35 Beleriand systemd[1]: Starting Netcfg multi-profile daemon...
Dec 01 19:08:35 Beleriand netcfg-daemon[4884]: No recorded netcfg state to restore
Dec 01 19:08:35 Beleriand systemd[1]: netcfg.service: main process exited, code=exited, status=1/FAILURE
Dec 01 19:08:35 Beleriand systemd[1]: Failed to start Netcfg multi-profile daemon.
Dec 01 19:08:35 Beleriand systemd[1]: Unit netcfg.service entered failed state
Here's what journalctl -xn returns
$ sudo journalctl -xn
-- Logs begin at Mon, 2012-11-26 12:49:07 EST, end at Fri, 2012-12-07 10:41:30 EST. --
Dec 07 10:06:17 Beleriand dbus-daemon[389]: dbus[389]: [system] Rejected send message, 11 matched rules; type="error", sender=":1.97" (uid=1000 pid=13824 comm="
Dec 07 10:06:17 Beleriand systemd[1]: Stopped Network Manager.
-- Subject: Unit NetworkManager.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286
-- Unit NetworkManager.service has finished shutting down.
Dec 07 10:06:28 Beleriand metalog[384]: fo> (eth0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]<14>Dec 7 10:06:16 NetworkManage
Dec 07 10:07:19 Beleriand metalog[384]: dhcpcd -qL -t 10 eth1<86>Dec 7 10:06:28 sudo: pam_unix(sudo:session): session closed for user root<30>Dec 7 10:06:31 d
Dec 07 10:41:01 Beleriand systemd[1]: Starting Netcfg multi-profile daemon...
-- Subject: Unit netcfg.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d4958e842da4a758f6c1cdc7b36dcc5
-- Unit netcfg.service has begun starting up.
Dec 07 10:41:01 Beleriand netcfg-daemon[421]: No recorded netcfg state to restore
Dec 07 10:41:01 Beleriand systemd[1]: netcfg.service: main process exited, code=exited, status=1/FAILURE
Dec 07 10:41:01 Beleriand systemd[1]: Failed to start Netcfg multi-profile daemon.
-- Subject: Unit netcfg.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- Unit netcfg.service has failed.
-- The result is failed.
Dec 07 10:41:01 Beleriand systemd[1]: Unit netcfg.service entered failed state
Dec 07 10:41:30 Beleriand metalog[384]: oot<37>Dec 7 10:24:42 sudo: palantir : TTY=pts/6 ; PWD=/home/palantir/repos/core/pkgbuilds/wine-starcraft-optimized/2i/

Network Manager fails to connect with Sierra Wireless 3G/4G modem

Hi,
I have three Asus Laptops running with Arch (Asus N56VZ, Asus F3JC, Asus UL80VS). All laptops work with Cinnamon Desktop. Everything works fine except 3G Modem in Network Manager. I have two USB modems: Sierra Wireless AirCard 310U and Sierra Wireless AirCard 320U.
Modems had worked fine in end of year 2012, when NetworkManager version was 0.9.6.4 and ModemManager 0.6.0.0. After update (NM >0.8.X.X, MM >0.7.X. - when the ModemManager.service appeared) until now, I can't connect to the internet on all Asus laptops. Since 2013 I have to use wvdial, because in wvdial modems works fine. It is Arch problem, because in Linux Mint 15 I can connect with NetworkManager.
Sierra AirCard 310U - When I'm connecting to the internet, modem reboots itself.
Sierra AirCard 320U - When I'm connecting to the internet, Network Manager can't obtain DHCP address.
I would be grateful for any help.
Sierra Wireless AirCard 310U (USB 3G Modem) log:
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) starting connection 'Orange PL'
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled...
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started...
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete.
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Simple connect started...
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Simple connect state (3/8): Enable
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <warn> (ttyUSB2): port attributes not fully set
aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:41:39 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '260', MNC: '3', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:41:40 AsusN56VZ kernel: usb 3-2: USB disconnect, device number 3
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ ModemManager[308]: mm_serial_port_close: assertion `priv->open_count > 0' failed
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (4/8): Wait to get fully enabled
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (5/8): Register
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> (tty/ttyUSB2): released by modem /sys/devices/pci0000:00/0000:00:14.0/usb3/3-2
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (6/8): Bearer
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB0: Sierra USB modem converter now disconnected from ttyUSB0
aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.0: device disconnected
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: Sierra USB modem converter now disconnected from ttyUSB1
aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.1: device disconnected
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: Sierra USB modem converter now disconnected from ttyUSB2
aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.3: device disconnected
aug 22 13:41:40 AsusN56VZ kernel: sierra_net 3-2:1.7 wwp0s20u2i7: unregister 'sierra_net' usb-0000:00:14.0-2, Sierra Wireless USB-to-WWAN Modem
aug 22 13:41:40 AsusN56VZ kernel: ModemManager[308]: segfault at 28 ip 0000000000433350 sp 00007ffff409e088 error 4 in ModemManager[400000+e0000]
aug 22 13:41:40 AsusN56VZ systemd[1]: ModemManager.service: main process exited, code=dumped, status=11/SEGV
aug 22 13:41:40 AsusN56VZ systemd[1]: Unit ModemManager.service entered failed state.
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> ModemManager disappeared from bus
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): device state change: prepare -> unmanaged (reason 'removed') [40 10 36]
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): deactivating device (reason 'removed') [36]
aug 22 13:41:40 AsusN56VZ laptop-mode[2414]: Laptop mode
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): cleaning up...
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): taking down device.
aug 22 13:41:40 AsusN56VZ laptop-mode[2415]: enabled, not active
aug 22 13:41:40 AsusN56VZ systemd-coredump[2336]: Process 308 (ModemManager) dumped core.
aug 22 13:41:40 AsusN56VZ systemd[1]: Starting Modem Manager...
aug 22 13:41:40 AsusN56VZ systemd[1]: ModemManager.service holdoff time over, scheduling restart.
aug 22 13:41:40 AsusN56VZ systemd[1]: Stopping Modem Manager...
aug 22 13:41:40 AsusN56VZ systemd[1]: Starting Modem Manager...
aug 22 13:41:43 AsusN56VZ kernel: sierra_net 3-2:1.7 (unregistered net_device): usb_control_msg failed, status -19
Sierra Wireless AirCard 320U (3G/4G Modem) log:
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) starting connection 'Orange PL'
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) scheduled...
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) started...
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) complete.
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Simple connect started...
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Simple connect state (3/8): Enable
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (disabled -> enabling)
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <warn> (ttyUSB3): port attributes not fully set
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <warn> (ttyUSB4): port attributes not fully set
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (unknown -> registering)
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (registering -> home)
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: '260', MNC: '3', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (enabling -> registered)
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (4/8): Wait to get fully enabled
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (5/8): Register
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (6/8): Bearer
aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> WWAN now enabled by management service
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (7/8): Connect
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (registered -> connecting)
aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (40)
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: access technology changed (unknown -> hsdpa, hsupa)
aug 22 13:48:09 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connecting -> connected)
aug 22 13:48:09 AsusN56VZ ModemManager[314]: <info> Simple connect state (8/8): All done
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) scheduled...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) starting...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: prepare -> config (reason 'none') [40 50 0]
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): bringing up device.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) successful.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) scheduled.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) complete.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) started...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (wwp0s20u2i7) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 22 13:48:09 AsusN56VZ kernel: IPv6: ADDRCONF(NETDEV_UP): wwp0s20u2i7: link is not ready
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> dhclient started with pid 2351
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) complete.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) started...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) complete.
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Internet Systems Consortium DHCP Client 4.2.5-P1
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Copyright 2004-2013 Internet Systems Consortium.
aug 22 13:48:09 AsusN56VZ dhclient[2351]: All rights reserved.
aug 22 13:48:09 AsusN56VZ dhclient[2351]: For info, please visit https://www.isc.org/software/dhcp/
aug 22 13:48:09 AsusN56VZ dhclient[2351]:
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (wwp0s20u2i7): DHCPv4 state changed nbi -> preinit
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Listening on LPF/wwp0s20u2i7/8e:1d:fe:e0:02:07
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Sending on LPF/wwp0s20u2i7/8e:1d:fe:e0:02:07
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Sending on Socket/fallback
aug 22 13:48:09 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 5
aug 22 13:48:14 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 5
aug 22 13:48:19 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
aug 22 13:48:26 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
aug 22 13:48:33 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
aug 22 13:48:36 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (40)
aug 22 13:48:40 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 10
aug 22 13:48:50 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 17
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <warn> (wwp0s20u2i7): DHCPv4 request timed out.
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (wwp0s20u2i7): canceled DHCP transaction, DHCP client pid 2351
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) started...
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <warn> Activation (ttyUSB3) failed for connection 'Orange PL'
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) complete.
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: failed -> disconnected (reason 'none') [120 30 0]
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): deactivating device (reason 'none') [0]
aug 22 13:48:54 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connected -> disconnecting)
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'connected' --> 'disconnecting' (reason: user-requested)
Last edited by Shocker (2013-09-14 20:08:08)

Shocker wrote:I don't think it's kernel problem, because Linux Mint 15 have kernel 3.8 and there is everything fine. Maybe systemd (Fedora & Arch have systemd, but Mint sysvinit..), maybe version of dhcpcd, I have no idea...
To test, I downgraded my kernel
~ ᐅ uname -r
3.9.5-301.fc19.x86_64.debug
And now I see in messages
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) starting connection 'Telstra'
Sep 15 09:46:17 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) scheduled...
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) started...
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) complete.
Sep 15 09:46:17 localhost modem-manager[757]: <info> (ttyUSB2) opening serial port...
Sep 15 09:46:17 localhost modem-manager[757]: <warn> (ttyUSB2): port attributes not fully set
Sep 15 09:46:17 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling)
Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <info> (ttyUSB2) opening serial port...
Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <warn> (ttyUSB2): port attributes not fully set
Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling)
Sep 15 09:46:18 localhost dbus-daemon[618]: modem-manager[757]: <info> (ttyUSB2): using PDU mode for SMS
Sep 15 09:46:18 localhost modem-manager[757]: <info> (ttyUSB2): using PDU mode for SMS
Sep 15 09:46:18 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling -> enabled)
Sep 15 09:46:18 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling -> enabled)
Sep 15 09:46:18 localhost NetworkManager[724]: <info> WWAN now enabled by management service
Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabled -> registered)
Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabled -> registered)
Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> connected)
Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> connected)
Sep 15 09:46:19 localhost kernel: [ 5056.773068] IPv6: ADDRCONF(NETDEV_UP): wwp0s29u1u1i7: link is not ready
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) scheduled...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) starting...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: prepare -> config (reason 'none') [40 50 0]
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): bringing up device.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) successful.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) complete.
Sep 15 09:46:19 localhost avahi-daemon[607]: Registering new address record for fe80::c0c3:a2ff:fe4a:207 on wwp0s29u1u1i7.*.
Sep 15 09:46:19 localhost kernel: [ 5056.876750] IPv6: ADDRCONF(NETDEV_CHANGE): wwp0s29u1u1i7: link becomes ready
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) started...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Beginning DHCPv4 transaction (timeout in 45 seconds)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> dhclient started with pid 10376
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) complete.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) started...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Sep 15 09:46:19 localhost dhclient[10376]: Internet Systems Consortium DHCP Client 4.2.5
Sep 15 09:46:19 localhost dhclient[10376]: Copyright 2004-2013 Internet Systems Consortium.
Sep 15 09:46:19 localhost dhclient[10376]: All rights reserved.
Sep 15 09:46:19 localhost dhclient[10376]: For info, please visit https://www.isc.org/software/dhcp/
Sep 15 09:46:19 localhost dhclient[10376]:
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed nbi -> preinit
Sep 15 09:46:19 localhost dhclient[10376]: Listening on LPF/wwp0s29u1u1i7/c2:c3:a2:4a:02:07
Sep 15 09:46:19 localhost dhclient[10376]: Sending on LPF/wwp0s29u1u1i7/c2:c3:a2:4a:02:07
Sep 15 09:46:19 localhost dhclient[10376]: Sending on Socket/fallback
Sep 15 09:46:19 localhost dhclient[10376]: DHCPREQUEST on wwp0s29u1u1i7 to 255.255.255.255 port 67 (xid=0x6e8c90b2)
Sep 15 09:46:19 localhost dhclient[10376]: DHCPNAK from 10.102.67.253 (xid=0x6e8c90b2)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed preinit -> expire
Sep 15 09:46:19 localhost dhclient[10376]: DHCPDISCOVER on wwp0s29u1u1i7 to 255.255.255.255 port 67 interval 6 (xid=0xae2cec8)
Sep 15 09:46:19 localhost dhclient[10376]: DHCPREQUEST on wwp0s29u1u1i7 to 255.255.255.255 port 67 (xid=0xae2cec8)
Sep 15 09:46:19 localhost dhclient[10376]: DHCPOFFER from 10.102.67.253
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed expire -> preinit
Sep 15 09:46:19 localhost dhclient[10376]: DHCPACK from 10.102.67.253 (xid=0xae2cec8)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed preinit -> bound
Sep 15 09:46:19 localhost NetworkManager[724]: <info> address 10.102.67.12
Sep 15 09:46:19 localhost NetworkManager[724]: <info> prefix 24 (255.255.255.0)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> gateway 10.102.67.12
Sep 15 09:46:19 localhost NetworkManager[724]: <info> nameserver '10.4.81.103'
Sep 15 09:46:19 localhost NetworkManager[724]: <info> nameserver '10.4.182.20'
Sep 15 09:46:19 localhost NetworkManager[724]: nm_ip4_config_add_wins: assertion `wins > 0' failed
Sep 15 09:46:19 localhost NetworkManager[724]: <info> wins '0.0.0.0'
Sep 15 09:46:19 localhost NetworkManager[724]: nm_ip4_config_add_wins: assertion `wins > 0' failed
Sep 15 09:46:19 localhost NetworkManager[724]: <info> wins '0.0.0.0'
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Commit) started...
Sep 15 09:46:19 localhost avahi-daemon[607]: Joining mDNS multicast group on interface wwp0s29u1u1i7.IPv4 with address 10.102.67.12.
Sep 15 09:46:19 localhost avahi-daemon[607]: New relevant interface wwp0s29u1u1i7.IPv4 for mDNS.
Sep 15 09:46:19 localhost avahi-daemon[607]: Registering new address record for 10.102.67.12 on wwp0s29u1u1i7.IPv4.
Sep 15 09:46:19 localhost dhclient[10376]: bound to 10.102.67.12 -- renewal in 97473 seconds.
Sep 15 09:46:20 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Sep 15 09:46:20 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Commit) complete.
Sep 15 09:46:20 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 15 09:46:20 localhost NetworkManager[724]: <info> Policy set 'Telstra' (wwp0s29u1u1i7) as default for IPv4 routing and DNS.
Sep 15 09:46:20 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) successful, device activated.
I'm going to ask on #fedora and see how i can best diagnose what's going on. At least I now have it working, albeit on an older kernel.
Last edited by qnm (2013-09-14 23:48:05)

T2000 Network Management

Hi Folks,
I just got a T2000 server, and have hooked it up (sort of).
Right now, I'm running everythign through the serial console, which I've found to be pretty darn ineffective.
I booted into solaris no problem, but I don't know how to get hte management network running.
The first thing I did was set netsc_dhcp=true, since that's how the network is configured. Then I did show netsc_ipaddr, and it told me 0.0.0.0, i.e. I screwed up!
How do I configure the network management port to work? I thought you could just DHCP and let the router take care of everything...
Thanks,
David

Try to run setupsc command (an interactive script mode)
sc> setupsc
and answer the question.

Network management

Hello guys..
this my first question for me at Cisco support forums..
I have couple of questions and I would like to get your views and answers..
Suppose that I am administrator of a university, and I created an excellent design for my network.
1)How can I manage my network from my office.. I mean what kind of software that helps me to monitor my entire network for faults, configuration, performance and security for medium enterprise like university with lowest cost possible.
does anyone have idea about how Cisco nac works??

If you look at Cisco NAC from an overall perspective of network management and network security, you can consider the following:
Additional NAC Services
The Cisco NAC Solution can be optionally deployed with the Cisco Identity Services Engine for profiling services and the NAC Guest Server.
• Cisco Identity Services Engine (ISE): Cisco ISE provides profiling capabilities that can discover, analyze, and classify in real time all the endpoints connecting to the network. Cisco ISE comes with hundreds of built-in profiles for devices such as IP phones, printers, mobile devices (IPads, IPhones), scanners, and more, making it possible to identify the type of device connecting to the network. Cisco ISE provides the administrator full visibility into everything connected to the network in real time. It allows the administrator to control the access privileges associated with each type of endpoint.
Starting the Cisco ISE Version 1.0 MR and Cisco NAC Version 4.9, the Cisco ISE can integrate with the Cisco NAC to provide profiler capabilities to a NAC deployment. The combined deployment of the Cisco NAC with the Cisco ISE is the replacement for the Cisco NAC Profiler, which has reached end-of-life status.
To find out more about Cisco ISE, please visit:http://www.cisco.com/en/US/products/ps11640/products_data_sheets_list.html.
• Cisco NAC Guest Server: The optional Cisco NAC Guest Server streamlines the provisioning, notification, management, and reporting of guest users on wired and wireless networks. It offloads resources from IT staff who are charged with supporting corporate visitors. The secure NAC Guest Server enhances your ability to protect your assets, employees, and information while providing network access that fully meets your visitors' business needs. For more information about the Cisco NAC Guest Server data sheet, visit: http://www.cisco.com/en/US/products/ps10160/products_data_sheets_list.html.
and that requires planning....
alot...
and lab tests first before entering production.
In a network with approx 1000 users you will definitely need a few monitoring tools. For security , really study NAC concepts and ISE. Keep in mind , the more users you have, the longer it takes to implement ISE, but if you have that going, you have the network on lockdown at your fingertips.
Please rate if you find helpfull
Let me know if you have more questions
Isak

[SOLVED] Network Manager systemd unit fails after update

EDIT: Reinstalling libnm-glib resolved this issue
After updating to the latest version of NetworkManager (networkmanager-0.9.8.10-3), the systemd unit fails to start. It works fine after downgrading back to the previous version though (networkmanager-0.9.8.10-1). I'm not sure if this is a bug or an error on my end; since the previous package works I've just dowgraded for the time being. For the update that doesn't work, here is the output of "systemctl status" and the systemd journal:
>>sudo systemctl daemon-reload
>> sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: failed (Result: exit-code) since Wed 2014-06-11 15:28:25 EDT; 10s ago
Process: 24073 ExecStart=/usr/bin/NetworkManager --no-daemon (code=exited, status=127)
Main PID: 24073 (code=exited, status=127)
Jun 11 15:28:25 kyle systemd[1]: NetworkManager.service: main process exited, code=exited, status=127/n/a
Jun 11 15:28:25 kyle systemd[1]: Failed to start Network Manager.
Jun 11 15:28:25 kyle systemd[1]: Unit NetworkManager.service entered failed state.
>> journalctl -xn
-- Logs begin at Tue 2014-06-10 12:47:19 EDT, end at Wed 2014-06-11 15:28:36 EDT. --
Jun 11 15:28:25 kyle sudo[24070]: pam_unix(sudo:session): session opened for user root by kyle(uid=0)
Jun 11 15:28:25 kyle systemd[1]: Starting Network Manager...
-- Subject: Unit NetworkManager.service has begun with start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit NetworkManager.service has begun starting up.
Jun 11 15:28:25 kyle systemd[1]: NetworkManager.service: main process exited, code=exited, status=127/n/a
Jun 11 15:28:25 kyle systemd[1]: Failed to start Network Manager.
-- Subject: Unit NetworkManager.service has failed
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit NetworkManager.service has failed.
-- The result is failed.
Jun 11 15:28:25 kyle systemd[1]: Unit NetworkManager.service entered failed state.
Jun 11 15:28:25 kyle sudo[24070]: pam_unix(sudo:session): session closed for user root
Jun 11 15:28:28 kyle dbus[489]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out
Jun 11 15:28:36 kyle sudo[24075]: kyle : TTY=pts/2 ; PWD=/var/cache/pacman/pkg ; USER=root ; COMMAND=/usr/bin/systemctl status NetworkManager
Jun 11 15:28:36 kyle sudo[24075]: pam_unix(sudo:session): session opened for user root by kyle(uid=0)
Jun 11 15:28:36 kyle sudo[24075]: pam_unix(sudo:session): session closed for user root
Last edited by T0k3n (2014-07-03 15:18:01)

Check the changes:
https://projects.archlinux.org/svntogit … e192881dc5
https://projects.archlinux.org/svntogit … ee906b6c44
When posting configs, code or command output, please use [ code ] tags, not [ quote ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and - in case of longer listings - more convenient to scroll through.

Network.manage-offline-status ineffective in FF4.0.1 on OSX 10.6.7

Similar Messages

Maybe you are looking for