[SOLVED] Network Difficulties

I have reinstalled Arch this afternoon only to run into a problem I have had in the past. My desktop is connected to a school network, which requires a user name and password. To solve this problem in the past I simply installed elinks from a usb drive. Today, when I run elinks I am told "Unable to retrieve http://www.google.com/: Host not found." I also cannot ping Google. Normally I would be redirect in elinks to the login site. I may very well be making a simple mistake as I am not terribly experienced with networking.
Log of ifconfig -a
Fri Apr 10 04:02:42 2009
eth0 Link encap:Ethernet HWaddr 00:22:15:EA:85:CF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17
eth1 Link encap:Ethernet HWaddr 00:22:15:EA:9D:97
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:18
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Fri Apr 10 04:02:42 2009
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost lotte
# End of file
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="America/New_York"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# 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=()
# 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="lotte"
# 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="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
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.0.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 netfs @crond)
Last edited by filam (2009-04-11 01:00:41)

Tenken wrote:It looks like you're missing a dhcp client (dhcpcd or dhclient) in your daemons line.
Wow. Thank you. I can't believe I didn't think to check my daemons.

Similar Messages

[SOLVED] network randomly doesn't work after reboot (e100)

Hi
Lately I have some weird issues with network. I shutdown computer during night, so basicly I reboot it at least once per day and every now and then without any pattern network doesn't work at all and so far only solution I have found is to reboot (again).
Before anything else I'm sure it's not hardware problem, since other OS on same computer don't have any issues, neither is router since other devices in network from laptops to mobile phones work flawless.
Relevant info and what I have found so far (not everything is copy/pasted so there may be some typos):
$less rc.conf (network part)
eth1="eth1 192.168.1.242 netmask 255.255.255.0 broadcast 192.168.1.255
INTERFACES=(eth1)
gateway="default gw 192.168.1.1"
ROUTES=(gateway)
$ifconfig
eth1 Link encap:Ethernet HWaddr 00:D0:B7:5A:7A:A9
inet addr:192.168.1.242 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:380 errors:0 dropped:0 overruns:0 frame:0
TX packets:380 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:36154 (35.3 Kb) TX bytes:36154 (35.3 Kb)
$route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
$ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data
From 192.168.1.242 icmp_seq=2 Destination Host Unreachable
So basicly network is dead, can't even ping router, cable connection is detected tho (lights are on). I have tried to restart newtork with /etc/rc.d/network stop/start, nothing. Only clue is dmesg.
$dmesg
Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.1 (GCC) ) #1 SMP PREEMPT Fri Jul 31 07:30:28 CEST 2009
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e100 0000:03:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
e100 0000:03:07.0: PME# disabled
e100: eth1: e100_probe: addr 0xfdfff000, irq 17, MAC addr 00:d0:b7:5a:7a:a9
e100 0000:03:07.0: firmware: requesting e100/d101m_ucode.bin
ADDRCONF(NETDEV_UP): eth1: link is not ready
modrope -r e100 and then reloading it doesn't help either, but reboot does (once I had to reboot twice tho).
Anyone with more clue and ideas then me, it's getting really annoying, it also kill whole KDE plasma-desktop for couple of minutes before plasmoids find out network is really down and I'm not really fan of morning "gamble". I can't pinpoint some hard date/update when this started to happening because like I said it's random but last couple of months should be quite accurate. Thanks in advance.
EDIT: dmesg when network works:
tilen@pikmin ~]$ dmesg | grep e100
pci 0000:03:07.0: Firmware left e100 interrupts enabled; disabling
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e100 0000:03:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
e100 0000:03:07.0: PME# disabled
e100: eth0: e100_probe: addr 0xfdfff000, irq 17, MAC addr 00:d0:b7:5a:7a:a9
Last edited by NoOrdinary (2009-09-05 09:47:20)

