Ir al contenido

Interfaces

Capturado el 2026-07-28 desde un CE de esta implementación. sitecli/capture-manifest.json registra qué nodo, y scripts/capture-sitecli.sh --check vuelve a verificar la superficie de comandos contra un CE en vivo.

Estos informan la visión del kernel. El plano de datos Argo mantiene la suya propia, visible a través de vif, y ambas pueden discrepar.

Recibe un subcomando ip. addr es el más habitual; route, link y neigh también funcionan.

Ventana de terminal
{"command":["ip","addr"]}
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: a-i-eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 60:45:bd:eb:3f:f2 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 60:45:bd:eb:38:ea brd ff:ff:ff:ff:ff:ff
inet 10.0.2.4/26 brd 10.0.2.63 scope global noprefixroute eth1
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 60:45:bd:eb:3d:f3 brd ff:ff:ff:ff:ff:ff
inet 10.0.3.4/26 brd 10.0.3.63 scope global noprefixroute eth2
valid_lft forever preferred_lft forever
inet6 fe80::55af:2cd4:23a1:7e06/64 scope link noprefixroute
valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 62:61:2b:33:cd:42 brd ff:ff:ff:ff:ff:ff
inet 100.64.255.1/29 brd 100.64.255.7 scope global docker0
valid_lft forever preferred_lft forever
10: tap_eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc multiq state UNKNOWN group default qlen 1000
link/ether 60:45:bd:eb:3f:f2 brd ff:ff:ff:ff:ff:ff
11: vhost0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether 60:45:bd:eb:3f:f2 brd ff:ff:ff:ff:ff:ff
inet 10.0.1.4/26 brd 10.0.1.63 scope global noprefixroute vhost0
valid_lft forever preferred_lft forever
13: vethfrr0@if12: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 02:01:02:03:04:05 brd ff:ff:ff:ff:ff:ff link-netns frrns
15: argo-envoy-0@if14: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1520 qdisc noqueue state UP group default qlen 1000
link/ether 00:00:5e:00:01:00 brd ff:ff:ff:ff:ff:ff link-netns envoy-ns
17: host-envoy-0@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ee:95:ea:b5:8c:2a brd ff:ff:ff:ff:ff:ff link-netns envoy-ns
inet 169.254.100.1/30 scope global host-envoy-0
valid_lft forever preferred_lft forever
18: xc-br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether aa:db:2f:e1:15:2c brd ff:ff:ff:ff:ff:ff
19: argo-end@xc-br0-end: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 76:e0:23:f6:48:8b brd ff:ff:ff:ff:ff:ff
20: xc-br0-end@argo-end: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master xc-br0 state UP group default qlen 1000
link/ether aa:db:2f:e1:15:2c brd ff:ff:ff:ff:ff:ff
22: linkquality0@if21: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 590 qdisc noqueue state UP group default
link/ether 00:00:5e:00:01:00 brd ff:ff:ff:ff:ff:ff link-netns ns-link-quality
24: vethbfd0@if23: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:00:5e:00:01:00 brd ff:ff:ff:ff:ff:ff link-netns bfdns
25: keepalived-tap: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 32:1d:e4:ae:46:0e brd ff:ff:ff:ff:ff:ff
inet 169.254.10.13/30 brd 169.254.10.15 scope global keepalived-tap
valid_lft forever preferred_lft forever
27: vethdnsmasq0@if26: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 02:01:02:03:04:07 brd ff:ff:ff:ff:ff:ff link-netnsid 4
inet 169.254.254.103/32 brd 169.254.255.255 scope global vethdnsmasq0
valid_lft forever preferred_lft forever

El CE tiene tres NIC de Azure por diseño —gestión/SLO, externa, interna/SLI—, pero el guest no las presenta de la forma que ese orden sugiere, y aquí es donde leer mal la salida cuesta tiempo.

En el guestTransporta
a-i-eth0ninguna dirección en absoluto — esta es la eth0 física renombrada, y el plano de datos Argo es su propietario
vhost0la dirección de gestión/SLO, la que utiliza BGP para el peering y la que informa el objeto de sitio
eth1 y eth2las direcciones externa e interna/SLI — pero no en un orden fijo

Que a-i-eth0 no lleve ninguna dirección es también toda la razón por la que no se puede alcanzar sshd en la dirección de gestión: allí no hay ningún proceso a la escucha, no es un puerto bloqueado. Consulte SSH.

Solo capa de enlace: estado, MTU, disciplina de encolado, MAC.

Ventana de terminal
{"command":["ip-link-show"]}
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: a-i-eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 60:45:bd:eb:3f:f2 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 60:45:bd:eb:38:ea brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 60:45:bd:eb:3d:f3 brd ff:ff:ff:ff:ff:ff
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 62:61:2b:33:cd:42 brd ff:ff:ff:ff:ff:ff
10: tap_eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc multiq state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 60:45:bd:eb:3f:f2 brd ff:ff:ff:ff:ff:ff
11: vhost0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 60:45:bd:eb:3f:f2 brd ff:ff:ff:ff:ff:ff
13: vethfrr0@if12: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 02:01:02:03:04:05 brd ff:ff:ff:ff:ff:ff link-netns frrns
15: argo-envoy-0@if14: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1520 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 00:00:5e:00:01:00 brd ff:ff:ff:ff:ff:ff link-netns envoy-ns
17: host-envoy-0@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether ee:95:ea:b5:8c:2a brd ff:ff:ff:ff:ff:ff link-netns envoy-ns
18: xc-br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether aa:db:2f:e1:15:2c brd ff:ff:ff:ff:ff:ff
19: argo-end@xc-br0-end: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 76:e0:23:f6:48:8b brd ff:ff:ff:ff:ff:ff
20: xc-br0-end@argo-end: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master xc-br0 state UP mode DEFAULT group default qlen 1000
link/ether aa:db:2f:e1:15:2c brd ff:ff:ff:ff:ff:ff
22: linkquality0@if21: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 590 qdisc noqueue state UP mode DEFAULT group default
link/ether 00:00:5e:00:01:00 brd ff:ff:ff:ff:ff:ff link-netns ns-link-quality
24: vethbfd0@if23: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 00:00:5e:00:01:00 brd ff:ff:ff:ff:ff:ff link-netns bfdns
25: keepalived-tap: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 32:1d:e4:ae:46:0e brd ff:ff:ff:ff:ff:ff
27: vethdnsmasq0@if26: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 02:01:02:03:04:07 brd ff:ff:ff:ff:ff:ff link-netnsid 4

Más rápido que ip addr cuando la pregunta es «¿está el enlace activo y cuál es su MTU?». Las discrepancias de MTU son una causa recurrente de túneles que se establecen pero no pasan tráfico.

Sección titulada «ip-link-set »

Activa o desactiva una interfaz o un grupo.

ip-link-set (<device>||<group>) (up||down)