[nos-bbs] No network connectivity

[Jay Nugent]

Greetings,

On Sun, 10 May 2009, Doug Kalish wrote:

> You were right.  The current Mandriva distro blocks a lot of incoming stuff
> and I couldn't ping 109 from the lan.  But I opened up the firewall
> completely, the lan pings work now and I'm still not able to resolve
> 192.168.0.109 from jnos...

   Gotta think like a packet....  In *BOTH* directions.   

   Okay, you confirmed that you have a route from the JNOS application
going to the Linux IP stack.  But you've said nothing about whether you
have a route in the other direction.

   Does the Linux route table have a route to JNOS via the tunnel?

   Add a route for 44/8 via the TUN0 interface.


      --- Jay Nugent  WB8TKL
   


> -----Original Message-----
> From: Bob Tenty [mailto:bobtenty at gmail.com] 
> Sent: Sunday, May 10, 2009 12:03 AM
> To: kalish.doug at gmail.com; TAPR xNOS Mailing List
> Subject: Re: [nos-bbs] No network connectivity
> 
> 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
> >
> >   
> 
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.5.325 / Virus Database: 270.12.22/2105 - Release Date: 05/09/09
> 06:54:00
> 
> 
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
> 

             
Train how you will Operate, and you will Operate how you were Trained.
+------------------------------------------------------------------------+
| Jay Nugent   jjn at nuge.com    (734)484-5105    (734)649-0850/Cell       |
|   Nugent Telecommunications  [www.nuge.com]                            |
|   Internet Consulting/Linux SysAdmin/Engineering & Design/ISP Reseller |
| ISP Monitoring [www.ispmonitor.org] ISP & Modem Performance Monitoring |
| Web-Pegasus    [www.webpegasus.com] Web Hosting/DNS Hosting/Shell Accts|
+------------------------------------------------------------------------+
  2:01pm  up 32 days, 13:17,  4 users,  load average: 0.00, 0.02, 0.00