[erlang-questions] low level packet access from erlang
Wed Apr 3 22:04:12 CEST 2013
It might be worth looking into how
https://www.erlang-solutions.com/products/openflow does it. IIRC it works
at the ethernet level so there's lots of info available.
On 3 April 2013 19:59, Garry Hodgson <garry@REDACTED> wrote:
> i am building an experimental firewall of sorts,
> and need to be able to access incoming packets
> directly, so i can muck around with low level
> src/dst/ports/etc information. it looks like the standard
> modules handle the low level things for me, such that
> i by the time i see an incoming message, the low level
> details are lost.
> how can i arrange access to the lower level information
> (ignoring performance issues for now)?
> i see like mentioned a way in an old (2001) thread:
> but the link to bluetail where his code was doesn't exist anymore.
> i've read the ei/pcap approach presented here:
> but i don't want to just sniff packets, but intercept them.
> i'd appreciate any insights into how to tackle this.
> Garry Hodgson
> AT&T Chief Security Office (CSO)
> "This e-mail and any files transmitted with it are AT&T property, are
> confidential, and are intended solely for the use of the individual or
> entity to whom this e-mail is addressed. If you are not one of the named
> recipient(s) or otherwise have reason to believe that you have received
> this message in error, please notify the sender and delete this message
> immediately from your computer. Any other use, retention, dissemination,
> forwarding, printing, or copying of this e-mail is strictly prohibited."
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions