m**t
发帖数: 1292 | 1
I am just giving perspective from the spec point of view, HUgh actually may
have a lot in the practical world how the products implement the
features
IKE is a peer to peer protocol, taht means with proper policy imposed on
both peers, whenever a peer needs to talk to the other, it needs to
set up the SA first, so for the responder(the one who receives the packets),
the SA should have been in place since the initiator was supposed to
do the IKE whenever the initiator sees the outbound packets | h**h
发帖数: 132 | 2 Most of my experiences are w/ Cisco, but for network administrator,
we only know a few outmost configs, and a very limited understanding
of the inner theory:-(
For speed of IPSec, there are two different things
1> for interactive traffic, such as telnet, it may be slow, not only
because the buffer of packets, but also protocol overhead
2> Encryption overhead, it depends on whether it is a hardware based
or software based, many of cisco's devices are utilizing ASIC and offload
encryption from pro | h**h
发帖数: 132 | 3 I guess so, at least that's what we do. both need to configure
for the particular peers, some steps but not limited to these
1> make sure both are using the same encryption, transform-set
authentication, using correct trigger for interesting traffic and etc.
2> generate keys (say RSA-Encrypted nonces) if none
3> obtain pubkey and distribute to the other (manual process)
4> configure pubkey for remote peer
5> test it out!!!
again, IPSec only works for peer session for particular interesting
packe |
|
