From: volodya@mindspring.com
To: Jeremiah Johnson <miah@netcis.com>
Cc: Steve Kieu <haiquy@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Re[2]: 2.4.9 UDP broke?
Date: Sun, 2 Sep 2001 22:25:44 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.20.0109022221340.14074-100000@node2.localnet.net> (raw)
In-Reply-To: <67111542696.20010831084646@netcis.com>
On Fri, 31 Aug 2001, Jeremiah Johnson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: MD5
>
> Hello Steve,
>
> Thursday, August 30, 2001, 10:50:08 PM, you wrote:
>
> SK> --- Jeremiah Johnson <miah@netcis.com> wrote: >
> SK> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: MD5
> >>
> >> Hello linux-kernel,
> >>
> >> I am having very strange problems with 2.4.9 and
> >> UDP. Basically,
> >> anything using UDP wont work. Anything using
> >> TCP/ICMP works fine.
>
> SK> May be it is not the kernel, I dont know but in my box
> SK> it works as normal
>
> SK> (I can use speakfreely ; it uses UDP and otehr program
> SK> too)
>
> Well considering the only thing I changed in my configuration is the
> kernel, I think its a problem there. Went from 2.4.3-ac? to 2.4.9.
> System is RedHat 7.1.. Maybe it has something to do with RedHats
> inclusion of a broken compiler, I'll have to check on that when I get
> into the office.
I had a very similar experience. In my case it turned out that for some
reason no UDP packets above 5524 would come through (try pinging with
larger than default packet sizes). The solution was to restrict NFS to
5000 (actually 4096) size packets. I have not been able to figure out the
cause of this yet. (and yes, tcpdump was able to see them fine).
Vladimir Dergachev
>
> I do have 2.4.9 working fine on other systems too. Strange.
> - --
> Best regards,
> Jeremiah mailto:miah@netcis.com
>
> -----BEGIN PGP SIGNATURE-----
> Version: 2.6
>
> iQEVAwUAO4+xapHTj7BlqKb5AQE/sQf+MNVYf4Dv4KRS2V3jiexwdlwpAUyNGUDp
> VUli3po/IuoBsiz0zubCK0tFSVMB/2o24kYzAFIBKajrQP7uVVSUqbQzWpwWazpg
> Vu3wAnHx3oPBpWmF3fxrMGjC/1g4FKUAnmBKne8VQOPaEVy+iUxZy5VQhXYXoBs0
> O98+7VzgxjPI7txEmmqcJdLJHy7hQSuKvN9+FYvDmueeWeZV909NuH9P3Estp00c
> HtuKAb57wkea8CcoZlknr+Iuei7geRAti4iGrGMYEVFNTYQxVVSC/FGM+T4UP1ia
> R08TX47WHR2sucVatXv8oT/ixyepo82D0xIHbBltYLB8yqC/JxkDYA==
> =5GKB
> -----END PGP SIGNATURE-----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2001-09-03 2:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 6:20 2.4.9 UDP broke? Jeremiah Johnson
2001-08-31 5:50 ` Steve Kieu
2001-08-31 15:46 ` Re[2]: " Jeremiah Johnson
2001-08-31 18:34 ` J Sloan
2001-09-03 2:25 ` volodya [this message]
2001-09-05 2:19 ` Re[4]: " Jeremiah Johnson
2001-09-05 3:54 ` volodya
2001-09-05 14:15 ` Jeremiah Johnson
2001-09-05 20:28 ` volodya
2001-09-07 17:34 ` Re[6]: " Jeremiah Johnson
2001-09-07 17:32 ` volodya
2001-09-01 10:32 ` Matthias Andree
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=Pine.LNX.4.20.0109022221340.14074-100000@node2.localnet.net \
--to=volodya@mindspring.com \
--cc=haiquy@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miah@netcis.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 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).