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, Apr 7, 8:56 AM

	Unknown Object (File)
	Sat, Mar 30, 11:34 PM

	Unknown Object (File)
	Feb 9 2024, 4:53 AM

	Unknown Object (File)
	Feb 8 2024, 5:02 PM

	Unknown Object (File)
	Jan 28 2024, 10:07 AM

	Unknown Object (File)
	Jan 2 2024, 8:03 PM

	Unknown Object (File)
	Dec 20 2023, 4:38 AM

	Unknown Object (File)
	Dec 20 2023, 4:05 AM

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