1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

TOR not working in latest shibby (117)?

Discussion in 'Tomato Firmware' started by rs232, Apr 22, 2014.

  1. rs232

    rs232 Network Guru Member

    I admit I haven't use it for sometime but I was giving it a go again today.

    The https://check.torproject.org displays my WAN IP and says that I'm not using tor, where the one below is the relevant part of the logfile:
    Code:
    Apr 22 15:46:27 tomato daemon.notice Tor[3893]: We now have enough directory information to build circuits.
    Apr 22 15:46:27 tomato daemon.notice Tor[3893]: Bootstrapped 80%: Connecting to the Tor network.
    Apr 22 15:46:28 tomato daemon.notice Tor[3893]: Bootstrapped 85%: Finishing handshake with first hop.
    Apr 22 15:46:28 tomato daemon.notice Tor[3893]: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
    Apr 22 15:46:28 tomato daemon.notice Tor[3893]: To correct this, use a version of OpenSSL built with none of its ciphers disabled.
    Apr 22 15:46:28 tomato daemon.notice Tor[3893]: Bootstrapped 90%: Establishing a Tor circuit.
    Apr 22 15:46:29 tomato daemon.notice Tor[3893]: Tor has successfully opened a circuit. Looks like client functionality is working.
    Apr 22 15:46:29 tomato daemon.notice Tor[3893]: Bootstrapped 100%: Done.
    
    Perhaps something related to the recent SSL changes?

    rs232
     
    Last edited: Apr 22, 2014
  2. shibby20

    shibby20 Network Guru Member

    thx, i will look.
     
  3. rs232

    rs232 Network Guru Member

    Also on this topic (perhaps same cause):

    Code:
    Apr 22 12:17:04 tomato daemon.warn Tor[30243]: Rejecting request for anonymous connection to private address [scrubbed] on a TransPort or NATDPort.  Possible loop in your NAT rules?
     

Share This Page