[nos-bbs] No network connectivity

[Bob Tenty]

Your tunnel is working otherwise you can't ping jnos from the linux side

Is no firewall rule in linux blocking it?
A lot of incoming stuff maybe blocked by default in the latest distros.

Can you ping your machine at its ethernet ip  address (192.168.0.109) from
another machine at your lan?


73,

Bob VE3TOK


doug at kalish.com wrote:
> I think that the problem must be in how the tunnel is set up.  From my 
> autoexec.nos, I am executing these lines:
>
> shell ifconfig tun0 192.168.0.109 pointopoint 44.4.14.128 mtu 1500 up
> pause 3                                                                    
> shell /sbin/arp -s 44.4.14.128 00:40:CA:28:76:9C pub                      
> pause 2
>
> Also:
> route add default tun0
>
>
>  From the jnos console:
> jnos> domain list
> Server address          srtt    mdev    timeout  queries responses timeouts
> 44.4.14.128            15000       0     15000         0         0         0
> 68.87.78.130           15000       0     15000         0         0         0
> 68.87.76.178           15000       0     15000         0         0         0
> jnos> route look 192.168.0.100
> Destination      Len Interface Gateway          Metric P Timer  Use
> default          0   tun0                       1        man    0
> jnos> ping 192.168.0.100
> jnos> Resolving 192.168.0.100...
>
> ...and it never pings.  So it is looking at the correct interface, but the name 
> never resolves.
>
>  From the linux console:
> [root at localhost jnos]# ifconfig tun0
> tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>           inet addr:192.168.0.109  P-t-P:44.4.14.128  Mask:255.255.255.255
>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>           RX packets:2 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:500
>           RX bytes:64 (64.0 b)  TX bytes:120 (120.0 b)
>
>
> I'm just not familiar enough with tunneling to know what's going on.  Any ideas?
>
> Doug KA3L
>
>