-
I have had some success in getting up 2 virtual Ethernet interfaces in Zephyr for the native POSIX board target. One interface will represent a common bridge between multiple running instances of a Zephyr application simulating a radio with a wired and wireless interface. The wireless interface for each instance will have a single IP assigned to each instance, and each wireless iface will have the MTU set to 9K, and will be promiscuous representing a radio being able to sense all over the air packets. I was able to set the MTU to the 9K range on the iface that will be the common OTA bridge for each running Zephyr instance. However, by inspection of the source code eth_native_posix.c, there is a suggestion that the threads are operating on tx and rx buffers that are of the typical 1500 byte size. Is IP fragmenting required to support IP Jumboframes?
Does anyone has experience attempting to use IP Jumboframes with the Zephyr network stack and particularly native POSIX emulation? The dump of my net ifaces is as follows suggesting support for the IP jumbo frames:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
There is currently no support for Jumboframes in the Zephyr stack, the MTU seems fixed to 1514 and below. This issue has been addressed as well as a potential bug listed as low priority. |
Beta Was this translation helpful? Give feedback.
-
There is a source code mod that can be made to a Native POSIX source file that will enabled this feature, but will not be incorporated into the mainline Zephyr code base, which does not support IP jumboframes. Refer to the following: |
Beta Was this translation helpful? Give feedback.
There is currently no support for Jumboframes in the Zephyr stack, the MTU seems fixed to 1514 and below. This issue has been addressed as well as a potential bug listed as low priority.