WEBVTT

1
00:00.000 --> 00:02.180
So now that we've had a few moments to consider

2
00:02.180 --> 00:04.460
some of these questions, let's compare notes.

3
00:04.460 --> 00:07.820
So first of all, if we want to allow clients here

4
00:07.820 --> 00:10.580
on the 1010-0 network and the 1020-0 network

5
00:10.580 --> 00:12.980
to go out to the internet, we need to swap out

6
00:12.980 --> 00:16.020
those source addresses first with a routable address

7
00:16.020 --> 00:18.300
on the internet before we can let those packets fly

8
00:18.300 --> 00:19.820
because if we don't translate them,

9
00:19.820 --> 00:21.740
they're not gonna make it all the way through the internet.

10
00:21.740 --> 00:23.940
So as far as which type of net should be used,

11
00:23.940 --> 00:26.980
it should be source net or S-net for short.

12
00:26.980 --> 00:28.340
And then the next question is,

13
00:28.340 --> 00:31.180
which gateway would you apply the net rules to?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:28.340 --> 00:31.180
which gateway would you apply the net rules to?

14
00:31.180 --> 00:34.540
And so we could do it here and here.

15
00:34.540 --> 00:35.740
Now currently in our topology,

16
00:35.740 --> 00:37.140
these are just distributed routers.

17
00:37.140 --> 00:41.100
So if we wanted to implement net services here,

18
00:41.100 --> 00:43.940
that would also invoke injecting a services router here

19
00:43.940 --> 00:46.020
on gateway A and on gateway B.

20
00:46.020 --> 00:49.020
Also we'd have to have a rule here for these VMs

21
00:49.020 --> 00:50.660
and a rule here for these VMs.

22
00:50.660 --> 00:52.460
So to make it simpler and also because we already have

23
00:52.460 --> 00:55.380
a services router function here at the gateway zero,

24
00:55.380 --> 00:57.060
it's very likely we'd want to implement

25
00:57.060 --> 00:58.900
our net services right here.

26
00:58.900 --> 01:01.900
And so currently we have an active standby situation
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
00:58.900 --> 01:01.900
And so currently we have an active standby situation

27
01:01.900 --> 01:04.100
for tier zero with edge one and edge two

28
01:04.100 --> 01:05.300
providing that support.

29
01:05.300 --> 01:07.820
So we could go ahead and just simply add a net rule here

30
01:07.820 --> 01:11.180
that says if traffic is source from 10.10.anything

31
01:11.180 --> 01:13.820
or coming from 10.20.anything,

32
01:13.820 --> 01:15.980
go ahead and do that translation.

33
01:15.980 --> 01:18.020
And as far as what we translated into,

34
01:18.020 --> 01:19.580
that leads us to the next question.

35
01:19.580 --> 01:21.580
And that is, will you use one-to-one

36
01:21.580 --> 01:23.660
or many-to-one address translation?

37
01:23.660 --> 01:27.420
So if we have four or 500 clients or devices

38
01:27.420 --> 01:29.460
that need access to the external network,

39
01:29.460 --> 01:31.820
it's very unlikely that we're gonna have four
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:29.460 --> 01:31.820
it's very unlikely that we're gonna have four

40
01:31.820 --> 01:34.380
or 500 uniquely routable addresses

41
01:34.380 --> 01:36.220
that we've been given from our service provider

42
01:36.220 --> 01:39.460
or more correctly we've purchased from our service provider.

43
01:39.460 --> 01:41.900
So oftentimes we'll do a lot of overloading

44
01:41.900 --> 01:44.500
on a single-address leveraging port address translation

45
01:44.500 --> 01:46.220
with a many-to-one scenario.

46
01:46.220 --> 01:48.340
So let's say for example, we want to take

47
01:48.340 --> 01:50.580
anybody who's coming from these source addresses

48
01:50.580 --> 01:53.780
and we will map them to 23.1.2.

49
01:53.780 --> 01:55.220
Let's go ahead and use 99.

