Hullo alug,
I've got a computer here at home running debian that gets packages from a remote repository running behind a firewall at work using an openvpn connection. Local address is 192.168.10.6, remote webserver is known as repo.tcl.office. Remote nameserver is 192.168.10.10. Openvpn uses a tunnel of 12.3.3.0.
I have a second computer on my internal network, address assigned as 192.168.1.whatever by the dhcp server (192.168.1.2) that i would very much like to be able to access this repository.
At the moment all the second computer (a balloon-type board) knows is that it is on the network 192.168.1.0 and that its nameserver is 192.168.1.2...not much use to me at all, especially as the nameserver is not on the openvpn and has no idea about tcl.office. I had a try at assigning a static address on the 12.3.3.0 network to no avail, it couldn't ping the computer here on its tun 12.3.3.6 address. Adding various addresses to /etc/resolv.conf on the balloon make no difference.
Is this an impossible mission, or are there any tricks and tools i can be using to make this happen? Running openvpn on the balloon is not an option, alas.
Hints gratefully received.
Thanks,
Jenny