Opened 7 years ago

Closed 4 years ago

#9426 closed defect (duplicate)

multicast connection tries

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor:
Severity: Normal Keywords: tor-relay private-address
Cc: Actual Points:
Parent ID: #7971 Points:
Reviewer: Sponsor:


local firewall log reports that
Tor version (git-17c24b3118224d65)
tries to connect to multicast destinations.
Seven tries per multicast destination and roughly ten different multicast destinations per day.

That means option ExtendAllowPrivateAddresses (default: 0)
doesn't deal with multicast destinations.

Do we missing something?

Child Tickets

Change History (3)

comment:1 Changed 7 years ago by arma

Milestone: Tor: 0.2.3.x-finalTor: unspecified

which addresses / networks? (are these actually reserved for multicast, or is this like the bogon netblocks, where they change every month and everybody's list is always out of date?)

comment:2 Changed 7 years ago by cypherpunks

I looked into source code, function tor_addr_is_internal() deals only with these ipv4 ranges

   if (((iph4 & 0xff000000) == 0x0a000000) || /*       10/8 */
       ((iph4 & 0xff000000) == 0x00000000) || /*        0/8 */
       ((iph4 & 0xff000000) == 0x7f000000) || /*      127/8 */
       ((iph4 & 0xffff0000) == 0xa9fe0000) || /* 169.254/16 */
       ((iph4 & 0xfff00000) == 0xac100000) || /*  172.16/12 */
       ((iph4 & 0xffff0000) == 0xc0a80000))   /* 192.168/16 */

Special use and reserved IPv4 prefixes (fltr-martian) includes

tor should filter these ipv4 ranges also,
maybe we need a new option ExtendAllowMartianAddresses.

comment:3 Changed 4 years ago by nickm

Keywords: tor-relay private-address added
Parent ID: #7971
Resolution: duplicate
Severity: Normal
Status: newclosed

Another piece for #7971

Note: See TracTickets for help on using tickets.