> > > The real solution is to pass the core_net_rec structure to the NET_TIME > > filter as user-data for the filter, the same way we do for CORE_IN and > > CORE_OUT. > > But you'll have to play some sort of trick to do that since the > NET_TIME filter is added from the create_request hook which does > not know about core_net_rec, only core_create_conn knows about that. > I suppose some core specific magic could be played but that would > prevent any other module from running it's own net_time hook.
This is why I didn't do this originally, but it wouldn't be hard to add. As long as it's just the core that knows about the core_net_rec, we are okay. I just ran out of time while doing the implementation. Ryan