Bill Sommerfeld writes: > If the management processor is picking off traffic for a particular > port, what happens when the host picks the same port for its own use > (for instance as the local port of an outgoing connection)? if we're > going to recommend using the shared ip mode we need some way to > persistently fence off that port from local use.
This was discussed just a short bit ago on this thread. The answer is that the daemon has to bind that special port so that nobody else can use it. How or if it does so is unclear. Binding ports exclusively (and properly) on Solaris is unnecessarily hard. (The snoop visibility issue seems like a pretty serious problem to me, but I guess I'll just give up on that front.) -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
