- Posts: 3
- Thank you received: 0
Racoon is using physical interface rather than logical one
- universalCitizen
- Topic Author
- Offline
- New Member
Less
More
16 years 6 months ago #25933
by universalCitizen
Hi,
I have a situation wherein the machine which I am using has
one ethernet card & I have configured two ips on it
eth0 a.b.c.d physical interface
eth0:1 a.b.c.e logical interface
Now, I want to setup ipsec between logical interface eth0:1 and another host a.b.c.f .
The problem is my machine receives isakmp(racoon) messages on logical interface correctly but is sending back isakmp(racoon) messages through physical interface. I am unable to understand the anamoly. Can anybody explain the behaviour?
Regards,
Raj
I have a situation wherein the machine which I am using has
one ethernet card & I have configured two ips on it
eth0 a.b.c.d physical interface
eth0:1 a.b.c.e logical interface
Now, I want to setup ipsec between logical interface eth0:1 and another host a.b.c.f .
The problem is my machine receives isakmp(racoon) messages on logical interface correctly but is sending back isakmp(racoon) messages through physical interface. I am unable to understand the anamoly. Can anybody explain the behaviour?
Regards,
Raj
16 years 6 months ago #25938
by Chris
Chris Partsenidis.
Founder & Editor-in-Chief
www.Firewall.cx
Replied by Chris on topic Re: Racoon is using physical interface rather than logical one
universalCitizen,
Obviously your machine is using eth0 as the the source IP address, when in fact you require it to be eth0:1. This is your problem.
I'd suggest you google around using keywords such as ISAKMP, 'the ipsec service your using', and 'source ip address' and you should get some results back. In needed, try any forums that are associated with the IPSec implementation/package your using to see how you can overcome this issue.
Hope that helps.
Obviously your machine is using eth0 as the the source IP address, when in fact you require it to be eth0:1. This is your problem.
I'd suggest you google around using keywords such as ISAKMP, 'the ipsec service your using', and 'source ip address' and you should get some results back. In needed, try any forums that are associated with the IPSec implementation/package your using to see how you can overcome this issue.
Hope that helps.
Chris Partsenidis.
Founder & Editor-in-Chief
www.Firewall.cx
Time to create page: 0.114 seconds