22 Sep
2017
22 Sep
'17
6:48 a.m.
Hi,
I'm moving my 44net connection from an OpenWRT device to a BeagleBone Black, because
I've got a TNCblack to connect directly to a radio.
However, in testing I'm finding the 44net connection doesn't stay up, max about
36hours before a reboot is required.
Any ideas why this is, or how I could diagnose further. The device is always accessible
via the local WiFi connection.
Currently I've just got this tacked onto the end of my rc.local
#Start 44net
/usr/sbin/amprd -d -v 2> /var/log/amprd/amprd_err.log > /var/log/amprd/amprd_std.log
&
sleep 30
ip route add default via 169.228.34.84 dev ampr0 onlink table default
ip rule add from 44.131.170.1 table default
ip rule add from 44.131.170.1 to 44.131.170.0/30 table main
sleep 10
ping -Iampr0 -c10 gw.ampr.org > /dev/null
Device is on m1bkf.ampr.org - sometimes!
Thanks. Bill (M1BKF)
--
Red to red, black to black, switch it on, but stand well back.
22 Sep
22 Sep
11:06 a.m.
Hello Bill;
On Fri, 2017-09-22 at 11:48 +0100, W.B.Hill wrote:
Hi,
I'm moving my 44net connection from an OpenWRT device to a BeagleBone
Black, because I've got a TNCblack to connect directly to a radio.
You may want to review:
http://n1uro.ampr.org/linuxconf/amprcable.html
OpenWRT is one of the systems that can help combat the issue described
on the webpage.
If that doesn't help review:
http://n1uro.ampr.org/linuxconf/dotun.html
In reviewing your info below it appears you may have a policy route
issue combined with being SAFed (Source Address Filtered)
---
I used to be a heavy gambler. But now I just make mental bets.
That's how I lost my mind.
--------
73 de Brian - N1URO/AFT1BR, President - EastNet Packet Network
3:47 p.m.
Those N1URO links are 404.
Ron W6RZ
On 09/22/2017 08:06 AM, Brian wrote:
Hello Bill;
On Fri, 2017-09-22 at 11:48 +0100, W.B.Hill wrote:
Hi,
I'm moving my 44net connection from an OpenWRT device to a BeagleBone
Black, because I've got a TNCblack to connect directly to a radio.
You may
want to review:
http://n1uro.ampr.org/linuxconf/amprcable.html
OpenWRT is one of the systems that can help combat the issue described
on the webpage.
If that doesn't help review:
http://n1uro.ampr.org/linuxconf/dotun.html
In reviewing your info below it appears you may have a policy route
issue combined with being SAFed (Source Address Filtered)
5:04 p.m.
Ron;
On Fri, 2017-09-22 at 12:47 -0700, Ron Economos wrote:
Those N1URO links are 404.
I just tried them from my smartphone and they worked fine.
--
I used to be a heavy gambler. But now I just make mental bets.
That's how I lost my mind.
--------
73 de Brian - N1URO/AFT1BR,
President - EastNet Packet Network
https://www.eastnetpacket.org
email: (see above)
Web: http://www.n1uro.net/
Ampr1: http://n1uro.ampr.org/ (ipv4 AND ipv6)
Ampr2: http://nos.n1uro.ampr.org
Linux Amateur Radio Services
axMail-Fax & URONode
http://uronode.sourceforge.net
http://axmail.sourceforge.net
AmprNet coordinator for:
Connecticut, Delaware, Maine,
Maryland, Massachusetts,
New Hampshire, New Jersey, Pennsylvania,
Rhode Island, and Vermont.
5:26 p.m.
They work from here ok... 73 jerry
-----Original Message-----
From: 44Net
[mailto:44net-bounces+n9lya=uronode.n9lya.ampr.org@mailman.ampr.org] On
Behalf Of Ron Economos
Sent: Friday, September 22, 2017 3:48 PM
To: 44net(a)mailman.ampr.org
Subject: Re: [44net] BeagleBone Black unstable connection.
Those N1URO links are 404.
Ron W6RZ
On 09/22/2017 08:06 AM, Brian wrote:
Hello Bill;
On Fri, 2017-09-22 at 11:48 +0100, W.B.Hill wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
Hi,
I'm moving my 44net connection from an OpenWRT device to a BeagleBone
Black, because I've got a TNCblack to connect directly to a radio.
You may
want to review:
http://n1uro.ampr.org/linuxconf/amprcable.html
OpenWRT is one of the systems that can help combat the issue described
on the webpage.
If that doesn't help review:
http://n1uro.ampr.org/linuxconf/dotun.html
In reviewing your info below it appears you may have a policy route
issue combined with being SAFed (Source Address Filtered)
5:28 p.m.
I guess this is just me. Looking at the wireshark trace, the
n1uro.ampr.net DNS lookup returns 44.88.0.9, but also returns an IPv6
address. My host uses the IPv6 address, which re-directs to
www.eastnetpacket.org.
Ron W6RZ
On 09/22/2017 12:47 PM, Ron Economos wrote:
Those N1URO links are 404.
Ron W6RZ
On 09/22/2017 08:06 AM, Brian wrote:
Hello Bill;
On Fri, 2017-09-22 at 11:48 +0100, W.B.Hill wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
Hi,
I'm moving my 44net connection from an OpenWRT device to a BeagleBone
Black, because I've got a TNCblack to connect directly to a radio.
You may
want to review:
http://n1uro.ampr.org/linuxconf/amprcable.html
OpenWRT is one of the systems that can help combat the issue described
on the webpage.
If that doesn't help review:
http://n1uro.ampr.org/linuxconf/dotun.html
In reviewing your info below it appears you may have a policy route
issue combined with being SAFed (Source Address Filtered)
5:57 p.m.
I get 404 too, and I am IPV6.
Mike KF5JXV
On Fri, Sep 22, 2017 at 3:28 PM, Ron Economos <w6rz(a)comcast.net> wrote:
I guess this is just me. Looking at the wireshark
trace, the
n1uro.ampr.net DNS lookup returns 44.88.0.9, but also returns an IPv6
address. My host uses the IPv6 address, which re-directs to
www.eastnetpacket.org.
Ron W6RZ
On 09/22/2017 12:47 PM, Ron Economos wrote:
Those N1URO links are 404.
Ron W6RZ
On 09/22/2017 08:06 AM, Brian wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
Hello Bill;
On Fri, 2017-09-22 at 11:48 +0100, W.B.Hill wrote:
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
Hi,
I'm moving my 44net connection from an OpenWRT device to a BeagleBone
Black, because I've got a TNCblack to connect directly to a radio.
You may want to review:
http://n1uro.ampr.org/linuxconf/amprcable.html
OpenWRT is one of the systems that can help combat the issue described
on the webpage.
If that doesn't help review:
http://n1uro.ampr.org/linuxconf/dotun.html
In reviewing your info below it appears you may have a policy route
issue combined with being SAFed (Source Address Filtered)
_________________________________________ 
9:35 p.m.
On 23/09/2017 7:57 AM, Mike Nabhan wrote:
I get 404 too, and I am IPV6.
Same here, looks
like an issue with incorrect IPv6 DNS information?
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com
2616
days inactive
2617
days old
7 comments
6 participants
participants (6)
-
Brian -
Jerry -
Mike Nabhan -
Ron Economos -
Tony Langdon -
W.B.Hill