Netcfg: net-auto-wireless missing

Maybe I just don't know the actual reason, but can someone tell me why netcfg installs net-auto-wired into /usr/bin but not net-auto-wireless?  To get it to work I've been having to copy it into /usr/bin.  Is there something else I should be doing?

http://mailman.archlinux.org/pipermail/ … 15241.html
Last edited by skottish (2011-08-28 19:39:24)

Similar Messages

  • Netcfg net-auto-wireless

    I am having a problem with netcfg's net-auto-wireless daemon. I am starting the daemon from my daemons array in /etc/rc.conf when I boot. However, some of my wireless network configs in /etc/network.d are symlinks to files on a encrypted drive which is only mounted after I login. So at the time net-auto-wireless is started those symlinks are not valid.
    I expected that net-auto-wireless would automatically "recover" after login and connect to a wireless network using the now valid symlinked configs, but this is not the case. net-auto-wireless will not connect at sit there doing nothing.
    Is there a way to make net-auto-wireless connect to a wireless without having to restart the daemon?
    Thanks,
    Daniel
    Last edited by daba (2012-07-15 16:48:01)

    If you bring up the netcfg connection manually/in a login script after that mount, maybe the daemon resumes watching by itself.

  • Net-auto-wireless priorities?

    Hey there,
    I've got an annoying problem with netcfg/net-auto-wireless and hope you can help me out.
    Basically, I have a wireless network at home, but there is also the university network. I use a wireless-wpa config for my home network and wireless-wpa-configsection for the university network (since it needs fancy stuff like certificates and such ).
    The problem is that net-auto-wireless seems to favor the university network, although the signal strength is much stronger for my home network. I do not know why this happens - maybe wireless-wpa-configsection entries have a higher priority than wireless-wpa? I would really appreciate it however if anyone could tell me how to get net-auto-wireless to use my home network first when it is available, and only use the university network when the home network isn't there. Any way to do this?
    Cheers,
    Natanji

    Hey there,
    I've got an annoying problem with netcfg/net-auto-wireless and hope you can help me out.
    Basically, I have a wireless network at home, but there is also the university network. I use a wireless-wpa config for my home network and wireless-wpa-configsection for the university network (since it needs fancy stuff like certificates and such ).
    The problem is that net-auto-wireless seems to favor the university network, although the signal strength is much stronger for my home network. I do not know why this happens - maybe wireless-wpa-configsection entries have a higher priority than wireless-wpa? I would really appreciate it however if anyone could tell me how to get net-auto-wireless to use my home network first when it is available, and only use the university network when the home network isn't there. Any way to do this?
    Cheers,
    Natanji

  • Net-auto-wireless isn't really doing anything

    I've got netcfg installed and I'm trying to use it for my wifi configuration on my laptop which has an ath9k wireless chip.
    I've got my profiles (WPA personal) setup just fine, when I do netcfg my.profile.name it brings it up and it works. However if my wireless drops for whatever reason, or I come to work, I always have to manually do "netcfg profile".
    In my rc.conf I have nothing in INTERFACES (only have wlan0 on this machine), I have WIRELESS_INTERFACE defined as wlan0, I have two profiles in NETWORKS, and I have "syslog-ng hal net-auto-wireless netfs crond" in my DAEMONS list.
    Can anyone see anything that I'm doing wrong? How does net-auto-wireless actually work?

    Okay I can't get it to automatically connect neither to wired no wireless network.
    ifplugd at least is trying to connect to networks, I can see in /var/log/everything that but wpa_actiond simply sits there silently and does nothing.
    When run manually, either via rc.d/net-auto-wireless or directly, it connects to a wireless access point immediately. No problem here.
    So, basically I had gone through the following scenario today. Went to work office, plugged in ethernet cable, ifplugd tried to connect to any of the networks specified in the profiles but failed to for whatever reason. No meaningful explanation. All it said was this:
    Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: ifplugd 0.28 initializing.
    Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: Using interface eth0/00:13:77:49:00:BE with driver <8139too> (version: 0.9.28)
    Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: Using detection mode: SIOCETHTOOL
    Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: Initialization complete, link beat detected.
    Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: Executing '/etc/ifplugd/netcfg.action eth0 up'.
    Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: client: up
    Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: client: loadin ho-eth
    Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: :: ho-eth up [BUSY] > DHCP IP lease attempt failed.
    Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: [FAIL]
    Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin pdp-wifi
    Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin st-mt
    Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin home-wifi
    Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin sc-eth
    Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin st-eth
    Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin st-wifi
    Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin uncle-wifi
    Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: Program execution failed, return value is 1.
    Jan 27 09:47:39 localhost ifplugd(eth0)[27597]: Executing '/etc/ifplugd/netcfg.action eth0 down'.
    Jan 27 09:47:39 localhost ifplugd(eth0)[27597]: Program execution failed, return value is 1.
    Jan 27 09:47:39 localhost ifplugd(eth0)[27597]: Exiting.
    So, I had to do netcfg -u $PROFILE to set up network connection manually. Then I went back home, where I use wireless ap to connect to the home LAN, I saw ifplugd detect that ethernet had been down so it properly unconfigured eth0, again /var/log/everything clearly stated that
    Jan 27 14:03:00 localhost ifplugd(eth0)[28240]: Link beat lost.
    Jan 27 14:03:11 localhost ifplugd(eth0)[28240]: Executing '/etc/ifplugd/netcfg.action eth0 down'.
    Jan 27 14:03:11 localhost ifplugd(eth0)[28240]: Program execution failed, return value is 1.
    but nothing was happening for wireless interface at all. This was registered in the log when I got bored with netcfg/wpa_actiond not doing my job for me so I ran /etc/rc.d/net-auto-wireless restart which configured wireless network connection:
    Jan 27 14:12:59 localhost wpa_actiond[4401]: Starting wpa_actiond session for interface 'wlan0'
    Jan 27 14:13:00 localhost wpa_actiond[4401]: Interface 'wlan0' connected to network '$ESSID'
    I think my configuration is correct but well I could've missed something of course. So, to save us time:
    - all profiles are in /etc/network.d/. one of these looks like this:
    % cat /etc/network.d/home-wifi
    CONNECTION='wireless'
    DESCRIPTION='A simple WPA encrypted wireless connection using a static IP'
    INTERFACE='wlan0'
    SECURITY='wpa'
    ESSID='$ESSID'
    KEY='$KEY'
    IP='static'
    IPCFG=('addr add dev wlan0 $CIDR/IP brd +' 'route add default via $IP')
    DNS=('$IP')
    POST_UP="sh /home/$USER/scripts/netcfg-home-post"
    - /etc/rc.conf:
    # net-auto-wireless support
    WIRELESS_INTERFACE="wlan0"
    WIRED_INTERFACE="eth0"
    DAEMONS=(... !network @net-profiles net-auto-wireless net-auto-wired ...)
    no ROUTES, no INTERFACES. Clean and neat. No syntax errors.
    Software installed:
    ifplugd 0.28-7
    wpa_actiond 1.1-1
    netcfg 2.5.4-1
    So far the problem is that ifplugd can't connect to a wired network, but at least it attempts to, while wpa_actiond does nothing at all.
    I really want my laptop to do this automatically. It's like... you know... 2011 already! Computers must do this stuff xD

  • Wpa_actiond & net-auto-wireless config ?

    Hi,
    as documentation of roaming network configuration is rather sparse I'm looking for an advice here.
    How can I set to use my roaming networks info stored in /etc/wpa_supplicant/wpa_supplicant.conf ? WPA_CONF option from /etc/network.d/interfaces/wlan0 is ignroed and wpa_supplicant is started with an empty configuration. In other words where does net-auto-wireless look for a configuration ?
    My wireless card Broadcom BCM4313 requires to be unblocked with rfkill on two devices (phy0 and wireless). May it be done with just netcfg options as RFKILL and RFKILL_NAME is probably parsed only once ? With PRE_UP and POST_DOWN actions ?
    Thanks.
    David

    Touching wpa supplicant configuration isn't needed. You just need to set profiles for all networks you want to connect to in /etc/conf.d/netcfg/ (check examples file in that dir). Then you specify wireless interface in /etc/conf.d/netcfg.
    Do not set AUTO_PROFILES var if you want all of the profiles to be probed. And that should do it.
    I don't think you need to use PRE and POST vars because net-auto should take care of rfkill automaticaly if it's configured in /etc/network.d/interfaces/wlan0 (I believe you have already done that).

  • Net-auto-wireless roaming with suspend

    I didn't really know how to name this thread, but I think the gist of it is up there.
    I bring my laptop to school and back every day, and use different wireless networks in each place.
    I use net-auto-wireless (n-a-w) to connect on boot, but after suspending, and resuming in the new location I have to manually restart the daemon to get a connection back. I'm not sure if n-a-w is supposed to handle this use case, or if there is a better way to handle it.
    Any tips?

    Those of you have net-auto-wireless, please stop saying "me too" and provide relevant logs from wpa_* stuff. When you suspend, wpa_supplicant deauthenticates -- what is the reaction of wpa_actiond? For example:
    dhcpcd[852]: wlan0: removing interface
    wpa_actiond[674]: Interface 'wlan0' disconnected from network 'lsusecure'
    After you wakeup the machine in a different location, is there a profile corresponding to your previous network in /run/network/profiles/?
    @tomk:
    I used net-profiles until very recently (when switched to net-auto-wireless) and suspend worked out of the box... you should probably investigate your problem further.
    Also, putting a script into /etc/pm/sleep.d which stops net-auto-wireless will cure the suspend problem...

  • Netcfg v2.5.2 - note: change in auto wireless config

    This release brings a completely new auto wireless/wired configuration. The old net-auto is deprecated and no longer included. There are also some very minor configuration changes that may affect a few people.
    Move to new auto-wireless/wired
    The new automatic connection has proper roaming support and will prove more reliable than the old setup - particularly with more complicated wireless configurations. To migrate to the new automatic wireless setup:
    1. pacman -S core/wpa_actiond
    2. Set WIRELESS_INTERFACE="" to your wireless interface in /etc/rc.conf.
    For example WIRELESS_INTERFACE="wlan0"
    3. Add net-auto-wireless to your DAEMONS=() array.
    Note: wpa-config profiles do not work with this, convert them to wpa-configsection profiles. An example is included in
    /etc/network.d/examples/
    The new auto-wired uses similar configuration - follow the above instructions except use the net-auto-wired daemon, and WIRED_INTERFACE configuration option.
    New features:
    - net-auto-wireless/wpa_actiond - Real wireless roaming/auto connection. Based on same principle as autowifi. Requires optional dependency: wpa_actiond
    - net-auto-wired - automatic ethernet configuration. Requires optional dependency: ifplugd
    - Interface configurations - set options for all profiles using an interface
    - Output hooks
    - Internal cleanup & improvement
    Internal changes:
    - Uses wpa_supplicant for all wireless configuration by default, including wep/none security. This adds improves support for most and should improve reliability.
      - Uses iproute by default for all static configuration. net_tools which contains ifconfig is effectively obsolete and hasnt seen a release for over 8 years. The 'ethernet-iproute' and 'ethernet' connection types have been merged together to simply 'ethernet'. All options are still supported and existing configurations will continue to work for both types. A symlink has been made to ensure that profiles using 'ethernet-iproute' will continue to function.
    Changes in configuration syntax
    - net-auto and AUTO_NETWORKS is now deprecated in favour of net-auto-wireless/net-auto-wired.
    - wireless: If you were previously specifying the wpa_supplicant driver in WPA_OPTS, you now need to specify it in WPA_DRIVER.
    - wireless: iwconfig based configuration for wep/none can be used by changing to wep-old or none-old. This should not be necessary and is left in place only for the possibility of very old drivers that do not
    support wpa_supplicant.
    - ethernet-iproute: As 'ethernet' is now iproute based, those using 'ethernet-iproute' can revert the name. There is a symlink in place, so existing configurations of either name will continue to function
    regardless.
    - wireless-dbus: Unsupported. The wpa_supplicant dbus interface isn't particularly well documented and it doesn't fit well into the netcfg codebase. There is a symlink in place so that configurations using wireless-dbus will continue to function using the 'wireless' connection scripts.
    Download:
    netcfg 2.5.2 is in [core].
    Source: ftp://ftp.archlinux.org/other/netcfg/ne … 5.2.tar.gz
    PKGBUILD: In subversion
    Documentation:
    http://wiki.archlinux.org/index.php/Network_Profiles
    Contributors:
    I had a few big contributors to this release:
    Jim Pryor: Many internal changes and improvements
    Thomas Bächler: wpa_actiond based auto roaming/connection
    Thanks guys!
    Future Plans:
    * Complete non-Arch support
    * Redo rfkill using the 'rfkill' tool in the repos
    * Fix bugs
    Bugs:
    On the bug tracker as always.
    Last edited by iphitus (2010-02-18 11:22:41)

    I continued to have difficulty connecting to my default wireless network, but I eventually figured out why.  I seem to recall netcfg used to not care if a POSTUP command failed.  I read somewhere that now it does.
    So once I got that taken care of, I experimented with net-auto-wireless.  It fails for me with no error message.
    Being a bit of a tinkerer, I looked into the net-auto-wireless script.  I found this line...
    /usr/bin/netcfg-wpa_actiond "${WIRELESS_INTERFACE}" >/dev/null
    ...Removed the >/dev/null, and ran it again.
    $ sudo /etc/rc.d/net-auto-wireless start
    :: Starting netcfg auto-wireless mode for interface wlan0 [BUSY]
    eth-xover
    eth-hc
    wifi-home
    wifi-rounds
    wifi-rollingst
    wifi-kevin
    eth-dhcp
    Line 12: WPA-PSK accepted for key management, but no PSK configured.
    Line 12: failed to parse network block.
    Line 22: WPA-PSK accepted for key management, but no PSK configured.
    Line 22: failed to parse network block.
    Failed to read or parse configuration '/tmp/wpa.wlan0/wpa.conf'.
    [FAIL]
    ...And now that I think about it,  I bet it's because I didn't set security="none" in the open network profiles.
    ...Yep, that was it.
    Last edited by aaaantoine (2010-02-21 01:03:02)

  • [Solved] net-auto-wired and ifplugd failing to work

    Having installed Arch successfully on one machine I then move to another, so I've just got a fresh install with nothing else.
    Using netcfg and ifplugd to manage network interfaces (trying to, did same process and it worked okay on other computer), however systemctl status of net-wired-auto gives:
    net-auto-wired.service - Provides automatic netcfg wired connection
    Loaded: loaded (/usr/lib/systemd/system/net-auto-wired.service; enabled)
    Active: active (running) since Wed 2013-03-13 14:00:22 GMT; 12min ago
    Main PID: 259 (ifplugd)
    CGroup: name=systemd:/system/net-auto-wired.service
    └─259 /usr/bin/ifplugd -i enp7s0 -r /etc/ifplugd/netcfg.action -fIns
    Mar 13 14:00:22 alexpc systemd[1]: Started Provides automatic netcfg wired connection.
    Mar 13 14:00:22 alexpc ifplugd[259]: ifplugd 0.28 initializing.
    Mar 13 14:00:22 alexpc ifplugd[259]: Using interface enp7s0/8C:89:A5:37:9F:51 with driver <r8169> (version: 2...-NAPI)
    Mar 13 14:00:22 alexpc ifplugd[259]: Using detection mode: SIOCETHTOOL
    Mar 13 14:00:22 alexpc ifplugd[259]: Initialization complete, link beat not detected.
    Mar 13 14:00:25 alexpc ifplugd[259]: Link beat detected.
    Mar 13 14:00:26 alexpc ifplugd[259]: Executing '/etc/ifplugd/netcfg.action enp7s0 up'.
    Mar 13 14:00:26 alexpc ifplugd[259]: client: up
    Mar 13 14:00:26 alexpc ifplugd[259]: Program execution failed, return value is 1.
    I've checked many times and interface is enp7s0 (only one anyway and no wireless)
    Running
    dhcpcd enp7s0
    does work fine and connects me to the network. Also realtek driver (r8269) is being loaded (obv given I can connect to network)
    Contents of /etc/conf.d/netcfg
    # Enable these netcfg profiles at boot time.
    # - prefix an entry with a '@' to background its startup
    # - set to 'last' to restore the profiles running at the last shutdown
    # - set to 'menu' to present a menu (requires the dialog package)
    # Network profiles are found in /etc/network.d
    NETWORKS=(last)
    # Specify the name of your wired interface for net-auto-wired
    WIRED_INTERFACE="enp7s0"
    # Specify the name of your wireless interface for net-auto-wireless
    WIRELESS_INTERFACE="wlan0"
    # Array of profiles that may be started by net-auto-wireless.
    # When not specified, all wireless profiles are considered.
    #AUTO_PROFILES=("profile1" "profile2")
    I can use dhcpcd service and it works fine - but it would be nice to use ifplugd/netcfg.
    Not really sure what else to try...
    Thanks.
    Last edited by alexjj (2013-03-15 12:15:46)

    I think you may need to also put a config file into /etc/network.d/ - you can copy one of the sample files there and adapt it to your situation.
    Also you have to set the correct interface in /etc/ifplugd/ifplugd.conf
    You will also need:
    systemctl start net-auto-wired
    systemctl enable net-auto-wired
    Hope this helps.
    Last edited by mcloaked (2013-03-13 18:09:55)

  • Order of profiles for netcfg-auto-wireless

    Hi fellow Archers,
    I'm running Arch Linux with netcfg 2.5.4 on my laptop, and have several wireless network profiles set up. Amongst other things, I have three profiles for my University WLAN. The reason for this is that the University offers three different wireless networks, one for Staff, one for Students and one unencrypted with a password-protected HTTP proxy. I have access to all three, but I want netcfg to attempt to connect to the networks in that order.
    I have tried to name the profiles as such:
    UniversityAStaff
    UniversityBStudent
    UniversityCOpen
    But that doesn't seem to make any difference; it still connects to the Student network by default.
    Is there any way of setting the priority of the wireless networks that netcfg-auto-wireless tries to connect to?
    Jon

    if you make your profiles like in /etc/network.d/examples/wireless-wpa-configsection you can put a priority falue in the wpa_supplicant section this should do the trick
    edit because of typo
    Last edited by parintachin (2010-03-08 14:48:44)

  • [Solved] NFS export at boot and net-auto-wired

    Hello Guys,
    I have a problem with my fileserver. Previously dhcp was enabled through systemctl enable dhcpd@eth0 and everything worked fine. I changed the network to be configured using net-auto-wired, because it seemed a reasonable thing to do and because it allows for a fallback-ip-address in case dhcp fails. Now the problem is that many daemons are (at boot) started before the net is up and so don't work properly, especially nfsd, because exportfs can't resolve the names of the allowed client computers.
    Mär 18 11:32:22 bigbrain systemd[1]: Started NFS server.
    Mär 18 11:32:22 bigbrain systemd[1]: Starting NFS Mount Daemon...
    Mär 18 11:32:22 bigbrain systemd[1]: Starting NFSv4 ID-name mapping daemon...
    Mär 18 11:32:23 bigbrain systemd[1]: Started NFSv4 ID-name mapping daemon.
    Mär 18 11:32:24 bigbrain systemd[1]: Started Samba SMB/CIFS server.
    Mär 18 11:32:24 bigbrain systemd[1]: Started NFS Mount Daemon.
    Mär 18 11:32:28 bigbrain kernel: Installing knfsd (copyright (C) 1996 [email protected]).
    Mär 18 11:32:28 bigbrain tunnel-httpd.sh[321]: ssh: Could not resolve hostname example.com: Name or service not known
    Mär 18 11:32:28 bigbrain tunnel-httpd.sh[321]: ssh: Could not resolve hostname example.com: Name or service not known
    Mär 18 11:32:28 bigbrain ifplugd[318]: Link beat detected.
    Mär 18 11:32:28 bigbrain ifplugd[318]: Executing '/etc/ifplugd/netcfg.action eth0 up'.
    Mär 18 11:32:28 bigbrain ifplugd[318]: client: up
    Mär 18 11:32:28 bigbrain ifplugd[318]: client: loading stw-wh
    Mär 18 11:32:28 bigbrain ifplugd[318]: client: loading dhcp
    Mär 18 11:32:28 bigbrain kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
    Mär 18 11:32:28 bigbrain dhcpcd[397]: version 5.6.7 starting
    Mär 18 11:32:28 bigbrain kernel: NFSD: starting 90-second grace period
    Mär 18 11:32:28 bigbrain exportfs[354]: exportfs: Failed to resolve some-domain.example.com
    Mär 18 11:32:28 bigbrain exportfs[354]: exportfs: Failed to resolve some-domain.example.com
    Mär 18 11:32:28 bigbrain exportfs[354]: exportfs: Failed to resolve some-other-domain.example.com
    Mär 18 11:32:28 bigbrain exportfs[354]: exportfs: Failed to resolve some-other-domain.example.com
    Mär 18 11:32:28 bigbrain exportfs[354]: exportfs: Failed to resolve some-domain.example.com
    Mär 18 11:32:28 bigbrain exportfs[354]: exportfs: Failed to resolve some-domain.example.com
    Mär 18 11:32:28 bigbrain exportfs[354]: exportfs: Failed to resolve some-other-domain.example.com
    Mär 18 11:32:28 bigbrain exportfs[354]: exportfs: Failed to resolve some-other-domain.example.com
    Mär 18 11:32:28 bigbrain kernel: r8169 0000:04:00.0 eth0: link up
    Mär 18 11:32:28 bigbrain kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    Mär 18 11:32:28 bigbrain systemd[1]: PID file /run/httpd/httpd.pid not readable (yet?) after start.
    Mär 18 11:32:29 bigbrain dhcpcd[397]: eth0: sending IPv6 Router Solicitation
    Mär 18 11:32:29 bigbrain dhcpcd[397]: eth0: broadcasting for a lease
    Mär 18 11:32:30 bigbrain dhcpcd[397]: eth0: offered 10.42.19.195 from 141.35.0.13
    Mär 18 11:32:30 bigbrain dhcpcd[397]: eth0: acknowledged 10.42.19.195 from 141.35.0.13
    Mär 18 11:32:30 bigbrain dhcpcd[397]: eth0: checking for 10.42.19.195
    Mär 18 11:32:30 bigbrain ntpd_intres[341]: host name not found: 0.pool.ntp.org
    Mär 18 11:32:30 bigbrain ntpd_intres[341]: host name not found: 1.pool.ntp.org
    Mär 18 11:32:30 bigbrain ntpd_intres[341]: host name not found: 2.pool.ntp.org
    Mär 18 11:32:32 bigbrain ntpd_intres[341]: host name not found: 0.pool.ntp.org
    Mär 18 11:32:32 bigbrain ntpd_intres[341]: host name not found: 1.pool.ntp.org
    Mär 18 11:32:32 bigbrain ntpd_intres[341]: host name not found: 2.pool.ntp.org
    Mär 18 11:32:33 bigbrain dhcpcd[397]: eth0: sending IPv6 Router Solicitation
    Mär 18 11:32:34 bigbrain dhcpcd[397]: eth0: leased 10.42.19.195 for 1800 seconds
    Mär 18 11:32:35 bigbrain dhcpcd[397]: forked to background, child pid 446
    Mär 18 11:32:35 bigbrain ifplugd[318]: client: :: dhcp up [done]
    Mär 18 11:32:35 bigbrain ifplugd[318]: Program executed successfully.
    Mär 18 11:32:36 bigbrain ntpd[336]: Listen normally on 5 eth0 10.42.19.195 UDP 123
    Mär 18 11:32:36 bigbrain ntpd[336]: peers refreshed
    Mär 18 11:32:36 bigbrain ntpd[336]: new interface(s) found: waking up resolver
    Mär 18 11:32:37 bigbrain dhcpcd[446]: eth0: sending IPv6 Router Solicitation
    Mär 18 11:32:38 bigbrain ntpd_intres[341]: DNS 0.pool.ntp.org -> 83.137.98.96
    Mär 18 11:32:38 bigbrain ntpd_intres[341]: DNS 1.pool.ntp.org -> 176.31.45.66
    Mär 18 11:32:38 bigbrain ntpd_intres[341]: DNS 2.pool.ntp.org -> 192.53.103.108
    what can I do to fix this?
    TIA
    Sunday
    Last edited by Sunday87 (2013-03-19 23:08:56)

    For future reference:
    net-auto-wired doesn't Wants=network.target at any time (neither when started nor when a connection is made) as does dhcpcd.service (so indeed i had the same problem already before i switched to net-auto-wired but i guess i didn't notice it). now i'm using netcfg.service which actually Wants=network.target and starts Before=network.target so everything works fine. The only thing that is missing is a fallback static ip in case the dhcp does not respond, but that is another question so i will mark this solved.

  • [solved] ifplugd; systemd, net-auto-wired: annoying beep

    Hello everyone!
    I experience annoying pc speaker beeps whenever the net-auto-wired service is getting started or stopped, e.g. on every boot or shutdown.
    I've already tried various ways to mute the pc speaker:
    "xset -b" in ~/.xinitrc
    blacklisting pcspkr module
    "setterm -blength 0" in /etc/profile
    It doesn't work.
    The following log corresponds to stopping and then re-starting the net-auto-wired service after having booted the system.
    Nov 24 11:34:19 virtus sudo[2298]: freddy : TTY=pts/0 ; PWD=/home/freddy ; USER=root ; COMMAND=/usr/bin/systemctl stop net-auto-wired.service
    Nov 24 11:34:19 virtus sudo[2298]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Nov 24 11:34:19 virtus systemd[1]: Stopping Provides automatic netcfg wired connection...
    Nov 24 11:34:19 virtus dhcpcd[2320]: sending signal 1 to pid 1819
    Nov 24 11:34:19 virtus dhcpcd[1819]: received SIGHUP, releasing
    Nov 24 11:34:19 virtus dhcpcd[1819]: eth0: releasing lease of 85.170.167.0
    Nov 24 11:34:19 virtus dhcpcd[2320]: waiting for pid 1819 to exit
    Nov 24 11:34:19 virtus dhcpcd[1819]: eth0: removing interface
    Nov 24 11:34:19 virtus netcfg[2301]: :: ethernet-dhcp down [done]
    Nov 24 11:34:20 virtus kernel: e1000e 0000:00:19.0: irq 47 for MSI/MSI-X
    Nov 24 11:34:20 virtus ifplugd[1675]: Link beat lost.
    Nov 24 11:34:20 virtus kernel: e1000e 0000:00:19.0: irq 47 for MSI/MSI-X
    Nov 24 11:34:20 virtus ifplugd[1675]: Executing '/etc/ifplugd/netcfg.action eth0 down'.
    Nov 24 11:34:20 virtus ifplugd[1675]: Program execution failed, return value is 1.
    Nov 24 11:34:20 virtus ifplugd[1675]: Exiting.
    Nov 24 11:34:20 virtus systemd[1]: Stopped Provides automatic netcfg wired connection.
    Nov 24 11:34:20 virtus sudo[2298]: pam_unix(sudo:session): session closed for user root
    Nov 24 11:34:21 virtus kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
    Nov 24 11:34:21 virtus kernel: e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO
    Nov 24 11:34:23 virtus sudo[2365]: freddy : TTY=pts/0 ; PWD=/home/freddy ; USER=root ; COMMAND=/usr/bin/journalctl
    Nov 24 11:34:23 virtus sudo[2365]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Nov 24 11:35:58 virtus sudo[2365]: pam_unix(sudo:session): session closed for user root
    Nov 24 11:36:03 virtus sudo[2469]: freddy : TTY=pts/0 ; PWD=/home/freddy ; USER=root ; COMMAND=/usr/bin/systemctl start net-auto-wired.service
    Nov 24 11:36:03 virtus sudo[2469]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Nov 24 11:36:03 virtus systemd[1]: Starting Provides automatic netcfg wired connection...
    Nov 24 11:36:03 virtus systemd[1]: Started Provides automatic netcfg wired connection.
    Nov 24 11:36:03 virtus sudo[2469]: pam_unix(sudo:session): session closed for user root
    Nov 24 11:36:03 virtus ifplugd[2472]: ifplugd 0.28 initializing.
    Nov 24 11:36:03 virtus ifplugd[2472]: Using interface eth0/00:1C:25:9F:3E:24 with driver <e1000e> (version: 2.0.0-k)
    Nov 24 11:36:03 virtus ifplugd[2472]: Using detection mode: SIOCETHTOOL
    Nov 24 11:36:03 virtus ifplugd[2472]: Initialization complete, link beat detected.
    Nov 24 11:36:03 virtus ifplugd[2472]: Executing '/etc/ifplugd/netcfg.action eth0 up'.
    Nov 24 11:36:03 virtus ifplugd[2472]: client: up
    Nov 24 11:36:03 virtus ifplugd[2472]: client: loading wireless-profile1
    Nov 24 11:36:03 virtus ifplugd[2472]: client: loading wireless-profile2
    Nov 24 11:36:03 virtus ifplugd[2472]: client: loading ethernet-dhcp
    Nov 24 11:36:03 virtus dhcpcd[2505]: version 5.6.3 starting
    Nov 24 11:36:03 virtus dhcpcd[2505]: all: configured as a router, not a host
    Nov 24 11:36:03 virtus dhcpcd[2505]: eth0: broadcasting for a lease
    Nov 24 11:36:04 virtus dhcpcd[2505]: eth0: offered 85.170.167.0 from 212.198.0.161
    Nov 24 11:36:04 virtus dhcpcd[2505]: eth0: ignoring offer of 85.170.167.70 from 212.198.0.162
    Nov 24 11:36:04 virtus dhcpcd[2505]: eth0: acknowledged 85.170.167.0 from 212.198.0.161
    Nov 24 11:36:04 virtus dhcpcd[2505]: eth0: checking for 85.170.167.0
    Nov 24 11:36:10 virtus dhcpcd[2505]: eth0: leased 85.170.167.0 for 14400 seconds
    Nov 24 11:36:10 virtus dhcpcd[2505]: forked to background, child pid 2603
    Nov 24 11:36:10 virtus ifplugd[2472]: client: :: ethernet-dhcp up [done]
    Nov 24 11:36:10 virtus ifplugd[2472]: Program executed successfully.
    This did not happen before using systemd, everything was fine back then.
    Any ideas? Thanks!
    Edit: Hardware is Lenovo T400.
    Last edited by ball (2013-01-23 22:45:20)

    @sie: thank you very much! This is it! Silence, finally!
    But instead of editing the .service file changing the ifplugd configuration is better IMHO. Otherwise the change won't survive an upgrade of netcfg. So I edited /etc/ifplugd/ifplugd.conf and added the "-b" flag to ARGS.
    EDIT: I just realized that adding "-b" to the default ARGS of ifplugd does not have the desired effect, the problem persists. So why is this the case? Do the flags which are employed in the .service file bypass the default ifplugd configuration? Or is this my very own user misconception? I did RTFM, though...
    Currently this is my /usr/lib/systemd/system/net-auto-wired.service:
    [Unit]
    Description=Provides automatic netcfg wired connection
    [Service]
    EnvironmentFile=/etc/conf.d/netcfg
    ExecStart=/usr/bin/ifplugd -i $WIRED_INTERFACE -r /etc/ifplugd/netcfg.action -fIns -b
    ExecStop=/usr/bin/netcfg iface-down $WIRED_INTERFACE
    [Install]
    WantedBy=multi-user.target
    If this issue really has to be addressed in the .service file, we should file a bug report/feature request.
    Last edited by ball (2013-01-23 18:13:13)

  • [Solved] Problems with net-auto-wired, no interent after install

    *Background*
    I am returning to Arch Linux after being away for about a year. I have finally had a chance to install Arch on my new laptop. Since I am new to systemd and the new installation process I followed the beginners guide very closely.
    *Description of the Steps I followed and the Error I encountered*
    When I came the the "Configure the Network" Portion of the Beginners' Guide, I chose to follow the net-auto-wired setup. This was partly because I found the warning to be confusing and could not understand why the Guide included a command that "won't work". Additionally I the "net-auto-wired" method seemed given the language of the Guide to be the superior alternative. So I followed the following steps:
    # pacman -S ifplugd
    # cd /etc/network.d
    # ln -s examples/ethernet-dhcp .
    # systemctl enable net-auto-wired.service
    These commands returned no errors, nor did the net-auto-wired daemon fail to initialize on reboot. I simply did not have a connection with the internet, even after confirming that all the wires were securely plugged in.
    *Question for the Forum*
    I was able to establish a connection with via several means as well I will likely be installing dbus and wicd to manage my internet connections. So my question is less about how to get connected and more (a) how to trouble shoot net-auto-wired and (b) what language and procedures can we change to the Beginners' Guide so that this issue is not encountered by beginners in the future.
    *Information I have Uncovered*
    When the net-auto-wired daemon failed to establish a connection. I immediately tried running the following command:
    # systemctl enable [email protected]
    The output of this command (what is following) showed me what the warning was talking about, how it rename the symbolic link to eth0.service and not enp4s0f2.service as it should have.
    ln -s '/usr/lib/systemd/system/[email protected]' '/etc/systemd/system/multi-user.target.wants/[email protected]'
    I attempted to resolve this issue by creating the symbolic link with the following command
    # ln -s /usr/lib/systemd/system/[email protected] /etc/systemd/system/multi-user.target.wants/[email protected]
    After reboot, the appropriately started the dhcpcd@ deamon and established an internet connection.
    It also hit me that the netcfg profile "ethernet-dhcp" would be pointing to the wrong interface. I edited the profile to interface with the enp4s0f2 not eth0 and was able to establish a connection manually with the following command but net-auto-wired still failed to work.
    # netcfg ethernet-dhcp
    At this point I checked the status of the of the net-auto-wired daemon with the following command which uncovered what is most certainly the issue.
    # systemctl status net-auto-wired
    net-auto-wired.service - Provides automatic netcfg wired connection
    Loaded: loaded (/usr/lib/systemd/system/net-auto-wired.service; disabled)
    Active: active (running) since Thu 2013-01-24 14:47:12 EST; 36s ago
    Main PID: 421 (ifplugd)
    CGroup: name=systemd:/system/net-auto-wired.service
    421 /usr/bin/ifpluged -i eth0 -r /etc/ifplugd/netcfg.action -fIns
    Jan 24 14:47:12 ragnarok systemd[1]: Started Provides automatic netcfg wired connection.
    Jan 24 14:47:12 ragnarok ifplugd[421]: ifplugd 0.28 initializing.
    Jan 24 14:47:12 ragnarok ifplugd[421]: Using interface eth0
    Jan 24 14:47:12 ragnarok ifplugd[421]: Initalization complete, link beat not detected.
    Obviously the issues with this are it use of eth0 and not enp4s0f2.
    I do not know where to go from here but I am curious if the issue of dhcpcd@ misnaming the symlink is some how related to this issue.
    Thanks for all your insight and responses.
    PS. This is the third time I have written this post. I finally typed it out in a separate text editor and then copied it in. Twice my login has timed out before I could submit and thus when I submitted I was logged out and my post lost. I do not post often with the forums but I was just frustrated to have lost so much effort. Has anyone else encountered this?
    Last edited by jash (2013-01-25 17:29:49)

    jash wrote:PS. This is the third time I have written this post. I finally typed it out in a separate text editor and then copied it in. Twice my login has timed out before I could submit and thus when I submitted I was logged out and my post lost. I do not post often with the forums but I was just frustrated to have lost so much effort. Has anyone else encountered this?
    Yes, it seems that after a period of inactivity (5 minutes ?) the forum software automatically logs someone out.
    After that happened to me for the zillionth time, i installed the firefox addon ReloadEvery .
    Now i always open 2 tabs for arch forums : 1 that just shows the index, and has reloadevery enabled with a time of 1 minute.
    The 2nd tab is for reading/answering etc.
    Haven't been logged out automatically since.

  • Net-auto-wired wont start

    Trying to enable and start net-auto-wired but systemctl says:
    net-auto-wired.service - Provides automatic netcfg wired connection
              Loaded: loaded (/usr/lib/systemd/system/net-auto-wired.service; enabled)
              Active: failed (Result: exit-code) since Thu, 2013-04-25 18:51:59 UTC; 1s ago
             Process: 21000 ExecStop=/usr/bin/netcfg iface-down $WIRED_INTERFACE (code=exited, status=0/SUCCESS)
             Process: 20998 ExecStart=/usr/bin/ifplugd -i $WIRED_INTERFACE -r /etc/ifplugd/netcfg.action -fIns (code=exited, status=203/EXEC)
              CGroup: name=systemd:/system/net-auto-wired.service
    Apr 25 18:51:59 u3640230-01 systemd[1]: Starting Provides automatic netcfg wired connection...
    Apr 25 18:51:59 u3640230-01 systemd[1]: Started Provides automatic netcfg wired connection.
    Apr 25 18:51:59 u3640230-01 systemd[1]: net-auto-wired.service: main process exited, code=exited, status=203/EXEC
    Apr 25 18:51:59 u3640230-01 systemd[1]: Unit net-auto-wired.service entered failed state
    What might I be doing wrong?

    after updating, and reinstalling pacman i could get netctl again
    when i do systemctl start [email protected] i get locked out from SSH and i have to reboot
    after reboot i do systemctl status [email protected]
    it shows:
    Apr 26 04:28:31 u364023 ifplugd[443]: client: Starting network profile 'ethernet-static'...
    Apr 26 04:28:31 u364023 ifplugd[443]: client: RTNETLINK answers: File exists
    Apr 26 04:28:31 u364023 ifplugd[443]: client: Could not add address '............./24' to interface 'eth0'
    Apr 26 04:28:31 u364023 ifplugd[443]: client: Failed to bring the network up for profile 'ethernet-static'
    Apr 26 04:28:31 u364023 ifplugd[443]: Program execution failed, return value is 1.
    i guess this is because ifconfig already has an ip set up?
    after that, there is:
    Apr 26 04:29:40 u364023 systemd[1]: Stopping Automatic wired network connection using netctl profiles...
    Apr 26 04:29:40 u364023 ifplugd[443]: Executing '/etc/ifplugd/netctl.action eth0 down'.
    Apr 26 04:29:40 u364023 ifplugd[443]: Program execution failed, return value is 1.
    Apr 26 04:29:40 u364023 ifplugd[443]: Exiting.
    Apr 26 04:29:40 u364023 systemd[1]: Stopped Automatic wired network connection using netctl profiles.
    guessing this is netctl trying to start up the profile after reboot..
    in my rc.conf i have my old settings for eth
    i tried to disable the old ip link lines, and rebooted with netctl service active but no ip is being set with ifconfig

  • IDOC Invoic02 - Segment E1EDP26 (net value) is missing because of val. 0,00

    Hello everyone,
    I have an idoc of type Invoic02 and the segment E1EDP26 with qualifier 003 (net value) is missing if the net value is 0,00u20AC. If the value is greater than zero, the segment is perfectly there.
    Does anyone have an idea how I can achieve that this segment is always there independent of the value?
    Thank you!
    Best regards
    Andreas

    I'm replying to this old post since it comes up in Search. We had the same issue - E1EDP26 with QUALF 003 would not be in the IDoc, but it was required by the receiving system.
    Here is a reply I received from SAP:
    This is the standard system behaviour and this is hard coded in the
    system.
    Please see the following from note 635337 (Conditions are missing in theIDoc):
    o The value of the condition must be <> 0.
    You may change the code in LVEDFF0F by removing the IF and ENDIF
    statements and then E1EDP26 segment 003 will always be output
    but this would be a modification and would be subject to the conditions
    from note 170183.
    *- Absoluter Nettowert
    IF NOT tvbdpr-netwr IS INITIAL. <<<
    CLEAR int_edidd.
    CLEAR e1edp26.
    int_edidd-segnam = 'E1EDP26'.
    e1edp26-qualf = '003'.
    PERFORM get_e1edp26_tcurx_currency USING tvbdpr-netwr.
    MOVE tvbdpr-netwr TO h_newr_btrg.
    MOVE e1edp26 TO int_edidd-sdata.
    APPEND int_edidd.
    PERFORM customer_function.
    ENDIF. <<<
    Since we already had a user exit EXIT_SAPLVEDF_002 implemented for the IDoc extension, instead we resolved it by adding the following code (fragment) there:
    DATA ls_e1edp26    TYPE e1edp26.   "document item pricing data
    DATA lv_kwert      TYPE kwert.
    CASE int_edidd-segnam.
      WHEN 'E1EDP26'.
        MOVE int_edidd-sdata TO ls_e1edp26.
        IF ls_e1edp26-qualf = '001'.
          IF xtvbdpr-netwr = 0.
            CLEAR: ls_e1edp26, lv_kwert.
            ls_e1edp26-qualf = '003'.
            ls_e1edp26-betrg = lv_kwert.   " so that decimals/format are the same
            SHIFT ls_e1edp26-betrg LEFT DELETING LEADING space.
            MOVE ls_e1edp26 TO int_edidd-sdata.
            APPEND int_edidd.
          ENDIF.
        ENDIF.      " ls_e1edp26-qualf = '001'
    ENDCASE.

  • I have a net gear wireless router and a APE working great inside the house, but the wireless signal is weak in the backyard, can I get a net gear extender for the back and it will also send my music to the airport express?

    I have a net gear wireless router and a APE working great inside the house, but the wireless signal is weak in the backyard, can I get a net gear extender for the back yard and it will boost our wo
    Ireless signal and also send my music to the airport express? Or does the airport express work as a stand alone hub?

    Trust me when I say this coming from 20 years of experience.
    Get a powered external drive, format it 1 Partition Option: GUID and OS X Extended Journed as the format in Disk Utility.
    Download and install Carbon Copy Cloner, clone internal drive to external drive.
    Set a schedule to remind you to do it at least once a week, keep it near your charger.
    When you plug your charger in, do plug the clone and power the machine up, set the display to sleep only,
    CCC will do the rest.
    If you want to boot from it, hold the option/alt and select it Startup Manager.
    I've seen many TimeMachine and TimeCapsule nightmares and so far haven't seen a problem from anyone using a bootable clone.
    It's simple, it's easy, it's more reliable and more powerful than what Apple does and it only takes plugging in a extra cable.
    Make as many clones as you want, keep them time seperated, off site etc. etc.
    Cables don't have network issues, clones can be verified in seconds merely by booting from them.
    Clones protect your productivity, your up in seconds on a clone despite even the hard drive dying.
    Software problem? No sweat, boot of the clone and reverse clone your problems away.
    If you want to fuss and muss with half implemented TimeMachine and TimeCapsule network headaches then prepare to suffer.
    I don't like to suffer, I bought a Mac not to suffer, but it appears you do with TimeMachine and TimeCapsule.
    Most commonly used backup methods

Maybe you are looking for