On Mon, Aug 24, 2020 at 2:15 AM Uli Heilmeier wrote:
> Am 05.08.20 um 19:06 schrieb Richard Sharpe:
> >> As discussed in the last Remote Developer Den meeting I see a Code of
> Conduct (CoC) as helpful for our community.
> >
> > Why? Nothing is broken at the moment, so nothing needs fixing,
On Sat, Mar 18, 2017 at 1:03 PM, Alexander Adolf <
alexander.ad...@condition-alpha.com> wrote:
> I've briefly looked at packet-dvb-s2-bb.c ,and it seems it does BBFrame
> ans well as some GSE handling. Before adding GSE reassembly, I think I
> might try to factor the GSE stuff out into a new
Hi Alexander,
I was the last one to contribute to the GSE dissector implementation in
epan/dissectors/packet-dvb-s2-bb.c.
My involvement is through an amateur radio project (Phase 4 Ground) that is
planning to use DVB-S2 for a ham radio (non-broadcast) satellite downlink.
As such, I'm not very
I want to add fragmentation reassembly to the dissector I'm improving for
DVB-S2-BB. To get things exactly right, I'll need to reassemble in a way
that doesn't seem to be supported by the existing code in
epan/reassemble.[ch]. What approach is considered most preferable?
1. Modify
