...

Access TCP services of EVE device (Dom0 side)

This is also similar to the above appliction access, but with Dom0 side of the IP addresses and ports. For example, TCP acces to the 'meta data' services for internal bridges:

• first use 'edgeview.sh socket' to find out which ports Dom0 side listening on

tcp LISTEN 0 1 0.0.0.0:5904 0.0.0.0:* users:(("qemu-system-x86",pid=4192,fd=24))

tcp LISTEN 0 1024 10.1.0.1:80 0.0.0.0:* users:(("zedbox",pid=1903,fd=378))

tcp LISTEN 0 1024 10.3.0.1:80 0.0.0.0:* users:(("zedbox",pid=1903,fd=347))

tcp LISTEN 0 1 0.0.0.0:5905 0.0.0.0:* users:(("qemu-system-x86",pid=4112,fd=24))

• setup TCP channel to both bridge's 'meta data' servers: edgeview.sh tcp/10.1.0.1:80/10.3.0.1:80

tcp mapping locally listening 2 ports to remote:
0.0.0.0:9001 -> 10.1.0.1:80

0.0.0.0:9002 -> 10.3.0.1:80

• open a web browser with 'http://localhost:9001/eve/v1/network.json' to get the external ip address on the device, it returns below in this example:

{"caller-ip":"10.1.0.1:57152","external-ipv4":"192.168.86.36","hostname":""}

Proxy Command

Copy Files Command

...