LarryMartell Posted May 15, 2005 Report Share Posted May 15, 2005 I have a system I just upgraded from 9.0 to 10.1. Now after the upgrade I find that the Ethernet interface is not automatically started when I boot the system. I have to go into Control Center->Network and Internet->Monitor Connections and click on "Connect Ethernet" each time after a reboot to bring up the network interface. I've checked in Manage Connections->Options and "Start at Boot" is selected, but it seems it's being ignored. -larry Quote Link to comment Share on other sites More sharing options...
griptypethyne Posted May 15, 2005 Report Share Posted May 15, 2005 This isrelated to a thread I have just started "Network Devices - which is default". While trying to solve my problem I formed the impression that MCC -> Internet does not always match information from the ecommand line - for example the ifconfig command. It is not the first time that I have lost confidence in MCC. To answer your question - open /etc/sysconfig/network-scripts/ifcg-eth0 with a text editor and look for a line BOOT=YES. Quote Link to comment Share on other sites More sharing options...
streeter Posted May 15, 2005 Report Share Posted May 15, 2005 That should be ONBOOT=yes See man ifcfg Chris Quote Link to comment Share on other sites More sharing options...
LarryMartell Posted May 16, 2005 Author Report Share Posted May 16, 2005 The file already did have ONBOOT=YES But still the interface does not come up unless I explicitly start it. -larry Quote Link to comment Share on other sites More sharing options...
streeter Posted May 16, 2005 Report Share Posted May 16, 2005 Are you starting networking on boot? Type drakxservices as root (or go to system->services in the control centre) and make sure network is being run at startup. If it is: What make/model of card is it? Is the module getting loaded? (type lsmod and look for the module name - if unsure, we can tell you from the card type) Output of ifconfig before network is started Chris Quote Link to comment Share on other sites More sharing options...
Crashdamage Posted May 16, 2005 Report Share Posted May 16, 2005 I've had this same problem ever since I went to 10.1 - have to start the net connection manually, even though eth0 *supposedly* starts at boot, the nic card module loads, and ONBOOT=yes Never bothered me much since I normally only reboot after power outages, etc., but it is a curiosity I have found a cure for - but then, I haven't tried very hard, either. Anyway, point is it must be a fairly common problem. I'd like to know the fix, just to learn something. Quote Link to comment Share on other sites More sharing options...
LarryMartell Posted May 16, 2005 Author Report Share Posted May 16, 2005 Well, I've taken a step backwards. I deleted the connection and tried to re-add it. It says it added it OK, but now I cannot bring up the interface at all. If I try to bring it up it fails with the message: eth0: no IPv6 routers present I've tried re-installing the driver, but I still get this error. What did I do and I do I un-do it? But in answer to your questions: > Are you starting networking on boot? > Type drakxservices as root (or go to system->services in the control centre) > and make sure network is being run at startup. Yes, the network is set to start on boot. > If it is: > What make/model of card is it? 3COM 3c905B > Is the module getting loaded? (type lsmod and look for the module name - if > unsure, we can tell you from the card type) The 3c59x module is loaded. > Output of ifconfig before network is started eth0 Link encap:Ethernet HWaddr 00:50:04:99:4F:A2 inet addr:192.168.1.82 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::250:4ff:fe99:4fa2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3224 errors:0 dropped:0 overruns:0 frame:0 TX packets:144 errors:0 dropped:0 verruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2861916 (279.4 Kb) TX bytes:18921 (18.4 Kb) Interrupt:11 Base address:0x100 Thanks! -larry Quote Link to comment Share on other sites More sharing options...
LarryMartell Posted May 16, 2005 Author Report Share Posted May 16, 2005 I've had this same problem ever since I went to 10.1 - have to start the net connection manually, even though eth0 *supposedly* starts at boot, the nic card module loads, and ONBOOT=yes Never bothered me much since I normally only reboot after power outages, etc., but it is a curiosity I have found a cure for - but then, I haven't tried very hard, either. Anyway, point is it must be a fairly common problem. I'd like to know the fix, just to learn something. <{POST_SNAPBACK}> FYI, I have 2 10.1 systems. One is new hardware and it DOES start the interface at boot. The other, an older Dell, is the one giving me trouble. -larry Quote Link to comment Share on other sites More sharing options...
streeter Posted May 17, 2005 Report Share Posted May 17, 2005 According to ifconfig, the network IS up, and has been assigned an IP address... Try pinging eth0 from the same machine, then pinging the other machine. Post output of route -n Have a look at the pinned post at the top of the networking forum for a howto. Chris Quote Link to comment Share on other sites More sharing options...
aioshin Posted May 17, 2005 Report Share Posted May 17, 2005 eth0 Link encap:Ethernet HWaddr 00:50:04:99:4F:A2inet addr:192.168.1.82 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::250:4ff:fe99:4fa2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3224 errors:0 dropped:0 overruns:0 frame:0 TX packets:144 errors:0 dropped:0 verruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2861916 (279.4 Kb) TX bytes:18921 (18.4 Kb) it seems that you have IPV6 enables, did youreally mean that? if not, maybe you can try to disable ipv6 ion that interface by inserting the line NETWORKING_IPV6=no on /etc/sysconfig/network Quote Link to comment Share on other sites More sharing options...
LarryMartell Posted May 17, 2005 Author Report Share Posted May 17, 2005 OK, I've got this going. I read your excellent "simple net setup" guide, and I found that the MII_NOT_SUPPORTED line in ifcfg-eth0 was set to no, and the GATEWAYDEV line in /etc/sysconfig/network was not there at all. Once I set these properly all was well - the interface now starts automagically at boot. Thank you all (especially Streeter) for all the help! I couldn't have done it without you! -larry Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.