Hi guys,
I have the following scenario, VPCOM VPN Client running on Windows machine, which really behaves more like a gateway than a Client because it creates a virtual adapter and uses
its ip address as LAN and a Linux machine running RH 6.2 (kernel 2.2.16) with FreS/WAN 1.5 and Roadwarrior configuration on the Linux side. The Client software allows you to specify also protocol/port entry that you want to protect. Also in the Client you have to start Phase 1 and Phase 2 separately, which is also starnge. IPSec is negotiated properly and everything works fine.
But when I upgared my Linux box to kernel 2.4.5 and FreeS/WAN 1.91 and didn't touched the Client side,
my Quick Mode negotiation fails and I can see the following errors:
<<Client ID payload ID_IPV4_ADDR specifies protocol 4, we only support 0>>
if I change to a different protocol/port entry in my client side I have the same message with just changed number for the << protocol>>> part in the logs saying:
<<Client ID payload ID_IPV4_ADDR specifies protocol 1, we only support 0>> etc.
So I wonder if there is any difference in the code which is making any extra check for protocol/port entries in FreeS/WAN 1.91 compared to FreeS/WAN 1.5. I know that it is not supported in the code, to specify which traffic to be protected and which not, but I just want to see what is going on? Any help will be greatly appreciated.
TIA,
Kaloyan Kaloyanov