From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 75221] New: CONFIG_PROC_SYSCTL is required for networking
Date: Thu, 1 May 2014 09:15:15 -0700 [thread overview]
Message-ID: <20140501091515.2371058e@nehalam.linuxnetplumber.net> (raw)
Begin forwarded message:
Date: Thu, 1 May 2014 03:17:32 -0700
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 75221] New: CONFIG_PROC_SYSCTL is required for networking
https://bugzilla.kernel.org/show_bug.cgi?id=75221
Bug ID: 75221
Summary: CONFIG_PROC_SYSCTL is required for networking
Product: Networking
Version: 2.5
Kernel Version: 3.14.2
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: shemminger@linux-foundation.org
Reporter: stefan@konink.de
Regression: No
I am in the proces of building an embedded kernel which I wanted to limit in
both functionality and memory. For this reason I disabled CONFIG_PROC_SYSCTL. I
have figured out the hard way that this functionality implements the successful
randomisation of source ports, it might be responsible for the initialisation
of net.ipv4.ip_local_port_range.
Effectively, booting a kernel with ip=dhcp works. Ping-pong (ICMP) to and from
an address works. DNS queries (UDP/53) don't because the source port remains 0,
a connection to a typical webserver also seems to result in a no reply
situation.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2014-05-01 16:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140501091515.2371058e@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).