Bug 20772 - ip= nfsaddrs= stopped working
Summary: ip= nfsaddrs= stopped working
Status: RESOLVED OBSOLETE
Alias: None
Product: Networking
Classification: Unclassified
Component: IPV4 (show other bugs)
Hardware: All Linux
: P1 high
Assignee: Stephen Hemminger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-19 18:20 UTC by mpetersen
Modified: 2012-08-14 11:17 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.33, 2.6.32, 2.6.26
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description mpetersen 2010-10-19 18:20:13 UTC
I can no longer set a static IP address using either ip= or nfsaddr=, ie ip=192.168.0.42:192.168.0.69:255.255.255.0:testhost:eth0:none has no effect, and DHCP is still attempted.

Even if I undefine IP_PNP_DHCP IP_PNP_BOOTP and IP_PNP_RARP in the config (but leave IP_PNP,) the kernel seems to ignore the static IP settings and try to get a an IP address with DHCP somehow.
Comment 1 Andrew Morton 2010-10-19 19:10:30 UTC
(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Tue, 19 Oct 2010 18:20:15 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=20772
> 
>            Summary: ip= nfsaddrs= stopped working
>            Product: Networking
>            Version: 2.5
>     Kernel Version: 2.6.33, 2.6.32, 2.6.26
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: IPV4
>         AssignedTo: shemminger@linux-foundation.org
>         ReportedBy: mpetersen@peak6.com
>         Regression: Yes
> 
> 
> I can no longer set a static IP address using either ip= or nfsaddr=, ie
> ip=192.168.0.42:192.168.0.69:255.255.255.0:testhost:eth0:none has no effect,
> and DHCP is still attempted.
> 
> Even if I undefine IP_PNP_DHCP IP_PNP_BOOTP and IP_PNP_RARP in the config
> (but
> leave IP_PNP,) the kernel seems to ignore the static IP settings and try to
> get
> a an IP address with DHCP somehow.
>
Comment 2 Horms 2010-10-28 08:35:06 UTC
On Tue, Oct 19, 2010 at 12:09:38PM -0700, Andrew Morton wrote:
> 
> (switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
> 
> On Tue, 19 Oct 2010 18:20:15 GMT
> bugzilla-daemon@bugzilla.kernel.org wrote:
> 
> > https://bugzilla.kernel.org/show_bug.cgi?id=20772
> > 
> >            Summary: ip= nfsaddrs= stopped working
> >            Product: Networking
> >            Version: 2.5
> >     Kernel Version: 2.6.33, 2.6.32, 2.6.26
> >           Platform: All
> >         OS/Version: Linux
> >               Tree: Mainline
> >             Status: NEW
> >           Severity: high
> >           Priority: P1
> >          Component: IPV4
> >         AssignedTo: shemminger@linux-foundation.org
> >         ReportedBy: mpetersen@peak6.com
> >         Regression: Yes
> > 
> > 
> > I can no longer set a static IP address using either ip= or nfsaddr=,
> > ie ip=192.168.0.42:192.168.0.69:255.255.255.0:testhost:eth0:none has no
> > effect, and DHCP is still attempted.
> > 
> > Even if I undefine IP_PNP_DHCP IP_PNP_BOOTP and IP_PNP_RARP in the
> > config (but leave IP_PNP,) the kernel seems to ignore the static IP
> > settings and try to get a an IP address with DHCP somehow.

Hi,

I believe that the problem is that there is a minor syntax error in the
configuration parameter. Specifically there should be two colons between
192.168.0.69 and 255.255.255.0 or between 192.168.0.42 and 192.168.0.69.

As it stands the settings are:

	my address	192.168.0.42
	server address	192.168.0.69
	gateway		255.255.255.0
	netmask		testhost
	hostname	eth0
	interface	none

I believe it is the interface=none that is killing any IP configuration
by the kernel as no such interface exists.
Comment 3 Chuck Lever 2010-10-28 14:34:36 UTC
On Oct 27, 2010, at 6:31 PM, Simon Horman wrote:

> On Tue, Oct 19, 2010 at 12:09:38PM -0700, Andrew Morton wrote:
>> 
>> (switched to email.  Please respond via emailed reply-to-all, not via the
>> bugzilla web interface).
>> 
>> On Tue, 19 Oct 2010 18:20:15 GMT
>> bugzilla-daemon@bugzilla.kernel.org wrote:
>> 
>>> https://bugzilla.kernel.org/show_bug.cgi?id=20772
>>> 
>>>           Summary: ip= nfsaddrs= stopped working
>>>           Product: Networking
>>>           Version: 2.5
>>>    Kernel Version: 2.6.33, 2.6.32, 2.6.26
>>>          Platform: All
>>>        OS/Version: Linux
>>>              Tree: Mainline
>>>            Status: NEW
>>>          Severity: high
>>>          Priority: P1
>>>         Component: IPV4
>>>        AssignedTo: shemminger@linux-foundation.org
>>>        ReportedBy: mpetersen@peak6.com
>>>        Regression: Yes
>>> 
>>> 
>>> I can no longer set a static IP address using either ip= or nfsaddr=,
>>> ie ip=192.168.0.42:192.168.0.69:255.255.255.0:testhost:eth0:none has no
>>> effect, and DHCP is still attempted.
>>> 
>>> Even if I undefine IP_PNP_DHCP IP_PNP_BOOTP and IP_PNP_RARP in the
>>> config (but leave IP_PNP,) the kernel seems to ignore the static IP
>>> settings and try to get a an IP address with DHCP somehow.
> 
> Hi,
> 
> I believe that the problem is that there is a minor syntax error in the
> configuration parameter. Specifically there should be two colons between
> 192.168.0.69 and 255.255.255.0 or between 192.168.0.42 and 192.168.0.69.
> 
> As it stands the settings are:
> 
>       my address      192.168.0.42
>       server address  192.168.0.69
>       gateway         255.255.255.0
>       netmask         testhost
>       hostname        eth0
>       interface       none
> 
> I believe it is the interface=none that is killing any IP configuration
> by the kernel as no such interface exists.

Did "interface=none" work in 2.6.36 and earlier?
Comment 4 Chuck Lever 2010-10-28 14:52:09 UTC
On Oct 28, 2010, at 10:32 AM, Chuck Lever wrote:

> 
> On Oct 27, 2010, at 6:31 PM, Simon Horman wrote:
> 
>> On Tue, Oct 19, 2010 at 12:09:38PM -0700, Andrew Morton wrote:
>>> 
>>> (switched to email.  Please respond via emailed reply-to-all, not via the
>>> bugzilla web interface).
>>> 
>>> On Tue, 19 Oct 2010 18:20:15 GMT
>>> bugzilla-daemon@bugzilla.kernel.org wrote:
>>> 
>>>> https://bugzilla.kernel.org/show_bug.cgi?id=20772
>>>> 
>>>>          Summary: ip= nfsaddrs= stopped working
>>>>          Product: Networking
>>>>          Version: 2.5
>>>>   Kernel Version: 2.6.33, 2.6.32, 2.6.26
>>>>         Platform: All
>>>>       OS/Version: Linux
>>>>             Tree: Mainline
>>>>           Status: NEW
>>>>         Severity: high
>>>>         Priority: P1
>>>>        Component: IPV4
>>>>       AssignedTo: shemminger@linux-foundation.org
>>>>       ReportedBy: mpetersen@peak6.com
>>>>       Regression: Yes
>>>> 
>>>> 
>>>> I can no longer set a static IP address using either ip= or nfsaddr=,
>>>> ie ip=192.168.0.42:192.168.0.69:255.255.255.0:testhost:eth0:none has no
>>>> effect, and DHCP is still attempted.
>>>> 
>>>> Even if I undefine IP_PNP_DHCP IP_PNP_BOOTP and IP_PNP_RARP in the
>>>> config (but leave IP_PNP,) the kernel seems to ignore the static IP
>>>> settings and try to get a an IP address with DHCP somehow.
>> 
>> Hi,
>> 
>> I believe that the problem is that there is a minor syntax error in the
>> configuration parameter. Specifically there should be two colons between
>> 192.168.0.69 and 255.255.255.0 or between 192.168.0.42 and 192.168.0.69.
>> 
>> As it stands the settings are:
>> 
>>      my address      192.168.0.42
>>      server address  192.168.0.69
>>      gateway         255.255.255.0
>>      netmask         testhost
>>      hostname        eth0
>>      interface       none
>> 
>> I believe it is the interface=none that is killing any IP configuration
>> by the kernel as no such interface exists.
> 
> Did "interface=none" work in 2.6.36 and earlier?

OK, I see that's a dumb question.

I made changes to this area of code in 2.6.37.  I was responding to the bug report above, and not Simon's observation that there was possibly a syntax error.

Sorry for the noise.
Comment 5 mpetersen 2012-08-14 11:17:25 UTC
I am currently out of the office and will return on August 20.  If you require immediate UNIX assistance please contact Unix-Administrators, otherwise I will reply upon my return.



Thanks,

Mark Petersen
______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email

Note You need to log in before you can comment on or make changes to this bug.