1
00:00:00,409 --> 00:00:09,158
[music]

2
00:00:09,159 --> 00:00:12,908
All right, now we're
going to look at

3
00:00:12,920 --> 00:00:17,670
full-blown DHCP server
configuration with IPv6.

4
00:00:17,671 --> 00:00:24,043
Again, we're going to be using, of course,
a router as the client and the server.

5
00:00:24,044 --> 00:00:28,015
We're going to stick with the same
topology we've used in previous lessons.

6
00:00:28,016 --> 00:00:31,204
Again, Router 3 and Router 6.

7
00:00:31,205 --> 00:00:34,115
For now, Router 3 is
going to be our server.

8
00:00:34,115 --> 00:00:38,012
Router 6 is going to be our client.

9
00:00:38,013 --> 00:00:41,267
We're going to start off
with the basic steps here,

10
00:00:41,267 --> 00:00:45,751
configuring the IPv6 router DHCP scope.

11
00:00:45,751 --> 00:00:47,684
If you've been following
through the other lessons,

12
00:00:47,685 --> 00:00:52,242
you know we'd already done some stuff
but I did clean that up just so we

13
00:00:52,243 --> 00:00:58,754
could start fresh here in this section.

14
00:00:58,754 --> 00:01:01,845
The first thing we're going to have to
do, but I do have the debugging on.

15
00:01:01,845 --> 00:01:03,403
Right now, I'm debugging.

16
00:01:03,404 --> 00:01:06,957
Let me just show you.

17
00:01:06,958 --> 00:01:13,870
We're debugging IPv6 DHCP on
both Router 6 and on Router 3.

18
00:01:13,871 --> 00:01:21,513
Right now Router 6 is set of course just
with a link local address, nothing more.

19
00:01:21,514 --> 00:01:25,951
Router 3 his running
config for his interface

20
00:01:25,963 --> 00:01:29,832
has the link local,
his global address,

21
00:01:29,833 --> 00:01:33,895
and I do still have the interval
modified to 30 seconds for the router

22
00:01:33,896 --> 00:01:37,262
advertisement but that's it.

23
00:01:37,262 --> 00:01:47,513
So again, Router 3 is going to be our
DHCP server so we say ipv6 dhcp pool.

24
00:01:47,514 --> 00:01:51,229
And again, we're just going to
call it 6POOL, no big deal.

25
00:01:51,229 --> 00:02:00,670
And then things you want to put in so
DNS server 2001:db8:100:100::1 domain

26
00:02:00,671 --> 00:02:03,782
name ine.com.

27
00:02:03,783 --> 00:02:05,497
No big deal there.

28
00:02:05,497 --> 00:02:13,041
And the part that becomes important now
is, if we're going to do full-blown DHCP,

29
00:02:13,041 --> 00:02:16,950
then he needs an actual address pool.

30
00:02:16,950 --> 00:02:22,977
So you say, address prefix, and then we
put in the prefix you want to hand out.

31
00:02:22,978 --> 00:02:34,127
So for this network it's
2001 DB8:100:36::/64.

32
00:02:34,127 --> 00:02:39,895
Now, you could hit enter here and get your
default lifetimes, or you can specify.

33
00:02:39,896 --> 00:02:43,788
And we'll do this just because we
mess around with a little bit before.

34
00:02:43,789 --> 00:02:50,984
And we could say that it's valid for 10
minutes, and it's preferred for 5 minutes,

35
00:02:50,985 --> 00:02:54,586
something like that.

36
00:02:54,587 --> 00:02:59,993
And of course any other DHCP options
that you want to put in there.

37
00:02:59,994 --> 00:03:03,588
okay, so any other scope options,
they are the ones that are supported

38
00:03:03,589 --> 00:03:09,729
by this particular code
for the IPv6 DHCP server.

39
00:03:09,730 --> 00:03:12,776
A lot of these you won't have
to worry about a whole lot.

40
00:03:12,777 --> 00:03:17,230
A lot of times it'll just be
vendor-specific for things like your

41
00:03:17,231 --> 00:03:22,918
wireless access points and
phones and things like that.

42
00:03:22,918 --> 00:03:26,821
The fun part here, to be honest,
is more on the client side of what

43
00:03:26,821 --> 00:03:29,336
happens here with the DHCP.

44
00:03:29,337 --> 00:03:32,189
The other thing of course you
could do is, if you wanted to,

