Re: Documentation Edit Request: 2.6 .4. Address Filter Administrative Web Page

Eric Shubert <[email protected]>
Newsgroups gmane.comp.security.ipcop.devel
Organization Eric Shubert & Associates
Message-ID <[email protected]>
Thanks for the info, Haute. It caused me to learn more about this, and 
I've reached the conclusion that there's no "true function name" for this.

Per wikipedia:
static allocation: The DHCP server allocates an IP address based on a 
table with MAC address/IP address pairs, which are manually filled in 
(perhaps by a network administrator). [Only requesting clients with a 
MAC address listed in this table will be allocated an IP address]. This 
feature (which is not supported by all DHCP servers) is variously called 
Static DHCP Assignment (by DD-WRT), fixed-address (by the dhcpd 
documentation), Address Reservation (by Netgear), DHCP reservation or 
Static DHCP (by Cisco/Linksys), and IP reservation or MAC/IP binding (by 
various other router manufacturers).

I might add that it's also called reservation by Windows Server.

I googled briefly for something about this in the RFCs, but came up with 
nothing. If there's something in an RFC about this, I'd like to know 
what it says.

I think that fixed and reserved are equally good terms, each with its 
own drawbacks. They're certainly better than static in my mind though.

-- 
-Eric 'shubes'

On 09/03/2012 04:07 PM, Haute SubZero wrote:
> While I agree that using the term 'static' is not only incorrect but also
> confusing, the true function in use is actually 'DHCP with Reservations' so
> I would recommend using 'reserved' instead of either fixed or static.
>
>
> -----Original Message-----
> From: Eric Shubert [mailto:[email protected]]
> Sent: Sunday, September 02, 2012 7:51 PM
> To: [email protected]
> Subject: [IPCop-devel] Documentation Edit Request: 2.6.4. Address Filter
> Administrative Web Page
>
> This page:
> http://www.ipcop.org/2.0.0/en/admin/html/firewall-blue-access.html
> refers to "fixed" addresses (DHCP page lingo, which I *really* like) as
> "static". I'd like to see "static" changed to "fixed", which is consistent
> with the DHCP page, and is a clearer term for what's being addressed. Is
> there some way I can help to edit the documentation?
>
> Thanks for everyone's great work on IPCop. I'm finally delving into 2.0!
> (Just in time for 2.1 I guess).
>
> --
> -Eric 'shubes'
>
>
>
> ----------------------------------------------------------------------------
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> IPCop-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>





------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.