Redirect packets into kernel protocol stack

[dungru]

For Driver modify: Enqueue the tx packet to the oppsite interface's rx_queue. For testing Script:

1. Create two stations interfaces and connect to AP.
2. Create two network namespace sta0/sta1
3. Create two macvlan interfaces macvlan0/macvlan1
4. Assign owl0/owl1 to macvlan
5. Assign two macvlan to different namespace sta0/sta1

[dungru]

Append the high level descriptions in README.md

My new idea is creating two network interfaces owl0 and owl1. owl0 bind with wifi stations(wiphy). owl1 is a fake AP net device. 'owl1' does not bind with any wiphy. The purpose of owl1 is redirecting the protocol packet to the kernel network stack.

Is it better to change owl1 interface name to ap0?

[jserv]

My new idea is creating two network interfaces owl0 and owl1. owl0 bind with wifi stations(wiphy). owl1 is a fake AP net device. 'owl1' does not bind with any wiphy. The purpose of owl1 is redirecting the protocol packet to the kernel network stack. Is it better to change owl1 interface name to ap0?

ap0 is ambiguous. Don't use that. According to your proposal, the new device owl1 sounds like something referring to current source and sink. Thus, we might create owl0 and its sink device node owl0sink, which distinguishes with each other.

[jserv]

@rickywu0421, Can you install multipass and attempt to run the proposed changes in a virtualized environment with make check to see if vwifi works as expected?

[rickywu0421]

@rickywu0421, Can you install multipass and attempt to run the proposed changes in a virtualized environment with make check to see if vwifi works as expected?

Machine launched by multipass was blocked and had no response when I executed sudo ip link set owl0 up. I'm trying to figure out the reason why.

[jserv]

Thank @dungru for the great work!