45
00:03:32,190 --> 00:03:39,467
you could say IPv6 DHCP database, and
if you let me back out of this so

46
00:03:39,468 --> 00:03:44,038
I can walk you through it here.

47
00:03:44,039 --> 00:03:48,923
So, it's IPv6 DHCP
database and then you

48
00:03:48,935 --> 00:03:54,309
give it a location to
go, so somewhere like,

49
00:03:54,309 --> 00:03:59,686
in this case I'll just write it to
flash and I'll just call it DHCPv6.

50
00:03:59,687 --> 00:04:03,777
That. Something like that.

51
00:04:03,777 --> 00:04:07,977
You can also set the write delay.

52
00:04:07,978 --> 00:04:10,517
So how often should it write to this.

53
00:04:10,517 --> 00:04:13,602
Going to be in seconds and you can
just say like once per minute.

54
00:04:13,603 --> 00:04:14,144
Something like that.

55
00:04:14,145 --> 00:04:16,782
That's fast as you can to it.

56
00:04:16,782 --> 00:04:19,172
If you want to, you
can set the time out.

57
00:04:19,173 --> 00:04:22,526
Hopefully it doesn't time out
writing to its own flash.

58
00:04:22,527 --> 00:04:26,086
Hopefully this would be more of an
option if you're going to some sort of

59
00:04:26,087 --> 00:04:29,899
external server like TFTP
or something like that.

60
00:04:29,899 --> 00:04:31,315
So I'm not even going to
bother with the time out.

61
00:04:31,315 --> 00:04:34,468
We're just going to say that.

62
00:04:34,468 --> 00:04:37,345
Then we just need to fire it up.

63
00:04:37,346 --> 00:04:45,344
So interface FA0/0.36. IPv6.

64
00:04:45,345 --> 00:04:47,845
DHCP server.

65
00:04:47,846 --> 00:04:50,084
Then you of course put
in the pool name.

66
00:04:50,084 --> 00:04:53,820
You could also say that-- you can also
tell it to automatically find a pool.

67
00:04:53,820 --> 00:04:57,330
Then of course it will look at the
addresses in each pool and decide which

68
00:04:57,331 --> 00:04:59,321
one it should pull it from.

69
00:04:59,321 --> 00:05:03,502
Or you can just say--
just specify the actual pool.

70
00:05:03,503 --> 00:05:04,911
I'm a control freak.

71
00:05:04,911 --> 00:05:08,186
I don't like automatic stuff,
so I'm going to tell it.

72
00:05:08,186 --> 00:05:10,372
For now, I'm just
going to hit enter.

73
00:05:10,373 --> 00:05:11,031
You know what?

74
00:05:11,031 --> 00:05:12,270
Actually, I won't.

75
00:05:12,271 --> 00:05:15,831
I'm going to show you this other option
first, because I always like to show you

76
00:05:15,831 --> 00:05:17,579
things before and after.

77
00:05:17,580 --> 00:05:23,921
But in this case, you can
turn it on on one side,

78
00:05:23,922 --> 00:05:29,341
and it doesn't do anything until it's on
the other, which is your rapid-commit.

79
00:05:29,342 --> 00:05:37,402
This allows DHCP to do just a 2-way
handshake instead of a 4-way handshake.

80
00:05:37,403 --> 00:05:40,724
We'll see that here in just a minute.

81
00:05:40,725 --> 00:05:43,308
You can also allow hints
from the clients.

82
00:05:43,309 --> 00:05:48,303
You can have the client send a hint as
far as which pool it should pull from,

83
00:05:48,304 --> 00:05:51,747
and you can also set the preference if
you have multiple DHCP servers on the

84
00:05:51,748 --> 00:05:54,872
wire - on the same segment.

85
00:05:54,873 --> 00:05:57,486
That way, it'll prefer
one over another.

86
00:05:57,486 --> 00:05:59,954
These aren't things we really have to
get into today, but those are some

87
00:05:59,955 --> 00:06:02,208
other options you have.

88
00:06:02,209 --> 00:06:04,776
So we'll turn that on - DHCP server.

89
00:06:04,777 --> 00:06:09,693
Now we're not going to see it fire up here,
because it was running from a previous

90
00:06:09,694 --> 00:06:11,894
lesson we did there.

91
00:06:11,895 --> 00:06:14,375
But now, we go over to Router 6.

