[iodine-users] Setting Up Iodine on macOS Sierra

[Marcus Poller]

> 10.0.0.1

I find routing easier if the tunnel has an address, that is outside the
range of the WLAN-hot-spot. I decided for 172.19.x.x for my tunnels.

> How connect to proxy via this? I successfully connected to iodine
> server, but don't know what step next.
> I found only 22/tcp open port at 10.0.0.1.

You can do nothing. That is a network route to some machine on the
internet. Unless you intend to exploit the machine...
The owner of the machine could do

    SOCKS_PROXY_PORT=5555
    ssh -D${SOCKS_PROXY_PORT} -n -i mykey.rsa user at 10.0.0.1
    echo "server = 127.0.0.1" |sudo tee -a /etc/tsocks.conf
    echo "server_port = ${SOCKS_PROXY_PORT}" \
       |sudo tee -a /etc/tsocks.conf
    tsocks myproxiedprogramm

Marcus

> 2017-05-12 0:51 GMT+04:00 Marcus Poller <don_sepia at freenet.de>:
> 
> > Dear Orkun,
> >
> > > My server is running at
> > > "t.duman.me" with the password "abc123" and the test page
> > > <http://code.kryo.se/iodine/check-it/> says it's fine. But I
> > > cannot get the client side to connect. This is the client side
> > > log: https://pastebin.com/s5ha9nMu
> >
> > I can connect successfully.
> >
> >  1. Try another DNS-server, you are using Googles 8.8.8.8
> >  2. Whats your servers version and client version? pre 2014 iodine
> > does not work if they missmatch.
> >
> > [2] $ /usr/sbin/iodine -v
> > iodine IP over DNS tunneling client
> > version: 0.7.0 from 2014-06-16
> >
> > [1] $ sudo /usr/sbin/iodine -f -P abc123 t.duman.me
> > Opened dns0
> > Opened IPv6 UDP socket
> > Sending DNS queries for t.duman.me to 2a02:908:2:a::1
> > Autodetecting DNS query type (use -T to override).
> > Using DNS type NULL queries
> > Version ok, both using protocol v 0x00000502. You are user
> > #0
> > Setting IP of dns0 to 10.0.0.2
> > Setting MTU of dns0 to 1130
> > Server tunnel IP is 10.0.0.1
> > Testing raw UDP data to the server (skip with -r)
> > Server is at 172.31.26.18, trying raw login: ....failed
> > Using EDNS0 extension
> > Switching upstream to codec Base128
> > Server switched upstream to codec Base128
> > No alternative downstream codec available, using default (Raw)
> > Switching to lazy mode for low-latency
> > Server switched to lazy mode
> > Autoprobing max downstream fragment size... (skip with -m fragsize)
> > 768 ok.. ...1152 not ok.. ...960 not ok.. 864 ok.. 912 ok.. 936
> > ok.. ...948 not ok.. will use 936-2=934 Setting downstream fragment
> > size to max 934... Connection setup complete, transmitting data.
> >
> > Marcus
> >
> > _______________________________________________
> > iodine-users mailing lists
> > iodine-users at lists.wpkg.org
> > https://lists.wpkg.org/mailman/listinfo/iodine-users
> >