I don't have anything special set at router but I doubt rc.conf play any role. I will try to set it up with dhcp (but I think I have tried that already) if there is any change.
This morning I had to reboot twice, so new kernel didn't help. Fowler, what network card are you using, also e100 (well or some intel)? I dunno, should this be handed to the kernel team? If it will piss me enough one morning I'll just go and buy a new network card, just wanna be sure that will really solve the problem.
UPDATE: OK, this is just silly. I remebered I have acctualy onboard LAN so I edited rc.conf and dived into the dust under my desk to move cable and there I found out it was acctual onboard in use all the time Now this dosen't make much sense to me anymore, when I can't get net up all the stuff in dmesg is e100 related. Anyway, I connected network to e100 and rebooted, suprise, same story. Dmesg reported again link was not ready. I edited rc.conf to
INTERFACES=(eth0 !eth1)
in case this has anything to do with proper timing at assigning whatever needs to be assigned to network cards at boot so I'm sure just 1 card with all info provided get's kicked in at boot. First reboot after that works, it dosen't prove anything yet but at leat it's some kind of progress in recognising proper cause.
UPDATE 2: Nah, still happens. Googling for "no link during initialization" show a lot of familiar problems, almost all on nforce motherboards and mine is nforce too. I just don't get it why this mess seperate PCI network card. In any case it's extremely annoying.
Last edited by NoOrdinary (2009-09-02 11:46:27)

[SOLVED] Network manager only works as root

Hello everyone,
I am brand new to arch and have been quite impressed over the past few days over all it has to offer. Everything has been running quite smoothly and I am now in the process of setting up wireless. I installed network manager and was able to connect to a wireless network as root. For my regular user, however, I am running into some issues. First one was that the nm-applet could not be opened in fluxbox. I received the following error:
** (nm-applet:1576): WARNING **: <WARN> request_name(): Could not acquire the NetworkManagerUserSettings service.
Error: (9) Connection ":1.27" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file
I "fixed" this by adding the following to /etc/dbus-1/system.d/nm-applet.conf. Original credit goes to the user in this thread (I only slightly modified his code): https://bbs.archlinux.org/viewtopic.php?id=63576

<policy user="myusername">
<allow own="org.freedesktop.NetworkManagerUserSettings"/>
<allow send_destination="org.freedesktop.NetworkManagerUserSettings"/>
<allow send_interface="org.freedesktop.NetworkManagerUserSettings"/>
<deny send_interface="org.freedesktop.NetworkManagerSetting.Secrets"/>
</policy>

Now the applet shows up for my regular user, the problem being that it doesn't connect to the wireless networks (only wired). Whenever I try to connect to wireless, nothing happens (the symbol doesn't change in any way, i.e. the green spheres should start circling); I am still able to succesfully connect to wireless using root. Does anyone know what the source of this issue may be? Thank you very much in advance.
Last edited by Ipozya (2011-01-20 04:49:55)

Solved: Had to install consolekit and add "ck-launch-session" to my .xinitrc file when starting fluxbox.
Edit: Please note that this also allowed me to remove the previous change to nm-applet.conf (no longer necessary)!
Last edited by Ipozya (2011-01-20 04:54:20)

[SOLVED] network-online.target is reached too early

Hi,
I want to start a systemd service once my wireless card is correctly set up (especially the wifi channel).
I think that the network-online is what I need.
So, I added the following lines at the beginning of my service file :
[Unit]
Description=...
Wants=network-online.target
After=network-online.target
However, it seems that the network-online.target is reached really early in the boot process, far before the discovery of the wireless card.
I don't know if it's important, but my wireless network is configured with netctl-auto.
I'm not very familiar with systemd, so I don't even understand how network-online.target is supposed to be notified that the network is online.
So, any help would be apreciated.
Thanks.
PS : I hope my approximative English is understandable enough.
Last edited by PHF (2013-10-28 02:51:43)

Lone_Wolf wrote:PHF, if i understand correctly you need to be sure the wireless connection is up and configured before the hostapd daemon runs ?
Yes, exactly.
Lone_Wolf wrote:a solution to achieve this might be to write a special command to check if the connection is up and add a service for it like the NetworkManager-wait-online.service .
This special command could be simple, like grepping the output op of ip addr show <interfacename> in a loop until it has a valid ip address.
Well, that's what I started to guess, without certitude : I need to manually order a waiting service before network-online.target.
I think my problem is solved now .
Meanwhile, I have found the ExecUpPost option for my netctl profiles.
It gives me the ability to execute a command once the connection is active.
So, I should be able to use it for unlocking my waiting service.
Thanks a lot for your help.

[SOLVED] Network restart before Arch can access internet via IPCop?