92
00:06:14,376 --> 00:06:23,746
And on Router 6, we're going to say,
IPv6 address DHCP, and just hit enter.

93
00:06:23,746 --> 00:06:29,929
This should send a client request, and
right there you have your 4-way handshake.

94
00:06:29,930 --> 00:06:35,023
So you send out a solicit - no big
deal - and again, that group,

95
00:06:35,024 --> 00:06:44,338
by the way - the FF02::1:2 -
is reserved for DHCP servers.

96
00:06:44,338 --> 00:06:46,393
So step one, solicit.

97
00:06:46,394 --> 00:06:49,702
Step two, we get an advertise.

98
00:06:49,703 --> 00:06:52,276
Step three, we say
yes, we like your

99
00:06:52,288 --> 00:06:55,432
address, we'll take it
- that's the request.

100
00:06:55,433 --> 00:06:59,492
And of course, step four, we get the reply,
which is sort of like the confirmation

101
00:06:59,493 --> 00:07:02,108
that okay, you're good.

102
00:07:02,109 --> 00:07:03,386
You have the lease.

103
00:07:03,387 --> 00:07:05,873
It's all yours.

104
00:07:05,873 --> 00:07:11,232
Then we get an actual address,
and we add it to the interface.

105
00:07:11,233 --> 00:07:13,178
Okay, fine.

106
00:07:13,179 --> 00:07:15,989
We set the timer
values, that's fine.

107
00:07:15,990 --> 00:07:20,556
Configure the DNS server, and
configure the domain name.

108
00:07:20,556 --> 00:07:22,201
And that's pretty much it.

109
00:07:22,201 --> 00:07:23,521
That's it.

110
00:07:23,521 --> 00:07:29,520
So that's traditional
DHCP 4-way handshake.

111
00:07:29,521 --> 00:07:32,546
Same basic things
you'll see on Router 3.

112
00:07:32,546 --> 00:07:36,388
Now, before we go too far with
some of the other options,

113
00:07:36,388 --> 00:07:38,772
let me just show you real quick how
to deal with a 2-way handshake.

114
00:07:38,773 --> 00:07:44,854
So I'm going to say shut, and I'm going to
let him actually unconfigure and send his

115
00:07:44,855 --> 00:07:46,538
release message.

116
00:07:46,539 --> 00:07:51,792
So he's going to return that address to
the pool right here, we send the release.

117
00:07:51,792 --> 00:07:53,121
No big deal.

118
00:07:53,122 --> 00:08:00,024
And then what I'm going to say, is on the
IP address DHCP we'll say rapid commit.

119
00:08:00,025 --> 00:08:04,668
Then we'll say no shut.

120
00:08:04,669 --> 00:08:12,379
Bring the interface
up, and already done.

121
00:08:12,380 --> 00:08:18,770
As you can see, this now reduces
it to the solicit and the reply.

122
00:08:18,771 --> 00:08:23,369
That's it. Over.

123
00:08:23,370 --> 00:08:29,876
Basic idea with this one is the DHCP
server is just going to assume that

124
00:08:29,877 --> 00:08:32,309
whatever he offers,
the client took it.

125
00:08:32,309 --> 00:08:35,079
He'll go ahead and write that to
his database already in fact.

126
00:08:35,079 --> 00:08:42,487
If we go over to Router 3 and we
say do show IPv6 DHCP bindings,

127
00:08:42,512 --> 00:08:47,185
we'll find out that he's already
given that address out.

128
00:08:47,186 --> 00:08:56,022
That's how long it's good for yet based
on the current date and time and so on.

129
00:08:56,023 --> 00:09:04,422
Go over to Router 6
and we're good to go.

130
00:09:04,423 --> 00:09:06,257
So we already put the address in.

131
00:09:06,258 --> 00:09:10,062
But now we're going to see a
little bit of a problem here.

132
00:09:10,063 --> 00:09:17,390
I'm going to say, do
ping 2001 DB8:100:36::3.

133
00:09:17,390 --> 00:09:26,675
And just in case you don't
remember, from our diagram.

134
00:09:26,676 --> 00:09:29,707
You always get the diagram
from the downloads of course.

135
00:09:29,707 --> 00:09:31,652
But that's his address right there.

136
00:09:31,653 --> 00:09:40,716
So we are in fact from Router 6, pinging
Router 3 which I just got my address from.

137
00:09:40,717 --> 00:09:47,119
So just to be a little bit ironic here,
he can't ping the DHCP server that

