Hi all. We have a wireless network with 3 principal nodes as you can see here
We are experiencing some troubles configuring routing between the 3 nodes without nat. The problem is that if we cannot activate natting in the interface that links 2 nodes we cannot reach the internet from the customers. Obviously there is a mistake somewhere but we cannot find it ! I would like to ask if somewhere there is a sample configuration for a network like this (I suppose so )

If necessary i can post all the configuration

Thanks in advance

Fabio Piazzon

I've just migrated my LocustWorld nodes to MikroTik RouterOS and have taken the opportunity to renumber my network to make it more logical.

There are infinite possibilities and no one right way to do it. So here's what I did, but superimposed on your network. Note that I've allowed for loads of expansion in my addressing scheme, lack of addresses in the original schema designed by a predecessor was the main reason for renumbering. A rule of thumb, however many addresses you think you'll need, double it and you can't go far wrong! The scheme is designed to make it easy to identify the geographical location from the IP address.

I can't make out from the picture what the links between nodes are, ethernet or wireless?

I have assumed a worst case scenario that a router might have public and private ethernet segments and public and private APs, thus I always allocate all the addresses even if currently the node doesn't have one of the interfaces, this makes it weasier to keep the addressing scheme logical and allow for adding other services at a later date.

This schema shown below only covers the main nodes, e.g. a subnode off node 1 on my network would have subnets 10.0.16.0/22, 10.0.20.0/22, 10.0.24.0/22 & 10.0.28.0/22, subnode off node2 would have subnets 10.2.16.0/22, 10.1.20.0/22, 10.1.24.0/22 & 10.1.28.0/22 etc. etc.

Hopefully you can follow my logic.


Internet Router
LAN 10.0.0.1/22 (Netmask 255.255.252.0)
route 10.0.0.0/16 via 10.0.0.2


Node 1
ether1 10.0.0.2/22
10.0.4.0/22 reserved for local private ethernet segment
10.0.8.0/22 private wireless AP for subscription based users
10.0.12.0/22 public wireless AP for ad hoc hotspot users
10.254.0.1 WDS bridge
10.254.0.0/16 used for WDS links between main nodes, e.g. node1 is 10.254.0.1, node2 is 10.254.1.1, node3 is 10.254.2.1. I then increment the last octet for an sub-nodes off the main node
default route (0.0.0.0/0) via 10.0.0.1
route 10.1.0.0/16 via 10.254.1.1
route 10.2.0.0/16 via 10.254.2.1


Node 2
10.1.0.0/22 for public ethernet
10.1.4.0/22 reserved for local ethernet segment
10.1.8.0/22 private wireless AP for subscription based users
10.1.12.0/22 public wireless AP for ad hoc hotspot users
10.254.1.1 WDS bridge
10.254.0.0/16 used for WDS links between main nodes
default route via 10.254.0.1
route 10.2.0.0/16 via 10.254.2.1


Node 3
10.2.0.0/22 for public ethernet
10.2.4.0/22 reserved for local ethernet segment
10.2.8.0/22 private wireless AP for subscription based users
10.2.12.0/22 public wireless AP for ad hoc hotspot users
10.254.2.1 WDS bridge
10.254.0.0/16 used for WDS links between main nodes
default route via 10.254.0.1


Note that the 10.254.0.0/16 network is bridged.

If you setup RIP all the internal network routes will be propagated.


Regards

Chris Macneill

Hi. Thank you for your answer. Nodes are linked via wireless. One more question.... is it necessary to have WDS ??? Is not possible to have "normal" routing ?

Thanks

Fabio Piazzon

If you have seperate wireless cards in your routers for backhaul and AP you can use normal routing. I have an existing infrastructure where the nodes only had one radio card, thus I had to use WDS.

Regards

Chris Macneill