Add "net events [on|off]" command that can be used to monitor the generated network management events. The monitor output looks like this when enabled: EVENT: L2 [1] up EVENT: L3 [1] IPv6 mcast address add ff02::1:ff00:1 EVENT: L3 [1] IPv6 mcast join ff02::1:ff00:1 EVENT: L3 [1] IPv6 address add 2001:db8::1 EVENT: L4 [1] connected EVENT: L3 [1] IPv6 prefix add 2002:5b9b:41a0:: EVENT: L3 [1] IPv6 address add 2002:5b9b:41a0:0:fec2:3dff:fe11:c147 EVENT: L3 [1] IPv6 neighbor add fe80::9ec7:a6ff:fe5e:4735 EVENT: L3 [1] IPv6 router add fe80::9ec7:a6ff:fe5e:4735 EVENT: L3 [1] IPv6 DAD ok fe80::fec2:3dff:fe11:c147 EVENT: L3 [1] IPv6 DAD ok 2001:db8::1 EVENT: L3 [1] IPv6 DAD ok 2002:5b9b:41a0:0:fec2:3dff:fe11:c147 EVENT: L3 [1] IPv4 address add 192.168.1.69 EVENT: L3 [1] DHCPv4 bound 192.168.1.69 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com> |
||
|---|---|---|
| .. | ||
| 8021Qav.rst | ||
| apis.rst | ||
| buf_mgmt.rst | ||
| can_api.rst | ||
| can_isotp_sequence.svg | ||
| can_isotp.rst | ||
| can_timing.svg | ||
| can_transceiver.svg | ||
| can.rst | ||
| coap.rst | ||
| dhcpv4.rst | ||
| dns_resolve.rst | ||
| ethernet_mgmt.rst | ||
| ethernet.rst | ||
| gptp.rst | ||
| gsm_modem.rst | ||
| ieee802154.rst | ||
| index.rst | ||
| ip_4_6.rst | ||
| lldp.rst | ||
| lwm2m.rst | ||
| mqtt.rst | ||
| net_buf.rst | ||
| net_config.rst | ||
| net_context.rst | ||
| net_core.rst | ||
| net_hostname.rst | ||
| net_if.rst | ||
| net_l2.rst | ||
| net_linkaddr.rst | ||
| net_mgmt.rst | ||
| net_offload.rst | ||
| net_pkt.rst | ||
| net_shell.rst | ||
| net_stats.rst | ||
| net_tech.rst | ||
| net_timeout.rst | ||
| ppp.rst | ||
| promiscuous.rst | ||
| protocols.rst | ||
| ptp_time.rst | ||
| sntp.rst | ||
| sockets.rst | ||
| socks5.rst | ||
| system_mgmt.rst | ||
| thread.rst | ||
| traffic-class.rst | ||
| trickle.rst | ||
| tsn.rst | ||
| vlan.rst | ||
| websocket.rst | ||