138
00:09:47,119 --> 00:09:49,404
gave him his own address.

139
00:09:49,405 --> 00:09:54,315
Now, what he can ping of course
is the link local address.

140
00:09:54,315 --> 00:10:09,587
So if I were to instead say to ping
fe80::3 %gigabitethernet 0/0.36.

141
00:10:09,587 --> 00:10:12,021
That's fine. Okay.

142
00:10:12,022 --> 00:10:15,083
So the link locals are fine,
but I can't ping the global.

143
00:10:15,084 --> 00:10:20,209
And the interesting part is to
actually look at the message,

144
00:10:20,209 --> 00:10:22,506
No valid route for destination.

145
00:10:22,506 --> 00:10:23,732
Okay, great.

146
00:10:23,732 --> 00:10:25,969
When you get something like that,
one of the things I always do,

147
00:10:25,970 --> 00:10:31,905
and this applies to IPv4 and
IPv6, is to say, do show ip cef,

148
00:10:31,906 --> 00:10:34,384
and then ask for that same prefix.

149
00:10:34,385 --> 00:10:36,381
Basically what you're
saying is, You know what,

150
00:10:36,382 --> 00:10:42,833
show me what the actual FIB says to do.

151
00:10:42,834 --> 00:10:43,606
Okay. No way.

152
00:10:43,606 --> 00:10:48,009
It's not IP cef,
IPv6 cef may help.

153
00:10:48,009 --> 00:10:54,267
Now, what he's telling you here basically
is, Okay, I would follow the default route.

154
00:10:54,268 --> 00:10:59,750
That's what I would follow, but
unfortunately I don't have one.

155
00:10:59,751 --> 00:11:03,286
What's really interesting about this--
the message is already on the screen.

156
00:11:03,287 --> 00:11:04,882
Maybe you've already seen it.

157
00:11:04,882 --> 00:11:08,542
Maybe you already know why because it's
in the debugs right in front of us,

158
00:11:08,543 --> 00:11:11,475
right at the top of the screen here.

159
00:11:11,476 --> 00:11:16,520
Adding address and look
at the mask on that.

160
00:11:16,521 --> 00:11:22,064
Look at the prefix length. /128.

161
00:11:22,065 --> 00:11:27,652
That makes that a host entry, which
means if I'm on Router 6 and I

162
00:11:27,652 --> 00:11:36,259
say do show IPv6 route,
he has the 36 network.

163
00:11:36,259 --> 00:11:41,295
But he has it as his
own address in a /128.

164
00:11:41,295 --> 00:11:44,763
So basically you could say from a
routing perspective of course he

165
00:11:44,764 --> 00:11:48,059
doesn't know how to get to the other
side because theoretically he thinks

166
00:11:48,060 --> 00:11:50,716
he's the only one on that wire.

167
00:11:50,716 --> 00:11:52,850
Now that's of course not the case.

168
00:11:52,850 --> 00:11:56,962
But this is what DHCP for IPv6 does.

169
00:11:56,962 --> 00:12:04,307
You can see he added the /128 and if we
go back to Router 3 and look at what

170
00:12:04,308 --> 00:12:09,446
he was given, never really
says a whole lot, does it?

171
00:12:09,447 --> 00:12:19,187
It looks up the binding, gives him
the address, that's it - that's it.

172
00:12:19,188 --> 00:12:24,682
Never actually tells you here, by the way,
the client is going to install this as

173
00:12:24,683 --> 00:12:29,407
a /128 because that's
really a client thing.

174
00:12:29,408 --> 00:12:34,481
But if we go over to Router 6-- of course,
the important thing here is not to see

175
00:12:34,482 --> 00:12:37,451
the problem and so on, but
to see the workaround.

176
00:12:37,451 --> 00:12:39,644
There's a couple ways you can do this.

177
00:12:39,645 --> 00:12:46,871
Now remember, again, this is a router
so that's part of the issue of course.

178
00:12:46,871 --> 00:12:50,055
If we were to go back--
I just want to show you here real

179
00:12:50,056 --> 00:12:56,365
quick though unlike our slack there's
no choice here to say default,

180
00:12:56,365 --> 00:13:00,483
and it's not just that it's not after
the rapid commit remember before we

181
00:13:00,484 --> 00:13:08,166
said IPv6 address-- and that was a
debug in the middle of all that.

