@@ -17,7 +17,7 @@ import (
1717
1818var (
1919 vnetFlag = & cli.StringFlag {
20- Name : "virtual-network " ,
20+ Name : "vnet " ,
2121 Aliases : []string {"vn" },
2222 Usage : "The ID or name of the virtual network to which the route is associated to." ,
2323 }
@@ -35,7 +35,7 @@ determine who can reach certain routes.
3535By default IP routes all exist within a single virtual network. If you use the same IP
3636space(s) in different physical private networks, all meant to be reachable via IP routes,
3737then you have to manage the ambiguous IP routes by associating them to virtual networks.
38- See "cloudflared tunnel network --help" for more information.` ,
38+ See "cloudflared tunnel vnet --help" for more information.` ,
3939 Subcommands : []* cli.Command {
4040 {
4141 Name : "add" ,
@@ -50,9 +50,9 @@ the specified Tunnel, and reach an IP in the given CIDR, as long as that IP is
5050reachable from cloudflared.
5151If the CIDR exists in more than one private network, to be connected with Cloudflare
5252Tunnels, then you have to manage those IP routes with virtual networks (see
53- "cloudflared tunnel network --help)". In those cases, you then have to tell
53+ "cloudflared tunnel vnet --help)". In those cases, you then have to tell
5454which virtual network's routing table you want to add the route to with:
55- "cloudflared tunnel route ip add --virtual-network [ID/name] [CIDR] [TUNNEL]".` ,
55+ "cloudflared tunnel route ip add --vnet [ID/name] [CIDR] [TUNNEL]".` ,
5656 Flags : []cli.Flag {vnetFlag },
5757 },
5858 {
0 commit comments