[nos-bbs] TUN0 addressing w/JNOS atop Linux

[Jay Nugent]

Greetings,
   Okay, I give up!  Someone who has *ACTUALLY* done this, please explain
to me how to set up the TUN0 addressing *and* the route table that needs
to be built on the linux side.

   A friend insists on running JNOS2.0d on Linux.  He's been 4 MONTHS
trying to get it to run.  Is there any wonder why I told him to trash the
idea and just keep it simple and run JNOS on DOS.  Sweet. clean and
simple.  He could have been up and operational in 20 minutes!
  
   Now I've been pulled into the mess to try to figure out what he has 
done wrong, and/or how it should be done right.

   This box will be configured as a HamGate, so his Public IP on his eth0
interface (216.144.222.182) *MUST* be delivered to the JNOS application
because he *will* be running IPIP encapsulation to all the other HamGates
across the world and this IP is what's published in encap.txt.

   This is how he has it set up (which doesn't work):


    JNOS application
      44.102.128.1
           |
           | TUN0
           |
      44.102.128.1  P-t-P 192.168.2.2

His route table on Linux:
=========================
Destination     Gateway         Genmask         Flags Metric Ref Use Iface
192.168.2.2     0.0.0.0         255.255.255.255 UH    0      0     0 tun0
216.144.222.176 0.0.0.0         255.255.255.248 U     0      0     0 eth0
0.0.0.0         216.144.222.177 0.0.0.0         UG    0      0     0 eth0

Ifconfig eth0:
==============
eth0 Link encap:Ethernet  HWaddr 00:20:78:1D:99:8B
     inet addr:216.144.222.182  Bcast:216.144.222.183 Mask:255.255.255.248
     inet6 addr: fe80::220:78ff:fe1d:998b/64 Scope:Link
     UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
     RX packets:13285 errors:0 dropped:0 overruns:0 frame:0
     TX packets:5245 errors:0 dropped:0 overruns:0 carrier:0
     collisions:1 txqueuelen:1000
     RX bytes:1043289 (1018.8 KiB)  TX bytes:696201 (679.8 KiB)
     Interrupt:10 Base address:0x8000



   NO traffic EVER goes up the TUN0 interface....


Pertinent parts of his autoexec.nos:
====================================
#
ip address 44.102.128.1
#
# Create a network interface. This allows us to talk to the linux
# box on which JNOS is running - and in turn - to the internet.
#--------------------------
attach tun tun0 1500 0
#
ifconfig tun0 ipaddress 44.102.128.1
ifconfig tun0 netmask 255.255.255.0
ifconfig tun0 mtu 1500
#
# Give it a chance to come up
pause 3
#
# JNOS creates the TUN device, so JNOS needs to do some post
# configuration, by shelling out to the linux command line and
# running 'ifconfig' command.
shell ifconfig tun0 44.102.128.1 pointopoint 192.168.2.2 mtu 1500 up
#


   Any suggestions where he went wrong?

   Thanks!

      --- Jay Nugent  WB8TKL

"Those that sacrifice essential liberty to obtain a little temporary safety
 deserve neither liberty nor safety."  -- Ben Franklin (1759) 
+------------------------------------------------------------------------+
| Jay Nugent   jjn at nuge.com    (734)484-5105    (734)544-4326/Fax        |
| Nugent Telecommunications  [www.nuge.com]     (734)649-0850/Cell       |
|   Internet Consulting/Linux SysAdmin/Engineering & Design/ISP Reseller |
| ISP Monitoring [www.ispmonitor.net] ISP & Modem Performance Monitoring |
| Web-Pegasus    [www.webpegasus.com] Web Hosting/DNS Hosting/Shell Accts|
| LinuxNIC, Inc. [www.linuxnic.net]   Registrar of the .linux TLD        |
+------------------------------------------------------------------------+
  3:01am  up 3 days,  1:42,  4 users,  load average: 0.00, 0.01, 0.00