The Leopard machines on our LAN have working internet on boot, my Arch box does not?
Even though I have the IPCop server's IP in the Arch /etc/resolv.conf.head file, I still have to do a sudo /etc/rc.d/network restart before I can use the internet.
Does anyone know how I can solve this one?
Thanks for your time.
Last edited by handy (2008-12-13 13:41:04)

tomk wrote:Post your /etc/rc.conf. If '/etc/rc.d/network start' works but network-at-boot-time doesn't, that's where the error is.
As a workaround I've put /etc/rc.d/network start in my /etc/rc.local & now I don't have to type it manually.
tomk wrote:Incidentally, dhcpcd messages don't show up in dmesg - you should be looking in messages.log or everything.log.
I looked in all the logs that had been changed after a boot.
Here is my rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_AU.utf8"
HARDWARECLOCK="UTC"
TIMEZONE="Australia/Sydney"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=(net-pf-10 pcspkr) ## turns off ipv6 & pc speaker
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
MODULES=(sky2 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore fglrx)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
HOSTNAME="archtypical"
# 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
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
###lo="lo 127.0.0.1"
# eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
###INTERFACES=(lo eth0)
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.0.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-profiles
#NET_PROFILES=(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 @iptables @network @netfs @crond @alsa @portmap @sshd @transmission-daemon @stb-admin @fam @gpm)# @tor @privoxy # @hal - hal's out on account of worker
# End of file
Last edited by handy (2008-12-13 12:30:42)

[solved]Network fails to start sometimes

Hello!
I'm having a problem with my network. Sometimes it fails to start. Usually, a reboot solves this. Here is the error log:
[root@claudia log]# cat errors.log
Aug 6 03:16:28 claudia dhcpcd[3194]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
rc.conf:
# NETWORKING
HOSTNAME="claudia"
# 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
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo 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)
hosts:
[root@claudia log]# cat /etc/hosts
# /etc/hosts: static lookup table for host names
#<ip> <hostname> <hostname>
127.0.0.1 localhost.localdomain localhost claudia
# End of file
What should I do to solve this?
Thanks and regards,
Gustavo

I'd say it's because since the ethernet over firewire module is loaded too, it's counted as a network device too - and which one gets to be eth0 depends if the NIC or ethernet over firewire module is loaded first. There are many solutions to this:
1) If you don't need ethernet over firewire, keep it from being loaded by putting the module name (eth1394 I think) in MOD_BLACKLIST in /etc/rc.conf, like this:
MOD_BLACKLIST=(eth1394)
2) You can make both eth0 and eth1 (and perhaps other NICs too) start up together (I do this with my 2 NICs). To do that, make the rc.conf network section something like this:
lo="lo 127.0.0.1"
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo eth0 eth1)
Then you should put a @ in front of "network" ( @network ) in the DAEMONS array unless you like waiting for a NIC that won't start

[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

[SOLVED] Network interface enp2s0 no longer detected

Hello,
Yesterday after rebooting, right after Grub, systemd-fsck does its stuff (clearing blocks, etc...) then nothing.
After a quick research I've found that removing "quiet" from the Grub command line would allow more messages to be displayed, which was quite helpful.
This is in fact not a partition mounting problem, here is what I have:
[ OK ] Started Accounts Service.
[ TIME ] Time out waiting for device sys-subsytem-net-devices-enp2s0.device
[ DEPEND ] Dependency failed for dhcpcd on enp2s0.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
I obviously have a networking problem (and probably a "Graphical Interface" or Nvidia related thing problem), so I log in another console, and after doing ip link list, I only have the loopback listed, no enp2s0 or WiFi interface, for some reason they are no longer detected.
I've run the live version of Arch to mount and arch-chroot my partitions, not to mention my network interfaces are detected and I can upgrade things with pacman, I've tried to disable dhcpcd on enp2s0 to avoid the time out thing, and while I can say it does what it's supposed to do, it doesn't solve anything anyway since I'm still stuck at Reached target Graphical Interface. (and don't have any network access, to state the obvious).
I've even thought about a Kernel/Driver problem after an update, but I'm not sure, any idea or some log I can have a look at ?
Thank you for your time.
Last edited by Blaxar (2013-06-25 18:35:50)

