In the last episode (Feb 11), Aaron Conaway said:
I'm looking to develop a database of IP addresses for the company and
have, of course, chosen mySQL as the backend. I want the app to add
(remove, etc.) a host, giving its hostname and segment. The app will
add the next available address to
On Tue, 11 Feb 2003, Dan Nelson wrote:
Store your addresses as INTs, so you would have three fields:
address, netmask, and gateway. You can either encode the values
yourself, or use mysql's INET_NTOA()/INET_ATON() functions.
...and beware, INET_NTOA/ATON calls aren't compatible (as far as I
]]
Sent: Tuesday, February 11, 2003 1:30 PM
To: Dan Nelson
Cc: Aaron Conaway; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: IP Addresses -- How to Store
On Tue, 11 Feb 2003, Dan Nelson wrote:
Store your addresses as INTs, so you would have three fields:
address, netmask, and gateway. You
On Tue, Feb 11, 2003 at 01:15:01PM -0500, Aaron Conaway wrote:
I'm looking to develop a database of IP addresses for the company and
have, of course, chosen mySQL as the backend. I want the app to add
(remove, etc.) a host, giving its hostname and segment. The app will
add the next available
- Original Message -
From: Michael T. Babcock [EMAIL PROTECTED]
To: Aaron Conaway [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, February 11, 2003 3:25 PM
Subject: Re: IP Addresses -- How to Store
On Tue, Feb 11, 2003 at 01:15:01PM -0500, Aaron Conaway wrote:
I'm looking
On Tue, Feb 11, 2003 at 03:34:52PM -0500, Peter Grigor wrote:
Dood, he's not gonna be very happy storing an IP as 16 bits :)
Excuse my long day; 32 bits would be much more useful.
--
Michael T. Babcock
CTO, FibreSpeed Ltd. (Hosting, Security, Consultation, Database, SQL)
