On Fri, Sep 09, 2011 at 05:17:55PM -0700, Bill Prince wrote:
> Well, the old AP is on ether2, and all the old SMs are there too and
> on the /26 subnet.
>
> The new AP is on ether7, and the new SMs will not talk to the old AP.
> So they will have to go somewhere, and I don't have enough spare IP
> addresses to just plunk down a new subnet on the new AP.
Why not just create a bridge interface, add ether2 and ether7. Move
the subnet, and dhcp server (if any) to the new bridge interface.
You can split it up after you get the equipment reorganized. Just
assign everyone IPs in the appropriate /26 per AP. Then it's easy
to split the /27 when you're done getting the clients shuffled.
You may need to add an extra IP in the top or bottom /26 for your
customers on each AP to use for their default gateway.
But if you're using DHCP just lower the lease time to 5 minutes and
when you setup the new DHCP server for the split subnet, nobody
will be out of commission for longer than that. Make the split at
2:00AM and very few people will notice.
You could just run the two AP groups in the same bridge with a
bridge filter to keep them from talking to one another and make
more efficient use of the IPs in that /27. I don't want bridges
spanning towers, but I don't mind all the APs being in the same
bridge. Address managment is much easier.
/interface bridge filter
add action=accept chain=forward disabled=no in-bridge=AP_bridge \
out-bridge=!AP_bridge
add action=drop chain=forward disabled=no in-bridge=AP_bridge
--
Scott Lambert KC5MLE Unix SysAdmin
[email protected]
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
