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, Jun 21, 5:59 PM

	Unknown Object (File)
	Wed, Jun 17, 3:22 AM

	Unknown Object (File)
	Mon, Jun 15, 5:04 AM

	Unknown Object (File)
	Sat, Jun 13, 6:41 AM

	Unknown Object (File)
	Wed, Jun 10, 6:54 PM

	Unknown Object (File)
	Wed, Jun 10, 2:04 PM

	Unknown Object (File)
	Thu, Jun 4, 6:57 PM

	Unknown Object (File)
	May 18 2026, 11:59 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.