Replies: 9 comments 16 replies
-
Have you considered adding a custom field on the prefix? (Although it would have to be plain text, as "IP address" is not one of the options) It's not something I've ever felt the need to store, as we have the simple rule that the first available IP address in every subnet is the gateway. Of course, this may be a VRRP or CARP address, and the real gateways are using the next addresses. |
Beta Was this translation helpful? Give feedback.
-
The default gateway for any device is just a component of your network's routing topology, which NetBox does not model. There's nothing special about the default route, nor is there any requirement that all interfaces within a prefix must use the same default gateway(s). The flow of traffic is entirely dependent upon your network's routing topology, which NetBox does not model. |
Beta Was this translation helpful? Give feedback.
-
I have read many issues regarding that. IMHO: Default gateway is the default routing information from the devices's point of view. Again, all this depends on the devices's point of view and will be differ in many infrastructures out there. I think this is a main reason why Jeremy can't agree with our proposals. I hope that i didn't misunderstood your answers in those issues, please correct me @jeremystretch if i am wrong. Our main goal is to document gateway informations for prefixes. A gateway is a combination of a device, an interface and a corresponding ip address on this interface. It's the "exit" out of a subnet. A gateway isn't only a device or an ip address, So how can we put those information in a correct way to netbox? In the UI it could be visualize as follows: I have looked around how other tools handles this.
What you are thinking about that? |
Beta Was this translation helpful? Give feedback.
-
I just mark the gateway IPs as "reserved" and put "gateway" in the description. My company just started using 6connect - oy vey... All devices go in as a /32 which is so freaking annoying. I have to hop on the routers to find the subnet mask. netbox has been awesome for me. My records for 153 racks so far has never been so accurate. |
Beta Was this translation helpful? Give feedback.
-
we have just come close to the trigger point on the move from racktables to netbox, all other objects are now migrated and "in sync" with racktables, only to now realise this is an issue. |
Beta Was this translation helpful? Give feedback.
-
Found my way here looking for a way to mark a single IP as default gateway, and I'm flabbergasted to find that there's now "real" way of doing it. I was looking into moving to NB from phpIPAM (where this is possible), as the ansible modules for NB are much more comprehensive. |
Beta Was this translation helpful? Give feedback.
-
What we document is the following: What are the L3 devices connected to a given prefix. This may be typically a router, firewall or similar device.
From the prefix view it is thus easy for a given subnet to know what routing devices are responsible for it. This is required because devices belonging to a prefix may be in multiple physical sites. We needed to know quickly to what routing devices are associated from the prefix view from a network planning perspective. |
Beta Was this translation helpful? Give feedback.
-
Usually the most important difference between manually doing whatever I please (like "tagging" defgw, or putting it into a note) is consistency: when it's part of the storage schema updating the subnet "updates" everything in the subnet, and no need to manually go around 1e30 interfaces and update them one by one. That is my main pain point here since no matter how I hack it, it will not be and stay consistent, and requires manual updates for both the network and the interfaces. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I have read through several issues [like #330 #819 #1434 #1610 #2163 #2953 #3109 #3237 ] where people have tried to figure out how to store the gateway(s) for a given subnet, by trying IP roles, tags, and various other ideas. As far as I see most of these issues were closed as various kinds of "bad idea".
However I don't really see how am I supposed to record defgw then?
For IPv4 it is an address, most of the time, so either an address or an interface+address acts as a default gateway; I expect to see the gateway when I open a subnet, an address or the list of interfaces, and these various mutations.
Theoretically I could tag addresses as "defgw" but the tag is not shown in almost any lists: not in prefixes (various forms), child prefixes or addresses, so the usability of it is close to none.
For IPv6 there may be multiple routers present and they are usually connected to specific interfaces, but they almost can be related to the v6 prefixes as well. Obviously tagging doesn't help here either.
As for contrast we've been using a different program for IPAM for years which can mark any address as "gateway", and when one pulls up a data sheet of a subnet both the gateway addresses and the interfaces of the routers are listed, extremely conveniently. It is also the way to draw IP topology automagically, like running "virtual traceroute" and draw the path throughout various vlans, VRFs and stuff.
Why this seems to be a largely ignored part in NB?
Beta Was this translation helpful? Give feedback.
All reactions