[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(racoon 832) Starter question
- To: racoon@kame.net
- Subject: (racoon 832) Starter question
- From: Dale Amon <amon@vnl.com>
- Date: Sat, 23 Oct 2004 03:28:36 +0100
- Delivered-to: racoon-archive@kame.net
- Delivered-to: racoon-outgo@kame.net
- Delivered-to: racoon@kame.net
- Reply-to: racoon@kame.net
- Sender: owner-racoon@kame.net
- User-agent: Mutt/1.5.6+20040722i
I set up a test on my internal lan and ran into what
I presume is a simple problem.
I added eth0:1 as 10.0.0.3 on the target test machine,
in addition to it's normal ip. I have to do this because
the machine does other things as well.
I set up my laptop to talk to that new ip using racoon
for the key exchange, but it balks because:
2004-10-23 03:23:49: NOTIFY: the packet is retransmitted by 10.0.0.41[500].
so apparently the racoon on the target machine is
rcving the query on 10.0.0.3 but responding on the
main ip. I've already told it to listen {} only on
10.0.0.3. Of course listen != reply, so is there
some way to tell it to only reply on the ip over
which it rcvd the query?
--
------------------------------------------------------
Dale Amon amon@islandone.org +44-7802-188325
International linux systems consultancy
Hardware & software system design, security
and networking, systems programming and Admin
"Have Laptop, Will Travel"
------------------------------------------------------