Thank for the tip, I've just had a look at pacman.log:
[2013-06-23 11:07] [PACMAN] Running 'pacman -Syu'
[2013-06-23 11:07] [PACMAN] synchronizing package lists
[2013-06-23 11:08] [PACMAN] starting full system upgrade
[2013-06-23 11:10] [PACMAN] upgraded automake (1.13.2-1 -> 1.13.4-1)
[2013-06-23 11:10] [PACMAN] upgraded ca-certificates (20130119-2 -> 20130610-1)
[2013-06-23 11:10] [PACMAN] upgraded cantarell-fonts (0.0.12-1 -> 0.0.13-1)
[2013-06-23 11:10] [PACMAN] upgraded cloog (0.18.0-1 -> 0.18.0-2)
[2013-06-23 11:10] [PACMAN] upgraded libcups (1.6.2-2 -> 1.6.2-3)
[2013-06-23 11:10] [PACMAN] upgraded cups (1.6.2-2 -> 1.6.2-3)
[2013-06-23 11:10] [PACMAN] upgraded e2fsprogs (1.42.7-2 -> 1.42.8-1)
[2013-06-23 11:10] [PACMAN] upgraded glib2 (2.36.2-1 -> 2.36.3-2)
[2013-06-23 11:10] [PACMAN] upgraded xkeyboard-config (2.9-1 -> 2.9-2)
[2013-06-23 11:10] [PACMAN] upgraded iso-codes (3.41-1 -> 3.43-1)
[2013-06-23 11:10] [PACMAN] upgraded gnome-desktop (1:3.8.3-1 -> 1:3.8.3-2)
[2013-06-23 11:10] [PACMAN] upgraded gnome-icon-theme-symbolic (3.8.2.2-1 -> 3.8.3-1)
[2013-06-23 11:10] [PACMAN] upgraded gzip (1.5-3 -> 1.6-1)
[2013-06-23 11:10] [PACMAN] upgraded lib32-e2fsprogs (1.42.7-1 -> 1.42.8-1)
[2013-06-23 11:10] [PACMAN] upgraded lib32-glib2 (2.36.2-1 -> 2.36.3-2)
[2013-06-23 11:10] [PACMAN] upgraded lib32-krb5 (1.11.2-1 -> 1.11.3-1)
[2013-06-23 11:10] [PACMAN] upgraded libxi (1.7.1-1 -> 1.7.1-2)
[2013-06-23 11:10] [PACMAN] upgraded lib32-libxi (1.7.1-1 -> 1.7.1-2)
[2013-06-23 11:10] [PACMAN] upgraded mesa (9.1.3-1 -> 9.1.3-2)
[2013-06-23 11:10] [PACMAN] upgraded lib32-mesa (9.1.3-2 -> 9.1.3-3)
[2013-06-23 11:10] [PACMAN] upgraded libbsd (0.5.2-1 -> 0.5.2-2)
[2013-06-23 11:10] [PACMAN] upgraded libltdl (2.4.2-9 -> 2.4.2-10)
[2013-06-23 11:10] [PACMAN] upgraded libmbim (1.0.0-1 -> 1.2.0-1)
[2013-06-23 11:10] [PACMAN] upgraded libnautilus-extension (3.8.1-1 -> 3.8.2-1)
[2013-06-23 11:10] [PACMAN] upgraded libpeas (1.8.0-2 -> 1.8.1-1)
[2013-06-23 11:10] [PACMAN] upgraded libqmi (1.2.0-2 -> 1.4.0-1)
[2013-06-23 11:10] [PACMAN] upgraded libreoffice-uk (4.0.3-1 -> 4.0.4-1)
[2013-06-23 11:10] [PACMAN] upgraded libtool (2.4.2-9 -> 2.4.2-10)
[2013-06-23 11:10] [PACMAN] upgraded libusb-compat (0.1.4-2 -> 0.1.5-1)
[2013-06-23 11:10] [PACMAN] upgraded libxv (1.0.8-1 -> 1.0.9-1)
[2013-06-23 11:10] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-06-23 11:10] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Starting build: 3.9.7-1-ARCH
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Starting build: 3.9.7-1-ARCH
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-06-23 11:11] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-06-23 11:11] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-06-23 11:11] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-06-23 11:11] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-06-23 11:11] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-06-23 11:11] [PACMAN] upgraded linux (3.9.6-1 -> 3.9.7-1)
[2013-06-23 11:11] [PACMAN] upgraded logrotate (3.8.4-2 -> 3.8.5-1)
[2013-06-23 11:11] [PACMAN] upgraded nautilus (3.8.1-1 -> 3.8.2-1)
[2013-06-23 11:11] [PACMAN] upgraded nvidia (319.23-2 -> 319.23-3)
[2013-06-23 11:11] [PACMAN] upgraded openresolv (3.5.4-3 -> 3.5.5-1)
[2013-06-23 11:11] [PACMAN] upgraded pacman (4.1.1-1 -> 4.1.2-1)
[2013-06-23 11:11] [PACMAN] upgraded poppler (0.22.4-1 -> 0.22.5-1)
[2013-06-23 11:11] [PACMAN] upgraded poppler-glib (0.22.4-1 -> 0.22.5-1)
[2013-06-23 11:11] [PACMAN] upgraded ppp (2.4.5-7 -> 2.4.5-8)
[2013-06-23 11:13] [PACMAN] Running 'pacman -S libreoffice-fr'
[2013-06-23 11:13] [PACMAN] installed libreoffice-fr (4.0.4-1)
[2013-06-23 11:13] [PACMAN] Running 'pacman -S libreoffice'
[2013-06-23 11:15] [PACMAN] installed raptor (2.0.9-2)
[2013-06-23 11:15] [PACMAN] installed rasqal (1:0.9.30-1)
[2013-06-23 11:15] [PACMAN] installed redland (1:1.0.16-2)
[2013-06-23 11:15] [PACMAN] installed hyphen (2.8.6-1)
[2013-06-23 11:15] [PACMAN] installed boost-libs (1.53.0-2)
[2013-06-23 11:15] [PACMAN] installed clucene (2.3.3.4-6)
[2013-06-23 11:15] [ALPM-SCRIPTLET] * see https://wiki.archlinux.org/index.php/LibreOffice
[2013-06-23 11:15] [ALPM-SCRIPTLET] -------------------------------------------------------------------
[2013-06-23 11:15] [ALPM-SCRIPTLET] LibreOffice has been split into several packages:
[2013-06-23 11:15] [ALPM-SCRIPTLET] - libreoffice-common
[2013-06-23 11:15] [ALPM-SCRIPTLET] - libreoffice-{base,calc,draw,impress,math,writer} - frontend applications
[2013-06-23 11:15] [ALPM-SCRIPTLET] - libreoffice-{gnome,kde4} - desktop integration plugins
[2013-06-23 11:15] [ALPM-SCRIPTLET] - libreoffice-{sdk,sdk-doc} - add-on and doc for programming using
[2013-06-23 11:15] [ALPM-SCRIPTLET] the LibreOffice APIs and for creating
[2013-06-23 11:15] [ALPM-SCRIPTLET] extensions (UNO components).
[2013-06-23 11:15] [ALPM-SCRIPTLET] -------------------------------------------------------------------
[2013-06-23 11:15] [ALPM-SCRIPTLET] * you need to install at least one libreoffice-langpack
[2013-06-23 11:15] [ALPM-SCRIPTLET] * you may want to pacman -Ss libreoffice-extensions
[2013-06-23 11:15] [ALPM-SCRIPTLET] to see what additional extensions are prepared to install
[2013-06-23 11:15] [ALPM-SCRIPTLET] * it's recommended to install {hunspell,mythes,hyphen}-xx pkg
[2013-06-23 11:15] [ALPM-SCRIPTLET] for spell checking
[2013-06-23 11:15] [ALPM-SCRIPTLET] * make sure you have installed some ttf font (ttf-dejavu recommended)
[2013-06-23 11:15] [PACMAN] installed libreoffice-common (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed libreoffice-base (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed lpsolve (5.5.2.0-2)
[2013-06-23 11:15] [PACMAN] installed libreoffice-calc (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed libreoffice-draw (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed libreoffice-gnome (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed libreoffice-impress (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed libreoffice-math (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed libwpd (0.9.6-1)
[2013-06-23 11:15] [PACMAN] installed libwps (0.2.9-1)
[2013-06-23 11:15] [PACMAN] installed libreoffice-writer (4.0.4-1)
[2013-06-23 19:57] [PACMAN] Running 'pacman -S ssh-key'
[2013-06-23 23:01] [PACMAN] Running 'pacman -Syu'
[2013-06-23 23:01] [PACMAN] synchronizing package lists
--From the live CD from now on--
[2013-06-23 23:29] [PACMAN] Running 'pacman -Syu'
[2013-06-23 23:29] [PACMAN] synchronizing package lists
[2013-06-23 23:30] [PACMAN] starting full system upgrade
[2013-06-23 23:32] [PACMAN] removed grub-bios (2.00-2)
[2013-06-23 23:32] [PACMAN] removed grub-common (2.00-2)
[2013-06-23 23:32] [ALPM-SCRIPTLET] Generating grub.cfg.example config file...
[2013-06-23 23:32] [ALPM-SCRIPTLET] This may fail on some machines running a custom kernel.
[2013-06-23 23:32] [ALPM-SCRIPTLET] done.
[2013-06-23 23:32] [PACMAN] installed grub (2.00-1)
[2013-06-23 23:32] [PACMAN] upgraded lib32-libjpeg-turbo (1.3.0-2 -> 1.3.0-3)
[2013-06-23 23:32] [PACMAN] upgraded libgsf (1.14.26-1 -> 1.14.27-1)
[2013-06-23 23:32] [PACMAN] upgraded libquvi-scripts (0.4.15-1 -> 0.4.16-1)
Among all of that, I've spotted this:
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
Do you think this may explain something ?
Anyway, from lspci:
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 06)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 RAID bus controller: Intel Corporation 82801 SATA Controller [RAID mode] (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GT200 [GeForce GTX 260] (rev a1)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
03:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire Controller
04:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb (rev 04)
05:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)
and ip a:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
Last edited by Blaxar (2013-06-24 20:10:25)

[SOLVED] Network Manager cannot connect to wifi after suspend

Hi,
There appears to be similar threads recently, but they relate to no wifi at all. I did some updates today, and now if I suspend or hibernate, network manager cannot reconnect to my wifi. It will (after a while) ask me to authenticate, but still fails. Nothing works except a reboot where it connects without issue.
It was fine yesterday, has only started today. Here is my pacman log for today's updates:
[2012-04-11 17:13] upgraded libpciaccess (0.13-1 -> 0.13.1-1)
[2012-04-11 17:13] upgraded lib32-libpciaccess (0.13-1 -> 0.13.1-1)
[2012-04-11 17:13] upgraded mpd (0.16.7-3 -> 0.16.8-2)
[2012-04-11 17:13] upgraded xorg-server-common (1.12.0.901-1 -> 1.12.0.902-1)
[2012-04-11 17:13] upgraded xorg-server (1.12.0.901-1 -> 1.12.0.902-1)
[2012-04-11 17:13] upgraded xorg-server-devel (1.12.0.901-1 -> 1.12.0.902-1)
[2012-04-11 17:13] upgraded xorg-server-xephyr (1.12.0.901-1 -> 1.12.0.902-1)
Here is my messages log:
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Auto-activating connection 'Padfoot'.
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) starting connection 'Padfoot'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0/wireless): connection 'Padfoot' has security, and secrets exist. No new secrets needed.
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'ssid' value 'Padfoot'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'scan_ssid' value '1'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'psk' value '<omitted>'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: set interface ap_scan to 1
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Apr 11 18:38:29 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0/wireless): association took too long.
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0/wireless): asking for new secrets
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> No agents were available for this request.
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0) failed for access point (Padfoot)
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> Marking connection 'Padfoot' invalid.
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0) failed.
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): deactivating device (reason 'none') [0]
Last edited by Padfoot (2012-04-13 23:47:55)

