STP works fine on etherip(4), it was gif(4) that lacked a MAC address.

getting etherip(4) to talk to a switch so i could verify this was
pretty fun.

remi@ pointed this bit of the manpage out somewhere, but it didn't
seem right anymore since etherip(4) was split out of gif(4). these
days if we have an interface that can be added to a bridge, we try
to make it look like an actual ethernet interface, which includes
having a mac address. we don't really have interfaces that change
modes and have these edge cases anymore.

1 files changed, 2 insertions, 5 deletions

diff --git a/share/man/man4/bridge.4 b/share/man/man4/bridge.4
index fa8f411b135..c288f7f8ecd 100644
--- a/share/man/man4/bridge.4
+++ b/share/man/man4/bridge.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: bridge.4,v 1.77 2019/05/10 18:27:50 akoshibe Exp $
+.\"	$OpenBSD: bridge.4,v 1.78 2019/08/16 01:55:21 dlg Exp $
 .\"
 .\" Copyright (c) 1999-2001 Jason L. Wright (jason@thought.net)
 .\" All rights reserved.
@@ -24,7 +24,7 @@
 .\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: May 10 2019 $
+.Dd $Mdocdate: August 16 2019 $
 .Dt BRIDGE 4
 .Os
 .Sh NAME
@@ -121,9 +121,6 @@ can be used to force operation in the common Spanning Tree Protocol
 without rapid state transitions.
 Note that RSTP will be compatible with remote bridges running common STP.
 .Pp
-STP will not work on
-.Xr etherip 4
-members because they lack a hardware MAC address.
 .Sh SPAN PORTS
 The bridge can have interfaces added to it as span ports.
 Span ports transmit a copy of every frame received by the bridge.