Transcript Project Orpheus

Project Orpheus
Network Issues
Ryan Troll
Carnegie Mellon University
Why is this an issue?


Microsoft migration towards IP only
Migration requires full backwards compatibility
 IPX
/ NetBIOS functionality
 No user visible network configuration
 Computer name settable by end user
 User name in any char set
WINS to DNS Migration


WINS handles clients changing names, IP address,
even across subnets
Utilizing DHCP Dynamic IP addresses and Dynamic
DNS
Network Configuration


Uses DHCP for IP address configuration
In the absence of DHCP, hosts automatically
configure an IP address
 Only
when there is no DHCP response
 Continues to check for a DHCP server
 Specific subnet
 Present in Win98/NT5 (And MacOS 8.5)
Network Configuration: Problems
and Solutions




CMU currently assigns static IP addresses to all
hosts via DHCP
Previously, no address assignment via DHCP
resulted in an error message to the user
Users now receive no error message, but can’t do
anything
Solution: Proposed DHCP extension to allow DHCP
server to tell clients ‘I have no address for you, and
you should not auto-configure one either.’
DNS Changes - Dynamic Update






User settable names utilizing secure DNS Dynamic
Update
Security mechanism not standardized yet, but in the
standardization process through the IETF.
Mechanism based on Kerberos5
Clients (or DHCP server) update A and PTR records
Appears to not handle CINDR correctly.
CMU: Testing CINDR, sending bug reports
DNS Changes - Character Sets



NetBIOS naming allows non-ASCII characters in
names.
For MS to move to DNS only, must be able to do so
MS is in the process of standardizing non-ASCII
DNS with the IETF.
Project Orpheus: Current Network
Projects

Attempting to use Unix DHCP and DNS servers to
support a full NT5 infrastructure
 No
dynamic DNS
 BIND 8.x, ISC DHCP

Evaluating Microsoft DNS Extensions
 Non-ASCII
interoperability
 Dynamic Update in a CINDR zone

Autonet DHCP extensions
Project Orpheus: Current Network
Projects

Evaluation of new browsing mechanism
 No
IPX, NetBIOS, or NT4 backwards compatibility
 How does the NT4 backwards compatibility
mechanism fit in?

Evaluation of dialup client support
What We Haven’t Touched (Yet)






IGMPv2 / Multicast
NAT
VPNs (L2TP / PPTP)
IPSec
IPv6
RSVP
Questions?


Ryan Troll <[email protected]>
http://asg.web.cmu.edu/orpheus