[SOLVED] netcfg "IP lease attempt failed" on ethernet connection

Since the latest update today I can't connect to the Internet (using an ethernet cable) any more.
# NETCFG_DEBUG="yes" netcfg cable
DEBUG: Loading profile cable
DEBUG: Configuring interface eth0
:: cable up [BUSY]
DEBUG: status reported to profile_up as:
DEBUG: Loading profile cable
DEBUG: Configuring interface eth0
DEBUG: ethernet_iproute_up ifup
DEBUG: ethernet_up dhcpd -qL -t 30 eth0
DEBUG:
> DHCP IP lease attempt failes.
DEBUG: profile_up connect failed
[FAIL]
System: Arch 64
Does anyone have any idea what might be wrong? Not sure where to start there, as the interface eth0 seems to be up and all right under ifconfig.
Thanks for any hints.
Last edited by JackH79 (2011-12-01 00:53:19)

Thanks very much for your suggestions, ewaller.
Weirdly enough though, this morning I came into work, plugged in the cable and, voilà, it worked straight away.
Maybe it's just that time of the month.
Anyway, thanks again to you and cybertorture. I'll mark this as solved for now.
EDIT: Just a little follow up to make it a bit more embarassing: I just realised that it was actually the port of the switch that's broken. So thanks to ewaller for stating the obvious
Last edited by JackH79 (2011-12-01 07:05:25)

Similar Messages

Netcfg WirelesLAN gives error "DHCP IP lease attempt failed" [SOLVED]

i couldn't find a solution for this on the forums, though it seems to be a well known problem ...
the drivers for my network device eth1 (zd1211) are installed and it is detected by iwconfig after a fresh arch install.
the file WirelessLAN is set up like this:
CONNECTION="wireless"
INTERFACE=eth1
SCAN="yes"
SECURITY="wpa"
ESSID="..."
KEY="..."
IP="dhcp"
TIMEOUT=20
but a netcfg2 WirelessLAN gives me:
:: WirelessLAN up [BUSY]
DHCP IP lease attempt failed [FAIL]
any ideas ???
Last edited by fdrebin (2008-09-28 16:13:20)

Hi.
I got the same problem since dhcpd was updated during the last full-system-upgrade (-Suy).
My profile is the following:
CONNECTION="ethernet"
DESCRIPTION="..."
INTERFACE=ra0
IP="dhcp"
DHCP_TIMEOUT="30"
PRE_UP="ifconfig ra0 up; iwconfig ra0 essid Ranger channel 9 mode managed"
I know that this config is very ugly, but it worked.
I have got another config, that may look better for you, but I don't know if it works. I created it today. If I try this new profile, I get the same error.
In the past configs like this led to other errors. So I made the ugly config above.
CONNECTION="wireless"
DESCRIPTION="..."
INTERFACE=ra0
SCAN="yes"
SECURITY="none"
ESSID="Ranger"
IP="dhcp"
DHCP_TIMEOUT=30
Do you have any hints, how I can get more a detailed error report. Downgrading dhcpd would be a good idea, too. Any hints for that?
Thanks for your help.
Alpha

[SOLVED] netcfg DHCP IP lease attempt failed

I'm trying to configure my network settings, I made a profile, netcfg recognizes the profile, but when it loads I get that error (DHCP IP lease attempt failed). Here is my profile...
CONNECTION='wireless'
INTERFACE='wlan0'
SECURITY='none'
ESSID='my network name'
IP='dhcp'
DCHP_TIMEOUT='30'
Last edited by oldstutz (2010-07-30 18:33:54)

jogan wrote:
jogan wrote:
Do you have any idea how to load the rt2860 driver from /lib/firmware/rt2860.bin?
My attempt to load the driver with MODULES in /etc/rc.conf has been unsuccessful.
oldstutz wrote:RaLink RT2860, and I have rt2860sta in my modules
I've battled this issue for weeks on my notebook ... wireless worked on Arch (2009.08)
last year. Seems to me now the culprit maybe rt2860sta.
OK, let's check
lsmod | grep -i rt2860

Netcfg laptop wireless - "DHCP ip lease attempt failed"??

