Re: Problems with irc because of tor?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Praedor Atrebates @ 11/20/2008 01:08 PM: [snip] Why does running tor suddenly cause me to be unable to connect to freenode? I am NOT running a torified irc client. if you have tor configured as an exit node on the same IP address, then that is probably why. freenode is probably just looking at the list of exit nodes and acting accordingly. Also, where's the address 127.0.0.1 coming from? Why is my REAL IP address now invisible (apparently) and tor causing sites to think I am trying to use the illegal localhost IP? i think that IP is generated by the freenode server. they could have configured their server to just say that IP address when they ban any address... -BEGIN PGP SIGNATURE- iD8DBQFJKk2CXhfCJNu98qARCDKRAKDwxetf4IVrLagnSFwxW5Gh91ZjowCeLDA2 Fk2ks2Hl3PZZq4HGgYpnKnw= =hEbF -END PGP SIGNATURE-
Re: Problems with irc because of tor?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 scar @ 11/23/2008 11:45 PM: Praedor Atrebates @ 11/20/2008 01:08 PM: [snip] Why does running tor suddenly cause me to be unable to connect to freenode? I am NOT running a torified irc client. if you have tor configured as an exit node on the same IP address, then that is probably why. freenode is probably just looking at the list of exit nodes and acting accordingly. Also, where's the address 127.0.0.1 coming from? Why is my REAL IP address now invisible (apparently) and tor causing sites to think I am trying to use the illegal localhost IP? i think that IP is generated by the freenode server. they could have configured their server to just say that IP address when they ban any address... oops, sorry about that. i thought no one had replied to you since *ahem* some people's clients break threading ;) looking further through the unread mails, i see that wasn't the case. hopefully my reply wasn't completely useless -BEGIN PGP SIGNATURE- iD8DBQFJKk7aXhfCJNu98qARCAZHAKD4YqrEXRZOcWaliVMX5uPc9FkT9QCg1FOC B1CjvF+25MVYTXHfY49/QwI= =zOws -END PGP SIGNATURE-
Re: Problems with irc because of tor?
On Thu, 20 Nov 2008 16:53:42 -0500 Praedor Atrebates [EMAIL PROTECTED] wrote: I am running Mandriva linux 2009.0. I have been using tork (as a tor manager) and tor for several years with a bunch of problems only occurring since going to 2009.0 AND upgrading to tor 0.2.1.7-alpha. Before this, I ran tor and tork AND access IRC (via Konversation in KDE) without problems. I've checked processes when tor appears to die and it really is dead. I check the debug log and there is literally nothing there to indicate any problems whatsoever, just a message that tor died: Nov 20 16:21:54.219 [info] command_process_netinfo_cell(): Got good NETINFO cell from [scrubbed]; OR connection is now open, using protocol version 2 Nov 20 16:21:54.219 [debug] connection_or_process_cells_from_inbuf(): 59: starting, inbuf_datalen 0 (0 pending in tls object). Nov 20 16:21:54.377 [debug] conn_read_callback(): socket 59 wants to read. Nov 20 16:21:54.377 [debug] connection_read_to_buf(): 59: starting, inbuf_datalen 0 (0 pending in tls object). at_most 12288. Nov 20 16:21:54.377 [debug] connection_read_to_buf(): After TLS read of 512: 586 read, 0 written Nov 20 16:21:54.377 [debug] connection_or_process_cells_from_inbuf(): 59: starting, inbuf_datalen 512 (0 pending in tls object). Nov 20 16:21:54.377 [debug] command_process_create_cell(): success: handed off onionskin. Nov 20 16:21:54.377 [debug] connection_or_process_cells_from_inbuf(): 59: starting, inbuf_datalen 0 (0 pending in tls object). Nov 20 16:21:54.377 [debug] conn_write_callback(): socket 5 wants to write. Nov 20 16:21:54.404 [debug] cpuworker_main(): onion_skin_server_handshake succeeded. Nov 20 16:21:54.404 [debug] conn_read_callback(): socket 5 wants to read. Nov 20 16:21:54.404 [debug] read_to_chunk(): Read 231 bytes. 231 on inbuf. Nov 20 16:21:54.404 [debug] onionskin_answer(): init digest forward 0xb2ff98cd, backward 0xb12cc861. Nov 20 16:21:54.404 [debug] append_cell_to_circuit_queue(): Made a circuit active. Nov 20 16:21:54.404 [debug] append_cell_to_circuit_queue(): Primed a buffer. Nov 20 16:21:54.404 [debug] connection_or_flush_from_first_active_circuit(): Made a circuit inactive. Nov 20 16:21:54.404 [debug] onionskin_answer(): Finished sending 'created' cell. Nov 20 16:21:54.404 [debug] connection_cpu_process_inbuf(): onionskin_answer succeeded. Yay. Nov 20 16:21:54.404 [debug] conn_write_callback(): socket 59 wants to write. Nov 20 16:21:54.404 [debug] flush_chunk_tls(): flushed 512 bytes, 0 ready to flush, 0 remain. Nov 20 16:21:54.404 [debug] connection_handle_write(): After TLS write of 512: 0 read, 586 written Nov 20 16:21:54.404 [debug] cpuworker_main(): finished writing response. Nov 20 16:21:54.610 [notice] Catching signal TERM, exiting cleanly. ^^ So what sent tor a SIGTERM? Given receipt of a SIGTERM, what follows appears to be normal enough. The question occurs to me whether if tor detects another tor process running under the same user id, will it issue a SIGTERM itself either to the other process or to itself to prevent conflicts (e.g., two tors bound to the same ORPort, DirPort, etc.)? Nov 20 16:21:54.611 [info] or_state_save(): Saved state to /home/praedor/.tor/state Nov 20 16:21:54.717 [debug] _connection_free(): closing fd 8. Nov 20 16:21:54.717 [debug] _connection_free(): closing fd 15. Nov 20 16:21:54.717 [debug] _connection_free(): closing fd 24. Nov 20 16:21:54.717 [debug] _connection_free(): closing fd 25. Nov 20 16:21:54.717 [debug] _connection_free(): closing fd 5. Nov 20 16:21:54.717 [info] cpuworker_main(): CPU worker exiting because Tor process closed connection (either rotated keys or died). Nov 20 16:21:54.718 [debug] _connection_free(): closing fd 43. Nov 20 16:21:54.719 [debug] _connection_free(): closing fd 50. Nov 20 16:21:54.719 [debug] _connection_free(): closing fd 45.
Re: Problems with irc because of tor?
-Ursprüngliche Nachricht- Von: Praedor Atrebates [EMAIL PROTECTED] Gesendet: 20.11.08 21:10:08 An: or-talk@freehaven.net Betreff: Problems with irc because of tor? I have been fighting to get tor-0.2.1.7-alpha working on my system for a while and finally appear to have it working now. Now I find that trying to connect to IRC servers fails: [15:06] [Info] Trying to reconnect to irc.freenode.org in 20 seconds. [15:06] [Info] Looking for server irc.freenode.org:6667... [15:06] [Info] Server found, connecting... [15:06] [Info] Connected; logging in... [15:06] [Notice] -- *** Looking up your hostname... [15:06] [Notice] -- *** Checking ident [15:06] [Notice] -- *** Couldn't look up your hostname [15:06] [Notice] -- *** No identd (auth) response [15:06] [Notice] -zelazny.freenode.net- *** Banned: Tor freenode is hidden- service-only (mejokbp2brhw4omd.onion) - see freenode.net/irc_servers.shtml. (2008/11/18 21.17) [15:06] [error] Closing Link: 127.0.0.1 (Banned) Why does running tor suddenly cause me to be unable to connect to freenode? I am NOT running a torified irc client. Also, where's the address 127.0.0.1 coming from? Why is my REAL IP address now invisible (apparently) and tor causing sites to think I am trying to use the illegal localhost IP? praedor Unfortunately, some service providers choose to not accept Tor users as part of their userbase and block connections from exit nodes. To resolve your freenode problem you can either use the hidden service, as the error message states, or you must disallow exiting to freenode's IRC ports so they can see that the connection is not coming from Tor, but rather from yourself. Sebastian
Re: Problems with irc because of tor?
Sebastian Hahn wrote: -Ursprüngliche Nachricht- Von: Praedor Atrebates [EMAIL PROTECTED] Gesendet: 20.11.08 21:10:08 An: or-talk@freehaven.net Betreff: Problems with irc because of tor? Why does running tor suddenly cause me to be unable to connect to freenode? I am NOT running a torified irc client. Also, where's the address 127.0.0.1 coming from? Why is my REAL IP address now invisible (apparently) and tor causing sites to think I am trying to use the illegal localhost IP? praedor Unfortunately, some service providers choose to not accept Tor users as part of their userbase and block connections from exit nodes. That wasn't the question, he was wondering why he was using Tor at all though he told his client not to use it. Praedor: Sure you don't use a proxy in your IRC-client? Also, check - if you're using some flavour of UNIX - if you have some variable like http_proxy set. Alex. signature.asc Description: OpenPGP digital signature
Re: Problems with irc because of tor?
Now I'm really lost on this. Tor quit running (I cannot run tor-0.2.1.7-alpha for more than a couple minutes, so it seems. It just suddenly quits without any errors. It's running then suddenly it isn't. Looks like it is back to the previous version again... That said, tor is down/off and I STILL get the same messages for my IRC client. It seems that simply running tor briefly is enough to bork my IRC client from then on (at least until I reboot)? On Thursday 20 November 2008 16:12:42 Alexander W. Janssen wrote: Sebastian Hahn wrote: -Ursprüngliche Nachricht- Von: Praedor Atrebates [EMAIL PROTECTED] Gesendet: 20.11.08 21:10:08 An: or-talk@freehaven.net Betreff: Problems with irc because of tor? Why does running tor suddenly cause me to be unable to connect to freenode? I am NOT running a torified irc client. Also, where's the address 127.0.0.1 coming from? Why is my REAL IP address now invisible (apparently) and tor causing sites to think I am trying to use the illegal localhost IP? praedor Unfortunately, some service providers choose to not accept Tor users as part of their userbase and block connections from exit nodes. That wasn't the question, he was wondering why he was using Tor at all though he told his client not to use it. Praedor: Sure you don't use a proxy in your IRC-client? Also, check - if you're using some flavour of UNIX - if you have some variable like http_proxy set. Alex.
Re: Problems with irc because of tor?
Praedor Atrebates wrote: Now I'm really lost on this. Tor quit running (I cannot run tor-0.2.1.7-alpha for more than a couple minutes, so it seems. It just suddenly quits without any errors. It's running then suddenly it isn't. OK, that's another thing. Looks like it is back to the previous version again... That said, tor is down/off and I STILL get the same messages for my IRC client. It seems that simply running tor briefly is enough to bork my IRC client from then on (at least until I reboot)? N, no way. A couple of questions: 1) You run some kind of transparent proxy? 2) If not, check if Tor is really disabled. Use ps in UNIX or the Windows Taskmanager to check. Shut down Tor. 3) Check all your IRC-client's settings. To be more precise: 4) What operating system are you using? 5) What IRC-Client are you using? The error-message you're describing is hand-crafted for people who want to use the Freenode-network with Tor. It wouldn't appear for any other users (unless Freenode borked up their scanners). By the way, the message Closing Link: 127.0.0.1 (Banned) seems to indicate that you're using some kind of proxy. If you give us more details, we might be able to help. Alex. signature.asc Description: OpenPGP digital signature
Re: Problems with irc because of tor?
Robert Hogan wrote: Do you run a server yourself? If so, your real IP may be on the irc server's 'tor blocklist'. I don't think so, Freenode wouldn't send the error-message with 127.0.0.1 then, but with his public IP-address. Alex. signature.asc Description: OpenPGP digital signature
Re: Problems with irc because of tor?
On Thu, 2008-11-20 at 22:39 +0100, Alexander W. Janssen wrote: Robert Hogan wrote: Do you run a server yourself? If so, your real IP may be on the irc server's 'tor blocklist'. I don't think so, Freenode wouldn't send the error-message with 127.0.0.1 then, but with his public IP-address. Alex. No, speaking from experience freenode sends 127.0.0.1 if you're on their blacklist, torified or no. They're also very slow to update; I've not been running my exit for some time, but for a long time I was still forced to use the hidden service. I'd probably still be banned if I hadn't had to reboot my router. signature.asc Description: This is a digitally signed message part
Re: Problems with irc because of tor?
I run a relay server only. Never an exit (at least, not for about a year) On Thursday 20 November 2008 16:37:29 Robert Hogan wrote: On Thursday 20 November 2008 21:25:46 Praedor Atrebates wrote: Now I'm really lost on this. Tor quit running (I cannot run tor-0.2.1.7-alpha for more than a couple minutes, so it seems. It just suddenly quits without any errors. It's running then suddenly it isn't. Looks like it is back to the previous version again... That said, tor is down/off and I STILL get the same messages for my IRC client. It seems that simply running tor briefly is enough to bork my IRC client from then on (at least until I reboot)? Do you run a server yourself? If so, your real IP may be on the irc server's 'tor blocklist'. I keep seeing the 127.0.0.1 banned message and wonder where this address is coming from to be mispresented to any outside server or computer. Why is my REAL IP address be sidestepped and my localhost overriding it? I am wondering if there is a tor configuration setting I am missing to prevent tor from presenting 127.0.0.1 as my address.
Re: Problems with irc because of tor?
Sebastian Hahn wrote: Unfortunately, some service providers choose to not accept Tor users as part of their userbase and block connections from exit nodes. That wasn't the question, he was wondering why he was using Tor at all though he told his client not to use it. Sorry I didn't make myself clear, he's not using Tor, freenode is (wrongly) thinking he's using Tor. Sebastian
Re: Problems with irc because of tor?
Ted Smith wrote: On Thu, 2008-11-20 at 22:39 +0100, Alexander W. Janssen wrote: Robert Hogan wrote: Do you run a server yourself? If so, your real IP may be on the irc server's 'tor blocklist'. I don't think so, Freenode wouldn't send the error-message with 127.0.0.1 then, but with his public IP-address. Alex. No, speaking from experience freenode sends 127.0.0.1 if you're on their blacklist, torified or no. They're also very slow to update; I've not been running my exit for some time, but for a long time I was still forced to use the hidden service. I'd probably still be banned if I hadn't had to reboot my router. What blacklist is Freenode using then? Do they run their own? Any chance to check if it's really that? Sounds sensible though... Alex. signature.asc Description: OpenPGP digital signature