50
01:55.220 --> 01:56.580
So that's a nine-feet address that's spreadable

51
01:56.580 --> 01:58.340
on the internet and let's also imagine

52
01:58.340 --> 01:59.820
from a service provider perspective,

53
01:59.820 --> 02:02.180
they have assigned us that IP address that we can use.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
01:59.820 --> 02:02.180
they have assigned us that IP address that we can use.

54
02:02.180 --> 02:05.220
Another option would be to overload on an existing address

55
02:05.220 --> 02:06.540
that would be another option as well.

56
02:06.540 --> 02:09.140
So far plan is to use a single IP address,

57
02:09.140 --> 02:10.900
then we'd be implementing effectively PAT

58
02:10.900 --> 02:12.980
with many-to-one address translation

59
02:12.980 --> 02:16.500
with many VMs down here as they go out to the internet

60
02:16.500 --> 02:18.060
being mapped to a single IP address.

61
02:18.060 --> 02:20.700
And since we have the topology already in place,

62
02:20.700 --> 02:23.460
let's go ahead and walk through the implementation

63
02:23.460 --> 02:24.700
of source NAT,

64
02:24.700 --> 02:28.500
implement it here with a net rule here on the tier zero gateway

65
02:28.500 --> 02:30.620
using a many-to-one mapping.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
02:28.500 --> 02:30.620
using a many-to-one mapping.

66
02:30.620 --> 02:33.460
Mapping all the clients on 10, 10, 20

67
02:33.460 --> 02:36.060
will map them all to the single IP address right here

68
02:36.060 --> 02:38.500
before forwarding it out to our external router.

69
02:38.500 --> 02:41.060
So with that in mind, let's configure NAT.

70
02:41.060 --> 02:44.420
So here in the NSX manager, we go to the networking tab

71
02:44.420 --> 02:47.220
and the left side down under network services,

72
02:47.220 --> 02:48.420
we click on NAT.

73
02:48.420 --> 02:50.180
So currently from our demos earlier,

74
02:50.180 --> 02:53.260
we have a source NAT rule and a destination NAT rule,

75
02:53.260 --> 02:55.820
and I am going to delete both of those

76
02:55.820 --> 02:58.900
and we'll replace it with the one based on the validation

77
02:58.900 --> 03:00.420
challenge we just took a look at.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
02:58.900 --> 03:00.420
challenge we just took a look at.

78
03:00.420 --> 03:04.260
And click on refresh, we now have absolutely zero NAT rules.

79
03:04.260 --> 03:05.980
So to start off, for the NAT rules,

80
03:05.980 --> 03:08.740
we want to apply the NAT rules to our tier zero gateway zero.

81
03:08.740 --> 03:10.740
So we'll select that tier zero gateway

82
03:10.740 --> 03:12.580
and then click here on add NAT rule.

83
03:12.580 --> 03:14.980
So we'll call this S NAT dash fee for validation.

84
03:14.980 --> 03:16.260
That's the section we're in.

85
03:16.260 --> 03:19.340
And the type of NAT we want to do is source NAT,

86
03:19.340 --> 03:22.060
swapping out the source address on that initial flow of traffic.

87
03:22.060 --> 03:23.940
And then here for the source address,

88
03:23.940 --> 03:25.660
we want it to be in the 10.

89
03:25.660 --> 03:26.500
In fact, we can do this.

90
03:26.500 --> 03:28.860
We say 10 anything with an 8-bit mask.

91
03:28.860 --> 03:30.860
And that way any source IP addresses
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
03:28.860 --> 03:30.860
And that way any source IP addresses

92
03:30.860 --> 03:33.860
that start with 10, 10, 10, 20, or 10, 30, et cetera,

93
03:33.860 --> 03:35.900
as long as they start with the first octet of 10,

94
03:35.900 --> 03:37.300
they're going to match this rule.

95
03:37.300 --> 03:38.980
And then for the destination, we'll leave that empty.

96
03:38.980 --> 03:41.300
So they could be going to a Google DNS server

