[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

[Openvpn-users] I still can'f figure out why my cleint can't acess other server side computers


  • Subject: [Openvpn-users] I still can'f figure out why my cleint can't acess other server side computers
  • From: Leith Bade <leithalweapon@xxxxxxxxxxxxxxx>
  • Date: Sat, 01 Jul 2006 21:36:06 +1200

From using traceroute and ping I have concluded it is the server that is breaking the chain between client, server and router.

I can’t think of what is stopping the server from forwarding data from the client to the router. I might do some packet sniffing to see what is going on.

If you guys could offer some advice, I would be glad.

 

Here is some route and firewall data in case it holds the key to the problem:

 

From the client’s (Windows XP) route table:

===========================================================================

Interface List

0x1 ........................... MS TCP Loopback interface

0x2 ...00 0f ea e1 71 91 ...... Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Con

troller - Packet Scheduler Miniport

0x10004 ...00 ff e1 fe 92 2e ...... TAP-Win32 Adapter V8 - Packet Scheduler Mini

port

0x40005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface

===========================================================================

===========================================================================

Active Routes:

Network Destination        Netmask          Gateway       Interface  Metric

          0.0.0.0          0.0.0.0    210.246.13.77   210.246.13.77       1

         10.8.0.1  255.255.255.255         10.8.0.5        10.8.0.6       1

         10.8.0.4  255.255.255.252         10.8.0.6        10.8.0.6       30

         10.8.0.6  255.255.255.255        127.0.0.1       127.0.0.1       30

   10.255.255.255  255.255.255.255         10.8.0.6        10.8.0.6       30

        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1

      192.168.0.0    255.255.255.0         10.8.0.5        10.8.0.6       1

      202.0.46.67  255.255.255.255    210.246.13.77   210.246.13.77       1

    210.246.13.77  255.255.255.255        127.0.0.1       127.0.0.1       50

   210.246.13.255  255.255.255.255    210.246.13.77   210.246.13.77       50

        224.0.0.0        240.0.0.0         10.8.0.6        10.8.0.6       30

        224.0.0.0        240.0.0.0    210.246.13.77   210.246.13.77       1

  255.255.255.255  255.255.255.255         10.8.0.6        10.8.0.6       1

  255.255.255.255  255.255.255.255         10.8.0.6               2       1

  255.255.255.255  255.255.255.255    210.246.13.77   210.246.13.77       1

Default Gateway:     210.246.13.77

 

From the server’s (Debian) route table:

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

10.8.0.2        *               255.255.255.255 UH    0      0        0 tun0

10.8.0.0        10.8.0.2        255.255.255.0   UG    0      0        0 tun0

192.168.0.0     *               255.255.255.0   U     0      0        0 eth0

default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0

 

From the servers iptables:

Chain INPUT (policy ACCEPT)

target     prot opt source               destination

ACCEPT     all  --  anywhere             anywhere

ACCEPT     all  --  anywhere             anywhere

 

Chain FORWARD (policy ACCEPT)

target     prot opt source               destination

ACCEPT     all  --  anywhere             anywhere

ACCEPT     all  --  anywhere             anywhere

 

Chain OUTPUT (policy ACCEPT)

target     prot opt source               destination

 

I hope that helps.

 

Thanks,

Leith Bade

Email: leithalweapon@xxxxxxxxxxxxxxx

 

Get stuff done quickly with pre-integrated technology to make your job easier
_______________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users