Hello and welcome to this lecture.
So let's now continue with the second troubleshooting scenario and specifically in this case I will
break the ice the camp say and let us go now.
So first before breaking it you can see that both of them are working so yep this is from the VPC is
one so pinging the VPC is in the assay branch and the second one it's pinging from the branch for the
gate going to the headquarter for the gate.
So we see that both are working now.
Let's go.
And again let's say.
Mean and I will break.
Now what.
Let's choose somehow together so.
Edit and authentication we have tested it.
So the Phase 1 proposal I would click edit and let's say we have authentication empty five.
So.
OK.
And let's see
now I say bring down yes and I'll try to bring it up but it's not working because authentication is
not the same.
Good.
So now let's concentrate on the bugs.
So I will take again the bugs.
So again start the debug for application Ike and enable it enable and debug and restart the whole process
so that we can see the negotiation.
We will see to things like in the previous lecture one is going to be successful for the branch for
the gate and for the SSA.
It will not work.
It will be broken.
So here it is
perfect.
Now let's stop it
and yep now Let's navigate the beginning and here it is.
Yes.
So let's see for branch 1 and branch 2 range 1.
This worm
for branch one initiate their main mode get first response.
I'm seeing here negotiation result for the proposal lifetime.
I should see now.
The authentication is successful.
Well let's see where is that perfect for branch 1 peer identifier is this authentication is okay established
I guess.
Perfect.
Now we move on to branch 2 so branch 2.
Let's see the message.
So here it is.
Branch 2 sent an Ike message from our self to the to the essay and here is ignoring unsupported informational
message.
Pretty self-explanatory huh.
No it's not.
So if it didn't or haven't seen this message uh I don't know before I'm pretty much sure that you wouldn't
guess exactly what this message is about.
So ignoring unsupported informational message that's not so self explanatory right.
So let's just start again.
I want to see some more logs like this.
I stopped in very very very very fast.
So here is ignoring ignoring unsupported informational message again for branch to branch 2 again here.
And guess what.
This message will not change.
Just repeat ignoring for branch 2 Ignoring unsupported informational message ignoring unsupported informational
message and again send a message.
Re transmit for Phase 1 p. 1 means Phase 1.
This is us and the NSA again ignoring unsupported information on message.
So yeah I know it's not that obvious.
So that's why I'm.
I'm also recording this.
This troubleshooting scenarios so that you will be well prepared when you encounter such a problem.
So you will see that the last troubleshooting scenario regarding Phase 2.
So the IP said negotiation he it's more human.
It's kind of readable but the first two are and are not so I believe that you agree with me so I will
take this message and paste it here as well.
And here are the two.
So for the pressure key mismatch ignoring unencrypted payload malformed from this IP address from the
NSA and for essay proposal proposals that do not match.
Ignoring unsupported information on message.
Wow.
Anyway so now let's let's have it working before moving to the next lecture so let's go through the
VPN and IP SEC tunnels.
So.
Edit The branch too.
We will go to the Phase 1 proposal and get back to show 1.
Just accept the configuration and heat.
Okay.
Wish should see again that the communication between the LAN user in the headquarter.
It's fine.
It's working with the land user in the in the NSA branch and here it is.
So the ping is successful.
We're happy happy.
Problem solved.
So see you in the next lecture.
Thanks a lot.