Is your feature request related to a problem? Please describe.
Currently, the bundle size generated by bpcat is fixed at compile time, and is about 16KB.
Describe the solution you'd like
For testing various scenarios, it is useful to be able to control the size at run time, through a command line option.
Describe alternatives you've considered
N/A
Additional context
In particular - the default size of 16KB necessitates UDP datagrams that will be fragmented and reassembled, as this is greater than the typical MTU of 1500 bytes. Although this should be transparent and handled by the underlying IP stack, it complicates debugging because a packet capture at the IP level will only show the fragments, not the complete bundle.
In these circumstances it would be helpful to use a bundle size that is smaller than the MTU, such that each UDP datagram has a complete bundle with no fragmentation or reassembly required.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
Is your feature request related to a problem? Please describe. Currently, the bundle size generated by bpcat is fixed at compile time, and is about 16KB.
Describe the solution you'd like For testing various scenarios, it is useful to be able to control the size at run time, through a command line option.
Describe alternatives you've considered N/A
Additional context In particular - the default size of 16KB necessitates UDP datagrams that will be fragmented and reassembled, as this is greater than the typical MTU of 1500 bytes. Although this should be transparent and handled by the underlying IP stack, it complicates debugging because a packet capture at the IP level will only show the fragments, not the complete bundle.
In these circumstances it would be helpful to use a bundle size that is smaller than the MTU, such that each UDP datagram has a complete bundle with no fragmentation or reassembly required.
Requester Info Joseph Hickey, Vantage Systems, Inc.