Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Russian / Re: Вылетает Outlook при запуске
« on: September 19, 2014, 07:23:30 pm »Может кто то может опистаь подробные действия подключения аутлука ? Может не так произвожу настройки...Получилось?
У меня такая же проблема.
2
Доброго Времени суток!!!
У кого нить работает ипсек версии 3.0.3.
У меня пишет ошибку типа он что-то не записал в правилах. В итоге канал вроде есть и нету.
В таблице не хватало -A postmodules -d 192.168.1.0/24 -o eth0 -j ACCEPT. После этого вроде все поднимается.
Модуль битый или руки кривые?
У кого нить работает ипсек версии 3.0.3.
У меня пишет ошибку типа он что-то не записал в правилах. В итоге канал вроде есть и нету.
В таблице не хватало -A postmodules -d 192.168.1.0/24 -o eth0 -j ACCEPT. После этого вроде все поднимается.
Модуль битый или руки кривые?
3
Installation and Upgrades / Re: zentyal 3 and ipsec
« on: October 10, 2012, 07:48:20 am »
are making the correct settings here: /etc/ipsec.conf
further: /etc/init.d/ipsec restart
further: /etc/init.d/ipsec restart
4
Installation and Upgrades / Re: zentyal 3 and ipsec
« on: October 08, 2012, 11:26:15 am »
Does anyone besides me not enjoy ipsec?
Developers are reading this forum?
Developers are reading this forum?
5
Installation and Upgrades / Re: zentyal 3 and ipsec
« on: October 08, 2012, 07:39:27 am »
ip 192.168.1.1
mask 255.255.255.0
Ordered through the console handles config ipseс as it should be, restart it works. Through the web admin panel is not working.
mask 255.255.255.0
Ordered through the console handles config ipseс as it should be, restart it works. Through the web admin panel is not working.
6
Installation and Upgrades / zentyal 3 and ipsec
« on: October 05, 2012, 01:20:16 pm »
Today tried to create a tunnel, but gives this error.
really need ipsec
really need ipsec
7
кусок лога
May 29 08:08:55 router pluto[17726]: packet from 91.219.xxx.xxx:201: ignoring Vendor ID payload [MS NT5 ISAKMPOAKLEY 00000004]
May 29 08:08:55 router pluto[17726]: packet from 91.219.xxx.xxx:201: ignoring Vendor ID payload [FRAGMENTATION]
May 29 08:08:55 router pluto[17726]: packet from 91.219.xxx.xxx:201: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n] method set to=106
May 29 08:08:55 router pluto[17726]: packet from 91.219.xxx.xxx:201: ignoring Vendor ID payload [Vid-Initial-Contact]
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: responding to Main Mode
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: transition from state STATE_MAIN_R0 to state STATE_MAIN_R1
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: STATE_MAIN_R1: sent MR1, expecting MI2
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: NAT-Traversal: Result using draft-ietf-ipsec-nat-t-ike-02/03: peer is NATed
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1127: ignoring informational payload, type NO_PROPOSAL_CHOSEN msgid=00000000
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1127: received and ignored informational message
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: transition from state STATE_MAIN_R1 to state STATE_MAIN_R2
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: STATE_MAIN_R2: sent MR2, expecting MI3
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: Main mode peer ID is ID_FQDN: '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: no suitable connection for peer '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:201
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: Main mode peer ID is ID_FQDN: '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: no suitable connection for peer '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:201
May 29 08:08:57 router pluto[17726]: "vpn_zelik" #1131: Main mode peer ID is ID_FQDN: '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:08:57 router pluto[17726]: "vpn_zelik" #1131: no suitable connection for peer '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:08:57 router pluto[17726]: "vpn_zelik" #1131: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:201
May 29 08:09:01 router pluto[17726]: "vpn_zelik" #1131: Main mode peer ID is ID_FQDN: '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:09:01 router pluto[17726]: "vpn_zelik" #1131: no suitable connection for peer '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:09:01 router pluto[17726]: "vpn_zelik" #1131: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:201
May 29 08:09:09 router pluto[17726]: "vpn_zelik" #1131: Main mode peer ID is ID_FQDN: '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:09:09 router pluto[17726]: "vpn_zelik" #1131: no suitable connection for peer '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:09:09 router pluto[17726]: "vpn_zelik" #1131: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:201
May 29 08:09:25 router pluto[17726]: "vpn_zelik" #1131: Main mode peer ID is ID_FQDN: '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:09:25 router pluto[17726]: "vpn_zelik" #1131: no suitable connection for peer '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:09:25 router pluto[17726]: "vpn_zelik" #1131: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:201
после перезапуска службы соединение не восстанавливается
после перезагрузки соединение восстанавливается
когда впн есть в логах все равно
May 29 09:14:47 router pluto[5703]: "vpn_zelik" #14: the peer proposed: 192.168.0.0/24:0/0 -> 91.219.xxx.xxx/32:0/0
May 29 09:14:47 router pluto[5703]: "vpn_zelik" #14: cannot respond to IPsec SA request because no connection is known for 192.168.0.0/24===62.205.xxx.xxx<62.205.xxx.xxx>[+S=C]...91.219.xxx.xxx<91.219.xxx.xxx>[+S=C]
May 29 09:14:47 router pluto[5703]: "vpn_zelik" #14: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:500
May 29 08:08:55 router pluto[17726]: packet from 91.219.xxx.xxx:201: ignoring Vendor ID payload [MS NT5 ISAKMPOAKLEY 00000004]
May 29 08:08:55 router pluto[17726]: packet from 91.219.xxx.xxx:201: ignoring Vendor ID payload [FRAGMENTATION]
May 29 08:08:55 router pluto[17726]: packet from 91.219.xxx.xxx:201: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n] method set to=106
May 29 08:08:55 router pluto[17726]: packet from 91.219.xxx.xxx:201: ignoring Vendor ID payload [Vid-Initial-Contact]
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: responding to Main Mode
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: transition from state STATE_MAIN_R0 to state STATE_MAIN_R1
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: STATE_MAIN_R1: sent MR1, expecting MI2
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: NAT-Traversal: Result using draft-ietf-ipsec-nat-t-ike-02/03: peer is NATed
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1127: ignoring informational payload, type NO_PROPOSAL_CHOSEN msgid=00000000
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1127: received and ignored informational message
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: transition from state STATE_MAIN_R1 to state STATE_MAIN_R2
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: STATE_MAIN_R2: sent MR2, expecting MI3
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: Main mode peer ID is ID_FQDN: '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: no suitable connection for peer '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:201
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: Main mode peer ID is ID_FQDN: '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: no suitable connection for peer '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:08:55 router pluto[17726]: "vpn_zelik" #1131: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:201
May 29 08:08:57 router pluto[17726]: "vpn_zelik" #1131: Main mode peer ID is ID_FQDN: '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:08:57 router pluto[17726]: "vpn_zelik" #1131: no suitable connection for peer '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:08:57 router pluto[17726]: "vpn_zelik" #1131: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:201
May 29 08:09:01 router pluto[17726]: "vpn_zelik" #1131: Main mode peer ID is ID_FQDN: '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:09:01 router pluto[17726]: "vpn_zelik" #1131: no suitable connection for peer '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:09:01 router pluto[17726]: "vpn_zelik" #1131: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:201
May 29 08:09:09 router pluto[17726]: "vpn_zelik" #1131: Main mode peer ID is ID_FQDN: '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:09:09 router pluto[17726]: "vpn_zelik" #1131: no suitable connection for peer '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:09:09 router pluto[17726]: "vpn_zelik" #1131: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:201
May 29 08:09:25 router pluto[17726]: "vpn_zelik" #1131: Main mode peer ID is ID_FQDN: '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:09:25 router pluto[17726]: "vpn_zelik" #1131: no suitable connection for peer '@keeper1-zlg.xxxxxxxx.xxxxxx.ru'
May 29 08:09:25 router pluto[17726]: "vpn_zelik" #1131: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:201
после перезапуска службы соединение не восстанавливается
после перезагрузки соединение восстанавливается
когда впн есть в логах все равно
May 29 09:14:47 router pluto[5703]: "vpn_zelik" #14: the peer proposed: 192.168.0.0/24:0/0 -> 91.219.xxx.xxx/32:0/0
May 29 09:14:47 router pluto[5703]: "vpn_zelik" #14: cannot respond to IPsec SA request because no connection is known for 192.168.0.0/24===62.205.xxx.xxx<62.205.xxx.xxx>[+S=C]...91.219.xxx.xxx<91.219.xxx.xxx>[+S=C]
May 29 09:14:47 router pluto[5703]: "vpn_zelik" #14: sending encrypted notification INVALID_ID_INFORMATION to 91.219.xxx.xxx:500
9
Russian / Re: pptp и dns
« on: February 22, 2012, 04:50:11 pm »
проблемма была в том, что у днс был другой прописан шлюз
11
Russian / pptp и dns
« on: February 15, 2012, 08:26:36 pm »
подключаюсь по pptp соединение есть, внутренняя сеть пингуется по ип подключнение по рдп тоже есть но по ип. Пинговать по доменному имени не получаеться. В настройках сервера указал основной днс сервера локальной сети(АД). в чем может быть проблемма?
Pages: [1]