I have many in use as plain switches. They have vlan support. I would really use a router in your case. Hotspot will work past it just fine.
On Sun, Jan 30, 2011 at 1:07 PM, Stuart Pierce <spie...@avolve.net> wrote: > > Which brings me to my original thought of using a Mikrotik Switch with SWos, > but I have never used one or looked into it's capabilities. Does the Mikrotik > SWos have these types of capabilities ? > > ---------- Original Message ---------------------------------- > From: Jeromie Reeves <jree...@18-30chat.net> > Reply-To: Mikrotik discussions <mikrotik@mail.butchevans.com> > Date: Sun, 30 Jan 2011 09:45:04 -0800 > >>Place a router or a vlan capable switch between the two networks. It >>will be the only way to do it. the hotspot will trigger on any >>mac address it sees and respond by trying to capture it. You could >>spend time to manual add each mac for the other network but >>that really is not going to work well (enough) for a production network. >> >>On Sun, Jan 30, 2011 at 5:43 AM, Stuart Pierce <spie...@avolve.net> wrote: >>> Actually WISP2 isn't a wisp but has AP's in the air and we want to use the >>> WISP2's locations and equipment. They all have static and do VPN to their >>> headend with a certain 192.168.x.x network range. So we can join the >>> wireless networks together in one building and extend the range/area/reach >>> of WISP1. >>> >>> SO I was thinking maybe there could be a firewall rule that says ignore >>> WISP2's ip address range. >>> >>> ---------- Original Message ---------------------------------- >>> From: Butch Evans <but...@butchevans.com> >>> Reply-To: Mikrotik discussions <mikrotik@mail.butchevans.com> >>> Date: Sun, 30 Jan 2011 01:19:45 -0600 >>> >>>>On 01/28/2011 07:18 AM, Stuart Pierce wrote: >>>>> Wish I had a quick dirt drawing program. >>>>> >>>>> Let's say there are two WISP's, two different networks and they just >>>>> happen to have a connection in the same building two both their separate >>>>> networks. >>>>> >>>>> WISP 1 uses a DSL connection ( not that it matters ) and a Mikrotik box >>>>> for their router and such for their WISP. >>>>> >>>>> WISP 2 uses cable connection and static ip's doing VPN's to their Cisco >>>>> router for their WISP. >>>>> >>>>> In the room where they both have a connection to each of their networks, >>>>> where the room happens to be in WISP 2's building ( not that it should >>>>> matter ), we put a switch in and connect both WISP's together. >>>>> >>>>> Creating one big WISP out of two. >>>>> >>>>> The thinking was that since WISP 2's network was utilizing VPN's that the >>>>> Mikrotik box wouldn't see it's traffic and go on it's merry way and still >>>>> go out it's original gateway. Even though knowing that more network >>>>> traffic would traverse both WISP from each other's networks. >>>>> >>>>> But yes, the Mikrotik hotspot sees the VPN traffic evidently and >>>>> interrupts WISP 2's network. >>>>> >>>>> So the switch was obviously taken out of the equation to allow WISP 2's >>>>> network to function properly again. >>>>> >>>>> So the question is, is there a way to do this, either by setting up a >>>>> firewall rule in the Mikrotik box to drop WISP 2's ip network at either >>>>> http unauth, pre hs input or input. Maybe even putting in a Mikrotik >>>>> switch to tag packets with WISP 2's ip network and pass them to the port >>>>> to their network. >>>>> >>>>> There has got to be a way. >>>>> >>>>Hotspot will break a LOT of things. In this scenario, the hotspot will >>>>break wisp 2 network because it will (essentially) poison the arp tables >>>>of the other clients. I guess the question is, why would you want to >>>>connect the 2 networks? Perhaps understanding that will lead us to a >>>>solution that will work for you. >>>> >>>>-- >>>>******************************************************************** >>>>* Butch Evans * Professional Network Consultation* >>>>* http://www.butchevans.com/ * Network Engineering * >>>>* http://store.wispgear.net/ * Wired or Wireless Networks * >>>>* http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * >>>>* NOTE THE NEW PHONE NUMBER: 702-537-0979 * >>>>******************************************************************** >>>> >>>>_______________________________________________ >>>>Mikrotik mailing list >>>>Mikrotik@mail.butchevans.com >>>>http://www.butchevans.com/mailman/listinfo/mikrotik >>>> >>>>Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS >>>> >>> >>> >>> >>> >>> >>> ________________________________________________________________ >>> Sent via the WebMail system at avolve.net >>> >>> >>> >>> >>> _______________________________________________ >>> Mikrotik mailing list >>> Mikrotik@mail.butchevans.com >>> http://www.butchevans.com/mailman/listinfo/mikrotik >>> >>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS >>> >>_______________________________________________ >>Mikrotik mailing list >>Mikrotik@mail.butchevans.com >>http://www.butchevans.com/mailman/listinfo/mikrotik >> >>Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS >> > > > > > > ________________________________________________________________ > Sent via the WebMail system at avolve.net > > > > > > _______________________________________________ > Mikrotik mailing list > Mikrotik@mail.butchevans.com > http://www.butchevans.com/mailman/listinfo/mikrotik > > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS > _______________________________________________ Mikrotik mailing list Mikrotik@mail.butchevans.com http://www.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
