Mipango 1.5 kwenye IPsec VPN ya ndani. Kujaribu demos

Hali hiyo

Nilipokea toleo la onyesho la bidhaa za C-Terra VPN toleo la 4.3 kwa miezi mitatu. Ninataka kujua ikiwa maisha yangu ya uhandisi yatakuwa rahisi baada ya kubadili toleo jipya.

Leo si vigumu, mfuko mmoja wa kahawa ya papo hapo 3 kwa 1 inapaswa kutosha. Nitakuambia jinsi ya kupata demo. Nitajaribu kujenga miradi ya GRE-over-IPsec na IPsec-over-GRE.

Jinsi ya kupata onyesho

Inafuata kutoka kwa takwimu kwamba ili kupata onyesho unahitaji:

• Andika barua kwa [barua pepe inalindwa] kutoka kwa anwani ya ushirika;
• Katika barua, onyesha TIN ya shirika lako;
• Orodhesha bidhaa na idadi yao.

Maonyesho ni halali kwa miezi mitatu. Muuzaji hana kikomo utendakazi wao.

Kupanua picha

Onyesho la Lango la Usalama ni picha ya mashine pepe. Ninatumia VMWare Workstation. Orodha kamili ya hypervisors inayotumika na mazingira ya uboreshaji inapatikana kwenye tovuti ya muuzaji.

Kabla ya kuanza, tafadhali kumbuka kuwa hakuna miingiliano ya mtandao katika picha chaguo-msingi ya mashine:

Mantiki iko wazi, mtumiaji lazima aongeze miingiliano mingi kadiri anavyohitaji. Nitaongeza nne mara moja:

Sasa ninaanza mashine ya kawaida. Mara baada ya uzinduzi, lango linahitaji jina la mtumiaji na nenosiri.

Kuna consoles kadhaa katika S-Terra Gateway na akaunti tofauti. Nitahesabu idadi yao katika nakala tofauti. Kwa sasa:
Login as: administrator
Password: s-terra

Ninaanzisha lango. Uanzishaji ni mlolongo wa vitendo: kuingiza leseni, kusanidi jenereta ya nambari ya kibaolojia (simulizi ya kibodi - rekodi yangu ni sekunde 27) na kuunda ramani ya kiolesura cha mtandao.

Ramani ya violesura vya mtandao. Ikawa rahisi

Toleo la 4.2 lilimsalimia mtumiaji anayefanya kazi kwa ujumbe:

Starting IPsec daemon….. failed
ERROR: Could not establish connection with daemon

Mtumiaji anayefanya kazi (kulingana na mhandisi asiyejulikana) ni mtumiaji ambaye anaweza kuanzisha chochote haraka na bila nyaraka.

Hitilafu fulani imetokea kabla ya kujaribu kusanidi anwani ya IP kwenye kiolesura. Yote ni kuhusu ramani ya kiolesura cha mtandao. Ilikuwa ni lazima kufanya:

/bin/netifcfg enum > /home/map
/bin/netifcfg map /home/map
service networking restart

Kwa hivyo, ramani ya kiolesura cha mtandao huundwa ambayo ina upangaji wa majina ya kiolesura halisi (0000:02:03.0) na nyadhifa zao za kimantiki katika mfumo wa uendeshaji (eth0) na kiweko kama cha Cisco (FastEthernet0/0):

#Unique ID iface type OS name Cisco-like name

0000:02:03.0 phye eth0 FastEthernet0/0

Uteuzi wa kimantiki wa miingiliano huitwa lakabu. Lakabu zimehifadhiwa katika faili ya /etc/ifaliases.cf.
Katika toleo la 4.3, wakati mashine ya kawaida inapoanzishwa, ramani ya kiolesura huundwa kiotomatiki. Ukibadilisha idadi ya violesura vya mtandao kwenye mashine pepe, basi tafadhali unda upya ramani ya kiolesura:

/bin/netifcfg enum > /home/map
/bin/netifcfg map /home/map
systemctl restart networking

Mpango wa 1: GRE-over-IPsec

Ninapeleka lango mbili za kawaida, ninabadilisha kama inavyoonyeshwa kwenye takwimu:

Hatua ya 1. Weka anwani za IP na njia

VG1(config) #
interface fa0/0
ip address 172.16.1.253 255.255.255.0
no shutdown
interface fa0/1
ip address 192.168.1.253 255.255.255.0
no shutdown
ip route 0.0.0.0 0.0.0.0 172.16.1.254

VG2(config) #
interface fa0/0
ip address 172.16.1.254 255.255.255.0
no shutdown
interface fa0/1
ip address 192.168.2.254 255.255.255.0
no shutdown
ip route 0.0.0.0 0.0.0.0 172.16.1.253

Kuangalia muunganisho wa IP:

root@VG1:~# ping 172.16.1.254 -c 4
PING 172.16.1.254 (172.16.1.254) 56(84) bytes of data.
64 bytes from 172.16.1.254: icmp_seq=1 ttl=64 time=0.545 ms
64 bytes from 172.16.1.254: icmp_seq=2 ttl=64 time=0.657 ms
64 bytes from 172.16.1.254: icmp_seq=3 ttl=64 time=0.687 ms
64 bytes from 172.16.1.254: icmp_seq=4 ttl=64 time=0.273 ms

