Why is option 1, setting "Max MTU size" as a variable in a config file
(maybe not auth.props), not an option which can be done quickly?
Normally this would only means adding a couple of code lines to the
program which sets the MTU size.
Something which could be done in a day or so.
Kind regards,
Ivar
ottomeister wrote:
On 9/7/06, Ivar Janmaat <[EMAIL PROTECTED]> wrote:
1. Sun can adds a "Max MTU size" option to auth.props
2. Sun fixes RFE/bug 6457500 so we can use *.parms files to set Max MTU
size.
3. Sun makes new firmware with which we can set the MTU size options on
the Sun Ray manually.
4. Sun develops something called MTU discovery between Sun Ray Server
and Sun Ray
We would prefer options 1 or 2 since this is probably fastest to
implement and will be sufficient for our needs.
For the future we think option 4 will be great.
Option 3 we don't like since we want the Sun Ray as stateless as
possible.
The important questions is: Which one can be done quickly?
Number 2 is probably the option that could be delivered the earliest.
Number 3 will probably happen but it's very unlikely that a change
that large would be considered for inclusion in a patch. It would have
to wait for a full release.
Number 4 might happen but there are many networks where PMTU
discovery does not work, usually because of ICMP messages not
being generated or being blocked or dropped or otherwise lost in the
network.
OttoM.
__
ottomeister
Disclaimer: These are my opinions. I do not speak for my employer.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
