No Ethernet Connection At Boot

Mark Sargent powderkeg at snow.email.ne.jp
Sun Mar 20 16:50:02 UTC 2005


Craig White wrote:

>On Mon, 2005-03-21 at 00:04 +0900, Mark Sargent wrote:
>  
>
>>Mark Sargent wrote:
>>
>>    
>>
>>>Craig White wrote:
>>>
>>>      
>>>
>>>>On Sun, 2005-03-20 at 17:59 +0900, Mark Sargent wrote:
>>>> 
>>>>
>>>>        
>>>>
>>>>>Hi All,
>>>>>
>>>>>came home 2 nights ago. Booted up, but, internet connection was 
>>>>>down. Asked sharemate, who said he didn't un why(but said it was the 
>>>>>same for him, apparently). Anyway, after some time, he said he had 
>>>>>fixed it. But, it still wouldn't connect. I then 
>>>>>deactivated/reactivated the connection and success. Now, when I boot 
>>>>>up, I get the sane occurrence, and have to deactivate/reactivate the 
>>>>>connection. I'm not seeing errors in boot.log, so what could this 
>>>>>be..? This is happening only with eth0(internet/lan nic), eth1 is 
>>>>>okay, as a client pc can obtain an ip through dhcp on this machine. 
>>>>>Cheers.
>>>>>
>>>>>PC has 2 nics
>>>>>eth0 is static set to 192.168.0.17
>>>>>eth1 is static set to 192.168.1.1
>>>>>  
>>>>>          
>>>>>
>>>>---
>>>>is ONBOOT = YES
>>>>
>>>>cat /etc/sysconfig/network-scripts/eth0
>>>>
>>>>does
>>>>service network restart
>>>>
>>>>turn it on or off?
>>>>
>>>>I would think that /var/log/messages and /var/log/dmesg might be better
>>>>places to look for errors with respect to the eth0 interface at bootup
>>>>
>>>>Craig
>>>>
>>>> 
>>>>
>>>>        
>>>>
>>>Hi All,
>>>
>>>Craig,
>>>
>>>      
>>>
>>>>cat /etc/sysconfig/network-scripts/eth0
>>>>        
>>>>
>>>doesn't exist
>>>
>>>service network restart brought me to where I didn't have a connection 
>>>again, and had to deactivate/reactivate again. Will check those logs 
>>>real soon. Cheers.
>>>
>>>Mark Sargent
>>>
>>>      
>>>
>>Hi All,
>>
>>I can ping, though and I'm getting an IP, just can't access the net or 
>>mail. Weird. Cheers
>>    
>>
>---
>sorry... s/h/b
>
>cat /etc/sysconfig/network-scripts/ifcfg-eth0
>
>can't ping across net or get off lan because you need a 'default
>gateway' setup might put these in the above mentioned ifcfg-ethX
>
>On a multi-homed system, I tend to not put default gateway in any
>network device configuration but rather put it
>into /etc/sysconfig/network
>
>I can't tell what your default gateway should be 
>  
>
>>>>eth0 is static set to 192.168.0.17
>>>>eth1 is static set to 192.168.1.1
>>>>        
>>>>
>
>but would guess that it is either 192.168.0.1 or 192.168.0.254 from the
>notion that if eth0 is down, you aren't getting anywhere.
>
>if that is the case...
>
>edit /etc/sysconfig/network
>
>add the lines...
>
>GATEWAYDEV='eth0'
>GATEWAY='192.168.0.1' #or whatever the proper address should be
>
>and then - 'service network restart'
>
>and you're good to go
>
>Craig
>
>  
>
Hi All,

problem solved. I retraced my steps of some changes I made when the last 
time things worked and realized I'd put 192.168.1.1 as the Default 
gateway adderess for eth1. This must have been confusing something, as 
removing the entry solved it. Cheers.

here are my settings for eth0,

[root at localhost log]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet
NETMASK=255.255.255.0
IPADDR=192.168.0.17
USERCTL=no
PEERDNS=yes
GATEWAY=192.168.0.1
IPV6INIT=no



Mark Sargent




More information about the fedora-list mailing list