[nos-bbs] Problem attaching tun device
Michael Curry
dgspotman at gmail.com
Fri Feb 24 13:09:46 EST 2012
A few other bits of info:
On the jnos side, the log now contains the messages
21:59:00 - using new [tun0] device
21:59:00 - tun_rx - listening for packets
where the "unable to setup tunnel" had been.
An additional command that's in my autoexec.nos, but that I failed to
document in my last post, is:
start telnet
This is after all the other commands that I did document (actually, all the
way at the end of my autoexec.nos file -- which is why I missed it last
time).
On the jnos side, "ifconfig tun0" shows packets sent and received -- in
fact, one more in each direction than the number of telnet attempts made
from the linux side. For example, this is the output after three telnet
attempts.
tun0 IP addr 192.168.1.67 MTU 1500 Link encap TUN
flags 0x0 trace 0x0 netmask 0x00000255 broadcast 0.0.0.0
sent: ip 4 tot 4 idle 0:00:00:17
recv: ip 4 tot 4 idle 0:00:00:17
On the linux side, each attempt to telnet to the IP address of the jnos end
of the tunnel increments both the "TX bytes" and "RX bytes" reported by
ifconfig for the tun0 interface (by 60 and 40, respectively). This is the
output of "ifconfig tun0" after three telnet attempts:
tun0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.1.68 P-t-P:192.168.1.67 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:160 (160.0 B) TX bytes:240 (240.0 B)
So both sides seem to agree that packets are flowing between them, but
apparently not the right ones to result in a proper telnet connection.
Any ideas what to try next? Thanks for all the feedback so far!
M
--
This cat is pushing a watermelon out of a lake. Your argument is invalid.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20120224/7382583d/attachment.html>
More information about the nos-bbs
mailing list