--- 172.16.1.254 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 0.273/0.540/0.687/0.164 ms

Hatua ya 2: Sanidi GRE

Ninachukua mfano wa kusanidi GRE kutoka kwa hati rasmi. Ninaunda faili ya gre1 kwenye /etc/network/interfaces.d saraka na yaliyomo.

kwa VG1:

auto gre1
iface gre1 inet static
address 1.1.1.1
netmask 255.255.255.252
pre-up ip tunnel add gre1 mode gre remote 172.16.1.254 local 172.16.1.253 key 1 ttl 64 tos inherit
pre-up ethtool -K gre1 tx off > /dev/null
pre-up ip link set gre1 mtu 1400
post-down ip link del gre1

kwa VG2:

auto gre1
iface gre1 inet static
address 1.1.1.2
netmask 255.255.255.252
pre-up ip tunnel add gre1 mode gre remote 172.16.1.253 local 172.16.1.254 key 1 ttl 64 tos inherit
pre-up ethtool -K gre1 tx off > /dev/null
pre-up ip link set gre1 mtu 1400
post-down ip link del gre1

Ninainua kiolesura kwenye mfumo:

root@VG1:~# ifup gre1
root@VG2:~# ifup gre1

Inaangalia:

root@VG1:~# ip address show
8: gre1@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1400 qdisc noqueue state UNKNOWN group default qlen 1
    link/gre 172.16.1.253 peer 172.16.1.254
    inet 1.1.1.1/30 brd 1.1.1.3 scope global gre1
       valid_lft forever preferred_lft forever

root@VG1:~# ip tunnel show
gre0: gre/ip remote any local any ttl inherit nopmtudisc
gre1: gre/ip remote 172.16.1.254 local 172.16.1.253 ttl 64 tos inherit key 1

C-Terra Gateway ina kivuta pumzi cha pakiti iliyojengewa ndani - tcpdump. Nitaandika utupaji wa trafiki kwa faili ya pcap:

root@VG2:~# tcpdump -i eth0 -w /home/dump.pcap

Ninaanza ping kati ya miingiliano ya GRE:

root@VG1:~# ping 1.1.1.2 -c 4
PING 1.1.1.2 (1.1.1.2) 56(84) bytes of data.
64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=0.918 ms
64 bytes from 1.1.1.2: icmp_seq=2 ttl=64 time=0.850 ms
64 bytes from 1.1.1.2: icmp_seq=3 ttl=64 time=0.918 ms
64 bytes from 1.1.1.2: icmp_seq=4 ttl=64 time=0.974 ms

--- 1.1.1.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 0.850/0.915/0.974/0.043 ms

Mtaro wa GRE unaendelea na unaendelea:

Hatua ya 3. Ficha kwa GOST GRE

Niliweka aina ya kitambulisho - kwa anwani. Uthibitishaji kwa ufunguo ulioainishwa awali (kulingana na Sheria na Masharti, vyeti vya dijitali lazima vitumike):

VG1(config)#
crypto isakmp identity address
crypto isakmp key KEY address 172.16.1.254

Niliweka vigezo vya Awamu ya IPsec:

VG1(config)#
crypto isakmp policy 1
encr gost
hash gost3411-256-tc26
auth pre-share
group vko2

Niliweka vigezo vya Awamu ya II ya IPsec:

VG1(config)#
crypto ipsec transform-set TSET esp-gost28147-4m-imit
mode tunnel

Ninaunda orodha ya ufikiaji kwa usimbaji fiche. Trafiki inayolengwa - GRE:

VG1(config)#
ip access-list extended LIST
permit gre host 172.16.1.253 host 172.16.1.254

Ninaunda ramani ya crypto na kuifunga kwa kiolesura cha WAN:

VG1(config)#
crypto map CMAP 1 ipsec-isakmp
match address LIST
set transform-set TSET
set peer 172.16.1.253
interface fa0/0
  crypto map CMAP

Kwa VG2, usanidi unaonyeshwa, tofauti ni:

VG2(config)#
crypto isakmp key KEY address 172.16.1.253
ip access-list extended LIST
permit gre host 172.16.1.254 host 172.16.1.253
crypto map CMAP 1 ipsec-isakmp
set peer 172.16.1.254

Inaangalia:

root@VG2:~# tcpdump -i eth0 -w /home/dump2.pcap

root@VG1:~# ping 1.1.1.2 -c 4
PING 1.1.1.2 (1.1.1.2) 56(84) bytes of data.
64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=1128 ms
64 bytes from 1.1.1.2: icmp_seq=2 ttl=64 time=126 ms
64 bytes from 1.1.1.2: icmp_seq=3 ttl=64 time=1.07 ms
64 bytes from 1.1.1.2: icmp_seq=4 ttl=64 time=1.12 ms

--- 1.1.1.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 1.077/314.271/1128.419/472.826 ms, pipe 2

Takwimu za ISAKMP/IPsec:

