Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Re: No ip address on eth0 after installing from perfSONAR-PS 3.3.1 NetInstall CD

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Re: No ip address on eth0 after installing from perfSONAR-PS 3.3.1 NetInstall CD


Chronological Thread 
  • From: Joseph Bernard <>
  • To: "" <>
  • Subject: Re: [perfsonar-user] Re: No ip address on eth0 after installing from perfSONAR-PS 3.3.1 NetInstall CD
  • Date: Thu, 17 Apr 2014 15:48:18 +0000
  • Accept-language: en-US

I get the same problem setting IPv4 to "Static" and disabling IPv6 during
setup.

Thanks,
Joseph B.

On Apr 17, 2014, at 11:34 AM, Jeremy Palmer
<>
wrote:

> I'm guessing this is due to the fact that I set IPv4 to "Static" and IPv6
> to "Automatic" during the setup.
>
> Jeremy Palmer
> Senior Network Engineer
> ViaWest, Inc.
> Office: 720.891.1045
> Fax: 303-874-5236
> http://www.viawest.com
>
> On 4/2/2014 3:17 PM, Jeremy Palmer wrote:
>> FYI, this bug still exists in 3.3.2. I just installed a new psToolkit box
>> using
>> the image:
>> pS-Performance_Toolkit-3.3.2-NetInstall-x86_64.iso
>>
>> I'm having the exact same issue as described in my email last July (below).
>> Once OS was installed, I had to edit ifcfg-eth0 and change "dhcp" to
>> "static"
>> even though I specified static IPv4 during setup.
>>
>> Jeremy Palmer
>> Senior Network Engineer
>> ViaWest, Inc.
>> Office: 720.891.1045
>> Fax: 303-874-5236
>> http://www.viawest.com
>>
>> On 8/23/2013 12:35 PM, Jeremy Palmer wrote:
>>> Just ran through a clean install using the latest 3.3.1 Netinstall i386
>>> CD image:
>>> pS-Performance_Toolkit-3.3.1-NetInstall-i386.iso
>>>
>>> After the install was completed and the server booted into
>>> CentOS/Toolkit3.3.1,
>>> there is no IP address on eth0.
>>>
>>> The issue appears to be the fact that the install put the following line
>>> in
>>> /etc/sysconfig/network-scripts/ifcfg-eth0 even though I selected Static
>>> during
>>> the install process:
>>> BOOTPROTO="dhcp"
>>>
>>> Otherwise all the correct static IP settings appear in the ifcfg-eth0 file
>>> (IPADDR, GATEWAY, DNS1, etc).
>>>
>>> I did notice that the network config screen is different when using the
>>> Toolkit
>>> 3.3.1 image compared to the Toolkit 3.3 image. Perhaps something changed
>>> between
>>> the two images?
>>>
>>> To fix this I edited the ifcfg-eth0 file and changed "dhcp" to "static".
>>> I then
>>> did a 'service network restart' to bring it up with the static IP info.
>>>
>>> Jeremy Palmer
>>> Senior Network Engineer
>>> ViaWest, Inc.
>>> Office: 720.891.1045
>>> Fax: 303-874-5236
>>> http://www.viawest.com
>>>
>>




Archive powered by MHonArc 2.6.16.

Top of Page