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)
	Fri, Jun 14, 6:59 AM

	Unknown Object (File)
	Tue, Jun 4, 10:36 AM

	Unknown Object (File)
	Tue, May 28, 5:28 PM

	Unknown Object (File)
	Tue, May 21, 10:38 AM

	Unknown Object (File)
	May 9 2024, 8:13 AM

	Unknown Object (File)
	May 6 2024, 10:02 AM

	Unknown Object (File)
	May 1 2024, 5:58 PM

	Unknown Object (File)
	Apr 27 2024, 6:27 PM

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