You will hear a response about this today. The two possible mentors are
discussing this and will respond on this group.
Arun
here's our thought for a sheep/goat project. The idea is that you
implement a simple packet filter that does the following. When
enabled, it should drop *every* [1] incoming / outgoing packet and
dump it on stdout in the appropriate format. You are asked to write
support to enable/disable the packet filter dynamically in MINIX 3.
You also have to write a simple user-space application which reads
rules from an input file. For now, rules are as simple as "simplepf
on" / "simplepf off" to enable / disable the simple packet filter.
[1] note: there are different ways to do it, of course. However, what
you don't have to do is to push the rules on each NIC, for instance.
We would like you to come up with an elegant solution ;-)
Cristiano & Lorenzo
--
You received this message because you are subscribed to the Google Groups "minix3" group.
To post to this group, send email to min...@googlegroups.com.
To unsubscribe from this group, send email to minix3+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/minix3?hl=en.
could you send the source tarball to in...@minix3.org, please? Of
course, remember to apply to GSoC (http://socghop.appspot.com/) if you
haven't done it yet.
TIA, bye
Lorenzo
> <mailto:arun.tho...@gmail.com>> wrote:
> > Murali Krishna wrote:
> > > Hello
> >
> > > Can any one tell me what is the sheep/goat project for the
> projects that
> > > involve networking part like MINIX Firewall?
> >
> > You will hear a response about this today. The two possible
> mentors are
> > discussing this and will respond on this group.
> >
> > Arun
>
> --
> You received this message because you are subscribed to the Google
> Groups "minix3" group.
> To post to this group, send email to min...@googlegroups.com
> <mailto:min...@googlegroups.com>.
> To unsubscribe from this group, send email to
> minix3+un...@googlegroups.com
> <mailto:minix3%2Bunsu...@googlegroups.com>.
> For more options, visit this group at
> http://groups.google.com/group/minix3?hl=en.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "minix3" group.
> To post to this group, send email to min...@googlegroups.com.
> To unsubscribe from this group, send email to
> minix3+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/minix3?hl=en.
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
--
Lorenzo `Gigi Sullivan' Cavallaro <sull...@few.vu.nl>
WWW on http://www.few.vu.nl/~sullivan
Until I loved, life had no beauty;
I did not know I lived until I had loved. (Theodor Korner)
See the reality in your eyes, when the hate makes you blind. (A.H.X)
I've also implemented a simple packet filter, as it was described.
As a briefly description, the patch is made entirely on the inet
server and the communication between user-space application and the
inet system process is made through the special device files (/dev/ip)
by using a special command within a ioctl() call. The behavior is
shortly presented on [1].
Should I attach the patch here or should I send it on in...@minix3.org?
Regards,
[1] http://pastebin.com/P7Wk8cmn
--
Claudiu-Dan Gheorghe
HelloEveryoneI tried the sheep/goat project for MINIX firewall. As required I am able to create a command called "data_table" with options-B Block the packets in coming-W Block the packets Out going-U Allow all the packets both incoming and outgoingI created a system call and using it I transfered the values from user level to kernel level data structure and then based on the flag values I am blocking the packets by freeing the packets using bf_afree(pack).I added several screen shots of the output. If required I will post the source code.