WEBVTT

0:00:03.160000 --> 0:00:07.440000
 Hello and welcome this video, which
 is a refresher on CAPWAP.

0:00:07.440000 --> 0:00:10.480000
 So let's go ahead and talk
 about what that is.

0:00:10.480000 --> 0:00:16.500000
 Okay, so imagine this
 for a moment.

0:00:16.500000 --> 0:00:20.880000
 You have this appliance called a wireless
 LAN controller, a physical box

0:00:20.880000 --> 0:00:25.560000
 that you purchase, you rack mounted
 it somewhere on one side of it.

0:00:25.560000 --> 0:00:30.920000
 Well, it's got some cables, some
 ethernet cables coming out of it.

0:00:30.920000 --> 0:00:35.000000
 And this wireless LAN controller can
 receive lots of different things.

0:00:35.000000 --> 0:00:40.040000
 For example, you could tell net
 to it, you could SSH to it.

0:00:40.040000 --> 0:00:44.660000
 It probably even has a GUI so
 you can HTTP or HTTPS to it.

0:00:44.660000 --> 0:00:48.160000
 So it can receive from you
 lots of different things.

0:00:48.160000 --> 0:00:53.400000
 In addition to that, we have some access
 points scattered throughout our

0:00:53.400000 --> 0:00:57.940000
 company. And those access points are
 going to be sending very specific

0:00:57.940000 --> 0:01:00.640000
 data to this wireless
 LAN controller.

0:01:00.640000 --> 0:01:06.640000
 For example, they're going to be sending
 radio information about RF statistics,

0:01:06.640000 --> 0:01:10.840000
 how many clients are on the BSS,
 who's just connected, who hasn't.

0:01:10.840000 --> 0:01:14.500000
 They're going to be forwarding client
 authentication information.

0:01:14.500000 --> 0:01:19.040000
 So, and then the clients themselves in
 a lightweight access point situation,

0:01:19.040000 --> 0:01:23.880000
 now not all of them are like this, but
 least in Cisco's implementation,

0:01:23.880000 --> 0:01:27.760000
 when you are connected to your Wi-Fi
 access point wirelessly and you're

0:01:27.760000 --> 0:01:32.560000
 sending data, once that data hits the
 Wi-Fi access point, it actually

0:01:32.560000 --> 0:01:37.020000
 has to go all the way is directed,
 all the way to the controller, and

0:01:37.020000 --> 0:01:42.080000
 then from there, it's released
 onto the wired network.

0:01:42.080000 --> 0:01:46.360000
 So this controller has to have some way
 of differentiating, hey, I'm receiving

0:01:46.360000 --> 0:01:50.380000
 till net packets, someone's trying to
 get access to my command line, I'm

0:01:50.380000 --> 0:01:54.900000
 receiving HTTP, someone's trying to
 get into my GUI, it also has to have

0:01:54.900000 --> 0:01:57.900000
 some way of differentiating, oh, here
 comes some information from one

0:01:57.900000 --> 0:02:01.600000
 of my access points, who's reporting
 information about himself to me,

0:02:01.600000 --> 0:02:02.780000
 some RF information.

0:02:02.780000 --> 0:02:05.240000
 Oh, he's reporting someone's
 trying to authenticate.

0:02:05.240000 --> 0:02:08.940000
 Oh, here's some actual data from a
 Wi-Fi client way down there that I

0:02:08.940000 --> 0:02:10.140000
 need to deal with.

0:02:10.140000 --> 0:02:16.120000
 So, the controller needs some way of
 saying, oh, here comes a packet,

0:02:16.120000 --> 0:02:20.740000
 I recognize that the body of this
 packet is special Wi-Fi stuff.

0:02:20.740000 --> 0:02:24.280000
 It's either an access point who is reaching
 out to me to be managed, or

0:02:24.280000 --> 0:02:27.700000
 it's a client connected that access
 point who's trying to get down to

0:02:27.700000 --> 0:02:33.280000
 the wired LAN. So, CapWAP is the protocol
 that's used between the access

0:02:33.280000 --> 0:02:38.120000
 point and the controller to send
 all that stuff back and forth.

0:02:38.120000 --> 0:02:43.000000
 So, CapWAP stands for the control and
 provisioning of wireless access

0:02:43.000000 --> 0:02:47.500000
 points. It is a standard, here's several
 RFCs in case you want to look

