From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] SOLVED: uml "ip header error" for large (fragmented) udp packets
Date: Mon, 11 Oct 2004 21:53:50 -0400 [thread overview]
Message-ID: <25642.1097546030@marajade.sandelman.ottawa.on.ca> (raw)
In-Reply-To: Message from BlaisorBlade <blaisorblade_spam@yahoo.it> of "Tue, 12 Oct 2004 03:10:59 +0200." <200410120310.59432.blaisorblade_spam@yahoo.it>
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "BlaisorBlade" == BlaisorBlade <blaisorblade_spam@yahoo.it> writes:
BlaisorBlade> Sadly there is a problem: since we use TAP and emulate
BlaisorBlade> whole Ethernet frames, the code does not allow to
BlaisorBlade> increase the MTU to > 1500 bytes. I think this cannot
BlaisorBlade> be fixed currently, but if you think this is wrong,
BlaisorBlade> please let us now.
I'm certain that we could go as big as 2047 without a problem.
It won't work when communicating outside the host, mind you.
Beyond 2048, we have to use 802 SNAP encapsulation. I think that Linux
is jumbo ethernet ready, but I've never been there, so I don't know what
might be involved.
- --
] "Elmo went to the wrong fundraiser" - The Simpson | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr@xelerance.com http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBQWs5LYqHRg3pndX9AQFPpQP7Bj9cO0Mbm6/Ai0YHJ3bCXMSVko+IvIlq
GF1lFDQx6TEPtFtsSm0qMf8kvOnHV0+oJ/M21e1lSnKsgzltjtjs+1sGB8RKzzJi
iCn6mXkfEGQhc2oGE4isKUmGrMxZPVhXiwq/1MYAV+1ONuCPG77v7UMqD9fG5GOP
XmDV4uTykio=
=MJ+I
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-10-12 1:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-03 2:36 [uml-devel] uml "ip header error" for large (fragmented) udp packets Lars Ellenberg
2004-10-03 15:11 ` BlaisorBlade
2004-10-03 19:29 ` Lars Ellenberg
2004-10-04 11:07 ` Gerd Knorr
2004-10-04 11:56 ` Henrik Nordstrom
2004-10-06 17:50 ` BlaisorBlade
2004-10-06 18:48 ` Lars Ellenberg
2004-10-06 20:35 ` Andi Kleen
2004-10-06 21:48 ` Lars Ellenberg
2004-10-07 18:41 ` BlaisorBlade
2004-10-07 18:41 ` BlaisorBlade
2004-10-07 20:24 ` Lars Ellenberg
2004-10-11 17:55 ` Lars Ellenberg
2004-10-12 0:03 ` [uml-devel] SOLVED: " Lars Ellenberg
2004-10-12 0:11 ` Andi Kleen
2004-10-12 1:10 ` BlaisorBlade
2004-10-12 1:53 ` Michael Richardson [this message]
2004-10-15 15:25 ` [uml-devel] larger MTU _does_ work Lars Ellenberg
2004-10-12 0:27 ` [uml-devel] SOLVED: uml "ip header error" for large (fragmented) udp packets BlaisorBlade
2004-10-12 14:00 ` Lars Ellenberg
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=25642.1097546030@marajade.sandelman.ottawa.on.ca \
--to=mcr@sandelman.ottawa.on.ca \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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