1. 16
  1.  

  2. 1

    I played with bridge in the past. It’s basically a software-defined ethernet cable.

    1. 1

      With the caveat that I haven’t dealt with the OpenBSD feature in question here (only what I think is the corresponding Linux functionality), isn’t it more like a software-defined ethernet switch?

      1. 1

        Indeed. However, hub is even closer:

        This link between the interfaces selectively forwards frames from each interface on the bridge to every other interface on the bridge.

        This would be a “cable”: https://man.openbsd.org/pair.4

        1.  

          Hmm, now I’m confused…

          veb(4) states:

          veb is a learning bridge that maintains a table of Ethernet addresses and the port that each address is reachable with.

          bridge(4) says:

          In general a bridge works like a hub, forwarding traffic from one interface to another. It differs from a hub in that it will “learn” which machines are on each of its attached segments by actively listening to incoming traffic and examining the headers of each frame. A table is built containing the MAC address and segment to which the MAC address is attached.

          I thought having a forwarding database and learning mac/port associations (and using it for selective forwarding) was the main thing differentiating a switch from a hub?