Hide Forgot
+++ This bug was initially created as a clone of Bug #589521 +++ Description of problem: Bringing up loopback interface: [ OK ] Bringing up interface Auto_kiilerich: Determining IP information for ... done. cat: /sys/class/net//ifindex: No such file or directory /etc/sysconfig/network-scripts/ifup-eth: line 286: 1000 + : syntax error: operand expected (error token is "+ ") Missing config file ifcfg-ifcfg-Auto_kiilerich. [ OK ] Same setup and config as in bug 545597 where REALDEVICE also isn't set: # head /etc/sysconfig/network-scripts/{ifcfg,keys}-* ==> /etc/sysconfig/network-scripts/ifcfg-Auto_kiilerich <== ESSID="kiilerich" MODE=Managed KEY_MGMT=WPA-PSK TYPE=Wireless BOOTPROTO=dhcp PEERDNS=yes PEERROUTES=yes NAME="Auto kiilerich" UUID=1b6ba851-d2a0-402d-92ee-3bf4e0e45592 ONBOOT=yes ==> /etc/sysconfig/network-scripts/ifcfg-lo <== DEVICE=lo IPADDR=127.0.0.1 NETMASK=255.0.0.0 NETWORK=127.0.0.0 # If you're having problems with gated making 127.0.0.0/8 a martian, # you can change this to something else (255.255.255.255, for example) BROADCAST=127.255.255.255 ONBOOT=yes NAME=loopback ==> /etc/sysconfig/network-scripts/keys-Auto_kiilerich <== WPA_PSK="zecret" ==> /etc/sysconfig/network-scripts/keys-eth1 <== KEY=s:1123581321 ==> /etc/sysconfig/network-scripts/keys-Wireless_connection_1 <== WPA_PSK=alsosecret! The missing ifcfg-ifcfg-Auto_kiilerich seems like an error too ... or perhaps the same ... Version-Release number of selected component (if applicable): initscripts-9.11-1.fc13.i686
Whoops, cloned wrong bug.
Although, found a fix for this too.
http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=8445668
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
Red Hat Enterprise Linux Beta 2 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.