Hello ErnestasB, thank you for your support.
When i try to run the command i get the following messages
RUT240a (OpenVPN server)
root@RUT240a:/# ip route add default 10.0.2.0/24 via 10.10.0.1 dev tun_s_1
Error: either "to" is duplicate, or "10.0.2.0/24" is a garbage.
RUT240b (OpenVPN client)
root@RUT240b:~# ip route add default 10.0.3.0/24 via 10.10.0.28 dev tun_c_2
Error: either "to" is duplicate, or "10.0.3.0/24" is a garbage.
Those routes already exits, should i delete them and then test this?
Here are some test from this morning, maybe they help. PCs from Server side can ping PCs on client side so there shouldn't be a routing problem because the packets return. I also tried /etc/init.d/firewall stop but nothing changed so it shouldn't be a firewall problem.
RUT240a
root@RUT240a:/# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.64.64.64 0.0.0.0 UG 0 0 0 3g-ppp
10.0.2.72 10.10.0.28 255.255.255.248 UG 0 0 0 tun_s_1
10.0.3.0 * 255.255.255.0 U 0 0 0 br-lan
10.10.0.0 * 255.255.255.0 U 0 0 0 tun_s_1
10.64.64.64 * 255.255.255.255 UH 0 0 0 3g-ppp
root@RUT240a:/# ping 10.0.2.78
PING 10.0.2.78 (10.0.2.78): 56 data bytes
64 bytes from 10.0.2.78: seq=0 ttl=64 time=112.445 ms
64 bytes from 10.0.2.78: seq=1 ttl=64 time=378.169 ms
^C
--- 10.0.2.78 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 112.445/245.307/378.169 ms
root@RUT240a:/# ping 10.0.2.77
PING 10.0.2.77 (10.0.2.77): 56 data bytes
64 bytes from 10.0.2.77: seq=0 ttl=127 time=685.800 ms
64 bytes from 10.0.2.77: seq=1 ttl=127 time=72.746 ms
64 bytes from 10.0.2.77: seq=2 ttl=127 time=278.531 ms
^C
--- 10.0.2.77 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 72.746/345.692/685.800 ms
root@RUT240a:/# traceroute 10.0.2.78
traceroute to 10.0.2.78 (10.0.2.78), 30 hops max, 38 byte packets
1 10.0.2.78 (10.0.2.78) 126.365 ms 61.841 ms 53.638 ms
root@RUT240a:/# traceroute 10.0.2.77
traceroute to 10.0.2.77 (10.0.2.77), 30 hops max, 38 byte packets
1 10.10.0.28 (10.10.0.28) 552.809 ms 70.038 ms 63.120 ms
2 10.0.2.77 (10.0.2.77) 63.181 ms 62.228 ms 52.530 ms
root@RUT240a:/#
RUT240b
root@RUT240b:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.64.64.64 0.0.0.0 UG 0 0 0 3g-ppp
10.0.2.72 * 255.255.255.248 U 0 0 0 br-lan
10.0.3.0 10.10.0.1 255.255.255.0 UG 0 0 0 tun_c_2
10.10.0.0 * 255.255.255.0 U 0 0 0 tun_c_2
10.64.64.64 * 255.255.255.255 UH 0 0 0 3g-ppp
root@RUT240b:~# ping 10.0.3.10
PING 10.0.3.10 (10.0.3.10): 56 data bytes
64 bytes from 10.0.3.10: seq=0 ttl=64 time=93.143 ms
64 bytes from 10.0.3.10: seq=1 ttl=64 time=619.488 ms
^C
--- 10.0.3.10 ping statistics ---
3 packets transmitted, 2 packets received, 33% packet loss
round-trip min/avg/max = 93.143/356.315/619.488 ms
root@RUT240b:~# ping 10.0.3.1
PING 10.0.3.1 (10.0.3.1): 56 data bytes
^C
--- 10.0.3.1 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
root@RUT240b:~# traceroute 10.0.3.10
traceroute to 10.0.3.10 (10.0.3.10), 30 hops max, 38 byte packets
1 10.0.3.10 (10.0.3.10) 104.171 ms 48.944 ms 58.505 ms
root@RUT240b:~# traceroute 10.0.3.1
traceroute to 10.0.3.1 (10.0.3.1), 30 hops max, 38 byte packets
1 10.10.0.1 (10.10.0.1) 248.971 ms 58.270 ms 57.983 ms
2 * * *
3^C
root@RUT240b:~#
PC1 (connected to RUT240b)
C:\Windows\system32>ping 10.0.3.10
Pinging 10.0.3.10 with 32 bytes of data:
Reply from 10.0.3.10: bytes=32 time=241ms TTL=63
Reply from 10.0.3.10: bytes=32 time=184ms TTL=63
Reply from 10.0.3.10: bytes=32 time=142ms TTL=63
Reply from 10.0.3.10: bytes=32 time=102ms TTL=63
Ping statistics for 10.0.3.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 102ms, Maximum = 241ms, Average = 167ms
C:\Windows\system32>ping 10.0.3.1
Pinging 10.0.3.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.0.3.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Windows\system32>tracert 10.0.3.10
Tracing route to 10.0.3.10 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.0.2.78
2 382 ms 70 ms 68 ms 10.0.3.10
Trace complete.
C:\Windows\system32>tracert 10.0.3.1
Tracing route to 10.0.3.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.0.2.78
2 395 ms 70 ms 58 ms 10.10.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 ^C
C:\Windows\system32>
Server1 (connected to RUT240a)
C:\Windows\system32>ping 10.0.2.78
Pinging 10.0.2.78 with 32 bytes of data:
Reply from 10.0.2.78: bytes=32 time=77ms TTL=63
Reply from 10.0.2.78: bytes=32 time=328ms TTL=63
Reply from 10.0.2.78: bytes=32 time=291ms TTL=63
Reply from 10.0.2.78: bytes=32 time=247ms TTL=63
Ping statistics for 10.0.2.78:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 328ms, Average = 235ms
C:\Windows\system32>ping 10.0.2.77
Pinging 10.0.2.77 with 32 bytes of data:
Reply from 10.0.2.77: bytes=32 time=238ms TTL=126
Reply from 10.0.2.77: bytes=32 time=200ms TTL=126
Reply from 10.0.2.77: bytes=32 time=149ms TTL=126
Reply from 10.0.2.77: bytes=32 time=106ms TTL=126
Ping statistics for 10.0.2.77:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 106ms, Maximum = 238ms, Average = 173ms
C:\Windows\system32>tracert 10.0.2.78
Tracing route to 10.0.2.78 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.0.3.10
2 656 ms 70 ms 76 ms 10.0.2.78
Trace complete.
C:\Windows\system32>tracert 10.0.2.77
Tracing route to 10.0.2.77 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 10.0.3.10
2 568 ms 69 ms 62 ms 10.10.0.28
3 79 ms 84 ms 87 ms 10.0.2.77
Trace complete.
C:\Windows\system32>