heiko wrote:linux-3.3.2 is released on www.kernel.org and reverts the patch that introduced this problem.
For those using the arch repo kernel the next release will solve this issue. So I suggest waiting for this (no more than a few days) and use the LTS kernel in the meantime (or using a fixed ath9k module if already built).
Thanks for that heiko. I thought that would be the case, hence I just waited.
Will mark this as solved.
Cheers.

[SOLVED] Network won't work after install

Hi
I've installed arch on a lot of different computers without any trouble. But now I'm trying to install it on a intel mini-ITX board with an atom processor and integrated network. When setting up the network during the install it downloads and installs the packages perfectly fine, but when the installation is finished and I reboot into my new system the network wont work.
If I try to ping my gateway at 192.168.1.1 it just says that the network is unreachable.
The ifconfig shows the following for eth0:
Link encap:Ethernet HWAddr 00:27:0E:05:AC:47
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 overruns:0 frame:0
TX packets:0 errors:0 overruns:0 frame:0
collisions:0 TX bytes:0 (0.0 b)
Interrupt:28 Base address:0xe000
Any ideas what could be wrong?
Thanks
//Lasse
Last edited by Lazze (2010-02-10 14:57:30)

Sorry I've been away for a couple of days, but it's solved now it was something in the hosts file which weren't correct.
Thanks for the reply though!

