Opened 9 years ago

Last modified 7 years ago

#1244 closed defect (Fixed)

resolve_my_address: Assertion rent->h_length == 4. IPv6 issue?

Reported by: cheako Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.2.1.22
Severity: Keywords:
Cc: cheako, nickm, Sebastian Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

/etc/hosts
2001:XXX::Y cheako cheako.broker.freenet6.net cheako.local

hostname
cheako.broker.freenet6.net

/etc/tor/torrc
## Configuration file for a typical Tor user
## Last updated 12 April 2009 for Tor 0.2.1.14-rc.
## (May or may not work for much older or much newer versions of Tor.)
##
## Lines that begin with "## " try to explain what's going on. Lines
## that begin with just "#" are disabled commands: you can enable them
## by removing the "#" symbol.
##
## See 'man tor', or https://www.torproject.org/tor-manual.html,
## for more options you can use in this file.
##
## Tor will look for this file in various places based on your platform:
## https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc

## Replace this with "SocksPort 0" if you plan to run Tor only as a
## relay, and not make any local application connections yourself.
SocksPort 9050 # what port to open for local application connections
SocksListenAddress 0.0.0.0 # listen on this IP:port also

## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SocksPolicy is set, we accept
## all (and only) requests from SocksListenAddress.
#SocksPolicy accept 192.168.0.0/16
#SocksPolicy reject *

## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many Log lines as
## you want.
##
## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
##
## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
#Log notice file /var/log/tor/notices.log
## Send every possible message to /var/log/tor/debug.log
#Log debug file /var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
#Log notice syslog
## To send all messages to stderr:
#Log debug stderr

## Uncomment this to start the process in the background... or use
## --runasdaemon 1 on the command line. This is ignored on Windows;
## see the FAQ entry if you want Tor to run as an NT service.
#RunAsDaemon 1

## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
#DataDirectory /var/lib/tor

## The port on which Tor will listen for local connections from Tor
## controller applications, as documented in control-spec.txt.
#ControlPort 9051
## If you enable the controlport, be sure to enable one of these
## authentication methods, to prevent attackers from accessing it.
#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C
#CookieAuthentication 1

############### This section is just for location-hidden services ###

## Once you have configured a hidden service, you can look at the
## contents of the file ".../hidden_service/hostname" for the address
## to tell people.
##
## HiddenServicePort x y:z says to redirect requests on port x to the
## address y:z.

#HiddenServiceDir /var/lib/tor/hidden_service/
#HiddenServicePort 80 127.0.0.1:80

#HiddenServiceDir /var/lib/tor/other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServicePort 22 127.0.0.1:22

################ This section is just for relays #####################
#
## See https://www.torproject.org/docs/tor-doc-relay for details.

## Required: what port to advertise for incoming Tor connections.
ORPort 9001
## If you want to listen on a port other than the one advertised
## in ORPort (e.g. to advertise 443 but bind to 9090), uncomment the
## line below too. You'll need to do ipchains or other port forwarding
## yourself to make this work.
#ORListenAddress 0.0.0.0:9090

## A handle for your relay, so people don't have to refer to it by key.
Nickname ChappOik4

## The IP address or full DNS name for your relay. Leave commented out
## and Tor will guess.
#Address nyso.is-a-geek.org

## Define these to limit how much relayed traffic you will allow. Your
## own traffic is still unthrottled. Note that RelayBandwidthRate must
## be at least 20 KBytes.
RelayBandwidthRate 50 KBytes # Throttle traffic to 100KB/s (800Kbps)
RelayBandwidthBurst 100 KBytes # But allow bursts up to 200KB/s (1600Kbps)

## Contact info to be published in the directory, so we can contact you
## if your relay is misconfigured or something else goes wrong. Google
## indexes this, so spammers might also collect it.
#ContactInfo Mike Mestnik <mmestnik@…>
## You might also include your PGP or GPG fingerprint if you have one:
ContactInfo 2048R/C1DA1FAA Mike Mestnik <mmestnik@…>

## Uncomment this to mirror directory information for others. Please do
## if you have enough bandwidth.
DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised
## in DirPort (e.g. to advertise 80 but bind to 9091), uncomment the line
## below too. You'll need to do ipchains or other port forwarding yourself
## to make this work.
#DirListenAddress 0.0.0.0:9091
## Uncomment to return an arbitrary blob of html on your DirPort. Now you
## can explain what Tor is if anybody wonders why your IP address is
## contacting them. See contrib/tor-exit-notice.html for a sample.
DirPortFrontPage /etc/tor/exit-notice.html

## Uncomment this if you run more than one Tor relay, and add the identity
## key fingerprint of each Tor relay you control, even if they're on
## different networks. You declare it here so Tor clients can avoid
## using more than one of your relays in a single circuit. See
## https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleServers
#MyFamily $keyid,$keyid,...

## A comma-separated list of exit policies. They're considered first
## to last, and the first match wins. If you want to _replace_
## the default exit policy, end this with either a reject *:* or an
## accept *:*. Otherwise, you're _augmenting_ (prepending to) the
## default exit policy. Leave commented to just use the default, which is
## described in the man page or at
## https://www.torproject.org/documentation.html
##
## Look at https://www.torproject.org/faq-abuse.html#TypicalAbuses
## for issues you might encounter if you use the default exit policy.
##
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down.
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
#ExitPolicy accept *:119 # accept nntp as well as default exit policy
#ExitPolicy reject *:* # no exits allowed
#
## Bridge relays (or "bridges") are Tor relays that aren't listed in the
## main directory. Since there is no complete public list of them, even if an
## ISP is filtering connections to all the known Tor relays, they probably
## won't be able to block all the bridges. Also, websites won't treat you
## differently because they won't know you're running Tor. If you can
## be a real relay, please do; but if not, be a bridge!
BridgeRelay 1
ExitPolicy reject *:*

