On 09/21/2011 12:33 PM, Bill Prince wrote:
I don't know how to do that. What do you do for gateway, etc.? Got a
link somewhere?
This is weird, but we're switching to this using a vlan for each
customer (tagged on their radio) and I'm liking it. If you're familiar
with doing route-bridge encapsulation ATM PVCs on a Cisco for DSL, it's
the same kind of setup, just with wireless and VLANs instead of DSL and
ATM. I'll leave out the VLAN part because it makes it more complicated
and isn't strictly necessary in your case.
Say your public subnet is 10.0.0.0/24. On router A you have customers
10, 11, 12 with IP addresses 10.0.0.10, 10.0.0.11, and 10.0.0.12,
respectively connected via ether2.
router_A> /interface bridge add name=loop
router_A> /interface ethernet set ether2 arp=proxy-arp
router_A> /ip address add address=10.0.0.1/24 interface=loop
router_A> /ip address add address=10.0.0.1/32 network=10.0.0.10
interface=ether2 comment=cust_10
router_A> /ip address add address=10.0.0.1/32 network=10.0.0.11
interface=ether2 comment=cust_11
router_A> /ip address add address=10.0.0.1/32 network=10.0.0.12
interface=ether2 comment=cust_12
That adds a connected route for .10, .11, and .12 on ether2. You could
have cust 12 on ether3, for example, and it still works because the
connected route causes the router to ARP on the correct interface.
Enabling proxy-arp causes the router to reply for customer ARP requests
on ether2 for addresses assigned to ether3, and vice versa.
In Cisco-ese, that looks like...
interface loopback 1
ip address 10.0.0.1 255.255.255.0
!
interface ATM0/0.10
ip unnumbered loopback 1
!
ip route 10.0.0.10 255.255.255.255 ATM0/0.10 1
...
That may work for ethernet interfaces (instead of ATM) as well, but I've
never tested it.
Now, if you're using OSPF and don't mind flooding your network with /32
routes, you can duplicate the same procedure on other routers using the
same /24. Since the /32 routes received from other routers via OSPF are
more specific than your /24 (and don't conflict with the other /32s),
it'll properly route traffic to other routers.
The other option would be to tunnel all of your traffic back to a
central router using EoIP tunnels or MPLS, bridge the tunnels together,
and assign the 24 to the bridge. Then you can assign addresses to any
POP from the same subnet. We've used this method to convert a bridged
WISP to routed, but that's another subject entirely.
HTH,
--
Kristian Hoffmann
System Administrator
[email protected]
http://www.fire2wire.com
Office - 209-543-1800 | Fax - 209-545-1469 | Toll Free - 800-905-FIRE
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
