Not doubting you however I cant ping these addys and I have tried unsuccessfully to utilize these IPs as a test. Either way, what do you suggest putting on my MT router to block the RFC1918 addys?
On Wed, Dec 17, 2014 at 5:59 PM, Justin Miller <[email protected]> wrote: > > Unless you put something in your network not to route rfc1918 space -it > will route. There is nothing technical that prevents it from routing. > > You should drop rfc1918 space exiting out of the wan of any device that > has that space behind it if you are NATing. You should drop it out your > edge as well to your upstream (only allow your prefixes/peer ips out). > I've actually pinged something I shouldn't have been able to ping wondering > wth and then doing a trace to find that my upstream was not dropping 1918. > Was a tier 2 east cost provider. > > *Justin Miller* > > VA SkyWire, LLC > 1707 E Main St > Richmond, VA 23223 > Office: (804) 521-4212 > Desk: (804) 591-0500 ext 101 <(804)%20591-0500;101> > Fax: (804) 591-1559 > [email protected] > > The information contained in this electronic message from VA SkyWire, LLC > is privileged, confidential, or otherwise protected from disclosure. It is > intended only for the use of the individual or entity named above. If you > are the intended recipient of this message, you are hereby notified that > you may not forward, distribute, copy or disclose the contents of this > email without notifying the sender of this email. If you are not the named > addressee, then any disclosure, copying, publication, distribution, or > other use of the contents of this electronic message is strictly > prohibited.. If you have received this communication in error, please > notify Scott Coonfield at (804) 521-4212 or by return e-mail to > [email protected], and purge the communication immediately without > making any copy or distribution. Thank You. > > On Dec 17, 2014, at 5:06 PM, RickG <[email protected]> wrote: > > Hey folks! I'm running Butch's QOS & Firewall. I noticed an several > 192.168.1.x IP addresses being caught by the SPAM filter (see attached > screen captures). I'm not routing that subnet. Any ideas how it getting > through to the firewall? > > -RickG KyWiFi > > <Image1.jpg> > > <Image2.jpg> > > _______________________________________________ > Mikrotik-users mailing list > [email protected] > http://lists.wispa.org/mailman/listinfo/mikrotik-users > > > _______________________________________________ > Mikrotik-users mailing list > [email protected] > http://lists.wispa.org/mailman/listinfo/mikrotik-users > > -- -RickG KyWiFi
_______________________________________________ Mikrotik-users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/mikrotik-users
