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)
	Sun, Mar 8, 3:16 PM

	Unknown Object (File)
	Wed, Mar 4, 11:09 PM

	Unknown Object (File)
	Tue, Mar 3, 9:52 PM

	Unknown Object (File)
	Fri, Feb 27, 5:26 AM

	Unknown Object (File)
	Thu, Feb 19, 3:25 AM

	Unknown Object (File)
	Mon, Feb 16, 4:46 PM

	Unknown Object (File)
	Jan 31 2026, 4:24 AM

	Unknown Object (File)
	Jan 31 2026, 3:56 AM

View All 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.