0:02:47.500000 --> 0:02:50.800000
 it up, and it's a tunneling protocol
 between the lightweight access point

0:02:50.800000 --> 0:02:53.380000
 and the wireless LAN controller.

0:02:53.380000 --> 0:02:59.100000
 So, basically what's going to happen
 is when that access point, let's

0:02:59.100000 --> 0:03:02.560000
 say the access point says, hey, I need
 to report back to the wireless

0:03:02.560000 --> 0:03:09.820000
 LAN controller about how many clients I
 have right now, my RF health statistics.

0:03:09.820000 --> 0:03:13.360000
 I've gathered about
 rogue access points.

0:03:13.360000 --> 0:03:18.360000
 It will collect all that stuff, put it
 inside of an IP packet, put a CapWAP

0:03:18.360000 --> 0:03:21.720000
 header in front of that saying, hey,
 here's some information about myself,

0:03:21.720000 --> 0:03:25.940000
 and then send that to the controller,
 which could be two, three, four,

0:03:25.940000 --> 0:03:28.100000
 seven routers away.

0:03:28.100000 --> 0:03:33.320000
 So, it's an encapsulation
 protocol.

0:03:33.320000 --> 0:03:39.380000
 So, actually, access points and controllers,
 like it said, build two CapWAP

0:03:39.380000 --> 0:03:41.700000
 tunnels between themselves.

0:03:41.700000 --> 0:03:47.960000
 One tunnel is used to manage
 or control the access points.

0:03:47.960000 --> 0:03:52.060000
 So, if you are on the controller's
 GUI or on the controller's command

0:03:52.060000 --> 0:03:56.600000
 line and you configure a new wireless
 LAN with some new security parameters

0:03:56.600000 --> 0:04:00.100000
 and you want to push that down to all
 the access points, that's going

0:04:00.100000 --> 0:04:05.000000
 to go down one CapWAP tunnel to
 all the different access points.

0:04:05.000000 --> 0:04:09.460000
 So, not just one, but each access points
 can have its own individual CapWAP

0:04:09.460000 --> 0:04:12.020000
 tunnel going to the controller.

0:04:12.020000 --> 0:04:16.360000
 And then another CapWAP tunnel is used
 for the actual Wi-Fi clients to

0:04:16.360000 --> 0:04:19.580000
 send their data on to get
 to that controller.

0:04:19.580000 --> 0:04:22.700000
 So, here's a picture of
 what that looks like.

0:04:22.700000 --> 0:04:25.060000
 So, notice some very important
 stuff right here.

0:04:25.060000 --> 0:04:28.140000
 These tunnels are built in UDP.

0:04:28.140000 --> 0:04:31.960000
 Okay? So, regardless of what
 your actual data is.

0:04:31.960000 --> 0:04:37.240000
 So, imagine for a moment that I'm doing
 web browsing on my wireless laptop.

0:04:37.240000 --> 0:04:39.940000
 Right? So, web browsing
 is TCP based.

0:04:39.940000 --> 0:04:41.360000
 Right? It is TCP based.

0:04:41.360000 --> 0:04:46.760000
 But what's going to happen is I'm going
 to create my TCP segment with

0:04:46.760000 --> 0:04:48.300000
 my IP header in front of it.

0:04:48.300000 --> 0:04:50.840000
 You know, it's got my HTTP
 stuff inside of it.

0:04:50.840000 --> 0:04:54.480000
 Then I'm going to put a 802
.11 header in front of that.

0:04:54.480000 --> 0:04:55.560000
 So, it's not an Ethernet header.

0:04:55.560000 --> 0:04:58.840000
 It's an 802.11 Wi-Fi header,
 which is very big.

0:04:58.840000 --> 0:05:00.560000
 Lots of different fields in it.

0:05:00.560000 --> 0:05:04.680000
 And then I'm going to transmit it
 wirelessly to the access point.

0:05:04.680000 --> 0:05:10.680000
 Once he gets it, he's going to strip off
 that 802.11 header, because that's

0:05:10.680000 --> 0:05:14.080000
 only used over the air,
 over the Wi-Fi.

0:05:14.080000 --> 0:05:17.320000
 And then what he's going to do, he's
 going to take my IP packet with my

0:05:17.320000 --> 0:05:23.900000
 TCP and append in front of that
 another IP header using UDP.

