- App_rpt-users - lists.keekles.org

DIAL on a PC
by kk6ecm 31 Dec '15

31 Dec '15

Now that I have RPi up and running with DIAL, and controlling the repeater, I'm working on loading DIAL on a PC; loaded the CD image, removed the CD when it was done, and the PC powered down, and I waited... No reboot, so I pressed the ON button, and it booted... A few quick flashes of something on the monitor, then it went black. I then ssh'ed into it, and logged on. So... Where do I go from here? I've not seen any prompts like I received on the RPi to create the nodes from the Allstar server, as described on the Allstar website for installing DIAL. Is there a command I need to enter. Thanks, Bob kk6ecm Sent from iPad

1 0

Pocsag
by Jeff Carrier 29 Dec '15

29 Dec '15

Has anyone been able to successfully implement Pocsag paging? I can't seem it make it work with chan_voter and I don't run any simple usb nodes. de K0jsc

3 2

Re: [App_rpt-users] Allstar node list
by Steve Zingman 29 Dec '15

29 Dec '15

When you say "the server" Do you mean a server hosting a number of nodes? Or the registration server? A server hosting a number of nodes downloads the nodelist from the registration server. Steve Sent via smoke signal (Verizon) On Dec 29, 2015 1:36 AM, kk6ecm <kk6ecm(a)gmail.com <mailto:kk6ecm@gmail.com>> wrote: How does the server update the nodes list? Does it download it, or is it pushed? Thanks, Bob kk6ecm Sent from iPad _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org <mailto: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.

1 0

Re: [App_rpt-users] ACID to DIAL Conversion
by Steve Zingman 29 Dec '15

29 Dec '15

Bob, Yes it does. Sometimes minor tweaks are required. Like zaptel to dahdi. Steve Sent via smoke signal (Verizon) On Dec 29, 2015 1:46 AM, kk6ecm <kk6ecm(a)gmail.com <mailto:kk6ecm@gmail.com>> wrote: Does DIAL use the same /etc/asterisk *.conf files? In other words, when converting, can I just copy the /etc/asterisk folder to DIAL to achieve the same setup as I had with ACID? Thanks, Bob kk6ecm Sent from iPad _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org <mailto: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.

1 0

ACID to DIAL Conversion
by kk6ecm 29 Dec '15

29 Dec '15

Does DIAL use the same /etc/asterisk *.conf files? In other words, when converting, can I just copy the /etc/asterisk folder to DIAL to achieve the same setup as I had with ACID? Thanks, Bob kk6ecm Sent from iPad

1 0

Allstar node list
by kk6ecm 29 Dec '15

29 Dec '15

How does the server update the nodes list? Does it download it, or is it pushed? Thanks, Bob kk6ecm Sent from iPad

1 0

2. Re: Registration Issues (Bobby Lacey)
by R Dahl 28 Dec '15

28 Dec '15