97
03:41.300 --> 03:43.260
or any resource out on the internet.

98
03:43.260 --> 03:44.100
It'd be great.

99
03:44.100 --> 03:46.140
We're not going to constrain that for the NAT rule.

100
03:46.140 --> 03:48.020
And then for the translated address,

101
03:48.020 --> 03:52.780
what we want to use based on our plan is 23.1.2.99.

102
03:52.780 --> 03:54.060
And then if we wanted to lock this down

103
03:54.060 --> 03:56.860
to specific edge ports, we can go ahead and click on set

104
03:56.860 --> 03:58.820
and simply select them right here.

105
03:58.820 --> 04:01.300
Or we could not select those and leave that empty.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
03:58.820 --> 04:01.300
Or we could not select those and leave that empty.

106
04:01.300 --> 04:02.780
It's not required to put it in.

107
04:02.780 --> 04:05.580
So they would still apply to our active edge nodes

108
04:05.580 --> 04:07.900
and we're not constraining it with this set option right here.

109
04:07.900 --> 04:10.100
So we'll scroll down, click on save,

110
04:10.100 --> 04:12.020
and let's check our work.

111
04:12.020 --> 04:14.340
And this source NAT rule says if traffic is sourced

112
04:14.340 --> 04:18.260
from 10 anything, including devices on the 1010 or 1020,

113
04:18.260 --> 04:21.500
et cetera, as they go through this gateway, Gateway Zero,

114
04:21.500 --> 04:23.300
based on the Gateway Zero's routing,

115
04:23.300 --> 04:25.180
it's going to go ahead and swap out the source address

116
04:25.180 --> 04:27.260
from the 10, whatever address it was,

117
04:27.260 --> 04:29.980
to the new source address of 23.1.2.99.

118
04:29.980 --> 04:32.220
And that'll be true for a bunch of VMs
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
04:29.980 --> 04:32.220
And that'll be true for a bunch of VMs

119
04:32.220 --> 04:33.700
that are going through this gateway.

120
04:33.700 --> 04:36.460
So that's the example of doing many to one with source NAT.

121
04:36.460 --> 04:38.260
And over here, it understands it says,

122
04:38.260 --> 04:40.420
uninitialized, we'll click on the refresh,

123
04:40.420 --> 04:41.260
and that looks good.

124
04:41.260 --> 04:44.300
And if we click here, that's going to show us these statistics.

125
04:44.300 --> 04:45.460
So currently there's no traffic

126
04:45.460 --> 04:46.860
trying to go through the gateway

127
04:46.860 --> 04:48.780
and there's no translations as a result.

128
04:48.780 --> 04:51.260
So we'll click on close, we'll collapse that,

129
04:51.260 --> 04:53.580
and let me expand the left-hand column, fantastic.

130
04:53.580 --> 04:55.460
So let's go ahead and test this out.

131
04:55.460 --> 04:58.620
So for testing, let's go ahead and open up VM1

132
04:58.620 --> 04:59.780
and also VM2.

133
04:59.780 --> 05:01.940
It'll give us an example of two different subnets.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
04:59.780 --> 05:01.940
It'll give us an example of two different subnets.

134
05:01.940 --> 05:04.020
And let's go ahead and try to send traffic out

135
05:04.020 --> 05:05.300
to the internet.

136
05:05.300 --> 05:06.340
And if that's successful,

137
05:06.340 --> 05:07.980
all the way out to the public internet,

138
05:07.980 --> 05:10.260
that implies that we have a address translation

139
05:10.260 --> 05:11.820
that's currently functioning here

140
05:11.820 --> 05:14.100
at our tier zero gateway based on the rule

141
05:14.100 --> 05:15.260
that we just created.

142
05:15.260 --> 05:18.500
So let's go to VM1 and VM2 and let's test it out.

143
05:18.500 --> 05:22.580
So here is VM1, I'll bring that over here on the left.

144
05:22.580 --> 05:25.860
And let's do a quick IAF config for ethernet zero,

