[App_rpt-users] Echolink Updates

[David Osborn]

Thanks for your input guys,

It turned out that our pFSense firewall was in a really mean mood. It would
allow traffic, then deny it (must be female!). I installed the latest
updates - which introduced a bunch of other problems requiring a power-off
reboot - then everything worked fine.... for now.

Good tip on the echolink database, though. That needs to be Drupal-ed :-)

Cheers

David

-----Original Message-----
From: Bryan Fields [mailto:Bryan at bryanfields.net] 
Sent: 07 June 2015 18:21
To: APP RPT
Subject: Re: [App_rpt-users] Echolink Updates

On 6/7/15 12:10 PM, David Osborn wrote:
> Aha!!!
> 
> So, I was looking under the wrong rock. He's there alright so the 
> mystery remains as to why we can't connect to his node :-(
> 
> snaefell*CLI> rpt fun 2480 *33356825
>     -- new CALL=OUTBOUND,ip=81.165.69.72,name=OUTBOUND

Do a traceroute to 81.165.69.72 and see what it looks like.

I had an issue with routing once like this, worked with every other echolink
user except my friend who was on a network in Chicago owned by the ISP that
my data center is owned by.  Since I bring my own IP space, they had a
routing issue with their cable customers getting to my IP's.

There was basically nothing of value in the logs to say why this happened.

73's
--
Bryan Fields

727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6079 bytes
Desc: not available
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20150608/7bb8f262/attachment.bin>