hey folks. just loaded arch onto a toshiba laptop. in the process of configuring wireless, i followed the netcfg config instructions in the wiki. It worked fine the first time, but when I rebooted every subsequent time i tried to connect I get the "DHCP IP lease attempt failed" error. IN my logs i get absolutely nothing helpful - just "wlan0: rebinding lease of 172.16.0.138" and "wlan0: timed out". Of course, when I had Windows XP on the laptop it had zero problems connecting to the network, and it makes no damn sense why I was able to connect intially but each time after that it times out. My router has no problems.
I did a forum search and someone suggested that this was because of a "bug" and to delete the file "/var/lib/dhcpcd/dhcpcd-wlan0.lease" file. I did this, and was able to connect successfully. But this is not a solution; am I really supposed to delete the lease EVERY time I reconnect/reboot the machine? Doesn't make any sense at all.
Can ANYONE please help on this? I can post whatever config file/log info you need. This seems like it should be a simple setup, but I've come to realize nothing's ever simple in the linux world.... btw my network uses WPA2. There wasn't anything in the wiki about WPA2 (must be really really old, huh?); could this be part of the problem?

Alternatively, try adding
PRE_UP=' [ -e /var/lib/dhcpcd/dhcpcd-wlan0.lease ] && rm /var/lib/dhcpcd/dhcpcd-wlan0.lease '
to the profile with the problem.
Edit: I misspelled "dhcpcd" in the code above.
Last edited by alexandrite (2010-08-15 14:54:33)

Wired "dhcp ip lease attempt failed"/no internet

Hi, I've been using netcfg on arch for a couple months now and never had trouble with it until today, I just changed internet carrier and the guy came install the modem here and I tried to plug my laptop to it and I can't get internet. Before whenever I plugged an Ethernet cable it would connect automatically because of ifplugd. I use the profile "ethernet-dhcp" from the examples that I copied to /etc/network.d. When I plug the wire, internet doesn't work so I tried : netcfg -a : Done, netcfg ethernet-dhcp and get "dhcp ip lease attempt failed".
I read the forums and tried some solution proposed to people with same error message but with wireless and sometimes I can connect to the profile, but I still don't have internet.
I've plugged the cable in my eepc running win7 and it works (I'm writing this from the eepc). Also the link light flashes on the modem And on my T61 when I plug the cable in the ethernet slot. I tried a static profile with the same ip as my eepc but no joy.
any suggestions ?
thank you

Hi, I've been using netcfg on arch for a couple months now and never had trouble with it until today, I just changed internet carrier and the guy came install the modem here and I tried to plug my laptop to it and I can't get internet. Before whenever I plugged an Ethernet cable it would connect automatically because of ifplugd. I use the profile "ethernet-dhcp" from the examples that I copied to /etc/network.d. When I plug the wire, internet doesn't work so I tried : netcfg -a : Done, netcfg ethernet-dhcp and get "dhcp ip lease attempt failed".
I read the forums and tried some solution proposed to people with same error message but with wireless and sometimes I can connect to the profile, but I still don't have internet.
I've plugged the cable in my eepc running win7 and it works (I'm writing this from the eepc). Also the link light flashes on the modem And on my T61 when I plug the cable in the ethernet slot. I tried a static profile with the same ip as my eepc but no joy.
any suggestions ?
thank you

Iwl4965, netcfg2 lease attempt failed