145
05:25.860 --> 05:27.460
just verify it's IP address.

146
05:27.460 --> 05:31.260
So that's here at 10100.10, fantastic.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

146
05:27.460 --> 05:31.260
So that's here at 10100.10, fantastic.

147
05:31.260 --> 05:34.940
Let's also bring in VM2, which should be at 10200.20.

148
05:34.940 --> 05:38.100
So here is VM20 right here.

149
05:38.100 --> 05:40.220
I'll put it over here so we can still see the topology.

150
05:40.220 --> 05:41.780
And a confirm its IP address,

151
05:41.780 --> 05:45.020
we'll do an IAF config or ethernet zero.

152
05:45.020 --> 05:47.980
And sure enough, it has the IP address as expected right here,

153
05:47.980 --> 05:49.420
10200.20.

154
05:49.420 --> 05:51.580
So this is VM2.

155
05:51.580 --> 05:54.260
And over here, this is VM1.

156
05:54.260 --> 05:55.900
And as a test, let's send traffic out

157
05:55.900 --> 05:59.340
to a Google DNS server at 8.8.8.8.

158
05:59.340 --> 06:03.500
So let's start over on VM1 with a ping to 8.8.8 to 8.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

158
05:59.340 --> 06:03.500
So let's start over on VM1 with a ping to 8.8.8 to 8.

159
06:03.500 --> 06:05.300
And that looks like it's working.

160
06:05.300 --> 06:06.100
Great, great, great.

161
06:06.100 --> 06:08.340
We'll do the same thing over here for VM2,

162
06:08.340 --> 06:11.300
we'll do a ping to 8.8.8 to 8.

163
06:11.300 --> 06:12.860
And well, those are both running.

164
06:12.860 --> 06:14.900
Let's go to our tier zero gateway

165
06:14.900 --> 06:17.420
and just verify that we have our stats

166
06:17.420 --> 06:19.700
that are being incremented regarding our NAT rule

167
06:19.700 --> 06:21.140
that we created a moment ago.

168
06:21.140 --> 06:22.820
So here in the NSX manager,

169
06:22.820 --> 06:24.260
I'll go ahead and collapse the left-hand side.

170
06:24.260 --> 06:25.900
So in our networking and NAT,

171
06:25.900 --> 06:28.420
we'll click right here on the icon for stats.

172
06:28.420 --> 06:30.700
And sure enough, we have packets that are going through.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

172
06:28.420 --> 06:30.700
And sure enough, we have packets that are going through.

173
06:30.700 --> 06:32.180
And because those pings are still going,

174
06:32.180 --> 06:33.580
if you click on refresh,

175
06:33.580 --> 06:35.420
the packet count and the data count

176
06:35.420 --> 06:38.140
should increase every time we do a refresh.

177
06:38.140 --> 06:39.340
And that looks great.

178
06:39.340 --> 06:41.300
The other interesting thing I'd like to show you

179
06:41.300 --> 06:43.460
is based on the NAT rule that we have set up,

180
06:43.460 --> 06:45.540
our services router and its routing table

181
06:45.540 --> 06:47.180
is gonna be slightly different

182
06:47.180 --> 06:48.460
because it now has to accommodate

183
06:48.460 --> 06:51.020
for that address 23.1.2.99,

184
06:51.020 --> 06:53.540
which is using as part of network address translation.

185
06:53.540 --> 06:55.100
So if we click on close here

186
06:55.100 --> 06:57.540
and let's go to the CLI for edge one,

187
06:57.540 --> 06:59.460
which is currently, let's verify that real quick.

188
06:59.460 --> 07:00.820
It's currently the active node,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

188
06:59.460 --> 07:00.820
It's currently the active node,

189
07:00.820 --> 07:02.580
it's doing actually the data plane work

190
07:02.580 --> 07:04.700
on behalf of the tier zero gateway.

191
07:04.700 --> 07:07.540
So here we're connecting to the management IP address

192
07:07.540 --> 07:10.260
on edge one, and then we'll do get gateways.

