diff --git a/src/lescrampte/corr/ft_ping/index.html b/src/lescrampte/corr/ft_ping/index.html new file mode 100644 index 0000000..8c24496 --- /dev/null +++ b/src/lescrampte/corr/ft_ping/index.html @@ -0,0 +1,436 @@ + + + + + + + + + + + + + + + +Intra Projects ft_ping Edit + + + + +
+
+
+

+Scale for project ft_ping +

+ +
+
+

Introduction

+

+
For the smooth running of this evaluation, please respect the following rules:

- Remain polite, kind, respectful and constructive whatever happens during
this conversation. It's a matter of confidence between you and the
42 community.

- Highlight the potential problems you ‘ve had with the work you're presented
to the person or the group you're grading, and take the time to talk about
and discuss those issues.

- Accept the fact that the exam subject or required functions might lead
to different interpretations. Listen to your discussion partner's
perspective with an open mind (are they right or wrong ?) and grade them as
fairly as possible.
42's teaching methods can make sense only if peer-evaluation is
taken seriously.
+

+
+
+

Guidelines

+

+
- You must only evaluate what you will find in the student's or group's
GiT repository.

- Take the time to check that the GiT repository matches the student or
group and the project.

- Double check that no malicious alias was used to mislead you and make you
grade something different from the official repository content.

- If a script supposed to help evaluate the exam is supplied by either side, the
other side will have to strictly check it to avoid nasty surprises.

- If the evaluating student has not yet taken this project, they will have to
read the exam subject in its entirety before starting the evaluation.

- Use the flags available on this grading system to signal an empty or non-
funcional project, a norm flaw, cheating, etc. In that case, evaluation stops
and final grade is 0 (or -42 if it's a cheating problem). However, if it's
not a cheating problem, you are invited to keep talking about the work that
has been done (or not done, as a matter of fact) in order to identify the
issues that lead to this stalemate and avoid it next time.

- Evaluation must be made with a virtual machine running with Debian >= 7 with root rights.
+

+
+ +
+
+

Attachments

+
+
+ +
+
+

+ +subject.pdf +

+
+
+ +
+ +
+
+
+
+

ft_ping base

+

+Attempt to use the project with options. +

+
+

Foreword

+

+

Before starting the evaluation, make sure that:

+ +
    +
  • Your project must be in C
    • +
  • All libC is authorised
    • +
  • However using the system ping or the sources of a standard ping in +any way is forbidden. (ping and execve functions are forbidden)
    • +
  • one Makefile containing the usual rules is present.
    • +
+ +

If one of the conditions has not been met, evaluation stops.

+ +

+
+ + +
+ + + + +
+
+

Checking arguments

+

+

The program checks that user has the necessary permissions and executes
+correctly with the "?" option. It displays a simple, clear and correct
+explanation of its use.

+ +

+
+ + +
+ + + + +
+
+
+
+
+
+

ft_ping ip

+

+For all the grading system questions, you will compare the standard output +with the system ping command with a diff. + +A 30ms +/- difference on a package will be tolerated. + +The tested address' DNS resolution in the return package is not mandatory. + +The final line (concerting the RTT) will be ignored. + +Program stop will be prompted by CTRL+C. +

+
+

ft_ping good ip

+

+

Run the program with a valid and functional IPv4 address as a parameter.

+ +

Does the program work like the system ping ?

+ +

Reminder: A 30ms +/- difference on a package will be tolerated.

+ +

+
+ + +
+ + + + +
+
+

ft_ping bad ip

+

+

Run the program with a valid and non-functional IPv4 address as a parameter.

+ +

Does the program work like the system ping?

+ +

+
+ + +
+ + + + +
+
+

ft_ping -v bad ip

+

+

Run the program with with the otion "-v" on a valid and non-functional
+IPv4 address.

+ +

The evaluated student will have to clearly explain the display return
+of their program.

+ +

+
+ + +
+ + + + +
+
+
+
+
+
+

ft_ping hostname

+

+
+

ft_ping good hostname

+

+

Run the program with a valid and functional hostname as a parameter.

+ +

Does the program work like the system ping?

+ +

+
+ + +
+ + + + +
+
+

ft_ping bad hostname

+

+

Run the program with a valid and non-functional hostname as a parameter.

+ +

Does the program work like the system ping?

+ +

+
+ + +
+ + + + +
+
+

ft_ping -v bad hostname

+

+

Run the program with the option "-v" on a valid and non-functional
+hostname as a parameter.

+ +

The TTL value will have to be modified. (you can use the flag --ttl if
+the student has implemented it otherwise change the hardcoded value and
+recompile the executable)

+ +

The evaluated student will have to clearly explain what their the display
+of their program.

+ +

+
+ + +
+ + + + +
+
+
+
+
+
+

ft_ping bonus

+

+Bonus will be taken into account only if ALL the previous points are valid. +

+
+

Bonus made for this project

+

+

For this project, you can take into account up to 5 different bonuses.

+ +

Check the subject for valid and invalid bonuses.

+ +

+
+ + +
Rate it from 0 (failed) through 5 (excellent)
+
+
+
+
+
+
+
+

Ratings

+

Don’t forget to check the flag corresponding to the defense

+
+ + +
+
+ + + + + + + +
+
+ +
+
+

Conclusion

+ +
+

Leave a comment on this evaluation ( 2048 chars max )

+ + +
+ +
+
+ +
+
+ +
+
+ + + + + + + + + +
+ + + + diff --git a/src/lescrampte/index.html b/src/lescrampte/index.html index 9f6a651..14d1df4 100644 --- a/src/lescrampte/index.html +++ b/src/lescrampte/index.html @@ -93,6 +93,9 @@ dslr + + ft_ping +