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

Tue Nov 7 21:04:18 EST 2017

Jeremy,

I don't know your situation of course but I assume Linux in your PI has also a 44 address and you can use that
also for the Linux side of your tun0 interface to jnos with its own 44 address.

For example in my case,

shell ifconfig tun0 44.135.85.151 pointopoint 44.135.85.30 mtu 1500 up

I'm running the ax25 utilities so Linux has already 44.135.85.151 of one of the interfaces.
You can use also one of your unused 44 address if Linux has no 44 address yet.

73,

Bob VE3TOK

On 2017-11-07 06:28 PM, jerome schatten wrote:
> Bob… are you suggesting that the DMZ end of the tunnel remains at .149 and the linux side uses my jnos 44 address?
> Best,
> jerome
> ve7ass
>
>> On Nov 7, 2017, at 12:10, Boudewijn (Bob) Tenty <bobtenty at gmail.com> wrote:
>>
>> Hi Jerome,
>>
>> I see no amprnet routing. The best is to use a 44 address only in jnos and to use the linux and jnos 44 addresses
>> for the tunnel setup from within jnos.
>>
>> 73,
>>
>> Bob VE3TOK
>>
>> On 2017-11-06 11:31 PM, jerome schatten wrote:
>>> 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