| Friday June 23 2017 |
| Time | Replies | Subject |
|---|
| 8:34PM |
1 |
Significance of port 655? |
| |
| Thursday June 22 2017 |
| Time | Replies | Subject |
|---|
| 6:25PM |
0 |
Significance of port 655? |
| |
| Wednesday June 21 2017 |
| Time | Replies | Subject |
|---|
| 11:57PM |
2 |
Significance of port 655? |
| 1:11AM |
0 |
How to diagnostic UDP discovery failed situation |
| 12:22AM |
2 |
How to diagnostic UDP discovery failed situation |
| |
| Sunday June 18 2017 |
| Time | Replies | Subject |
|---|
| 1:49PM |
0 |
Why sometimes the MTU discovery by UDP never get a response? |
| 1:49PM |
0 |
Reliability between TCPonly and UDP for tinc? |
| 1:44PM |
2 |
Reliability between TCPonly and UDP for tinc? |
| 1:25PM |
0 |
Reliability between TCPonly and UDP for tinc? |
| 12:53PM |
2 |
Reliability between TCPonly and UDP for tinc? |
| |
| Monday June 12 2017 |
| Time | Replies | Subject |
|---|
| 11:53AM |
0 |
Segfault with 1.1 |
| |
| Thursday June 8 2017 |
| Time | Replies | Subject |
|---|
| 5:01AM |
0 |
Tinc still run on single core of CPU? |
| |
| Friday June 2 2017 |
| Time | Replies | Subject |
|---|
| 7:33PM |
0 |
I've stumbled across weird chain of multiple failures |
| |
| Thursday June 1 2017 |
| Time | Replies | Subject |
|---|
| 2:21AM |
1 |
Cache of the the unreachable nodes cause un-optimized route? |