search

SadeghHayeri / GreenTunnel

GreenTunnel is an anti-censorship utility designed to bypass the DPI system that is put in place by various ISPs to block access to certain websites.
MIT License
4.38k stars 277 forks source link

Green Tunnel makes my router web interface shows code 404 in certain page #44

Open pc-v2 opened 4 years ago

pc-v2 commented 4 years ago

Describe the bug i can't access some settings in my router

To Reproduce Steps to reproduce the behavior:

  1. run green-tunnel
  2. open router address
  3. click some page
  4. 404

Expected behavior No 404 in router settings

Desktop (please complete the following information):

Screenshot Screenshot-from-2019-12-02-16-46-03.png

SadeghHayeri commented 4 years ago

can you show your network (inspect elements) or run green-tunnel in terminal using -v 'green-tunnel:*' option?

pc-v2 commented 4 years ago

sadly, i came back to windows because of this :(

pc-v2 commented 4 years ago

will try in vm

pc-v2 commented 4 years ago

green-tunnel:proxy server listen on 127.0.0.1 port 8000 +0ms green-tunnel:proxy system proxy set +54ms green-tunnel:https-handler [HTTP REQUEST] 192.168.1.1 +0ms green-tunnel:dns [DNS] 192.168.1.1 -> 192.168.1.1 (0 ms) +0ms green-tunnel:socket [Socket] connected to 192.168.1.1 (192.168.1.1) (2 ms) +0ms green-tunnel:https-handler [HTTPS REQUEST] tiles.services.mozilla.com +0ms green-tunnel:https-handler [HTTP REQUEST] 192.168.1.1 +185ms green-tunnel:https-handler [HTTP REQUEST] 192.168.1.1 +1ms green-tunnel:socket [Socket] connected to 192.168.1.1 (192.168.1.1) (1 ms) +182ms green-tunnel:socket [Socket] connected to 192.168.1.1 (192.168.1.1) (1 ms) +1ms green-tunnel:https-handler [HTTP REQUEST] 192.168.1.1 +73ms green-tunnel:socket [Socket] connected to 192.168.1.1 (192.168.1.1) (2 ms) +74ms green-tunnel:dns [DNS] tiles.services.mozilla.com -> 52.39.224.180 (223 ms) +318ms green-tunnel:socket [Socket] connected to tiles.services.mozilla.com (52.39.224.180) (230 ms) +289ms green-tunnel:https-handler [HTTPS HELLO] tiles.services.mozilla.com (length: 100) +456ms green-tunnel:https-handler [HTTPS HELLO] tiles.services.mozilla.com (length: 100) +0ms green-tunnel:https-handler [HTTPS HELLO] tiles.services.mozilla.com (length: 100) +1ms green-tunnel:https-handler [HTTPS HELLO] tiles.services.mozilla.com (length: 100) +0ms green-tunnel:https-handler [HTTPS HELLO] tiles.services.mozilla.com (length: 100) +0ms green-tunnel:https-handler [HTTPS HELLO] tiles.services.mozilla.com (length: 17) +0ms green-tunnel:https-handler [HTTPS] receive from tiles.services.mozilla.com (length: 3014) +461ms green-tunnel:https-handler [HTTPS] send to tiles.services.mozilla.com (length: 126) +4ms green-tunnel:https-handler [HTTPS] send to tiles.services.mozilla.com (length: 1106) +1ms green-tunnel:https-handler [HTTPS] receive from tiles.services.mozilla.com (length: 51) +234ms green-tunnel:https-handler [HTTPS] receive from tiles.services.mozilla.com (length: 255) +238ms green-tunnel:https-handler [HTTP REQUEST] 192.168.1.1 +15s green-tunnel:socket [Socket] connected to 192.168.1.1 (192.168.1.1) (1 ms) +14s green-tunnel:https-handler [HTTP REQUEST] 192.168.1.1 +2s green-tunnel:socket [Socket] connected to 192.168.1.1 (192.168.1.1) (1 ms) +2s green-tunnel:https-handler [HTTP REQUEST] 192.168.1.1 +5s green-tunnel:socket [Socket] connected to 192.168.1.1 (192.168.1.1) (1 ms) +5s green-tunnel:https-handler [HTTP REQUEST] 192.168.1.1 +15s green-tunnel:socket [Socket] connected to 192.168.1.1 (192.168.1.1) (1 ms) +15s green-tunnel:https-handler [HTTPS] receive from tiles.services.mozilla.com (length: 31) +1m green-tunnel:https-handler [HTTPS] send to tiles.services.mozilla.com (length: 31) +1ms green-tunnel:https-handler [HTTPS END] client ended tiles.services.mozilla.com +0ms green-tunnel:https-handler [HTTPS END] server ended tiles.services.mozilla.com +235ms

pc-v2 commented 4 years ago

Request URL:http://192.168.1.1/getpage.gch?pid=1002&nextpage=IPv46_net_wan2_conf_t.gch Request method:GET Remote address:127.0.0.1:8000 Status code: 404 Version:HTTP/1.1 Referrer Policy:no-referrer-when-downgrade

ardinusawan commented 4 years ago

I got same error. The easiest ways is to put your router IP on the exception not to use http proxy