pikers
/
piker
3
0
Fork 0
Code Issues 2 Pull Requests 4 Packages Projects Releases Wiki Activity
piker/dockering/ib
History
Tyler Goodlet 06832b94d4 Add vnc password auth, connection reset logic 
Now that we have working client auth thanks to:
https://github.com/barneygale/asyncvnc/pull/4 and related issue,
we can use a pw for the vnc server, though we should eventually
auto-generate a random one from a docker super obviously.

Add logic to the data reset hack loop to do a connection reset after
2 failed/timeout attempts at the regular data reset. We need to also add
this logic around reconnectionn events that are due to the host
network connection: aka roaming that's faster then timing logic
builtin to the gateway.
 		2022-06-04 20:44:03 -04:00
..
README.rst Add readme for `ib-gw` container usage 2022-06-04 20:18:29 -04:00
docker-compose.yml Comment unneeded port map for now 2022-06-03 10:21:29 -04:00
fork_ports_delayed.sh Add working, template docker setup for `ib-gw` 2022-05-21 14:22:11 -04:00
ibc.ini Only bind IBC command server to localhost 2022-06-03 10:21:37 -04:00
jts.ini Flip tz to NY, add note about .env file 2022-05-24 09:29:35 -04:00
run_x11_vnc.sh Add vnc password auth, connection reset logic 2022-06-04 20:44:03 -04:00

README.rst

running ib gateway in docker

We have a config based on the (now defunct) image from "waytrade":

https://github.com/waytrade/ib-gateway-docker

To startup this image with our custom settings simply run the command:

docker compose up

And you should have the following socket-available services:

  • x11vnc1@127.0.0.1:3003
  • ib-gw@127.0.0.1:4002

You can attach to the container via a VNC client without password auth.

SECURITY STUFF!?!?!

Though "ib" claims they host filter connections outside localhost (aka 127.0.0.1) it's probably better if you filter the socket at the OS level using a stateless firewall rule:

ip rule add not unicast iif lo to 0.0.0.0/0 dport 4002

We will soon have this baked into our own custom image but for now you'll have to do it urself dawgy.