In the case of facebook.com, the default TTL values of packets sent from the server don't appear to be one of the three standard values (64, 128, 255), which seems to cause infer_hop to malfunction.
2026-02-26 16:51:37 [DEBUG] HopTab::put: hit empty 76; HopTabEntry{ ip=57.144.188.1, state=0x01, hop=42, ts=0, meta=0x0000000000002a01 }
2026-02-26 16:51:37 [DEBUG] HopTab::put: update 76 to HopTabEntry{ ip=57.144.188.1, state=0x01, hop=42, ts=0, meta=0x0000000000002a01 }
2026-02-26 16:51:37 [DEBUG] HopTab::find_hop: found 76; HopTabEntry{ ip=57.144.188.1, state=0x01, hop=42, ts=0, meta=0x0000000000002a01 }
2026-02-26 16:51:37 [DEBUG] autottl: set ttl to 41
2026-02-26 16:51:37 [DEBUG] HopTab::find_hop: found 76; HopTabEntry{ ip=57.144.188.1, state=0x03, hop=42, ts=0, meta=0x0000000000002a03 }
2026-02-26 16:51:37 [DEBUG] autottl: set ttl to 41
2026-02-26 16:51:37 [DEBUG] send_split: dst=57.144.188.1 segments=[0, 1] tcp_payload_len=1380
In the case of facebook.com, the default TTL values of packets sent from the server don't appear to be one of the three standard values (64, 128, 255), which seems to cause infer_hop to malfunction.