Manufacturer Usage Descriptions (MUDs) allow manufacturers of IoT equipment to specify the intended network communication patterns of the devices they manufacture.
The access control policies described in a MUD File allow network controllers to automatically enforce rules on the device, resulting in devices only being allowed to communicate within the boundaries of the access control policies.
Things that can be done
Fix (most) TODOs ... :-)
Improve README.md
Add 'Use' to commands
Add tests
Customize / improve the MUD Visualizer?
Add logging (with levels)
Replace calls to fmt with proper logging / output
Allow the tool to be chained (i.e. use STDIN/STDOUT, pipes, etc.)
A command for generating MUD files (from pcap or some different way)
A command for editing MUD files (i.e. metadata)
A command that initializes a .mud directory inside user HOME, that is used for intermediate storage? If necessary, of course.
...
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.