[MLB-WIRELESS] IP allocations within a node???

[Dan Flett]

Hi Mark,

I'll offer some practical IP addressing advice here:

The IP Allocations are really intended to be used by a node running an
Access Point (or Adhoc mode into wide-sector or omnidirectional antenna)

So node HRW is running an Access Point through an Omni antenna.  It should
request an IP Block through the Mapping database.  Let's pretend it gets
given 10.10.147.32/28.  Any node connected to that access point needs to use
addresses from within this range.  

Your useable address range would be 10.10.147.33-10.10.147.46.

As an example, you could give Node HRW's server PC the address of
10.10.147.33, and it's DL900+ AP 10.10.147.34.

Perhaps you have some other servers at Node HRW so give them
10.10.147.35-10.10.147.37.  

Permanent client nodes to HRW could be given IP addresses from the range
10.10.147.38-10.10.147.43 - either by DHCP (recognising their MAC address
each time to give them the same IP) or by static addressing by prior
arrangement.

"Transient" client nodes to HRW should be given addresses via DHCP - from a
range of 10.10.147.44-10.10.147.46.  I find 3 addresses more than adequate
to cater for casual passers by.  I then do some tricks with my firewall to
redirect their web-browser requests to my Node's homepage. ;)  This is
useful to do some PR for Melbourne Wireless - I recommend doing it.

If you are a client node to HRW, you do not need necessarily need your own
IP address allocation.  You don't need to use your 10.10.145.208/28 range at
all.  If you have a couple of servers at your (client) end, you can ask if
HRW will give you some of it's extra IP addresses for your servers.  If you
are connecting to HRW using an external client device like a Minitar, you
could connect the Minitar to a switch and connect your servers to the
switch.  If you are connecting using a card in a PC, you could
software-bridge your wireless card to a wired NIC and connect the servers to
that.  Since there is limited address space in a /28 block (AKA subnet),
this doesn't work so well.

If you only have one radio (your wireless card connecting to HRW's AP), but
multiple servers at your end, you could put your servers on your own
allocated 10.10.145.208/28 subnet, and *route* between your subnet and HRW's
(hypothetical 10.10.147.32/28) subnet.  This really is the preferred way to
connect two nodes together.  (You will still need at least one address from
HRW's subnet at your end though.)

You could do it statically, with a default route at your end - but HRW's
owners would need to enter the route to your node into their Quagga setup as
a static rotue and tell OSPF to redistribute static routes so that everyone
else on the network can see your node.

It is better to just set up dynamic routing (OSPF) at your end - then the
route to your subnet gets advertised to everyone else automatically - and
you will see individual routes to every other node's subnet on the network.
You will need to set up OSPF (or whatever protocol we use in the future) on
your node - it is worth learning how to do this.

If in future you decide to also get your own access point, give it an
address from within your own subnet - then you can have your own client
nodes and route their traffic between your subnet and HRW's subnet.  By
doing this you will contribute to the further spread of the network.

I'm thinking that this sort of thing should be covered in any workshops we
do in future - IP addressing, subnetting, and routing between nodes - with
practical examples.  I will look at my roster at work and see if I can get a
night free to do it - weeknights are good for me.

Cheers,

Dan

> -----Original Message-----
> From: owner-melbwireless at wireless.org.au [mailto:owner-
> melbwireless at wireless.org.au] On Behalf Of Mark Aitken
> Sent: Monday, 28 February 2005 12:33
> To: melbwireless at wireless.org.au
> Subject: [MLB-WIRELESS] IP allocations within a node???
> 
> I have a question about allocating IP addresses with a single node.
> 
> Here deep down south we have established NodeHRW as our central point.
> Currently just using 192.168.0.x addressing till
> we sort out a few things.  But, me, NodeGXT have an allocation
> 10.10.145.208/28.
> 
> I link to HRW as a client, as do other users, it naturally being the AP.
> 
> Is it better to DHCP ip address from within the HRW allocation block for
> users of that system, then "bridging/linking" another
> AP system, say GXT, with it's own allocation?
> 
> Hope this makes sense?
> 
> Mark
> 
> 
> 
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 266.5.1 - Release Date: 27/02/2005
> 
> 
> To unsubscribe: send mail to majordomo at wireless.org.au
> with "unsubscribe melbwireless" in the body of the message


To unsubscribe: send mail to majordomo at wireless.org.au
with "unsubscribe melbwireless" in the body of the message