[nos-bbs] jnos doesn't see the net on new pi sdcard

[Michael Fox - N6MEF]

If your intention is a /30 subnet for tun0, then you've got the wrong host addresses. Network 192.168.0.148/30 would have host addresses 149 and 150.  But if you don't care about aligning on subnet boundaries, then it doesn't matter much for a linux p2p tunnel interface.

You say you can't ping the 44 address of JNOS.  The reason is you have no route to 44.x in your linux routing table below.  Add a route to your JNOS address, next hop of linux end of tun0.

You say you can't ping past the tunnel from JNOS.  I suspect the JNOS routing table is missing a default route with next hop of the linux end of tun0.

Michael
N6MEF

> -----Original Message-----
> From: nos-bbs [mailto:nos-bbs-bounces at tapr.org] On Behalf Of jerome
> schatten
> Sent: Monday, November 6, 2017 8:32 PM
> To: TAPR xNOS Mailing List <nos-bbs at tapr.org>
> Subject: Re: [nos-bbs] jnos doesn't see the net on new pi sdcard
> 
> Bob - thanks for your reply!
> 
> Yes… that is exactly my first thought too, but alas 'cat
> /proc/sys/net/ipv4/ip_forward' yields a ‘1’, so no joy yet.
> 
> Here’s my linux routing table with jnos running:
> 
> pi at raspberrypi1:~ $ route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> default         192.168.0.1     0.0.0.0         UG    202    0        0
> eth0
> 192.168.0.0     *               255.255.255.0   U     202    0        0
> eth0
> 192.168.0.149   *               255.255.255.255 UH    0      0        0
> tun0
> pi at raspberrypi1:~ $
> 
> So my tunnel is .148 and .149 — 149 .  148 is the linux side and 149 is
> the jnos side and in the DMZ. Does anything stand out from this?
> 
> Best,
> jerome
> 
> 
> > On Nov 6, 2017, at 17:39, Boudewijn (Bob) Tenty <bobtenty at gmail.com>
> wrote:
> >
> > It looks like or ipv4 packet forwarding is switched off?
> > Check 'net.ipv4.ip_forward' in /etc/sysctl.conf as it should be one.
> >
> > 73,
> >
> > Bob VE3TOK
> >
> >
> > On 2017-11-06 07:18 PM, jerome schatten wrote:
> >> The SD card on my jnos pi2b has quite a number of file system problems
> now although jnos still works fine.  I thought to fix it, so I tarred up
> the working jnos and put it on a usb stick.  I then made a new SD card
> using the most recent noobs, and then sftp’d the tarred jnos into a jnos
> directory on the new card. Jnos comes up with no errors, however, I no
> longer can ping the router from inside jnos — and thus jnos can’t see the
> net.
> >>
> >> So, in it’s simplest form the problem is: Jnos can’t see the router.
> >>
> >> Pinging around:
> >>
> >> 1. From the linux prompt I can ping both sides of tun0; the address of
> the Pi, and the rest of the world including the router. I cannot ping the
> 44 address of the pi.
> >>
> >> 2. From within jnos, I can ping my 44 address and both sides of tun0,
> and the address of the pi — but as I said, I can’t ping the router. It is
> as I have lost the routing between jnos and linux.
> >>
> >> The new version of raspian jessie (the latest) seems to have changed a
> bit, and I’m hoping I’ve just missed something.  Any ideas are welcome.
> >>
> >> Best,
> >> jerome - ve7ass/va7vv
> >> Vancouver
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> nos-bbs mailing list
> >> nos-bbs at tapr.org
> >> http://www.tapr.org/mailman/listinfo/nos-bbs
> >
> >
> > _______________________________________________
> > nos-bbs mailing list
> > nos-bbs at tapr.org
> > http://www.tapr.org/mailman/listinfo/nos-bbs
> 
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs