[nos-bbs] No network connectivity
bobtenty at gmail.com
Fri May 8 02:59:30 EDT 2009
I miss a default route to the linux kernel in the autoexec.nos
route add default tun0
Restart jnos after adding that line.
Can you ping jnos now from the linux shell?
Realize also that it is better if your get a 44 address so that
you can set "ip address" to that instead as the host ka3l-1.ampr.org
doesn't resolve in the dns.
(the range 44.128/16 can be used for test purposes in the mean time)
For hosts not registered in the dns add them to the domain.txt
Also look for the ipv4 forwarding line in /etc/sysctl.conf
so that jnos can be reached from the lan.
Remove the '#' in front of it.
With the linux command: sysctl -p you can reload sysctl.conf
doug at kalish.com wrote:
> Hi Guys: I'm new to this list and new to JNOS so please bear with me. I've
> got JNOS 2.0f running on the Spring 2009 distro of Mandriva. The BBS is
> running and I can log in over RF and send and retrieve mail. From the jnos
> console however I don't seem to be connected to linux, ie "ping
> 192.168.0.100" results in 'Trying to resolve 192.168.0.100". So I don't
> have network connectivity. I'm using the bare bones autoexec.nos (see below).
> Any help would be appreciated. Also, anybody on this list in the SF Bay
> Area who is willing to mentor me through this process, I'd appreciate it
> Doug KA3L
> # 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. Any packet radio
> # users can connect to JNOS through the single RF port which can be any TNC
> # running in KISS mode. This configuration also allows JNOS users to exchange
> # mail with other JNOS users (local mail), using the Send and Receive cmds.
> # The jnosinstaller was designed for first time JNOS users, giving them
> # something to start playing with.
> # This autoexec.nos was GENERATED by jnosinstaller (version 2.1), which was
> # released in January of 2008. The original version was written in July of
> # the year 2005 - both versions written by Maiko Langelaar / VE4KLM.
> # 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 ka3l-1
> ax25 mycall ka3l-1
> # Local DNS is done via the 'domain.txt' file !
> domain addserver 22.214.171.124
> domain addserver 126.96.36.199
> # 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
> # Give it a chance to come up
> pause 1
> # 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 192.168.0.109 pointopoint 192.168.2.2 mtu 1500 up
> pause 3
> shell /sbin/arp -s 192.168.2.2 00:40:CA:28:76:9C pub
> pause 2
> # Attach a kiss enabled TNC
> attach asy ttyS0 - ax25 vhf 4096 256 9600
> ifconfig vhf description "vhf - 1200 baud port"
> param vhf 2 256
> param vhf 3 1
> param vhf 5 1
> param vhf TxDelay 25
> # Beacon out the RF port every 20 minutes
> ax25 bctext "KA3L Test JNOS internet gateway"
> ax25 bcinterval 1200
> ax25 bc vhf
> # Start the engines
> start ax25
> start telnet
> start smtp
> #route add default vhf direct
> route add 188.8.131.52 vhf direct
> # Put modem into KISS mode
> comm vhf "kiss on"
> comm vhf "restart"
> # Don't verify mbox send; for Outpost compatibility
> mbox sendquery off
> mbox register off
> nos-bbs mailing list
> nos-bbs at tapr.org
More information about the nos-bbs