I'm trying to get my iwl4965 running with netcfg2, but i keep getting stuck on the actual connection/dhcp process. These are the packages i have installed:
core/wireless_tools 29-2 [installed]
Wireless Tools
core/iwlwifi-4965-ucode 228.57.2.21-1 [installed]
Intel wireless firmware for IPW4965 (iwlwifi driver)
core/wpa_supplicant 0.5.10-1 [installed]
A utility providing key negotiation for WPA wireless networks
core/netcfg 2.0.6-1 [installed]
Network configuration and profile scripts
test.profile:
CONNECTION="wireless"
INTERFACE=wlan0
SCAN="no"
SECURITY="wpa"
ESSID="Meow"
KEY="mypasswd"
IP="dhcp"
TIMEOUT=20
iwlist wlan0 scan:
Cell 02 - Address: 00:19:CB:09:35:EE
ESSID:"Meow"
Mode:Master
Channel:7
Frequency:2.442 GHz (Channel 7)
Quality=85/100 Signal level=-48 dBm Noise level=-127 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:tsf=0000000c3c85d01a
when i issue a netcfg2 test.profile, it's status says BUSY and stays like that indefinitely. when i then press control-c i get an extra line saying the DHCP lease failed:
:: Meow up [BUSY]
^C - DHCP IP lease attempt failed [FAIL]
dmesg:
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:19:cb:09:35:ee
wlan0: RX authentication from 00:19:cb:09:35:ee (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:19:cb:09:35:ee
wlan0: RX AssocResp from 00:19:cb:09:35:ee (capab=0x51 status=0 aid=2)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
wlan0: deauthenticate(reason=3)
could it be something trivial i'm missing? i've used wireless without problems before using networkmanager, but i really would like to use netcfg2 instead.

Hello, there seems to problems with this iwl4965-driver.
Those guys have similar problems:
http://bbs.archlinux.org/viewtopic.php?id=53300
and here is another problem with this driver described:
http://bbs.archlinux.org/viewtopic.php? … 42#p396142
So, it seems as these problems are related, so just try to use an older driver version.

Wireless: DHCP IP lease attempt failed

Hi,
did an upgrade today and now I get the above error message, when trying to connect to my router with netcfg2. The exact error message is like following:
[root@tux matthias]#
[root@tux matthias]# netcfg2 home
dhcpcd: wlan0: ignoring DHCP message; no Server ID
dhcpcd: wlan0: ignoring DHCP message; no Server ID
dhcpcd: wlan0: ignoring DHCP message; no Server ID
dhcpcd: timed out
:: home up - DHCP IP lease attempt failed [FAIL]
My /etc/network.d/home looks like that:
CONNECTION="wireless"
INTERFACE=wlan0
QUIRKS=(prescan preessid)
SCAN="yes"
SECURITY="wpa"
ESSID="wirelessbox"
KEY="..."
IP="dhcp"
TIMEOUT=30
I did nothing except updating. Everything worked fine before that.
Any hints?
EDIT: I added the QUIRKS line after getting the error message, because a guy on IRC suggested that. This didn't help either.
Last edited by mamr (2009-05-11 12:46:11)

rsmarples wrote:
dhave wrote:
rsmarples wrote:You can't "turn the message off" as such. You you see the ignoring message then the DHCP packet really is ignored. So if you see that message AND dhcpcd still works with a proper IP (ie not ipv4ll) then you have 2 DHCP servers running on your network and one of them is fautly.
Thanks for the explanation. Is this a problem to have a broken DHCP server running for no purpose? Is this hurting my gas mileage or anything?
Well, you're probably better off finding the faulty router and disabling it.
dhcpcd presently selects and uses the first DHCP working reply it gets and if the server is "fixed" to send ServerID then you could get conflicting lease information.
I see I have a lot to learn. The reason it's finding two routers is that I have a modem-router and then, in another part of the house, an access point that I've configured as a repeater (actually, since it has a separate ssid, maybe it's not considered a repeater; I don't know).
When I move my laptop from my office into the living room, I often switch from connecting through the "repeater" and connect directly to the modem-router. It's at this point that I get the messages about "no server ID". So, in fact, dhcpcd is doing what it's supposed to be doing, I guess.
I need to do some reading and try to figure out if my setup could be cleaned up so as to avoid lease conflicts or whatever. When I fool with network stuff, I'm always working beyond my level of understanding. I usually just fiddle until I get things to work, which means I probably could do a lot to streamline and improve performance.

A connection attempt failed because the connected party did not properly respond after a period of time

Prior to the Increase Capacity for Outbound Network Calls update, my Azure websites running in
Standard mode experienced occasional connection attempt failed errors. Since this update the errors stopped but starting on 12/30/14, these errors started up again on both
South Central and East regions:
"A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond [IP]:80"
It occurs when attempting to consume an external web service over HTTP. This issue is not reproducible on our local environments nor did it occur with our previous shared hosting provider.
On Azure, the same web service call can result in this error or will return a response successfully.
There doesn't appear to be any pattern as to why the same call would work one time but not another.
How can this be resolved again? Any feedback is appreciated. Thanks.

Hi,
Please have a look at this article:
http://blogs.msdn.com/b/narahari/archive/2011/12/21/azure-a-connection-attempt-failed-because-the-connected-party-did-not-properly-respond-after-a-period-of-time-or-established-connection-failed-because-connected-host-has-failed-to-respond-x-x-x-x-x-quot.aspx,
it gives us several ways to solve this issue, hope this helps.
Best Regards,
Jambor
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

DHCP IP lease attempt failed

Hello
I have a problem with netcfg. It works perfectly at home. However, now that I am trying to connect to another router it keeps giving me this error and I can't figure out why and how to fix.
I have read several discussion on this forum on netcfg errors, however, none of them helped me, so I am asking here again.

More details required - start with "wired or wireless?", then move on to "have I created a profile for the new network?".
If wired, make sure your link lights are on, then try a static IP.
If wireless, try a manual connection, as described in the wiki's wireless page.

[SOLVED] netcfg fails to add IPv6 gateway

After updating the (~2-month backlog of) packages on an Arch Linux VPS, I can no longer get netcfg to bring up eth0 with an IPv6 gateway. However, if I bring up eth0 manually, it works...
[root@inception ~]# ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 metric 1
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[root@inception ~]# lsmod
Module Size Used by
evdev 9370 0
pcspkr 1819 0
ext4 374587 1
crc16 1359 1 ext4
jbd2 71543 1 ext4
mbcache 5977 1 ext4
xen_netfront 17247 0
xen_blkfront 12625 2
xenbus_probe_frontend 3239 2 xen_blkfront,xen_netfront
[root@inception ~]# rc.d start net-profiles
:: eth0 up [BUSY] RTNETLIN
K answers: No route to host
> Adding gateway 2a00:7b80:3008::1 failed
[FAIL]
> No profile started.
[root@inception ~]# ifconfig eth0 up
[root@inception ~]# rc.d start net-profiles
:: eth0 up [DONE]
[root@inception ~]# cat /etc/network.d/eth0
CONNECTION='ethernet'
DESCRIPTION='Ethernet 0'
INTERFACE='eth0'
IP='static'
ADDR='xx.xx.xxx.xxx'
GATEWAY='77.95.224.1'
IP6='static'
ADDR6=('xxxx:xxxx:xxxx:x::xxxx:xxxx' 'xxxx:xxxx:xxxx:x::xxxx:xxxx' 'xxxx:xxxx:xxxx:x::xxx
x:xxxx' 'xxxx:xxxx:xxxx:x::xxx:xxxx' 'xxxx:xxxx:xxxx:x::xxxx:xxxx')
GATEWAY6='2a00:7b80:3008::1'
DNS=('8.8.8.8' '8.8.4.4' '2001:4860:4860::8888' '2001:4860:4860::8844')
[root@inception ~]# uname -a
Linux inception 3.0.38-1-lts #1 SMP PREEMPT Fri Jul 20 09:22:28 CEST 2012 x86_64 GNU/Linu
x
I don't know if I borked something during the package upgrades -- there were those couple announced ones that required minor manual intervention. Any ideas?
Last edited by MindlessXD (2013-01-26 16:44:42)

(I've changed the IP addresses.)
# cat /etc/network.d/eth0
INTERFACE="eth0"
DESCRIPTION="static IP for eth0"
CONNECTION="ethernet"
IP="static"
ADDR="204.51.26.215"
GATEWAY="204.51.26.1"
IP6="static"
ADDR6=(2402:4400:2:16c1::1/64)
GATEWAY6="2402:4400:2::2"
# netcfg -v
netcfg v2.8.3
# NETCFG_DEBUG="yes" netcfg eth0
DEBUG: Loading profile eth0
DEBUG: Configuring interface eth0
:: eth0 up DEBUG: status reported to profile_up as:
DEBUG: Loading profile eth0
DEBUG: Configuring interface eth0
DEBUG: ethernet_up ifup
DEBUG: ethernet_up ip addr add 204.51.26.215/24 brd + dev eth0
DEBUG: ethernet_up ip route add default via 204.51.26.1 dev eth0
DEBUG: ethernet_up ip -6 addr add 2402:4400:2:16c1::1/64 dev eth0
DEBUG: ethernet_up ip -6 route replace default via 2402:4400:2::2 dev eth0
DEBUG: ethernet_up ip -6 addr show dev eth0 tentative
DEBUG: ethernet_up hostname galloway
[done]
# netcfg -v
netcfg v2.8.8
# NETCFG_DEBUG="yes" netcfg eth0
DEBUG: Loading profile eth0
DEBUG: Configuring interface eth0
:: eth0 up DEBUG: status reported to profile_up as:
DEBUG: Loading profile eth0
DEBUG: Configuring interface eth0
DEBUG: ethernet_up bring_interface up eth0
DEBUG: ethernet_up ip addr add 204.51.26.215/24 brd + dev eth0
DEBUG: ethernet_up ip route add default via 204.51.26.1 dev eth0
DEBUG: ethernet_up ip -6 addr add 2402:4400:2:16c1::1/64 dev eth0
DEBUG: ethernet_up ip -6 route replace default via 2402:4400:2::2 dev eth0
RTNETLINK answers: No route to host
Adding gateway 2402:4400:2::2 failed
DEBUG: profile_up connect failed
[fail]

[Solved] Netcfg 2.6.1 - suddenly fails to associate with WPA2 network

Everything around here seems to be breaking these days... Anyways.
I upgraded netcfg yesterday. Today I fire up my laptop, but no wireless. I run netcfg again, this is what wpa_supplicant spits out:
# netcfg intel
:: intel up [BUSY]
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
^C
The funny thing is, nothing's changed in the netcfg config file, which looks like this:
CONNECTION="wireless"
INTERFACE="intel"
HOSTNAME="hermes"
# AP authentication
SCAN="yes"
SECURITY="wpa-config"
WPA_CONF="/etc/wpa_supplicant.conf"
WPA_OPTS="-Dwext -B"
ESSID="Zeus 802.11n"
# IP address
IP="dhcp"
DHCP_TIMEOUT=10
I compared my config to the examples that come with netcfg - just to be sure nothing's changed that I wasn't aware of - but it looks pretty identical. Oddly enough, calling wpa_supplicant and then dhcpcd directly just connects me to my WLAN, like netcfg used to be able to do.
For reference, netcfg seems to call wpa_supplicant like this, going by htop's output:
wpa_supplicant -Dwext,nl80211 -c /etc/wpa_supplicant.conf -B -i intel -d
When run separately, however, that works just fine, just like using -Dwext like I used to do before.
Last edited by .:B:. (2011-06-21 22:29:55)

My understanding is that the thing fails in start_wpa(). From /usr/lib/network/8021x:
start_wpa()
local INTERFACE="$1" WPA_CONF="$2" WPA_DRIVER="$3"
shift 3
local WPA_OPTS="$*"
wpa_supplicant -B -P "/run/wpa_supplicant_${INTERFACE}.pid" -i "$INTERFACE"-D "$WPA_DRIVER" -c "$WPA_CONF" $WPA_OPTS
sleep 1
if [[ ! -f "/run/wpa_supplicant_${INTERFACE}.pid" ]]; then
return 1
fi
So, you should have seen "-P' in htop, no? Have you tried w/o WPA_OPTS?
EDIT: OK, I was wrong. The error seems to come from wpa_supplicant/wp_cli calls with the new /run standard:
arch~> grep "/run/wpa_supplicant" ./usr/lib/network/8021x
WPA_CLI="wpa_cli -p /run/wpa_supplicant"
wpa_supplicant -B -P "/run/wpa_supplicant_${INTERFACE}.pid" -i "$INTERFACE" -D "$WPA_DRIVER" -c "$WPA_CONF" $WPA_OPTS
if [[ ! -f "/run/wpa_supplicant_${INTERFACE}.pid" ]]; then
if [[ -f "/run/wpa_supplicant_$1.pid" ]]; then
kill "$(cat "/run/wpa_supplicant_$1.pid")" &>/dev/null &
wpa_supplicant -B -i"$INTERFACE" -Dnl80211,wext -C/run/wpa_supplicant -P/run/wpa_supplicant.pid || return 1
kill "$(cat /run/wpa_supplicant.pid)"
echo "ctrl_interface=/run/wpa_supplicant" >> "$WPA_CONF/wpa.conf" # we know $WPA_CONF now has no spaces, but it may have other nasty chars, so still needs to be quoted
Could you change the ctrl_interface to to /run/wpa_supplicant in /etc/wpa_supplicant.conf?
Last edited by Leonid.I (2011-06-21 21:19:59)

[SOLVED] Netcfg.service always failing.

Hello,
Since systemd got pushed down with an update I decided to jump the ship (even though roughly a week ago I tried it and decided to wait a while, the irony ) With the help of my previous topic and the knowledge that e4rat does work with systemd, I got everything working and it's working faster than ever too. Win/win if you ask me.
There's only one issue: the netcfg.service that I have enabled with systemctl enable netcfg.service always fail on boot and I have to manually connect later. I don't know why it fails, so I hope you can help me tracking the issue.
This is the output of systemctl status netcfg.service right after booting:
┌─[jente @ lappy ~] 19:39:30
└─■ systemctl status netcfg.service
netcfg.service - Netcfg multi-profile daemon
Loaded: loaded (/usr/lib/systemd/system/netcfg.service; enabled)
Active: failed (Result: exit-code) since Fri, 31 Aug 2012 19:35:04 +0200; 4min 27s ago
Process: 253 ExecStart=/usr/bin/netcfg-daemon start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/netcfg.service
And here's systemctl --failed list-units:
┌─[jente @ lappy ~] 19:39:32
└─■ systemctl --failed list-units
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
netcfg.service loaded failed failed Netcfg multi-profile daemon
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
1 units listed. Pass --all to see inactive units, too.
And here's the journal output:
----- Reboot -----
Aug 31 19:35:04 lappy netcfg-daemon[253]: :: [ESSID] up interface wlan0 does not exist
Aug 31 19:35:04 lappy netcfg-daemon[253]: [fail]
I don't think it's any netcfg configuration file, because it did work with SysV and the net-profiles daemon.
Last edited by Unia (2012-10-31 14:20:21)

I use a custom "network.service" as I have a static ip on my wireless lan (oh, and I chucked in the hdparm stuff because after suspend I found the disk had lost those settings, so don't copy that line). Based on this wiki section.
$ cat /etc/systemd/system/network.service
[Unit]
Description=Network Connectivity
Wants=network.target
Before=network.target
After=sys-devices-pci0000:00-0000:00:1c.1-0000:02:00.0-bcma0:0-net-wlan0.device
BindTo=sys-devices-pci0000:00-0000:00:1c.1-0000:02:00.0-bcma0:0-net-wlan0.device
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network
ExecStart=/sbin/hdparm --yes-i-know-what-i-am-doing -m 16 -S0 -B255 /dev/sda
ExecStart=/usr/sbin/wpa_supplicant -B -i ${interface} -c /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
ExecStart=/sbin/ip link set dev ${interface} up
ExecStart=/sbin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev ${interface}
ExecStart=/sbin/ip route add default via ${gateway}
ExecStop=/sbin/ip addr flush dev ${interface}
ExecStop=/sbin/ip link set dev ${interface} down
ExecStop=/usr/bin/killall wpa_supplicant
[Install]
WantedBy=multi-user.target

[Solved] Netcfg switches between interfaces

Hello,
I switched to netcfg, to get a pure systemd install.
How ever, sometimes the netcfg can't bring up the interface even though it used that interface before.
It's like netcfg are switching between what interface it can use. Sometimes it's eth0 other times eth1.
So when I boot and don't have any network connection, I change the config files to use the other interface (ex. eth1) and netcfg can connect.
How can this be?
configs:
/etc/network.d/mynetwork
CONNECTION='ethernet'
DESCRIPTION='A basic static ethernet connection using iproute'
INTERFACE='eth1'
IP='static'
ADDR='192.168.1.3'
#ROUTES=('192.168.0.0/24 via 192.168.1.2')
GATEWAY='192.168.1.1'
DNS=('dns1', 'dns2)
## For IPv6 autoconfiguration
#IP6=stateless
## For IPv6 static address configuration
#IP6='static'
#ADDR6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
#ROUTES6=('abcd::1234')
#GATEWAY6='1234:0:123::abcd'
/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=(mynetwork)
# Specify the name of your wired interface for net-auto-wired
WIRED_INTERFACE="eth1"
# 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")
Last edited by KLIM (2012-12-06 14:22:23)

Did you checked for netcfg.service is enabled (systemd) ?
BTW, I see a missing single quote on DNS line : DNS=('dns1', 'dns2)
You may check these forum posts :
"[SOLVED] Netcfg.service always failing." @ https://bbs.archlinux.org/viewtopic.php?id=148079
"Systemd and Netcfg" @ https://bbs.archlinux.org/viewtopic.php?id=151662
"netcfg/systemd not bringing up eth0 (static profile)" @ https://bbs.archlinux.org/viewtopic.php?id=147300
"[SOLVED] netcfg fails at boot" @ https://bbs.archlinux.org/viewtopic.php?pid=1200518
And this wiki entry about netcfg @ https://wiki.archlinux.org/index.php/Netcfg

HP 2000-2b16NR Recovery Attempt Failed Windows 8 64bit

Product Name: HP 2000-2b16NR
Operating System: Windows 8 x64
I was attempting to do a recovery with the discs I had bought from HP and I got this message "Recovery Attempt Failed" with options to restart recovery or view details. So I restarted the recovery and inserted disc 1 as it asked. It went through the process again and it came up with this same message "Recovery Attempt Failed". This time I clicked view details and it came up with notepad titled CTOERROR.flg with the following:
[13:17:34.28] ChkErrBB.CMD:
[13:17:34.28] Detect some error during PININST_BBV
[13:17:34.28] Check C:\system.sav\logs\BurnBootWarn.log
[13:17:34.28] or, check C:\system.sav\logs\BurnBootMerge.log
My Hard drive is completely wiped and I can not preform a system recovery by pressing f11 and I can not access Windows.
My question is why can I not successfully complete the recovery process?
This question was solved.
View Solution.

-the tip here about changing year in BIOS may help:
http://h30434.www3.hp.com/t5/Notebook-Operating-Systems-e-g-Windows-8-and-Software/restoration-faile...
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

[Solved] Can't get netctl working with ethernet/dhcp

I'm trying to use netctl with the example file for dhcp:
Description='A basic dhcp ethernet connection'
Interface=enp0s25
Connection=ethernet
IP=dhcp
## for DHCPv6
#IP6=dhcp
## for IPv6 autoconfiguration
#IP6=stateless
Starting this profile results in:
A dependency job for netctl@ethernet\x2ddhcp.service failed. See 'journalctl -xn' for details.
journalctl -xn
-- Logs begin at Sat 2014-09-13 19:32:03 CEST, end at Mon 2014-09-15 02:17:52 CEST. --
Sep 15 02:16:07 toms_machine sudo[2768]: pam_unix(sudo:session): session closed for user root
Sep 15 02:16:07 toms_machine dhcpcd[990]: exited
Sep 15 02:16:22 toms_machine sudo[2772]: ben : TTY=pts/2 ; PWD=/etc/netctl ; USER=root ; COMMAND=/usr/bin/netctl start ethernet-dhcp
Sep 15 02:16:22 toms_machine sudo[2772]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 15 02:17:52 toms_machine systemd[1]: Job sys-subsystem-net-devices-eth0.device/start timed out.
Sep 15 02:17:52 toms_machine systemd[1]: Timed out waiting for device sys-subsystem-net-devices-eth0.device.
-- Subject: Unit sys-subsystem-net-devices-eth0.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sys-subsystem-net-devices-eth0.device has failed.
-- The result is timeout.
Sep 15 02:17:52 toms_machine systemd[1]: Dependency failed for A basic dhcp ethernet connection.
-- Subject: Unit netctl@ethernet\x2ddhcp.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit netctl@ethernet\x2ddhcp.service has failed.
-- The result is dependency.
Note it is saying something about eth0 while ip link is resulting in
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 28:d2:44:52:2e:ad brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 5c:51:4f:fb:7b:51 brd ff:ff:ff:ff:ff:ff
Obviously there is no eth0. How can I set things up using the interface name "enp0s25"? By the way using dhcpcd works so there is no problem with the phsyical connection.
Last edited by gladixy (2014-09-18 12:00:15)

I solved the problem by replacing
/etc/systemd/system/netctl\@ethernet\\x2ddhcp.service
.include /usr/lib/systemd/system/[email protected]
[Unit]
Description=A basic dhcp ethernet connection
BindsTo=sys-subsystem-net-devices-eth0.device
After=sys-subsystem-net-devices-eth0.device
with
.include /usr/lib/systemd/system/[email protected]
[Unit]
Description=A basic dhcp ethernet connection
BindsTo=sys-subsystem-net-devices-enp0s25.device
After=sys-subsystem-net-devices-enp0s25.device
I'm not sure whether this is the best way to solve the problem. If somebody knows a better solution it would not hurt to post it here.

[SOLVED] netcfg "IP lease attempt failed" on ethernet connection

Similar Messages

Maybe you are looking for