LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 02-26-2014, 10:25 AM   #1
Vita
Member
 
Registered: May 2012
Distribution: Debian 6, CentOS 6
Posts: 39

Rep: Reputation: Disabled
Problem with VPN pptpd network, clients can't talk to specific client?


Hi,

Here's the thing I have a few computers on this VPN network. Let's call them like this:\

VPN IP subnet 192.168.0.0/24.

X - My remote VPS server hosting pptpd VPN. (192.168.0.1)
A - local web server (Linux Debian 7 Cubian) connected to a VPN server X. (192.168.0.10)
B - local PC (Windows) also connected to a VPN server X. (192.168.0.3)

Server X can ping computer B but can't ping server A or access it in any kind. Computer B can ping remote server X but can't ping server A. When I try to ping server X and computer B from a local web server A it works.

Here is a diagram of this situation if it's not clear.
http://i.imgur.com/dd0Msj1.png

So I guess the problem is with my local web server A. Other computers on the VPN can't access the local web server A or ping it but server A can access and ping other computers on the VPN.

Also on the local network computer A responds to ping packets and can be accessed without a problem.\

Server A info (192.168.0.10):
Code:
cubie@Cubian:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr XX:b0:XX:59:04:XX
          inet addr:192.168.1.7  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::c2b0:cbff:fe59:470/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:54203 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40987 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8258576 (7.8 MiB)  TX bytes:3641634 (3.4 MiB)
          Interrupt:87 Base address:0x8000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:40667 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40667 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5076069 (4.8 MiB)  TX bytes:5076069 (4.8 MiB)

ppp0      Link encap:Point-to-Point Protocol
          inet addr:192.168.0.10  P-t-P:192.168.0.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1496  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:938 (938.0 B)  TX bytes:824 (824.0 B)

cubie@Cubian:~$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         PENTIUM1        0.0.0.0         UG    0      0        0 eth0
web.nikos-hosti PENTIUM1        255.255.255.255 UGH   0      0        0 eth0
192.168.0.0     *               255.255.255.0   U     0      0        0 ppp0
192.168.0.1     *               255.255.255.255 UH    0      0        0 ppp0
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0

cubie@Cubian:~$ ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
64 bytes from 192.168.0.3: icmp_req=1 ttl=127 time=299 ms
64 bytes from 192.168.0.3: icmp_req=2 ttl=127 time=398 ms
64 bytes from 192.168.0.3: icmp_req=3 ttl=127 time=301 ms
64 bytes from 192.168.0.3: icmp_req=4 ttl=127 time=343 ms
^C
--- 192.168.0.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 299.381/335.674/398.799/40.498 ms

cubie@Cubian:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_req=1 ttl=64 time=144 ms
64 bytes from 192.168.0.1: icmp_req=2 ttl=64 time=145 ms
64 bytes from 192.168.0.1: icmp_req=3 ttl=64 time=144 ms
64 bytes from 192.168.0.1: icmp_req=4 ttl=64 time=143 ms
^C
--- 192.168.0.1 ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4004ms
rtt min/avg/max/mdev = 143.992/144.823/145.721/0.721 ms
VPN host server X:
Code:
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:849 errors:0 dropped:0 overruns:0 frame:0
          TX packets:849 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:79496 (79.4 KB)  TX bytes:79496 (79.4 KB)

ppp0      Link encap:Point-to-Point Protocol
          inet addr:192.168.0.1  P-t-P:192.168.0.10  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1400  Metric:1
          RX packets:23 errors:0 dropped:0 overruns:0 frame:0
          TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:1580 (1.5 KB)  TX bytes:1694 (1.6 KB)

ppp1      Link encap:Point-to-Point Protocol
          inet addr:192.168.0.1  P-t-P:192.168.0.3  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1400  Metric:1
          RX packets:10699 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14492 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:1926190 (1.9 MB)  TX bytes:10095165 (10.0 MB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:127.0.0.2  P-t-P:127.0.0.2  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:188141 errors:0 dropped:0 overruns:0 frame:0
          TX packets:191114 errors:0 dropped:170 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:60151570 (60.1 MB)  TX bytes:63591812 (63.5 MB)

venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:162.XXX.9.XXX  P-t-P:162.XXX.9.XXX  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1

venet0:1  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:162.XXX.9.XXX  P-t-P:162.XXX.9.XXX  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1

root@web:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.10    *               255.255.255.255 UH    0      0        0 ppp0
192.168.0.3     *               255.255.255.255 UH    0      0        0 ppp1
default         *               0.0.0.0         U     0      0        0 venet0

root@web:~# ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
64 bytes from 192.168.0.3: icmp_req=1 ttl=128 time=154 ms
64 bytes from 192.168.0.3: icmp_req=2 ttl=128 time=182 ms
^C
--- 192.168.0.3 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 154.680/168.731/182.783/14.057 ms
root@web:~# ping 192.168.0.10
PING 192.168.0.10 (192.168.0.10) 56(84) bytes of data.
64 bytes from 178.221.37.39: icmp_req=1 ttl=50 time=157 ms
64 bytes from 178.221.37.39: icmp_req=2 ttl=50 time=153 ms
64 bytes from 178.221.37.39: icmp_req=3 ttl=50 time=154 ms
^C
Computer B info (Windows):
Code:
C:\Windows\System32>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=155ms TTL=64
Reply from 192.168.0.1: bytes=32 time=156ms TTL=64
Reply from 192.168.0.1: bytes=32 time=156ms TTL=64
Reply from 192.168.0.1: bytes=32 time=156ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 155ms, Maximum = 156ms, Average = 155ms

C:\Windows\System32>ping 192.168.0.10

Pinging 192.168.0.10 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.10:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
UPDATE: As I can see, now the VPN server X can only ping but not access web server (port 80) on server A, that's weird because ping and access to a web server didn't work yesterday.

What should I do to allow the other computers on the VPN to access and ping the local web server A?

Thanks for the help!

Best Regards!

Last edited by Vita; 02-26-2014 at 11:35 AM. Reason: Change the title and update thread
 
Old 02-27-2014, 12:34 PM   #2
pingu
Senior Member
 
Registered: Jul 2004
Location: Skuttunge SWEDEN
Distribution: Debian preferably
Posts: 1,350

Rep: Reputation: 127Reputation: 127
It looks like a firewall problem
You need to check firewall rules on server A, and also rules on server X - which I believe is some kind of main firewall?
And remember, when you access through vpn it is the *vpn* (ppp) ip address that needs to be allowed.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Why i cant see Windows 7 PPTP VPN clients in Network Neighborhood? endy66 Linux - Networking 1 04-02-2013 01:48 PM
strange problem with pptpd and windows clients m.sabouri Linux - Networking 0 08-16-2011 12:29 PM
VPN pptpd connected vpn server only access need help please u4david Linux - Networking 1 10-17-2008 03:54 PM
pptpd vpn on SuSE: All users can login but only two user could reach to network behin ikhmer Linux - Networking 2 12-25-2006 01:15 AM
VPN with pptpd m1111 Linux - Networking 0 02-07-2006 01:42 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 02:14 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration