support ah and esp protocals #775
Conversation
| esp_error: | ||
| proto_unregister(&dp_vs_proto_esp); | ||
| ah_error: | ||
| proto_unregister(&dp_vs_proto_ah); | ||
| return err; | ||
| } |
There was a problem hiding this comment.
Please unregister protocols in the reverse order when error occurs. Note the label sequence.
There was a problem hiding this comment.
yes, I have fixed it. thank you.
| &iph->saddr, &iph->daddr, | ||
| htons(PORT_ISAKMP), htons(PORT_ISAKMP), | ||
| direct, reverse); | ||
|
|
There was a problem hiding this comment.
Does it need to support connection redirection?
There was a problem hiding this comment.
it's logic for the first negotiation packages and the process is similar to the kernel ipvs code.
|
Does AE/ESP work with DPVS Fullnat? |
ywc689
added
the
pr/codes-need-change
I tested the code in the DR mode and it worked well when I use the ipsec protocal and I think it can work well in FullNat mode and Tunnel mode. It just helps the dpvs for more protocal support such as ah and esp. The use is totally the same. The users just need to configure the dpvs server in port 500(PORT_ISAKMP) and it can deal with the ipsec process logic. |
support ah and esp protocals