[solved]network connection down after -Syu

Couple of days ago, I used "pacman -Syu" to upgrade, since then when I start arch I can't connect to internet, not via wireless nor wired. Upgrade included few packages which I can't remember and I don't know a way to learn. Only one I recognized was Chromium, which I believe, shouldn't affect anything at all. Any help please?
Last edited by sonay (2010-04-13 02:18:05)

Stupid of me that I didn't try kde network plasma (I wasn't using before). Anyway, network connection was somehow not enabled, so I enabled and the problem is solved.

[SOLVED] Network Shared Pacman Cache problems

Hi all,
I've got a couple of Arch servers and an Arch workstation that I'm working on; only the workstation has internet access and I need to keep the servers up to date and be able to install packages.
At the moment, the servers have the workstation's pacman package and cache directories mounted via SSHFS, but I've got problems with keys (pacman not being able to look up keys) and system upgrades. Nothing that I can't work around, but I'm thinking there must be a more "professional" way to get this done.
TL;DR - What's the best way to set up internetless Arch servers with a network pacman repo/cache?
Last edited by syngin (2012-04-03 07:00:21)

Yep, well capable of doing that which is why I'm asking - I can't do that without having to have difficult conversations with the security team here. And, no, I don't need to be told about the lack of security implications in doing this
As far as keys, I've just set the SigLevel to "Never" as I trust the packages on my workstation, but this all feels a little hinky.

