| 1 |
* It seems that `-l' and `-g' will not work correctly together (IPv6). |
| 2 |
|
| 3 |
Wait for "flow label" API to be appeared in kernel-headers and |
| 4 |
think about it immediately after that... :) |
| 5 |
|
| 6 |
|
| 7 |
* The "final hop" issue. |
| 8 |
|
| 9 |
All methods, usable when firewalls are present in the network path, |
| 10 |
normally use some particular destination port. Most often it is a port |
| 11 |
of an already running application. |
| 12 |
|
| 13 |
It requires that the packet sent should be correct for such an application |
| 14 |
(for example, for tracing with udp to port 53, it should be correct DNS |
| 15 |
request), and the application normally should answer something on it. |
| 16 |
(TCP has no such an issue, as there are just syn to, and ack or reset from). |
| 17 |
|
| 18 |
In general, we should fill the packet's data depending on the dest port |
| 19 |
and protocol. It seems not a task for traceroute itself, it could be |
| 20 |
some cmdline option or even external hook... |
| 21 |
|
| 22 |
|
| 23 |
* Think about SCTP method. |
| 24 |
|
| 25 |
|
| 26 |
* Think about "multicast tracerouting" (mrouted(8) and other). |
| 27 |
The idea is to increase the room in the mtrace packet step-by-step |
| 28 |
(as well as we increase ttl). It seems that if there is no more space |
| 29 |
in the probe's room, the mrouted(8) daemon answers immediately, the same |
| 30 |
way as if it is a final hop. |
| 31 |
|
| 32 |
For IPv6 mtrace, there is an RFC draft for this already... |
| 33 |
|