EntityDB holds all network allocations and associated information.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Marek Küthe 5e026a49bc Merge pull request 'maxlen filter script: Add UCI support' (#36) from mark22k/crxn-entitydb:master into master
Reviewed-on: #36
2 months ago
LICENSE.md Add autistic gay penis licsense version three 2 years ago
README.md Fix invalid JSON in README.md 2 years ago
bandura.json add new router 2 months ago
build_maxlen_filter.sh maxlen filter script: Add UCI support 2 months ago
deavmi.json fix deavmi 5 months ago
reddawn.json fix && format 5 months ago
schema solve problem `Every 'entity' has its data stored in a JSON file named as 'UNIQUE.json' where UNIQUE is any unique identifier (UUID/hash/name etc.).` 4 months ago
skiqqy.json fix && format 5 months ago
test.sh use another for each method and check for device 4 months ago
ty3r0x.json Fixed discrepancies 2 months ago

README.md

entitydb

EntityDB holds all network allocations and associated information.

Format

Every 'entity' has its data stored in a JSON file named as 'UNIQUE.json' where UNIQUE is any unique identifier (UUID/hash/name etc.).

Content of entity (data)

The data should be a JSON object with a anonymous top-level object and "route" as only object. "route" should be a list of all routes provided by the entity with a required list of devices named "device".

"device" must contain at least one device that is reachable. A router is commonly used as the only object for the network as it is necessary in most setups.

Every device can contain the type of the device (router, generic, server), along with the list of services as "service". When no type is defined, generic is assumed.

Services must have a type (eg. tcp, udp, http, rsync, git) and at least one endpoint in the endpoints list.

Every object may contain a optional description, except lists.

Descriptions should not be used other than for describing things in a human-readable form.

Example

Here's a example that you may modify to your needs.

{
  "route": {
    "fdaa:bbcc:ddee::/48": {
      "description": "My home network",
      "device": {
        "fdaa:bbcc:ddee::1": {
          "type": "router",
          "description": "My custom router running BIRD"
        },
        "fdaa:bbcc:ddee::5": {
          "description": "Electronic mail endpoint",
          "service": [
            {
              "type": "smtp",
              "endpoint": [
                { "port": 25 }
              ]
            },
            {
              "description": "Super-secret authentication gateway",
              "type": "kerberos",
              "endpoint": [
                { "port": 89 }
              ]
            },
            {
              "type": "imap",
              "endpoint": [
                { "port": 143 }
              ]
            }
          ]
        }
      }
    },
    "fdcc:ba11:b00b::/48": {
      "device": {
        "fdcc:ba11:b00b::1": {
          "type": "router"
        }
      }
    }
  }
}