EnterNet Subscriber Client

1
EnterNet Subscriber Client

• NTS Multi-Tunnel Architectures
• Simultaneous PPPoE Sessions

2
Multiple Session Options
Network Adapters
On-Demand
Application
Application
Application
WSOCK
TCP
PPPoE-1
PPPoE
MAC
MAC
Dedicated on-demand application pathSimple
install without reboot
Conventional MS architecture
Pro
Pro
Questionable routingInstall and binding required
Con
Application-specific
Con
3
Single Protocol Architecture
Windows architecture for multiple networks
all apps call the same wsock32.dll
Applications
file access uses NetBIOS API(for enterprise, not
internet)
File Redirector
WSOCK
MSTCP
NETBIOS
MSTCP can bind to multiple MAC drivers each MAC
is a distinct network

• MSTCP traffic is IP routed to specific
  networkrouting is not perfect
• browser traffic may be sprayed across all
  networksmost application focus on a single
  destination
• pseudo adapters must send/receive thru real
  adapters

NET3
NET2
NET1
4
Pseudo Adapters
MSTCP
PPPoE
MAC
pseudo
real
5
Bindings
Application
MSTCP
NTSTAP1 into the bindings setup via NDIS between
MSTCP and the real Ethernet MAC Driver and can
intercept packets going to/from the net or inject
packets that need to go to the net or to MSTCP
NDIS Upper
NDIS Upper
NDIS Lower
NDIS Lower
PPPoE LANDriver
Real LANDriver
6
Multi-SessionIntegrated
Multiple sessions using standard Windows
architecture

• PPP session ID separates traffic
• GUI must manage session setup
• routing decisions made by MSTCP
• browser not constrained
• special applications like video are not dedicated

EnterNet ControlApplication
WSOCK
MSTCP
EnterNet VPN over PPPoE
MSTCP
MAC
PPPoE-n
PPPoE-1
PPPoE-2
PPPoE
MAC
VPN
two adapters
7
Multi-Protocol Architecture

• multiple winsocks allow multiple paths
• browsers use just one winsock
• some apps may be winsock-specific

Multiple protocols can bind to same MAC
MSTCP
IPX
NETBEUI
NTSTCP
Applications can bind to different stacks
Application
Application
MAC
WSOCK
WSOCK
NTSTCP
MSTCP
NETBIOS
NETBIOS

• multiple TCP stacks can co-exist
• applications use one API or another
• routing is per-application, thus dedicated

MAC
PPPoE
8
Multi-SessionSeparated

• NTS protocols are stamped with ID
• applications need not be ID aware
• ID aware apps can use multiplePPP sessions
• session establishment can be static or dynamic

Multiple sessions using standard architecture
Application
Application
Application
Application
WSOCK
WSOCK
WSOCK
WSOCK
NTSTCP
MSTCP
NTSTCP
NTSTCP
PPPoE
PPPoE
PPPoE
MAC
9
Application tunnels
Application
Application
Application
PrivateDLL
PrivateDLL
PrivateDLL
MSTCP
MPX
Application Tunnels
MAC

• each application has a dedicated IP personality
• personality obtained at application start
• no limit to number of applications-sessions
• dynamic run-time loading from small DLL files
• Independent from Windows TCP configuration
• session establishment id data-driven
• choice of underlying access layer protocol

10
Inside the DLL
Application
Application
WSOCK
SessionEstablishment
PrivateDLL
120KB
PrivateTCP
PPPoE
MAC
11
Intelligent Protocol Architecture
Tunnel-aware applications can load multiple DLLs
Application
Any number of PPPoE sessions for one application