gateway address/allocated address
psyber
05-01-2010 13:39:05
I see you have a bug listed to add this feature (FS#15 - Flag a single IP on a subnet as the gateway address )
highlander style
I'd like to dissuade you on that point, many of our networks have multiple gateways and it's becoming more and more common.
Take for instance VRRP, multiple routers with a virtual gateway, each ip is a valid default route off the network (though if you want the benefit of the redundancy you will choose the virtual gateway address) There may be times when you want to force traffic through a specific router or interface and to do that you would use one of the real IPs.
Only slightly realated...
Just being able to mark an IP as "reserved" or "mysteriously in use" without having to give it a unique name would be a big help (and make them easier to find later). We recently switched over from doing the files manually to using ONA and though we did get everything that was in DNS into ONA I still find that we have several hosts that are not registered but are active (my only clues to what they are are the MAC addresses and the data from IPPlan which we were using for allocation tracking). One day I will seek out all those hosts/admins and deal with them on a "personal" level but for now I just want to prevent the IP conflicts. Another possible solution might be an indicator on the available IPs that tells you if it answers pings or an nmap scan.
highlander style
I'd like to dissuade you on that point, many of our networks have multiple gateways and it's becoming more and more common.
Take for instance VRRP, multiple routers with a virtual gateway, each ip is a valid default route off the network (though if you want the benefit of the redundancy you will choose the virtual gateway address) There may be times when you want to force traffic through a specific router or interface and to do that you would use one of the real IPs.
Only slightly realated...
Just being able to mark an IP as "reserved" or "mysteriously in use" without having to give it a unique name would be a big help (and make them easier to find later). We recently switched over from doing the files manually to using ONA and though we did get everything that was in DNS into ONA I still find that we have several hosts that are not registered but are active (my only clues to what they are are the MAC addresses and the data from IPPlan which we were using for allocation tracking). One day I will seek out all those hosts/admins and deal with them on a "personal" level but for now I just want to prevent the IP conflicts. Another possible solution might be an indicator on the available IPs that tells you if it answers pings or an nmap scan.
Matt
07-01-2010 22:28:42
I understand your position here. My thought for this feature is that it will simply be a classification of an IP on the network. It will not be a requirement to tag an interface nor will it be much more than just a note about the IP being the default.
While I agree that there can potentially be many gateways to a subnet, I believe there will always only be one "default" gateway. Let me know if this does not jive with reality though.
Another motivation for this feature was a way to do a one click task to flag the gateway IP and then the DHCP build scripts could use that for the dhcp default gateway option for that subnet instead of having to manually add it as a dhcp option. If one forgets to manually add it, the subnet will not build.
So, I agree with what you have stated but I plan that the feature would not be required and more of an informational thing for just the default of many gateways
As far as marking an IP as reserved or in use without requiring a name.. you are not the first to suggest this one (I my self have wanted it from time to time). At this point I dont plan on adding that ability because it will require lots of code to get around inherent things in ONA. Adding a dummy dns name and the IP does not take too long to add. Also, while it may take time to do, it is a good thing to track down those hosts and deal with them (yea yea I know.. wishful thinking in many organizations).
When it comes to an indicator that shows available ips based on pings/nmap scans.... that I can do for you.. in fact it is actually built and is part of the next release. It provides an audit of your network based on nmap pings and compares that to data in ONA so you can keep things accurate and audited. This tool will also update the "last response" flag for an IP so you can run reports on IPs that are potentially no longer in use. A simple screenshot is here:
![]()
http://opennetadmin.com/images/nmap_scan.png[/img:3u0op8r3]
Hope that helps?
While I agree that there can potentially be many gateways to a subnet, I believe there will always only be one "default" gateway. Let me know if this does not jive with reality though.
Another motivation for this feature was a way to do a one click task to flag the gateway IP and then the DHCP build scripts could use that for the dhcp default gateway option for that subnet instead of having to manually add it as a dhcp option. If one forgets to manually add it, the subnet will not build.
So, I agree with what you have stated but I plan that the feature would not be required and more of an informational thing for just the default of many gateways
As far as marking an IP as reserved or in use without requiring a name.. you are not the first to suggest this one (I my self have wanted it from time to time). At this point I dont plan on adding that ability because it will require lots of code to get around inherent things in ONA. Adding a dummy dns name and the IP does not take too long to add. Also, while it may take time to do, it is a good thing to track down those hosts and deal with them (yea yea I know.. wishful thinking in many organizations).
When it comes to an indicator that shows available ips based on pings/nmap scans.... that I can do for you.. in fact it is actually built and is part of the next release. It provides an audit of your network based on nmap pings and compares that to data in ONA so you can keep things accurate and audited. This tool will also update the "last response" flag for an IP so you can run reports on IPs that are potentially no longer in use. A simple screenshot is here:
Hope that helps?