As someone doing it in practice, I just drag and drop 255 rows for the
IPs.  It's not that big of a deal.  One time I had to do a whole 2048 rows
and it probably took me a minute.

On Mon, Sep 15, 2025 at 3:29 PM Brian Knight via NANOG <
[email protected]> wrote:

> On 2025-09-15 13:30, Bryan Fields via NANOG wrote:
> > Has anyone found a solution to represent IPv4 addresses in a
> > spreadsheet, preferably Google Sheets?  I'm not here to debate the use
> > of spreadsheets for tracking IP addresses, just find something better
> > than storing v4 dotted decimal as text in a spreadsheet.  We don't need
> > v6 at this time; we're using a spreadsheet for tracking addressing, v6
> > is beyond us.
> >
> > At minimum we need to store it as a 32 bit INT, and display as dotted
> > decimal.  If there's some way to make it aware of subnet slash
> > notation, so much the better.  I'm a bit at a loss as to why there's no
> > IPv4 number format with how often spreadsheets are the source of truth
> > in some rather large service providers.
> >
> > Again, not looking for non-spreadsheet solutions to this, and ideally a
> > web interface spreadsheet would be best for sharing.  We don't need a
> > real database if it's on the web :-)
>
> If you're not allergic to MS Excel, you could use Python for Excel to
> convert back and forth with the excellent ipaddress module.
>
> https://www.google.com/?q=google%20sheets%20ip%20functions turned up an
> interesting add-on, have you looked into IP Functions at all?
>
> Could also just roll your own inet_aton() in your columns for the dotted
> quads using LEFT(), MID(), RIGHT(), and FIND().
>
> Or just spin up Netbox and load your prefixes into that and be done.
>
> -Brian
> _______________________________________________
> NANOG mailing list
>
> https://lists.nanog.org/archives/list/[email protected]/message/QIZBM4KIRQRM22MRRZB2XXZMPX7JQB2Z/
>
_______________________________________________
NANOG mailing list 
https://lists.nanog.org/archives/list/[email protected]/message/ZRQN2X6TX77BE4RGUTXHZSNNB4YQN6YU/

Reply via email to