diff options
| author | Christian Poessinger <christian@poessinger.com> | 2020-07-18 14:43:03 +0200 |
|---|---|---|
| committer | Christian Poessinger <christian@poessinger.com> | 2020-07-18 14:43:05 +0200 |
| commit | 3435b2514ccd75fa9919ec5cdbe5e4e7e10b0818 (patch) | |
| tree | a04c889d9791a54dc38f89337f6f5dfaff58972c /op-mode-definitions | |
| parent | 6897aaf40e321cb585b299a75085f75666b5f816 (diff) | |
| download | vyos-1x-3435b2514ccd75fa9919ec5cdbe5e4e7e10b0818.tar.gz vyos-1x-3435b2514ccd75fa9919ec5cdbe5e4e7e10b0818.zip | |
monitor: ndp: T2706: remove ability to send commands
The "monitor" operational mode tree is for listening in on logfiles, chatter
on the wire or other things - it subscribes to the system. Hence it should under
no circumstances - ever - generate data. Sending our those requests, same as
e.g. calling ndisc6 should be placed under a different node.
Which one? I yet have no idea.
Diffstat (limited to 'op-mode-definitions')
| -rw-r--r-- | op-mode-definitions/monitor-ntp.xml (renamed from op-mode-definitions/ndp-monitor.xml) | 16 |
1 files changed, 0 insertions, 16 deletions
diff --git a/op-mode-definitions/ndp-monitor.xml b/op-mode-definitions/monitor-ntp.xml index 6ef3bce60..e25eccf3a 100644 --- a/op-mode-definitions/ndp-monitor.xml +++ b/op-mode-definitions/monitor-ntp.xml @@ -25,14 +25,6 @@ <list>rs ra ns na</list> </completionHelp> </properties> - <children> - <tagNode name="send"> - <command>sudo ndptool send --ifname=$4 --msg-type=$6</command> - <properties> - <help>Send a specified type of NDP message</help> - </properties> - </tagNode> - </children> </tagNode> </children> </tagNode> @@ -44,14 +36,6 @@ <list>rs ra ns na</list> </completionHelp> </properties> - <children> - <tagNode name="send"> - <command>sudo ndptool send --msg-type=$4</command> - <properties> - <help>Send a specified type of NDP message</help> - </properties> - </tagNode> - </children> </tagNode> </children> </node> |