(solved) Network Restart

I've recently discovered a new problem with arch...
The network daemon can't be restarted properly. Whenever I try a "/etc/rc.d/network restart" everything seems to be working fine but I don't have a functioning network afterwards. After a second restart, however, it suddenly works. First of all I thought it was a suspend issue but it also happens directly after a boot.
Don't know what could've caused it nor have I an idea how to solve it.
Help appreciated
Last edited by MrFuji (2007-06-20 18:11:22)

Yep, you're perfectly right, only starting my wireless interface (madwifi btw) but...
nope, that didn't work....
But here's something that might be useful...
First restart
[sven@svenlap ~]$ sudo /etc/rc.d/network stop
:: Stopping Network [DONE]
[sven@svenlap ~]$ sudo /etc/rc.d/network start
:: Starting Network [DONE]
[sven@svenlap ~]$ iwconfig ath0
ath0 IEEE 802.11g ESSID:"FeelGood" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: 00:12:BF:A5:62:A4
Bit Rate:54 Mb/s Tx-Power:16 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=35/94 Signal level=-58 dBm Noise level=-93 dBm
Rx invalid nwid:7556 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
[sven@svenlap ~]$ ifconfig ath0
ath0 Link encap:Ethernet HWaddr 00:19:7D:33:F5:53
inet6 addr: fe80::219:7dff:fe33:f553/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:356 errors:0 dropped:0 overruns:0 frame:0
TX packets:194 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:115759 (113.0 Kb) TX bytes:48925 (47.7 Kb)
And the second one:
[sven@svenlap ~]$ sudo /etc/rc.d/network stop
:: Stopping Network [DONE]
[sven@svenlap ~]$ sudo /etc/rc.d/network start
:: Starting Network [DONE]
[sven@svenlap ~]$ iwconfig ath0
ath0 IEEE 802.11g ESSID:"FeelGood" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: 00:12:BF:A5:62:A4
Bit Rate:54 Mb/s Tx-Power:16 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=32/94 Signal level=-61 dBm Noise level=-93 dBm
Rx invalid nwid:9185 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
[sven@svenlap ~]$ ifconfig ath0
ath0 Link encap:Ethernet HWaddr 00:19:7D:33:F5:53
inet addr:192.168.2.101 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::219:7dff:fe33:f553/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:410 errors:0 dropped:0 overruns:0 frame:0
TX packets:204 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:118887 (116.1 Kb) TX bytes:50183 (49.0 Kb)
There doesn't seem to be something wrong with the iwconfig part but obviously I don't have an IP address after the first restart.
Then maybe misfit is right and it's still something wrong with the dhcpd variable?
edit: It has obviously something to do with dhcpcd because if I restart the network after a "killall dhcpcd" everything works fine....
Last edited by MrFuji (2007-06-20 13:47:13)

