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 Juni
I don't know about terminating VLANs but I have set up a bandwidth
shaper in bridge mode that handles several VLANs, including VLAN 1 on
two NICs (Internal / External)
On 6/17/11 11:39 AM, Jacob Heider wrote:
I wouldn't ask this, if I hadn't been burned by Juniper on this very
issue. Anyone ab
No, ROS will not support untagged and tagged on the same layer 3 interface.
--
Blake Covarrubias
On Jun 17, 2011, at 9:39 AM, 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
Works fine for me. Got several instances where vlan 1 is untagged and also
have tagged vlans on the same physical interface.
Eric
On Jun 17, 2011 1:06 PM, "Blake Covarrubias" wrote:
> No, ROS will not support untagged and tagged on the same layer 3
interface.
>
> --
> Blake Covarrubias
>
> On Jun
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
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
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-i
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;
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)
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
2nding what Andrew has said here, using bridges etc allows tagged/untagged
vlans to be used on same ports.
I believe the newly introduced switch config sections may allow more
in-depth vlan setups however I can't say I've had time to explore this and
have just worked with the tried and tested for
In my experience, you can't bridge the untagged interface on a MikroTik
if you have VLAN interfaces on that same interface. For example...
/in br add name=test
/in br port add bridge=test interface=ether1
/in vlan add interface=ether1 vlan-id=10 disabled=no name=ether1.10
In this example, ether1
12 matches
Mail list logo
