<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>You could also look at procket:<div><br></div><div><a href="http://blog.listincomprehension.com/">http://blog.listincomprehension.com/</a></div><div><br></div><div><a href="https://github.com/msantos/procket">https://github.com/msantos/procket</a></div><div><br><br><div><div id="SkyDrivePlaceholder"></div>> From: nem@erlang.geek.nz<br>> Date: Wed, 3 Apr 2013 11:06:14 -0700<br>> To: garry@research.att.com<br>> CC: erlang-questions@erlang.org<br>> Subject: Re: [erlang-questions] low level packet access from erlang<br>> <br>> Hi there - I'm slowly building a TAP interface based library for networking at https://github.com/archaelus/enet -- some of the code might save you some time. You can send and receive packets with it, but it's missing a lot of mechanisms and infrastructure for making that easy. <br>> <br>> I've used the packet parsing code a bunch for pcap file analysis, and the generation code only a little to try and build an IP stack.<br>> <br>> The docs are non-existent but I'm more than happy to answer questions about the code.<br>> <br>> -Geoff<br>> <br>> On 2013-04-03, at 10:59 , Garry Hodgson <garry@research.att.com> wrote:<br>> <br>> > i am building an experimental firewall of sorts,<br>> > and need to be able to access incoming packets<br>> > directly, so i can muck around with low level<br>> > src/dst/ports/etc information. it looks like the standard<br>> > modules handle the low level things for me, such that<br>> > i by the time i see an incoming message, the low level<br>> > details are lost.<br>> > <br>> > how can i arrange access to the lower level information<br>> > (ignoring performance issues for now)?<br>> > <br>> > i see like mentioned a way in an old (2001) thread:<br>> > http://www.trapexit.org/forum/viewtopic.php?p=4258&sid=4469db61020efe9100e1e1c2504bfc8c<br>> > but the link to bluetail where his code was doesn't exist anymore.<br>> > <br>> > i've read the ei/pcap approach presented here:<br>> > http://blog.listincomprehension.com/2009/12/erlang-packet-sniffer-using-ei-and.html<br>> > <br>> > but i don't want to just sniff packets, but intercept them.<br>> > <br>> > i'd appreciate any insights into how to tackle this.<br>> > <br>> > -- <br>> > Garry Hodgson<br>> > AT&T Chief Security Office (CSO)<br>> <br>> <br>> <br>> <br>> <br>> _______________________________________________<br>> erlang-questions mailing list<br>> erlang-questions@erlang.org<br>> http://erlang.org/mailman/listinfo/erlang-questions<br></div></div> </div></body>
</html>