[nos-bbs] JNOS routing to TUN0

[Bill V WA7NWP]

Good morning...

Sun's out in Seattle, it's warm, the lawn and the weeds are growing
like crazy -- so it's obviously a good day to stay in and do some JNOS
work.


I'm setting up my first TUN interface.   The point-to-point connection
between the host linux system and JNOS2.0f is working fine.  At least
the PING is working.

I've used Maiko's basic setup as a start:

---
autoexec.nos:

  ip address 192.168.27.27

  attach tun tun0 1500 0

  ifconfig tun0 ipaddress 192.168.27.27
  ifconfig tun0 netmask 255.255.255.0
  ifconfig tun0 mtu 1500

  pause 1

  shell ifconfig tun0 192.168.27.33 pointtopoint 192.168.27.27 mtu 1500 up

----

The LAN address for the linux host is 192.168.27.33.
The JNOS instance is 192.168.27.27.


The netmask on tun0 implies that interface should be able to contact
any station on the 192.168.27 LAN..

Sending a ping to 192.168.27.6  -- the windows box running the BPQ32
node -- shows an outgoing ICMP Echo Request on tun0 as expected.

No reply.   Likewise on the windows box, a ping to 192.168.27.27
(JNOS) doesn't appear on TUN0.

In the old SLattach setup, I'd have hard coded a proxy ARP and route
statement on Linux so it would look for the JNOS packets and forward
them.  I'd also have to enable IP forwarding in the /proc system.

This leads to the primary query of this posting - Is the proxy ARP and
IP forwarding still necessary with TUN or is there another mechanism?

Once I get IP working between JNOS and other LAN systems, I'm assuming
it's a simple matter of adding the route default entries to open up
the network connectivity.

Thanks and 73...
Bill - WA7NWP

PS.  I'm not really going to stay inside today.    The rain comes back
Monday so there's lots to be done before then.

PPS.   A sunny weekend and rainy work week is just plain scary...
Normally it's the other way.