Allow vlan interfaces to rx through netmap(4)
ClosedPublic
Actions

Authored by mjoras on Aug 31 2017, 9:35 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Mon, Dec 9, 6:13 AM

	Unknown Object (File)
	Thu, Dec 5, 3:39 PM

	Unknown Object (File)
	Thu, Nov 28, 4:42 PM

	Unknown Object (File)
	Nov 17 2024, 4:52 AM

	Unknown Object (File)
	Nov 17 2024, 4:48 AM

	Unknown Object (File)
	Nov 17 2024, 2:39 AM

	Unknown Object (File)
	Nov 3 2024, 2:11 AM

	Unknown Object (File)
	Oct 28 2024, 4:36 PM

View All 68 Files

Subscribers

imp

Details

Reviewers

rstone

Group Reviewers

network

Commits

rS323513: Allow vlan interfaces to rx through netmap(4).

Summary

Normally after receiving a packet, a vlan(4) interface sends the packet
back through its parent interface's rx routine so that it can be
processed as an untagged frame. It does this by using the parent's
ifp->if_input. This is incompatible with netmap(4), which replaces the
vlan(4) interface's if_input with a netmap(4) hook. Fix this by using
the vlan(4) interface's ifp instead of the parent's directly.