[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
On (06/18/07 11:35), [EMAIL PROTECTED] wrote:
...
As for what to display for "possible", I don't think that
this is meaningful here. I would rather see the default
output just be "LINK", "PROPERTY", "VALUE" and "DEFAULT".
unfortunately we already follow the above convention (printing
POSSIBLE) for wifi links.. so unless we want to break the trend, we
are stuck with reporting possible. I personally also feel ther eis some
use in printing possible, as this gives a hint of input range.
What scope for change do you have here?
Is that "stable"/"committed" or just "private"?
Additionally, what are you reporting at the MTU here?
The network layer MTU or the link layer MTU?
The mtu reported here is the same as that reported in 'ifconfig -a',
i.e., the link-layer mtu.
"ifconfig -a" reports the network layer MTU, not the link layer MTU
because (to repeat what everyone else says), ifconfig on Solaris
shows IP network interfaces, not anything else.
I can shove 1536 bytes of garbage in a normal ethernet frame.
I can shove 1500 bytes of garbage in a normal IP packet.
If I want to capture an entire 1500 byte IP packet with snoop,
I have to specify "-s 1536".
Whomever decided that dladm should show "1500" for ethernet
should to be made to drink a case of budweiser beer (and not
the European brand.)
1500 bytes is the maximum size of an Ethernet frame, sans Ethernet
headers. Pretty much all implementations honor this. If you look in
our device drivers for example, you will see that they will typically
drop any frame that is more than 1514 bytes (1518 for vlans) long.
Note that this does not include certain bits that are not strictly part
of the frame that is passed from the device to the host. For example,
ethernet frame checksums are not included (4 bytes), nor are the 7-byte
preamble or 1 byte start-of-frame delimiter.
You cannot normally see any of those parts (12 bytes) so its not fair to
include them.
AFAIK, the 1536 number comes from 0x600 hex, which is the minimum
ethernet type number. (Values less than this are interpreted as an
802.3 length value, instead of the Ethernet II frame type.)
-- Garrett
Darren
_______________________________________________
networking-discuss mailing list
[EMAIL PROTECTED]
_______________________________________________
driver-discuss mailing list
driver-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
