I know there are many posts on this subject because I have combed through them but nothing really to solve my issue. I still don't know how find out if this is a problem that requires a driver or extension. So far I tried dmesg | grep eth0 (and e100) but nothing comes back.
I am using a fork of microcore called mine os+ for hosting minecraft server. I had a lot of succes on vmware to install and run so I ran out and got myself a dedicated server and since it was quite the custom install, they gave me remote access through DRAC for a Dell PowerEdge R410, Bios v 1.1.5, I don't know details on the network adapter, but I've been told that the eth0 port is up and ready for usage, I have 5 ip addresses.
ifconfig only returned lo, now it returns dummy0 and lo, looks like support tried a few things to make it work, looks like scripts for configuration files like /etc/resolv.conf. and commands like route add default gw xx.xx.xx.xx
I've read that there are no configuration files in tiny core, per se.
Support there suggests using ifup eth0 and proper configuration fies are populated but ifup: command not found :-P
Pretty lost at this point, but I'm invested to make this work.