<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
Run the command "tail -f /var/syslog" in one terminal while you
(re)start jnos in another shell.<br>
You will see an error logged in syslog right away.<br></div></blockquote><div><br>Ah, no... it just sits there. (Actually in my case the command has to be "tail -f /var/log/syslog".)<br></div></div><br>But I snuck a bit of code into tun.c to log the value of errno along with the "unable to setup tunnel" message, and got "1" (EPERM). And I found in the nos-bbs archive that there's a message in this thread from Pascal VE2HOM (which never showed up in my Gmail client, hmm) saying that one needs to be root to attach the tun device.<br>
<br>So I ran jnos as "sudo ~/bin/jnos", and the error message went away.<br><br>(Um, so, did I miss this point in the documentation? I don't recall seeing anything until VE2HOM's post suggesting that I need to run jnos as root.)<br>
<br>*Anyway*, pressing on to configuring the linux side of the tunnel, *NOW* is when I start to get messages in syslog:<br><br><span style="font-family:courier new,monospace">Feb 23 21:42:08 linuxbox avahi-daemon[692]: Withdrawing workstation service for tun0.</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">Feb 23 21:42:08 linuxbox NetworkManager[691]: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/tun0, iface: tun0)</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">Feb 23 21:42:23 linuxbox modem-manager: (net/tun0): could not get port's parent device</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">Feb 23 21:42:23 linuxbox NetworkManager[691]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/tun0, iface: tun0)</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">Feb 23 21:42:23 linuxbox NetworkManager[691]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found.</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">Feb 23 21:42:23 linuxbox kernel: [458309.056830] tun0: Disabled Privacy Extensions</span><br><br>That "no ifupdown configuration found" message doesn't look too good to me.<br>
<br>And, of course, attempting to telnet to the IP address on the jnos end of the tunnel fails with "telnet: Unable to connect to remote host: Connection refused".<br><br>For what it's worth, the relevant commands in my autoexec.nos are:<br>
<br><span style="font-family:courier new,monospace">ip address 192.168.1.67</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">attach tun tun0 1500 0</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">ifconfig tun0 ipaddress 192.168.1.67</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">ifconfig tun0 netmask 255.255.255.0</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">ifconfig tun0 mtu 1500</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">pause 1</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">shell ifconfig tun0 192.168.1.68 pointopoint 192.168.1.67 mtu 1500 up</span><br style="font-family:courier new,monospace">
<style type="text/css">p { margin-bottom: 0.08in; }</style><font style="font-family:courier new,monospace" face="Courier New, monospace"><font>route
addprivate default tun0</font></font>
<br><br>And here's what (linux) "ifconfig tun0" reports:<br><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 </span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> inet addr:192.168.1.68 P-t-P:192.168.1.67 Mask:255.255.255.255</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> RX packets:1 errors:0 dropped:0 overruns:0 frame:0</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"> TX packets:1 errors:0 dropped:0 overruns:0 carrier:0</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> collisions:0 txqueuelen:500 </span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"> RX bytes:40 (40.0 B) TX bytes:60 (60.0 B)</span><br>
<br>The "Link encap: UNSPEC" part also looks a little suspicious...<br><br>(I suppose it might help if I had some idea what any of this meant! :-)<br><br>M<br>-- <br>This cat is pushing a watermelon out of a lake. Your argument is invalid.<br>
<br>