> I checked in changes to: > > make the minimum and maximum packet sizes #defines; > > crank the maximum packet size up to 65535 bytes. > > (4096 isn't big enough for a full FDDI frame, or the large frames that > may be sent over ATM). Microsoft's Network Monitor lets you specify either a capture length, or "Full". It might be nice to have a special value that means "don't limit my capture" in the "Capture Properties" spin box for capture length, which would currently set the max packet size to 65535 (but it might be nice to have "wiretap" let you not specify a capture length and, on those platforms where you have to make a call to *set* the capture length, just not make that call if no capture length was specified). This would, I think, mean not making that field in the "Capture Preferences" dialog box be a spin box; the spin box is somewhat nice in that it can limit you to values between the minimum and maximum (it's currently not set up to limit you to values at or above the minimum, but I'll be checking in a change to do that), but maybe there's some way to let it be either a number or a special value. It might also be nice to have it default to "no limit", as "snoop" and Network Monitor do, at least for those of us who deal a lot with protocols above the transport layer.
Powered by MHonArc 2.6.10