Skip to contentSkip to conversation

New: ip= nfsaddrs= stopped working

Bugme-new Andrew Morton 3 participants 4 messages Oct 19, 2010 – Oct 28, 2010 1 message not in the archive

Subsystems (2)
Networking Network drivers
lore
Share & tools
lore

Andrew Morton

author
#1 lore raw
In reply to a message not in the archive

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface).

Quoted 26 lines · On Tue, 19 Oct 2010 18:20:15 GMT [email protected] 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: [email protected]
        ReportedBy: [email protected]
        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.

#2 lore raw
Quoted 32 lines · Andrew Morton

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface).

Quoted 25 lines · On Tue, 19 Oct 2010 18:20:15 GMT [email protected] 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: [email protected]
        ReportedBy: [email protected]
        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.

#3 lore raw
Quoted 49 lines · Simon Horman
Quoted 32 lines · Andrew Morton

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface).

Quoted 25 lines · On Tue, 19 Oct 2010 18:20:15 GMT [email protected] 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: [email protected]
ReportedBy: [email protected]
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
Quoted 2 lines

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?

Signature · 2 lines
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
#4 lore raw
Quoted 52 lines · Chuck Lever
Quoted 49 lines · Simon Horman
Quoted 32 lines · Andrew Morton

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface).

Quoted 25 lines · On Tue, 19 Oct 2010 18:20:15 GMT [email protected] 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: [email protected]
ReportedBy: [email protected]
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
Quoted 4 lines
Quoted 2 lines

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.

Signature · 2 lines
Chuck Lever
chuck[dot]lever[at]oracle[dot]com