Difference between revisions of "VPN PPTP"
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | * | + | * Known Issues |
| − | There is a know issue with VPN PPTP service. When this problem occurs VPN PPTP users will be able to establish a VPN connection but will not be able to access any internal network resources. | + | There is a know issue with VPN PPTP service in version 6.0 update 1. When this problem occurs VPN PPTP users will be able to establish a VPN connection but will not be able to access any internal network resources. |
| − | The workaround for this problem | + | The workaround for this problem is the following procedure to be executed in the CLI as root: |
- ''ps ax | grep pptp'' | - ''ps ax | grep pptp'' | ||
| Line 21: | Line 21: | ||
4177 pts/4 S+ 0:00 grep pptp | 4177 pts/4 S+ 0:00 grep pptp | ||
| − | 15088 ? S 0:11 pptpd [ | + | 15088 ? S 0:11 pptpd [88.152.241.124:FFE9 - 0F00] |
| − | 15089 pts/0 Ss+ 0:00 /usr/sbin/pppd local file /etc/ppp/pptpd-options 115200 192.168.0.151:192.168.0.152 ipparam | + | 15089 pts/0 Ss+ 0:00 /usr/sbin/pppd local file /etc/ppp/pptpd-options 115200 192.168.0.151:192.168.0.152 ipparam 88.152.241.124 remotenumber 88.152.241.124 |
20619 ? Ss 0:00 /usr/sbin/pptpd | 20619 ? Ss 0:00 /usr/sbin/pptpd | ||
| Line 36: | Line 36: | ||
4188 pts/4 S+ 0:00 grep pptp | 4188 pts/4 S+ 0:00 grep pptp | ||
| − | 15088 ? S 0:11 pptpd [ | + | 15088 ? S 0:11 pptpd [88.152.241.124:FFE9 - 0F00] |
| − | 15089 pts/0 Ss+ 0:00 /usr/sbin/pppd local file /etc/ppp/pptpd-options 115200 192.168.0.151:192.168.0.152 ipparam | + | 15089 pts/0 Ss+ 0:00 /usr/sbin/pppd local file /etc/ppp/pptpd-options 115200 192.168.0.151:192.168.0.152 ipparam 88.152.241.124 remotenumber 88.152.241.124 |
ipbrick:~# | ipbrick:~# | ||
Latest revision as of 20:47, 14 December 2014
- Known Issues
There is a know issue with VPN PPTP service in version 6.0 update 1. When this problem occurs VPN PPTP users will be able to establish a VPN connection but will not be able to access any internal network resources.
The workaround for this problem is the following procedure to be executed in the CLI as root:
- ps ax | grep pptp
- /etc/init.d/pptpd stop [stop the service]
- Identify the process Id number of pptpd that is still running and force it to stop with the command:
- kill -9 <pid number>
- /etc/init.d/pptpd start [start the service]
For example:
ipbrick:~# ps ax | grep pptp
4177 pts/4 S+ 0:00 grep pptp 15088 ? S 0:11 pptpd [88.152.241.124:FFE9 - 0F00] 15089 pts/0 Ss+ 0:00 /usr/sbin/pppd local file /etc/ppp/pptpd-options 115200 192.168.0.151:192.168.0.152 ipparam 88.152.241.124 remotenumber 88.152.241.124 20619 ? Ss 0:00 /usr/sbin/pptpd
ipbrick:~#
ipbrick:~# /etc/init.d/pptpd stop
Stopping PPTP: pptpd.
ipbrick:~#
ipbrick:~# ps ax | grep pptp
4188 pts/4 S+ 0:00 grep pptp 15088 ? S 0:11 pptpd [88.152.241.124:FFE9 - 0F00] 15089 pts/0 Ss+ 0:00 /usr/sbin/pppd local file /etc/ppp/pptpd-options 115200 192.168.0.151:192.168.0.152 ipparam 88.152.241.124 remotenumber 88.152.241.124
ipbrick:~#
ipbrick:~# kill -9 15088
ipbrick:~# ps ax | grep pptp
4235 pts/4 S+ 0:00 grep pptp
ipbrick:~# /etc/init.d/pptpd start
Starting PPTP Daemon: pptpd.
ipbrick:~# ps ax | grep pptp
4242 ? Ss 0:00 /usr/sbin/pptpd 4244 pts/4 S+ 0:00 grep pptp
ipbrick:~#
