<div dir="ltr"><br><br><div class="gmail_quote">On Mon, Jan 17, 2011 at 11:43 PM, John Mahoney <span dir="ltr"><<a href="mailto:jmahoney@waav.com">jmahoney@waav.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">On Mon, Jan 17, 2011 at 4:24 PM, Kfir Lavi <<a href="mailto:lavi.kfir@gmail.com">lavi.kfir@gmail.com</a>> wrote:<br>
> Hi,<br>
> How can one implement custom header network protocol.<br>
> I mean header that wraps regular network packets like ethernet, udp, tcp,<br>
> etc...<br>
> The sending of this custom packets is done between processes running<br>
> locally.<br>
> ie. I get a Ethernet packet, inspect it, then add my custom header and<br>
> forward<br>
> it to another process that listens to a socket, and expect to get data<br>
> wrapped with<br>
> this custom header.<br>
><br>
> What is a good way to go about and implement this thing?<br>
<br>
</div></div>Have you looked at the tun/tap drivers?<br>
<br></blockquote><div>Yes I did, they can work for me, but I need to modify the code.<br>They expect certain protocols and are not passing anything. <br>It is a bit ugly to go this way. <br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Also, try asking this question on a network specific list.<br>
<br>
--<br>
<font color="#888888">John<br>
</font></blockquote></div><br></div>