| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
- added proper error reporting to NAT-test-start/stop
- timed-out nat tests not automatically stop the test itself
- fixed a design flaw in nat-test
- fixed a potential crash in the tests of the nat functionality (NOT NAT_TEST_xy...)
|
|
|
|
|
|
|
|
|
| |
the library
- updated NAT API accordingly
- removed obsolete timeout handling code from gnunet-transport
- updated result callback for nat-test gnunet-transport to not always just report success, but we now actually report the proper result code we got from the NAT API
- updated nat tests
|
|
|
|
| |
- integrated more error-reporting changes for nat_test.c
|
|
|
|
| |
icmp_client server and client not contained in this commit.
|
|
|
|
|
|
|
| |
- NAT lib now uses error-code enums to signal success and errors
- reworked related code to return errorcodes
- added and updated a missing doxygen documention
- todo next: testcases
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
to currently windows-only tests (less work in the future, even if this
is ATM unused)
|
|
|
|
|
| |
todo: nat-server
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
checking in windows. To do so, tested binaries must still be supplied
with valid commandline arguments, but on windows gnunet will utilize the
-d flag to run the programs initialization phase or privileged
operations only. In these modes, a program will not enter its mainloop
or communicate with the outside.
updated relevant function calls gnunet-wide to meet the extended
function parameters.
|
| |
|
| |
|
| |
|
| |
|
|
|