Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Bubu on November 13, 2002, 01:04:58 PM
-
Hello,
The situation is as follows. Server E-smith V5, Connection ADSL IP dyn domain on No-IP
To reach the administration page and to remotely see the messages (in bottom) I use a tunnel on SSH, port 980
But now I would like to create a VPN.
I use a router CoyoteLinux, rules NAT are correct (FAQ coyotelinux),
but when I connect myself with customer PPTP of Windows 98 (update dun14) via a network entreprise (LAN)
Error 650
Is this normal that the client created a connection dial-up as via modem?
Which password is it necessary to give? (very tested) Here messages received at the time of my last attempt.
It’s not very clearly, you can help me and to say to me if I am on the good way ; I already found not badly of tricks on the VPN but now I dry. (je sèche)
Thank you
Bubu
Tranlate with altavista.be
Nov 13 10:14:57 bubu pptpd[5959]: MGR: Launching /usr/sbin/pptpctrl to handle client
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: local address = 192.168.0.200
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: remote address = 192.168.0.250
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: pppd speed = 460800
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: pppd options file = /etc/ppp/options.pptpd
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: Client 195.244.XXX.XXX control connection started
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: Received PPTP Control Message (type: 1)
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: Made a START CTRL CONN RPLY packet
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: I wrote 156 bytes to the client.
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: Sent packet to client
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: Received PPTP Control Message (type: 7)
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: 0 min_bps, 0 max_bps, 32 window size
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: Made a OUT CALL RPLY packet
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: Starting call (launching pppd, opening GRE)
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: pty_fd = 5
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: tty_fd = 6
Nov 13 10:14:57 bubu pptpd[5960]: CTRL (PPPD Launcher): Connection speed = 460800
Nov 13 10:14:57 bubu pptpd[5960]: CTRL (PPPD Launcher): local address = 192.168.0.200
Nov 13 10:14:57 bubu pptpd[5960]: CTRL (PPPD Launcher): remote address = 192.168.0.250
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: I wrote 32 bytes to the client.
Nov 13 10:14:57 bubu pptpd[5959]: CTRL: Sent packet to client
Nov 13 10:14:57 bubu modprobe: modprobe: Can't locate module char-major-108
Nov 13 10:14:57 bubu pppd[5960]: pppd 2.4.0 started by root, uid 0
Nov 13 10:14:57 bubu pppd[5960]: Using interface ppp0
Nov 13 10:14:57 bubu pppd[5960]: Connect: ppp0 <--> /dev/pts/1
Nov 13 10:15:28 bubu pppd[5960]: LCP: timeout sending Config-Requests
Nov 13 10:15:28 bubu pppd[5960]: Connection terminated.
Nov 13 10:15:28 bubu pppd[5960]: Exit.
Nov 13 10:15:28 bubu pptpd[5959]: Error reading from pppd: Input/output error
Nov 13 10:15:28 bubu pptpd[5959]: CTRL: GRE read or PTY write failed (gre,pty)=(6,5)
Nov 13 10:15:28 bubu pptpd[5959]: CTRL: Client 195.244XXXXXX control connection finished
Nov 13 10:15:28 bubu pptpd[5959]: CTRL: Exiting now
Nov 13 10:15:28 bubu pptpd[3329]: MGR: Reaped child 5959
-
Nov 13 10:15:28 bubu pptpd[5959]: CTRL: GRE read or PTY write failed (gre,pty)=(6,5)
Do you have GRE (protocol 47) forwarded to the SME also?
-
hello, Bill
The answer is No,
I just place 2 Into the field "numbre PPtP" .
Else to do and how ?
bubu
-
Bubu wrote:
>
> I use a router CoyoteLinux, rules NAT are correct (FAQ
> coyotelinux),
> but when I connect myself with customer PPTP of Windows 98
> (update dun14) via a network entreprise (LAN)
> Error 650
Is the SME behind the Coyote router, or were you just saying that you had previous experience with Coyote?
If you have a router between the ADSL and the SME, you'll need to have the router forward the PPTP information to the SME. PPTP uses TCP port 1723 and GRE protocol 47. If you have the SME directly connected to the internet (public IP), you shouldn't need to do anything other than specify the number of clients allowed.
I've had a lot of client-side issues. Even after DUN 1.4 was installed, reinstalling it has sometimes fixed weird problems I've had. So you might want to try reinstalling DUN 1.4, just to make sure...
-
Hello
SME is behind the router Coyotelinux and the rules are ( find on coyote Forum)
Start ipfwd by adding to rc.local:
#(this will forward all GRE 47 packets to the VPN-server)
/sbin/ipfwd --masq 192.168.0.200 47 &
Tight up your firewall and open port 1723. Forward port 1723 to your
internal VPN-server (this entry can be placed in either rc.firewall or rc.masquerade, it makes no difference):
/sbin/ipchains -I output -j ACCEPT -p tcp -s $EXTIPADDR /32 -d 0.0.0.0/0 1723 -i eth1
/sbin/ipchains -I input -j ACCEPT -p tcp -s 0.0.0.0/0 1723 -d $EXTIPADDR /32 -i eth1
/sbin/ipchains -I output -j ACCEPT -p 47 -s $EXTIPADDR /32 -d 0.0.0.0/0 -i eth1
/sbin/ipchains -I input -j ACCEPT -p 47 -s 0.0.0.0/0 -d $EXTIPADDR /32 -i eth1
/sbin/ipmasqadm autofw -A -r tcp 1723 1723 -h 192.168.0.200
Note that in this example, 192.168.0.200 is the internal VPN-server, the outside/WAN IP , $EXTIPADDR
Open /var/lib/lrpkg/modules.list and add /sbin/ipfwd to the list.
Don't forget to BACKUP! Save changes to any files, and use the Back-Up Utility found in the Configuration Menu (lrcfg).
-
hello,
here is the problem (find on the forum Coyote).
Author: Canuckle (---.ab.hsia.telus.net) Date: 05-03-02 09:13 1) How did you create the Coyote floppy? If it was the Windows version, there is NO VPN support. You have to use Linux for it. 2) The VPN protocol support is limited as noted in the information provided by the FAQ