Date: Mon, 20 Apr 2015 17:35:13 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Petko Bordjukov <bordjukov@gmail.com> Cc: "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: Control over the RSTP functionality of the AR8327 switch engine Message-ID: <CAJ-VmonezF2KGu00eUzKJn9ODRiR_DoMRF9Jy4chpeYHCPcXOQ@mail.gmail.com> In-Reply-To: <1429576261.20150.31.camel@gmail.com> References: <1429572177.20150.28.camel@gmail.com> <CAJ-VmokzcNSLzBSy2v2KQU1oVENM9nautcAwviaRDMO7ZdmztQ@mail.gmail.com> <CAAgmp6ucYsXVh=1nL=yoCCObpA-4OXmFVT4bAjGqp_U%2Bpj2eTQ@mail.gmail.com> <CAJ-Vmo==Vf-9U0znnO9P=uPBwTRh-yA2cvFuU_rR-L0KWFcxZw@mail.gmail.com> <1429576261.20150.31.camel@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Oh. So, I think the point here is that you can control the port STP mode (blocked, learning, active, etc) - you then glue that into the existing bridge code in software that's speaking STP. I don't know if the AR8327 speaks STP/RSTP itself. I know it manages its own learning. -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonezF2KGu00eUzKJn9ODRiR_DoMRF9Jy4chpeYHCPcXOQ>