On Tue, Jun 08, 2004 at 10:58:31AM +0400, Gleb Smirnoff wrote: > On Tue, Jun 08, 2004 at 09:52:35AM +0300, Ruslan Ermilov wrote: > R> > J> > J> In addition the ng_ksocket node adds info into metadata and I suspect > R> > J> > J> there are people using that. > R> > J> > > R> > J> > Since ng_ksocket tags packets for itself only, we can safely change it. > R> > J> > R> > J> Since I did not add that code I am not very familiar with it or who uses > R> > J> it. (or why) > R> > J> > R> > J> if this is true than yes we can do this.. > R> > > R> > It is used only on UDP connection, to send replies back to where the original > R> > packets came from. > R> > > R> I wouldn't hardcode it this way. Rather, it just mimics the > R> sendto()/recvfrom() semantics, to represent the "to"/"from" > R> arguments, respectively. > > Pardon, haven't understand what do you suggest. You mean, that it'll be better > if node originating packets will insert this tag? > It's not just used "to send replies back". In our proprietary module, we expect the connected node to be of a type "inet/dgram/udp ksocket", and insert tags appropriately to send datagrams to a correct router. We also read tags to verify that the datagrams are coming from the correct router. And it just mimics the sendto()/recvfrom() behavior. Cheers, -- Ruslan Ermilov ru_at_FreeBSD.org FreeBSD committer
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:56 UTC