Opened 7 years ago

Closed 7 years ago

Last modified 6 years ago

#7493 closed defect (fixed)

connection_ap_get_begincell_flags() and DirPort not reachable

Reported by: Safari Owned by:
Priority: High Milestone: Tor: 0.2.4.x-final
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I try to connect with SOCKS (polipo) and it fails with these funny errors.
Running Tor as middleman seems to work.
DNS resolution thru Tor works.

now trying tor git ca0c71551e519a1d27cec5db9c9e6722a382d19d
git 83b1a50cc0b worked ok

2012-11-16 02:58:45.722295951 [warn] connection_ap_get_begincell_flags(): Bug: Hey; I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's probably not going to work.
2012-11-16 02:58:46.475374023 [warn] Got a connected cell to 63.245.217.112 with unsupported address family. Closing.

Child Tickets

Change History (17)

comment:1 Changed 7 years ago by nickm

Resolution: fixed
Status: newclosed

Yeowch! Should be fixed in 28cbe908398f24366a9056d2508ae94690d82bba. Please re-open if it isn't.

comment:2 Changed 7 years ago by nickm

Milestone: Tor: 0.2.4.x-final

comment:3 Changed 7 years ago by arma

Resolution: fixed
Status: closedreopened

comment:4 Changed 7 years ago by arma

Nov 18 14:58:44.000 [warn] connection_ap_get_begincell_flags(): Bug: Hey; I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's probably not going to work.

on moria5 running on git master (06d367ea365f).

SoakedNoodle on irc saw this too. He experienced a related "now my dirport isn't reachable anymore" bug, which might be our hint.

comment:5 Changed 7 years ago by cypherpunks

Summary: both IPv4 and IPv6 are unsupported on Linux 3.6 ;) connection_ap_get_begincell_flagsconnection_ap_get_begincell_flags() and DirPort not reachable
Version: Tor: 0.2.4.5-alphaTor: unspecified

Nov 18 !20:12:58.000 [warn] connection_ap_get_begincell_flags(): Bug: Hey; I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's probably not going to work.
Nov 18 !20:13:34.000 [warn] connection_ap_get_begincell_flags(): Bug: Hey; I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's probably not going to work.

Tor version 0.2.4.6-alpha-dev (git-06d367ea365ff3e6)

And I also seem to get the message

Your server has not managed to confirm that its DirPort is reachable.

And this is in fact true, atlas did not report my DirPort (although the html blob is served).

comment:6 Changed 7 years ago by SoakedNoodle

Version: Tor: unspecified

This is how it looks after re-starting the relay.

Nov 18 23:05:03.000 [notice] Bootstrapped 100%: Done.
Nov 18 23:05:03.000 [notice] Now checking whether ORPort 80.101.115.170:443 and DirPort 80.101.115.170:80 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Nov 18 23:05:03.000 [warn] connection_ap_get_begincell_flags(): Bug: Hey; I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's probably not going to work.
Version 0, edited 7 years ago by SoakedNoodle (next)

comment:7 Changed 7 years ago by nickm

Can one of you post your torrc?

comment:8 Changed 7 years ago by arma

geoipfile ../git/src/config/geoip
safelogging 0
log notice file moria5-notice
log info file moria5-info
log notice stdout
DataDirectory moria5
Nickname moria5
ORPort 9005
dirport auto
SocksPort 0
MyFamily moria1,moria2,moria3,moria4,moria5,peacetime
ExitPolicy reject *:*
ContactInfo 1024D/28988BF5 Roger Dingledine <arma@mit.edu>

basically, it's a standard relay with dirport set.

comment:9 Changed 7 years ago by nickm

Status: reopenedneeds_review

ooh, ooh, I know! Try branch "bug7493_redux" in my public repo. If that helps, and it looks ok, please feel free to merge it and close this.

comment:10 Changed 7 years ago by arma

Looks promising:

Nov 18 17:22:13.343 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.

soakednoodle, how about you?

comment:11 Changed 7 years ago by SoakedNoodle

If you guys keep quiet I can post my comment, without trac raping my formatting. :P

I submitted the comment a bit early, it has found out the ORPort works, but the DirPort is still dead.

Nov 18 23:05:37.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. 
Nov 18 23:06:01.000 [warn] connection_ap_get_begincell_flags(): Bug: Hey; I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's probably not going to work. 
Nov 18 23:08:04.000 [notice] Performing bandwidth self-test...done. 
Nov 18 23:08:08.000 [warn] connection_ap_get_begincell_flags(): Bug: Hey; I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's probably not going to work.

My torrc:

ORPort 443 NoListen
ORPort 9090 NoAdvertise
ORPort [y:y:y:y]:6697
DirPort 80 NoListen
DirPort 9091 NoAdvertise

DataDirectory /usr/local/var/tor
ControlPort 9051
CookieAuthentication 1
ExitPolicy reject *:*
DisableDebuggerAttachment
Last edited 6 years ago by SoakedNoodle (previous) (diff)

comment:12 Changed 7 years ago by SoakedNoodle

Nope, since 23:08:08 this got logged:

Nov 18 23:12:08.000 [notice] Low circuit success rate 59/162 for guard phillw=B4DAE5A91950915A945D518B58562141E601608D.
Nov 18 23:12:24.000 [warn] connection_ap_get_begincell_flags(): Bug: Hey; I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's probably not going to work.
Nov 18 23:18:13.000 [warn] connection_ap_get_begincell_flags(): Bug: Hey; I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's probably not going to work.
Nov 18 23:24:19.000 [warn] connection_ap_get_begincell_flags(): Bug: Hey; I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's probably not going to work.
Nov 18 23:25:00.000 [warn] Your server (x.x.x.x:80) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Last edited 6 years ago by SoakedNoodle (previous) (diff)

comment:13 Changed 7 years ago by nickm

Nope, since 23:08:08 this got logged:

And that is using the branch I mentioned above? It isn't merged into master yet.

comment:14 in reply to:  10 Changed 7 years ago by arma

Replying to arma:

Looks promising:

I'm a happy camper on my side. Not sure about soakednoodle though.

comment:15 Changed 7 years ago by nickm

Priority: blockermajor
Status: needs_reviewneeds_information

ok; merging bug7493_redux into master, since looking at it I can't see what harm it could do (ha ha famous last words), and I believe it should in fact fix this.

Once we know whether it's fixed the issue, we can close or investigate further.

comment:16 in reply to:  13 Changed 7 years ago by SoakedNoodle

I'm now running 'Tor v0.2.4.6-alpha-dev (git-5375719aa89fe3a0)'

Nov 19 07:40:48.000 [notice] Bootstrapped 100%: Done.
Nov 19 07:41:56.000 [notice] Performing bandwidth self-test...done.
Nov 19 07:41:56.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.

Looks good, no connection_ap_get_begincell_flags() messages anymore, and I guess they would have popped up by now.

comment:17 Changed 7 years ago by arma

Resolution: fixed
Status: needs_informationclosed

Closing as re-fixed then. As Nick so finely put it, "Please re-open if it isn't."

Note: See TracTickets for help on using tickets.