It turns out that the problem was with one of Forethought's switches. The node is now up and performing normally.
Thanks to those who tried to help troubleshoot.

73,
Jeremy W0JRL
http://jlappliedtechnologies.com

On 05/30/2016 08:41 PM, Jeremy Lincicome wrote:
After doing some research, I think the problem is being caused by the ISP. 29997 seams to be the only node having the issue. I think there might be a routing issue with Forethought. I'll contact Forethought tomorrow and see what they say.
However, I think it's weird that I'm only seeing the issue on allstarlink.org and register.allstarlink.org.

On 05/30/2016 06:27 AM, Mark Johnston wrote:
If you have a way to change you public IP, if it isn't static/fixed - could be as simple as changing the MAC of the WAN side on the router (assuming it has a pub IP) , hopefully after a refresh/reboot get a new IP, if it's banned at the server side then that would show it...



"Got Root?"

How many software engineers does it take to change a light bulb?
None. It's a hardware problem.


Unix is user friendly. It's just very particular about who it's friends are.
WINDOWS: Will Install Needless Data On Whole System
MICROSOFT: Most Intelligent Customers Realize Our Software Only Fools Teenagers.


A ntennas
P oorly
P laced
L acks
E ngineering


The best way to accelerate a computer running Windows is at 9.81 m/sē.

"I get paid to support Windows, I use Linux to get work done."


On Mon, May 30, 2016 at 2:10 AM, Jeremy Lincicome <w0jrl1@gmail.com> wrote:
The traceroute, ping, and nslookup were all run from a laptop on the same network as the node. I wonder, is something like fail2ban blocking the node server side? If I run:
wget http://stats.allstarlink.org
I am able to download index.html. I'll try putting the node in the DMZ and see what happens.


On 05/30/2016 02:21 AM, Mark Johnston wrote:
Is there another computer on this same router/network PC/Mac/Linux anything? can it ping/complete a traceroute to allstarlink.org or the IP either way...?
if it can, perhaps something with this computer's configuration, might try getting a diff internal IP for it... make sure iptables and all that are not enabled 
is it practical to bypass the router? as a test.

/etc/hosts.deny is there anything in there etc?



"Got Root?"

How many software engineers does it take to change a light bulb?
None. It's a hardware problem.


Unix is user friendly. It's just very particular about who it's friends are.
WINDOWS: Will Install Needless Data On Whole System
MICROSOFT: Most Intelligent Customers Realize Our Software Only Fools Teenagers.


A ntennas
P oorly
P laced
L acks
E ngineering


The best way to accelerate a computer running Windows is at 9.81 m/sē.

"I get paid to support Windows, I use Linux to get work done."


On Sun, May 29, 2016 at 11:16 PM, Jeremy Lincicome <w0jrl1@gmail.com> wrote:
Loren,
That script has been on the node since I built it over a year ago. Thank you for the suggestion though. DNS is provided by the ISP through the router.
David,
When I run:

wget http://register.allstarlink.org

The terminal just hangs. I have to kill it with CTRL c. However, if I ping google.com, I get an immediate response.

Jeremy W0JRL


On 05/29/2016 11:32 PM, David McGough wrote:
Jeremy,

To confirm if your Internet is working and you can get to the
registration server, try:

wget http://register.allstarlink.org


If you get a "401 Authorization Required" error back, you can see the
registration server just fine via TCP.


73, David KB4FXC


On Sun, 29 May 2016, Jeremy Lincicome wrote:

Mark,
Here are the results of nslookup, ping, and traceroute.

nslookup allstarlink.org
Server:        127.0.1.1
Address:    127.0.1.1#53

Non-authoritative answer:
Name:    allstarlink.org
Address: 67.215.233.179

ping -c4 67.215.233.179:
PING 67.215.233.179 (67.215.233.179) 56(84) bytes of data.

--- 67.215.233.179 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3024ms

traceroute 67.215.233.179
traceroute to 67.215.233.179 (67.215.233.179), 30 hops max, 60 byte packets
   1  DD-WRT (192.168.55.1)  5.094 ms  22.644 ms  22.651 ms
   2  216-98-194-1.forethought.net (216.98.194.1)  25.671 ms  31.059 ms
40.912 ms
   3  vl203.de01.forethought.net (206.124.21.201)  40.914 ms  40.908 ms
40.908 ms
   4  216-241-35-213.static.forethought.net (216.241.35.213)  40.904 ms
40.897 ms  40.888 ms
   5  206-124-24-110.static.forethought.net (206.124.24.110)  44.864 ms
44.866 ms  75.615 ms
   6  te4-1.cr01.lax.citylinkfiber.net (216.243.117.17)  86.184 ms 58.349
ms  45.012 ms
   7  te4-1.cr01.sjc.citylinkfiber.net (216.243.119.129)  59.803 ms
59.797 ms  59.789 ms
   8  * * *
   9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Jeremy W0JRL

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.