Changing en2 to en0? My change won't stick after reboot!

[legionX]

I've tried several times editing /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist so that my card is set to en0 instead of en2, but every single time I reboot it resets itself. How is that possible? Why won't it just accept what I put in? (I need this so FCP will work)

 

Here's my NetworkInterfaces.plist:

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>Interfaces</key>

<array>

<dict>

<key>BSD Name</key>

<string>en1</string>

<key>IOBuiltin</key>

<false/>

<key>IOInterfaceType</key>

<integer>6</integer>

<key>IOInterfaceUnit</key>

<integer>1</integer>

<key>IOLocation</key>

<string></string>

<key>IOMACAddress</key>

<data>

ABbPoF5V

</data>

<key>IOPathMatch</key>

<string>IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/P0P3@1C,2/IOPCI2PCIBridge/pci14e4,4311@0/AirPort_Brcm43xx/IO80211Interface</string>

</dict>

<dict>

<key>Active</key>

<true/>

<key>BSD Name</key>

<string>en2</string>

<key>IOBuiltin</key>

<true/>

<key>IOInterfaceType</key>

<integer>6</integer>

<key>IOInterfaceUnit</key>

<integer>2</integer>

<key>IOMACAddress</key>

<data>

AB6MQLs4

</data>

<key>IOPathMatch</key>

<string>IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/P0P5@1C,1/IOPCI2PCIBridge/ethernet@0/rtl_r1000_nic_ext/IOEthernetInterface</string>

<key>SCNetworkInterfaceType</key>

<string>Ethernet</string>

</dict>

<dict>

<key>Active</key>

<true/>

<key>BSD Name</key>

<string>fw0</string>

<key>IOBuiltin</key>

<true/>

<key>IOInterfaceType</key>

<integer>144</integer>

<key>IOInterfaceUnit</key>

<integer>0</integer>

<key>IOMACAddress</key>

<data>

AJDmBRUAJcE=

</data>

<key>IOPathMatch</key>

<string>IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/P0P1@1E/IOPCI2PCIBridge/pci10b9,5253@5,4/AppleFWOHCI/IOFireWireController/IOFireWireLocalNode/IOFireWireIP/IOFWInterface</string>

<key>SCNetworkInterfaceType</key>

<string>FireWire</string>

</dict>

</array>

</dict>

</plist>

 

 

I don't even know what en1 is, I only have one NIC and it's showing up in the profiler as en2.

[legionX]

anything guys?

[BigPimpin]

From the user's point of view it cannot be changed. If you're writing a network device driver it can be changed, but even then it's not so easy. The only reason you should be getting en2 is if en0 and en1 are already in use. Try running 'ifconfig' from a Terminal command line to see if they are. It seems very strange that fcp depends on a network interface name.

[legionX]

yes FCP won't start properly unless you have a functioning en0, which I do not. I had done this with 10.4.9 to get FCP working, but it doesn't seem to work with 10.5.2I ran IFCONFIG and this is what I gotlo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280stf0: flags=0<> mtu 1280fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 494 lladdr 00:90:e6:05:15:00:25:c1 media: autoselect <full-duplex> status: inactive supported media: autoselect <full-duplex>en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet6 fe80::21e:8cff:fe40:bb38%en2 prefixlen 64 scopeid 0x5 inet 100.100.100.101 netmask 0xffffff00 broadcast 100.100.100.255 ether 00:1e:8c:40:bb:38 media: autoselect status: active supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 100baseTX <half-duplex> 100baseTX <full-duplex> 1000baseT <half-duplex> 1000baseT <full-duplex>

[dawntodon]

funny. I think I'm having the same issue as you are. Has anyone figured this one out by now?

[smcpipint]

NetworkInterfaces.plist is regenerated on every boot, so far as I am aware.

 

One suggestion is an EFI string for the network interface. EFI studio will generate a default one, but if that doesn't work for you (don't understand why you don't have eno, and EFI studio might also not understand(!)), you might have to build one manually. There are various posts and guides on how to do that here, just search