[App_rpt-users] What is wrong with my node?

Wed Sep 5 15:26:34 UTC 2012

Apologies to all  for MIS-reading the thread.

—————
iThing:  Big thumbs & little keys. Please excuse typo, spelling and
grammar errors • Good planets are hard to find – think before you
print • My desire to be well-informed is currently at odds with my
desire to remain sane. • Last night I played a blank CD at full blast.
The Mime next door went nuts.

On 2012-09-05, at 11:18, "Jeffrey S. Carrier"
<jeff.carrier at rmsmsecurity.com> wrote:

> That was my reply to jim.  Jim stated he had a static, I do not.  I'm running the no-ip client on the nodes
>
> Jeffrey S. Carrier
> Fire Inspector, Plant Protection
> (719) 561-7199 direct
> (719) 561-6567 fax
> 1612 E. Abriendo Ave. Pueblo, Colorado 81004
> jeffrey.carrier at evrazincna.com
>
> Sent from my Android phone using TouchDown
>
>
> -----Original Message-----
> From: S. Scott [8f27e956 at gmail.com]
> Received: Wednesday, 05 Sep 2012, 9:15am
> To: Jim W7RY [w7ry at centurytel.net]
> CC: app_rpt-users at ohnosec.org [app_rpt-users at ohnosec.org]
> Subject: Re: [App_rpt-users] What is wrong with my node?
>
>
> You wrote, "I have a STATIC IP" and then in another reply wrote, "but it
> changes wildly.".
>
> The two statements are incongruous.
>
> How does your network detect and then apply the new address to applicable
> interface when "...it wildly changes."
>
>
>
> —————
> iThing:  Big thumbs & little keys. Please excuse typo, spelling and grammar
> errors • Good planets are hard to find – think before you print • My desire
> to be well-informed is currently at odds with my desire to remain sane.
> • Last night I played a blank CD at full blast. The Mime next door went
> nuts.
>
>
> On 2012-09-05, at 10:18, Jim W7RY <w7ry at centurytel.net> wrote:
>
> I have a static IP.
>
> Only one device on the LAN. The WAN connector on the router goes to the
> IP’s switch, the LAN connector goes to the node.
>
> 73
> Jim W7RY
>
>
> *From:* S. Scott <8f27e956 at gmail.com>
> *Sent:* Wednesday, September 05, 2012 6:59 AM
> *To:* Jim W7RY <w7ry at centurytel.net>
> *Cc:* app_rpt-users at ohnosec.org
> *Subject:* Re: [App_rpt-users] What is wrong with my node?
>
> Is the ISP service STATIC or DYNAMIC IP assignment?
>
> In cases other than AllStar, I have seen situations where the IP address
> changes (due to dynamic/dhcp re-assignment) and the site LAN device(s)
> continue to ARP CACHE the old IP-to-MAC address pair.
>
> While AllStar uses periodic IAX registrations to keep the ALlStar 'network'
> aligned, these re-registrations would have zero affect on local ARP CACHE
> entries (and their timeout), if ARP CACHE is your issue.
>
> You need the commands to display the ARP table on EACH and ALL of the
> devices on your LAN  path between the node and the internet, as well as on
> the Linux node host itself.
>
> Linux command,
> # arp -v
>
> As a shot in the dark, you may want to confirm that your wireless router's
> firmware is the most up to date there is.
>
> Cycling the interface can clear the ARP Entries.  you can DOWN the
> interface, pause, and UP the interface.  Don't DOWN a REMOTE interface
> you're doing the remote connection through. You need a small script to
> down, sleep, and up that'll run in the background (&) so when you get
> disconnected, you can re-connect when the script UPs the interface.
>
> Again, I don't know if this is your issue, but I have seen ARP tables
> MIS-matches cause these types of issues.
>
> Good luck.
>
> —————
>
>
> On 2012-09-05, at 0:21, Jim W7RY <w7ry at centurytel.net> wrote:
>
>    The node is at a wireless internet provider hub.  I have 1.5 Mb of
> speed at all times. This has started to happen after I installed the keep
> connected commands. The node has always had this issue though.
>
> 73
> Jim W7RY
>
>
> *From:* Jeffrey S. Carrier <jeff.carrier at rmsmsecurity.com>
> *Sent:* Tuesday, September 04, 2012 8:20 PM
> *To:* Jim W7RY <w7ry at centurytel.net> ; app_rpt-users at ohnosec.org
> *Subject:* RE: [App_rpt-users] What is wrong with my node?
>
>
> This is usually an ISP issue.  Happens to me all the time with my crummy
> cable ISP.  Usually have to restart the cable modem and router to get it
> playing nice again.  DMZ or not, your router or the remote router could be
> blocking traffic.  I’ve seen it a 100 times here though your issue could be
> different, my two cents.
>
>
>
>
>
> 73 de K0JSC
>
>
>
>
> ------------------------------
>
> *From:* Jim W7RY [mailto:w7ry at centurytel.net]
> *Sent:* Tuesday, September 04, 2012 9:01 PM
> *To:* app_rpt-users at ohnosec.org
> *Subject:* [App_rpt-users] What is wrong with my node?
>
>
>
> Why is this happening? See below.....   The internet is working just fine
> from the site. I logged into the node and the router remotely at the
> moment. The node repeater is in the DMZ. I can ping google.com so the DNS
> is working.
>
>
>
> This node not being able to re-connect or connect is really not cool!
>
>
>
> What is going on here?
>
>
>
>
>
> Thanks!
>
> Jim W7RY
>
>
>
>
>
>
>
> 2560 on IAX2/208.70.77.197:4569-13708
>
> [Sep  4 19:57:01] WARNING[2315]: app_rpt.c:17622 attempt_reconnect:
> Reconnect At                                              tempt to 2560 in
> process
>
> [Sep  4 19:57:05] NOTICE[2295]: chan_iax2.c:4071 __auto_congest:
> Auto-congesting                                               call due to
> slow response
>
>    -- Hungup 'IAX2/208.70.77.197:4569-13708'
>
>    -- rpt (attempt_reconnect) initiating call to IAX2/
> radio at 208.70.77.197:4569/                                              2560
> on IAX2/208.70.77.197:4569-14388
>
> [Sep  4 19:57:13] WARNING[2315]: app_rpt.c:17622 attempt_reconnect:
> Reconnect At                                              tempt to 2560 in
> process
>
> [Sep  4 19:57:17] NOTICE[2293]: chan_iax2.c:4071 __auto_congest:
> Auto-congesting                                               call due to
> slow response
>
>    -- Hungup 'IAX2/208.70.77.197:4569-14388'
>
>    -- rpt (attempt_reconnect) initiating call to IAX2/
> radio at 208.70.77.197:4569/2560 on IAX2/208.70.77.197:4569-15647
>
> [Sep  4 19:57:25] WARNING[2315]: app_rpt.c:17622 attempt_reconnect:
> Reconnect Attempt to 2560 in process
>
> [Sep  4 19:57:29] NOTICE[2286]: chan_iax2.c:4071 __auto_congest:
> Auto-congesting call due to slow response
>
>    -- Hungup 'IAX2/208.70.77.197:4569-15647'
>
>    -- rpt (attempt_reconnect) initiating call to IAX2/
> radio at 208.70.77.197:4569/2560 on IAX2/208.70.77.197:4569-6971
>
> [Sep  4 19:57:37] WARNING[2315]: app_rpt.c:17622 attempt_reconnect:
> Reconnect Attempt to 2560 in process
>
> [Sep  4 19:57:41] NOTICE[2287]: chan_iax2.c:4071 __auto_congest:
> Auto-congesting call due to slow response
>
>    -- Hungup 'IAX2/208.70.77.197:4569-6971'
>
>    -- rpt (attempt_reconnect) initiating call to IAX2/
> radio at 208.70.77.197:4569/2560 on IAX2/208.70.77.197:4569-13440
>
> [Sep  4 19:57:49] WARNING[2315]: app_rpt.c:17622 attempt_reconnect:
> Reconnect Attempt to 2560 in process
>
> [Sep  4 19:57:53] NOTICE[2295]: chan_iax2.c:4071 __auto_congest:
> Auto-congesting call due to slow response
>
>    -- Hungup 'IAX2/208.70.77.197:4569-13440'
>
> w7ry*CLI> exit
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users