Reference
Interface settings
Name your routers' interfaces, set which side each faces, set subscribed rates, and choose which appear on the Interfaces page.
Configure → Interface settings lists every interface Heimnull knows, by exporter. Interfaces come from SNMP (with their names) or from flow records (by index, until SNMP names them).
| Role | For | Effect |
|---|---|---|
| Transit | Links to your transit providers | Faces the internet |
| Peering | Internet exchanges and private peers | Faces the internet |
| Internal | Customers, core, LAN | Inside your network |
| Other | Anything else | Inside your network |
Only “faces the internet” changes what Heimnull does:
- Direction. Traffic entering on a Transit or Peering interface and leaving on any other is inbound, even when neither address is in your networks; the reverse is outbound. Such traffic also feeds the Possibly missing networks list on the Networks page.
- Copies. On an exporter sampled on both sides, a sample taken anywhere but a Transit or Peering interface is a copy, kept out of the totals.
- Planning. Capacity forecasts, the transit view and congestion escalation use the Transit and Peering interfaces.
- NAT. The Juniper SRX’s NAT correlation reads Internal as the LAN side.
Internal and Other behave the same; Internal documents the inside.
Other settings
Section titled “Other settings”| Setting | What it does |
|---|---|
| Name | A display name, if the SNMP name isn’t clear |
| Subscribed rate | The capacity to measure against, when it’s below the port speed (your commit, or a rate-limited port). Accepts k, M, G and T, for example 2G or 500M. Empty uses the port speed from SNMP |
| Show on the Interfaces page | Lists the interface under Traffic → Interfaces and in Planning |