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)
	Sat, Jan 31, 4:24 AM

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

	Unknown Object (File)
	Fri, Jan 30, 8:53 PM

	Unknown Object (File)
	Tue, Jan 27, 10:27 PM

	Unknown Object (File)
	Wed, Jan 21, 10:31 AM

	Unknown Object (File)
	Tue, Jan 20, 8:35 PM

	Unknown Object (File)
	Mon, Jan 19, 7:08 AM

	Unknown Object (File)
	Jan 9 2026, 8:42 PM

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.