+1.

My thoughts exactly. A bridged port is slaved in a sense, but I would want to distinguish a switched port from a bridged port. Because when I see the S, my mind says <S>witched, even though MT thinks of it as <S>lave. Make the bridged ports <B>ridged.

... and maybe make the switch master <M>aster?


bp

On 2/3/2014 10:46 AM, Paul McCall wrote:
+1 on the distinctive letter .... thinking a "B" for bridge?  Naaah... that 
would make too much sense
:)

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Grand Avenue 
Broadband
Sent: Monday, February 03, 2014 12:53 PM
To: Mikrotik discussions
Subject: Re: [Mikrotik] Bridge Ports showing with an S on version 6.7

I assume it was to remind you they were bridged, so you don't try to do the 
wrong stuff with the individual interfaces, like hang addresses on them, or do 
DHCP to them (although I understand that in 6.8 you can now do that).  Would 
have been nice, though, if they had used a distinct letter.

On Feb 3, 2014, at 10:50 AM, Ty Featherling <[email protected]> wrote:

Yeah but why? Some updated functionality of bridge involving the
switch chip?

-Ty
On Feb 3, 2014 11:24 AM, "Justin Miller" <[email protected]> wrote:

It's normal in 6. It's a new feature. A port in a bridge will have a
S now on all devices.


On Feb 3, 2014, at 10:38 AM, Paul McCall <[email protected]> wrote:

First time using 6.x.   running it on a Cloud Switch router

I created a bridge for all our APs

I noticed that when I add an interface to the bridge, it adds an "S"
(for slave) in the interface.   Normally, I would expect that if I told it
some other interface was its master, but that is not the case.   Not all
ports show S... just the ones I bridged.
Is this a 6.7 thing, a Could switch thing ?

Is there a command to "fix that" ?

Paul

Paul McCall, Pres.
PDMNet / Florida Broadband
658 Old Dixie Highway
Vero Beach, FL 32962
772-564-6800 office
772-473-0352 cell
www.pdmnet.com<http://www.pdmnet.com/>
[email protected]<mailto:[email protected]>

-------------- next part -------------- An HTML attachment was
scrubbed...
URL: <
http://mail.butchevans.com/pipermail/mikrotik/attachments/20140203/77
6e5932/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

-------------- next part -------------- An HTML attachment was
scrubbed...
URL:
<http://mail.butchevans.com/pipermail/mikrotik/attachments/20140203/5a
b05ed7/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


_______________________________________________
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