Okay now in the previous lecture we've seen how we can fix the association problem if river could not
associate with the target and was just giving you the fail to associate problem in here.
And we've seen how we can fix that by manually associate with the target.
Now in many cases that said that'll be the end of the issues.
So that was a completely separate issue that we solved.
The problem is after we solved that issue we ran river.
We bypassed that issue but we were kind of stuck at 0.00 percent and the river wasn't moving.
It wasn't giving us any information.
So we really didn't know what to do.
So we're kind of stuck on what's the next step.
So what I want to show you in this lecture is a way of debugging and knowing what's happening in the
background.
And we'll see how to bypass the issue that's actually happening.
So first of all before I started trying solutions I want to know what's happening in the background
and to do that.
We're going to run the exact same command using the exact same sequence that we were doing before but
I'm going to add one more argument to the command and that is Dash the the read.
And what this does it basically tells River to produce verbose output which means that it will give
us as much information as possible about what's happening in the background.
Now we usually don't use this option because you'll see the screen will get filled with messages and
it will be hard to track what's happening.
But if you're getting stuck this is the only way for you to debug and know what's happening.
So I'm going to hit enter for this and it's asking me if I want to continue I'm going to say no because
I like to always start from scratch especially if I didn't make any progress.
And before I do that I'll get my command ready here and I'm going to hit enter here you go back here
hit enter to associate and let's see what's happening.
So I'm going to let this run for a little bit and then I'm going to Control-C out of it obviously because
we know this is actually not going to work.
And once we once we stop we're going to analyze the output and see what's happening.
But as you can see it with using a lot of output.
And that's why we usually don't use it.
Should we be worried.
Because if things are going well we actually don't need to see these messages.
OK.
And I think this is enough for us to know what's happening.
So I'm just going to Control-C here and I'm getting Control-C in here.
I'm going to bring this down a little bit so we can focus on the top so we can see the start here.
We can see that it associated here with no problem.
So that's all good and we can see this is the first pin that it's getting so 000 5 5 6 7 3 now it's
sending the requests.
And as you can see it's getting a time out error.
Now let's keep going and see what's happening.
Now we can see after sending the snack packets we're getting a message saying WPX transaction failed
and it's going to try the last pin so it doesn't know whether this point is valid or not.
So it's just going to try the exact same PIN again looking back at what's happening.
The same thing happens that it sends a WASC nag and then again the same thing happens the transaction
fails goes back to trying the same exact pin go down and say the same thing happening and it's still
trying the same pin now.
Looking at this let's look at the help.
So let's do river dash dash help
so show us all the options that we can use with the river.
And if you look in here you'll see we have an option of capital and or dash dash no knocks.
And what this does it tells River not to send NACC messages when out of order packets are received.
Now looking at the output here at the way that river keeps receiving these packets and then it's repeating
the same thing because it's sent in the WSC now.
We can't try to tell the river not to send the snark and just keep trying and see if this actually fixes
the problem because it looks like it's the WASC nak packet's that's causing rebirth to get stuck in
this loop.
So I'm going to run the exact same command again and this time we're either in one more argument and
we're saying no no x.
Ok so I'm going to hit enter again I'm going to say no to start from scratch and I'm going to prepare
my command here.
So Antar Antar and let's see what happens.
Now reverse try and this spin which is 0 0 0 0 5 6 7 8.
Let's see if the next pin is going to be different.
Now I already know the spin is different than the first one because I noticed the first one but let's
see.
And boom your next pin is different now.
0 1 2 3 5 6 7 8 and again.
And you pin.
So we're doing 1 1 1 5 670 and perfect So so far.
River has tried four pins and it's actually making progress so we're not stuck at where we were where
we managed to bypass the zero x 2 ends your x 3 issues and now we can just let weever work and brute
force the password for me.
Now it detected a period delimiting which is another issue that I'm going to cover later but for now
we managed to bypass the Zura x 2 and 0 x 3 issue.
So the take home lesson from this lecture is you can do with the minus v v v to debug and see exactly
what's happening in the background.
You can do dash dash help to see the options and we see how we can use the known acts to bypass the
0 x 2 0 x 3 issues.
Now I want to note that each of these issues now with the router I have right now is a very stubborn
one.
So probably you might not face all of these issues that I'm covering now in a router for example you
might face the issue that I covered previously about the association but everything will run smoothly
after that.
Or maybe you could associate with no problem.
You won't need to manually associate but you'll get stuck after that and you'll have to run v.v see
what's happening and then maybe use no knocks like I showed you.
Or maybe you won't face any of these issues and you might jump straight to the rate limiting issue that
we're getting right now.
I said I'm going to cover later.
So each of these issues I'm putting them in a different lecture because you might only face one of them.
And obviously there might be the case where you face two or three of them like I'm showing you right
now.
But the idea is you might actually only face one of these.
And I want you to understand how to bypass each one of these issues individually instead of just giving
you along River command that will bypass or that will try to bypass most issues.