All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick <patrick@spacesurfer.com>
To: kuznet@ms2.inr.ac.ru
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel oops in tcp_ipv4.c
Date: Sun, 14 Jan 2001 20:05:05 +0000	[thread overview]
Message-ID: <3A620671.B6C15F01@spacesurfer.com> (raw)
In-Reply-To: <200101141946.WAA25337@ms2.inr.ac.ru>

kuznet@ms2.inr.ac.ru wrote:
> 
> Hello!
> 
> > Recently I tried 2.2.17, this kernel was up for about a month, before
> > there was a kernel oops. The syslog messages are:
> 
> This is caused by illegal setting of /proc/sys/net/ipv4/ip_local_port_range
> with kernels before 2.2.18.
> 
> Do not touch this value or change it to something reasonable,
> f.e. to one of values recommended in net/ipv4/tcp_ipv4.c
> 
> Alexey

You are right I had the range set to 16384-65535!
I have changed the high limit to 61000, that should be ok.
Is there any point in having the low limit above 1024?


regards,
Patrick

-- 
Patrick Mackinlay                                patrick@spacesurfer.com
ICQ: 59277981                                        tel: +44 7050699851
                                                     fax: +44 7050699852
SpaceSurfer Limited                          http://www.spacesurfer.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-14 20:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12 19:06 Kernel oops in tcp_ipv4.c Patrick
2001-01-14 19:46 ` kuznet
2001-01-14 20:05   ` Patrick [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-13 13:36 Patrick
     [not found] <200101132029.f0DKTla156931@saturn.cs.uml.edu>
2001-01-14 13:23 ` Patrick

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=3A620671.B6C15F01@spacesurfer.com \
    --to=patrick@spacesurfer.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pim@uknet.spacesurfer.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.