[nos-bbs] JNOS routing to TUN0

[Doug Kalish]

I had this same problem until I enabled ip forwarding.  Put into
autoexec.nos, after publishing arp:

 

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

    shell iptables -t nat -A POSTROUTING -o eth0 -s 192.168.27.27 -j
MASQUERADE

 

where eth0 is the public facing interface

 

This enables ip routing only when JNOS is invoked.  You can also do it
permanently if you wish.



-------- Original Message -------- 


Subject: 

Re: [nos-bbs] JNOS routing to TUN0


Date: 

Sat, 16 May 2009 12:24:44 -0400


From: 

Mark Phillips  <mailto:g7ltt at g7ltt.com> <g7ltt at g7ltt.com>


Reply-To: 

g7ltt at g7ltt.com, TAPR xNOS Mailing List  <mailto:nos-bbs at tapr.org>
<nos-bbs at tapr.org>


To: 

TAPR xNOS Mailing List  <mailto:nos-bbs at tapr.org> <nos-bbs at tapr.org>


References: 

 <mailto:5abd436b0905160821y45db0521gabbc82c8459d42a8 at mail.gmail.com>
<5abd436b0905160821y45db0521gabbc82c8459d42a8 at mail.gmail.com>

 

Did you publish your arp?
 
On the Linux box you have to get it to respond to calls addressed to
your JNOS virtual box.
 
What will then happen is that when calls from your JNOS box to your lan
go out the lan device will ask for the hardware address of the JNOS box.
You linux box will offer up its own address and thus the packet flows.
 
 
On Sat, 2009-05-16 at 08:21 -0700, Bill V WA7NWP wrote:
> 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.
> 
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
-- 
 
 
 
Mark Phillips, G7LTT/NI2O
Randolph, NJ
 
 
_______________________________________________
nos-bbs mailing list
nos-bbs at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
 

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.329 / Virus Database: 270.12.32/2117 - Release Date: 05/15/09
17:55:00

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.329 / Virus Database: 270.12.32/2117 - Release Date: 05/15/09
17:55:00

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20090516/c4f2839d/attachment.html>