Re: OpenVPN jak skonfigurować routing

Article View: pl.comp.sieci

Article #57221

#57221

From: markpunk
Date: Wed, 13 Dec 2017 21:35

111 lines
7023 bytes

W dniu środa, 13 grudnia 2017 10:58:28 UTC+1 użytkownik elmer radi radisson napisał:
> On 2017-12-08 20:03, markpunk wrote:
> 
> > wyglądało obiecująco ale nadal coś robię źle
> 
> Skoro juz sa logi (prawidlowo), wypadaloby sie zainteresowac bledami ;)
> 
> > Fri Dec 08 19:40:44 2017 C:\Windows\system32\route.exe ADD 192.168.1.128 MASK 255.255.255.0 10.4.0.2
> > Fri Dec 08 19:40:44 2017 Warning: address 192.168.1.128 is not a network address in relation to netmask 255.255.255.0
> > Fri Dec 08 19:40:44 2017 ROUTE: route addition failed using CreateIpForwardEntry: Parametr jest niepoprawny.   [status=87 if_index=9]
> > Fri Dec 08 19:40:44 2017 Route addition via IPAPI failed [adaptive]
> 
> Skad pomysl na 192.168.1.128? Proponuje zmienic po prostu na 192.168.1.0


to był jakiś wypadek przy pracy

 
> Tak swoja droga, skoro serwer stoi na Windows, zakladam ze odpaliles ip 
> forwarding/routing?

nie bardzo rozumiem, rozwiń myśl proszę



generalnie robię postępy:

wyedytowałem w rejestrze wpis (zarówno na serverze jak i kliencie)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Double click the IPEnableRouter entry and set the Value data field to ‘1’ 



następnie w server.ovpn dodałem następujące routy:
route 192.168.1.0 255.255.255.0
push "route 192.168.2.0 255.255.255.0"
push "route 192.168.1.0 255.255.255.0"

client-to-client


w konfigu klienta w ccd dodałem jedynie:
iroute 192.168.1.0 255.255.255.0



i teraz tak z punktu widzenia servera wszystko jest zajebiście
pinguje klienta, łączę sie remote desktopem etc

z podsieci servera po dodaniu odpowiedniego route add  jestem w stanie połaczyć z klientem za pomocą RDP ale nie jestem w stanie go pingowac

i analogicznie ze strony klienta jestem w stanie połaczyć się za pomocą RDP z serverem ale nie jestem w stanie go pingować ani na adresie 192.168.2.100 ani 10.4.0.1


route print z servera wygląda tak:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.2.1    192.168.2.100     25
         10.4.0.0    255.255.255.0         On-link          10.4.0.1    291
         10.4.0.1  255.255.255.255         On-link          10.4.0.1    291
       10.4.0.255  255.255.255.255         On-link          10.4.0.1    291
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
      192.168.1.0    255.255.255.0         10.4.0.2         10.4.0.1     35
      192.168.2.0    255.255.255.0         On-link     192.168.2.100    281
    192.168.2.100  255.255.255.255         On-link     192.168.2.100    281
    192.168.2.255  255.255.255.255         On-link     192.168.2.100    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link          10.4.0.1    291
        224.0.0.0        240.0.0.0         On-link     192.168.2.100    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link          10.4.0.1    291
  255.255.255.255  255.255.255.255         On-link     192.168.2.100    281
===========================================================================



a z klienta tak:

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1    192.168.1.100     35
         10.4.0.0    255.255.255.0         On-link          10.4.0.2    291
         10.4.0.2  255.255.255.255         On-link          10.4.0.2    291
       10.4.0.255  255.255.255.255         On-link          10.4.0.2    291
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
      192.168.1.0    255.255.255.0         On-link     192.168.1.100    291
    192.168.1.100  255.255.255.255         On-link     192.168.1.100    291
    192.168.1.255  255.255.255.255         On-link     192.168.1.100    291
      192.168.2.0    255.255.255.0         10.4.0.1         10.4.0.2     35
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link          10.4.0.2    291
        224.0.0.0        240.0.0.0         On-link     192.168.1.100    291
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link          10.4.0.2    291
  255.255.255.255  255.255.255.255         On-link     192.168.1.100    291
===========================================================================





dlaczego nie chodzą pingi i dlaczego nie widze na kliencie trasy do 10.4.0.0 przez 10.4.0.1 ?

Technical Details

Message-ID: <f7ce4789-7d4b-4670-a4de-64ca518f1b19@googlegroups.com>

Path:

mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!peer02.am4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!g35no541810qtk.1!news-out.google.com!t48ni290qtc.1!nntp.google.com!g35no541804qtk.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail

References:

<d95d999c-baab-46e3-bbcd-ff92f2c6d54c@googlegroups.com> <5a145e13$0$5155$65785112@news.neostrada.pl> <7601eb8e-e800-448a-b5c9-8dddf14f098d@googlegroups.com> <ov6bau$qnr$1@portraits.wsisiz.edu.pl> <5a4d5ac5-6739-4fd7-838e-f6bf272e3778@googlegroups.com> <p08ijl$fg9$1@portraits.wsisiz.edu.pl> <p08j7s$glc$1@portraits.wsisiz.edu.pl> <bd51d29e-60e1-4126-af83-3a152b064c51@googlegroups.com> <p0qtk4$lqm$1@portraits.wsisiz.edu.pl>

Show Full Headers

Complete Article Headers

X-Received: by 10.200.35.113 with SMTP id b46mr6435846qtb.48.1513200935215;        Wed, 13 Dec 2017 13:35:35 -0800 (PST)
X-Received: by 10.31.94.215 with SMTP id s206mr873782vkb.1.1513200934976; Wed, 13 Dec 2017 13:35:34 -0800 (PST)
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!peer02.am4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!g35no541810qtk.1!news-out.google.com!t48ni290qtc.1!nntp.google.com!g35no541804qtk.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: pl.comp.sieci
Date: Wed, 13 Dec 2017 13:35:34 -0800 (PST)
In-Reply-To: <p0qtk4$lqm$1@portraits.wsisiz.edu.pl>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=87.207.62.176; posting-account=X7Ky1woAAAD8hRHIDu-SyiBI46tOA_3K
NNTP-Posting-Host: 87.207.62.176
References: <d95d999c-baab-46e3-bbcd-ff92f2c6d54c@googlegroups.com> <5a145e13$0$5155$65785112@news.neostrada.pl> <7601eb8e-e800-448a-b5c9-8dddf14f098d@googlegroups.com> <ov6bau$qnr$1@portraits.wsisiz.edu.pl> <5a4d5ac5-6739-4fd7-838e-f6bf272e3778@googlegroups.com> <p08ijl$fg9$1@portraits.wsisiz.edu.pl> <p08j7s$glc$1@portraits.wsisiz.edu.pl> <bd51d29e-60e1-4126-af83-3a152b064c51@googlegroups.com> <p0qtk4$lqm$1@portraits.wsisiz.edu.pl>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <f7ce4789-7d4b-4670-a4de-64ca518f1b19@googlegroups.com>
Subject: Re: OpenVPN jak skonfigurować routing
From: markpunk <markpunk@poczta.fm>
Injection-Date: Wed, 13 Dec 2017 21:35:35 +0000
X-Received-Body-CRC: 455139711
X-Received-Bytes: 7773
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Reply to Parent Message