Hello everybody and welcome to this tutorial. Today, I am going to just
continue up on evil twin. We have managed to get the client to associate with us,
but what good is it? Primarily, because, that client will not have internet
access until we configure our network settings, so that there is a bridge
between our fake wireless access point and our network interface,
which actually has an internet connection. Only then will the client on the other
side actually be able to access the Internet, and only then will we actually be able
to harvest any sort of information, whatsoever. So, on the right side, for this
purpose, I have made a series of commands which you will need to run. And they're
not really complicated, it's more or less the same command running over and over
again with different interfaces. What you will need first is bridge-utils. So go
ahead and type in yum, let me just zoom this in for you, yum search, and I'm just
gonna copy paste the name. Excellent, there we go. So it says bridge-utils.x86_64,
you need to install this. Hopefully by now you have learned how to install
these things, but just in case you didn't, all you need to do is type in yum
install, and then paste that. By default it will pick up that it's this package
x86_64. Just type in yum install bridge-utils -y and that's gonna
install without asking you any questions. Now I have it already installed here, so
there's no need to go through the process. Next up what we need to do is
have this one, it says brctl addbr evil. You can name it any way you like, I have
named it evil, but it doesn't really matter. Whatever name you go with, this
name is completely irrelevant as far as I know, so just go ahead
and type it in. It says device evil already exists; can't create bridge with the same
name. It doesn't matter for me, it already exists because I have previously created.
For you this command will just fly without any sort of problems
whatsoever. Now, the next thing that you need to do, well this is
where it says p8p1, that is the interface, let me just show you, ifconfig,
there's a whole lot of interfaces and information now here. I'm gonna need
to change the zoom here, excellent, this is much better. So, look the interface
p8p1 is the interface that I'm currently using, that is my wired interface, and
that interface has internet access. What I need to do is bridge evil and p8p1,
and that is exactly what this command will do for us. So just go ahead and copy,
there we go. OK, p8p1 is already a member of bridge; can't enslave it to the
bridge evil. So I've already added it, so it
can't repeat the process twice. For you, again, the command will fly. Now, we have
linked this intermediary evil interface, interface named evil, to the interface
p8p1 which actually has Internet connectivity. However, we also need to add
to this the interface which is created by airbase, and that is at0.
Basically, what we're doing is repeating the process twice, so let's just go ahead and
clear the screen, paste. So you see previously I have added p8p1 which
has Internet connectivity to evil, I have bridged them, and now I'm going to bridge
at0 to evil. Don't worry, at0 should be the same on your system because
airbase will create this interface for you. No problems there, all you need to do is
bridge it to this intermediary, and you should eventually have
internet connectivity. Press Enter, again I get an error message because it says
that the process has already taken place and it cannot duplicate it. For you
it's gonna fly. Next up, basically, what we need to do is add IP addresses to these
interfaces, and furthermore we need to change their
state to up. Primarily, because, the states of these
interfaces are not up by default, and that can be a problem. So you just need to
bring it up manually, no big deal, these commands are pretty simple and
straightforward. So, ifconfig, which we've used before, name of the interface,
strange as it might look this actually is the IP address, and just
say up. Excellent! There we go. No confirmation message,
nothing, the command has passed through, excellent! Now we need to bring evil up
as well, also our bridging interface. ifconfig evil up, no need to
assign an IP address there. And we don't need to bring p8p1 of course up,
primarily because it's already up, it has Internet connectivity. Just copy this as
well, paste, so dhclient3 evil &, press ENTER, yep, there we go.
Hold on...wait, wait, wait. Why are you giving me this? Let's remove the
redirection...excellent! There we go. So you can just type in dhclient3 evil and
that should work as well. I'm fairly certain that this command has worked a
moment ago, but it doesn't really matter. It says dhclient is already
running - exiting. So, no need to actually do anything here for me, but for you you
will just need to go and follow through pretty much exactly what I've said. Now,
once this is configured, you see that my airbase on this side is still running
so I have not shut it down since the last time I did this, now the
client on the other side, either the phone, or a tablet, or a computer, or
something of a kind, that is connecting to our fake access point, to our evil
twin, will have internet connectivity, will be able to browse the net, and will
literally suspect nothing. Because, you know, you get disconnected from
wireless, it's not uncommon. I mean, be honest with yourselves.
Ask yourselves if I get disconnected from a wireless for a couple of seconds
will I suspect that there's some foul play here, that
somebody's doing something, or that somebody's hacking, or something of a
kind? No, of course not. If you get deauthenticated you will
simply press reconnect, or the device will reconnect automatically for you. And
while you're waiting for that reconnect you'll probably be staring at the device,
literally looking at it, and not suspecting a thing. Anyway, in the follow up
tutorial I am going to show you how you can actually monitor the
traffic of somebody that is connected to your fake wireless access point, and
how you can extract that information. Until then I bid you farewell, and hope
to see you in the next tutorial.