[nos-bbs] Problem attaching tun device

[Maiko Langelaar]

Michael,

I didn't get your callsign, anyways just try out the attached
autoexec.nos (basic JNOS to linux connectivity with telnet).

Replace MMMMMM with your callsign. This is a very simple config
that works very well on any slackware and redhat based systems.

You have to make sure ip forwarding is enabled :

    echo "1" > /proc/sys/net/ipv4/ip_forward

It simply has to work, once you see how it does, then you
can go further with it. There are no ARPs or no IPTABLES or
anything else needed for this basic setup. Try it out.

Maiko
-------------- next part --------------
#
# A minimal autoexec.nos for a JNOS system having network connectivity to
# the linux box on which it is running on. From JNOS you can telnet to the
# linux box, and from the linux box you can telnet to JNOS.
#
# Enable JNOS to log events to dated files in /jnos/logs directory
#
log on
#
# Maximize TCP performance for standard LAN having MTU 1500
#
tcp mss 1460
tcp window 5840
#
tcp maxwait 30000
tcp retries 5
#
ip address 192.168.2.2
#
# Hostname and default ax25 call
#
hostname MMMMMM
ax25 bbscall MMMMMM
ax25 mycall MMMMMM-1
#
# Local DNS is done via the 'domain.txt' file !
#
# 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 192.168.2.2
ifconfig tun0 netmask 255.255.255.0
ifconfig tun0 mtu 1500
#
# 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.
#
pause 1
shell /sbin/ifconfig tun0 192.168.2.1 pointopoint 192.168.2.2 mtu 1500 up
pause 1
#
# Start the engines
#
start telnet
#