Thanks for the information. I agree that a command line switch would be the most strait forward solution. An more general alternative might be a configuration parameter specifying which interfaces to bind to - similar to the "query-source" option of the bind name server.

Probably not a valuable opinion, since I don't have the skill to implement it.

Jack

On Jan 7, 2004, at 7:25 AM, Dr. Greg Wettstein wrote:

On Jan 7, 12:17am, Sam Hartman wrote:
} Subject: Re: Loopback Interface

"ms419" == ms419 <[EMAIL PROTECTED]> writes:

ms419> I'm running a slave kerberos KDC on my OS X laptop. I need ms419> to access the KDC when the laptop is disconnected from any ms419> network, but the KDC doesn't bind to the loopback ms419> interface, and I can't seem to setup a dummy interface in ms419> OS X. OS X shuts down any interface on which it can't ms419> detect a link. How can I force the KDC to bind to the ms419> loopback interface?

You cannot do so with the KDC shipped with OSX.

There has been enough discussion of this feature of the code that we
may want to revisit allowing the kdc to bind to the loopback address.

A command-line switch (default not to bind) to turn on binding to loopback might be the most appropriate solution.

Best wishes for a productive week to everyone.

Greg

}-- End of excerpt from Sam Hartman

As always,
Dr. G.W. Wettstein, Ph.D. Enjellic Systems Development, LLC.
4206 N. 19th Ave. Specializing in information infra-structure
Fargo, ND 58102 development.
PH: 701-281-1686
FAX: 701-281-3949 EMAIL: [EMAIL PROTECTED]
----------------------------------------------------------------------- -------
"This is a single non-reentrant routine which takes the received packet
queue and throws it at the networking layers in the hope that something
useful will emerge."
-- dev.c, Linux Networking Sources




________________________________________________ Kerberos mailing list [EMAIL PROTECTED] https://mailman.mit.edu/mailman/listinfo/kerberos

Reply via email to