lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 28 Oct 2010 10:51:32 -0400
From:	Chuck Lever <chuck.lever@...cle.com>
To:	Simon Horman <horms@...ge.net.au>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, netdev@...r.kernel.org,
	bugzilla-daemon@...zilla.kernel.org,
	bugme-daemon@...zilla.kernel.org, mpetersen@...k6.com
Subject: Re: [Bugme-new] [Bug 20772] New: ip= nfsaddrs= stopped working


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@...zilla.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@...ux-foundation.org
>>>>       ReportedBy: mpetersen@...k6.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.

-- 
Chuck Lever
chuck[dot]lever[at]oracle[dot]com




--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