182
00:13:08,166 --> 00:13:10,787
I was trying to show you the
question mark and a debug popped up.

183
00:13:10,788 --> 00:13:11,925
That's it.

184
00:13:11,925 --> 00:13:20,027
Bot just that it's
 not after the rapid commit.

0:12:59.200000 --> 0:13:04.020000
 Remember before we
 said IPV6 address.

0:13:04.020000 --> 0:13:08.620000
 And that was a debug in the middle of
 all that I was trying to show you

0:13:08.620000 --> 0:13:10.700000
 the question mark and
 a debug popped up.

0:13:10.700000 --> 0:13:19.280000
 That's it. But in any case with the IPV6
 address auto there was an option

0:13:19.280000 --> 0:13:23.460000
 to say hey you know what take the
 default route and use that.

0:13:23.460000 --> 0:13:28.160000
 Okay. Problem is there's not one of
 those on DHCP and of course sort of

0:13:28.160000 --> 0:13:31.020000
 the I don't want to say obvious reason
 because maybe you didn't think

0:13:31.020000 --> 0:13:34.040000
 of it but I did sort of
 mention it earlier.

0:13:34.040000 --> 0:13:40.940000
 The reason is you don't get your default
 route or default gateway from

0:13:40.940000 --> 0:13:52.560000
 DHCP. The only way to get it is manually
 configure it or to actually tell

0:13:52.560000 --> 0:13:56.720000
 it to use the address from
 neighbor discovery.

0:13:56.720000 --> 0:14:00.480000
 So basically what I could do here is
 I could still get my address from

0:14:00.480000 --> 0:14:07.880000
 DHCP. But I could say IPV6 neighbor
 discovery auto config.

0:14:07.880000 --> 0:14:12.260000
 Now notice that's not address that's
 IPV6 neighbor discovery auto config

0:14:12.260000 --> 0:14:17.220000
 and tell him to actually
 get the prefix.

0:14:17.220000 --> 0:14:29.160000
 If I do that and look at the show IPV6
 route now he gets that NDP route

0:14:29.160000 --> 0:14:32.980000
 back that we talked about
 a little bit earlier.

0:14:32.980000 --> 0:14:36.120000
 We saw that in a previous lesson when
 we were actually going over neighbor

0:14:36.120000 --> 0:14:40.340000
 discovery and such.

0:14:40.340000 --> 0:14:43.920000
 So that's the route that he's going
 to use to get to the other side.

0:14:43.920000 --> 0:14:49.340000
 If we go back now to our CEPH requests
 notice that he now shows it is

0:14:49.340000 --> 0:14:54.000000
 being attached which also means that
 I could go back to my ping that we

0:14:54.000000 --> 0:14:56.720000
 tried to do earlier that failed.

0:14:56.720000 --> 0:15:00.280000
 Not that one that one and
 it should now work.

0:15:00.280000 --> 0:15:03.460000
 Now we have a route to get to the other
 side but you have to actually

0:15:03.460000 --> 0:15:06.960000
 tell him okay and let me
 just summarize here.

0:15:06.960000 --> 0:15:11.740000
 Do show run interface
 gigabit 00 got 36.

0:15:11.740000 --> 0:15:18.560000
 You have to tell him that he's getting
 his address from DHCP but to go

0:15:18.560000 --> 0:15:22.860000
 ahead and install the prefix
 from neighbor discovery.

0:15:22.860000 --> 0:15:28.480000
 So to have the router sort of act like
 a full blown client for DHCP so

0:15:28.480000 --> 0:15:34.320000
 to speak you would have to
 combine those two things.

0:15:34.320000 --> 0:15:44.780000
 Okay and the other thing to note here
 is that if you switch over not switch

0:15:44.780000 --> 0:15:47.040000
 over sorry we're already
 on router six.

0:15:47.040000 --> 0:15:53.340000
 Do show IPV6 interface brief is even
 though I have the link local address

0:15:53.340000 --> 0:15:56.240000
 hard coded on this one.

0:15:56.240000 --> 0:16:00.640000
 Notice that does not affect the
 address he gets from DHCP.

0:16:00.640000 --> 0:16:07.420000
 So this does not affect DHCP the same
 as it does you know stateless auto

0:16:07.420000 --> 0:16:12.660000
 configuration or just saying you know
 IPV6 address putting in a prefix

0:16:12.660000 --> 0:16:15.360000
 and saying EUY 64.

