This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Fwd: [mat-wg] Atlas: DNS TCP Errors
- Previous message (by thread): [atlas] Fwd: [mat-wg] Atlas: DNS TCP Errors
- Next message (by thread): [atlas] Cannot understand the daily limit
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nils Ohlmeier
lists at ohlmeier.org
Tue Mar 14 22:58:02 CET 2017
On 3/14/17 14:37, John wrote: > """ > Normally, UDP pretty much ignores ICMP errors, so if you want to see > them, you need to open a raw socket to receive all ICMP packets and look > for ones relevant to your socket. > > On Linux, at least, an alternative is to set the IP_RECVERR socket > option. If you do that, you can do a recvmsg with the MSG_ERRQUEUE flag > set to get any ICMP (or other) errors associated with your socket. This > has the advantage of not requiring elevated privileges or a second socket. > """ > > http://stackoverflow.com/questions/23118113/c-sockets-send-udp-and-process-icmp-reply-from-router The connected UDP socket (second answer) should work fine on Linux to receive ICMP errors for rejected UDP messages. Best Nils
- Previous message (by thread): [atlas] Fwd: [mat-wg] Atlas: DNS TCP Errors
- Next message (by thread): [atlas] Cannot understand the daily limit
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]