Determining IP information for lo... failed

Sam Varshavchik mrsam at courier-mta.com
Sat Oct 13 02:35:55 UTC 2007


Peter Horst writes:

> Sam Varshavchik wrote:
>> Peter Horst writes:
>>
>> > Sam Varshavchik wrote:
>> >> Peter Horst writes:
>> >>
>> >> [snip]
>> >>
>> >> You probably have the BOOTP environment variable set somewhere. Grep for 
>> >> BOOTP in /etc/sysconfig/network and /etc/sysconfig/network-scripts/*
>> >>
>> >> You'll find several references to the BOOTP environment variables. You're 
>> >> looking for something that sets it.
>> >>   
>> > 
>> > Hm. /etc/sysconfig/network-scripts/ifup has:
>>
>> What about -- as I said -- /etc/sysconfig/network?
>>
>> ifup is just a shell script. Noone can really debug this remotely for you. 
>> You'll have to step through the ifup script yourself and figure out why it 
>> wants to bring the loopback interface up with dhcp -- which is what your 
>> problem is.
>>
>>   
> 
> the "network" script is:
> 
> NETWORKING=yes
> HOSTNAME=obtunded.depaulacs.org
> GATEWAY=192.168.10.1
> GATEWAYDEV=""
> BOOTPROTO=dhcp
> 
> Is this "BOOTPROTO" the same as the "BOOTP" you're referring to? 

Why, yes, BOOTPROTO defaults to BOOTP, if it's set, read the ifup script. 
Get rid of this. You may need to run system-config-network, and flip your 
actual network interface to explicitly use dhcp, if that's what you need.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20071012/1506bfb5/attachment-0001.sig>


More information about the fedora-list mailing list