summaryrefslogtreecommitdiff
path: root/docs/configuration/system/ip.md
blob: 2445509d55a471bc884a8e12d3d42531cc9222b2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
# IP

## System configuration commands

```{eval-rst}
.. cfgcmd:: set system ip disable-forwarding

   Use this command to disable IPv4 forwarding on all interfaces.
```

```{eval-rst}
.. cfgcmd:: set system ip disable-directed-broadcast

   Use this command to disable IPv4 directed broadcast forwarding on all
   interfaces.

   If set, IPv4 directed broadcast forwarding will be completely disabled
   regardless of whether per-interface directed broadcast forwarding is
   enabled or not.
```

```{eval-rst}
.. cfgcmd:: set system ip arp table-size <number>

   Use this command to define the maximum number of entries to keep in
   the ARP cache (1024, 2048, 4096, 8192, 16384, 32768).
```

```{eval-rst}
.. cfgcmd:: set system ip multipath layer4-hashing

   Use this command to use Layer 4 information for IPv4 ECMP hashing.
```

### Zebra/Kernel route filtering

Zebra supports prefix-lists and Route Mapss to match routes received from
other FRR components. The permit/deny facilities provided by these commands
can be used to filter which routes zebra will install in the kernel.

```{eval-rst}
.. cfgcmd:: set system ip protocol <protocol> route-map <route-map>

   Apply a route-map filter to routes for the specified protocol. The following
   protocols can be used: any, babel, bgp, connected, eigrp, isis, kernel,
   ospf, rip, static, table

   .. note:: If you choose any as the option that will cause all protocols that
      are sending routes to zebra.
```

### Nexthop Tracking

Nexthop tracking resolve nexthops via the default route by default. This is enabled
by default for a traditional profile of FRR which we use. It and can be disabled if
you do not wan't to e.g. allow BGP to peer across the default route.

```{eval-rst}
.. cfgcmd:: set system ip nht no-resolve-via-default

   Do not allow IPv4 nexthop tracking to resolve via the default route. This
   parameter is configured per-VRF, so the command is also available in the VRF
   subnode.
```

## Operational commands

### show commands

See below the different parameters available for the IPv4 **show** command:

```none
vyos@vyos:~$ show ip
Possible completions:
  access-list   Show all IP access-lists
  as-path-access-list
                Show all as-path-access-lists
  bgp           Show Border Gateway Protocol (BGP) information
  community-list
                Show IP community-lists
  extcommunity-list
                Show extended IP community-lists
  forwarding    Show IP forwarding status
  groups        Show IP multicast group membership
  igmp          Show IGMP (Internet Group Management Protocol) information
  large-community-list
                Show IP large-community-lists
  multicast     Show IP multicast
  ospf          Show IPv4 Open Shortest Path First (OSPF) routing information
  pim           Show PIM (Protocol Independent Multicast) information
  ports         Show IP ports in use by various system services
  prefix-list   Show all IP prefix-lists
  protocol      Show IP route-maps per protocol
  rip           Show Routing Information Protocol (RIP) information
  route         Show IP routes
```

### reset commands

And the different IPv4 **reset** commands available:

```none
vyos@vyos:~$ reset ip
Possible completions:
  arp           Reset Address Resolution Protocol (ARP) cache
  bgp           Clear Border Gateway Protocol (BGP) statistics or status
  igmp          IGMP clear commands
  multicast     IP multicast routing table
  route         Reset IP route
```