From owner-freebsd-net Wed Apr 11 0:37:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from online.tmx.com.au (online.tmx.com.au [192.150.129.1]) by hub.freebsd.org (Postfix) with ESMTP id B06D937B424 for ; Wed, 11 Apr 2001 00:37:10 -0700 (PDT) (envelope-from mtaylor@bytecraft.com.au) Received: from melexc01.bytecraft.com.au ([203.9.250.249]) by online.tmx.com.au (8.9.3/8.8.8) with ESMTP id RAA07368 for Wed, 11 Apr 2001 17:37:07 +1000 (EST) Received: by MELEXC01 with Internet Mail Service (5.5.2448.0) id <2QBTJ6C9>; Wed, 11 Apr 2001 17:38:31 +1000 Message-ID: <710709BB8B02D311942E0060674418105442BF@MELEXC01> From: Murray Taylor To: "'freebsd-net@freebsd.org'" Subject: mpd setup Date: Wed, 11 Apr 2001 17:38:13 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Very gently, without wanting to break an existing, working setup he asks.... Given the following Netgraph Frame Relay configuration, are these scripts enough to create an mpd-netgraph pptp connection throught the frame relay internet connection? Or do I need to add some extra netgraphism's to connect into the frame relay chain? Proposed configuration files mpd.links frame-pptp: set link type pptp set pptp self 10.1.2.30 set pptp enable incoming set pptp disable originate mpd.conf pptp1: new -i ng0 frame-pptp frame-pptp set iface disable on-demand set iface enable proxy-arp set iface idle 1800 set bundle disable multilink set bundle authname user1 set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set ipcp yes vjcomp # require server to be .170 and remote laptop user to be .171 # as first guess set ipcp ranges 10.1.2.170/32 10.1.2.171/32 # our dns server set ipcp dns 10.x.y.z # our WINS servers set ipcp nbns 10.a.b.c 10.d.e.f mpd.secret user1 "pwd1" -o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o- - hardware setup ng0 ip fxp0 ip xxx.yyy.zzz.13 SPYDER 10.1.2.30 +----------+ aaa.bbb.ccc.1 alias | | +---+ |-+-+ +-| frame | N | X21 |s|n| |f| 100BaseT =======| T |========|r|g| |x|~~~~~~~~~~~~ relay | U | |0|0| |p| +---+ |-+-+ |0| | +-| | | | | | | | | +----------+ Netgraph setup for Frame Relay Internet access [ ] [ lmi ](annexD) --------+ [ ] | | [sync_sr0] [ ](dlci0) ---+ [physical](rawdata) --- (downstream)[ frame_relay ] [ ] [ ](dlci16)---+ | +-----------------------------------------------------------+ | | { ] [ ng0 ] 10.1.2.30 +--- (downstream)[ rcf1490 ](inet) --- (inet)[ iface ] aaa.bbb.ccc.1 [ ] [ ] ================ start_if.ng0 ============================= #!/bin/sh # script to set up a frame relay link on the sr card. # The dlci used is selected below. The default is 16 # WANic 405 CARD=sync_sr0 DLCI=16 # create a frame_relay type node and attach it to the sync port. ngctl mkpeer ${CARD}: frame_relay rawdata downstream # Attach the dlci output of the (de)multiplexor to a new # Link management protocol node using ANSI AnnexD ngctl mkpeer ${CARD}:rawdata lmi dlci0 annexD # Attach the DLCI(channel) the Telco has assigned you to # a node to hadle whatever protocol encapsulation your peer # is using. In this case rfc1490 encapsulation. ngctl mkpeer ${CARD}:rawdata rfc1490 dlci${DLCI} downstream # Attach the ip (inet) protocol output of the protocol mux to the ip (inet) # input of a netgraph "interface" node (ifconfig should show it as "ng0"). ngctl mkpeer ${CARD}:rawdata.dlci${DLCI} iface inet inet ================end of start_if.ng0 ======================== Murray Taylor Project Engineer Bytecraft P/L +61 3 9587 2555 +61 3 9587 1614 fax mtaylor@bytecraft.com.au www.bytecraftentertainment.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message