I like that one! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
On Fri, Jan 28, 2011 at 10:19 AM, Terri Kelley <net...@farm-market.net>wrote: > Network Notepad > > Terri > > > > > On Jan 28, 2011, at 9:17 AM, Josh Luthman wrote: > > > Pen & paper works. Dia works and is free. > > > > Visio is out there... > > > > Josh Luthman > > Office: 937-552-2340 > > Direct: 937-552-2343 > > 1100 Wayne St > > Suite 1337 > > Troy, OH 45373 > > > > > > On Fri, Jan 28, 2011 at 8:18 AM, Stuart Pierce <spie...@avolve.net> > 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. > >> > >> ---------- Original Message ---------------------------------- > >> From: Jeromie Reeves <jree...@18-30chat.net> > >> Reply-To: Mikrotik discussions <mikrotik@mail.butchevans.com> > >> Date: Thu, 27 Jan 2011 20:01:20 -0800 > >> > >>> If I read the network map correctly, you have a Switch (A) with 2 > >>> routers and 2 wireless access points, and the MT is snagging one it > >>> should not, Correct? > >>> > >>> > >>> On Thu, Jan 27, 2011 at 4:47 PM, Stuart Pierce <spie...@avolve.net> > >> wrote: > >>>> Well they have routers, but both networks ( 10.5.50.x & 192.168.x.x ) > >> will run over the bridged wireless network. So there really is two > wireless > >> networks in the air, put a switch in the middle and the wireless > networks > >> will see each others traffic. > >>>> > >>>> But when both wireless networks are connected through the switch, the > >> non-Mikrotik network gets captured by the Mikrotik box. Even though the > >> 192.168.x.x network is vpn from client to router, encapsulated. > >>>> > >>>> Actually do binding for devices in the dhcp server, I just want the > >> hotspot to ignore and 192.168.x.x ip address traffic at all and go about > >> it's original path. > >>>> > >>>> ---------- Original Message ---------------------------------- > >>>> From: Josh Luthman <j...@imaginenetworksllc.com> > >>>> Reply-To: Mikrotik discussions <mikrotik@mail.butchevans.com> > >>>> Date: Thu, 27 Jan 2011 19:12:34 -0500 > >>>> > >>>>> It looks like both Wan interfaces have privates? Weird. > >>>>> > >>>>> If you have a mt hotspot you can do a binding for an entire range of > IPs > >> if > >>>>> that helps. I know I'm still confused on what devices and subnets > >> there > >>>>> are. > >>>>> On Jan 27, 2011 7:08 PM, "Scott Reed" <sr...@nwwnet.net> wrote: > >>>>>> I am still confused. How are you getting 192.168.x.x addresses on > the > >>>>>> TW Internet? > >>>>>> > >>>>>> On 1/27/2011 6:19 PM, Stuart Pierce wrote: > >>>>>>> Ok > >>>>>>> > >>>>>>> Network 1 - 10.5.50.x > >>>>>>> V > >>>>>>> Frontier DSL Internet > >>>>>>> V > >>>>>>> Mikrotik hotspot > >>>>>>> V > >>>>>>> wireless network/cloud > >>>>>>> V > >>>>>>> Netgear Switch > >>>>>>> V > >>>>>>> wireless network/cloud > >>>>>>> ^ > >>>>>>> Cisco VPN > >>>>>>> ^ > >>>>>>> Time Warner Internet > >>>>>>> ^ > >>>>>>> Network 2 - 192.168.x.x > >>>>>>> > >>>>>>> If you took out the Netgear switch the two networks wouldn't see > each > >>>>> other. Network 2 is supposedly all VPN. We put both networks in the > >> switch > >>>>> and Network 2 clients ( all of them I suppose ) start to get the > >> Mikrotik > >>>>> hotspot login or are captured by the mikrotik box. > >>>>>>> > >>>>>>> I was really hoping that network 2 being vpn based wouldn't be > >> captured > >>>>> by the mikrotik hotspot. So I was thinking of a firewall rule to tell > >> the > >>>>> mikrotik box to just disregard any network of 192.168.x.x > >>>>>>> > >>>>>>> ---------- Original Message ---------------------------------- > >>>>>>> From: Josh Luthman<j...@imaginenetworksllc.com> > >>>>>>> Reply-To: Mikrotik discussions<mikrotik@mail.butchevans.com> > >>>>>>> Date: Thu, 27 Jan 2011 16:21:13 -0500 > >>>>>>> > >>>>>>>> I know I'm really lost and I would need to see a much better > network > >>>>>>>> diagram. > >>>>>>>> > >>>>>>>> Josh Luthman > >>>>>>>> Office: 937-552-2340 > >>>>>>>> Direct: 937-552-2343 > >>>>>>>> 1100 Wayne St > >>>>>>>> Suite 1337 > >>>>>>>> Troy, OH 45373 > >>>>>>>> > >>>>>>>> > >>>>>>>> On Thu, Jan 27, 2011 at 3:57 PM, Stuart Pierce<spie...@avolve.net > > > >>>>> wrote: > >>>>>>>> > >>>>>>>>> Got this situation: > >>>>>>>>> > >>>>>>>>> Network 1 Network 2 > >>>>>>>>> Internet tik-hotspot - wireless - vpn-network - Internet > >>>>>>>>> > >>>>>>>>> Network 1 is the usual 10.5.50.x > >>>>>>>>> Network 2 is 192.168.x.x > >>>>>>>>> > >>>>>>>>> Want to run both networks on the same equipment at the wireless > >>>>> juncture, > >>>>>>>>> each having their own gateways. Thinking the VPN network would > not > >> be > >>>>>>>>> captured by the tik-hotspot once the join is complete at the > switch > >> at > >>>>> the > >>>>>>>>> wireless juncture, but the VPN network is captured by the > >> tik-hotspot. > >>>>>>>>> > >>>>>>>>> Is there a way to make this work by telling the tik-hotspot to > >>>>> disregard > >>>>>>>>> any traffic from the 192.168.x.x network so that that network > just > >>>>> flows to > >>>>>>>>> it's original intended gateway ? > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> ________________________________________________________________ > >>>>>>>>> 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 > >>>>>>>>> > >>>>>>>> -------------- next part -------------- > >>>>>>>> An HTML attachment was scrubbed... > >>>>>>>> URL:< > >>>>> > >> > http://www.butchevans.com/pipermail/mikrotik/attachments/20110127/c8eb441e/attachment.html > >>>>>> > >>>>>>>> _______________________________________________ > >>>>>>>> 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 > >>>>>>> > >>>>>> > >>>>>> -- > >>>>>> Scott Reed > >>>>>> Owner > >>>>>> NewWays Networking, LLC > >>>>>> Wireless Networking > >>>>>> Network Design, Installation and Administration > >>>>>> Mikrotik Advanced Certified > >>>>>> www.nwwnet.net > >>>>>> (765) 855-1060 > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> 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 > >>>>> -------------- next part -------------- > >>>>> An HTML attachment was scrubbed... > >>>>> URL: < > >> > http://www.butchevans.com/pipermail/mikrotik/attachments/20110127/29775fbc/attachment.html > >>> > >>>>> _______________________________________________ > >>>>> 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 > >> > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: < > http://www.butchevans.com/pipermail/mikrotik/attachments/20110128/0c4a4d38/attachment.html > > > > _______________________________________________ > > 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 > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://www.butchevans.com/pipermail/mikrotik/attachments/20110128/afddabed/attachment.html > > > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.butchevans.com/pipermail/mikrotik/attachments/20110128/09a03daf/attachment.html> _______________________________________________ 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