193
07:10.260 --> 07:11.100
And then specifically,

194
07:11.100 --> 07:13.220
I wanna take a look and go inside the VRF

195
07:13.220 --> 07:15.060
for this services router right here,

196
07:15.060 --> 07:16.660
which is VRF number six,

197
07:16.660 --> 07:18.740
so we'll type in VRF six.

198
07:18.740 --> 07:20.820
And here we can do things like get route

199
07:20.820 --> 07:22.340
to look at the routing table

200
07:22.340 --> 07:23.980
and where those routes came from.

201
07:23.980 --> 07:25.620
We can also do a get forwarding,

202
07:25.620 --> 07:30.580
which is another way of looking at routing information.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

202
07:25.620 --> 07:30.580
which is another way of looking at routing information.

203
07:30.580 --> 07:33.140
And then here in VRF number six

204
07:33.140 --> 07:34.460
for our services router,

205
07:34.460 --> 07:36.060
if we should get interfaces,

206
07:36.060 --> 07:38.460
I'll use a pipe symbol and I'll go ahead and type in more.

207
07:38.460 --> 07:40.180
That way we can do one page at a time

208
07:40.180 --> 07:41.500
and I'll press enter a few times,

209
07:41.500 --> 07:42.860
go down a little bit further,

210
07:42.860 --> 07:44.140
check out this interface right here.

211
07:44.140 --> 07:46.060
It's a loopback interface that it created

212
07:46.060 --> 07:48.780
for the purposes of network address translation.

213
07:48.780 --> 07:52.820
So 127.001 is the default IPV4 loopback address.

214
07:52.820 --> 07:53.780
And in addition to that,

215
07:53.780 --> 07:56.540
it has this IP address also set up as a loopback,

216
07:56.540 --> 07:58.260
23.1, 29.99.

217
07:58.260 --> 07:59.940
So it's leveraging this loopback address

218
07:59.940 --> 08:03.420
as part of the network address translation that we've set up.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

218
07:59.940 --> 08:03.420
as part of the network address translation that we've set up.

219
08:03.420 --> 08:05.180
And another cool thing is that if we went back

220
08:05.180 --> 08:07.380
to this NAT rule that we had and we edited it

221
08:07.380 --> 08:08.220
and we said, you know what,

222
08:08.220 --> 08:11.620
instead of just being the 23.1.2.99,

223
08:11.620 --> 08:13.220
let's go ahead and modify that.

224
08:13.220 --> 08:18.220
And let's make it 23.1.2.99 through 23.1.2.

225
08:18.220 --> 08:19.860
Let's say 150.

226
08:19.860 --> 08:21.820
So now it's gonna be a whole range of IP addresses

227
08:21.820 --> 08:23.700
that can use as part of the source NAT

228
08:23.700 --> 08:26.220
and we'll go ahead and scroll down, click on save.

229
08:26.220 --> 08:28.460
So now that we've updated that and give it a bigger range,

230
08:28.460 --> 08:30.340
check out what it did behind the scenes
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

230
08:28.460 --> 08:30.340
check out what it did behind the scenes

231
08:30.340 --> 08:31.420
regarding its loopbacks.

232
08:31.420 --> 08:34.860
So a moment ago, we had this one loopback with this IP address.

233
08:34.860 --> 08:38.060
Now if we do the get interfaces for this router

234
08:38.060 --> 08:39.580
and let's scroll up a little bit,

235
08:39.580 --> 08:40.940
check out our loopback interface.

236
08:40.940 --> 08:42.860
It now has not only just one IP address,

237
08:42.860 --> 08:44.980
but it has all the IP addresses

238
08:44.980 --> 08:46.220
that we specified in that range.

239
08:46.220 --> 08:47.660
So if we scroll to the right a little bit,

240
08:47.660 --> 08:50.660
it just goes on and on and on

241
08:50.660 --> 08:52.660
because it has all those IP addresses

242
08:52.660 --> 08:54.140
that it's responsible for

