50-Advanced Routing: BGP Community properties: No-export

First, the experimental topology:

Second, the experimental requirements:
1, increase R5:as 5, and R2 through the Direct Connect route to establish BGP neighbor relationship;
2, R2 deployed in BGP under Send-conmmunity to R5;
3, R4 deployment ACL crawl 4.4.4.4 traffic, Route-map named Shuchu, call ACL, set community no-export, and invoke Route-map Shuchu out in the BGP process;
4. See if R1, R2, R3 contain 4.4.4.4 routes that carry No-export, and R5 do not learn the route entry for 4.4.4.4?
Third, command deployment:
R4#show IP access-lists
Standard IP access list 10
Permit 4.4.4.0, wildcard bits 0.0.0.255 (1 match)

R4#show Run | S Route-map
Neighbor 14.1.1.1 Route-map Shuchu out
Route-map Shuchu Permit 20
Match IP Address 10
Set Community No-export
Route-map Shuchu Permit 1000

Four, verify:
R5#show IP BGP//NULL

R2#show IP BGP 4.4.4.4
BGP routing table entry for 4.4.4.0/24, version 2
Paths: (1 available, best #1, table default-ip-routing-table, not advertised to EBGP peer)
flag:0x820
Not advertised to any peer
(65001) 4
3.3.3.3 (Metric 156160) from 3.3.3.3 (3.3.3.3)
Origin IGP, Metric 0, Localpref, valid, confed-external, best
Community:no-export
Similarly: R1, R3

50-Advanced Routing: BGP Community properties: No-export