Tim saved my bacon in a similar circumstance regarding Mikrotik. It sounds like you have at least two gateways available and the registration requests go out both of them with unpredictable results. I believe you need to craft a a firewall rule to always force the use of the correct one. This seems Mikrotik specific. 73 de Ross ve6ars > > Message: 2 > Date: Sun, 27 Dec 2015 12:28:28 -0500 > From: Bobby Lacey <kf4gta(a)amsat.org> > To: Lu V <luvencl8(a)gmail.com> > Cc: app_rpt mailing list <app_rpt-users(a)ohnosec.org>, Tim Sawyer > <tisawyer(a)gmail.com> > Subject: Re: [App_rpt-users] Registration Issues > Message-ID: > < > CA+TDQEz2Q5YB6M9FiNi7sF-ngAs6Epy1Yw_DPRw_vf_EzV_F5Q(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Thank you for the info, Tim & Lu! Since I'm not running NAT on my 44 > subnet, I don't do any masquerade rules. I'm only adding firewall filter > rules to open the firewall up for 4569 since I block everything by default. > > Strangely enough, everything started working again this morning with no > intervention on my part! My nodes on my 44 subnet are all registered. > Again, same issue as last time - so, we'll see how long this lasts! Would > really like to figure out why it does this every few months. > > Thanks again for everyone's help! > > 73 > Bobby > KF4GTA > > On Sun, Dec 27, 2015 at 6:45 AM, Lu V <luvencl8(a)gmail.com> wrote: > > > I have an issue that comes up from time to time with my setup in > Colorado. > > The first time it happened, I changed the port in Allstar to another > port > > and that was the fix. I thought it was my ISP blocking 4569. > > Then a month later it happened again. So I changed the port again and of > > course made the forwarding rule change in my router. > > After a few iterations of this, I decided that the next time this > happens, > > that I would just blow away to rule and rebuild it and see what happens. > > Sure enough that was the key to fix the issue. Keep in mind, it takes a > > little while sometimes for all the other nodes to see that you registered > > by the update to the ip list ,but in my case the problem seems to be with > > the router. It is a two wire DSL router and one day I will replace it > with > > one that someone could recommend. But for whatever it is worth, I am able > > to log into the modem remotely and issue a restart. I have found that > > sometimes it takes 2 to 3 restarts to the modem/router and the problem is > > resolved. I don't understand why this continues to be a problem but it > > could possibly be similar in your case. > > > > Lu Vencl > > KA4EPS > > > > On Dec 26, 2015, at 10:25 PM, Tim Sawyer <tisawyer(a)gmail.com> wrote: > > > > I had a hell of a time getting a MikroTik router to let AllStar register. > > The big trick is to insure outbound masqueraded packets go out the WAN > > interface. Otherwise they come back at you and confuse the heck out of > > Asterisk. > > > > Here's my masquerade rule: > > add action=masquerade chain=srcnat out-interface=ether1-WAN src-address= > > 192.168.1.0/24 > > > > And just fyi, here's my forwarding rule: > > add action=dst-nat chain=dstnat dst-port=4569 in-interface=ether1-WAN > > protocol=udp to-addresses=192.168.1.6 to-ports=4569 > > > > > > > > On Sat, Dec 26, 2015 at 3:56 PM, Bobby Lacey <kf4gta(a)amsat.org> wrote: > > > >> I still haven't been able to figure out when it keeps trying to > register, > >> but never does. All port forwards are set on my Mikrotik edge router. > Like > >> I said earlier, it works for months on end and then has trouble > registering > >> all of a sudden. Has anyone else had any registration issues using a > >> Mikrotik device? IAX has been stuck on the Registering/Retrying/Timeout > for > >> about 5 days now. > >> > >> Thank you for any help! > >> 73 > >> Bobby > >> > >> On Wed, Dec 23, 2015 at 10:16 PM, Bobby Lacey <kf4gta(a)amsat.org> wrote: > >> > >>> Hi David, > >>> > >>> Yes - source IP is the same 44/8 address that the allstar node is using > >>> for registering. > >>> > >>> [root@146-760 ~]# wget http://ipinfo.io/ip -qO - > >>> 44.36.x.x > >>> > >>> Just strange that it works for months, then stops all of a sudden? > >>> > >>> Thanks for your help! > >>> > >>> 73 > >>> > >>> Bobby > >>> > >>> On Wed, Dec 23, 2015 at 1:00 PM, David McGough <kb4fxc(a)inttek.net> > >>> wrote: > >>> > >>>> > >>>> Hi, > >>>> > >>>> I think you're hitting a security feature of the Registration System. > >>>> > >>>> When running wget (or the node info collection scripts, like: > >>>> rc.updatenodelist), you must use the same source IP address as > >>>> used during the Asterisk registration requests sent from Asterisk when > >>>> it > >>>> is running. And, your node must be properly registered to retrieve the > >>>> node list. > >>>> > >>>> So, is the source IP address of the AllStar/Asterisk server on the > >>>> 44.0.0.0/8 network? And, if so, when running wget, do you use the > same > >>>> source IP address as Asterisk? If not, these addresses must be the > >>>> same. > >>>> > >>>> > >>>> Merry Christmas and Happy Holidays!! > >>>> > >>>> 73, David KB4FXC > >>>> > >>>> > >>>> On Wed, 23 Dec 2015, Bobby Lacey wrote: > >>>> > >>>> > Hello! > >>>> > > >>>> > Every few months, we run into a problem where our nodes will > >>>> de-register > >>>> > with register.allstarlink.org and just set there before timing out > >>>> and > >>>> > retrying. It never does register until it just magically starts > >>>> working > >>>> > again often many days later. > >>>> > > >>>> > I haven't really had time to troubleshooted it before, but since I'm > >>>> home > >>>> > from work for a few days, I'm trying to trace down the problem. > >>>> > > >>>> > Something interesting I've found: These nodes are sitting on my > 44Net > >>>> ( > >>>> > 44.0.0.0/8) address space and get the following when I try to wget > >>>> nodes.pl: > >>>> > > >>>> > [root@146-760 ~]# wget > http://nodes1.allstarlink.org/cgi-bin/nodes.pl > >>>> > --2015-12-23 11:36:23-- > >>>> http://nodes1.allstarlink.org/cgi-bin/nodes.pl > >>>> > Resolving nodes1.allstarlink.org (nodes1.allstarlink.org) > >>>> 96.36.57.202 > >>>> > Connecting to nodes1.allstarlink.org > >>>> > (nodes1.allstarlink.org)|96.36.57.202|:80... > >>>> > connected. > >>>> > HTTP request sent, awaiting response... 403 > >>>> > 2015-12-23 11:36:23 ERROR 403: (no description). > >>>> > > >>>> > [root@146-760 ~]# wget > http://nodes2.allstarlink.org/cgi-bin/nodes.pl > >>>> > --2015-12-23 11:36:57-- > >>>> http://nodes2.allstarlink.org/cgi-bin/nodes.pl > >>>> > Resolving nodes2.allstarlink.org (nodes2.allstarlink.org) > >>>> 209.159.155.200 > >>>> > Connecting to nodes2.allstarlink.org > >>>> > (nodes2.allstarlink.org)|209.159.155.200|:80... > >>>> > connected. > >>>> > HTTP request sent, awaiting response... 403 Forbidden > >>>> > 2015-12-23 11:36:57 ERROR 403: Forbidden. > >>>> > > >>>> > [root@146-760 ~]# wget > http://nodes3.allstarlink.org/cgi-bin/nodes.pl > >>>> > --2015-12-23 11:37:28-- > >>>> http://nodes3.allstarlink.org/cgi-bin/nodes.pl > >>>> > Resolving nodes3.allstarlink.org (nodes3.allstarlink.org) > >>>> 65.110.110.172 > >>>> > Connecting to nodes3.allstarlink.org > >>>> > (nodes3.allstarlink.org)|65.110.110.172|:80... > >>>> > connected. > >>>> > HTTP request sent, awaiting response... 403 > >>>> > 2015-12-23 11:37:28 ERROR 403: (no description). > >>>> > > >>>> > > >>>> > When I try from my ISP's public IP (non 44Net), it works fine. This > >>>> is just > >>>> > an observation and I'm not sure if it actually is the problem. > >>>> > > >>>> > Anyone have any ideas? > >>>> > > >>>> > Tnx and 73 > >>>> > > >>>> > Bobby > >>>> > KF4GTA > >>>> > > >>>> > >>>> _______________________________________________ > >>>> App_rpt-users mailing list > >>>> App_rpt-users(a)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(a)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. > >> > > > > > > > > -- > > -- > > Tim > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users(a)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. > > > > >

1 0

Registration Issues
by Bobby Lacey 27 Dec '15

27 Dec '15

Hello! Every few months, we run into a problem where our nodes will de-register with register.allstarlink.org and just set there before timing out and retrying. It never does register until it just magically starts working again often many days later. I haven't really had time to troubleshooted it before, but since I'm home from work for a few days, I'm trying to trace down the problem. Something interesting I've found: These nodes are sitting on my 44Net ( 44.0.0.0/8) address space and get the following when I try to wget nodes.pl: [root@146-760 ~]# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl --2015-12-23 11:36:23-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl Resolving nodes1.allstarlink.org (nodes1.allstarlink.org) 96.36.57.202 Connecting to nodes1.allstarlink.org (nodes1.allstarlink.org)|96.36.57.202|:80... connected. HTTP request sent, awaiting response... 403 2015-12-23 11:36:23 ERROR 403: (no description). [root@146-760 ~]# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl --2015-12-23 11:36:57-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl Resolving nodes2.allstarlink.org (nodes2.allstarlink.org) 209.159.155.200 Connecting to nodes2.allstarlink.org (nodes2.allstarlink.org)|209.159.155.200|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2015-12-23 11:36:57 ERROR 403: Forbidden. [root@146-760 ~]# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl --2015-12-23 11:37:28-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl Resolving nodes3.allstarlink.org (nodes3.allstarlink.org) 65.110.110.172 Connecting to nodes3.allstarlink.org (nodes3.allstarlink.org)|65.110.110.172|:80... connected. HTTP request sent, awaiting response... 403 2015-12-23 11:37:28 ERROR 403: (no description). When I try from my ISP's public IP (non 44Net), it works fine. This is just an observation and I'm not sure if it actually is the problem. Anyone have any ideas? Tnx and 73 Bobby KF4GTA

4 6

Includeifexists
by Scott Weis 27 Dec '15

27 Dec '15

I am trying to add a directive to a node stanza via the includeifexists file specified at the bottom of the rpt.conf file. What format does the custom/rpt.conf file need to be to be included? Thanks & 73, Scott KB2EAR

2 1

Redundancy
by Robert Newberry 26 Dec '15

26 Dec '15

I was talking with another sysop on our little network up here. Occasionally some little internet hiccup will cause the network to go down at the hub we use. We also rely on allmon2 for "command and control" Is it possible in asterisk if there is a problem with the network connection at the system hub to automatically shift the connected repeaters somewhere else? Allmon2 two isn't an issue since we can leave that running full time at the "backup location" and we can just access it from the alternate address. Currently we manually shift everything and it doesn't happen often. I was just wondering if anyone has automated it. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658

1 0