0:05:23.900000 --> 0:05:29.260000
 UDP port, in this case, if it's data,
 UDP port 5247, as we can see right

0:05:29.260000 --> 0:05:39.060000
 here. And that will be directed
 to the wireless LAN controller.

0:05:39.060000 --> 0:05:46.820000
 So, CAPWAP control messages, which
 go across that control tunnel, are

0:05:46.820000 --> 0:05:49.260000
 authenticated and encrypted.

0:05:49.260000 --> 0:05:53.120000
 It actually uses X.509 digital
 certificates for that.

0:05:53.120000 --> 0:05:58.300000
 So, every lightweight access point comes
 pre-built with a digital certificate

0:05:58.300000 --> 0:06:00.420000
 already installed on it.

0:06:00.420000 --> 0:06:04.480000
 And when it discovers the wireless LAN
 controller, who also has a digital

0:06:04.480000 --> 0:06:08.620000
 certificate on him, there's this
 exchange of digital certificates.

0:06:08.620000 --> 0:06:11.640000
 And that's how they can build this
 encrypted tunnel for the control of

0:06:11.640000 --> 0:06:15.360000
 the access point.

0:06:15.360000 --> 0:06:19.740000
 And that uses UDP port 5246.

0:06:19.740000 --> 0:06:22.660000
 That's the control tunnel.

0:06:22.660000 --> 0:06:25.480000
 Now, the data tunnel is
 like I was describing.

0:06:25.480000 --> 0:06:29.160000
 That's for all the frames at my laptop
 or my smartphone or my tablet is

0:06:29.160000 --> 0:06:30.640000
 sending wirelessly.

0:06:30.640000 --> 0:06:34.660000
 It uses UDP port 5247.

0:06:34.660000 --> 0:06:39.540000
 This is not encrypted by default.

0:06:39.540000 --> 0:06:46.920000
 But we can, if optionally, add
 dTLS for additional encryption.

0:06:46.920000 --> 0:06:50.640000
 And so this is what it looks like.


0:06:50.640000 --> 0:06:56.460000
 So, just to reinforce what I was mentioning
 just a moment ago, this might

0:06:56.460000 --> 0:07:02.520000
 be my HTTP data or my HTTP S data if
 I'm browsing a website, which means

0:07:02.520000 --> 0:07:11.380000
 I'm using TCP. This right here is
 the IP address of the website.

0:07:11.380000 --> 0:07:20.540000
 Maybe Iany.com. When that gets to the
 Wi-Fi access point that's in the

0:07:20.540000 --> 0:07:25.300000
 ceiling right above me, he strips
 off my 802.11 header.

0:07:25.300000 --> 0:07:26.760000
 So, we don't see that right here.

0:07:26.760000 --> 0:07:28.920000
 But there's an 802
.11 Wi-Fi header.

0:07:28.920000 --> 0:07:30.080000
 He strips that off.

0:07:30.080000 --> 0:07:33.740000
 And in front of all of this,
 he adds a calf web header.

0:07:33.740000 --> 0:07:36.240000
 And we can see that right here.

0:07:36.240000 --> 0:07:41.700000
 Okay. If you're interested in what these
 fields mean, I would recommend

0:07:41.700000 --> 0:07:45.140000
 that you go to, by the way, you don't
 have to know that for the CCNA.

0:07:45.140000 --> 0:07:52.780000
 I recommend you go to RSC5415
 and you look in section 4.3.

0:07:52.780000 --> 0:07:56.960000
 Section 4.3 goes into the
 details of what these are.

0:07:56.960000 --> 0:08:04.380000
 But the calf web header and the access
 point adds a UDP header to that.

0:08:04.380000 --> 0:08:05.860000
 Followed by an IP header.

0:08:05.860000 --> 0:08:12.260000
 Now this IP header, the destination
 is the wireless LAN controller.

0:08:12.260000 --> 0:08:15.640000
 And then we have the Ethernet header
 to get it to the next hop, which

0:08:15.640000 --> 0:08:17.620000
 is probably a router.

0:08:17.620000 --> 0:08:26.120000
 And we know that the UDP will
 be either 5246 or 5247.

0:08:26.120000 --> 0:08:30.560000
 Depending on if what's being carried is
 actually application data or control

0:08:30.560000 --> 0:08:36.160000
 data from the access point itself.


0:08:36.160000 --> 0:08:41.400000
 So that concludes this overview
 and refresher of calf web.

