How would you go about customizing the operation of the
tcp/ip driver in a Solaris 2.x kernel, such as illustrated by
the following 2 fictitious examples
ex.1 - all outgoing ip packets shall have the "high priority" and
"low delay" bits set, and in addition, time-to-live shall be
incremented by 4 unless wrap-around would be caused.
ex.2 - all outgoing ip packets on interface le1 shall be subject
to loose source routing before being allowed to proceed.
The idea is that you want to exercise greater control over the ip
layer from user level processes.
Restrictions: kernel sources are presumed unavailable (pricey!!),
therefore, non-standard solutions that make use of new ioctl's or
newly defined system calls do not count.
Solutions using data link access, and a user-level tcp/ip stack
cannot be accepted, either.
Why do I get the impression that solaris 2.x leaves little space for
maneuver when it comes to tcp/ip network management?