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, Nov 3, 2:11 AM

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

	Unknown Object (File)
	Oct 15 2024, 9:48 PM

	Unknown Object (File)
	Oct 3 2024, 12:10 AM

	Unknown Object (File)
	Oct 2 2024, 8:23 PM

	Unknown Object (File)
	Oct 2 2024, 8:25 AM

	Unknown Object (File)
	Sep 30 2024, 11:44 AM

	Unknown Object (File)
	Sep 17 2024, 3:51 PM

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