Sorry for the spam, but I’m guessing that split horizon is basically community 
private vlans in Cisco’ese?


> On Feb 12, 2015, at 5:47 PM, Alexander Neilson <[email protected]> 
> wrote:
> 
> The horizon can be any accepted number, I think its a 32bit number.
> 
> However this will not use the switch chip. I may be wrong (as this bridge
> split horizon is generic for all mikrotiks) but I think OP wanted port
> isolate / split horizon using the switch chip.
> 
> I use 1000 as my standard horizon. And within a bridge any ports with the
> same horizon value can't communicate with each other but different numbers
> in one bridge can.
> 
> 
> Regards
> Alexander
> 
> Alexander Neilson
> Neilson Productions Limited
> 
> [email protected]
> 021 329 681
> 
> On 13 February 2015 at 11:24, Martín Ruiz <[email protected]> wrote:
> 
>> And what if you want to make 2 groups? X could be 2?3? Why 1?!
>> 
>> Martín Ruiz
>> Director técnico
>> 902 909 858 - 669379521
>> www.ibersystems.es
>> 
>>> El 12/02/2015, a las 22:59, "Shayne Lebrun" <[email protected]>
>> escribió:
>>> 
>>> Pretty simple, really:
>>> 
>>> /interface bridge add name=mybridge
>>> /interface bridge port add bridge=mybridge interface=ether1 horizon=1
>>> /interface bridge port add bridge=mybridge interface=ether2 horizon=1
>>> /interface bridge port add bridge=mybridge interface=ether3 horizon=1
>>> /interface bridge port add bridge=mybridge interface=ether4 horizon=1
>>> /interface bridge port add bridge=mybridge interface=ether5 horizon=1
>>> 
>>> Traffic from any port with horizon 'x' won't go back to any other port on
>>> that bridge with horizon 'x'.
>>> -----Original Message-----
>>> From: [email protected]
>>> [mailto:[email protected]] On Behalf Of Ty
>> Featherling
>>> Sent: Thursday, February 12, 2015 4:47 PM
>>> To: Mikrotik discussions
>>> Subject: [Mikrotik] Split-horizon on CRS125
>>> 
>>> Does anyone have a sample config that shows split-horizon setup? I would
>>> like port-isolation on my CRS125s. If it matters I have all ports in a
>>> bridge save for the upstream port. Doing some simple routing.
>>> 
>>> -Ty
>>> -------------- next part --------------
>>> An HTML attachment was scrubbed...
>>> URL:
>>> <
>> http://mail.butchevans.com/pipermail/mikrotik/attachments/20150212/ec4d41de
>>> /attachment.html>
>>> _______________________________________________
>>> Mikrotik mailing list
>>> [email protected]
>>> http://mail.butchevans.com/mailman/listinfo/mikrotik
>>> 
>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
>> RouterOS
>>> 
>>> _______________________________________________
>>> Mikrotik mailing list
>>> [email protected]
>>> http://mail.butchevans.com/mailman/listinfo/mikrotik
>>> 
>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
>> RouterOS
>> _______________________________________________
>> Mikrotik mailing list
>> [email protected]
>> http://mail.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://mail.butchevans.com/pipermail/mikrotik/attachments/20150213/078a4550/attachment.html>
> _______________________________________________
> Mikrotik mailing list
> [email protected]
> http://mail.butchevans.com/mailman/listinfo/mikrotik
> 
> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS


_______________________________________________
Mikrotik mailing list
[email protected]
http://mail.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS

Reply via email to