1. Windows Internet Connection Sharing Dave Eitelbach Program Manager Networking And Communications Microsoft Corporation

2. Goals  Enable multiple users in the home to connect to the Internet  Handle roaming laptops transparently  Simplify or eliminate configuration  Enable telecommuting using the Internet as a WAN (VPNs)

3. Issues For Deployment Of Home Networks  Installation should be easy  There are no Net admins at home.  Automatic Network Configuration has to be automatic  There are no Net admins at home..  Network health and recovery should take care of itself  There are no Net admins at home...

4. Requirements  Transparent network configuration for end user  No client software (from both IHVs and OEMs)  Support for legacy and non-Windows clients  Demand dial support  Support for remote client UI for demand dial control and progress indication  Dial control and client “usage” APIs  Comprehensive protocol support  Built in support for basic protocols (e.g., FTP, etc.)  Built-in support for Internet games (no config UI)  Built-in support for VPNs (e.g., PPTP)

5. Connecting To The Internet  Share the Internet connection transparently for both  Dial-Up media  Always-available media  Resolve Internet names to addresses  Use Internet protocols (DNS and DHCP) to solve the problem  Clients on the home network should just work

6. Addresses And The Internet  Home network clients need to share the public IP address of the gateway system when sending and receiving traffic on the Internet  Internet addresses must be unique and routable  Private home addresses won’t work  Consumer Internet access (via an ISP) is typically a single IP address

7. Connection Sharing Architecture  “Connection Sharing" components:  NAT transparently shares single public IP address for clients on the local network  DHCP Allocator assigns address, gateway and name server on the local-network  DNS Proxy resolves names on behalf of local-network clients  Auto-dial makes connections automatically

8. Alternative Gateways  Basic options for Internet Gateway  Application Proxy Server  Winsock Proxy Server  Network Address Translator (NAT)

9. Application Proxy stack winsock app stack winsock app-proxy  Every application on every client must be configured to use proxy  Proxy requires logic for every application

10. Winsock Proxy stack winsock app stack winsockproxy  Client winsock must be configured to forward socket calls to winsock proxy  Transparent for most applications

11. Network Address Translation stack winsock app NAT  No client configuration; transparent for all applications on the client  NAT requires protocol handlers for some protocols (FTP, games, etc)

12. Network Address Translator  NAT (Network Address Translation)  Typically maps set of private addresses to set of public addresses  NAT keeps state on private source IP address and public destination address for outbound flows  NAT changes the IP address information and edits needed IP header information on the fly

13. 10.0.0.2 131.107.1.7D S 172.31.249.14 10.0.0.2=172.31.249.14  Records the mapping between original and replacement address What Is NAT?  A NAT changes IP addresses in packets on the fly

14. Autoconfiguring The Home Network Via DHCP  The client machines in the home network need to be configured for address, name server address, and default gateway address  Static addressing requires “networking 101” knowledge, and configuration of each PC  Automatic self-addressing generates a unique address for each PC (in single subnet)  DHCP (Dynamic Host Configuration Protocol) assigns IP address, default gateway, and DNS info to each client  DHCP is widely used on both Enterprise and small networks (e.g., Small Business Server)

15. Autoconfiguring The Home Network Via DHCP  Enable mobile laptops  Laptops will come home from Enterprise network  They should work on both the Enterprise network as well as the home network without reconfiguration  Laptops must return to the Enterprise network without causing network problems  Base solution on standard protocols, DHCP

16. DHCP Allocator  A simplified DHCP server for the home network  Assumes single segment LAN (i.e., single subnet) connected to the Internet gateway  Relies on broadcast-based defense  Multiple segments would require true DHCP server and potentially DHCP relays  Assigns its own address (i.e., the address of the “private” interface of Internet sharing PC) as the DNS address and default gateway address

17. DNS Proxy  DHCP Allocator provides its own address as DNS server address to home network client machines  Clients have DNS server address in disconnected dial-up case  Clients are shielded from changing Internet DNS server addresses  Internet DNS requests are then proxied to the Internet connection  Dial up link is connected if needed

18. Home LAN Windows Internet Connection Sharing 169.254.0.3 169.254.0.4 Internet NAT translates packets to and from the assigned public IP address Clients access corporate networks using PPTP through the NAT DHCP allocator assigns address, gateway, and name- server on home LAN; DNS proxy forwards queries Connection Sharing Example  Auto-configured home/ small-office networking

19. Windows Internet Connection Sharing  Windows 2000 and Windows 98 will provide base Connection Sharing capabilities  DHCP Allocator  DNS Proxy  Network Address Translation  Support for popular applications and games  APIs for config, status, and dial control  Enable ISV hybrid solutions on Windows platform

20. Windows Internet Connection Sharing Requirements revisited  Transparent network configuration for end user - YES  Support for legacy and non-Windows clients - YES  Demand dial support - YES  Support for remote client UI for demand dial control and progress indication - YES  Dial control and client “usage” APIs  No client software (from both IHVs and OEMs) - YES  Comprehensive protocol support - YES  Easy support (e.g., no config UI) for popular Internet games  VPN (e.g., PPTP)

21. Windows Connection Sharing TCPIP NAT Kernel User DHCP DNS Proxy Extensions Automates addressing of LAN clients Forwards name queries from LAN clients Shares single IP address among LAN clients Automatically dials public network for LAN clients Forwards packets through NAT before routing Windows 2000 Connection Sharing Architecture

22. NDIS ICSMACPPPMACEthernet IPICSPROT TCP/UDP Internal Home Network Modem NDIS protocols NDIS adapters Data flow in kernel Windows 98 Internet Connection Sharing Architecture

23. Windows 2000 Connection Sharing Integration  Turning on connection sharing for new dial-up connections

24. Windows 2000 Connection Sharing Integration  Turning on connection sharing for existing connections

25. Windows 98 Internet Connection Sharing  Turning on Internet Connection Sharing

26. Windows Internet Connections Sharing Demo ICS PC Client PC Internet DSL link HomePNA

27. Call To Action  Provide feedback on your key Internet sharing requirements  Send e-mail to hnetfb@microsoft.com  Ship “Sharing Enabled” PCs  Broadband + LAN  Dial + LAN  ISDN + LAN  Build value add control applications and UI on base Internet Sharing APIs