Community discussions

Search found 11 matches

by janel
Tue Jul 01, 2014 3:27 am
Forum: General
Topic: CRS documentation
Replies: 79
Views: 30310

Re: CRS documentation

Hello,

Just wanted to report that with 6.15 CRS becomes perfectly useable.
Thanks for your efforts!
by janel
Tue Jul 01, 2014 3:24 am
Forum: General
Topic: v6.15 released
Replies: 302
Views: 103918

Re: v6.15 released

CPU load in 6.15 vs 6.11 on a CRS125-24G-1S mk-cpuload.png /system resource pr uptime: 18m53s version: 6.15 build-time: Jun/12/2014 12:25:29 free-memory: 107.9MiB total-memory: 128.0MiB cpu: MIPS 74Kc V4.12 cpu-count: 1 cpu-frequency: 600MHz cpu-load: 11% free-hdd-space: 109.6MiB total-hdd-space: 12...
by janel
Sun May 11, 2014 11:53 pm
Forum: General
Topic: v6.12 released
Replies: 237
Views: 57870

Re: v6.12 released

same problem here, steen. Downgrade to the previous version worked for me.
by janel
Sat Apr 19, 2014 9:40 pm
Forum: General
Topic: v6.12 released
Replies: 237
Views: 57870

Re: v6.12 released

I've tried this a few times today with 6.12 and it's not just print in the interface section that will cause it to lock up, exporting config also causes the device to hard lock up. Should add I started with a clean configuration and then applied the config bit by bit, the entire config was accepted...
by janel
Sun Mar 30, 2014 2:38 am
Forum: General
Topic: CRS documentation
Replies: 79
Views: 30310

Re: CRS documentation

Agreed. But in the current CRS documentation the tagging/untagging is just a basic process of VLAN translation: - Trunk port VID xxx mapped to Access port VID 0 - Access port VID 0 mapped to trunk port VID xxx That allows all other tagged VIDs to be copied on the access port, and I think that's not ...
by janel
Wed Mar 26, 2014 6:03 pm
Forum: General
Topic: CRS documentation
Replies: 79
Views: 30310

Re: CRS documentation

Yeah, that was my discovery too - Trunk is leaking somehow, like I said, if you disconnect the trunk the problem isnt there (no vlan <-> vlan leak on same CRS). I've tried changing all kind of parameters, and no go. I guess that is due to the fact that the proposed approach is not a real VLAN encap...
by janel
Wed Mar 26, 2014 1:40 pm
Forum: General
Topic: CRS documentation
Replies: 79
Views: 30310

Re: CRS documentation

@trn76: using the same tutorial I have discovered that the access ports are still receiving tagged traffic from the trunk port. You can verify that for yourself by running a tcpdump -n e i enX on the "access" port, you will be able to see the VLAN IDs affected as well. I think that the approach desc...
by janel
Sat Mar 22, 2014 1:18 am
Forum: General
Topic: CRS documentation
Replies: 79
Views: 30310

Re: CRS documentation

@timberwolf: I totally agree with you, it is not al true L3 switch, but however, some nice examples about L3 inter-VLAN routing would help. I have managed to do it myself, but I guess that others may find this very helpful, especially if we consider that this new switch chip is rather different from...
by janel
Fri Mar 14, 2014 1:37 am
Forum: General
Topic: Known issues and bugs - a list
Replies: 283
Views: 111683

Re: Known issues and bugs - a list

Issue: CRS125-24G-1S-RM: Configuration elements missing from the Web interface: Switch and LCD Description: Switch setting bridge-type=customer-vlan-bridge is not retained after reboot. In my case this causes traffic to be copied on all ports linked to the current master, as described before by oth...
by janel
Wed Mar 12, 2014 10:58 pm
Forum: General
Topic: Known issues and bugs - a list
Replies: 283
Views: 111683

Re: Known issues and bugs - a list

Issue:
CRS125-24G-1S-RM: Configuration elements missing from the Web interface: Switch and LCD

Description:
The configuration sections for the Switch and LCD are missing from the Web interface, but present in the CLI and Winbox.

Versions affected:
6.10

How to reproduce:
Always
by janel
Wed Mar 12, 2014 10:48 pm
Forum: General
Topic: CRS documentation
Replies: 79
Views: 30310

Re: CRS documentation

Hello,

I just would like some more configuration examples such as a basic L3 switch with inter-VLAN routing. The way how a VLAN interface interacts with the switch is pretty unclear for me.

Thanks!