This is automatically generated documentation. Edit after the "COMMENTS" heading; changes to the main body will be lost.

PPTPServer Element Documentation

NAME

PPTPServer -- Click element; Handles PPTP-over-TCP connections.

SYNOPSIS

PPTPServer([KEYWORDS])

Ports: any number of inputs, any number of outputs
Processing: push
Drivers: userlevel
Package: iias

DESCRIPTION

Handles PPTP-over-TCP connections. The number of tunnels supported is equal to the number of input/output pairs. PPPControlProtocol elements such as IPCP and LCP should feedback from the outputs of PPTPServer to its inputs. IP packets destined for remote peers should be PPP encapsulated (see PPPEncap) and routed to the appropriate input. IP packets from the remote peer are pushed out the appropriate output and should be PPP decapsulated (see Strip). Keyword arguments are:

VERBOSE
Boolean. When true, PPTPServer will print messages whenever it accepts a new connection or drops an old one. Default is false.

EXAMPLES

The following snippet enables a single PPTP tunnel with local address 10.0.0.1 and remote address 10.0.0.100. Shared IP input path and routing table ip :: CheckIPHeader(INTERFACES 10.0.0.1) rt :: StaticIPLookup( 10.0.0.1 0, 10.0.0.100 1 ) PPTP server pptpd :: PPTPServer(VERBOSE 1) ppp0 pptpd[0] -> ppp0 :: Classifier(2/0021, 2/8021, -) IP from remote peer 0 ppp0[0]

  1. > Strip(4)
  2. > ip
  3. > rt

IPCP negotiation for peer 0 ppp0[1] -> IPCP(local, remote0, VERBOSE 1) -> [0]pptpd LCP negotiation for peer 0 ppp0[2]

  1. > LCP(VERBOSE 1)
  2. > [0]pptpd

Local delivery rt[0] -> Print(toh) -> Discard IP to remote peer 0 rt[1]

  1. > PPPEncap(0x0021)
  2. > [0]pptpd

SEE ALSO

PPPControlProtocol, IPCP, LCP, PPPEncap, Strip

Generated by 'click-elem2man' from 'ppp/pptpserver.hh:37' on 17/Jan/2012.

COMMENTS

 
elements/pptpserver.txt · Last modified: 2012/01/17 10:23 (external edit)
 
Recent changes RSS feed Driven by DokuWiki