DNSPort 9053
AutomapHostsOnResolve 1

ifconfig
br0 Link encap:Ethernet HWaddr 00:24:8c:67:34:60

inet addr:192.168.167.100 Bcast:192.168.167.255 Mask:255.255.255.0
inet6 addr: 2001:XXX::Y/64 Scope:Global
inet6 addr: fe80::224:8cff:fe67:3460/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2912290 errors:0 dropped:0 overruns:0 frame:0
TX packets:3056967 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1875328824 (1.7 GiB) TX bytes:2698210581 (2.5 GiB)

br1 Link encap:Ethernet HWaddr 00:24:8c:67:34:60

inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3077659 errors:0 dropped:0 overruns:0 frame:0
TX packets:3098061 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2553730437 (2.3 GiB) TX bytes:2044123568 (1.9 GiB)

eth0 Link encap:Ethernet HWaddr 00:24:8c:67:34:60

UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:6264318 errors:0 dropped:0 overruns:0 frame:0
TX packets:6444578 errors:0 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:1000
RX bytes:456557751 (435.4 MiB) TX bytes:686818471 (655.0 MiB)
Interrupt:27

eth0.2 Link encap:Ethernet HWaddr 00:24:8c:67:34:60

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2912290 errors:0 dropped:0 overruns:0 frame:0
TX packets:3056969 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1875341897 (1.7 GiB) TX bytes:2698210749 (2.5 GiB)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:383043 errors:0 dropped:0 overruns:0 frame:0
TX packets:383043 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:748979643 (714.2 MiB) TX bytes:748979643 (714.2 MiB)

tun6 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00

inet6 addr: 2001:XXXX::YYYY/128 Scope:Global
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:59701 errors:0 dropped:0 overruns:0 frame:0
TX packets:55738 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:28478989 (27.1 MiB) TX bytes:9009484 (8.5 MiB)

DSL modem ifconfig
br0 Link encap:Ethernet HWaddr 00:24:7B:55:D0:48

inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ASYMMTU:1500
RX packets:4906591 errors:0 dropped:0 overruns:0 frame:0
TX packets:4713527 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3363891567 (3208.0 Mb) TX bytes:3368580587 (3212.5 Mb)

br1 Link encap:Ethernet HWaddr 00:00:00:00:00:00

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ASYMMTU:1500
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

br2 Link encap:Ethernet HWaddr 00:00:00:00:00:00

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ASYMMTU:1500
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

br3 Link encap:Ethernet HWaddr 00:00:00:00:00:00

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ASYMMTU:1500
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:24:7B:55:D0:48

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ASYMMTU:1500
RX packets:2450062 errors:0 dropped:0 overruns:0 frame:0
TX packets:2286139 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1530282543 (1459.3 Mb) TX bytes:1826189017 (1741.5 Mb)

imq0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00

UP RUNNING NOARP MTU:1500 Metric:1 ASYMMTU:1500
RX packets:2252586 errors:0 dropped:0 overruns:0 frame:0
TX packets:2252586 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1774849795 (1692.6 Mb) TX bytes:1774849795 (1692.6 Mb)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1 ASYMMTU:0
RX packets:88 errors:0 dropped:0 overruns:0 frame:0
TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27856 (27.2 kb) TX bytes:27856 (27.2 kb)

nas0 Link encap:Ethernet HWaddr 00:24:7B:55:D0:49

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ASYMMTU:1500
RX packets:2456555 errors:0 dropped:0 overruns:0 frame:0
TX packets:2427381 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1833617196 (1748.6 Mb) TX bytes:1566664920 (1494.0 Mb)

ppp0 Link encap:Point-Point Protocol

inet addr:174.X.Y.Z P-t-P:207.225.140.218 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 ASYMMTU:1500
RX packets:2433773 errors:0 dropped:0 overruns:0 frame:0
TX packets:2404731 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1778703990 (1696.3 Mb) TX bytes:1488739597 (1419.7 Mb)

usb0 Link encap:Ethernet HWaddr 00:24:7B:55:D0:4A

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ASYMMTU:1500
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (6)

comment:1 Changed 9 years ago by Sebastian

I wonder if we can get away with using gethostbyname2 there, and specifying
we only want ipv4 data? Not sure how portable this is (it's a glibc extension, it
appears) and what else that would break. Ideas?

comment:2 Changed 9 years ago by nickm

Why the heck are we using gethostbyname at all? tor_addr_lookup is there for a reason; we should use it.

(In a more ideal world, we'd use getaddrinfo, which is actually standard, but which doesn't exist everywhere it should,
and doesn't work the same everywhere it does exist.)

comment:3 Changed 9 years ago by Sebastian

I think I have a fix, branch bug1244 in my repo. Or do we want to fix stable, too?
Might be worthwhile because this is an assertion that could be prevented. Just in case,
branch bug1244_maint in my repo for a backport.

comment:4 Changed 9 years ago by nickm

Merged; thanks!

comment:5 Changed 9 years ago by nickm

flyspray2trac: bug closed.

comment:6 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.