Commit Graph

18 Commits

Author SHA1 Message Date
a485e3d9eb Move send.py and fix it up for use docker to test direct requests to i2p HTTP proxy
#1 - Forward using iptables, pr0xy and custom DNS
2019-07-27 21:37:25 +02:00
09597a2703 Remove trailing '.' from the hostname passed from DNS request
#1 - Forward using iptables, pr0xy and custom DNS
2019-07-27 21:36:17 +02:00
221d2641d4 Handle requests to unix socket better and log errors
#1 - Forward using iptables, pr0xy and custom DNS
2019-07-27 21:35:35 +02:00
88bf17ca8c Try to shutdown the UnixSocketServer when our program exits
Also add logging

#1 - Forward using iptables, pr0xy and custom DNS
2019-07-27 21:34:45 +02:00
e04e2989e5 Redirect traffic to NFQUEUE
Right now all it does is print the packet payload. Need to find out wtf
 that actually is and how to treat it

#1 - Forward using iptables, pr0xy and custom DNS
2019-07-27 00:08:35 +02:00
25525d2ae6 Add simple netfilter script with its dependencies
- python requirements are now kept in a file and installed during build
 - variables are used in exec.sh to remove magic values
 - executable scripts are moved into one directory

#1 - Forward using iptables, pr0xy and custom DNS
2019-07-27 00:07:09 +02:00
7f739bcdc7 A first implementation of FakeDNSServer
It will return random IPs for unique requests e.g
```
$ dig @localhost -p 1053 idontactuallyexist.test

; <<>> DiG 9.11.3-1ubuntu1.8-Ubuntu <<>> @localhost -p 1053
idontactuallyexist.test
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53511
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL:
0

;; QUESTION SECTION:
;idontactuallyexist.test.       IN      A

;; ANSWER SECTION:
idontactuallyexist.test. 0      IN      A       172.57.143.249

;; Query time: 6 msec
;; SERVER: 127.0.0.1#1053(127.0.0.1)
;; WHEN: Fri Jul 26 00:42:18 CEST 2019
;; MSG SIZE  rcvd: 57
```

 #1 - Forward using iptables, pr0xy and custom DNS
2019-07-26 00:40:47 +02:00
eee72c25ba Remove unnecessary lines
#1 - Forward using iptables, pr0xy and custom DNS
2019-07-26 00:33:16 +02:00
ddd3f03275 Start documenting exec.sh a bit
#1 - Forward using iptables, pr0xy and custom DNS
2019-07-26 00:31:55 +02:00
8be3ff02ac Move contents for contained image into contained dir
We don't wanna pollute the root dir with files pertaining
 to the contained image

 #1 - Forward using iptables, pr0xy and custom DNS
2019-07-24 13:41:57 +02:00
0663e4dcb3 Simple python script testing CONNECT HTTP tunnel
When sending messages to HTTP servers operated by I2P
 one has to use the MYOB User-Agent for some reason.
 Otherwise the requests are rejected with 403

 #1 - Figure out why packets aren't being forwarded using iptables and pr0xy
2019-07-22 17:47:28 +02:00
fbc94448d0 Add docker-compose to requirements
#1 - Figure out why packets aren't being forwarded using iptables and pr0xy
2019-07-22 17:46:35 +02:00
31d716beaf Trying to make curl stats.i2p work
- Log the packet filtering
 - dump the packets from all interfaces

 #1 Figure out why packets aren't being forwarded using iptables and pr0xy
2019-07-22 17:43:15 +02:00
4a0d4d24b6 Attempt at forwarding all traffic through an HTTP proxy
DNS doesn't work so there was an attempt at just forcing
 stats.i2p to localhost, with no success.

A tcpdump is created on the host machine at /tmp/contained/tcp.dmp
 to try and figure out what is being sent where, but
 it doesn't seem like any HTTP traffice is being sent at all.

`iptables` is logged to /var/log/ so maybe that'll give a hint
 as to where the stuff is going.
Maybe the rules are just bad too 🤷‍♂
2019-07-20 21:25:00 +02:00
11dcd76749 Fix link in README 2019-07-20 10:46:47 +00:00
7857298892 Start listing possibilities 2019-07-20 10:45:21 +00:00
7eff81a0f2 Add LICENSE 2019-07-20 10:12:06 +00:00
0d55605885 Initial commit 2019-07-20 10:11:48 +00:00