Alright, I feel better then. That coincides with my experience.
On 2011-06-17 7:25 PM, Andrew Thrift wrote:
Ok, after a bit of digging.
SRX and J series do not support "Flexible Vlan Tagging" meaning you
cannot have an untagged "native" vlan... EX, MX do support this.
We have replaced all of our J series with Mikrotik's and any SRX's we
sold have been replaced with FortiGates (hence my poor memory)
Mikrotik does support this, there is no "native" vlan as such, but if
you need to translate to another tag you can use bridges to do so.
Vlan support in mikrotik is quite flexible, but not as logical as it
could be.
On 18/06/2011 11:15 a.m., Andrew Thrift wrote:
I should mention that was off EX, i'll fish out a J-Series config.
On 18/06/2011 11:13 a.m., Andrew Thrift wrote:
Yes I am certain.
Config format is:
ge-0/1/0 {
description "L2 Aggregation";
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members [ Voice Management ];
}
native-vlan-id default;
}
}
}
On 18/06/2011 10:49 a.m., Jacob Heider wrote:
Are you sure about that, Andrew? I went back and forth with JTAC
and they told me definitively that their OS didn't support it,
which certainly bore out what I was seeing. I was forced to use two
connections from my router to my switch, one for VLAN 1, and one
for the "tagged" traffic. This was on J-series routers (J2320s).
On 2011-06-17 6:40 PM, Andrew Thrift wrote:
JunOS devices can do this, I have a large number of clients
running these configurations. Juniper J Series, EX, MX and SRX
devices.
On 18/06/2011 4:39 a.m., Jacob Heider wrote:
I wouldn't ask this, if I hadn't been burned by Juniper on this
very issue. Anyone able to state definitively if RouterOS will
support both vlan 1 ("untagged") and higher number ("tagged")
traffic on the same interface? Cisco devices could care less, but
for some reason, fully confirmed by Juniper support, you can only
have either tagged or untagged traffic on a given interface. I
would assume ROS doesn't have this limitation, but I figured it
was worth asking before I jump into provisioning this.
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
