That's a bittorrent local service discovery packet. There is probably a BT torrent client running on the same machine (PY2EN) with the AXIP tunnel endpoint. Multicast packets get not routed without proper multicast support by PIM or proxy, so it is probably a directly connected machine, no router in the way, and it also uses the ax0 interface resulting in the shown behaviour.
-----Original Message----- From: Brian Sent: Tuesday, December 22, 2015 02:40 To: 44net@hamradio.ucsd.edu Subject: [44net] Misconfigured router?
(Please trim inclusions from previous messages) _______________________________________________ I'm getting bombed with these frames:
-- IP: len 162 10.1.1.5->239.192.152.143 ihl 20 ttl 1 DF prot UDP UDP: len 142 40445->6771 Data 134 0000 BT-SEARCH * HTTP/1.1..Host: 239.192.152.143:6771..Port: 8999..In 0040 fohash: c28b3973f693bae99c1b0c13a137a051eef8d9d5..cookie: 5f9721 0080 ...... ax0: fm PY2ZEN-15 to QST ctl UI pid=CC(IP) len 162 IP: len 162 10.1.1.5->239.192.152.143 ihl 20 ttl 1 DF prot UDP UDP: len 142 40445->6771 Data 134 0000 BT-SEARCH * HTTP/1.1..Host: 239.192.152.143:6771..Port: 8999..In 0040 fohash: c28b3973f693bae99c1b0c13a137a051eef8d9d5..cookie: 5f9721 0080 ...... mailman/listinfo/44net