VRFs
0
No VRF devices in this namespace. Create one with ip link add blue type vrf table 1001, then add interfaces with ip link set eth1 master blue.
default no VRF device table main (254) ipv6 routes: 4
| Member | Type | State | Via | Addresses |
|---|---|---|---|---|
| eth0 | device | up | fd20:0:10::2:0:0/96 fe80::e9:82ff:fe19:a7b0/64 |
|
| lo | device | unknown | 127.0.0.1/8 ::1/128 |
Routes in table main (4)
| Family | Type | Destination | Gateway | Device | Source | Encap | Protocol | Scope | Metric |
|---|---|---|---|---|---|---|---|---|---|
| ipv6 | unicast | fd20:0:10::2:0:0/96 | eth0 | kernel | universe | 256 | |||
| ipv6 | unicast | fe80::/64 | eth0 | kernel | universe | 256 | |||
| ipv6 | unicast | default | fd20:0:10::1 | eth0 | boot | universe | 1024 | ||
| ipv6 | unicast | default | fe80::a073:44ff:fea2:d9fe | eth0 | ra | universe | 1024 |
A VRF's members route through its table: the kernel's l3mdev rule sends their traffic there before the main table is consulted. Routes for the VRF's own addresses live in its table, not in local. Interfaces joined through a bridge or bond show it under Via.