From: volodya@mindspring.com
To: Jeremiah Johnson <miah@netcis.com>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: Re: Re[6]: 2.4.9 UDP broke?
Date: Fri, 7 Sep 2001 13:32:47 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.20.0109071329370.8051-100000@node2.localnet.net> (raw)
In-Reply-To: <8638021391.20010907103407@netcis.com>
On Fri, 7 Sep 2001, Jeremiah Johnson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: MD5
>
> Hello volodya,
>
> If I enable both of these options though, UDP totally breaks for me.
> So its definitely something in there. Maybe I'll get some time and
> test to see which option is actually doing the breaking.
After some testing: 2.4.6 and 2.4.8 require both of these options be
disabled. 2.4.9 wants them enabled.
Furthemore: after I turned on these option on the only 2.4.9 kernel I
currently have I was able to ping all machines on the network (and they
were able to ping each other). However, before (when options were turned
off) none of the machines on the network could ping each other with
packets of size 6000, though I could see them with tcpdump.
<whine>
tulip worked so great earlier, why mess with it ?
</whine>
Vladimir Dergachev
>
> Wednesday, September 05, 2001, 1:28:39 PM, you wrote:
>
> vmc> On Tue, 4 Sep 2001, Jeremiah Johnson wrote:
>
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: MD5
> >>
> >> Hello volodya,
> >>
> >> I found the answer to the problem today. It has to do with a bug in
> >> one of these options:
> >>
> >> CONFIG_TULIP_MWI
> >> CONFIG_TULIP_MMIO
> >>
>
> vmc> You are absolutely correct - once I enabled both of these it works
> vmc> great. My guess is that whoever tested the patches was concentrated on the
> vmc> case when options were enabled.
>
> vmc> Vladimir Dergachev
>
> - --
> Best regards,
> Jeremiah mailto:miah@netcis.com
>
> -----BEGIN PGP SIGNATURE-----
> Version: 2.6
>
> iQEVAwUAO5kFFJHTj7BlqKb5AQG+9ggAnKz03bYjsYYSsrINzUTKEFCtWs2bRP0t
> sGsIZ55rpi4FH9QFbJGIzxih6C5Mf3p1IJU2fUEP5ci4ddEDJbWbAia/4yz6S2qd
> hAe3pjep/Oy1XBky8PKxIpLkOJMAgFgqeM9aguwFVCuhXxZBvK6NNPaozqZ/nYHl
> 9EM8/kuwfNONaJxYnduqkCRPKdCUPxPZcuwd56Wt3JvJ6meUW249pGEBJhFM63Qe
> +esn3TweBeYj5M80mYcU0CunDRr3D0ABMrdtApCUv0FMIP7ke0LTCQBeZZrUtajW
> +k/gDEySN3tRIuCUltYZ5SYMxtxFZ6eYgerwyhr3s8iKfD+7Tk1BFg==
> =/5Uc
> -----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-07 17:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 6:20 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 ` Re[2]: " volodya
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 [this message]
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.0109071329370.8051-100000@node2.localnet.net \
--to=volodya@mindspring.com \
--cc=jgarzik@mandrakesoft.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
all inboxes | Powered by JetHome®