243
08:54.140 --> 08:56.700
as part of the network address translation process.

244
08:56.700 --> 08:58.340
And if we scroll up a little bit,

245
08:58.340 --> 09:01.020
it also is showing us regarding proxy ARP.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

245
08:58.340 --> 09:01.020
it also is showing us regarding proxy ARP.

246
09:01.020 --> 09:03.740
So effectively, if someone does an ARP request

247
09:03.740 --> 09:05.820
for any of these IP addresses

248
09:05.820 --> 09:07.820
because we're using those or could be using those

249
09:07.820 --> 09:09.900
as part of our network address translation,

250
09:09.900 --> 09:12.020
that trains this gateway to respond back

251
09:12.020 --> 09:13.820
when somebody's looking for the layer two address

252
09:13.820 --> 09:15.860
associated with these layer three addresses.

253
09:15.860 --> 09:17.940
And again, these are all the layer three addresses

254
09:17.940 --> 09:19.580
that we're using or can use

255
09:19.580 --> 09:21.420
as part of our network address translation.

256
09:21.420 --> 09:23.620
So I thought it'd be useful in seeing behind the scenes

257
09:23.620 --> 09:26.060
what it's doing to support that range of addresses,

258
09:26.060 --> 09:28.700
including associating all those with its loopback

259
09:28.700 --> 09:31.820
and then also being prepared to respond to ARP requests
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

259
09:28.700 --> 09:31.820
and then also being prepared to respond to ARP requests

260
09:31.820 --> 09:33.540
for any of those IP addresses

261
09:33.540 --> 09:34.980
that it's using or could be using

262
09:34.980 --> 09:36.700
for network address translation.

263
09:36.700 --> 09:39.740
Also here in our VRF for the services router,

264
09:39.740 --> 09:41.940
if we did a get route, check this out.

265
09:41.940 --> 09:43.820
Not only did they have its normal routes,

266
09:43.820 --> 09:46.100
which include our static default route here

267
09:46.100 --> 09:49.420
and the routes we're getting from our tier one gateways,

268
09:49.420 --> 09:51.580
but we also have these routes little N here.

269
09:51.580 --> 09:53.180
And the decode for that is right here.

270
09:53.180 --> 09:56.460
That's a tier zero NAT on this tier zero router.

271
09:56.460 --> 09:58.020
And we press enter a few times,

272
09:58.020 --> 10:00.220
those are gonna continue for the entire range of addresses
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

272
09:58.020 --> 10:00.220
those are gonna continue for the entire range of addresses

273
10:00.220 --> 10:02.420
that we're using for network address translation.

274
10:02.420 --> 10:05.140
Or if we did a get forwarding and press enter,

275
10:05.140 --> 10:07.500
it also is gonna have all of those routes

276
10:07.500 --> 10:09.220
identified right here as well.

277
10:09.220 --> 10:11.300
Because this gateway is now responsible

278
10:11.300 --> 10:14.980
for responding to and acting on behalf of those IP addresses

279
10:14.980 --> 10:16.020
in the event they're used

280
10:16.020 --> 10:17.820
as part of our network address translation.

281
10:17.820 --> 10:19.620
So regarding this validation section,

282
10:19.620 --> 10:21.940
we've not only discussed some of our options here

283
10:21.940 --> 10:23.780
regarding NAT for customer traffic,

284
10:23.780 --> 10:25.540
but we've also implemented it

285
10:25.540 --> 10:27.180
and verified that it's working.

286
10:27.180 --> 10:28.340
So thanks for joining me.

287
10:28.340 --> 10:29.900
In this set of videos and in the skill,

288
10:29.900 --> 10:32.620
we're getting network address translation with NSX.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

288
10:29.900 --> 10:32.620
we're getting network address translation with NSX.

289
10:32.620 --> 10:35.820
And I'll see you my friend in another skill very, very soon.

290
10:35.820 --> 10:38.100
Until then, I hope this has been informative

291
10:38.100 --> 10:40.700
and I'd like to thank you for viewing.