... I should add that all I describe here is being done on a single machine, i.e. locally. <br><br><div class="gmail_quote">On Sat, Aug 6, 2011 at 5:55 PM, neil rabinowitz <span dir="ltr"><<a href="mailto:neil.rabinowitz@merton.ox.ac.uk">neil.rabinowitz@merton.ox.ac.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I'm still trying to figure out this local vs remote kernel story. Aside
from my ssh question below, can someone offer an explanation/example of how i
set up and connect to a remote kernel (on linux), even if unsecured? The most I can find is from the ipython_qtconsole_config.py file:<br><br># Set the kernel's IP address [default localhost]. If the IP address is <br>
# something other than localhost, then Consoles on other machines will be able <br># to connect to the Kernel, so be careful! <br># c.IPythonQtConsoleApp.ip = '127.0.0.1' <br>
<br>If I try to specify my network-facing interface IP with a flag, e.g.:<br>ipython qtconsole --ip=192.168.X.X<br><br>then it fails, printing a stack and the following:<br><br>RuntimeError: Can only launch a kernel on a local interface. Make sure that the '*_address' attributes are configured properly. Currently valid addresses are: ['127.0.0.1', '127.0.1.1', '0.0.0.0', '']<br>
<br>Following the documentation that 0.0.0.0 opens up the kernel to all interfaces, I try launching ipython with the ip tag set to 0.0.0.0, which does indeed launch a console. However, I can't then seem to connect to this instance anyway I try. The usual method (launching a new instance with the "--existing ..." flags) brings up a qtconsole, displaying the usual headers, but no prompt ever appears. The same is true if I append the extra flags to the second qtconsole of --ip=0.0.0.0 or --ip=192.168.1.2 and so on -- just a promptless console.<br>
<br>Is there a simple syntactical trick I'm missing, or is my use case is not what this system is designed for?<br><br>Thanks<br><font color="#888888">Neil</font><div><div></div><div class="h5"><br><br><br><div class="gmail_quote">
On Thu, Aug 4, 2011 at 9:48 PM, neil rabinowitz <span dir="ltr"><<a href="mailto:neil.rabinowitz@merton.ox.ac.uk" target="_blank">neil.rabinowitz@merton.ox.ac.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hello<br><br>firstly, much credit is due to all who have contributed to the 0.11 release. i've been migrating the last couple of days, and i'm impressed with all you've done.<br>
<br>i'm trying to have a play around with the client/kernel architecture. in particular, i usually run instances of python on my lab server, which i access remotely via ssh (e.g. from elsewhere in the lab or at home). i'm wondering what is the standard protocol for securely connecting a qt console client to a remote kernel -- i can't seem to find appropriate documentation. could someone please point me in the appropriate direction?<br>
<br>best<br><font color="#888888">neil<br>
</font></blockquote></div><br>
</div></div></blockquote></div><br>