ALT Linux Community general discussions
 help / color / mirror / Atom feed
From: svgol@samkon.ru
To: Community <community@altlinux.ru>
Subject: Re: [Comm] IPSec help need
Date: Tue, 15 Jul 2003 12:06:33 +0400
Message-ID: <20030715080633.GA5662@sysadm.hq.samkon.ru> (raw)
In-Reply-To: <20030712135149.71cdf32b.gosha@zkb.ru>

On 12 Jul Sat 13:51, Igor Solovyov wrote:
<skip>
> 
> А в /etc/ipsec.conf:
> 
> xxx.xxx.xxx.2 yyy.yyy.yyy.2: PSK "My_Very_Secure_Key"

имеется в виду /etc/ipsec.secrets?

> стартую - service ipsec start, а в логах вижу:
> 
> WARNING: ipsec0 has route filtering turned on, KLIPS
> may not work (/proc/sys/net/ipv4/conf/ipsec0/rp_filter = `1',
> should be 0)
> 
> Вопрос 1:
> Интересно как это я должен сделать
> /proc/sys/net/ipv4/conf/ipsec0/rp_filter=0
> если интерфейс ipsec0 до старта ipsec еще не существует?
> Я закинул туда 0 уже после поднятия ipsec0, это правильно?

Из FAQ:

To get rid of this message you can add the following rules 
into your firewall configuration script:

for interface in /proc/sys/net/ipv4/conf/*/rp_filter; do /bin/echo "0" > ${interface}; done 

> 
> далее делаю:
>  
> # ipsec manual --up My_Conn

для "ручных" каналов нужно  указывать ключи в файле /etc/ipsec.conf
или включать другой файл с ключами опцией also. Если я правильно понял,
Вы пытаетесь использовать  общий ключ из /etc/ipsec.secrets, а это уже
"автоматический" канал. Соответственно, команда

ipsec auto --up My_Conn


-- 
Sergey V. Golovin


  reply	other threads:[~2003-07-15  8:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-12  7:51 Igor Solovyov
2003-07-15  8:06 ` svgol [this message]
2003-07-15 17:02   ` Igor Solovyov
2003-07-16  9:56     ` svgol
2003-07-16 10:53       ` Dmitriy Gnidchenko
2003-07-16 11:18         ` Igor Solovyov
2003-07-16 11:44           ` Dmitriy Gnidchenko
2003-07-16 15:56             ` Igor Solovyov
2003-07-16 16:23               ` Dmitriy Gnidchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030715080633.GA5662@sysadm.hq.samkon.ru \
    --to=svgol@samkon.ru \
    --cc=community@altlinux.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Community general discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
		mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
	public-inbox-index community

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.community


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git