From: L A Walsh <lartc@tlinx.org>
To: lartc@vger.kernel.org
Subject: routing & conversion between 2 networks using different packet sizes (1500 & 9000 bytes)
Date: Wed, 23 Nov 2022 23:10:07 +0000 [thread overview]
Message-ID: <637EA84F.9070802@tlinx.org> (raw)
My computers and switches handle 9k jumbo packets and file transfers go
faster
between 2 computers using them, however, ran into a slight snag -- IOT
(Internet of Things): things like media devices, TV, receiver, disc
player -- all talk ethernet
@ 1.5k packet size.
So I'm wondering, if I setup the devices on a separate subnet and route
traffic from
my desktop into my server, and have a route to the devices that uses
1.5k packets, will the networking stack automatically marshal the 9k
into 1.5k packets for data that gets sent to the 1.5k subnet? I'm
guessing it won't automatically do the reverse, but that's not so
important, since sending 1.5k packets to a 9k destination will just use
the smaller packets -- its only when I send from a 9k packet enabled
network port to a 1.5k-talking device that I think problems occur
(occasional random data loss and connection resets). Does it sound
like that would work?
I currently have a bridge on the server between 2 networks, one w/9k
packets and the other with 1.5k packets and that seems to work fine --
I'm hoping that's not a coincidence(?)
Thanks!
next reply other threads:[~2022-11-23 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 23:10 L A Walsh [this message]
2022-11-24 2:17 ` routing & conversion between 2 networks using different packet sizes (1500 & 9000 bytes) Grant Taylor
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=637EA84F.9070802@tlinx.org \
--to=lartc@tlinx.org \
--cc=lartc@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