[MLB-WIRELESS] ip allocation list based on suburb

[Longmuir, Brad]

What r the goals/requirements for an IP structure?

To allow for over all expansion.
Ensure that each class of node has the appropriate subnet/subnets for it to
function.
Adhere to a structure that supports route summary for a dynamic routing
protocol if it is implemented.

Are there any requirements from other services that rely on a IP structure?


Let other higher services deal with area identification, IP structure is not
the best way to do these things.  Keep it simple I say.

My two cents....




-----Original Message-----
From: Michael McKinnon [mailto:MichaelM at zonewerx.com]
Sent: Wednesday, 13 February 2002 1:15 PM
To: 'melbwireless at wireless.org.au'
Subject: RE: [MLB-WIRELESS] ip allocation list based on suburb


I like the suburb allocation idea, but why not go back to postcodes with:

Postcode 3000 = 10.30.1.x
Postcode 3121 = 10.31.21.x
Postcode 3550 = 10.35.50.x
Postcode 3032 = 10.30.32.x

It just depends how the C class that is left is separated.  In reality, each
node should not require more than 1 IP for each link to each other node, so
what is the average number of nodes in each suburb going to be?

.MJM

> -----Original Message-----
> From: drew at no6.com [mailto:drew at no6.com]
> Sent: Wednesday, 13 February 2002 8:04 AM

> have 10.1.xx for melb, 10.2.x.x for richmond, etc, etc. then 

-- SNIP --

-Drew



--
To unsubscribe, send mail to minordomo at wireless.org.au with a subject of
'unsubscribe melbwireless'  
Archive at:
http://www.wireless.org.au/cgi-bin/minorweb.pl?A=LIST&L=melbwireless
IRC at: au.austnet.org #melb-wireless

--
To unsubscribe, send mail to minordomo at wireless.org.au with a subject of 'unsubscribe melbwireless'  
Archive at: http://www.wireless.org.au/cgi-bin/minorweb.pl?A=LIST&L=melbwireless
IRC at: au.austnet.org #melb-wireless