0:16:15.360000 --> 0:16:18.520000
 And that's because although this is
 a way of automatically getting your

0:16:18.520000 --> 0:16:24.120000
 address it's not a way of automatically
 assigning yourself an address.

0:16:24.120000 --> 0:16:27.580000
 So that's the real difference here
 you're actually getting an address

0:16:27.580000 --> 0:16:34.980000
 from DHCP. If I let the link local
 address override that host portion.

0:16:34.980000 --> 0:16:40.860000
 Well I mean just to be blunt you might
 as well go back to doing slack

0:16:40.860000 --> 0:16:45.800000
 again then because frankly you haven't
 accomplished anything you came

0:16:45.800000 --> 0:16:50.680000
 here to do. The idea behind this whole
 thing honestly is that you can

0:16:50.680000 --> 0:17:01.160000
 come back over here and we can say for
 example do more DHCP V6 dot that.

0:17:01.160000 --> 0:17:05.440000
 Oops I know that's not found
 because that's not right.

0:17:05.440000 --> 0:17:09.740000
 Okay and if you take a look at this
 this is just a text output of the

0:17:09.740000 --> 0:17:11.400000
 DHCP binding table.

0:17:11.400000 --> 0:17:13.920000
 I'm just showing you
 that you can see it.

0:17:13.920000 --> 0:17:19.720000
 You can of course also see it obviously
 by doing the bindings which I

0:17:19.720000 --> 0:17:22.080000
 looked at a minute ago.

0:17:22.080000 --> 0:17:26.640000
 But you know he's got a record he's got
 a database that that exact address

0:17:26.640000 --> 0:17:29.220000
 has been given out to that client.


0:17:29.220000 --> 0:17:34.340000
 And you know this is what makes this
 state full versus stateless.

0:17:34.340000 --> 0:17:39.040000
 We looked at stateless DHCP in the
 previous lesson and if that's what

0:17:39.040000 --> 0:17:42.820000
 we wanted then we should
 have stayed there.

0:17:42.820000 --> 0:17:47.140000
 The whole point of this is we want
 to actually get the client portion

0:17:47.140000 --> 0:17:53.380000
 of the address the host portion
 if you will from DHCP.

0:17:53.380000 --> 0:17:57.420000
 So this is of course going to be that
 exception to the you know oh the

0:17:57.420000 --> 0:17:59.940000
 link local address overrides
 dynamically learned.

0:17:59.940000 --> 0:18:03.840000
 This is technically dynamically
 learned but it's been assigned.

0:18:03.840000 --> 0:18:08.960000
 It's not just being made up which is
 what we get with the other choices.

0:18:08.960000 --> 0:18:13.340000
 Okay so to switch back over here we did
 take a look at already configuring

0:18:13.340000 --> 0:18:20.660000
 the IPv6 interface and again that's
 just saying IPv6 address DHCP.

0:18:20.660000 --> 0:18:24.440000
 Okay so that was just and of course
 not to mention the of course signing

0:18:24.440000 --> 0:18:26.340000
 a signing on the server side.

0:18:26.340000 --> 0:18:32.540000
 Assigning the server to the interface
 and then the DHCP client.

0:18:32.540000 --> 0:18:35.800000
 Okay controlling the host portion
 with the link local address.

0:18:35.800000 --> 0:18:39.360000
 Well the answer on this
 one is you can't.

0:18:39.360000 --> 0:18:43.800000
 Okay so put that on there just so I
 remember to show you but there it

0:18:43.800000 --> 0:18:45.260000
 is you can't control it.

0:18:45.260000 --> 0:18:49.720000
 And just as a final here because I will
 clean this up again for the next

0:18:49.720000 --> 0:18:56.040000
 lesson. Just to show you one last time
 so do show run interface f a 00

0:18:56.040000 --> 0:19:09.660000
 dot 36. Okay so one more time you've got
 the pool assigned to the interface

0:19:09.660000 --> 0:19:16.240000
 that's really all you need except
 an actual active address as well.

0:19:16.240000 --> 0:19:20.080000
 Okay and also on router six.

0:19:20.080000 --> 0:19:29.840000
 Space got in the wrong place.

0:19:29.840000 --> 0:19:40.580000
 So again he's just getting his address
 from DHCP and if you want the route

0:19:40.580000 --> 0:19:43.540000
 the auto config prefix.

