On Mon, 1 Jul 2002 22:24:11 -0500 "guitarlynn" <[EMAIL PROTECTED]> wrote:
> On Monday 01 July 2002 16:51, Abjin M H wrote: > > Thank you Charles. Now I am getting a different error > > > > Jul 1 14:30:38 babylon ipsec_setup: Starting FreeS/WAN IPsec 1.91... > > Jul 1 14:30:38 babylon ipsec_setup: KLIPS debug `all' > > Jul 1 14:30:39 babylon ipsec_setup: KLIPS ipsec0 on eth0 > > 24.72.35.91/255.255.255.0 broadcast 24.72.35.255 Jul 1 14:30:39 > > babylon ipsec_setup: WARNING: ipsec0 has route filtering turned on, > > KLIPS may not work Jul 1 14:30:39 babylon ipsec_setup: > > (/proc/sys/net/ipv4/conf/ipsec0/rp_filter = `1', should be 0) Jul 1 > > 14:30:39 babylon ipsec_setup: WARNING: eth0 has route filtering > > turned on, KLIPS may not work Jul 1 14:30:39 babylon ipsec_setup: > > (/proc/sys/net/ipv4/conf/eth0/rp_filter = `1', should be 0) Jul 1 > > 14:30:39 babylon ipsec_setup: ...FreeS/WAN IPsec started > > This can be safely ignored and should not affect operation. Unfortunately, I have found this not to be the case with my configuration. I see the above statement on many lists, but a few months ago when I was doing heavy experimentation with freeswan, I found that I needed to unset rp_filter on the interfaces involved. I cannot tell you the specific circumstances involved at the time, only that it was very definitely needed. -- ------------------------------------------------------------------------ Chad Carr [EMAIL PROTECTED] ------------------------------------------------------------------------ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek No, I will not fix your computer. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
