Page MenuHomeFreeBSD

netgraph/ng_bridge: Derive forwarding mode from first attached hook
ClosedPublic

Authored by donner on Feb 5 2021, 8:07 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Oct 24, 7:03 AM
Unknown Object (File)
Wed, Oct 23, 9:57 PM
Unknown Object (File)
Mon, Oct 21, 8:11 PM
Unknown Object (File)
Sep 29 2024, 1:07 PM
Unknown Object (File)
Sep 28 2024, 6:52 AM
Unknown Object (File)
Sep 27 2024, 2:56 PM
Unknown Object (File)
Sep 27 2024, 10:10 AM
Unknown Object (File)
Sep 27 2024, 3:26 AM
Subscribers

Details

Summary

Handling of unknown MACs on an bridge with incomplete learning
capabilites (aka uplink ports) can be defined in different ways.

The classical approach is to broadcast unicast frames send to an
unknown MAC, because the unknown devices can be everywhere. This mode
is default for ng_bridge(4).

In the case of dedicated uplink ports, which prohibit learning of MAC
addresses in order to save memory and CPU cycles, the broadcast
approach is dangerous. All traffic to the uplink port is broadcasted
to every downlink port, too. In this case, it's better to restrict the
distribution of frames to unknown MAC to the uplink ports only.

In order to keep the chance small and the handling as natural as
possible, the first attached link is used to determine the behaviour
of the bridge: If it is an "uplink" port, then the bridge switch from
classical mode to restricted mode.

Depends On: D23963

Test Plan

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

donner requested review of this revision.Feb 5 2021, 8:07 AM
  • rebased after landing parent
  • Switch to the new man page macros
  • rebased after landing man page modifications

Approved by: kp (mentor)

This revision is now accepted and ready to land.Feb 6 2021, 12:52 PM