no internet in Incognito... at ALL
Ok.... it would REALLY be appreciated if someone could help me out, I have been trying to get incognito running for 3 days and have yet to load a web page or connect to tor. I've tried it from LiveCD boot and from qemu virtual boot on windows - i've tried both on a wired desktop and a wireless laptop - same deal. the internet and tor work fine on both computers normally through windows, as well as using a live cd boot of ubuntu. incognito is the only one tripping.
I've tried to connect to tor through tork and vidalia and have had no success. both hang, "can't get enough information" type errors, and I have restarted them many times. the clock is set to the correct time. The deeper problem however seems to be with the internet itself; i can't load a single page. knetworkmanager finds and connects to my router just fine (just like windows and ubuntu), but when i open a browser - nothing. I've tried Firefox and Konqueror, both with proxy deselected (direct to internet connection), tork closed and torbutton disabled. konqueror "can't find server" and firefox just shows a yellow triange with an ! symbol and a try again button - no text. I'm not a linux regular but I feel like i've tried everything that I could think of at this point and all I have done is boil the problem down to something within incognito itself. I've searched and searched on this and while the resources for this distro is a bit thin, I managed to find one other guy having a similar issue, who thinks he solved it by upgrading his firmware on his router, which i have also done, and the problem persists. I don't see why it would be a router issue anyway, as everything else on earth connects/passes through it just fine. Lol.... i need help...... dios mio |
Does your router has a firewall?
|
Quote:
Are you normally required to do something special in order to get your Internet connection working, like logging in using some tool or website? A more detailed description of your network setup will help. Please try if restarting Tor (not to be confused with restarting TorK, which is only a monitor for Tor) does anything: Code:
sudo /etc/init.d/tor restart Quote:
Code:
sudo /etc/init.d/iptables stop Of course, this is not a solution, only part of troubleshooting your problem. |
Okay! whew, here's the status:
Code: sudo /etc/init.d/iptables stop ^^ ran this code, tried loading pages with ip addresses, went verrry slow, but eventually turned up those "watered down" version of the pages, like when most of the page content is stripped away and not in the proper font/format and such. I did however test out my wampserver site served from my desktop (using it's local ip), and it loaded/worked perfect. Also... after i did that, I attempted to connect to tor again, and.... it almost worked! lol, it said i was connected in both tork and vidalia, i saw the list of servers in tork, BUT, i still couldn't load any pages through the proxy with torbutton enabled. i tried restarting tor with the other script, then i could only connect through tork, not vidalia, and still no pages. I tried tork in client and local mode, because it had reported once that it was already running. I'm still working on the tor logs, I'm trying to work out how to save them to a windows readable format to transfer with a flash, lol |
Quote:
Quote:
It would also help if you answered the following from my previoius post: Quote:
|
1 - no, i don't have to do anything special to access the internet,
2 - when i said "slow" i meant, a few minutes, go do something else and come back just to see a 10% version of the page content you were loading slow - not regular tor slow 3 - i finally got the logs - i ended up emailing them to myself (<-- explanation in #4), the issue was when i would save them to a flash drive with kedit they would either not appear when i inserted the drive into the windows machine, or it would be unopenable 4 - i think I may have solved the problem, :P as i was fooling with getting the logs over i realized that it still was still reporting the time error. Even though the clock was set to the right time in my timezone, tor was going by some "other" servers clock, and, apparently, that's what it wanted. i pushed it ahead 5 hours, and bing bam shapoopie, it works. i was in qemu mode when i fixed it, and loaded a few pages (pretty slow in qemu), but then for some reason tor dropped out yet again with the "not enough info" error, so i just rebooted into livecd, pushed the clock 5hours, and it hasn't stopped working yet (bout 30min) so i guess the main question is: is this what i was supposed to be doing all allong? is this normal? heres the logs since i booted in livecd mode, guess there wont be much to see here except for me pushing time forward=success near the bottom, lol: 2009-03-26 15:45:19 TorK (1 of 1) Tor can't retrieve a list of all servers on the network yet! 2009-03-26 15:45:20 WARN (1 of 1) Controller gave us config lines that didn't validate: Must set TunnelDirConns if PreferTunneledDirConns is set. 2009-03-26 15:45:20 NOTICE (1 of 1) Closing no-longer-configured OR listener on 0.0.0.0:9001 2009-03-26 15:45:20 NOTICE (1 of 1) Closing no-longer-configured Directory listener on 0.0.0.0:9030 2009-03-26 15:45:20 NOTICE (1 of 1) Closing old OR listener on 0.0.0.0:9001 2009-03-26 15:45:20 NOTICE (1 of 1) Closing old Directory listener on 0.0.0.0:9030 2009-03-26 15:45:39 TorK (1 of 1) Your Broadband Router May Not Be Plug 'n Playable! 2009-03-26 15:46:11 NOTICE (1 of 1) Application request when we're believed to be offline. Optimistically trying directory fetches again. 2009-03-26 15:46:11 NOTICE (1 of 1) No current certificate known for authority moria1; launching request. 2009-03-26 15:46:11 NOTICE (1 of 1) No current certificate known for authority tor26; launching request. 2009-03-26 15:46:11 NOTICE (1 of 1) No current certificate known for authority dizum; launching request. 2009-03-26 15:46:11 NOTICE (1 of 1) No current certificate known for authority ides; launching request. 2009-03-26 15:46:11 NOTICE (1 of 1) No current certificate known for authority gabelmoo; launching request. 2009-03-26 15:46:11 NOTICE (1 of 1) No current certificate known for authority dannenberg; launching request. 2009-03-26 15:46:14 NOTICE (1 of 1) No current certificate known for authority moria1; launching request. 2009-03-26 15:46:14 NOTICE (1 of 1) No current certificate known for authority tor26; launching request. 2009-03-26 15:46:14 NOTICE (1 of 1) No current certificate known for authority dizum; launching request. 2009-03-26 15:46:14 NOTICE (1 of 1) No current certificate known for authority ides; launching request. 2009-03-26 15:46:14 NOTICE (1 of 1) No current certificate known for authority gabelmoo; launching request. 2009-03-26 15:46:14 NOTICE (1 of 1) No current certificate known for authority dannenberg; launching request. 2009-03-26 15:46:14 WARN (1 of 2) Received directory with skewed time (server '86.59.21.38:443'): It seems that our clock is behind by 5 hours, 0 minutes, 2009-03-26 15:46:14 WARN (2 of 2) or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings. 2009-03-26 15:46:14 WARN (1 of 1) 0 unknown, 6 missing key, 0 good, 0 bad, 0 no signature, 4 required 2009-03-26 15:46:14 NOTICE (1 of 1) No current certificate known for authority moria1; launching request. 2009-03-26 15:46:14 NOTICE (1 of 1) No current certificate known for authority tor26; launching request. 2009-03-26 15:46:14 NOTICE (1 of 1) No current certificate known for authority dizum; launching request. 2009-03-26 15:46:14 NOTICE (1 of 1) No current certificate known for authority ides; launching request. 2009-03-26 15:46:14 NOTICE (1 of 1) No current certificate known for authority gabelmoo; launching request. 2009-03-26 15:46:14 NOTICE (1 of 1) No current certificate known for authority dannenberg; launching request. 2009-03-26 15:46:14 NOTICE (1 of 1) I learned some more directory information, but not enough to build a circuit: We have no network-status consensus. 2009-03-26 15:46:14 WARN (1 of 2) Received directory with skewed time (server '86.59.21.38:443'): It seems that our clock is behind by 5 hours, 0 minutes, 2009-03-26 15:46:14 WARN (2 of 2) or that theirs is ahead. Tor requires an accurate clock to work: please check your time and date settings. 2009-03-26 15:46:15 WARN (1 of 2) Our clock is 4 hours, 13 minutes behind the time published in the consensus network status document (2009-03-26 20:00:00 2009-03-26 15:46:15 WARN (2 of 2) GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings! 2009-03-26 15:46:15 NOTICE (1 of 2) I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus 2009-03-26 15:46:15 NOTICE (2 of 2) . 2009-03-26 15:46:16 NOTICE (1 of 1) Application request when we're believed to be offline. Optimistically trying directory fetches again. 2009-03-26 20:47:15 NOTICE (1 of 1) Your system clock just jumped 17997 seconds forward; assuming established circuits no longer work. 2009-03-26 20:47:15 NOTICE (1 of 1) Tried for 18064 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit) 2009-03-26 20:47:15 NOTICE (1 of 1) Tried for 18059 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for circuit) 2009-03-26 20:47:20 NOTICE (1 of 1) I learned some more directory information, but not enough to build a circuit: We have only 96/1354 usable descriptors. 2009-03-26 20:47:21 NOTICE (1 of 1) I learned some more directory information, but not enough to build a circuit: We have only 192/1354 usable descriptors. 2009-03-26 20:47:21 NOTICE (1 of 1) I learned some more directory information, but not enough to build a circuit: We have only 288/1354 usable descriptors. 2009-03-26 20:47:22 NOTICE (1 of 1) We now have enough directory information to build circuits. 2009-03-26 20:47:25 NOTICE (1 of 1) Tor has successfully opened a circuit. Looks like client functionality is working. 2009-03-26 20:47:25 TorK (1 of 1) Tor is ready for use as a client. 2009-03-26 20:47:43 TorK (1 of 1) Your Traffic Can Be Eavesdropped! |
Quote:
Quote:
|
Cool, thanks for all your assistance! as for the direct to internet not working, i'm gathering that this is the nature of incognito? Not to allow any connections of data to be sent without going through tor/proxy?
my oninon stays tiny and red, does something need to be tweaked? should i have a full green onion? also, about the "your data can be eavesdropped!" error on port 80, is this critical? do i need to adjust something for this as well? lastly, how do we go about upgrading? torks telling me new tor is ready, and it's serious business, lol Thanks again |
Quote:
Quote:
Quote:
Quote:
|
Hmmmmm, not even on a persistent usb install?
And what would be a useful feature on a future version - a higher screen resolution option. I have a notebook with a pretty big screen and high res and it would be nice to be able to utilize the extra space, as well as not feel like all of my text and windows and are jumpin off the screen, lol ;) great job, and thanks again! |
Quote:
Quote:
|
All times are GMT -5. The time now is 06:53 AM. |