<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Mikrotik Noob - Gotta be missing something. in Wireless Service Providers</title>
<link>http://www.dslreports.com/forum/r23298961</link>
<description></description>
<language>en</language>
<pubDate>Wed, 10 Feb 2010 08:45:56 EDT</pubDate>
<lastBuildDate>Wed, 10 Feb 2010 08:45:56 EDT</lastBuildDate>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23313560</link>
<description><![CDATA[<A HREF="/useremail/u/1184806"><b>Inssomniak</b></A> : <div class="bquote"><small>said by  spectrumhead <A HREF="/useremail/u/1641357"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>Yes if you type just an IP address without CIDR notation it automatically does it /32 as far as I know.<br><br>Happy that you found your solution. <br> </div>Yes this is correct, assumes /32 if you dont type it on or add the network/broadcast]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23313560</guid>
<pubDate>Mon, 09 Nov 2009 09:25:47 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23313214</link>
<description><![CDATA[<A HREF="/useremail/u/1641357"><b>spectrumhead</b></A> : Yes if you type just an IP address without CIDR notation it automatically does it /32 as far as I know.<br><br>Happy that you found your solution. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23313214</guid>
<pubDate>Mon, 09 Nov 2009 07:21:38 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23303207</link>
<description><![CDATA[<A HREF="/useremail/u/673878"><b>bryandj23</b></A> : Got it!<br><br>For some reason the Mikrotik set its interfaces for /32 rather than /24.<br><br>Local part is working.   Now I just gotta get internet to respond on that interface.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23303207</guid>
<pubDate>Fri, 06 Nov 2009 16:35:46 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23301118</link>
<description><![CDATA[<A HREF="/useremail/u/673878"><b>bryandj23</b></A> : Ok, I still think my Mikrotik is the issue;  here's why.<br><br>I've made some changes to my firewall rules on pfsense.  On my lapop, I get a 192.168.200.101 address.<br><br>I plug another laptop (lap2) into the switch that is part of the 10.0.0.0/16 network.<br><br>From my laptop, I can ping lap2 which is at 10.0.0.5.   I cannot ping the Mikrotik at 10.0.0.10.<br><br>If I plug my laptop into the 10.0/16 switch, I can ping the Mikrotik.<br><br>So....is it possible that the Mikrotik is saying "Hey, I'm getting a ping request, but it's from 192.168.200.101, which isn't part of my network, so screw them".<br><br>Actually, while typing that, I'm wondering if the Mikrotik needs to know the route to the 192.168.200/24 network;  but then again, if its default route points to a gateway that contains both networks (pfsense), then pfsense should be doing it's job.<br><br>Sorry if I'm going around in circles here.   I appreciate any help or advice!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23301118</guid>
<pubDate>Fri, 06 Nov 2009 10:28:40 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23300248</link>
<description><![CDATA[<A HREF="/useremail/u/673878"><b>bryandj23</b></A> : Thanks Insommniak.   I appreciate it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23300248</guid>
<pubDate>Fri, 06 Nov 2009 06:36:19 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23299488</link>
<description><![CDATA[<A HREF="/useremail/u/1184806"><b>Inssomniak</b></A> : Hmm, Im out of suggestions, although Im sure the problem lies with the pfsense rather than the Mikrotik.  Im not familiar with it, so unless Im in front of one I cant say for sure.<br><br>Maybe its trying to NAT the traffic before it even knows where its going yet?<br><br>You could try disabling all NAT and see what happens.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23299488</guid>
<pubDate>Thu, 05 Nov 2009 23:00:19 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23299388</link>
<description><![CDATA[<A HREF="/useremail/u/673878"><b>bryandj23</b></A> : Yeah, I'm aware it's wide-open.   Since we're still in testing phase, I'm trying to get the basic networking down before going back to lock things up.<br><br>I've read a pointer regarding outbound NAT in pfsense, but I don't think that should apply as of yet, since we don't have our WAN connection installed yet (that comes tomorrow, actually), and I'm only trying to route between LAN and OPT.<br><br>I'd think that my firewall rules in pfsense (basically saying to allow anything in from LAN to OPT and vice versa would cover it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23299388</guid>
<pubDate>Thu, 05 Nov 2009 22:37:28 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23299342</link>
<description><![CDATA[<A HREF="/useremail/u/1184806"><b>Inssomniak</b></A> : <div class="bquote"><small>said by  bryandj23 <A HREF="/useremail/u/673878"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>I had thought maybe the pfsense box was causing the issue, however within its logs I see that traffic is passing from LAN to OPT, so it leaves me a bit puzzled as to where my issue REALLY is.<br><br>I may also consider just running our core "wireless" network on a router seperate from our core "office" network.   The original idea was to use one router, so that we could access AP's from the office.   Also, since some of our servers (web, radius, dns) sit on the office network, I figured this way would be easier to go.<br><br>Having them each on their own router would probably alleviate this issue, then all I'd need are static routes between the two routers.<br> </div>Well.. All I can say is a mikrotik device that is without any firewall rules is a wide open device.  If the routes exist, you can use winbox anywhere.<br><br>PF sense logs can indicate the traffic routing between the LAN and the OPT port, the further down the chain a firewall rule is dropping it?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23299342</guid>
<pubDate>Thu, 05 Nov 2009 22:27:31 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23299318</link>
<description><![CDATA[<A HREF="/useremail/u/673878"><b>bryandj23</b></A> : I had thought maybe the pfsense box was causing the issue, however within its logs I see that traffic is passing from LAN to OPT, so it leaves me a bit puzzled as to where my issue REALLY is.<br><br>I may also consider just running our core "wireless" network on a router seperate from our core "office" network.   The original idea was to use one router, so that we could access AP's from the office.   Also, since some of our servers (web, radius, dns) sit on the office network, I figured this way would be easier to go.<br><br>Having them each on their own router would probably alleviate this issue, then all I'd need are static routes between the two routers.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23299318</guid>
<pubDate>Thu, 05 Nov 2009 22:21:43 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23299277</link>
<description><![CDATA[<A HREF="/useremail/u/673878"><b>bryandj23</b></A> : Yeah.   In a sense I'd rather stick with what I know, but then again, with all the features that are available in Mikrotik, I might as well just get down and dirty with it.<br><br>That's why I think I'm missing something completely stupid;  Mikrotik is so picky (not necessarily a bad thing), where I'm probably used to things being automatically configured "behind the scenes" on other platforms, that I'm just not quite getting the Mikrotik right.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23299277</guid>
<pubDate>Thu, 05 Nov 2009 22:15:54 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23299256</link>
<description><![CDATA[<A HREF="/useremail/u/1409765"><b>livewireless</b></A> : All I can say is your in the right forum. I've had questions for support at MT and have not had any luck getting clear answers back from them. I think they've over sold and have 2 guys on support patrol.<br>I wish I'd not purchased their product even though it's solid if you want to climb the learning curve. <br>Pisses me off, I just bought a license and can't get responses from them.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23299256</guid>
<pubDate>Thu, 05 Nov 2009 22:12:52 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23299248</link>
<description><![CDATA[<A HREF="/useremail/u/1184806"><b>Inssomniak</b></A> : <div class="bquote"><small>said by  bryandj23 <A HREF="/useremail/u/673878"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>The MikroTik does has its default route set to 10.0.0.1.<br><br>Should I need to define the 192.168.200.0/24 route on the Mikrotik, even though 10.0.0.1 knows how to reach the 192.168.200.0 network (both interfaces are on the same Pfsense box)?<br> </div>I dont know much about anything about pfsense, Im thinking then a firewall between OPT and LAN?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23299248</guid>
<pubDate>Thu, 05 Nov 2009 22:11:12 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23299191</link>
<description><![CDATA[<A HREF="/useremail/u/673878"><b>bryandj23</b></A> : The MikroTik does has its default route set to 10.0.0.1.<br><br>Should I need to define the 192.168.200.0/24 route on the Mikrotik, even though 10.0.0.1 knows how to reach the 192.168.200.0 network (both interfaces are on the same Pfsense box)?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23299191</guid>
<pubDate>Thu, 05 Nov 2009 22:01:01 EDT</pubDate>
</item>

<item>
<title>Re: Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23299047</link>
<description><![CDATA[<A HREF="/useremail/u/1184806"><b>Inssomniak</b></A> : Probably silly question<br><br>But is the default gateway configured properly on the Mikrotik and your 192.168 network?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23299047</guid>
<pubDate>Thu, 05 Nov 2009 21:34:28 EDT</pubDate>
</item>

<item>
<title>Mikrotik Noob - Gotta be missing something.</title>
<link>http://www.dslreports.com/forum/remark,23298961</link>
<description><![CDATA[<A HREF="/useremail/u/673878"><b>bryandj23</b></A> : Hi all.  I'm getting things set up for a new wisp venture, and I've reached a point where I'm stumped, and I believe Mikrotik is to blame (or my lack of Mikrotik knowledge).  Here's my setup:<br><br>(Internet)<br>    |<br>    |<br>Pfsense -- Lan -- 192.168.200.1/24 - Office  LAN<br>     |<br>    OPT<br>     |----10.0.0.1/16 --- switch --- laptop (10.0.0.35)<br>                                    |<br>                                 mikrotik 10.0.0.10<br><br>The laptop also contains a wireless card, which is getting a 192.168.200.101 address via AP connected to LAN.<br><br>I've configured rules in PFsense to allow anything back and forth between LAN and OPT.<br><br>Now, the laptop can ping anything along 192.168.200.0/24, using either wired (10.0.0.35) or wireless (192.168).  It CANNOT ping the mikrotik at 10.0.0.10.<br><br>Using winbox, I can ping 10.0.0.1 from the mikrotik, but CANNOT ping anything along 192.168.200.0/24.  The fact that I can ping either pfsense interface on the laptop via either subnet makes me believe its something in the tik.<br><br>Add to this:  Can't access Mikrotik (via ping or winbox) on the laptop when the laptop is connected wireless and has a 192.168.200.0/24 address.   Once I hard wire the laptop to the switch, and give myself a 10.0.0.35 address, it works like a charm.<br><br>could something in mikrotik be preventing me from ping and winbox from a network outside of the mikrotik's eth interface??<br><br>Thanks much in advance!<br><br>PS:  Funny part - pfsense logs show that pings are going through from LAN to OPT...after playing with it for two hours, I figured I needed a break]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23298961</guid>
<pubDate>Thu, 05 Nov 2009 21:22:47 EDT</pubDate>
</item>

</channel>
</rss>