0:19:43.540000 --> 0:19:50.440000
 Now one other thing to note since this
 is a router and we'll get to this

0:19:50.440000 --> 0:19:54.260000
 possibly a little bit later but it
 doesn't really matter a whole lot.

0:19:54.260000 --> 0:20:02.920000
 I just want to point out that if you
 were also going to run OSPF, EIGRP,

0:20:02.920000 --> 0:20:07.620000
 RIP, BGP not so much but if you were
 going to run one of your routing

0:20:07.620000 --> 0:20:13.240000
 protocols over all of this then you
 don't need that auto config prefix.

0:20:13.240000 --> 0:20:19.820000
 Because even though I have a slash
 128 which again is right here even

0:20:19.820000 --> 0:20:28.380000
 though that's what I have I would learn
 the slash 64 from OSPF, EIGRP,

0:20:28.380000 --> 0:20:30.740000
 RIP, whatever's on the other side.


0:20:30.740000 --> 0:20:33.980000
 I would learn that anyway.

0:20:33.980000 --> 0:20:38.640000
 So another way to get around that IPv6
 neighbor discovery auto config

0:20:38.640000 --> 0:20:45.080000
 prefix would be to actually run a well
 I can't say any but most of your

0:20:45.080000 --> 0:20:49.380000
 routing protocols over this would
 fix this problem as well.

0:20:49.380000 --> 0:20:54.320000
 You could always of course do a static
 default route as well which just

0:20:54.320000 --> 0:20:56.480000
 to show you be very
 very simple right.

0:20:56.480000 --> 0:20:59.100000
 I would just say no.

0:20:59.100000 --> 0:21:03.060000
 Take out the prefix.

0:21:03.060000 --> 0:21:12.160000
 This then should not be pingable
 to the other side again.

0:21:12.160000 --> 0:21:24.300000
 No valid route. And then just say IPv6
 route colon colon slash zero out.

0:21:24.300000 --> 0:21:29.640000
 It's really the best to put in the next
 top so F E eight zero colon colon

0:21:29.640000 --> 0:21:34.500000
 three and then it's going to want the
 egress interface admin distance

0:21:34.500000 --> 0:21:39.200000
 and so on. So we'll say.

0:21:39.200000 --> 0:21:42.960000
 Yeah. I know that.

0:21:42.960000 --> 0:21:47.120000
 So why is it not so it's going to make
 me actually do it this way fine

0:21:47.120000 --> 0:21:54.540000
 so percent. Some of the older code asked
 you for the interface right there

0:21:54.540000 --> 0:21:57.180000
 and this code is not.

0:21:57.180000 --> 0:22:04.180000
 You have it ethernet zero
 zero drop thirty six.

0:22:04.180000 --> 0:22:09.260000
 I thought I did that.

0:22:09.260000 --> 0:22:13.600000
 As you can see when you start messing
 with link locals like that it becomes

0:22:13.600000 --> 0:22:14.900000
 a little bit entertaining.

0:22:14.900000 --> 0:22:16.400000
 It wants the interface first.

0:22:16.400000 --> 0:22:18.180000
 There we go. All right fine.

0:22:18.180000 --> 0:22:23.480000
 So gigabit zero zero dot thirty
 six to the next top.

0:22:23.480000 --> 0:22:28.060000
 F E eight zero colon
 colon three there.

0:22:28.060000 --> 0:22:30.520000
 All of that is put
 in a static route.

0:22:30.520000 --> 0:22:35.140000
 You can see how often I
 use static routes right.

0:22:35.140000 --> 0:22:39.400000
 Since that's one of the big no nose
 on your CCIE labs and I teach that

0:22:39.400000 --> 0:22:44.060000
 a lot then. You actually start getting
 a little bit rusty on like the

0:22:44.060000 --> 0:22:49.560000
 simple stuff. And I want
 to do the painting.

0:22:49.560000 --> 0:22:51.740000
 I was probably way far back.

0:22:51.740000 --> 0:22:56.140000
 There we go. See but now we have
 a static routes and now it works.

0:22:56.140000 --> 0:23:00.520000
 So do show IP V six out.

0:23:00.520000 --> 0:23:05.420000
 And now we have a static default
 just because we put it in.

0:23:05.420000 --> 0:23:10.880000
 So easy enough. So that's DHCP if you
 actually want to use the router

0:23:10.880000 --> 0:23:16.820000
 as a standard DHCP server and
 a standard DHCP client.