[solved] network

Hi all,
I've been trying to set network working on my desktop but haven't been succeeded till now..
I noticed a weird situation (at least to me)
if I do ping google: ping -c 3 www.google.com
I'll get in the final statistics time = 11149ms
but if I do ping google as : ping -c 3 209.85.229.147
I'll get time = 2003 ms
>.< hope anyone knows what's wrong so I can fix this
tks in advance for your time
Last edited by babalu_pt (2010-04-20 22:07:38)

First of all I wanna say tks for all that gave me some replies >.<
apparently I got this working
steps I've done ..
1st remove wicd and reactivate network
2nd setup static IP
3nd deactivate resolv.conf update
4th set nameservers manually
this is my actual config:
rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# HARDWARE
MODULES=(!net-pf-10 !snd_pcsp !pcspkr loop sis900 !mii !ppp_generic !slhc !soundcore)
# one of the 1st things I've done ( heading to solve the problem ) was only load the module I wanted to use
# so I ran hwdetect --show-net to see what it'd show (mii ppp_generic sis900 slhc)
# so I loaded the sis900 and discarded all others... dunno if it has any influence but I did :)
# have I done the correct thing?
# NETWORKING
HOSTNAME="arch"
#Static IP
eth0="eth0 10.10.10.171 netmask 255.255.255.0 broadcast 10.10.10.255"
INTERFACES=(eth0 !wlan0)
gateway="default gw 10.10.10.1"
ROUTES=(gateway)
# DAEMONS
DAEMONS=(network dhcdbd !networkmanager @syslog-ng gpm netfs @crond dbus hal oss !wicd)
# here I did discarded wicd and set back network :)
I only pasted the things that I've changed to set up network.. all others erased them
then I disabled the nameserver refresh at /etc/dhcpd.conf
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Inform the DHCP server of our hostname for DDNS.
hostname
# To share the DHCP lease across OSX and Windows a ClientID is needed.
# Enabling this may get a different lease than the kernel DHCP client.
# Some upstream DHCP servers may also require a ClientID, such as FRITZ!Box.
#clientid
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
noipv4ll
nohook resolv.conf
I just added this last line
then I set up nameservers manualy at /etc/resolv.conf
# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
nameserver 212.55.154.174
nameserver 212.55.154.190
# /etc/resolv.conf.tail can replace this line
this way it's all working apparently fine
if there is any thing that I've done worng pls correct me.. so I won't have troubles in the future
ps. I guess all I needed to do was to set the nohook at dhcpd.conf and set the nameservers manualy... but I feel ok with the static ip tougth I had to try till make it to work
Last edited by babalu_pt (2010-04-20 22:33:40)

[SOLVED] network is not detected r8169 module is not loaded

Hey there,
I have problems to get my archlinux server running, it has no network.
It's a server at kimsufi so I only can chroot in the new installation.
It looks like the module 'r8169' isn't loaded at start, so it has no network.
After adding '/etc/modules-load.d/r8169.conf' with 'r8169' inside (w/o quotes) the journalctl says:
systemd-modules-load[92]: Failed to lookup alias 'r8169': Function not implemented
The installation is up-to-date, newest kernel.
I hope you have some ideas how to get that module loaded.
Greetings
edit: I tried it just now again and it worked atm. If network will work completely, I will mark this thread as solved.
Last edited by lookingaty (2014-02-14 21:19:43)

I'm sorry that I opened the thread.
I had built myself a kernel with kdump and had set debug and loglevel=7 parameters.
Either one of the parameter was bad or my buildprocess was bad.
Now (with the original kernel) I don't get that error and the module is loading fine.
I have (after about a month) the server up and running.
At least I got some new experience.
Last edited by lookingaty (2014-02-14 21:23:48)

[SOLVED] Network Difficulties

Similar Messages

Maybe you are looking for