+ Archie Cobbs wrote:
| Are you intending to have this hook into the normal FreeBSD TCP/IP
| stack or be truly standalone? I read your question as the latter but
| others seem to read it as the former.
I am very much a babe in the woods at this point. I have no plan aside
from reading as
Steve Tremblett wrote:
A while back someone was fishing for a project to take on and someone
suggested a complete TCP/IP implementation in netgraph. I found the
idea interesting and am considering taking a shot at it. My main goal
in all this is to learn as much as possible and at this point
I do not think that you need a raw IP netgraph node. Something similar
already exists. Why not use the ng_ksocket in order to open a raw IP socket
under your TCP node ?
Vincent
Le Jeudi 17 Octobre 2002 20:59, vous avez écrit :
Steve Tremblett wrote:
A while back someone was fishing for a
Vincent Jardin wrote:
I do not think that you need a raw IP netgraph node. Something similar
already exists. Why not use the ng_ksocket in order to open a raw IP socket
under your TCP node ?
Because the packet will never get to your protocol processing, unless
you turn of standard TCP
Julian Elischer wrote:
There is also the m_pullup() issue of the TCP protocol that is
being passed IP datagrams which may be frags of TCP packets, in
order to get the full TCP header, with options.
The tcp code should handle this anyway.
It should, but it won't. The issue is when you