root@VG1:~# sa_mgr show
ISAKMP sessions: 0 initiated, 0 responded

ISAKMP connections:
Num Conn-id (Local Addr,Port)-(Remote Addr,Port) State Sent Rcvd
1 1 (172.16.1.253,500)-(172.16.1.254,500) active 1086 1014

IPsec connections:
Num Conn-id (Local Addr,Port)-(Remote Addr,Port) Protocol Action Type Sent Rcvd
1 1 (172.16.1.253,*)-(172.16.1.254,*) 47 ESP tunn 480 480

Hakuna pakiti kwenye dampo la trafiki la GRE:

Hitimisho: mpango wa GRE-over-IPsec hufanya kazi kwa usahihi.

Mchoro 1.5: IPsec-over-GRE

Sina mpango wa kutumia IPsec-over-GRE kwenye mtandao. Ninakusanya kwa sababu nataka.

Ili kupeleka mpango wa GRE-over-IPsec kwa njia nyingine kote:

• Rekebisha orodha ya ufikiaji wa usimbaji fiche - trafiki inayolengwa kutoka LAN1 hadi LAN2 na kinyume chake;
• Sanidi uelekezaji kupitia GRE;
• Weka cryptomap kwenye kiolesura cha GRE.

Kwa chaguo-msingi, hakuna kiolesura cha GRE kwenye koni ya lango kama la Cisco. Inapatikana tu katika mfumo wa uendeshaji.

Ninaongeza kiolesura cha GRE kwenye koni kama ya Cisco. Ili kufanya hivyo, ninahariri /etc/ifaliases.cf faili:

interface (name="FastEthernet0/0" pattern="eth0")
interface (name="FastEthernet0/1" pattern="eth1")
interface (name="FastEthernet0/2" pattern="eth2")
interface (name="FastEthernet0/3" pattern="eth3")
interface (name="Tunnel0" pattern="gre1")
interface (name="default" pattern="*")

ambapo gre1 ni jina la kiolesura katika mfumo wa uendeshaji, Tunnel0 ni jina la kiolesura katika kiweko kinachofanana na Cisco.

Ninahesabu tena heshi ya faili:

root@VG1:~# integr_mgr calc -f /etc/ifaliases.cf

SUCCESS:  Operation was successful.

Sasa kiolesura cha Tunnel0 kimeonekana kwenye koni kama ya Cisco:

VG1# show run
interface Tunnel0
ip address 1.1.1.1 255.255.255.252
mtu 1400

Kurekebisha orodha ya ufikiaji kwa usimbaji fiche:

VG1(config)#
ip access-list extended LIST
permit ip 192.168.1.0 0.0.0.255 192.168.3.0 0.0.0.255

Ninasanidi njia kupitia GRE:

VG1(config)#
no ip route 0.0.0.0 0.0.0.0 172.16.1.254
ip route 192.168.3.0 255.255.255.0 1.1.1.2

Ninaondoa cryptomap kutoka Fa0 / 0 na kuifunga kwa kiolesura cha GRE:

VG1(config)#
interface Tunnel0
crypto map CMAP

Kwa VG2 ni sawa.

Inaangalia:

root@VG2:~# tcpdump -i eth0 -w /home/dump3.pcap

root@VG1:~# ping 192.168.2.254 -I 192.168.1.253 -c 4
PING 192.168.2.254 (192.168.2.254) from 192.168.1.253 : 56(84) bytes of data.
64 bytes from 192.168.2.254: icmp_seq=1 ttl=64 time=492 ms
64 bytes from 192.168.2.254: icmp_seq=2 ttl=64 time=1.08 ms
64 bytes from 192.168.2.254: icmp_seq=3 ttl=64 time=1.06 ms
64 bytes from 192.168.2.254: icmp_seq=4 ttl=64 time=1.07 ms

--- 192.168.2.254 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 1.064/124.048/492.972/212.998 ms

Takwimu za ISAKMP/IPsec:

root@VG1:~# sa_mgr show
ISAKMP sessions: 0 initiated, 0 responded

ISAKMP connections:
Num Conn-id (Local Addr,Port)-(Remote Addr,Port) State Sent Rcvd
1 2 (172.16.1.253,500)-(172.16.1.254,500) active 1094 1022

IPsec connections:
Num Conn-id (Local Addr,Port)-(Remote Addr,Port) Protocol Action Type Sent Rcvd
1 2 (192.168.1.0-192.168.1.255,*)-(192.168.2.0-192.168.2.255,*) * ESP tunn 352 352

Katika dampo la trafiki la ESP, pakiti zilizowekwa kwenye GRE:

Hitimisho: IPsec-over-GRE inafanya kazi kwa usahihi.

Matokeo ya

Kikombe kimoja cha kahawa kilitosha. Nilichora maagizo ya kupata toleo la onyesho. Imesanidiwa GRE-over-IPsec na kutumwa kinyume chake.

Ramani ya miingiliano ya mtandao katika toleo la 4.3 ni otomatiki! Ninajaribu zaidi.

Mhandisi asiyejulikana
t.me/mhandisi_asiyejulikana

Chanzo: mapenzi.com