<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.1">
</HEAD>
<BODY>
jerome, if your desired gateway is via RF path to your neighbor you only need tun to permit host & LAN access to jnos.<BR>
it sounds like you are already at that configuration?<BR>
If you want direct internet access across your LAN gateway bridge, there are several models to open your jnos to internet that work, part of the choice of model is based on bridge capacities.<BR>
<BR>
Try these out (Constants - some are assumed by me and need correction by you.):<BR>
jnos IP=44<FONT COLOR="#000000">.135.160.113</FONT><BR>
jnos gateway= 192.168.0.1<BR>
host IP=192.168.0.32 (static is good - DHCP is problematic)<BR>
host /proc/sys/net/ipv4/ip_forward=1<BR>
<FONT COLOR="#000000">LinuxNICMAC</FONT>= (use linux tool kit to list this after boot or read it off the device lable)<BR>
LAN bridge IP=192.168.0.1<BR>
WAN IP=[dynamic]<BR>
Internet domain registered va7vv.no-ip.org (type service)<BR>
<BR>
Config 1: bridge does not masquerade Internet traffic on LAN<BR>
<FONT COLOR="#000000">> tun0=192.168.</FONT>0<FONT COLOR="#000000">.32 pointtopoint </FONT>44<FONT COLOR="#000000">.135.160.113</FONT><BR>
<FONT COLOR="#000000">> h</FONT>ost<FONT COLOR="#000000"> route=</FONT>44<FONT COLOR="#000000">.135.160.113 * tun0</FONT><BR>
<FONT COLOR="#000000">> bridge route=</FONT>44<FONT COLOR="#000000">.135.160.113 gateway </FONT>192.168.0.32<BR>
> bridge pinholes (DMZ) direct to 44<FONT COLOR="#000000">.135.160.113</FONT><BR>
<BR>
Config 2: per Maikos rules for sample install<BR>
<FONT COLOR="#000000">> tun0=192.168.</FONT>2.1<FONT COLOR="#000000"> pointtopoint 192.168.</FONT>2.2<BR>
<FONT COLOR="#000000">> h</FONT>ost<FONT COLOR="#000000"> route=192.168.</FONT>2.2<FONT COLOR="#000000"> * tun0</FONT><BR>
<FONT COLOR="#000000">> bridge route=192.168.</FONT>2.2<FONT COLOR="#000000"> gateway </FONT>192.168.0.32<BR>
> bridge pinholes (DMZ) direct to <FONT COLOR="#000000">192.168.</FONT>2.2<BR>
<BR>
Config 3: bridge masquerades Internet traffic and permits only Class C in-LAN traffic<BR>
<FONT COLOR="#000000">> tun0=</FONT>192.168.0.32<FONT COLOR="#000000"> pointtopoint 192.168.</FONT>0<FONT COLOR="#000000">.3</FONT>3<BR>
<FONT COLOR="#000000">> h</FONT>ost<FONT COLOR="#000000"> </FONT>arp -s 192.168.0.33 <FONT COLOR="#000000"> [LinuxNICMAC] pub</FONT><BR>
> bridge pinholes (DMZ) direct to <FONT COLOR="#000000">192.168.</FONT>0.33<BR>
<BR>
After one of these is in place, <BR>
jnos access to internet is open to DNS, telnet, ping, smtp, encap, etc, services your ISP will permit.<BR>
Internet access to your jnos gateway is for example "...> telnet va7vv.no-ip.org".<BR>
You now have an open door that needs firewalling and access control by you - the price of being public.<BR>
If your ISP serves you with a static IP, then your registration at no-ip is not needed and ampr-gates.org has the scoop.<BR>
<BR>
I know the above is tailored toward what you will read from configuration output instead of configuration command detail.<BR>
I hope my memory permitted me to include everything and you are OK with that & I trust you will fill in that command detail?<BR>
Also for convenience edit /etc/hosts with names and numbers.<BR>
<BR>
Greatest of luck & 73<BR>
<BR>
<BR>
On Tue, 2006-08-08 at 16:56 -0700, jerome schatten last wrote:<BR>
>SNIP<<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de Skip k8rra k<BR>
<BR>
<BR>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>