[522] in linux-net channel archive
Re: CONFIG_INET_SNARL: What for?
daemon@ATHENA.MIT.EDU (Matthias Urlichs)
Fri Jun 16 15:15:16 1995
To: submit-linux-dev-net@ratatosk.yggdrasil.com
From: urlichs@smurf.noris.de (Matthias Urlichs)
Date: 16 Jun 1995 20:16:43 +0200
In linux.dev.net, article <95Jun14.104422edt.607019@enfm.utcc.utoronto.ca>,
"C. Harald Koch" <harald@enfm.utcc.utoronto.ca> writes:
>
> > You cannot tell the size of the block from the address. ifconfig knows
> > the correct netmask and that's what should be used.
>
> If you send a full-size packet packet on FDDI (with an 4352 byte MTU), and
> it crosses onto an Ethernet, (with a 1500 byte MTU), Then the router must
> fragment the packet into three pieces to deliver it.
>
So you have a router. So you have a route. So you can add the MTU to the
route in newer kernels. Problem solved; you just add two routes to the
router, one for the Ethernet with a MTU of 1500 and a default route with
the MTU of 576 or whatever.
> [ Path MTU ]
> This is the current best way to handle the problem of determining the MTU to
> use to send to a particular destination.
True. Now we only need somebody to implement it...
--
He who steps on others to reach the top has good balance.
--
Matthias Urlichs \ XLink-POP Nürnberg | EMail: urlichs@smurf.noris.de
Schleiermacherstraße 12 \ Unix+Linux+Mac | Phone: ...please use email.
90491 Nürnberg (Germany) \ Consulting+Networking+Programming+etc'ing 42
PGP: 1B 89 E2 1C 43 EA 80 44 15 D2 29 CF C6 C7 E0 DE
Click <A HREF="http://smurf.noris.de/~urlichs/finger">here</A>.
