Absolutely there is.
I was going to suggest the GUI alternative, through the Network Utility's Info Tab or the Option +
Click onto the WiFi icon in the menu bar to bring up current statistics. A set of easy to follow steps that are well-documented in this article.
You are however asking for a "native command" and thus interested in the following:
netstat -i : contains
Outgoing Packets (just another name for
TX). By default every interface returns its data but you can easily narrow it down using either
netstat -i | grep en0.
netstat -I en1 (note the capital
-I flag) will produce an output for only that specified interface (here,
en0). This is a more direct approach that does not require further filtering such as the
grep operation above.
Let me know if you have success with any combination of the above, or if there is anything you don't understand/want to refine.
In a comment, you mention seeing three lines of output when querying the interface using
netstat -I, and ask how to handle that data. They are all the same values because they tie back to the same interface, read one line only (usually the first) and don't add them all together as you suggested.
In the Terminal output, those 3 lines are referring to the same interface because multiple addresses are associated with it. In plain terms, it is much like having multiple phone numbers forwarding their calls to your cell phone instead of ringing at their physical location.
In my case (on an iMac, querying
en1), the first line's Address column shows the MAC address of my (ethernet) network card. Which is typically referred to as the most reliable out of the three entries because it is hardcoded and unique to the network card itself (hence won't change unless the physical unit is replaced).
The second line is (at least in my case) associated with an IPv6, while the third is an IPv4 address. These are susceptible to change depending on your network configuration and location. That's why the first line is usually the most reliable out of all. Think of line 1 as your cell phone to which lines 2 and 3 are forwarding the calls - it is also the only entry with error (
Why are the errors only logged there?
Well, think of it as a direct reference/shortcut, if that's all they are (logical connections), they do not exist physically - the only physical interface is where the MAC address resides and thus the only location for packets to be verified and error reporting to take place.
I really hope that made sense, I know you were just after the procedure at the top, but I thought a bit of an explanation won't hurt. Is that helpful in any way?