From wayne at anywherehost.net Mon Sep 1 03:57:07 2014 From: wayne at anywherehost.net (Wayne) Date: Sun, 31 Aug 2014 20:57:07 -0700 Subject: [App_rpt-users] Using an Intermediate Repeater In-Reply-To: <39A0E6FA-B964-4B70-9E3F-7ED642090D39@mac.com> References: <7EA85E4B11D941949648E7C7C7C86709@desktop> <39A0E6FA-B964-4B70-9E3F-7ED642090D39@mac.com> Message-ID: <61DEF641D9D14D3F937C69E84A504539@desktop> Sorry for writing a book. It's go time! Thanks for the reply, Tim. I ordered a RTCM yesterday. We have three repeaters that we could vote but we think it better to continue using our RC-210's. The resale value on them is so low that we'd be throwing away over $1k. There are benefits on both sides of the question. We CAN get wi-fi to one site but not others and none of them inexpensively. We figure that we'll reuse the frequency pair with GPS to sync the transmitters (something I've never done before,) lower the TX power so that two repeaters don't crash into one another but instead pleasantly overlap, and then let users choose which repeater they want to come in on. I'd love full time voting and we may get there one day. The biggest problem we have being in southern California is that all the hilltops are equally able to hear bases and mobiles and to some extent HT's. We are already coordinated on three of the four sites in question. We want guaranteed coverage in the event of a regional emergency, like another earthquake in Northridge. The ease by which we can telephone the RC-210 and unlink that site is important. The trick as I have been warned is avoiding conflicting DTMF. As I see it by telephoning the controller instead of OTR we might avoid these conflicts. Additionally, our 900MHz system will serve as our back-up linking. We can still communicate with any site using 900MHz. I don't want to sell the RTCM short since I haven't even used one yet. But we have weather receivers, link repeaters With this said, in an emergency situation, like the Big One hitting southern California, we will be delinking all repeaters. Allstar will not be needed during this event. Does it make sense having a RTCM on each repeater rather than just one RTCM on the primary repeater? The others will get theirs over the link anyway. Lastly, my boss owns an internet company and the server has been donated and will be placed in the data center with 100Mbps throughput 24/7/365. The server will be a dual processor AMD 248 single core with 4GB of RAM and RAID 5. I believe in giving back and will gladly share with others. Will I able to offer to others? As well, I can either have a dedicated server but my preference is a dedicated VPS using CentOS 6.x. They backup all servers nightly and using Virtuozzo (part of Parallels Plesk environment; we load Virtuozzo 4.7x and then Plesk on top of the container.) The advantage is that if we have a hardware failure our node may be migrated to another node in their server farm. If it is a catastrophic failure they can restore from a recent backup. I even have an app on my phone that allows me to control and even reboot the server. Virtuozzo automatically installs its own template of CentOS and some packages are missing, etc. Many are added back, like PHP and mySQLi and most of the CentOS distro. How then can I load Acid and configure it in a Virtuozzo environment? We may even load Plesk 12 on top of the node considering the horsepower that it has. Is there a list of files that I will need to get onto the VPS as well as RPM's or packages required by Allstar? _____ From: Tim Sawyer [mailto:tim.sawyer at mac.com] Sent: Sunday, August 31, 2014 6:51 AM To: Wayne Cc: app_rpt mailing list Subject: Re: [App_rpt-users] Using an Intermediate Repeater Yes, the RTCM could be wired to the ground end 900MHz radio, full duplex of course. Too bad you can't get WiFi to your site, but ya do what ya gota do. -- Tim WD6AWP On Aug 31, 2014, at 5:19 AM, Wayne wrote: I have finally ordered our first of four RTCM's - progress! We are having difficulty getting wi-fi to our remote repeater site. I am wondering if we may do the following: Our repeater is VHF. We have a 900MHz full duplex link pair. W4e have a RC-210 controller controlling the repeater and the 900MHz is on port 3. Can we wire the RTCM to a full duplex (or even semi-duplex) transceiver to get Allstar to the VHF machine? Thank you. _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From N1XBM at amsat.org Wed Sep 3 13:33:37 2014 From: N1XBM at amsat.org (Robert Newberry) Date: Wed, 3 Sep 2014 09:33:37 -0400 Subject: [App_rpt-users] IAX help Message-ID: Anyone on the list good with IAX. I have a few issues I'm trying to sort thru. I have two clients setup and working on smartphones now. 1. The connect welcome message does not play when connected. Also when I hit pound (#) I do not get the repeater tail beep. Not sure if that can be remedied. 2. I'd like to assign a four digit extension numbers to my clients. I had this up and running before I shut down SIP on my server. I've looked at the extension and SIP .conf and am wondering if it's similar. That's all I got for now. By the way I posted for a issues with audio last week. I got lots of replies that were very helpful and concise. My repeater is sounding great. Thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: From buddy at brannan.name Wed Sep 3 14:55:47 2014 From: buddy at brannan.name (Buddy Brannan) Date: Wed, 3 Sep 2014 10:55:47 -0400 Subject: [App_rpt-users] Fwd: EchoLink Policy Reminder References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> Message-ID: <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> I wonder if anyone else got this Email? I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I?ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. ? Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy at brannan.name > Begin forwarded message: > > From: "EchoLink Support" > Subject: EchoLink Policy Reminder > To: "EchoLink Node Operators" <> > > We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm). > > In general, EchoLink does not permit cross-linking. > > More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world. > > Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node. > > In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made. > > If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel. > > Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed. > > 73 > EchoLink Support > > (Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm) From fred at moses.bz Wed Sep 3 14:57:57 2014 From: fred at moses.bz (Fredric Moses) Date: Wed, 3 Sep 2014 10:57:57 -0400 Subject: [App_rpt-users] Fwd: EchoLink Policy Reminder In-Reply-To: <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> Message-ID: <73265614-72A4-4D50-8108-CADAF4D46233@moses.bz> Yea I got it on a few of my email address?s that are registered to call signs? Was a broadcast mail? Guess if they block me it?s one less headache to deal with... -- Fredric Moses - W8FSM - WQOG498 fred at moses.bz On Sep 3, 2014, at 10:55 AM, Buddy Brannan wrote: > I wonder if anyone else got this Email? > > I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I?ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? > > As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. > > ? > Buddy Brannan, KB5ELV - Erie, PA > Phone: 814-860-3194 > Mobile: 814-431-0962 > Email: buddy at brannan.name > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From buddy at brannan.name Wed Sep 3 15:05:19 2014 From: buddy at brannan.name (Buddy Brannan) Date: Wed, 3 Sep 2014 11:05:19 -0400 Subject: [App_rpt-users] EchoLink Policy Reminder In-Reply-To: <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> Message-ID: BTW, I hate autocorrect. I also hate not hitting all the letters. (Sigh) ? Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy at brannan.name > On Sep 3, 2014, at 10:55 AM, Buddy Brannan wrote: > > I wonder if anyone else got this Email? > > I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I?ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? > > As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. > > ? > Buddy Brannan, KB5ELV - Erie, PA > Phone: 814-860-3194 > Mobile: 814-431-0962 > Email: buddy at brannan.name > > > >> Begin forwarded message: >> >> From: "EchoLink Support" >> Subject: EchoLink Policy Reminder >> To: "EchoLink Node Operators" <> >> >> We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm). >> >> In general, EchoLink does not permit cross-linking. >> >> More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world. >> >> Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node. >> >> In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made. >> >> If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel. >> >> Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed. >> >> 73 >> EchoLink Support >> >> (Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm) > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. From n3fe at repeater.net Wed Sep 3 15:11:37 2014 From: n3fe at repeater.net (Corey Dean) Date: Wed, 3 Sep 2014 11:11:37 -0400 Subject: [App_rpt-users] Fwd: EchoLink Policy Reminder In-Reply-To: <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> Message-ID: <3F8F559F-2B6A-43DD-BAC8-9156E6D8D079@repeater.net> Yes, I got it as well... Sent from my iPhone > On Sep 3, 2014, at 10:55 AM, Buddy Brannan wrote: > > I wonder if anyone else got this Email? > > I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I?ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? > > As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. > > ? > Buddy Brannan, KB5ELV - Erie, PA > Phone: 814-860-3194 > Mobile: 814-431-0962 > Email: buddy at brannan.name > > > >> Begin forwarded message: >> >> From: "EchoLink Support" >> Subject: EchoLink Policy Reminder >> To: "EchoLink Node Operators" <> >> >> We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm). >> >> In general, EchoLink does not permit cross-linking. >> >> More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world. >> >> Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node. >> >> In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made. >> >> If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel. >> >> Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed. >> >> 73 >> EchoLink Support >> >> (Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm) > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. From bdboyle at bdboyle.com Wed Sep 3 15:28:00 2014 From: bdboyle at bdboyle.com (Bryan D. Boyle) Date: Wed, 3 Sep 2014 11:28:00 -0400 Subject: [App_rpt-users] Fwd: EchoLink Policy Reminder In-Reply-To: <73265614-72A4-4D50-8108-CADAF4D46233@moses.bz> References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> <73265614-72A4-4D50-8108-CADAF4D46233@moses.bz> Message-ID: agreed. it's inferior technology anyway. -- Bryan Sent from my iPhone 5...No electrons were harmed in the sending of this message. > On Sep 3, 2014, at 10:57, Fredric Moses wrote: > > Yea I got it on a few of my email address?s that are registered to call signs? Was a broadcast mail? Guess if they block me it?s one less headache to deal with... > -- > Fredric Moses - W8FSM - WQOG498 > fred at moses.bz > > > > >> On Sep 3, 2014, at 10:55 AM, Buddy Brannan wrote: >> >> I wonder if anyone else got this Email? >> >> I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I?ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? >> >> As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. >> >> ? >> Buddy Brannan, KB5ELV - Erie, PA >> Phone: 814-860-3194 >> Mobile: 814-431-0962 >> Email: buddy at brannan.name > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Wed Sep 3 16:20:54 2014 From: doug at crompton.com (Doug Crompton) Date: Wed, 3 Sep 2014 12:20:54 -0400 Subject: [App_rpt-users] Fwd: EchoLink Policy Reminder In-Reply-To: References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91>, <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name>, <73265614-72A4-4D50-8108-CADAF4D46233@moses.bz>, Message-ID: Personally I would ignore it. Its their loss. I doubt there would be any actual blocking unless there was a flagrant violation taking place. I am certainly not going to worry about it. I have an echolink input on my Allstar hub mainly for convenience as it is mostly the Allstar users away from home using their smart phones that come in on it. Has anyone on Allstar every had a problem with unlicensed infiltration? Actually I would think echolink is easier to infiltrate than IRLP and Allstar just because there are so many gateway software packages into it. Echolink also has the most non-radio communications of any of the ham voip systems. I would say a good percentage of the communications on echolink are computer to computer. Technically you would not even need a license for that. 73 Doug WA3DSP http://www.crompton.com/hamradio From: bdboyle at bdboyle.com Date: Wed, 3 Sep 2014 11:28:00 -0400 To: fred at moses.bz CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Fwd: EchoLink Policy Reminder agreed. it's inferior technology anyway. --BryanSent from my iPhone 5...No electrons were harmed in the sending of this message. On Sep 3, 2014, at 10:57, Fredric Moses wrote: Yea I got it on a few of my email address?s that are registered to call signs? Was a broadcast mail? Guess if they block me it?s one less headache to deal with... -- Fredric Moses - W8FSM - WQOG498 fred at moses.bz On Sep 3, 2014, at 10:55 AM, Buddy Brannan wrote: I wonder if anyone else got this Email? I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I?ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. ? Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy at brannan.name _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Wed Sep 3 16:34:39 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Wed, 03 Sep 2014 09:34:39 -0700 Subject: [App_rpt-users] EchoLink Policy Reminder In-Reply-To: <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> Message-ID: Did not get that email. We use Echolink for away members to check into our RACES net. It?s a pain in the butt, the huge delays causes doubling with RF stations and cell phone Echolink clients sound like poop. This new (to me) Echolink policy gives me the perfect excuse to turn it off. -- Tim :wq On Sep 3, 2014, at 7:55 AM, Buddy Brannan wrote: > I wonder if anyone else got this Email? > > I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I?ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? > > As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. > > ? > Buddy Brannan, KB5ELV - Erie, PA > Phone: 814-860-3194 > Mobile: 814-431-0962 > Email: buddy at brannan.name > > > >> Begin forwarded message: >> >> From: "EchoLink Support" >> Subject: EchoLink Policy Reminder >> To: "EchoLink Node Operators" <> >> >> We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm). >> >> In general, EchoLink does not permit cross-linking. >> >> More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world. >> >> Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node. >> >> In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made. >> >> If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel. >> >> Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed. >> >> 73 >> EchoLink Support >> >> (Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm) > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Wed Sep 3 16:55:59 2014 From: Bryan at bryanfields.net (Bryan Fields) Date: Wed, 03 Sep 2014 12:55:59 -0400 Subject: [App_rpt-users] EchoLink Policy Reminder In-Reply-To: References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> Message-ID: <5407481F.5040201@bryanfields.net> On 9/3/14, 12:34 PM, Tim Sawyer wrote: > This new (to me) Echolink policy gives me the perfect excuse to turn it off. Agreed. Could be worse, cough IRLP, cough..... -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net From wb6egr at gmail.com Wed Sep 3 17:07:03 2014 From: wb6egr at gmail.com (Kirk Just Kirk) Date: Wed, 3 Sep 2014 10:07:03 -0700 Subject: [App_rpt-users] EchoLink Policy Reminder In-Reply-To: <5407481F.5040201@bryanfields.net> References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> <5407481F.5040201@bryanfields.net> Message-ID: :) it's OK...IRLP is dying out slowly, Dave's cash register is not ringing much these days.... On Wed, Sep 3, 2014 at 9:55 AM, Bryan Fields wrote: > On 9/3/14, 12:34 PM, Tim Sawyer wrote: > > This new (to me) Echolink policy gives me the perfect excuse to turn it > off. > Agreed. > > Could be worse, cough IRLP, cough..... > > -- > Bryan Fields > > 727-409-1194 - Voice > 727-214-2508 - Fax > http://bryanfields.net > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorentedford at gmail.com Wed Sep 3 17:41:48 2014 From: lorentedford at gmail.com (Loren Tedford) Date: Wed, 3 Sep 2014 12:41:48 -0500 Subject: [App_rpt-users] Fwd: EchoLink Policy Reminder In-Reply-To: <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> Message-ID: I got the email too not sure what to think.. Loren Tedford (KC9ZHV) Email: lorentedford at gmail.com Email: lorentedford at live.com Email: lorentedford at aol.com Email: LorenCS at Ltcraft.net Email: lorentedford at yahoo.com Email: loren at lorentedford.com Email: loren at richlandcountycomputers.com Phone: 618-553-0806 http://www.lorentedford.com http://www.Ltcraft.net http://www.richlandcountycomputers.com http://kc9zhv.lorentedford.com On Wed, Sep 3, 2014 at 9:55 AM, Buddy Brannan wrote: > I wonder if anyone else got this Email? > > I have my Echlin attached to an Allstar node number that only is Echlin. > The RF link, which also allows dial in via All Star web transceiver or > phone, stays connected to the Echlin All Star node number most of the time, > but I can drop that at will. Moreover, I think I?ve turned off any access > to the web transceiver or phone gateway to the Echlin node number. Is there > anything else I need to do to be in compliance? > > As a side note, all of these regulations against interconnecting systems > are getting kind of ridiculous. > > ? > Buddy Brannan, KB5ELV - Erie, PA > Phone: 814-860-3194 > Mobile: 814-431-0962 > Email: buddy at brannan.name > > > > > Begin forwarded message: > > > > From: "EchoLink Support" > > Subject: EchoLink Policy Reminder > > To: "EchoLink Node Operators" <> > > > > We wanted to remind you of an important item in EchoLink's access > policies (which can be found online at > http://www.echolink.org/access_policies.htm). > > > > In general, EchoLink does not permit cross-linking. > > > > More specifically, EchoLink does not permit cross-linking with other > VoIP systems that can be accessed off-the-air (for example, directly from a > PC or Web browser). This is because other systems may have a validation > procedure that is far less comprehensive than EchoLink's, and we want to > continue to ensure that EchoLink is solely for use by licensed Amateur > Radio operators around the world. > > > > Therefore, while excellent systems such as Zello, AllStar, eQSO, > WIRES-II, etc. all serve an important purpose within the Amateur Radio > community, our policy is that they cannot be directly connected to a > registered EchoLink node. > > > > In other words, your node must function only as a direct RF gateway, and > not as a cross-link to another system. If your node is reachable through > another path, that path must be disabled when an EchoLink connection is in > progress. For example, an EchoIRLP node is permitted, since it functions > only as an RF gateway when an EchoLink connection is made. > > > > If you are running Asterisk with app_rpt and an EchoLink channel, be > sure it is configured not to allow other VoIP connections when an EchoLink > station is connected. If this isn't practical, please disable the EchoLink > channel. > > > > Thanks for ensuring that your node adheres to this policy. In some cases > we do restrict logins to be sure the policy is being followed. > > > > 73 > > EchoLink Support > > > > (Note: This mailbox is not able to handle replies. For help and > information, please see www.echolink.org/support.htm) > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorentedford at gmail.com Wed Sep 3 17:45:01 2014 From: lorentedford at gmail.com (Loren Tedford) Date: Wed, 3 Sep 2014 12:45:01 -0500 Subject: [App_rpt-users] Problem with two repeaters.. Message-ID: Hello having issues running both repeaters for some reason it is telling me that Device usb27103 currently not active what does this mean? its all plugged in was working then all the suddenly stopped working randomly is it not detecting the device number correctly with the URI? I am running 2 Cm200 on vhf for this repeater and node 29925 is running flawlessly with out any issues with 2 Cm200 on UHF Loren Tedford (KC9ZHV) Email: lorentedford at gmail.com http://kc9zhv.lorentedford.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From hromano at earthlink.net Wed Sep 3 19:15:44 2014 From: hromano at earthlink.net (harry) Date: Wed, 3 Sep 2014 15:15:44 -0400 Subject: [App_rpt-users] Web Tranciever Message-ID: <000301cfc7ab$76869420$6393bc60$@net> Hello All, Both of my servers stoped working with the web transceiver . It is turned on according to allstarlink.org. Where do I look in the servers files to make sure it's on. IAXRPT does work on both servers . Any ideas on what's next??? Harry KC4RPP -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at dyb.com Wed Sep 3 19:54:38 2014 From: george at dyb.com (George Csahanin) Date: Wed, 03 Sep 2014 14:54:38 -0500 Subject: [App_rpt-users] Echo Message-ID: <540771FE.2000709@dyb.com> Well, fine. First they gave me hassles a few years ago about having an echolink node but not using their software. Now this? Y'know what? Let them keep their awful audio and the lids, kids and space cadets they attract. I block all but a handful of echolink nodes for those who normally connect just to avoid the horrid audio. But one or two "usual" connections regularly have other connections going to some of the worlds worst audio (usually from San Antonio). And because one of their annointed three couldn't connect to me they kicked up a fuss, so there are three callsigns in my accept list for them. So when I get home from the office today I'll nuke my echolink port, good riddance to the trash and idiots that wouldn't know the business end of a soldering iron.Never used IRLP. Stopped any thought of it when I got to the part where they wanted to sell me something and I had no control over stuff. No way. (I think I have an opinion on these things) GeorgeC W2DB 2360 From mike at midnighteng.com Wed Sep 3 20:42:22 2014 From: mike at midnighteng.com (mike at midnighteng.com) Date: Wed, 03 Sep 2014 13:42:22 -0700 Subject: [App_rpt-users] =?utf-8?q?Web_Tranciever?= Message-ID: <20140903134222.71befee5dbd13c5325dd1a521b4e73ee.b10a926a9b.wbe@email06.secureserver.net> An HTML attachment was scrubbed... URL: From wb6egr at gmail.com Wed Sep 3 20:58:04 2014 From: wb6egr at gmail.com (Kirk Just Kirk) Date: Wed, 3 Sep 2014 13:58:04 -0700 Subject: [App_rpt-users] Echo In-Reply-To: <540771FE.2000709@dyb.com> References: <540771FE.2000709@dyb.com> Message-ID: Totally AGREE George, with all the dingbats, the drive by connects/disconnects, the god awful audio, use of foreign languages and the first question...HOW IS THE WEATHER???? I have had mine locked down to -L or -R only to stop the keyboard idiots. I'm thinking of killing it also... On Wed, Sep 3, 2014 at 12:54 PM, George Csahanin wrote: > Well, fine. First they gave me hassles a few years ago about having an > echolink node but not using their software. Now this? Y'know what? Let them > keep their awful audio and the lids, kids and space cadets they attract. I > block all but a handful of echolink nodes for those who normally connect > just to avoid the horrid audio. But one or two "usual" connections > regularly have other connections going to some of the worlds worst audio > (usually from San Antonio). And because one of their annointed three > couldn't connect to me they kicked up a fuss, so there are three callsigns > in my accept list for them. So when I get home from the office today I'll > nuke my echolink port, good riddance to the trash and idiots that wouldn't > know the business end of a soldering iron.Never used IRLP. Stopped any > thought of it when I got to the part where they wanted to sell me something > and I had no control over stuff. No way. > > (I think I have an opinion on these things) > > GeorgeC > W2DB > 2360 > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From k9mar at hotmail.com Wed Sep 3 22:19:18 2014 From: k9mar at hotmail.com (OMAR- K9MAR) Date: Wed, 3 Sep 2014 15:19:18 -0700 Subject: [App_rpt-users] App_rpt-users Digest, Vol 67, Issue 2 In-Reply-To: References: Message-ID: What's next...SVXLINK? > From: app_rpt-users-request at ohnosec.org > Subject: App_rpt-users Digest, Vol 67, Issue 2 > To: app_rpt-users at ohnosec.org > Date: Wed, 3 Sep 2014 13:07:06 -0400 > > Send App_rpt-users mailing list submissions to > app_rpt-users at ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request at ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner at ohnosec.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. Re: Fwd: EchoLink Policy Reminder (Doug Crompton) > 2. Re: EchoLink Policy Reminder (Tim Sawyer) > 3. Re: EchoLink Policy Reminder (Bryan Fields) > 4. Re: EchoLink Policy Reminder (Kirk Just Kirk) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 3 Sep 2014 12:20:54 -0400 > From: Doug Crompton > To: "app_rpt-users at ohnosec.org" > Subject: Re: [App_rpt-users] Fwd: EchoLink Policy Reminder > Message-ID: > Content-Type: text/plain; charset="windows-1252" > > Personally I would ignore it. Its their loss. I doubt there would be any actual blocking unless there was a flagrant violation taking place. I am certainly not going to worry about it. I have an echolink input on my Allstar hub mainly for convenience as it is mostly the Allstar users away from home using their smart phones that come in on it. > > Has anyone on Allstar every had a problem with unlicensed infiltration? Actually I would think echolink is easier to infiltrate than IRLP and Allstar just because there are so many gateway software packages into it. Echolink also has the most non-radio communications of any of the ham voip systems. I would say a good percentage of the communications on echolink are computer to computer. Technically you would not even need a license for that. > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: bdboyle at bdboyle.com > Date: Wed, 3 Sep 2014 11:28:00 -0400 > To: fred at moses.bz > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Fwd: EchoLink Policy Reminder > > agreed. it's inferior technology anyway. > > --BryanSent from my iPhone 5...No electrons were harmed in the sending of this message. > > > On Sep 3, 2014, at 10:57, Fredric Moses wrote: > > Yea I got it on a few of my email address?s that are registered to call signs? Was a broadcast mail? Guess if they block me it?s one less headache to deal with... > -- > Fredric Moses - W8FSM - WQOG498 > fred at moses.bz > > > > > On Sep 3, 2014, at 10:55 AM, Buddy Brannan wrote: > > I wonder if anyone else got this Email? > > I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I?ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? > > As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. > > ? > Buddy Brannan, KB5ELV - Erie, PA > Phone: 814-860-3194 > Mobile: 814-431-0962 > Email: buddy at brannan.name > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 2 > Date: Wed, 03 Sep 2014 09:34:39 -0700 > From: Tim Sawyer > To: Buddy Brannan > Cc: app_rpt mailing list > Subject: Re: [App_rpt-users] EchoLink Policy Reminder > Message-ID: > Content-Type: text/plain; charset="windows-1252" > > Did not get that email. > > We use Echolink for away members to check into our RACES net. It?s a pain in the butt, the huge delays causes doubling with RF stations and cell phone Echolink clients sound like poop. > > This new (to me) Echolink policy gives me the perfect excuse to turn it off. > > -- > Tim > :wq > > On Sep 3, 2014, at 7:55 AM, Buddy Brannan wrote: > > > I wonder if anyone else got this Email? > > > > I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I?ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? > > > > As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. > > > > ? > > Buddy Brannan, KB5ELV - Erie, PA > > Phone: 814-860-3194 > > Mobile: 814-431-0962 > > Email: buddy at brannan.name > > > > > > > >> Begin forwarded message: > >> > >> From: "EchoLink Support" > >> Subject: EchoLink Policy Reminder > >> To: "EchoLink Node Operators" <> > >> > >> We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm). > >> > >> In general, EchoLink does not permit cross-linking. > >> > >> More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world. > >> > >> Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node. > >> > >> In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made. > >> > >> If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel. > >> > >> Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed. > >> > >> 73 > >> EchoLink Support > >> > >> (Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm) > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at 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. > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 3 > Date: Wed, 03 Sep 2014 12:55:59 -0400 > From: Bryan Fields > To: APP RPT > Subject: Re: [App_rpt-users] EchoLink Policy Reminder > Message-ID: <5407481F.5040201 at bryanfields.net> > Content-Type: text/plain; charset=ISO-8859-1 > > On 9/3/14, 12:34 PM, Tim Sawyer wrote: > > This new (to me) Echolink policy gives me the perfect excuse to turn it off. > Agreed. > > Could be worse, cough IRLP, cough..... > > -- > Bryan Fields > > 727-409-1194 - Voice > 727-214-2508 - Fax > http://bryanfields.net > > > > ------------------------------ > > Message: 4 > Date: Wed, 3 Sep 2014 10:07:03 -0700 > From: Kirk Just Kirk > To: Bryan Fields > Cc: APP RPT > Subject: Re: [App_rpt-users] EchoLink Policy Reminder > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > :) it's OK...IRLP is dying out slowly, Dave's cash register is not ringing > much these days.... > > > On Wed, Sep 3, 2014 at 9:55 AM, Bryan Fields wrote: > > > On 9/3/14, 12:34 PM, Tim Sawyer wrote: > > > This new (to me) Echolink policy gives me the perfect excuse to turn it > > off. > > Agreed. > > > > Could be worse, cough IRLP, cough..... > > > > -- > > Bryan Fields > > > > 727-409-1194 - Voice > > 727-214-2508 - Fax > > http://bryanfields.net > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at 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. > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > End of App_rpt-users Digest, Vol 67, Issue 2 > ******************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From kk6ecm at gmail.com Thu Sep 4 00:33:34 2014 From: kk6ecm at gmail.com (Bob) Date: Wed, 3 Sep 2014 17:33:34 -0700 Subject: [App_rpt-users] Echo In-Reply-To: References: <540771FE.2000709@dyb.com> Message-ID: I know my hearing is not the greatest, but when I connect into my Allstar node via iax, and my friend connects into the node via Echolink from his iPhone, the audio going both ways is very good. When I connect to my node/repeater using my radio, his incoming signal sounds pretty good, but he complains that mine is noisy. I'm going to try a portable radio vs the HT, and see how that works. The service monitor says my HT is under modulated. I guess I'm not understanding the "awful audio" comment. I'd like to learn more about what it is about the audio that makes it less than acceptable. Thanks, Bob kk6ecm _____ From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Kirk Just Kirk Sent: Wednesday, September 03, 2014 1:58 PM To: George Csahanin Cc: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Echo Totally AGREE George, with all the dingbats, the drive by connects/disconnects, the god awful audio, use of foreign languages and the first question...HOW IS THE WEATHER???? I have had mine locked down to -L or -R only to stop the keyboard idiots. I'm thinking of killing it also... On Wed, Sep 3, 2014 at 12:54 PM, George Csahanin wrote: Well, fine. First they gave me hassles a few years ago about having an echolink node but not using their software. Now this? Y'know what? Let them keep their awful audio and the lids, kids and space cadets they attract. I block all but a handful of echolink nodes for those who normally connect just to avoid the horrid audio. But one or two "usual" connections regularly have other connections going to some of the worlds worst audio (usually from San Antonio). And because one of their annointed three couldn't connect to me they kicked up a fuss, so there are three callsigns in my accept list for them. So when I get home from the office today I'll nuke my echolink port, good riddance to the trash and idiots that wouldn't know the business end of a soldering iron.Never used IRLP. Stopped any thought of it when I got to the part where they wanted to sell me something and I had no control over stuff. No way. (I think I have an opinion on these things) GeorgeC W2DB 2360 _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From email at jonbyrne.com Thu Sep 4 08:05:07 2014 From: email at jonbyrne.com (Jon Byrne) Date: Thu, 4 Sep 2014 09:05:07 +0100 Subject: [App_rpt-users] Fwd: EchoLink Policy Reminder In-Reply-To: References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> Message-ID: Morning All Apparently Echolink did a test and Allstarlink allowed them to register a call sign without providing a copy of a valid license, they just needed the Postal and Email address. This is not the way it works for UK License holders, we have to send a copy of our license but is it for US Stations? Regards Jon 2E0RFU ------------ Jon Byrne email at jonbyrne.com On 3 September 2014 18:41, Loren Tedford wrote: > I got the email too not sure what to think.. > > Loren Tedford (KC9ZHV) > Email: lorentedford at gmail.com > Email: lorentedford at live.com > Email: lorentedford at aol.com > Email: LorenCS at Ltcraft.net > Email: lorentedford at yahoo.com > Email: loren at lorentedford.com > Email: loren at richlandcountycomputers.com > Phone: 618-553-0806 > http://www.lorentedford.com > http://www.Ltcraft.net > http://www.richlandcountycomputers.com > http://kc9zhv.lorentedford.com > > > > On Wed, Sep 3, 2014 at 9:55 AM, Buddy Brannan wrote: > >> I wonder if anyone else got this Email? >> >> I have my Echlin attached to an Allstar node number that only is Echlin. >> The RF link, which also allows dial in via All Star web transceiver or >> phone, stays connected to the Echlin All Star node number most of the time, >> but I can drop that at will. Moreover, I think I?ve turned off any access >> to the web transceiver or phone gateway to the Echlin node number. Is there >> anything else I need to do to be in compliance? >> >> As a side note, all of these regulations against interconnecting systems >> are getting kind of ridiculous. >> >> ? >> Buddy Brannan, KB5ELV - Erie, PA >> Phone: 814-860-3194 >> Mobile: 814-431-0962 >> Email: buddy at brannan.name >> >> >> >> > Begin forwarded message: >> > >> > From: "EchoLink Support" >> > Subject: EchoLink Policy Reminder >> > To: "EchoLink Node Operators" <> >> > >> > We wanted to remind you of an important item in EchoLink's access >> policies (which can be found online at >> http://www.echolink.org/access_policies.htm). >> > >> > In general, EchoLink does not permit cross-linking. >> > >> > More specifically, EchoLink does not permit cross-linking with other >> VoIP systems that can be accessed off-the-air (for example, directly from a >> PC or Web browser). This is because other systems may have a validation >> procedure that is far less comprehensive than EchoLink's, and we want to >> continue to ensure that EchoLink is solely for use by licensed Amateur >> Radio operators around the world. >> > >> > Therefore, while excellent systems such as Zello, AllStar, eQSO, >> WIRES-II, etc. all serve an important purpose within the Amateur Radio >> community, our policy is that they cannot be directly connected to a >> registered EchoLink node. >> > >> > In other words, your node must function only as a direct RF gateway, >> and not as a cross-link to another system. If your node is reachable >> through another path, that path must be disabled when an EchoLink >> connection is in progress. For example, an EchoIRLP node is permitted, >> since it functions only as an RF gateway when an EchoLink connection is >> made. >> > >> > If you are running Asterisk with app_rpt and an EchoLink channel, be >> sure it is configured not to allow other VoIP connections when an EchoLink >> station is connected. If this isn't practical, please disable the EchoLink >> channel. >> > >> > Thanks for ensuring that your node adheres to this policy. In some >> cases we do restrict logins to be sure the policy is being followed. >> > >> > 73 >> > EchoLink Support >> > >> > (Note: This mailbox is not able to handle replies. For help and >> information, please see www.echolink.org/support.htm) >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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 at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vencl at att.net Thu Sep 4 11:51:25 2014 From: vencl at att.net (Lu Vencl) Date: Thu, 4 Sep 2014 07:51:25 -0400 Subject: [App_rpt-users] Fwd: EchoLink Policy Reminder In-Reply-To: References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> Message-ID: Allstar is not an enforcement bureau. Neither is Icom, Yeasu, etc. If anyone is on the air without a proper license, I think most of us as hams are capable in knowing what to do. It's not difficult. Personally I am glad to be on a network with rich audio and away from the other undesirable nonsense. I have echolink setup but know with an allow list for emergencies only. Otherwise I would just pull it. Lu Vencl > On Sep 4, 2014, at 4:05 AM, Jon Byrne wrote: > > Morning All > > Apparently Echolink did a test and Allstarlink allowed them to register a call sign without providing a copy of a valid license, they just needed the Postal and Email address. This is not the way it works for UK License holders, we have to send a copy of our license but is it for US Stations? > > Regards > > Jon > 2E0RFU > > ------------ > Jon Byrne > email at jonbyrne.com > > >> On 3 September 2014 18:41, Loren Tedford wrote: >> I got the email too not sure what to think.. >> >> Loren Tedford (KC9ZHV) >> Email: lorentedford at gmail.com >> Email: lorentedford at live.com >> Email: lorentedford at aol.com >> Email: LorenCS at Ltcraft.net >> Email: lorentedford at yahoo.com >> Email: loren at lorentedford.com >> Email: loren at richlandcountycomputers.com >> Phone: 618-553-0806 >> http://www.lorentedford.com >> http://www.Ltcraft.net >> http://www.richlandcountycomputers.com >> http://kc9zhv.lorentedford.com >> >> >> >>> On Wed, Sep 3, 2014 at 9:55 AM, Buddy Brannan wrote: >>> I wonder if anyone else got this Email? >>> >>> I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I?ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? >>> >>> As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. >>> >>> ? >>> Buddy Brannan, KB5ELV - Erie, PA >>> Phone: 814-860-3194 >>> Mobile: 814-431-0962 >>> Email: buddy at brannan.name >>> >>> >>> >>> > Begin forwarded message: >>> > >>> > From: "EchoLink Support" >>> > Subject: EchoLink Policy Reminder >>> > To: "EchoLink Node Operators" <> >>> > >>> > We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm). >>> > >>> > In general, EchoLink does not permit cross-linking. >>> > >>> > More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world. >>> > >>> > Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node. >>> > >>> > In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made. >>> > >>> > If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel. >>> > >>> > Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed. >>> > >>> > 73 >>> > EchoLink Support >>> > >>> > (Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm) >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike.lussier at gmail.com Thu Sep 4 12:16:09 2014 From: mike.lussier at gmail.com (Mike Lussier) Date: Thu, 4 Sep 2014 08:16:09 -0400 Subject: [App_rpt-users] App_rpt-users Digest, Vol 67, Issue 5 In-Reply-To: References: Message-ID: Good morning all, Could this be that Echo link because of their lack of security, Behind closed doors has gotten its wrist smacked and they are just looking for some one else to blame for the trouble ? Just my two cents I have echolink setup on one of my repeaters as of right now. I have two of the four repeaters with the ALL Star link setup , I'm not sure how much echolink will be used. Mike AE4ML > 1. Re: Fwd: EchoLink Policy Reminder (Jon Byrne) > 2. Re: Fwd: EchoLink Policy Reminder (Lu Vencl) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 4 Sep 2014 09:05:07 +0100 > From: Jon Byrne > To: Loren Tedford > Cc: app_rpt mailing list > Subject: Re: [App_rpt-users] Fwd: EchoLink Policy Reminder > Message-ID: > bFGBgUwSr2KM0BNrY9yKOq7WgYe9PHKw at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Morning All > > Apparently Echolink did a test and Allstarlink allowed them to register a > call sign without providing a copy of a valid license, they just needed the > Postal and Email address. This is not the way it works for UK License > holders, we have to send a copy of our license but is it for US Stations? > > Regards > > Jon > 2E0RFU > > ------------ > Jon Byrne > email at jonbyrne.com > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdboyle at bdboyle.com Thu Sep 4 12:25:40 2014 From: bdboyle at bdboyle.com (Bryan D. Boyle) Date: Thu, 4 Sep 2014 08:25:40 -0400 Subject: [App_rpt-users] Fwd: EchoLink Policy Reminder In-Reply-To: References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> Message-ID: <03C00826-32F0-41B9-A8E1-D07EF35D1677@bdboyle.com> Alternative (since it does have a use...) is to register a node, assign the echolink channel to it, but leave it disconnected unless it's needed (dummy load node?) write a couple scripts that use the allstar management interface to control the node, and build a smartphone-compatible web interface to it. :) it's what i have on my node cluster. That way, you can raise the echo node when YOU need it, and take it down when you don't. Echolink is ancient technology, hasn't been updated in over a decade, but is not entirely worthless, regardless of what the League thinks. I do find it marginally useful when out of range of the NJ/PA network, but am circumspect in how it gets used. Maybe most of the clueless (l)users aren't, but I'm thinking the combined cerebral power of this list isn't in that camp. -- Bryan Sent from my iPhone 5...No electrons were harmed in the sending of this message. > On Sep 4, 2014, at 7:51, Lu Vencl wrote: > > Allstar is not an enforcement bureau. Neither is Icom, Yeasu, etc. If anyone is on the air without a proper license, I think most of us as hams are capable in knowing what to do. It's not difficult. > Personally I am glad to be on a network with rich audio and away from the other undesirable nonsense. I have echolink setup but know with an allow list for emergencies only. > Otherwise I would just pull it. > > Lu Vencl > >> On Sep 4, 2014, at 4:05 AM, Jon Byrne wrote: >> >> Morning All >> >> Apparently Echolink did a test and Allstarlink allowed them to register a call sign without providing a copy of a valid license, they just needed the Postal and Email address. This is not the way it works for UK License holders, we have to send a copy of our license but is it for US Stations? >> >> Regards >> >> Jon >> 2E0RFU >> >> ------------ >> Jon Byrne >> email at jonbyrne.com >> >> >>> On 3 September 2014 18:41, Loren Tedford wrote: >>> I got the email too not sure what to think.. >>> >>> Loren Tedford (KC9ZHV) >>> Email: lorentedford at gmail.com >>> Email: lorentedford at live.com >>> Email: lorentedford at aol.com >>> Email: LorenCS at Ltcraft.net >>> Email: lorentedford at yahoo.com >>> Email: loren at lorentedford.com >>> Email: loren at richlandcountycomputers.com >>> Phone: 618-553-0806 >>> http://www.lorentedford.com >>> http://www.Ltcraft.net >>> http://www.richlandcountycomputers.com >>> http://kc9zhv.lorentedford.com >>> >>> >>> >>>> On Wed, Sep 3, 2014 at 9:55 AM, Buddy Brannan wrote: >>>> I wonder if anyone else got this Email? >>>> >>>> I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I?ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? >>>> >>>> As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. >>>> >>>> ? >>>> Buddy Brannan, KB5ELV - Erie, PA >>>> Phone: 814-860-3194 >>>> Mobile: 814-431-0962 >>>> Email: buddy at brannan.name >>>> >>>> >>>> >>>> > Begin forwarded message: >>>> > >>>> > From: "EchoLink Support" >>>> > Subject: EchoLink Policy Reminder >>>> > To: "EchoLink Node Operators" <> >>>> > >>>> > We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm). >>>> > >>>> > In general, EchoLink does not permit cross-linking. >>>> > >>>> > More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world. >>>> > >>>> > Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node. >>>> > >>>> > In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made. >>>> > >>>> > If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel. >>>> > >>>> > Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed. >>>> > >>>> > 73 >>>> > EchoLink Support >>>> > >>>> > (Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm) >>>> >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ea8ee1 at gmail.com Thu Sep 4 15:05:58 2014 From: ea8ee1 at gmail.com (ea8ee) Date: Thu, 4 Sep 2014 17:05:58 +0200 Subject: [App_rpt-users] Fwd: EchoLink Policy Reminder In-Reply-To: <03C00826-32F0-41B9-A8E1-D07EF35D1677@bdboyle.com> References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> <03C00826-32F0-41B9-A8E1-D07EF35D1677@bdboyle.com> Message-ID: a good options is disable echolink only a call from webtransceiver is active and then enable when the webstransceiver isnt active El jueves, 4 de septiembre de 2014, Bryan D. Boyle escribi?: > Alternative (since it does have a use...) is to register a node, assign > the echolink channel to it, but leave it disconnected unless it's needed > (dummy load node?) > > write a couple scripts that use the allstar management interface to > control the node, and build a smartphone-compatible web interface to it. > :) it's what i have on my node cluster. > > That way, you can raise the echo node when YOU need it, and take it down > when you don't. > > Echolink is ancient technology, hasn't been updated in over a decade, but > is not entirely worthless, regardless of what the League thinks. I do find > it marginally useful when out of range of the NJ/PA network, but am > circumspect in how it gets used. > > Maybe most of the clueless (l)users aren't, but I'm thinking the combined > cerebral power of this list isn't in that camp. > > -- > Bryan > Sent from my iPhone 5...No electrons were harmed in the sending of this > message. > > > > On Sep 4, 2014, at 7:51, Lu Vencl > wrote: > > Allstar is not an enforcement bureau. Neither is Icom, Yeasu, etc. If > anyone is on the air without a proper license, I think most of us as hams > are capable in knowing what to do. It's not difficult. > Personally I am glad to be on a network with rich audio and away from the > other undesirable nonsense. I have echolink setup but know with an allow > list for emergencies only. > Otherwise I would just pull it. > > Lu Vencl > > On Sep 4, 2014, at 4:05 AM, Jon Byrne > wrote: > > Morning All > > Apparently Echolink did a test and Allstarlink allowed them to register a > call sign without providing a copy of a valid license, they just needed the > Postal and Email address. This is not the way it works for UK License > holders, we have to send a copy of our license but is it for US Stations? > > Regards > > Jon > 2E0RFU > > ------------ > Jon Byrne > email at jonbyrne.com > > > On 3 September 2014 18:41, Loren Tedford > wrote: > >> I got the email too not sure what to think.. >> >> Loren Tedford (KC9ZHV) >> Email: lorentedford at gmail.com >> >> Email: lorentedford at live.com >> >> Email: lorentedford at aol.com >> >> Email: LorenCS at Ltcraft.net >> >> Email: lorentedford at yahoo.com >> >> Email: loren at lorentedford.com >> >> Email: loren at richlandcountycomputers.com >> >> Phone: 618-553-0806 >> http://www.lorentedford.com >> http://www.Ltcraft.net >> http://www.richlandcountycomputers.com >> http://kc9zhv.lorentedford.com >> >> >> >> On Wed, Sep 3, 2014 at 9:55 AM, Buddy Brannan > > wrote: >> >>> I wonder if anyone else got this Email? >>> >>> I have my Echlin attached to an Allstar node number that only is Echlin. >>> The RF link, which also allows dial in via All Star web transceiver or >>> phone, stays connected to the Echlin All Star node number most of the time, >>> but I can drop that at will. Moreover, I think I've turned off any access >>> to the web transceiver or phone gateway to the Echlin node number. Is there >>> anything else I need to do to be in compliance? >>> >>> As a side note, all of these regulations against interconnecting systems >>> are getting kind of ridiculous. >>> >>> -- >>> Buddy Brannan, KB5ELV - Erie, PA >>> Phone: 814-860-3194 >>> Mobile: 814-431-0962 >>> Email: buddy at brannan.name >>> >>> >>> >>> >>> > Begin forwarded message: >>> > >>> > From: "EchoLink Support" >> > >>> > Subject: EchoLink Policy Reminder >>> > To: "EchoLink Node Operators" <> >>> > >>> > We wanted to remind you of an important item in EchoLink's access >>> policies (which can be found online at >>> http://www.echolink.org/access_policies.htm). >>> > >>> > In general, EchoLink does not permit cross-linking. >>> > >>> > More specifically, EchoLink does not permit cross-linking with other >>> VoIP systems that can be accessed off-the-air (for example, directly from a >>> PC or Web browser). This is because other systems may have a validation >>> procedure that is far less comprehensive than EchoLink's, and we want to >>> continue to ensure that EchoLink is solely for use by licensed Amateur >>> Radio operators around the world. >>> > >>> > Therefore, while excellent systems such as Zello, AllStar, eQSO, >>> WIRES-II, etc. all serve an important purpose within the Amateur Radio >>> community, our policy is that they cannot be directly connected to a >>> registered EchoLink node. >>> > >>> > In other words, your node must function only as a direct RF gateway, >>> and not as a cross-link to another system. If your node is reachable >>> through another path, that path must be disabled when an EchoLink >>> connection is in progress. For example, an EchoIRLP node is permitted, >>> since it functions only as an RF gateway when an EchoLink connection is >>> made. >>> > >>> > If you are running Asterisk with app_rpt and an EchoLink channel, be >>> sure it is configured not to allow other VoIP connections when an EchoLink >>> station is connected. If this isn't practical, please disable the EchoLink >>> channel. >>> > >>> > Thanks for ensuring that your node adheres to this policy. In some >>> cases we do restrict logins to be sure the policy is being followed. >>> > >>> > 73 >>> > EchoLink Support >>> > >>> > (Note: This mailbox is not able to handle replies. For help and >>> information, please see www.echolink.org/support.htm) >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at 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 at 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 at 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 at 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. > > -- Enviado desde EA8EE red movil -------------- next part -------------- An HTML attachment was scrubbed... URL: From N1XBM at amsat.org Thu Sep 4 22:22:05 2014 From: N1XBM at amsat.org (Robert Newberry) Date: Thu, 4 Sep 2014 18:22:05 -0400 Subject: [App_rpt-users] Networks with chatter Message-ID: I can't seem to find an archive to search. Someone had a thread on here about networks with activity. I have a new repeater and I'm looking for a few networks to monitor/talk. Obviously I'm going to leave it disconnected during our commute time, but it would be nice to generate some chatter during the day and evening hours. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Thu Sep 4 22:49:46 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Thu, 04 Sep 2014 15:49:46 -0700 Subject: [App_rpt-users] Networks with chatter In-Reply-To: References: Message-ID: Win System, Allstar Node 2560. -- Tim :wq On Sep 4, 2014, at 3:22 PM, Robert Newberry wrote: > I can't seem to find an archive to search. Someone had a thread on here about networks with activity. > > I have a new repeater and I'm looking for a few networks to monitor/talk. Obviously I'm going to leave it disconnected during our commute time, but it would be nice to generate some chatter during the day and evening hours. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdboyle at bdboyle.com Thu Sep 4 22:56:53 2014 From: bdboyle at bdboyle.com (Bryan D. Boyle) Date: Thu, 4 Sep 2014 18:56:53 -0400 Subject: [App_rpt-users] Networks with chatter In-Reply-To: References: Message-ID: you'll have more continuous noise...than you know what to do. make sure you've got good cooling on the transmitter. -- Bryan Sent from my iPhone 5...No electrons were harmed in the sending of this message. > On Sep 4, 2014, at 18:49, Tim Sawyer wrote: > > Win System, Allstar Node 2560. > -- > Tim > :wq > >> On Sep 4, 2014, at 3:22 PM, Robert Newberry wrote: >> >> I can't seem to find an archive to search. Someone had a thread on here about networks with activity. >> >> I have a new repeater and I'm looking for a few networks to monitor/talk. Obviously I'm going to leave it disconnected during our commute time, but it would be nice to generate some chatter during the day and evening hours. >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ar at dseven.org Thu Sep 4 23:26:47 2014 From: ar at dseven.org (iain macdonnell - N6ML) Date: Thu, 4 Sep 2014 16:26:47 -0700 Subject: [App_rpt-users] Networks with chatter In-Reply-To: References: Message-ID: The bubble-map is kindof interesting when connected there too! 73, ~iain / N6ML On Thu, Sep 4, 2014 at 3:56 PM, Bryan D. Boyle wrote: > you'll have more continuous noise...than you know what to do. make sure > you've got good cooling on the transmitter. > > -- > Bryan > Sent from my iPhone 5...No electrons were harmed in the sending of this > message. > > > > On Sep 4, 2014, at 18:49, Tim Sawyer wrote: > > Win System, Allstar Node 2560. > -- > Tim > :wq > > On Sep 4, 2014, at 3:22 PM, Robert Newberry wrote: > > I can't seem to find an archive to search. Someone had a thread on here > about networks with activity. > > I have a new repeater and I'm looking for a few networks to monitor/talk. > Obviously I'm going to leave it disconnected during our commute time, but it > would be nice to generate some chatter during the day and evening hours. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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 at 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. From N1XBM at amsat.org Fri Sep 5 01:54:03 2014 From: N1XBM at amsat.org (Robert Newberry) Date: Thu, 4 Sep 2014 21:54:03 -0400 Subject: [App_rpt-users] Networks with chatter In-Reply-To: References: Message-ID: Thank you everyone who replied. I've got plenty of nodes to drop into now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From electricity440 at gmail.com Fri Sep 5 12:59:15 2014 From: electricity440 at gmail.com (Skyler F) Date: Fri, 5 Sep 2014 06:59:15 -0600 Subject: [App_rpt-users] using IRLP seperately Message-ID: HI, So I know that it is banned by IRLP to cross connect, but is there a way to dial an IRLP node separately (and disable cross connecting) using an allstar system? 73 Skyler KD?WHB -- Skyler Fennell amsatnet.info KD?WHB electricity440 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From n8ohu at yahoo.com Fri Sep 5 22:25:21 2014 From: n8ohu at yahoo.com (Matthew Pitts) Date: Fri, 5 Sep 2014 15:25:21 -0700 Subject: [App_rpt-users] using IRLP seperately In-Reply-To: References: Message-ID: <1409955921.52044.YahooMailNeo@web141001.mail.bf1.yahoo.com> Not since the IRLP support was removed some years back at Mr. Cameron's request. Matthew Pitts N8OHU ________________________________ From: Skyler F To: "app_rpt-users at ohnosec.org" Sent: Friday, September 5, 2014 8:59 AM Subject: [App_rpt-users] using IRLP seperately HI, So I know that it is banned by IRLP to cross connect, but is there a way to dial an IRLP node separately (and disable cross connecting) using an allstar system? 73 Skyler KD?WHB -- Skyler Fennell amsatnet.info KD?WHB electricity440 at gmail.com _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ars.w5omr at gmail.com Sat Sep 6 12:33:18 2014 From: ars.w5omr at gmail.com (Geoff) Date: Sat, 06 Sep 2014 07:33:18 -0500 Subject: [App_rpt-users] EchoLink Policy Reminder In-Reply-To: <5407481F.5040201@bryanfields.net> References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> <5407481F.5040201@bryanfields.net> Message-ID: <540AFF0E.8050308@gmail.com> On 09/03/2014 11:55 AM, Bryan Fields wrote: > On 9/3/14, 12:34 PM, Tim Sawyer wrote: >> This new (to me) Echolink policy gives me the perfect excuse to turn it off. > Agreed. > > Could be worse, cough IRLP, cough..... > at least IRLP -sounds- (or could, anyway) a lot better than EchoClunk. From bdboyle at bdboyle.com Sat Sep 6 13:11:24 2014 From: bdboyle at bdboyle.com (Bryan D. Boyle) Date: Sat, 06 Sep 2014 09:11:24 -0400 Subject: [App_rpt-users] EchoLink Policy Reminder In-Reply-To: <540AFF0E.8050308@gmail.com> References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> <5407481F.5040201@bryanfields.net> <540AFF0E.8050308@gmail.com> Message-ID: <540B07FC.8070108@bdboyle.com> On 9/6/2014 8:33 AM, Geoff wrote: > at least IRLP -sounds- (or could, anyway) a lot better than EchoClunk. Could being the operative word. Considering lots of people have no bloody idea what good audio sounds like, how to set levels ("What do you mean, I shouldn't bounce the VU meter indicator off the right hand stop?") let alone how limiting, compression, pre/de-emphasis, average modulation level, modulation indices, etc all interact...and then throw in the pee-poor codec, hacked together applications, and variable internet connectivity... All you have to do is listen to the pedantic and tiring discussion over audio quality on the trbo list and whether or not to use AGC, setting levels using an ephemeral LED VU meter with a webcam on it...and you'd quickly 1) tire of the discussion, and 2) give thanks to whatever deity (or not) that Allstar is as good as it is. End even with blatant, clear, and simple-to-follow directions...people still futz it up. B From jrorke at cogeco.ca Sat Sep 6 13:14:11 2014 From: jrorke at cogeco.ca (REDBUTTON_CTRL) Date: Sat, 06 Sep 2014 09:14:11 -0400 Subject: [App_rpt-users] EchoLink Policy Reminder In-Reply-To: <540AFF0E.8050308@gmail.com> References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> <5407481F.5040201@bryanfields.net> <540AFF0E.8050308@gmail.com> Message-ID: <540B08A3.6030609@cogeco.ca> Correct me if I'm wrong but setting up an Allstar node doesnt set up an Echolink node. You must already have an Echolink node to embed into the Allstar node. So you must already have a call sign to get an Echolink node number right? And you must also have a call sign to have an Allstar node right? So how does having an Echolink node embedded into your Allstar node have to do with non licensed people getting into Echolink? I dont have any Echolink nodes so I dont know but just asking. Or is the problem the cross linking voip systems thing? Ahh just love the politics. Next thing you know the Dstar crowd will be banning analog bridges.... wait they are! Allstar does everything Echolink does and IRLP too and more. So that's why I dont bother with Echolink. I have IRLP on a separate system but its almost never used. Time for the rest of the word to migrate to Allstar. VA3RQ On 9/6/2014 8:33 AM, Geoff wrote: > On 09/03/2014 11:55 AM, Bryan Fields wrote: >> On 9/3/14, 12:34 PM, Tim Sawyer wrote: >>> This new (to me) Echolink policy gives me the perfect excuse to turn it off. >> Agreed. >> >> Could be worse, cough IRLP, cough..... >> > at least IRLP -sounds- (or could, anyway) a lot better than EchoClunk. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > From ars.w5omr at gmail.com Sat Sep 6 13:24:12 2014 From: ars.w5omr at gmail.com (Geoff) Date: Sat, 06 Sep 2014 08:24:12 -0500 Subject: [App_rpt-users] Problem with two repeaters.. In-Reply-To: References: Message-ID: <540B0AFC.7020102@gmail.com> On 09/03/2014 12:45 PM, Loren Tedford wrote: > Hello having issues running both repeaters for some reason it is > telling me that Device usb27103 currently not active what does this > mean? its all plugged in was working then all the suddenly stopped > working randomly is it not detecting the device number correctly with > the URI? I am running 2 Cm200 on vhf for this repeater and node 29925 > is running flawlessly with out any issues with 2 Cm200 on UHF > Sometimes, things happen. Some software bug causes the usb daemon to fall, or something... On that note, I did a quick google search for start/stop/status on usb devices for CentOS and came up with http://www.zedt.eu/tech/linux/restarting-usb-subsystem-centos/ Their suggestion of looking in |/sys/bus/pci/drivers/ehci_hcd or xhci_hcd doesn't exist in my directory path. So, I did a 'lsusb' and came up with: [root at W5OMR /sys/bus/usb/drivers/usbfs]# lsusb Bus 005 Device 001: ID 0000:0000 Bus 005 Device 003: ID 0d8c:013a C-Media Electronics, Inc. Bus 005 Device 002: ID 0d8c:013a C-Media Electronics, Inc. Bus 002 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 | >From the link, they suggest;| echo -n "0000:00:xx.y" > unbind| Remember to enable them back: |echo -n "0000:00:xx.y" > bind| where instead of xx.y you fill in the correct set of numbers to use the IDs discovered above. This procedure is the same for all RHEL-like distributions (Red Hat Enterprise, CentOS, Fedora). The bottom line is, there's hardly ever a reason to reboot an entire working Linux operating system loaded machine. Services can stopped and restarted from the command line without the need to reboot the entire system. I have had, on occasion, the need to restart the networking sub-system. By performing a root at w5omr> /etc/init.d/networking restart takes care of that problem. Just my 0.02c 73 = Best Regards, -Geoff/W5OMR -------------- next part -------------- An HTML attachment was scrubbed... URL: From electricity440 at gmail.com Sat Sep 6 14:08:26 2014 From: electricity440 at gmail.com (Skyler F) Date: Sat, 6 Sep 2014 08:08:26 -0600 Subject: [App_rpt-users] List of IRLP reflectors with allstar Message-ID: I want to communicate with someone using an IRLP node. The only way is through an IRLP reflector with allstar. Is there a list anywhere of all of the IRLP reflectors which have AllStar on them? I don't want to go through an echoIrlp because the audio sucks and echo-links new policy. 73 Skyler KD?WHB -- Skyler Fennell amsatnet.info KD?WHB electricity440 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From k0xm at byrg.net Sat Sep 6 14:18:41 2014 From: k0xm at byrg.net (Chuck Kraly) Date: Sat, 6 Sep 2014 07:18:41 -0700 Subject: [App_rpt-users] List of IRLP reflectors with allstar In-Reply-To: References: Message-ID: Skyler, There is no way that there will be an IRLP connect- at least not one that will be passed on in a public forum. Dave has informed the developers to remove- not disable the IRLP connections. Now, is that saying there will not be a "backdoor" connection? No. but officially there will not be on mentioned. On Sat, Sep 6, 2014 at 7:08 AM, Skyler F wrote: > I want to communicate with someone using an IRLP node. The only way is > through an IRLP reflector with allstar. > > Is there a list anywhere of all of the IRLP reflectors which have AllStar > on them? I don't want to go through an echoIrlp because the audio sucks and > echo-links new policy. > > 73 > Skyler KD?WHB > > -- > Skyler Fennell > amsatnet.info > KD?WHB > electricity440 at gmail.com > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > -- Chuck K0XM Backyard Repeater Group k0xm at byrg.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From electricity440 at gmail.com Sat Sep 6 14:20:40 2014 From: electricity440 at gmail.com (Skyler F) Date: Sat, 6 Sep 2014 08:20:40 -0600 Subject: [App_rpt-users] List of IRLP reflectors with allstar In-Reply-To: References: Message-ID: Well im just thinking of the alaska reflector for instance, you can go there weather you have irlp, allstar or echolink On Sat, Sep 6, 2014 at 8:18 AM, Chuck Kraly wrote: > Skyler, > There is no way that there will be an IRLP connect- at least not one that > will be passed on in a public forum. Dave has informed the developers to > remove- not disable the IRLP connections. Now, is that saying there will > not be a "backdoor" connection? No. but officially there will not be on > mentioned. > > > > On Sat, Sep 6, 2014 at 7:08 AM, Skyler F wrote: > >> I want to communicate with someone using an IRLP node. The only way is >> through an IRLP reflector with allstar. >> >> Is there a list anywhere of all of the IRLP reflectors which have AllStar >> on them? I don't want to go through an echoIrlp because the audio sucks and >> echo-links new policy. >> >> 73 >> Skyler KD?WHB >> >> -- >> Skyler Fennell >> amsatnet.info >> KD?WHB >> electricity440 at gmail.com >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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. >> > > > > -- > Chuck K0XM > Backyard Repeater Group > k0xm at byrg.net > -- Skyler Fennell amsatnet.info KD?WHB electricity440 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ea8ee1 at gmail.com Sat Sep 6 14:26:52 2014 From: ea8ee1 at gmail.com (ea8ee) Date: Sat, 6 Sep 2014 16:26:52 +0200 Subject: [App_rpt-users] List of IRLP reflectors with allstar In-Reply-To: References: Message-ID: node 0063 irlp main spanish traffic limked to dstar xrf007b and alt 27684 El s?bado, 6 de septiembre de 2014, Skyler F escribi?: > I want to communicate with someone using an IRLP node. The only way is > through an IRLP reflector with allstar. > > Is there a list anywhere of all of the IRLP reflectors which have AllStar > on them? I don't want to go through an echoIrlp because the audio sucks and > echo-links new policy. > > 73 > Skyler KD?WHB > > -- > Skyler Fennell > amsatnet.info > KD?WHB > electricity440 at gmail.com > > -- Enviado desde EA8EE red movil -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike at midnighteng.com Sat Sep 6 15:14:58 2014 From: mike at midnighteng.com (mike at midnighteng.com) Date: Sat, 06 Sep 2014 08:14:58 -0700 Subject: [App_rpt-users] =?utf-8?q?Problem_with_two_repeaters=2E=2E?= Message-ID: <20140906081458.71befee5dbd13c5325dd1a521b4e73ee.b2880bd421.wbe@email06.secureserver.net> An HTML attachment was scrubbed... URL: From mike.lussier at gmail.com Sat Sep 6 17:47:46 2014 From: mike.lussier at gmail.com (Mike Lussier) Date: Sat, 6 Sep 2014 13:47:46 -0400 Subject: [App_rpt-users] WX Alert scripts Message-ID: Good afternoon to all, I have a question on the weather alert scripts that I have been reading about. Before I attempt to add this to my pair of nodes has any one else done this on the Beagle Bone Black ? I don't want to over load them but this is something that I feel is of great importance. Thank you Mike AE4ML -- *"We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan* -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sat Sep 6 17:57:05 2014 From: doug at crompton.com (Doug Crompton) Date: Sat, 6 Sep 2014 13:57:05 -0400 Subject: [App_rpt-users] WX Alert scripts In-Reply-To: References: Message-ID: The weather forecast and alert scripts will be an option in the next release of the BBB code in about 2 weeks. I would wait for that because in general you will want to update to this version as there will also be a great USB stability increase and wifi that actually works. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Sat, 6 Sep 2014 13:47:46 -0400 From: mike.lussier at gmail.com To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] WX Alert scripts Good afternoon to all, I have a question on the weather alert scripts that I have been reading about. Before I attempt to add this to my pair of nodes has any one else done this on the Beagle Bone Black ? I don't want to over load them but this is something that I feel is of great importance. Thank you Mike AE4ML -- "We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike.lussier at gmail.com Sat Sep 6 18:09:08 2014 From: mike.lussier at gmail.com (Michael Lussier) Date: Sat, 6 Sep 2014 14:09:08 -0400 Subject: [App_rpt-users] WX Alert scripts In-Reply-To: References: Message-ID: <342C5604-471C-4950-B613-785270975C13@gmail.com> Thanks Doug , I will wait for the release. These are keeping busy here learning more about functions and DTMF Mike AE4ML Sent from an iPhone 5 > On Sep 6, 2014, at 13:57, Doug Crompton wrote: > > The weather forecast and alert scripts will be an option in the next release of the BBB code in about 2 weeks. I would wait for that because in general you will want to update to this version as there will also be a great USB stability increase and wifi that actually works. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > Date: Sat, 6 Sep 2014 13:47:46 -0400 > From: mike.lussier at gmail.com > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] WX Alert scripts > > Good afternoon to all, > I have a question on the weather alert scripts that I have been reading about. Before I attempt to add this to my pair of nodes has any one else done this on the Beagle Bone Black ? I don't want to over load them but this is something that I feel is of great importance. > > Thank you > > Mike AE4ML > > -- > "We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan > > > > _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ars.w5omr at gmail.com Sun Sep 7 02:20:39 2014 From: ars.w5omr at gmail.com (Geoff) Date: Sat, 06 Sep 2014 21:20:39 -0500 Subject: [App_rpt-users] Fwd: EchoLink Policy Reminder In-Reply-To: <03C00826-32F0-41B9-A8E1-D07EF35D1677@bdboyle.com> References: <201409031438.s83EcKnY015738@domU-12-31-39-01-5C-91> <26137683-3BBF-41CE-BB0E-FD96C151E850@brannan.name> <03C00826-32F0-41B9-A8E1-D07EF35D1677@bdboyle.com> Message-ID: <540BC0F7.1090604@gmail.com> In case anyone is interested, my take on the whole Echolink thing is, it's an option that is available, when I want or need it. I use it to connect with my SmartPhone when I'm out of repeater range from my system, or any that are linked to it. Perfect example, I was in Ozona, Tx earlier this week, and echolinked on my phone to my repeater, after disconnecting my nodes from the outside world. Echolinked in at the time the family was going to/from work, so I could talk to them from outside the network. For that, it works great. For me. I'm leaving things as they are. -Geoff/W5OMR From kk6ecm at gmail.com Sun Sep 7 18:15:59 2014 From: kk6ecm at gmail.com (Bob) Date: Sun, 7 Sep 2014 11:15:59 -0700 Subject: [App_rpt-users] Beagleboard-XM & LOX Message-ID: <7F56E3AEB39E41BBBAFEC1D049A47EE6@ThePykesHP> I've been running my Beagleboard-XM with LOX for about 9 months. It has recently stopped working; Asterisk stops running, and the LOX PTT LED lights. When I do a reboot (from the command line or by power reset) it works fine for a week or so, then does it again. I suspect the Beagleboard-XM is having memory errors, but since Asterisk stops running, I can't get into asterisk -r to see what it is doing (just returns me to the Linux command line). Other than this, it works fine. Has anyone had this experience? If so, did you find a solution other than using crontab to reboot weekly? Thanks, Bob kk6ecm -------------- next part -------------- An HTML attachment was scrubbed... URL: From zeppelin.1 at netzero.com Sun Sep 7 20:20:49 2014 From: zeppelin.1 at netzero.com (zeppelin.1 at netzero.com) Date: Sun, 7 Sep 2014 20:20:49 GMT Subject: [App_rpt-users] URI GPIO manipulation Message-ID: <20140907.162049.21786.0@webmail07.dca.untd.com> Greetings; a technical question for anyone interested in answering. Incorporated k0kn txfan script on node 29103 successfully controlling a fan via PP4. Has anyone attempted controlling a fan via URI gpio4 with success? Anton/ kc2rqr Node 29103 ____________________________________________________________ The #1 Worst Carb Ever? Click to Learn #1 Carb that Kills Your Blood Sugar (Don't Eat This!) http://thirdpartyoffers.netzero.net/TGL3231/540cbe459554b3e45237bst02duc From petem001 at hotmail.com Mon Sep 8 02:38:29 2014 From: petem001 at hotmail.com (pete M) Date: Sun, 7 Sep 2014 22:38:29 -0400 Subject: [App_rpt-users] debian? Message-ID: I want to do a central node for my repeaters.. I have 2 repeater on a site , another is already online and 2 other comming in soon.. I want them linked permanently but dont want to have any of those server as the central node cause none have the abndwith for it.. So I stumbled on a company that host vps server for real cheap.. But they are on debian. is it possible to install a node on a debian system? can someone point me in the right direction? Thanks Pierre VE2PFpresident VE2MRC for the curious.. here is the hosting company:https://www.beastnode.com/vps -------------- next part -------------- An HTML attachment was scrubbed... URL: From petem001 at hotmail.com Mon Sep 8 02:48:40 2014 From: petem001 at hotmail.com (pete M) Date: Sun, 7 Sep 2014 22:48:40 -0400 Subject: [App_rpt-users] debian? In-Reply-To: References: Message-ID: Never mind.. Just found out they can have a debian 5 installed.. https://www.beastnode.com/portal/knowledgebase/110/Operating-System-Templates-or-ISOs.html From: petem001 at hotmail.com To: app_rpt-users at ohnosec.org Date: Sun, 7 Sep 2014 22:38:29 -0400 Subject: [App_rpt-users] debian? I want to do a central node for my repeaters.. I have 2 repeater on a site , another is already online and 2 other comming in soon.. I want them linked permanently but dont want to have any of those server as the central node cause none have the abndwith for it.. So I stumbled on a company that host vps server for real cheap.. But they are on debian. is it possible to install a node on a debian system? can someone point me in the right direction? Thanks Pierre VE2PFpresident VE2MRC for the curious.. here is the hosting company:https://www.beastnode.com/vps _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From petem001 at hotmail.com Mon Sep 8 04:32:38 2014 From: petem001 at hotmail.com (pete M) Date: Mon, 8 Sep 2014 00:32:38 -0400 Subject: [App_rpt-users] beastnode (was debian) In-Reply-To: References: , Message-ID: Ok got a 3 month account with them.. got debian 5 installed.. of course the kernel is way too new to install asterisk with out problem here is the output for the version of the kernel.:# cat /proc/versionLinux version 2.6.32-042stab093.4 (root at kbuild-rh6-x64) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Mon Aug 11 18:47:39 MSK 2014 So if I run phase2.sh from /etc/rc.d/ ( I did copy the script there and the acidrepo file at the same place, I have an error, can't compile zaptel. here is the last few lines from the compiler: make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml'gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.amake[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect'make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect'Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue.*********************************************************** make: *** [menuselect.makeopts] Error 255Failure: Unable to compile Zaptel 2Fatal error: Unable to install Asterisk![root at node rc.d]# Anyone have a simple answer to this? Do I need zaptel since I wont be connecting and radio directly to this server? If I dont need it. How do I prevent the install script from compiling it? Lots of question.. But I am not that used to such stuff ;-) Pierre MartelVE2PF From: petem001 at hotmail.com To: app_rpt-users at ohnosec.org Date: Sun, 7 Sep 2014 22:48:40 -0400 Subject: Re: [App_rpt-users] debian? Never mind.. Just found out they can have a debian 5 installed.. https://www.beastnode.com/portal/knowledgebase/110/Operating-System-Templates-or-ISOs.html From: petem001 at hotmail.com To: app_rpt-users at ohnosec.org Date: Sun, 7 Sep 2014 22:38:29 -0400 Subject: [App_rpt-users] debian? I want to do a central node for my repeaters.. I have 2 repeater on a site , another is already online and 2 other comming in soon.. I want them linked permanently but dont want to have any of those server as the central node cause none have the abndwith for it.. So I stumbled on a company that host vps server for real cheap.. But they are on debian. is it possible to install a node on a debian system? can someone point me in the right direction? Thanks Pierre VE2PFpresident VE2MRC for the curious.. here is the hosting company:https://www.beastnode.com/vps _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Mon Sep 8 05:18:38 2014 From: doug at crompton.com (Doug Crompton) Date: Mon, 8 Sep 2014 01:18:38 -0400 Subject: [App_rpt-users] beastnode (was debian) In-Reply-To: References: , , , Message-ID: Pete, It has been awhile since I have done it but I have a PC system in the basement that has acid on it with Debian. I was experimenting when i was working on the RPi. You need to use dahdi not zaptel. I could probably tar up the source. It doesn't have the dahdi patches but they could easily be added. It was the latest Debian at the time - about last April or so. It did work well. You would have to setup the compile environment and recompile. If you are not comfortable with mucking in Linux then it might be a problem. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: app_rpt-users at ohnosec.org Date: Mon, 8 Sep 2014 00:32:38 -0400 Subject: Re: [App_rpt-users] beastnode (was debian) Ok got a 3 month account with them.. got debian 5 installed.. of course the kernel is way too new to install asterisk with out problem here is the output for the version of the kernel.:# cat /proc/versionLinux version 2.6.32-042stab093.4 (root at kbuild-rh6-x64) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Mon Aug 11 18:47:39 MSK 2014 So if I run phase2.sh from /etc/rc.d/ ( I did copy the script there and the acidrepo file at the same place, I have an error, can't compile zaptel. here is the last few lines from the compiler: make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml'gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.amake[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect'make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect'Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue.*********************************************************** make: *** [menuselect.makeopts] Error 255Failure: Unable to compile Zaptel 2Fatal error: Unable to install Asterisk![root at node rc.d]# Anyone have a simple answer to this? Do I need zaptel since I wont be connecting and radio directly to this server? If I dont need it. How do I prevent the install script from compiling it? Lots of question.. But I am not that used to such stuff ;-) Pierre MartelVE2PF From: petem001 at hotmail.com To: app_rpt-users at ohnosec.org Date: Sun, 7 Sep 2014 22:48:40 -0400 Subject: Re: [App_rpt-users] debian? Never mind.. Just found out they can have a debian 5 installed.. https://www.beastnode.com/portal/knowledgebase/110/Operating-System-Templates-or-ISOs.html From: petem001 at hotmail.com To: app_rpt-users at ohnosec.org Date: Sun, 7 Sep 2014 22:38:29 -0400 Subject: [App_rpt-users] debian? I want to do a central node for my repeaters.. I have 2 repeater on a site , another is already online and 2 other comming in soon.. I want them linked permanently but dont want to have any of those server as the central node cause none have the abndwith for it.. So I stumbled on a company that host vps server for real cheap.. But they are on debian. is it possible to install a node on a debian system? can someone point me in the right direction? Thanks Pierre VE2PFpresident VE2MRC for the curious.. here is the hosting company:https://www.beastnode.com/vps _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob at ah2s.org Mon Sep 8 05:23:11 2014 From: rob at ah2s.org (Rob Pectol - AH2S) Date: Mon, 08 Sep 2014 05:23:11 +0000 Subject: [App_rpt-users] beastnode (was debian) In-Reply-To: References: , Message-ID: Have the hosting provider load a 32-bit OS and you'll have more luck. ?However, even if you get through the install process, don't be surprised if you experience choppy and unpredictable audio. ?Many including myself have only had limited success running AllStar virtualized. ?Not saying it won't work, but don't be disappointed if it doesn't. ?Good luck... -- Rob - AH2S September 8 2014 1:32 PM, "pete M" wrote: Ok got a 3 month account with them.. got debian 5 installed.. of course the kernel is way too new to install asterisk with out problem here is the output for the version of the kernel.: # cat /proc/version Linux version 2.6.32-042stab093.4 (root at kbuild-rh6-x64) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Mon Aug 11 18:47:39 MSK 2014 So if I run phase2.sh from /etc/rc.d/ ( I did copy the script there and the acidrepo file at the same place, I have an error, can't compile zaptel. here is the last few lines from the compiler: make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** ? The existing menuselect.makeopts file did not specify ? that 'zttool' should not be included. ?However, either some ? dependencies for this module were not found or a ? conflict exists. ? Either run 'make menuselect' or remove the existing ? menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# Anyone have a simple answer to this? Do I need zaptel since I wont be connecting and radio directly to this server?? If I dont need it. How do I prevent the install script from compiling it?? Lots of question.. But I am not that used to such stuff ;-) Pierre Martel VE2PF ? ------------------------------------ From: petem001 at hotmail.com (mailto:petem001 at hotmail.com) To: app_rpt-users at ohnosec.org (mailto:app_rpt-users at ohnosec.org) Date: Sun, 7 Sep 2014 22:48:40 -0400 Subject: Re: [App_rpt-users] debian? ? Never mind.. Just found out they can have a debian 5 installed.. https://www.beastnode.com/portal/knowledgebase/110/Operating-System-Templates-or-ISOs.html (https://www.beastnode.com/portal/knowledgebase/110/Operating-System-Templates-or-ISOs.html) ? ------------------------------------ From: petem001 at hotmail.com (mailto:petem001 at hotmail.com) To: app_rpt-users at ohnosec.org (mailto:app_rpt-users at ohnosec.org) Date: Sun, 7 Sep 2014 22:38:29 -0400 Subject: [App_rpt-users] debian? ? I want to do a central node for my repeaters.. I have 2 repeater on a site , another is already online and 2 other comming in soon..? I want them linked permanently but dont want to have any of those server as the central node cause none have the abndwith for it.. So I stumbled on a company that host vps server for real cheap..? But they are on debian. ?is it possible to install a node on a debian system?? can someone point me in the right direction? Thanks Pierre VE2PF president VE2MRC for the curious.. here is the hosting company: https://www.beastnode.com/vps (https://www.beastnode.com/vps) _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org (mailto:App_rpt-users at ohnosec.org) http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users (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 (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 at ohnosec.org (mailto:App_rpt-users at ohnosec.org) http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users (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 (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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From petem001 at hotmail.com Mon Sep 8 10:36:25 2014 From: petem001 at hotmail.com (pete M) Date: Mon, 8 Sep 2014 06:36:25 -0400 Subject: [App_rpt-users] beastnode (was debian) In-Reply-To: References: , , , , Message-ID: Sorry, I wrote debian 5 cause I must have been a bit tired.. I have Centos 5 32 bit on the vps. Could I download an old version of the kernel, compile it on the machine and change the boot loader to run that older version? Or would I break something trying to comile from the lastest svn? does phase2.sh take the lastest svn from the allstar repo? for now the machine react very fast.. Ihope it will keep like that. Date: Mon, 8 Sep 2014 05:23:11 +0000 From: rob at ah2s.org To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] beastnode (was debian) Have the hosting provider load a 32-bit OS and you'll have more luck. However, even if you get through the install process, don't be surprised if you experience choppy and unpredictable audio. Many including myself have only had limited success running AllStar virtualized. Not saying it won't work, but don't be disappointed if it doesn't. Good luck... -- Rob - AH2S September 8 2014 1:32 PM, "pete M" wrote: Ok got a 3 month account with them.. got debian 5 installed.. of course the kernel is way too new to install asterisk with out problem here is the output for the version of the kernel.: # cat /proc/version Linux version 2.6.32-042stab093.4 (root at kbuild-rh6-x64) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Mon Aug 11 18:47:39 MSK 2014 So if I run phase2.sh from /etc/rc.d/ ( I did copy the script there and the acidrepo file at the same place, I have an error, can't compile zaptel. here is the last few lines from the compiler: make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# Anyone have a simple answer to this? Do I need zaptel since I wont be connecting and radio directly to this server? If I dont need it. How do I prevent the install script from compiling it? Lots of question.. But I am not that used to such stuff ;-) Pierre Martel VE2PF From: petem001 at hotmail.com To: app_rpt-users at ohnosec.org Date: Sun, 7 Sep 2014 22:48:40 -0400 Subject: Re: [App_rpt-users] debian? Never mind.. Just found out they can have a debian 5 installed.. https://www.beastnode.com/portal/knowledgebase/110/Operating-System-Templates-or-ISOs.html From: petem001 at hotmail.com To: app_rpt-users at ohnosec.org Date: Sun, 7 Sep 2014 22:38:29 -0400 Subject: [App_rpt-users] debian? I want to do a central node for my repeaters.. I have 2 repeater on a site , another is already online and 2 other comming in soon.. I want them linked permanently but dont want to have any of those server as the central node cause none have the abndwith for it.. So I stumbled on a company that host vps server for real cheap.. But they are on debian. is it possible to install a node on a debian system? can someone point me in the right direction? Thanks Pierre VE2PF president VE2MRC for the curious.. here is the hosting company: https://www.beastnode.com/vps _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ismaelisuani at gmail.com Mon Sep 8 22:39:28 2014 From: ismaelisuani at gmail.com (Ismael Isuani) Date: Mon, 8 Sep 2014 19:39:28 -0300 Subject: [App_rpt-users] Asterisk Segmentation Fault when decode mdc1200 on ilink nodes Message-ID: Hello to the group, I have 2 radios with different frequencies connected to the asterisk with 2 URI interfaces. I compiled asterisk with mdc 1200. MDC 1200 decoder works well, but if i link both nodes, such as: rpt cmd 1001 ilink 3 1002 now when mdc is decoded asterisk died with: Memory Allocation Failure - '-297310267' bytes in function ast_frdup at line 469 of frame.c I attached the backtrace file. app_rpt version 0.323 06/07/2014 asterisk 1.4.23-pre Is anyone to help me? Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- [New LWP 5475] [New LWP 5448] [New LWP 5476] [New LWP 5450] [New LWP 5449] [New LWP 5453] [New LWP 5454] [New LWP 5457] [New LWP 5455] [New LWP 5458] [New LWP 5456] [New LWP 5462] [New LWP 5473] [New LWP 5463] [New LWP 5467] [New LWP 5472] [New LWP 5471] [New LWP 5470] [New LWP 5469] [New LWP 5459] [New LWP 5468] [New LWP 5460] [New LWP 5466] [New LWP 5461] [New LWP 5477] [New LWP 5464] [New LWP 5465] [New LWP 5474] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `asterisk -vvvvvg -c'. Program terminated with signal 11, Segmentation fault. #0 0x00007fd178436080 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #0 0x00007fd178436080 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00000000004768b5 in ast_frdup (f=0x7fd15c46f500) at frame.c:486 out = 0x7fd0ea2ab080 len = 1911302085 srclen = 12 buf = 0x7fd0ea2ab080 frames = 0x10eba70 __PRETTY_FUNCTION__ = "ast_frdup" #2 0x00007fd171c629bc in rpt_qwrite (l=0x11008a0, f=0x7fd15c46f500) at app_rpt.c:4210 f1 = 0x7fd15c46f310 #3 0x00007fd171c63c65 in mdc1200_send (myrpt=0x7fd171ec2708, data=0x7fd15c4713f0 "I1234") at app_rpt.c:4657 l = 0x11008a0 wf = {frametype = AST_FRAME_TEXT, subclass = 0, datalen = 1911301896, samples = 0, mallocd = 0, mallocd_hdr_len = 0, offset = 0, src = 0x7fd171cad8d8 "mdc1200_send", data = 0x7fd15c46f430, delivery = {tv_sec = 140537656592981, tv_usec = 17111136}, frame_list = {next = 0x7fd15c471408}, flags = 1548162058, ts = 140537173054475, len = 140537173054472, seqno = 1548162058} str = "I 1002 I1234\000\177\000\000\000\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\377\377\377\377\001\000\000\000\001\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000@\227ix\321\177", '\000' , "\n\026\000\000 \000\000\000\060", '\000' , ".G\\\321\177", '\000' "\330, \062\066x\321\177\000\000\030\000\000\000\060\000\000\000\220\365F\\\321\177\000\000\320\364F\\\321\177\000\000\001", '\000' "\200, \365F\\\321\177\000\000_9\306q\321\177\000\000\344\354Q\000\000\000\000" #4 0x00007fd171c99ae8 in rpt (this=0x7fd171ec2708) at app_rpt.c:20596 op = 1 '\001' arg = 0 '\000' unitID = 4660 ustr = "I1234\000\000\000\000" ubuf = "\216\223\201iiyxfcw\206}r\177\224\222\200y\204\233\252\233{^Sf\204\225\213p]c\200\236\245\220p`l\212\241\236\204iam\177\222\237\242\234\216~obZWZalz\210\224\236\244\246\244\237\227\215\202wngb`adipw\177\207\216\223\227\230\230\226\222\215\207\201{vronnoqtx|\200\204\207\212\214\215\215\215\213\211\207\204\201}yvuuuvxz{}\177\201\203\204\206\206\207\207\207\206\205\203}|\206\213\207\203{somnrw}\203\210\214\216\216\215", '\000' sp = 0x7fd16c056918 n = 1 ismuted = 0 cs1 = {0x1054ed0, 0x10a4a30, 0x10d5390, 0x10d76e0, 0x10d9bc0, 0x10a3250, 0x10f7cc0, 0x11035d0, 0x10850a0, 0x0 } elap = 11 toexit = 0 f1 = 0x10ee760 cs = {0x10850a0, 0x1054ed0, 0x10a4a30, 0x10d5390, 0x10d76e0, 0x10d9bc0, 0x10a3250, 0x10f7cc0, 0x11035d0, 0x0 } n = 9 x = 0 f = 0x7fd16c056920 f2 = 0x10ec010 totx = 0 myrpt = 0x7fd171ec2708 tele = 0x7fd15c4729e6 "usb02" idtalkover = 0x0 c = 0 '\000' myfirst = 0 '\000' p = 0x7fd171cab606 "version 0.323 06/07/2014" ms = 9 i = 0 lasttx = 0 lastexttx = 1 lastpatchup = 0 val = 1 identqueued = 0 othertelemqueued = 0 tailmessagequeued = 0 ctqueued = 0 dtmfed = 0 lastmyrx = 1 localmsgqueued = 0 u = 0 fp = 0x0 mystat = {st_dev = 0, st_ino = 0, st_nlink = 140537645088352, st_mode = 3772, st_uid = 0, st_gid = 1548171712, __pad0 = 32721, st_rdev = 140537658740800, st_size = 3, st_blksize = 140537641886212, st_blocks = 0, st_atim = {tv_sec = 0, tv_nsec = 3792}, st_mtim = {tv_sec = 4404473, tv_nsec = 140537645088456}, st_ctim = {tv_sec = 7685248, tv_nsec = 140537173060640}, __unused = {4406013, 3824, 1017907249152}} who = 0x10850a0 ci = {chan = 32779, confno = 1021, confmode = 516} t = 1410188002 was = 0 l = 0x7fd171ec4550 m = 0x7fd171ec4550 telem = 0x7fd171ec6640 tmpstr = "Radio\000usb02", '\000' lstr = "L ", '\000' lat = '\000' lon = '\000' elev = '\000' __PRETTY_FUNCTION__ = "rpt" #5 0x00000000004e21e8 in dummy_start (data=0x10511d0) at utils.c:925 __cancel_buf = {__cancel_jmp_buf = {{__cancel_jmp_buf = {0, -5520470306634710247, 140537657933168, 140537173064128, 140537658740800, 3, -5520470306666167527, 5530949839522775833}, __mask_was_saved = 0}}, __pad = {0x7fd15c472f80, 0x0, 0x0, 0x0}} __cancel_routine = 0x42b275 __cancel_arg = 0x7fd15c473700 __not_first_call = 0 ret = 0x0 a = {start_routine = 0x7fd171c92028 , data = 0x7fd171ec2708, name = 0x10534a0 "rpt", ' ' , "started at [21998] app_rpt.c rpt_master()"} lock_info = 0x109ec10 mutex_attr = {__size = "\001\000\000", __align = 1} __PRETTY_FUNCTION__ = "dummy_start" #6 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 No symbol table info available. #7 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #8 0x0000000000000000 in ?? () No symbol table info available. Thread 28 (Thread 0x7fd15c4af700 (LWP 5474)): #0 0x00007fd1783ea963 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00000000004a7872 in poll (pArray=0x7fd15c4ab1e0, n_fds=17, timeout=20) at poll.c:296 #2 0x000000000044b49f in ast_waitfor_nandfds (c=0x7fd15c4ac010, n=9, fds=0x0, nfds=0, exception=0x0, outfd=0x0, ms=0x7fd15c4aebcc) at channel.c:1741 #3 0x000000000044b8d3 in ast_waitfor_n (c=0x7fd15c4ac010, n=9, ms=0x7fd15c4aebcc) at channel.c:1803 #4 0x00007fd171c97605 in rpt (this=0x7fd171ebbe40) at app_rpt.c:20030 #5 0x00000000004e21e8 in dummy_start (data=0x1055b50) at utils.c:925 #6 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x0000000000000000 in ?? () Thread 27 (Thread 0x7fd170041700 (LWP 5465)): #0 0x00007fd178d6c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd1652ad087 in __ast_cond_wait (filename=0x7fd1652ed82b "chan_iax2.c", lineno=10058, func=0x7fd1652f3980 "iax2_process_thread", cond_name=0x7fd1652edba3 "&thread->cond", mutex_name=0x7fd1652edb95 "&thread->lock", cond=0x7fd16d6b7778, t=0x7fd16d6b7600) at /usr/src/trunk/asterisk/include/asterisk/lock.h:605 #2 0x00007fd1652da4ab in iax2_process_thread (data=0x7fd16d6b6540) at chan_iax2.c:10058 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6abb10) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 26 (Thread 0x7fd17007d700 (LWP 5464)): #0 0x00007fd178d6c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd1652ad087 in __ast_cond_wait (filename=0x7fd1652ed82b "chan_iax2.c", lineno=10058, func=0x7fd1652f3980 "iax2_process_thread", cond_name=0x7fd1652edba3 "&thread->cond", mutex_name=0x7fd1652edb95 "&thread->lock", cond=0x7fd16d6ab828, t=0x7fd16d6ab6b0) at /usr/src/trunk/asterisk/include/asterisk/lock.h:605 #2 0x00007fd1652da4ab in iax2_process_thread (data=0x7fd16d6aa5f0) at chan_iax2.c:10058 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6a39b0) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 25 (Thread 0x7fd15c3fb700 (LWP 5477)): #0 0x00007fd1783ea963 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fd169265d79 in ast_select (nfds=51, rfds=0x7fd15c3fabd0, wfds=0x0, efds=0x0, tvp=0x7fd15c3fac60) at /usr/src/trunk/asterisk/include/asterisk/channel.h:1325 #2 0x00007fd169268d2d in hidthread (arg=0x7fd16c053610) at chan_usbradio.c:1758 #3 0x00000000004e21e8 in dummy_start (data=0x104f8c0) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 24 (Thread 0x7fd170131700 (LWP 5461)): #0 0x00007fd178d6c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd1652ad087 in __ast_cond_wait (filename=0x7fd1652ed82b "chan_iax2.c", lineno=10058, func=0x7fd1652f3980 "iax2_process_thread", cond_name=0x7fd1652edba3 "&thread->cond", mutex_name=0x7fd1652edb95 "&thread->lock", cond=0x7fd16d6a78c8, t=0x7fd16d6a7750) at /usr/src/trunk/asterisk/include/asterisk/lock.h:605 #2 0x00007fd1652da4ab in iax2_process_thread (data=0x7fd16d6a6690) at chan_iax2.c:10058 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6a39b0) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 23 (Thread 0x7fd1652a1700 (LWP 5466)): #0 0x00007fd178d6c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd1652ad087 in __ast_cond_wait (filename=0x7fd1652ed82b "chan_iax2.c", lineno=10058, func=0x7fd1652f3980 "iax2_process_thread", cond_name=0x7fd1652edba3 "&thread->cond", mutex_name=0x7fd1652edb95 "&thread->lock", cond=0x7fd16d6b8a98, t=0x7fd16d6b8920) at /usr/src/trunk/asterisk/include/asterisk/lock.h:605 #2 0x00007fd1652da4ab in iax2_process_thread (data=0x7fd16d6b7860) at chan_iax2.c:10058 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6a39b0) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 22 (Thread 0x7fd17016d700 (LWP 5460)): #0 0x00007fd178d6c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd1652ad087 in __ast_cond_wait (filename=0x7fd1652ed82b "chan_iax2.c", lineno=10058, func=0x7fd1652f3980 "iax2_process_thread", cond_name=0x7fd1652edba3 "&thread->cond", mutex_name=0x7fd1652edb95 "&thread->lock", cond=0x7fd16d6a63a8, t=0x7fd16d6a6230) at /usr/src/trunk/asterisk/include/asterisk/lock.h:605 #2 0x00007fd1652da4ab in iax2_process_thread (data=0x7fd16d6a5170) at chan_iax2.c:10058 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6a39b0) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 21 (Thread 0x7fd165229700 (LWP 5468)): #0 0x00007fd178d6c64b in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd1652ad640 in __ast_cond_timedwait (filename=0x7fd1652ed82b "chan_iax2.c", lineno=10519, func=0x7fd1652f3894 "sched_thread", cond_name=0x7fd1652edbfe "&sched_cond", mutex_name=0x7fd1652edbf2 "&sched_lock", cond=0x7fd1654fe2e0, t=0x7fd1654fa6a0, abstime=0x7fd165228dc0) at /usr/src/trunk/asterisk/include/asterisk/lock.h:676 #2 0x00007fd1652dc73b in sched_thread (ignore=0x0) at chan_iax2.c:10519 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6a39b0) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 20 (Thread 0x7fd177432700 (LWP 5459)): #0 0x00007fd178d6c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd1652ad087 in __ast_cond_wait (filename=0x7fd1652ed82b "chan_iax2.c", lineno=10058, func=0x7fd1652f3980 "iax2_process_thread", cond_name=0x7fd1652edba3 "&thread->cond", mutex_name=0x7fd1652edb95 "&thread->lock", cond=0x7fd16d6a4e88, t=0x7fd16d6a4d10) at /usr/src/trunk/asterisk/include/asterisk/lock.h:605 #2 0x00007fd1652da4ab in iax2_process_thread (data=0x7fd16d6a3c50) at chan_iax2.c:10058 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6a39b0) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 19 (Thread 0x7fd1651ed700 (LWP 5469)): #0 0x00007fd1783ea963 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00000000004a7872 in poll (pArray=0x7fd16d69eb50, n_fds=1, timeout=-1) at poll.c:296 #2 0x0000000000480aff in ast_io_wait (ioc=0x7fd16d69eab0, howlong=-1) at io.c:266 #3 0x00007fd1652dcaf7 in network_thread (ignore=0x0) at chan_iax2.c:10593 #4 0x00000000004e21e8 in dummy_start (data=0x7fd16d6abb10) at utils.c:925 #5 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x0000000000000000 in ?? () Thread 18 (Thread 0x7fd163784700 (LWP 5470)): #0 0x00007fd1783c133d in nanosleep () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fd1783c11b0 in sleep () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007fd1637881df in scan_thread (unused=0x0) at pbx_spool.c:451 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6c2d70) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 17 (Thread 0x7fd1614bb700 (LWP 5471)): #0 0x00007fd178d6c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd1614c159f in __ast_cond_wait (filename=0x7fd1614d2474 "app_queue.c", lineno=699, func=0x7fd1614d73b0 "device_state_thread", cond_name=0x7fd1614d3eae "&device_state.cond", mutex_name=0x7fd1614d3e9b "&device_state.lock", cond=0x7fd1616d9308, t=0x7fd1616d9190) at /usr/src/trunk/asterisk/include/asterisk/lock.h:605 #2 0x00007fd1614c2354 in device_state_thread (data=0x0) at app_queue.c:699 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6cfcb0) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 16 (Thread 0x7fd15f5cf700 (LWP 5472)): #0 0x00007fd1783ea963 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00000000004a7872 in poll (pArray=0x7fd16d6d9d50, n_fds=1, timeout=1000) at poll.c:296 #2 0x0000000000480aff in ast_io_wait (ioc=0x7fd16d6d9cb0, howlong=1000) at io.c:266 #3 0x00007fd15f6206f7 in do_monitor (data=0x0) at chan_sip.c:16184 #4 0x00000000004e21e8 in dummy_start (data=0x7fd16d6de1d0) at utils.c:925 #5 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x0000000000000000 in ?? () Thread 15 (Thread 0x7fd165265700 (LWP 5467)): #0 0x00007fd178d6c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd1652ad087 in __ast_cond_wait (filename=0x7fd1652ed82b "chan_iax2.c", lineno=10058, func=0x7fd1652f3980 "iax2_process_thread", cond_name=0x7fd1652edba3 "&thread->cond", mutex_name=0x7fd1652edb95 "&thread->lock", cond=0x7fd16d6b9fb8, t=0x7fd16d6b9e40) at /usr/src/trunk/asterisk/include/asterisk/lock.h:605 #2 0x00007fd1652da4ab in iax2_process_thread (data=0x7fd16d6b8d80) at chan_iax2.c:10058 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6abb10) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 14 (Thread 0x7fd1700b9700 (LWP 5463)): #0 0x00007fd178d6c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd1652ad087 in __ast_cond_wait (filename=0x7fd1652ed82b "chan_iax2.c", lineno=10058, func=0x7fd1652f3980 "iax2_process_thread", cond_name=0x7fd1652edba3 "&thread->cond", mutex_name=0x7fd1652edb95 "&thread->lock", cond=0x7fd16d6aa308, t=0x7fd16d6aa190) at /usr/src/trunk/asterisk/include/asterisk/lock.h:605 #2 0x00007fd1652da4ab in iax2_process_thread (data=0x7fd16d6a90d0) at chan_iax2.c:10058 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6a39b0) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 13 (Thread 0x7fd15c4eb700 (LWP 5473)): #0 0x00007fd1783ea963 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00000000004a7872 in poll (pArray=0x7fd15c4eadf0, n_fds=1, timeout=-1) at poll.c:296 #2 0x0000000000431881 in monitor_sig_flags (unused=0x0) at asterisk.c:2613 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d703a00) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 12 (Thread 0x7fd1700f5700 (LWP 5462)): #0 0x00007fd178d6c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd1652ad087 in __ast_cond_wait (filename=0x7fd1652ed82b "chan_iax2.c", lineno=10058, func=0x7fd1652f3980 "iax2_process_thread", cond_name=0x7fd1652edba3 "&thread->cond", mutex_name=0x7fd1652edb95 "&thread->lock", cond=0x7fd16d6a8de8, t=0x7fd16d6a8c70) at /usr/src/trunk/asterisk/include/asterisk/lock.h:605 #2 0x00007fd1652da4ab in iax2_process_thread (data=0x7fd16d6a7bb0) at chan_iax2.c:10058 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6a39b0) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 11 (Thread 0x7fd179264700 (LWP 5456)): #0 0x00007fd1783ea963 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fd169265d79 in ast_select (nfds=11, rfds=0x7fd179262cb0, wfds=0x7fd179262d30, efds=0x0, tvp=0x0) at /usr/src/trunk/asterisk/include/asterisk/channel.h:1325 #2 0x00007fd16926a6d1 in sound_thread (arg=0x7fd16c033110) at chan_usbradio.c:2226 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16c053370) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 10 (Thread 0x7fd1791ec700 (LWP 5458)): #0 0x00007fd178d6c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fd1652ad087 in __ast_cond_wait (filename=0x7fd1652ed82b "chan_iax2.c", lineno=10058, func=0x7fd1652f3980 "iax2_process_thread", cond_name=0x7fd1652edba3 "&thread->cond", mutex_name=0x7fd1652edb95 "&thread->lock", cond=0x7fd16d6a38c8, t=0x7fd16d6a3750) at /usr/src/trunk/asterisk/include/asterisk/lock.h:605 #2 0x00007fd1652da4ab in iax2_process_thread (data=0x7fd16d6a2690) at chan_iax2.c:10058 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16d6a39b0) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 9 (Thread 0x7fd1792a0700 (LWP 5455)): #0 0x00007fd1783ea963 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00000000004a7872 in poll (pArray=0x104cd20, n_fds=0, timeout=1000) at poll.c:296 #2 0x00007fd16b9e5736 in do_monitor (data=0x0) at chan_dahdi.c:7007 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16c015a60) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 8 (Thread 0x7fd179228700 (LWP 5457)): #0 0x00007fd1783ea963 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fd169265d79 in ast_select (nfds=13, rfds=0x7fd179226cb0, wfds=0x7fd179226d30, efds=0x0, tvp=0x0) at /usr/src/trunk/asterisk/include/asterisk/channel.h:1325 #2 0x00007fd16926a6d1 in sound_thread (arg=0x7fd16c053610) at chan_usbradio.c:2226 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16c075100) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 7 (Thread 0x7fd1792dc700 (LWP 5454)): #0 0x00007fd1783c133d in nanosleep () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fd1783eb084 in usleep () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007fd171c9fb3e in rpt_master (ignore=0x0) at app_rpt.c:22101 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16c008280) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 6 (Thread 0x7fd179318700 (LWP 5453)): #0 0x00007fd1783ea963 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fd173bc1a3d in ast_select (nfds=0, rfds=0x7fd179317cc0, wfds=0x0, efds=0x7fd179317c40, tvp=0x0) at /usr/src/trunk/asterisk/include/asterisk/channel.h:1325 #2 0x00007fd173bc89d9 in do_parking_thread (ignore=0x0) at res_features.c:2032 #3 0x00000000004e21e8 in dummy_start (data=0x108f590) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 5 (Thread 0x7fd179390700 (LWP 5449)): #0 0x00007fd1783ea963 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00000000004a7872 in poll (pArray=0x7fd17938fd70, n_fds=1, timeout=-1) at poll.c:296 #2 0x000000000042d0e8 in listener (unused=0x0) at asterisk.c:1000 #3 0x00000000004e21e8 in dummy_start (data=0x1030070) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 4 (Thread 0x7fd179354700 (LWP 5450)): #0 0x00007fd178d6c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x0000000000464661 in __ast_cond_wait (filename=0x518794 "devicestate.c", lineno=352, func=0x518bd0 "do_devstate_changes", cond_name=0x518b28 "&change_pending", mutex_name=0x518b38 "&state_changes.lock", cond=0x7698a0, t=0x759b10) at /usr/src/trunk/asterisk/include/asterisk/lock.h:605 #2 0x000000000046551b in do_devstate_changes (data=0x0) at devicestate.c:352 #3 0x00000000004e21e8 in dummy_start (data=0x10380a0) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 3 (Thread 0x7fd15c437700 (LWP 5476)): #0 0x00007fd1783ea963 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fd169265d79 in ast_select (nfds=54, rfds=0x7fd15c436bd0, wfds=0x0, efds=0x0, tvp=0x7fd15c436c60) at /usr/src/trunk/asterisk/include/asterisk/channel.h:1325 #2 0x00007fd169268d2d in hidthread (arg=0x7fd16c033110) at chan_usbradio.c:1758 #3 0x00000000004e21e8 in dummy_start (data=0x7fd16c051e90) at utils.c:925 #4 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 2 (Thread 0x7fd179392700 (LWP 5448)): #0 0x00007fd178d6f18d in read () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00000000004e9a1a in read_char (el=0x1026b20, cp=0x7fff61150c4f "") at read.c:296 #2 0x00000000004ecc95 in el_getc (el=el at entry=0x1026b20, cp=cp at entry=0x7fff61150c4f "") at read.c:347 #3 0x00000000004edc0a in read_getcmd (ch=, cmdnum=, el=) at read.c:243 #4 el_gets (el=0x1026b20, nread=0x7fff6115107c) at read.c:443 #5 0x0000000000433325 in main (argc=3, argv=0x7fff61151378) at asterisk.c:3159 #6 0x00007fd178333eed in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x0000000000416669 in ?? () #8 0x00007fff61151368 in ?? () #9 0x000000000000001c in ?? () #10 0x0000000000000003 in ?? () #11 0x00007fff61152e05 in ?? () #12 0x00007fff61152e0e in ?? () #13 0x00007fff61152e16 in ?? () #14 0x0000000000000000 in ?? () Thread 1 (Thread 0x7fd15c473700 (LWP 5475)): #0 0x00007fd178436080 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00000000004768b5 in ast_frdup (f=0x7fd15c46f500) at frame.c:486 #2 0x00007fd171c629bc in rpt_qwrite (l=0x11008a0, f=0x7fd15c46f500) at app_rpt.c:4210 #3 0x00007fd171c63c65 in mdc1200_send (myrpt=0x7fd171ec2708, data=0x7fd15c4713f0 "I1234") at app_rpt.c:4657 #4 0x00007fd171c99ae8 in rpt (this=0x7fd171ec2708) at app_rpt.c:20596 #5 0x00000000004e21e8 in dummy_start (data=0x10511d0) at utils.c:925 #6 0x00007fd178d67b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x00007fd1783f0e6d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x0000000000000000 in ?? () From petem001 at hotmail.com Tue Sep 9 14:00:28 2014 From: petem001 at hotmail.com (pete M) Date: Tue, 9 Sep 2014 10:00:28 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Message-ID: Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org... Getting files.tar.gz from http://dl.allstarlink.org... ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? -------------- next part -------------- An HTML attachment was scrubbed... URL: From kk6ecm at gmail.com Tue Sep 9 14:55:06 2014 From: kk6ecm at gmail.com (Bob) Date: Tue, 9 Sep 2014 07:55:06 -0700 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: Message-ID: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> I've done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS website No features, tools only, no desktop (competes with Asterisk) Set ssh /etc/ssh/sshd_config Run "setup" at comand line and disable firewall vi /etc/rc.d/acidrepo http://dl.allstarlink.org Execute portion of ks.cfg, each line at a time cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig cat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.sh Auto reboot after phase1.sh executed phase2.sh runs automatically to completion Bob kk6ecm _____ From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org... Getting files.tar.gz from http://dl.allstarlink.org... ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? -------------- next part -------------- An HTML attachment was scrubbed... URL: From petem001 at hotmail.com Tue Sep 9 15:27:56 2014 From: petem001 at hotmail.com (pete M) Date: Tue, 9 Sep 2014 11:27:56 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> Message-ID: Ok will try that.. thanks! From: Bob Sent: Tuesday, September 09, 2014 10:55 AM To: 'APP RPT' Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I?ve done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS website No features, tools only, no desktop (competes with Asterisk) Set ssh /etc/ssh/sshd_config Run "setup" at comand line and disable firewall vi /etc/rc.d/acidrepo http://dl.allstarlink.org Execute portion of ks.cfg, each line at a time cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig cat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.sh Auto reboot after phase1.sh executed phase2.sh runs automatically to completion Bob kk6ecm -------------------------------------------------------------------------------- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org../. Getting files.tar.gz from http://dl.allstarlink.org../. ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? -------------------------------------------------------------------------------- _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From petem001 at hotmail.com Tue Sep 9 17:36:19 2014 From: petem001 at hotmail.com (pete M) Date: Tue, 9 Sep 2014 13:36:19 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> Message-ID: Hi! Ok did the whole thing.. even did this on a fresh install. (loaded a vanilla image) But I had to edit phase1.sh to not look at the version of centos. (even if its centos 5) and not mess with my network programming. It all went well, updated a lot of stuff.. I also prevented the auto reboot from the phase1 script cause I am doing all this from Putty.. So renames phase2.sh so that it wont start by itself. rebooted. went back to phase2.sh. and renamed it properly and started it.. It start to compile.. and same problem with zttool (part of zaptel) Anyone can please help me pass that thing? Please pretty please?? Pierre VE2PF -------------- next part -------------- An HTML attachment was scrubbed... URL: From kk6ecm at gmail.com Tue Sep 9 17:40:02 2014 From: kk6ecm at gmail.com (kk6ecm) Date: Tue, 9 Sep 2014 10:40:02 -0700 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> Message-ID: <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com> I use this when ACID will not load, usually due to issues with BIOS and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. Thanks, Bob kk6ecm Sent from iPad > On Sep 9, 2014, at 8:27 AM, pete M wrote: > > Ok will try that.. > > thanks! > > > From: Bob > Sent: Tuesday, September 09, 2014 10:55 AM > To: 'APP RPT' > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I?ve done this several times without issue. Here are the steps I used. > > Load CentOS 5.10 downloaded from CentOS website > No features, tools only, no desktop (competes with Asterisk) > Set ssh /etc/ssh/sshd_config > Run "setup" at comand line and disable firewall > vi /etc/rc.d/acidrepo > http://dl.allstarlink.org > Execute portion of ks.cfg, each line at a time > cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig > cat <>/etc/rc.d/rc.local > > cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh > > chmod 755 /etc/rc.d/phase1.sh > > /etc/rc.d/phase1.sh > Auto reboot after phase1.sh executed > phase2.sh runs automatically to completion > > Bob > kk6ecm > > From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M > Sent: Tuesday, September 09, 2014 7:00 AM > To: APP RPT > Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. > > I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. > > here is the out put from the script > > sh phase2.sh > ****** Phase 2 post install ****** > Getting asterisk install script from http://dl.allstarlink.org../. > Getting files.tar.gz from http://dl.allstarlink.org../. > ****** Asterisk Installation ****** > /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found > Unpacking files.tar.gz... > Compiling Zaptel... > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking how to run the C preprocessor... gcc -E > checking for a BSD-compatible install... /usr/bin/install -c > checking whether ln -s works... yes > checking for GNU make... make > checking for grep... /bin/grep > checking for sh... /bin/sh > checking for ln... /bin/ln > checking for wget... /usr/bin/wget > checking for grep that handles long lines and -e... (cached) /bin/grep > checking for egrep... /bin/grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for initscr in -lcurses... no > checking for initscr in -lncurses... no > checking for newtBell in -lnewt... no > checking for usb_init in -lusb... no > configure: creating ./config.status > config.status: creating build_tools/menuselect-deps > config.status: creating makeopts > config.status: creating build_tools/make_firmware_object > configure: *** Zaptel build successfully configured *** > make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking for GNU make... make > checking for asprintf... yes > checking for getloadavg... yes > checking for setenv... yes > checking for strcasestr... yes > checking for strndup... yes > checking for strnlen... yes > checking for strsep... yes > checking for strtoq... yes > checking for unsetenv... yes > checking for vasprintf... yes > checking how to run the C preprocessor... gcc -E > checking for egrep... grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for initscr in -lcurses... no > checking for initscr in -lncurses... no > checking for pkg-config... No > configure: creating ./config.status > config.status: creating makeopts > config.status: creating autoconfig.h > configure: configuring in mxml > configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking for g++... no > checking for c++... no > checking for gpp... no > checking for aCC... no > checking for CC... no > checking for cxx... no > checking for cc++... no > checking for cl... no > checking for FCC... no > checking for KCC... no > checking for RCC... no > checking for xlC_r... no > checking for xlC... no > checking whether we are using the GNU C++ compiler... no > checking whether g++ accepts -g... no > checking for a BSD-compatible install... /usr/bin/install -c > checking for ranlib... ranlib > checking for ar... /usr/bin/ar > checking for cp... /bin/cp > checking for ln... /bin/ln > checking for mkdir... /bin/mkdir > checking for nroff... /usr/bin/nroff > checking for rm... /bin/rm > checking for strdup... yes > checking for vsnprintf... yes > configure: creating ./config.status > config.status: creating Makefile > config.status: creating mxml.list > config.status: creating mxml.pc > config.status: creating config.h > configure: Menuselect build configuration successfully completed > make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c > gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c > gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c > make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' > gcc -O -Wall -c mxml-attr.c > gcc -O -Wall -c mxml-entity.c > gcc -O -Wall -c mxml-file.c > gcc -O -Wall -c mxml-index.c > gcc -O -Wall -c mxml-node.c > gcc -O -Wall -c mxml-search.c > gcc -O -Wall -c mxml-set.c > gcc -O -Wall -c mxml-private.c > gcc -O -Wall -c mxml-string.c > /bin/rm -f libmxml.a > /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o > a - mxml-attr.o > a - mxml-entity.o > a - mxml-file.o > a - mxml-index.o > a - mxml-node.o > a - mxml-search.o > a - mxml-set.o > a - mxml-private.o > a - mxml-string.o > ranlib libmxml.a > make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' > gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a > make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > Generating input for menuselect ... > > *********************************************************** > The existing menuselect.makeopts file did not specify > that 'zttool' should not be included. However, either some > dependencies for this module were not found or a > conflict exists. > > Either run 'make menuselect' or remove the existing > menuselect.makeopts file to resolve this issue. > *********************************************************** > > make: *** [menuselect.makeopts] Error 255 > Failure: Unable to compile Zaptel 2 > Fatal error: Unable to install Asterisk! > [root at node rc.d]# > > I dont know where to go from there.. > > Anyone care to help a bit? > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kk6ecm at gmail.com Tue Sep 9 19:25:04 2014 From: kk6ecm at gmail.com (kk6ecm) Date: Tue, 9 Sep 2014 12:25:04 -0700 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com> Message-ID: Understand. I did not get this picture before. Perhaps there is someone on the list that understands the compiler compatibility requirements. This is beyond my capability. Thanks, Bob kk6ecm Sent from iPad > On Sep 9, 2014, at 11:13 AM, pete M wrote: > > I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. > > I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. > > > > From: kk6ecm > Sent: Tuesday, September 09, 2014 1:40 PM > To: APP RPT > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I use this when ACID will not load, usually due to issues with BIOS and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. > > Thanks, > Bob > kk6ecm > > Sent from iPad > > >> On Sep 9, 2014, at 8:27 AM, pete M wrote: >> >> Ok will try that.. >> >> thanks! >> >> >> From: Bob >> Sent: Tuesday, September 09, 2014 10:55 AM >> To: 'APP RPT' >> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> >> I?ve done this several times without issue. Here are the steps I used. >> >> >> >> Load CentOS 5.10 downloaded from CentOS website >> >> No features, tools only, no desktop (competes with Asterisk) >> >> Set ssh /etc/ssh/sshd_config >> >> Run "setup" at comand line and disable firewall >> >> vi /etc/rc.d/acidrepo >> >> http://dl.allstarlink.org >> >> Execute portion of ks.cfg, each line at a time >> >> cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig >> >> cat <>/etc/rc.d/rc.local >> >> >> >> cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh >> >> >> >> chmod 755 /etc/rc.d/phase1.sh >> >> >> >> /etc/rc.d/phase1.sh >> >> Auto reboot after phase1.sh executed >> >> phase2.sh runs automatically to completion >> >> >> >> Bob >> >> kk6ecm >> >> >> >> From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M >> Sent: Tuesday, September 09, 2014 7:00 AM >> To: APP RPT >> Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> >> >> >> Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. >> >> >> >> I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. >> >> >> >> here is the out put from the script >> >> >> >> sh phase2.sh >> >> ****** Phase 2 post install ****** >> >> Getting asterisk install script from http://dl.allstarlink.org../. >> >> Getting files.tar.gz from http://dl.allstarlink.org../. >> >> ****** Asterisk Installation ****** >> >> /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found >> >> Unpacking files.tar.gz... >> >> Compiling Zaptel... >> >> checking for gcc... gcc >> >> checking for C compiler default output file name... a.out >> >> checking whether the C compiler works... yes >> >> checking whether we are cross compiling... no >> >> checking for suffix of executables... >> >> checking for suffix of object files... o >> >> checking whether we are using the GNU C compiler... yes >> >> checking whether gcc accepts -g... yes >> >> checking for gcc option to accept ISO C89... none needed >> >> checking how to run the C preprocessor... gcc -E >> >> checking for a BSD-compatible install... /usr/bin/install -c >> >> checking whether ln -s works... yes >> >> checking for GNU make... make >> >> checking for grep... /bin/grep >> >> checking for sh... /bin/sh >> >> checking for ln... /bin/ln >> >> checking for wget... /usr/bin/wget >> >> checking for grep that handles long lines and -e... (cached) /bin/grep >> >> checking for egrep... /bin/grep -E >> >> checking for ANSI C header files... yes >> >> checking for sys/types.h... yes >> >> checking for sys/stat.h... yes >> >> checking for stdlib.h... yes >> >> checking for string.h... yes >> >> checking for memory.h... yes >> >> checking for strings.h... yes >> >> checking for inttypes.h... yes >> >> checking for stdint.h... yes >> >> checking for unistd.h... yes >> >> checking for initscr in -lcurses... no >> >> checking for initscr in -lncurses... no >> >> checking for newtBell in -lnewt... no >> >> checking for usb_init in -lusb... no >> >> configure: creating ./config.status >> >> config.status: creating build_tools/menuselect-deps >> >> config.status: creating makeopts >> >> config.status: creating build_tools/make_firmware_object >> >> configure: *** Zaptel build successfully configured *** >> >> make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' >> >> checking build system type... i686-pc-linux-gnu >> >> checking host system type... i686-pc-linux-gnu >> >> checking for gcc... gcc >> >> checking for C compiler default output file name... a.out >> >> checking whether the C compiler works... yes >> >> checking whether we are cross compiling... no >> >> checking for suffix of executables... >> >> checking for suffix of object files... o >> >> checking whether we are using the GNU C compiler... yes >> >> checking whether gcc accepts -g... yes >> >> checking for gcc option to accept ANSI C... none needed >> >> checking for GNU make... make >> >> checking for asprintf... yes >> >> checking for getloadavg... yes >> >> checking for setenv... yes >> >> checking for strcasestr... yes >> >> checking for strndup... yes >> >> checking for strnlen... yes >> >> checking for strsep... yes >> >> checking for strtoq... yes >> >> checking for unsetenv... yes >> >> checking for vasprintf... yes >> >> checking how to run the C preprocessor... gcc -E >> >> checking for egrep... grep -E >> >> checking for ANSI C header files... yes >> >> checking for sys/types.h... yes >> >> checking for sys/stat.h... yes >> >> checking for stdlib.h... yes >> >> checking for string.h... yes >> >> checking for memory.h... yes >> >> checking for strings.h... yes >> >> checking for inttypes.h... yes >> >> checking for stdint.h... yes >> >> checking for unistd.h... yes >> >> checking for initscr in -lcurses... no >> >> checking for initscr in -lncurses... no >> >> checking for pkg-config... No >> >> configure: creating ./config.status >> >> config.status: creating makeopts >> >> config.status: creating autoconfig.h >> >> configure: configuring in mxml >> >> configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. >> >> checking for gcc... gcc >> >> checking for C compiler default output file name... a.out >> >> checking whether the C compiler works... yes >> >> checking whether we are cross compiling... no >> >> checking for suffix of executables... >> >> checking for suffix of object files... o >> >> checking whether we are using the GNU C compiler... yes >> >> checking whether gcc accepts -g... yes >> >> checking for gcc option to accept ANSI C... none needed >> >> checking for g++... no >> >> checking for c++... no >> >> checking for gpp... no >> >> checking for aCC... no >> >> checking for CC... no >> >> checking for cxx... no >> >> checking for cc++... no >> >> checking for cl... no >> >> checking for FCC... no >> >> checking for KCC... no >> >> checking for RCC... no >> >> checking for xlC_r... no >> >> checking for xlC... no >> >> checking whether we are using the GNU C++ compiler... no >> >> checking whether g++ accepts -g... no >> >> checking for a BSD-compatible install... /usr/bin/install -c >> >> checking for ranlib... ranlib >> >> checking for ar... /usr/bin/ar >> >> checking for cp... /bin/cp >> >> checking for ln... /bin/ln >> >> checking for mkdir... /bin/mkdir >> >> checking for nroff... /usr/bin/nroff >> >> checking for rm... /bin/rm >> >> checking for strdup... yes >> >> checking for vsnprintf... yes >> >> configure: creating ./config.status >> >> config.status: creating Makefile >> >> config.status: creating mxml.list >> >> config.status: creating mxml.pc >> >> config.status: creating config.h >> >> configure: Menuselect build configuration successfully completed >> >> make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' >> >> make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' >> >> make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' >> >> gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c >> >> gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c >> >> gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c >> >> make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' >> >> gcc -O -Wall -c mxml-attr.c >> >> gcc -O -Wall -c mxml-entity.c >> >> gcc -O -Wall -c mxml-file.c >> >> gcc -O -Wall -c mxml-index.c >> >> gcc -O -Wall -c mxml-node.c >> >> gcc -O -Wall -c mxml-search.c >> >> gcc -O -Wall -c mxml-set.c >> >> gcc -O -Wall -c mxml-private.c >> >> gcc -O -Wall -c mxml-string.c >> >> /bin/rm -f libmxml.a >> >> /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o >> >> a - mxml-attr.o >> >> a - mxml-entity.o >> >> a - mxml-file.o >> >> a - mxml-index.o >> >> a - mxml-node.o >> >> a - mxml-search.o >> >> a - mxml-set.o >> >> a - mxml-private.o >> >> a - mxml-string.o >> >> ranlib libmxml.a >> >> make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' >> >> gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a >> >> make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' >> >> make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' >> >> Generating input for menuselect ... >> >> >> >> *********************************************************** >> >> The existing menuselect.makeopts file did not specify >> >> that 'zttool' should not be included. However, either some >> >> dependencies for this module were not found or a >> >> conflict exists. >> >> >> >> Either run 'make menuselect' or remove the existing >> >> menuselect.makeopts file to resolve this issue. >> >> *********************************************************** >> >> >> >> make: *** [menuselect.makeopts] Error 255 >> >> Failure: Unable to compile Zaptel 2 >> >> Fatal error: Unable to install Asterisk! >> >> [root at node rc.d]# >> >> >> >> I dont know where to go from there.. >> >> >> >> Anyone care to help a bit? >> >> >> >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hammin75 at gmail.com Wed Sep 10 01:36:24 2014 From: hammin75 at gmail.com (Bradley Haney) Date: Tue, 9 Sep 2014 20:36:24 -0500 Subject: [App_rpt-users] XIPAR Dialing an extension from Repeater to IP phone failing.... Message-ID: Hello all.. I am getting this error when i am trying to dial from the radio to a local PBX extension on Xipar.. Anyone know where to start? localhost*CLI> [Sep 9 20:29:54] WARNING[31176]: app_dial.c:1310 dial_exec_full: Unable to create channel of type 'SIP' (cause 20 - Unknown) [Sep 9 20:29:54] WARNING[31176]: app_dial.c:1310 dial_exec_full: Unable to create channel of type 'SIP' (cause 20 - Unknown) localhost*CLI> [Sep 9 20:29:59] WARNING[31177]: func_db.c:180 function_db_delete: DB_DELETE requires an argument, DB_DELETE(/) [Sep 9 20:29:59] WARNING[31177]: func_db.c:180 function_db_delete: DB_DELETE requires an argument, DB_DELETE(/) Thanks.. Bradley From mike at midnighteng.com Wed Sep 10 02:40:40 2014 From: mike at midnighteng.com (mike at midnighteng.com) Date: Tue, 09 Sep 2014 19:40:40 -0700 Subject: [App_rpt-users] =?utf-8?q?XIPAR_Dialing_an_extension_from_Repeate?= =?utf-8?q?r_to_IP_phone_failing=2E=2E=2E=2E?= Message-ID: <20140909194040.71befee5dbd13c5325dd1a521b4e73ee.7864952445.wbe@email06.secureserver.net> An HTML attachment was scrubbed... URL: From petem001 at hotmail.com Wed Sep 10 15:30:01 2014 From: petem001 at hotmail.com (pete M) Date: Wed, 10 Sep 2014 11:30:01 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP><6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com> Message-ID: OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? If I did I am sorry.. And I gave my apology to every one I could have offended.. But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. From: kk6ecm Sent: Tuesday, September 09, 2014 1:40 PM To: APP RPT Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I use this when ACID will not load, usually due to issues with BIOS and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. Thanks, Bob kk6ecm Sent from iPad On Sep 9, 2014, at 8:27 AM, pete M wrote: Ok will try that.. thanks! From: Bob Sent: Tuesday, September 09, 2014 10:55 AM To: 'APP RPT' Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I?ve done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS website No features, tools only, no desktop (competes with Asterisk) Set ssh /etc/ssh/sshd_config Run "setup" at comand line and disable firewall vi /etc/rc.d/acidrepo http://dl.allstarlink.org Execute portion of ks.cfg, each line at a time cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig cat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.sh Auto reboot after phase1.sh executed phase2.sh runs automatically to completion Bob kk6ecm ---------------------------------------------------------------------------- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org../. Getting files.tar.gz from http://dl.allstarlink.org../. ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? ---------------------------------------------------------------------------- _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kk6ecm at gmail.com Wed Sep 10 16:15:13 2014 From: kk6ecm at gmail.com (kk6ecm) Date: Wed, 10 Sep 2014 09:15:13 -0700 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com> Message-ID: <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com> Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} Thanks, Bob kk6ecm Sent from iPad > On Sep 10, 2014, at 8:30 AM, pete M wrote: > > OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? > > If I did I am sorry.. And I gave my apology to every one I could have offended.. > > But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. > > Like just point me the pathway.. I will try to do it on my own.. > > Thanks > > > > > > > >> On Sep 9, 2014, at 11:13 AM, pete M wrote: >> >> I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. >> >> I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. >> >> >> >> From: kk6ecm >> Sent: Tuesday, September 09, 2014 1:40 PM >> To: APP RPT >> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> >> I use this when ACID will not load, usually due to issues with BIOS and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. >> >> Thanks, >> Bob >> kk6ecm >> >> Sent from iPad >> >> >>> On Sep 9, 2014, at 8:27 AM, pete M wrote: >>> >>> Ok will try that.. >>> >>> thanks! >>> >>> >>> From: Bob >>> Sent: Tuesday, September 09, 2014 10:55 AM >>> To: 'APP RPT' >>> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >>> >>> I?ve done this several times without issue. Here are the steps I used. >>> >>> >>> >>> Load CentOS 5.10 downloaded from CentOS website >>> >>> No features, tools only, no desktop (competes with Asterisk) >>> >>> Set ssh /etc/ssh/sshd_config >>> >>> Run "setup" at comand line and disable firewall >>> >>> vi /etc/rc.d/acidrepo >>> >>> http://dl.allstarlink.org >>> >>> Execute portion of ks.cfg, each line at a time >>> >>> cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig >>> >>> cat <>/etc/rc.d/rc.local >>> >>> >>> >>> cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh >>> >>> >>> >>> chmod 755 /etc/rc.d/phase1.sh >>> >>> >>> >>> /etc/rc.d/phase1.sh >>> >>> Auto reboot after phase1.sh executed >>> >>> phase2.sh runs automatically to completion >>> >>> >>> >>> Bob >>> >>> kk6ecm >>> >>> >>> >>> From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M >>> Sent: Tuesday, September 09, 2014 7:00 AM >>> To: APP RPT >>> Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >>> >>> >>> >>> Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. >>> >>> >>> >>> I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. >>> >>> >>> >>> here is the out put from the script >>> >>> >>> >>> sh phase2.sh >>> >>> ****** Phase 2 post install ****** >>> >>> Getting asterisk install script from http://dl.allstarlink.org../. >>> >>> Getting files.tar.gz from http://dl.allstarlink.org../. >>> >>> ****** Asterisk Installation ****** >>> >>> /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found >>> >>> Unpacking files.tar.gz... >>> >>> Compiling Zaptel... >>> >>> checking for gcc... gcc >>> >>> checking for C compiler default output file name... a.out >>> >>> checking whether the C compiler works... yes >>> >>> checking whether we are cross compiling... no >>> >>> checking for suffix of executables... >>> >>> checking for suffix of object files... o >>> >>> checking whether we are using the GNU C compiler... yes >>> >>> checking whether gcc accepts -g... yes >>> >>> checking for gcc option to accept ISO C89... none needed >>> >>> checking how to run the C preprocessor... gcc -E >>> >>> checking for a BSD-compatible install... /usr/bin/install -c >>> >>> checking whether ln -s works... yes >>> >>> checking for GNU make... make >>> >>> checking for grep... /bin/grep >>> >>> checking for sh... /bin/sh >>> >>> checking for ln... /bin/ln >>> >>> checking for wget... /usr/bin/wget >>> >>> checking for grep that handles long lines and -e... (cached) /bin/grep >>> >>> checking for egrep... /bin/grep -E >>> >>> checking for ANSI C header files... yes >>> >>> checking for sys/types.h... yes >>> >>> checking for sys/stat.h... yes >>> >>> checking for stdlib.h... yes >>> >>> checking for string.h... yes >>> >>> checking for memory.h... yes >>> >>> checking for strings.h... yes >>> >>> checking for inttypes.h... yes >>> >>> checking for stdint.h... yes >>> >>> checking for unistd.h... yes >>> >>> checking for initscr in -lcurses... no >>> >>> checking for initscr in -lncurses... no >>> >>> checking for newtBell in -lnewt... no >>> >>> checking for usb_init in -lusb... no >>> >>> configure: creating ./config.status >>> >>> config.status: creating build_tools/menuselect-deps >>> >>> config.status: creating makeopts >>> >>> config.status: creating build_tools/make_firmware_object >>> >>> configure: *** Zaptel build successfully configured *** >>> >>> make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' >>> >>> checking build system type... i686-pc-linux-gnu >>> >>> checking host system type... i686-pc-linux-gnu >>> >>> checking for gcc... gcc >>> >>> checking for C compiler default output file name... a.out >>> >>> checking whether the C compiler works... yes >>> >>> checking whether we are cross compiling... no >>> >>> checking for suffix of executables... >>> >>> checking for suffix of object files... o >>> >>> checking whether we are using the GNU C compiler... yes >>> >>> checking whether gcc accepts -g... yes >>> >>> checking for gcc option to accept ANSI C... none needed >>> >>> checking for GNU make... make >>> >>> checking for asprintf... yes >>> >>> checking for getloadavg... yes >>> >>> checking for setenv... yes >>> >>> checking for strcasestr... yes >>> >>> checking for strndup... yes >>> >>> checking for strnlen... yes >>> >>> checking for strsep... yes >>> >>> checking for strtoq... yes >>> >>> checking for unsetenv... yes >>> >>> checking for vasprintf... yes >>> >>> checking how to run the C preprocessor... gcc -E >>> >>> checking for egrep... grep -E >>> >>> checking for ANSI C header files... yes >>> >>> checking for sys/types.h... yes >>> >>> checking for sys/stat.h... yes >>> >>> checking for stdlib.h... yes >>> >>> checking for string.h... yes >>> >>> checking for memory.h... yes >>> >>> checking for strings.h... yes >>> >>> checking for inttypes.h... yes >>> >>> checking for stdint.h... yes >>> >>> checking for unistd.h... yes >>> >>> checking for initscr in -lcurses... no >>> >>> checking for initscr in -lncurses... no >>> >>> checking for pkg-config... No >>> >>> configure: creating ./config.status >>> >>> config.status: creating makeopts >>> >>> config.status: creating autoconfig.h >>> >>> configure: configuring in mxml >>> >>> configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. >>> >>> checking for gcc... gcc >>> >>> checking for C compiler default output file name... a.out >>> >>> checking whether the C compiler works... yes >>> >>> checking whether we are cross compiling... no >>> >>> checking for suffix of executables... >>> >>> checking for suffix of object files... o >>> >>> checking whether we are using the GNU C compiler... yes >>> >>> checking whether gcc accepts -g... yes >>> >>> checking for gcc option to accept ANSI C... none needed >>> >>> checking for g++... no >>> >>> checking for c++... no >>> >>> checking for gpp... no >>> >>> checking for aCC... no >>> >>> checking for CC... no >>> >>> checking for cxx... no >>> >>> checking for cc++... no >>> >>> checking for cl... no >>> >>> checking for FCC... no >>> >>> checking for KCC... no >>> >>> checking for RCC... no >>> >>> checking for xlC_r... no >>> >>> checking for xlC... no >>> >>> checking whether we are using the GNU C++ compiler... no >>> >>> checking whether g++ accepts -g... no >>> >>> checking for a BSD-compatible install... /usr/bin/install -c >>> >>> checking for ranlib... ranlib >>> >>> checking for ar... /usr/bin/ar >>> >>> checking for cp... /bin/cp >>> >>> checking for ln... /bin/ln >>> >>> checking for mkdir... /bin/mkdir >>> >>> checking for nroff... /usr/bin/nroff >>> >>> checking for rm... /bin/rm >>> >>> checking for strdup... yes >>> >>> checking for vsnprintf... yes >>> >>> configure: creating ./config.status >>> >>> config.status: creating Makefile >>> >>> config.status: creating mxml.list >>> >>> config.status: creating mxml.pc >>> >>> config.status: creating config.h >>> >>> configure: Menuselect build configuration successfully completed >>> >>> make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' >>> >>> make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' >>> >>> make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' >>> >>> gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c >>> >>> gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c >>> >>> gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c >>> >>> make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' >>> >>> gcc -O -Wall -c mxml-attr.c >>> >>> gcc -O -Wall -c mxml-entity.c >>> >>> gcc -O -Wall -c mxml-file.c >>> >>> gcc -O -Wall -c mxml-index.c >>> >>> gcc -O -Wall -c mxml-node.c >>> >>> gcc -O -Wall -c mxml-search.c >>> >>> gcc -O -Wall -c mxml-set.c >>> >>> gcc -O -Wall -c mxml-private.c >>> >>> gcc -O -Wall -c mxml-string.c >>> >>> /bin/rm -f libmxml.a >>> >>> /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o >>> >>> a - mxml-attr.o >>> >>> a - mxml-entity.o >>> >>> a - mxml-file.o >>> >>> a - mxml-index.o >>> >>> a - mxml-node.o >>> >>> a - mxml-search.o >>> >>> a - mxml-set.o >>> >>> a - mxml-private.o >>> >>> a - mxml-string.o >>> >>> ranlib libmxml.a >>> >>> make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' >>> >>> gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a >>> >>> make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' >>> >>> make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' >>> >>> Generating input for menuselect ... >>> >>> >>> >>> *********************************************************** >>> >>> The existing menuselect.makeopts file did not specify >>> >>> that 'zttool' should not be included. However, either some >>> >>> dependencies for this module were not found or a >>> >>> conflict exists. >>> >>> >>> >>> Either run 'make menuselect' or remove the existing >>> >>> menuselect.makeopts file to resolve this issue. >>> >>> *********************************************************** >>> >>> >>> >>> make: *** [menuselect.makeopts] Error 255 >>> >>> Failure: Unable to compile Zaptel 2 >>> >>> Fatal error: Unable to install Asterisk! >>> >>> [root at node rc.d]# >>> >>> >>> >>> I dont know where to go from there.. >>> >>> >>> >>> Anyone care to help a bit? >>> >>> >>> >>> >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From petem001 at hotmail.com Wed Sep 10 18:12:38 2014 From: petem001 at hotmail.com (pete M) Date: Wed, 10 Sep 2014 14:12:38 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com> References: , <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP>, , <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com>, , , , <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com> Message-ID: Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. If it would be installed at least up to a point. I would be able to do it.. I just dont know how to tell the compiler not to compile that part and go on.. From: kk6ecm at gmail.com Date: Wed, 10 Sep 2014 09:15:13 -0700 To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} Thanks,Bobkk6ecm Sent from iPad On Sep 10, 2014, at 8:30 AM, pete M wrote: OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? If I did I am sorry.. And I gave my apology to every one I could have offended.. But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. From: kk6ecm Sent: Tuesday, September 09, 2014 1:40 PM To: APP RPT Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I use this when ACID will not load, usually due to issues with BIOS and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. Thanks, Bob kk6ecm Sent from iPad On Sep 9, 2014, at 8:27 AM, pete M wrote: Ok will try that.. thanks! From: Bob Sent: Tuesday, September 09, 2014 10:55 AM To: 'APP RPT' Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I?ve done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS website No features, tools only, no desktop (competes with Asterisk) Set ssh /etc/ssh/sshd_config Run "setup" at comand line and disable firewall vi /etc/rc.d/acidrepo http://dl.allstarlink.org Execute portion of ks.cfg, each line at a time cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig cat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.sh Auto reboot after phase1.sh executed phase2.sh runs automatically to completion Bob kk6ecm From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org../. Getting files.tar.gz from http://dl.allstarlink.org../. ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Wed Sep 10 22:16:03 2014 From: doug at crompton.com (Doug Crompton) Date: Wed, 10 Sep 2014 18:16:03 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: , , <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP>, , , , <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com>, , , , , , , , <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com>, Message-ID: Pete, I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org Date: Wed, 10 Sep 2014 14:12:38 -0400 Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. If it would be installed at least up to a point. I would be able to do it.. I just dont know how to tell the compiler not to compile that part and go on.. From: kk6ecm at gmail.com Date: Wed, 10 Sep 2014 09:15:13 -0700 To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} Thanks,Bobkk6ecm Sent from iPad On Sep 10, 2014, at 8:30 AM, pete M wrote: OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? If I did I am sorry.. And I gave my apology to every one I could have offended.. But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. From: kk6ecm Sent: Tuesday, September 09, 2014 1:40 PM To: APP RPT Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. Thanks, Bob kk6ecm Sent from iPad On Sep 9, 2014, at 8:27 AM, pete M wrote: Ok will try that.. thanks! From: Bob Sent: Tuesday, September 09, 2014 10:55 AM To: 'APP RPT' Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I?ve done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS website No features, tools only, no desktop (competes with Asterisk) Set ssh /etc/ssh/sshd_config Run "setup" at comand line and disable firewall vi /etc/rc.d/acidrepo http://dl.allstarlink.org Execute portion of ks.cfg, each line at a time cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig cat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.sh Auto reboot after phase1.sh executed phase2.sh runs automatically to completion Bob kk6ecm From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org../. Getting files.tar.gz from http://dl.allstarlink.org../. ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln< /font> checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdboyle at bdboyle.com Thu Sep 11 00:15:08 2014 From: bdboyle at bdboyle.com (Bryan D. Boyle) Date: Wed, 10 Sep 2014 20:15:08 -0400 Subject: [App_rpt-users] semi-free to good home Message-ID: <4FE31707-310B-4754-939D-939BC35CD628@bdboyle.com> pick up ONLY near trenton nj at QRZ QTH: Not playing shipping clerk. 1 MSF5000 900 MHz 150 watt digital station. E-Z adaptation to allstar, literally 4 wires. Have one on air and it's rock steady and working; haven't touched it in months. RSS programmable. needs tuning, but if you have experience with these, and access to a test panel and service monitor, it's a cinch. From the PSE&G cache. $100. 1 MSR2000 440 analog repeater. 60w. Rocked for 444.9875 +5 needs tuning. With test panel, $75. 'working when removed' 1 GM300 VHF mobile, 45w. Tuned per spec, w/DTMF mic, works fine down to 144. $50 1 GM300-based 45w (turned down to 30w) 2m repeater setup w/URI. was on air till CPU went tango uniform. $150 1 Phelps-Dodge 144MHZ 6-can duplexer. The big one. Interconnect cables need re-doing (they were RG-8 from the factory, in the days when rcvrs weren't sensitive, it didn't matter), and cans need retuning. $400. 1 never used RTCM. $200. Box of Spectra A4 heads free. If no one wants the stuff, i'm sure the metal recycler will pick up from curb. Don't have time or inclination to futz with this stuff, and need to start thinning out the herd and cleaning out the homestead. -- Bryan Sent from my iPhone 5...No electrons were harmed in the sending of this message. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Thu Sep 11 03:11:32 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Wed, 10 Sep 2014 20:11:32 -0700 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com> <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com> Message-ID: <3106238D-9CCD-48F4-AEF2-E3E2A0EE2839@mac.com> Is this what you were thinking of? > From: Jim Duuuude > Subject: [App_rpt-users] "Official" "fixed" DAHDI patches > Date: March 25, 2014 at 11:32:09 AM PDT > To: app_rpt mailing list , "mike at glaserelectronics.com" > > After much lamenting this morning, I have come up with what I feel comfortable > as a "working" DAHDI patch set. This is useful if you are wanting to "roll your own" > app_rpt system (perhaps on some non-(Centos 5.X 32 bit) platform). > > If you take any of the distros of DAHDI 2.5.1 or newer, and apply these patches, > it should "work". > > This patch set may be obtained from: > > https://allstarlink.org/fixed-dahdi-patches.tar.gz > > or from SVN at: > > http://svn.ohnosec.org/viewvc/projects/allstar/astsrc-1.4.23-pre/trunk/fixed-dahdi-patches/?root=svn > > -- Tim :wq On Sep 10, 2014, at 11:12 AM, pete M wrote: > Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. > > If it would be installed at least up to a point. I would be able to do it.. > > I just dont know how to tell the compiler not to compile that part and go on.. > > > > From: kk6ecm at gmail.com > Date: Wed, 10 Sep 2014 09:15:13 -0700 > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. > > As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} > > Thanks, > Bob > kk6ecm > > Sent from iPad > > > On Sep 10, 2014, at 8:30 AM, pete M wrote: > > OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? > > If I did I am sorry.. And I gave my apology to every one I could have offended.. > > But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. > > Like just point me the pathway.. I will try to do it on my own.. > > Thanks > > > > > > > > On Sep 9, 2014, at 11:13 AM, pete M wrote: > > I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. > > I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. > > > > From: kk6ecm > Sent: Tuesday, September 09, 2014 1:40 PM > To: APP RPT > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I use this when ACID will not load, usually due to issues with BIOS and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. > > Thanks, > Bob > kk6ecm > > Sent from iPad > > > On Sep 9, 2014, at 8:27 AM, pete M wrote: > > Ok will try that.. > > thanks! > > > From: Bob > Sent: Tuesday, September 09, 2014 10:55 AM > To: 'APP RPT' > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I?ve done this several times without issue. Here are the steps I used. > > Load CentOS 5.10 downloaded from CentOS website > No features, tools only, no desktop (competes with Asterisk) > Set ssh /etc/ssh/sshd_config > Run "setup" at comand line and disable firewall > vi /etc/rc.d/acidrepo > http://dl.allstarlink.org > Execute portion of ks.cfg, each line at a time > cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig > cat <>/etc/rc.d/rc.local > > cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh > > chmod 755 /etc/rc.d/phase1.sh > > /etc/rc.d/phase1.sh > Auto reboot after phase1.sh executed > phase2.sh runs automatically to completion > > Bob > kk6ecm > > From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M > Sent: Tuesday, September 09, 2014 7:00 AM > To: APP RPT > Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. > > I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. > > here is the out put from the script > > sh phase2.sh > ****** Phase 2 post install ****** > Getting asterisk install script from http://dl.allstarlink.org../. > Getting files.tar.gz from http://dl.allstarlink.org../. > ****** Asterisk Installation ****** > /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found > Unpacking files.tar.gz... > Compiling Zaptel... > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking how to run the C preprocessor... gcc -E > checking for a BSD-compatible install... /usr/bin/install -c > checking whether ln -s works... yes > checking for GNU make... make > checking for grep... /bin/grep > checking for sh... /bin/sh > checking for ln... /bin/ln > checking for wget... /usr/bin/wget > checking for grep that handles long lines and -e... (cached) /bin/grep > checking for egrep... /bin/grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for initscr in -lcurses... no > checking for initscr in -lncurses... no > checking for newtBell in -lnewt... no > checking for usb_init in -lusb... no > configure: creating ./config.status > config.status: creating build_tools/menuselect-deps > config.status: creating makeopts > config.status: creating build_tools/make_firmware_object > configure: *** Zaptel build successfully configured *** > make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking for GNU make... make > checking for asprintf... yes > checking for getloadavg... yes > checking for setenv... yes > checking for strcasestr... yes > checking for strndup... yes > checking for strnlen... yes > checking for strsep... yes > checking for strtoq... yes > checking for unsetenv... yes > checking for vasprintf... yes > checking how to run the C preprocessor... gcc -E > checking for egrep... grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for initscr in -lcurses... no > checking for initscr in -lncurses... no > checking for pkg-config... No > configure: creating ./config.status > config.status: creating makeopts > config.status: creating autoconfig.h > configure: configuring in mxml > configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking for g++... no > checking for c++... no > checking for gpp... no > checking for aCC... no > checking for CC... no > checking for cxx... no > checking for cc++... no > checking for cl... no > checking for FCC... no > checking for KCC... no > checking for RCC... no > checking for xlC_r... no > checking for xlC... no > checking whether we are using the GNU C++ compiler... no > checking whether g++ accepts -g... no > checking for a BSD-compatible install... /usr/bin/install -c > checking for ranlib... ranlib > checking for ar... /usr/bin/ar > checking for cp... /bin/cp > checking for ln... /bin/ln > checking for mkdir... /bin/mkdir > checking for nroff... /usr/bin/nroff > checking for rm... /bin/rm > checking for strdup... yes > checking for vsnprintf... yes > configure: creating ./config.status > config.status: creating Makefile > config.status: creating mxml.list > config.status: creating mxml.pc > config.status: creating config.h > configure: Menuselect build configuration successfully completed > make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c > gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c > gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c > make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' > gcc -O -Wall -c mxml-attr.c > gcc -O -Wall -c mxml-entity.c > gcc -O -Wall -c mxml-file.c > gcc -O -Wall -c mxml-index.c > gcc -O -Wall -c mxml-node.c > gcc -O -Wall -c mxml-search.c > gcc -O -Wall -c mxml-set.c > gcc -O -Wall -c mxml-private.c > gcc -O -Wall -c mxml-string.c > /bin/rm -f libmxml.a > /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o > a - mxml-attr.o > a - mxml-entity.o > a - mxml-file.o > a - mxml-index.o > a - mxml-node.o > a - mxml-search.o > a - mxml-set.o > a - mxml-private.o > a - mxml-string.o > ranlib libmxml.a > make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' > gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a > make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > Generating input for menuselect ... > > *********************************************************** > The existing menuselect.makeopts file did not specify > that 'zttool' should not be included. However, either some > dependencies for this module were not found or a > conflict exists. > > Either run 'make menuselect' or remove the existing > menuselect.makeopts file to resolve this issue. > *********************************************************** > > make: *** [menuselect.makeopts] Error 255 > Failure: Unable to compile Zaptel 2 > Fatal error: Unable to install Asterisk! > [root at node rc.d]# > > I dont know where to go from there.. > > Anyone care to help a bit? > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From w2ymm1 at gmail.com Thu Sep 11 12:10:11 2014 From: w2ymm1 at gmail.com (Bob Prybyzerski) Date: Thu, 11 Sep 2014 08:10:11 -0400 Subject: [App_rpt-users] semi-free to good home In-Reply-To: <4FE31707-310B-4754-939D-939BC35CD628@bdboyle.com> References: <4FE31707-310B-4754-939D-939BC35CD628@bdboyle.com> Message-ID: <90343AE1-10D8-41F1-8FA7-FBF40AFDA70C@gmail.com> Bryan, I am interested in the MSF. Bob W2YMM Direct email is w2ymm1 at gmail.com 1 MSF5000 900 MHz 150 watt digital station. E-Z adaptation to allstar, literally 4 wires. Have one on air and it's rock steady and working; haven't touched it in months. RSS programmable. needs tuning, but if you have experience with these, and access to a test panel and service monitor, it's a cinch. From the PSE&G cache. $100. Sent from my iPhone Bob Prybyzerski 631-960-1051 > On Sep 10, 2014, at 8:15 PM, "Bryan D. Boyle" wrote: > > pick up ONLY near trenton nj at QRZ QTH: Not playing shipping clerk. > > 1 MSF5000 900 MHz 150 watt digital station. E-Z adaptation to allstar, literally 4 wires. Have one on air and it's rock steady and working; haven't touched it in months. RSS programmable. needs tuning, but if you have experience with these, and access to a test panel and service monitor, it's a cinch. From the PSE&G cache. $100. > > 1 MSR2000 440 analog repeater. 60w. Rocked for 444.9875 +5 needs tuning. With test panel, $75. 'working when removed' > > 1 GM300 VHF mobile, 45w. Tuned per spec, w/DTMF mic, works fine down to 144. $50 > > 1 GM300-based 45w (turned down to 30w) 2m repeater setup w/URI. was on air till CPU went tango uniform. $150 > > 1 Phelps-Dodge 144MHZ 6-can duplexer. The big one. Interconnect cables need re-doing (they were RG-8 from the factory, in the days when rcvrs weren't sensitive, it didn't matter), and cans need retuning. $400. > > 1 never used RTCM. $200. > > Box of Spectra A4 heads free. > > If no one wants the stuff, i'm sure the metal recycler will pick up from curb. > > Don't have time or inclination to futz with this stuff, and need to start thinning out the herd and cleaning out the homestead. > -- > Bryan > Sent from my iPhone 5...No electrons were harmed in the sending of this message. > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kb1ncj at gmail.com Thu Sep 11 12:55:45 2014 From: kb1ncj at gmail.com (Greg) Date: Thu, 11 Sep 2014 08:55:45 -0400 Subject: [App_rpt-users] change location name In-Reply-To: References: Message-ID: <54119BD1.2030307@gmail.com> Hi, I can't seem to find any place to change the name of my location that appears in the public node list or description of my node. If it is local to my server, which file is modified? Thanks Greg From kb1ncj at gmail.com Thu Sep 11 13:06:01 2014 From: kb1ncj at gmail.com (Greg) Date: Thu, 11 Sep 2014 09:06:01 -0400 Subject: [App_rpt-users] update-change location name In-Reply-To: References: Message-ID: <54119E39.6040202@gmail.com> Never mind.. I was blind! Hi, I can't seem to find any place to change the name of my location that appears in the public node list or description of my node. If it is local to my server, which file is modified? Thanks Greg From kb1ncj at gmail.com Thu Sep 11 13:20:52 2014 From: kb1ncj at gmail.com (Greg) Date: Thu, 11 Sep 2014 09:20:52 -0400 Subject: [App_rpt-users] another (legitimate) question In-Reply-To: References: Message-ID: <5411A1B4.3070101@gmail.com> I looked up my node on the Echolink link status page and see that the frequency and tone and ant height etc is all garbled with the missing variables in the comments field. I did a search near the Los Angeles area and noticed others the same (that have it coupled with Allstar). Maybe this hasn't been noticed yet.. I almost never look up my node there but was checking since I moved my location. Greg From kb1ncj at gmail.com Thu Sep 11 13:28:08 2014 From: kb1ncj at gmail.com (Greg) Date: Thu, 11 Sep 2014 09:28:08 -0400 Subject: [App_rpt-users] update-another (legitimate) question In-Reply-To: References: Message-ID: <5411A368.9040007@gmail.com> Well oh well.. now it is fine!! Maybe a bug in my browser?? Strange because all the other nodes in the list were fine. I looked up my node on the Echolink link status page and see that the frequency and tone and ant height etc is all garbled with the missing variables in the comments field. I did a search near the Los Angeles area and noticed others the same (that have it coupled with Allstar). Maybe this hasn't been noticed yet.. I almost never look up my node there but was checking since I moved my location. Greg From kb1ncj at gmail.com Thu Sep 11 13:30:13 2014 From: kb1ncj at gmail.com (Greg) Date: Thu, 11 Sep 2014 09:30:13 -0400 Subject: [App_rpt-users] update-another (legitimate) question In-Reply-To: References: Message-ID: <5411A3E5.9000600@gmail.com> Actually, it's not quite right yet.. it still shows odd values for power and height. Maybe someone can check on this and see if they see what I am seeing.. Well oh well.. now it is fine!! Maybe a bug in my browser?? Strange because all the other nodes in the list were fine. I looked up my node on the Echolink link status page and see that the frequency and tone and ant height etc is all garbled with the missing variables in the comments field. I did a search near the Los Angeles area and noticed others the same (that have it coupled with Allstar). Maybe this hasn't been noticed yet.. I almost never look up my node there but was checking since I moved my location. Greg From petem001 at hotmail.com Thu Sep 11 13:42:08 2014 From: petem001 at hotmail.com (pete M) Date: Thu, 11 Sep 2014 09:42:08 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: , , <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP>, , , , <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com>, , , , , , , , <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com>, Message-ID: well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.. I can run the system on bunch of disto.. Here is the list.. CentOS 5 32bit CentOS 5 64bit CentOS 6 32bit CentOS 6 64bit CentOS 7 64bit CentOS 7 64bit Minimal Debian 6 32bit Debian 6 64bit Debian 7 32bit Debian 7 32bit Minimal Debian 7 64bit Debian 7 64bit Minimal Fedora 17 32bit Fedora 17 64bit Fedora 19 32bit Fedora 19 64bit Starbound-Ubuntu 13.10 32bit SUSE 12.2 32bit SUSE 12.2 64bit Ubuntu 10.04 32bit Ubuntu 10.04 64bit Ubuntu 11.10 32bit Ubuntu 11.10 64bit Ubuntu 12.10 32bit Ubuntu 12.10 64bit Ubuntu 13.10 32bit Ubuntu 13.10 64bit Ubuntu 14.04 32bit Ubuntu 14.04 32bit Minimal Ubuntu 14.04 64bit Ubuntu 14.04 64bit Minimal So I have lots of choice But I was under the feeling that the best distro was centos 5 for acid.. (using the install script from the cd.. Unless you can point me in another direction.. From: Doug Crompton Sent: Wednesday, September 10, 2014 6:16 PM To: pete M Cc: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Pete, I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. 73 Doug WA3DSP http://www.crompton.com/hamradio -------------------------------------------------------------------------------- From: petem001 at hotmail.com To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org Date: Wed, 10 Sep 2014 14:12:38 -0400 Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. If it would be installed at least up to a point. I would be able to do it.. I just dont know how to tell the compiler not to compile that part and go on.. -------------------------------------------------------------------------------- From: kk6ecm at gmail.com Date: Wed, 10 Sep 2014 09:15:13 -0700 To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} Thanks, Bob kk6ecm Sent from iPad On Sep 10, 2014, at 8:30 AM, pete M wrote: OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? If I did I am sorry.. And I gave my apology to every one I could have offended.. But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. From: kk6ecm Sent: Tuesday, September 09, 2014 1:40 PM To: APP RPT Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. Thanks, Bob kk6ecm Sent from iPad On Sep 9, 2014, at 8:27 AM, pete M wrote: Ok will try that.. thanks! From: Bob Sent: Tuesday, September 09, 2014 10:55 AM To: 'APP RPT' Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I?ve done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS website No features, tools only, no desktop (competes with Asterisk) Set ssh /etc/ssh/sshd_config Run "setup" at comand line and disable firewall vi /etc/rc.d/acidrepo http://dl.allstarlink.org Execute portion of ks.cfg, each line at a time cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig cat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.sh Auto reboot after phase1.sh executed phase2.sh runs automatically to completion Bob kk6ecm -------------------------------------------------------------------------- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org../. Getting files.tar.gz from http://dl.allstarlink.org../. ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln< /font> checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? -------------------------------------------------------------------------- _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wlEmoticon-winkingsmile[1].png Type: image/png Size: 1135 bytes Desc: not available URL: From petem001 at hotmail.com Thu Sep 11 13:43:29 2014 From: petem001 at hotmail.com (pete M) Date: Thu, 11 Sep 2014 09:43:29 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: <3106238D-9CCD-48F4-AEF2-E3E2A0EE2839@mac.com> References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com> <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com> <3106238D-9CCD-48F4-AEF2-E3E2A0EE2839@mac.com> Message-ID: Thanks Tim. this will help a lot.. My searching skills are usely not bad, But I dont have any good luck on the archive site.. From: Tim Sawyer Sent: Wednesday, September 10, 2014 11:11 PM To: pete M Cc: Bob ; APP RPT Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Is this what you were thinking of? From: Jim Duuuude Subject: [App_rpt-users] "Official" "fixed" DAHDI patches Date: March 25, 2014 at 11:32:09 AM PDT To: app_rpt mailing list , "mike at glaserelectronics.com" After much lamenting this morning, I have come up with what I feel comfortable as a "working" DAHDI patch set. This is useful if you are wanting to "roll your own" app_rpt system (perhaps on some non-(Centos 5.X 32 bit) platform). If you take any of the distros of DAHDI 2.5.1 or newer, and apply these patches, it should "work". This patch set may be obtained from: https://allstarlink.org/fixed-dahdi-patches.tar.gz or from SVN at: http://svn.ohnosec.org/viewvc/projects/allstar/astsrc-1.4.23-pre/trunk/fixed-dahdi-patches/?root=svn -- Tim :wq On Sep 10, 2014, at 11:12 AM, pete M wrote: Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. If it would be installed at least up to a point. I would be able to do it.. I just dont know how to tell the compiler not to compile that part and go on.. ------------------------------------------------------------------------------ From: kk6ecm at gmail.com Date: Wed, 10 Sep 2014 09:15:13 -0700 To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} Thanks, Bob kk6ecm Sent from iPad On Sep 10, 2014, at 8:30 AM, pete M wrote: OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? If I did I am sorry.. And I gave my apology to every one I could have offended.. But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. From: kk6ecm Sent: Tuesday, September 09, 2014 1:40 PM To: APP RPT Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I use this when ACID will not load, usually due to issues with BIOS and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. Thanks, Bob kk6ecm Sent from iPad On Sep 9, 2014, at 8:27 AM, pete M wrote: Ok will try that.. thanks! From: Bob Sent: Tuesday, September 09, 2014 10:55 AM To: 'APP RPT' Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I?ve done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS website No features, tools only, no desktop (competes with Asterisk) Set ssh /etc/ssh/sshd_config Run "setup" at comand line and disable firewall vi /etc/rc.d/acidrepo http://dl.allstarlink.org Execute portion of ks.cfg, each line at a time cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig cat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.sh Auto reboot after phase1.sh executed phase2.sh runs automatically to completion Bob kk6ecm ------------------------------------------------------------------------ From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org../. Getting files.tar.gz from http://dl.allstarlink.org../. ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? ------------------------------------------------------------------------ _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Thu Sep 11 15:03:44 2014 From: doug at crompton.com (Doug Crompton) Date: Thu, 11 Sep 2014 11:03:44 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: , , <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP>, , , , <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com>, , , , , , , , <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com>, , Message-ID: I am not sure what you are saying when you comment.... "well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.." Did you mean "will" ?? The patches can be applied against the latest dahdi and it will compile on late kernels. The BBB is an example of that. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 09:42:08 -0400 well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.. I can run the system on bunch of disto.. Here is the list.. CentOS 5 32bit CentOS 5 64bit CentOS 6 32bit CentOS 6 64bit CentOS 7 64bit CentOS 7 64bit Minimal Debian 6 32bit Debian 6 64bit Debian 7 32bit Debian 7 32bit Minimal Debian 7 64bit Debian 7 64bit Minimal Fedora 17 32bit Fedora 17 64bit Fedora 19 32bit Fedora 19 64bit Starbound-Ubuntu 13.10 32bit SUSE 12.2 32bit SUSE 12.2 64bit Ubuntu 10.04 32bit Ubuntu 10.04 64bit Ubuntu 11.10 32bit Ubuntu 11.10 64bit Ubuntu 12.10 32bit Ubuntu 12.10 64bit Ubuntu 13.10 32bit Ubuntu 13.10 64bit Ubuntu 14.04 32bit Ubuntu 14.04 32bit Minimal Ubuntu 14.04 64bit Ubuntu 14.04 64bit Minimal So I have lots of choice But I was under the feeling that the best distro was centos 5 for acid.. (using the install script from the cd.. Unless you can point me in another direction.. From: Doug Crompton Sent: Wednesday, September 10, 2014 6:16 PM To: pete M Cc: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Pete, I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org Date: Wed, 10 Sep 2014 14:12:38 -0400 Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. If it would be installed at least up to a point. I would be able to do it.. I just dont know how to tell the compiler not to compile that part and go on.. From: kk6ecm at gmail.com Date: Wed, 10 Sep 2014 09:15:13 -0700 To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} Thanks, Bob kk6ecm Sent from iPad On Sep 10, 2014, at 8:30 AM, pete M wrote: OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? If I did I am sorry.. And I gave my apology to every one I could have offended.. But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. From: kk6ecm Sen t: Tuesday, September 09, 2014 1:40 PM To: APP RPT Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. Thanks, Bob kk6ecm Sent from iPad On Sep 9, 2014, at 8:27 AM, pete M wrote: Ok will try that.. thanks! From: Bob Sent: Tuesday, September 09, 2014 10:55 AM To: 'APP RPT' Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I?ve done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS website No features, tools only, no desktop (competes with Asterisk) Set ssh /etc/ssh/sshd_config Run "setup" at comand line and disable firewall vi /etc/rc.d/acidrepo http://dl.allstarlink.org Execute portion of ks.cfg, each line at a time cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig cat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.sh Auto reboot after phase1.sh executed phase2.sh runs automatically to completion Bob kk6ecm From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org../. Getting files.tar.gz from http://dl.allstarlink.org../. ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preproc esso r... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln< /font> checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wlEmoticon-winkingsmile[1].png Type: image/png Size: 1135 bytes Desc: not available URL: From kb4fxc at inttek.net Thu Sep 11 16:55:16 2014 From: kb4fxc at inttek.net (David McGough) Date: Thu, 11 Sep 2014 12:55:16 -0400 (EDT) Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: Message-ID: Hi Pete, I've been briefly following this thread, but no time to respond until now. Asterisk/AllStar does run fine on Debian Wheezy (version 7.6), 64-bit. I'm using the exact source code (including Jim's dahdi patches) as found in the BeagleBone Black release, in the /usr/src/utils directory. This debian system is used as a "hub server," so it sees a lot of traffic and it has run perfectly. Unfortunately, getting the code compiled from scratch under Wheezy is a chore best suited for those with a moderate level of Linux experience. By that I mean you must manually resolve many dependencies, etc. In the near future I expect a how-to explaining this process, but, we don't have one yet. I will also mention that CentOS5, included with the current ACID release, is a dead end for most modern motherboards. The old kernel included does not have proper drivers for peripherals or chipsets. I hope this helps some- 73, David KB4FXC On Thu, 11 Sep 2014, pete M wrote: > well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.. > > I can run the system on bunch of disto.. > > Here is the list.. > > > CentOS 5 32bit > CentOS 5 64bit > CentOS 6 32bit > CentOS 6 64bit > CentOS 7 64bit > CentOS 7 64bit Minimal > Debian 6 32bit > Debian 6 64bit > Debian 7 32bit > Debian 7 32bit Minimal > Debian 7 64bit > Debian 7 64bit Minimal > Fedora 17 32bit > Fedora 17 64bit > Fedora 19 32bit > Fedora 19 64bit > Starbound-Ubuntu 13.10 32bit > SUSE 12.2 32bit > SUSE 12.2 64bit > Ubuntu 10.04 32bit > Ubuntu 10.04 64bit > Ubuntu 11.10 32bit > Ubuntu 11.10 64bit > Ubuntu 12.10 32bit > Ubuntu 12.10 64bit > Ubuntu 13.10 32bit > Ubuntu 13.10 64bit > Ubuntu 14.04 32bit > Ubuntu 14.04 32bit Minimal > Ubuntu 14.04 64bit > Ubuntu 14.04 64bit Minimal > > So I have lots of choice > > But I was under the feeling that the best distro was centos 5 for acid.. (using the install script from the cd.. > > Unless you can point me in another direction.. > > > > > > From: Doug Crompton > Sent: Wednesday, September 10, 2014 6:16 PM > To: pete M > Cc: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Pete, > > I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > > > -------------------------------------------------------------------------------- > From: petem001 at hotmail.com > To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org > Date: Wed, 10 Sep 2014 14:12:38 -0400 > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > > Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. > > If it would be installed at least up to a point. I would be able to do it.. > > I just dont know how to tell the compiler not to compile that part and go on.. > > > > > > -------------------------------------------------------------------------------- > From: kk6ecm at gmail.com > Date: Wed, 10 Sep 2014 09:15:13 -0700 > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > > Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. > > As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} > > Thanks, > Bob > kk6ecm > > Sent from iPad > > > On Sep 10, 2014, at 8:30 AM, pete M wrote: > > > OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? > If I did I am sorry.. And I gave my apology to every one I could have offended.. > But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. > Like just point me the pathway.. I will try to do it on my own.. > Thanks > On Sep 9, 2014, at 11:13 AM, pete M wrote: > > > I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. > > I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. > > > > From: kk6ecm > Sent: Tuesday, September 09, 2014 1:40 PM > To: APP RPT > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. > > Thanks, > Bob > kk6ecm > > Sent from iPad > > > On Sep 9, 2014, at 8:27 AM, pete M wrote: > > > Ok will try that.. > > thanks! > > > From: Bob > Sent: Tuesday, September 09, 2014 10:55 AM > To: 'APP RPT' > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I?ve done this several times without issue. Here are the steps I used. > > > > Load CentOS 5.10 downloaded from CentOS website > > No features, tools only, no desktop (competes with Asterisk) > > Set ssh /etc/ssh/sshd_config > > Run "setup" at comand line and disable firewall > > vi /etc/rc.d/acidrepo > > http://dl.allstarlink.org > > Execute portion of ks.cfg, each line at a time > > cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig > > cat <>/etc/rc.d/rc.local > > > > cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh > > > > chmod 755 /etc/rc.d/phase1.sh > > > > /etc/rc.d/phase1.sh > > Auto reboot after phase1.sh executed > > phase2.sh runs automatically to completion > > > > Bob > > kk6ecm > > > > > -------------------------------------------------------------------------- > > From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M > Sent: Tuesday, September 09, 2014 7:00 AM > To: APP RPT > Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > > > Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. > > > > I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. > > > > here is the out put from the script > > > > sh phase2.sh > > ****** Phase 2 post install ****** > > Getting asterisk install script from http://dl.allstarlink.org../. > > Getting files.tar.gz from http://dl.allstarlink.org../. > > ****** Asterisk Installation ****** > > /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found > > Unpacking files.tar.gz... > > Compiling Zaptel... > > checking for gcc... gcc > > checking for C compiler default output file name... a.out > > checking whether the C compiler works... yes > > checking whether we are cross compiling... no > > checking for suffix of executables... > > checking for suffix of object files... o > > checking whether we are using the GNU C compiler... yes > > checking whether gcc accepts -g... yes > > checking for gcc option to accept ISO C89... none needed > > checking how to run the C preprocessor... gcc -E > > checking for a BSD-compatible install... /usr/bin/install -c > > checking whether ln -s works... yes > > checking for GNU make... make > > checking for grep... /bin/grep > > checking for sh... /bin/sh > > checking for ln... /bin/ln > > checking for wget... /usr/bin/wget > > checking for grep that handles long lines and -e... (cached) /bin/grep > > checking for egrep... /bin/grep -E > > checking for ANSI C header files... yes > > checking for sys/types.h... yes > > checking for sys/stat.h... yes > > checking for stdlib.h... yes > > checking for string.h... yes > > checking for memory.h... yes > > checking for strings.h... yes > > checking for inttypes.h... yes > > checking for stdint.h... yes > > checking for unistd.h... yes > > checking for initscr in -lcurses... no > > checking for initscr in -lncurses... no > > checking for newtBell in -lnewt... no > > checking for usb_init in -lusb... no > > configure: creating ./config.status > > config.status: creating build_tools/menuselect-deps > > config.status: creating makeopts > > config.status: creating build_tools/make_firmware_object > > configure: *** Zaptel build successfully configured *** > > make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > > checking build system type... i686-pc-linux-gnu > > checking host system type... i686-pc-linux-gnu > > checking for gcc... gcc > > checking for C compiler default output file name... a.out > > checking whether the C compiler works... yes > > checking whether we are cross compiling... no > > checking for suffix of executables... > > checking for suffix of object files... o > > checking whether we are using the GNU C compiler... yes > > checking whether gcc accepts -g... yes > > checking for gcc option to accept ANSI C... none needed > > checking for GNU make... make > > checking for asprintf... yes > > checking for getloadavg... yes > > checking for setenv... yes > > checking for strcasestr... yes > > checking for strndup... yes > > checking for strnlen... yes > > checking for strsep... yes > > checking for strtoq... yes > > checking for unsetenv... yes > > checking for vasprintf... yes > > checking how to run the C preprocessor... gcc -E > > checking for egrep... grep -E > > checking for ANSI C header files... yes > > checking for sys/types.h... yes > > checking for sys/stat.h... yes > > checking for stdlib.h... yes > > checking for string.h... yes > > checking for memory.h... yes > > checking for strings.h... yes > > checking for inttypes.h... yes > > checking for stdint.h... yes > > checking for unistd.h... yes > > checking for initscr in -lcurses... no > > checking for initscr in -lncurses... no > > checking for pkg-config... No > > configure: creating ./config.status > > config.status: creating makeopts > > config.status: creating autoconfig.h > > configure: configuring in mxml > > configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. > > checking for gcc... gcc > > checking for C compiler default output file name... a.out > > checking whether the C compiler works... yes > > checking whether we are cross compiling... no > > checking for suffix of executables... > > checking for suffix of object files... o > > checking whether we are using the GNU C compiler... yes > > checking whether gcc accepts -g... yes > > checking for gcc option to accept ANSI C... none needed > > checking for g++... no > > checking for c++... no > > checking for gpp... no > > checking for aCC... no > > checking for CC... no > > checking for cxx... no > > checking for cc++... no > > checking for cl... no > > checking for FCC... no > > checking for KCC... no > > checking for RCC... no > > checking for xlC_r... no > > checking for xlC... no > > checking whether we are using the GNU C++ compiler... no > > checking whether g++ accepts -g... no > > checking for a BSD-compatible install... /usr/bin/install -c > > checking for ranlib... ranlib > > checking for ar... /usr/bin/ar > > checking for cp... /bin/cp > > checking for ln... /bin/ln< /font> > > checking for mkdir... /bin/mkdir > > checking for nroff... /usr/bin/nroff > > checking for rm... /bin/rm > > checking for strdup... yes > > checking for vsnprintf... yes > > configure: creating ./config.status > > config.status: creating Makefile > > config.status: creating mxml.list > > config.status: creating mxml.pc > > config.status: creating config.h > > configure: Menuselect build configuration successfully completed > > make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > > make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > > make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > > gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c > > gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c > > gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c > > make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' > > gcc -O -Wall -c mxml-attr.c > > gcc -O -Wall -c mxml-entity.c > > gcc -O -Wall -c mxml-file.c > > gcc -O -Wall -c mxml-index.c > > gcc -O -Wall -c mxml-node.c > > gcc -O -Wall -c mxml-search.c > > gcc -O -Wall -c mxml-set.c > > gcc -O -Wall -c mxml-private.c > > gcc -O -Wall -c mxml-string.c > > /bin/rm -f libmxml.a > > /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o > > a - mxml-attr.o > > a - mxml-entity.o > > a - mxml-file.o > > a - mxml-index.o > > a - mxml-node.o > > a - mxml-search.o > > a - mxml-set.o > > a - mxml-private.o > > a - mxml-string.o > > ranlib libmxml.a > > make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' > > gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a > > make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > > make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > > Generating input for menuselect ... > > > > *********************************************************** > > The existing menuselect.makeopts file did not specify > > that 'zttool' should not be included. However, either some > > dependencies for this module were not found or a > > conflict exists. > > > > Either run 'make menuselect' or remove the existing > > menuselect.makeopts file to resolve this issue. > > *********************************************************** > > > > make: *** [menuselect.makeopts] Error 255 > > Failure: Unable to compile Zaptel 2 > > Fatal error: Unable to install Asterisk! > > [root at node rc.d]# > > > > I dont know where to go from there.. > > > > Anyone care to help a bit? > > > > > > > -------------------------------------------------------------------------- > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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. From lorentedford at gmail.com Thu Sep 11 17:11:41 2014 From: lorentedford at gmail.com (Loren Tedford) Date: Thu, 11 Sep 2014 12:11:41 -0500 Subject: [App_rpt-users] Ideas (Mobile App) Message-ID: Since allstar is pretty well accessible with sip clients i wonder how easy it would be to build a mobile app that we could use on both Iphones and Andriod based OS I know that this would involve alot of work probably however I think it would help out Allstar greatly especially if we were to compare it to Echolink where thats all the old timers talk about.. Echolink to them is just name recognition but just like Windows it has its flaws... This is only just an Idea if some one else has thought of this i apologize for stepping on anybody toes... I just know that to keep some project like this going requires pushing the edges of technology is good especially for long term.. I wish i knew enough about programming if i did i personally would love to help out but I am not that good when it comes down to that sort of things.. Anyway thanks for the help everyone on earlier projects Loren Tedford (KC9ZHV) Email: lorentedford at gmail.com http://www.lorentedford.com http://kc9zhv.lorentedford.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Thu Sep 11 17:15:14 2014 From: doug at crompton.com (Doug Crompton) Date: Thu, 11 Sep 2014 13:15:14 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: , , <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP>, , , , <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com>, , , , , , , , <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com>, , , , , Message-ID: Pete, I have done this so many times but unfortunately I never documented it. Here is a simple description. Get a distro and configure it like you normally would. Get ntpd running, network setup, etc. Download the acid code and the latest dahdi - I see it is 2.10.0 The last I used was 2.9.x but I suspect it will work the same. If not you could get the 2.9 version. http://www.asterisk.org/downloads/dahdi Apply the patch - info on how to do that is in the readme https://allstarlink.org/fixed-dahdi-patches.tar.gz Compile and install dahdi. Then compile and install asterisk Don't run any offsite updates. Configure it manually - not hard to do - and run. If you already have a configured system you can use those files from /etc.asterisk. BTW the BBB setup procedure and howto's at http://hamvoip.org describe how to do that very easily which would also apply here. The only caveat is the config files would be different to start with so some consideration has to be given to that. All that sounds easy but you undoubtedly will have some hiccups and things you will have to do to get it to work. It is impossible to document that as it would be different on the multitude of distros and kernel versions. I have compiled it on the latest Debian and Ubuntu. The real problem is OSS support which is required. Debian has it, Ubuntu does not. You have to recompile the kernel and add it back in. For that reason Ubuntu is not recommended as kernel versions can change with frequent updates. I guess the big question is do you really need to do this. I forget why you said you can't run a local system. In that case you could just install an acid release on a PC or maybe go with the BBB. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 12:08:04 -0400 well can you point me a few pointers on how to do so? Never patched some software before. From: Doug Crompton Sent: Thursday, September 11, 2014 11:03 AM To: pete M Cc: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I am not sure what you are saying when you comment.... "well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.." Did you mean "will" ?? The patches can be applied against the latest dahdi and it will compile on late kernels. The BBB is an example of that. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 09:42:08 -0400 well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.. I can run the system on bunch of disto.. Here is the list.. CentOS 5 32bit CentOS 5 64bit CentOS 6 32bit CentOS 6 64bit CentOS 7 64bit CentOS 7 64bit Minimal Debian 6 32bit Debian 6 64bit Debian 7 32bit Debian 7 32bit Minimal Debian 7 64bit Debian 7 64bit Minimal Fedora 17 32bit Fedora 17 64bit Fedora 19 32bit Fedora 19 64bit Starbound-Ubuntu 13.10 32bit SUSE 12.2 32bit SUSE 12.2 64bit Ubuntu 10.04 32bit Ubuntu 10.04 64bit Ubuntu 11.10 32bit Ubuntu 11.10 64bit Ubuntu 12.10 32bit Ubuntu 12.10 64bit Ubuntu 13.10 32bit Ubuntu 13.10 64bit Ubuntu 14.04 32bit Ubuntu 14.04 32bit Minimal Ubuntu 14.04 64bit Ubuntu 14.04 64bit Minimal So I have lots of choice But I was under the feeling that the best distro was centos 5 for acid.. (using the install script from the cd.. Unless you can point me in another direction.. From: Doug Crompton Sent: Wednesday, September 10, 2014 6:16 PM To: pete M Cc: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Pete, I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org Date: Wed, 10 Sep 2014 14:12:38 -0400 Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. If it would be installed at least up to a point. I would be able to do it.. I just dont know how to tell the compiler not to compile that part and go on.. From: kk6ecm at gmail.com Date: Wed, 10 Sep 2014 09:15:13 -0700 To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} Thanks, Bob kk6ecm Sent from iPad On Sep 10, 2014, at 8:30 AM, pete M wrote: OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? If I did I am sorry.. And I gave my apology to every one I could have offended.. But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. From: kk6ecm Sen t: Tuesday, September 09, 2014 1:40 PM To: APP RPT Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. Thanks, Bob kk6ecm Sent from iPad On Sep 9, 2014, at 8:27 AM, pete M wrote: Ok will try that.. thanks! From: Bob Sent: Tuesday, September 09, 2014 10:55 AM To: 'APP RPT' Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I?ve done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS website No features, tools only, no desktop (competes with Asterisk) Set ssh /etc/ssh/sshd_config Run "setup" at comand line and disable firewall vi /etc/rc.d/acidrepo http://dl.allstarlink.org Execute portion of ks.cfg, each line at a time cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig cat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.sh Auto reboot after phase1.sh executed phase2.sh runs automatically to completion Bob kk6ecm From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org../. Getting files.tar.gz from http://dl.allstarlink.org../. ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preproc esso r... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln< /font> checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wlEmoticon-winkingsmile[1].png Type: image/png Size: 1135 bytes Desc: not available URL: From doug at crompton.com Thu Sep 11 17:59:41 2014 From: doug at crompton.com (Doug Crompton) Date: Thu, 11 Sep 2014 13:59:41 -0400 Subject: [App_rpt-users] Ideas (Mobile App) In-Reply-To: References: Message-ID: Loren, There is a free iax application right now called zoiper which is available on both iphone and android and works into allstar. There is an example in the BBB iax.conf - I probably should do a howto on it. http://www.zoiper.com/en Setup an iax account in the app and in iax.conf. It uses *99 to key and # to unkey. It works and sounds pretty good but awkward to use compared to a radio handheld. If you have inbound IAX port forwarded you already are setup for using this with the appropriate configuration. Another option is to create a mobile Allstar node using something like the BBB with appropriate interface. Some of the new cars actually have wifi hotspots built in! 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Thu, 11 Sep 2014 12:11:41 -0500 From: lorentedford at gmail.com To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Ideas (Mobile App) Since allstar is pretty well accessible with sip clients i wonder how easy it would be to build a mobile app that we could use on both Iphones and Andriod based OS I know that this would involve alot of work probably however I think it would help out Allstar greatly especially if we were to compare it to Echolink where thats all the old timers talk about.. Echolink to them is just name recognition but just like Windows it has its flaws... This is only just an Idea if some one else has thought of this i apologize for stepping on anybody toes... I just know that to keep some project like this going requires pushing the edges of technology is good especially for long term.. I wish i knew enough about programming if i did i personally would love to help out but I am not that good when it comes down to that sort of things.. Anyway thanks for the help everyone on earlier projects Loren Tedford (KC9ZHV) Email: lorentedford at gmail.com http://www.lorentedford.com http://kc9zhv.lorentedford.com _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorentedford at gmail.com Thu Sep 11 19:59:46 2014 From: lorentedford at gmail.com (Loren Tedford) Date: Thu, 11 Sep 2014 14:59:46 -0500 Subject: [App_rpt-users] Ideas (Mobile App) In-Reply-To: References: Message-ID: What about a system that is similar to lets say Echolink in the ability to search and select what repeater you want to add to your quick list then use this to connect to the repeater through a web transceiver like setup kinda like an all in one type software.. If i understood what you were talking about this you would have to setup up repeater side individually for each user.. Loren Tedford (KC9ZHV) Email: lorentedford at gmail.com http://www.lorentedford.com http://kc9zhv.lorentedford.com On Thu, Sep 11, 2014 at 12:59 PM, Doug Crompton wrote: > Loren, > > There is a free iax application right now called zoiper which is > available on both iphone and android and works into allstar. There is an > example in the BBB iax.conf - I probably should do a howto on it. > > http://www.zoiper.com/en > > Setup an iax account in the app and in iax.conf. It uses *99 to key and # > to unkey. It works and sounds pretty good but awkward to use compared to a > radio handheld. > > If you have inbound IAX port forwarded you already are setup for using > this with the appropriate configuration. > > Another option is to create a mobile Allstar node using something like the > BBB with appropriate interface. Some of the new cars actually have wifi > hotspots built in! > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > Date: Thu, 11 Sep 2014 12:11:41 -0500 > From: lorentedford at gmail.com > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Ideas (Mobile App) > > > Since allstar is pretty well accessible with sip clients i wonder how easy > it would be to build a mobile app that we could use on both Iphones and > Andriod based OS I know that this would involve alot of work probably > however I think it would help out Allstar greatly especially if we were to > compare it to Echolink where thats all the old timers talk about.. Echolink > to them is just name recognition but just like Windows it has its flaws... > This is only just an Idea if some one else has thought of this i apologize > for stepping on anybody toes... I just know that to keep some project like > this going requires pushing the edges of technology is good especially for > long term.. > > > I wish i knew enough about programming if i did i personally would love to > help out but I am not that good when it comes down to that sort of things.. > > Anyway thanks for the help everyone on earlier projects > > Loren Tedford (KC9ZHV) > Email: lorentedford at gmail.com > > http://www.lorentedford.com > http://kc9zhv.lorentedford.com > > > _______________________________________________ App_rpt-users mailing list > App_rpt-users at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From electricity440 at gmail.com Thu Sep 11 21:05:04 2014 From: electricity440 at gmail.com (Skyler F) Date: Thu, 11 Sep 2014 15:05:04 -0600 Subject: [App_rpt-users] Where is the echolink "text greeting" Page Message-ID: When I connect from an echolink client capable of veiwing the text, it says "Welcome to Allstar node *x* Echo-link node *y* Number *z* Stations connected" I really like all of that stuff how it is, I just want to add some text on top of it. Does anybody know where the file is? On another subject is there a way to transmit a greeting when someone connects to the connecting station, but not anywhere else? (be it allstar or echolink) For example, I have 2 nodes connected. When the third one connects, a greeting is played to the third node, but not anybody else (not on the local repeater or to any of the two nodes already connected) *73* *Skyler KD?WHB* -- Skyler Fennell amsatnet.info KD?WHB electricity440 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike at midnighteng.com Thu Sep 11 21:07:56 2014 From: mike at midnighteng.com (mike at midnighteng.com) Date: Thu, 11 Sep 2014 14:07:56 -0700 Subject: [App_rpt-users] =?utf-8?q?Ideas_=28Mobile_App=29?= Message-ID: <20140911140756.71befee5dbd13c5325dd1a521b4e73ee.ad7cb9f92a.wbe@email06.secureserver.net> An HTML attachment was scrubbed... URL: From kb4fxc at inttek.net Thu Sep 11 21:23:23 2014 From: kb4fxc at inttek.net (David McGough) Date: Thu, 11 Sep 2014 17:23:23 -0400 (EDT) Subject: [App_rpt-users] Where is the echolink "text greeting" Page In-Reply-To: Message-ID: Skyler, The "Welcome" text, etc., is hard-coded in the chan_echolink.c driver. Currently, you would need to modify the driver source code and re-compile to change or add extra text, etc. Also, I'm not aware of any direct way to send a audio clip only to echolink (like immediately after someone connects), currently. 73, David KB4FXC On Thu, 11 Sep 2014, Skyler F wrote: > When I connect from an echolink client capable of veiwing the text, it says > > "Welcome to Allstar node *x* > Echo-link node *y* > Number *z* > > Stations connected" > > I really like all of that stuff how it is, I just want to add some text on > top of it. Does anybody know where the file is? > > On another subject is there a way to transmit a greeting when someone > connects to the connecting station, but not anywhere else? (be it allstar > or echolink) > > For example, I have 2 nodes connected. When the third one connects, a > greeting is played to the third node, but not anybody else (not on the > local repeater or to any of the two nodes already connected) > > *73* > *Skyler KD??WHB* > > > From electricity440 at gmail.com Thu Sep 11 21:46:20 2014 From: electricity440 at gmail.com (Skyler F) Date: Thu, 11 Sep 2014 15:46:20 -0600 Subject: [App_rpt-users] Where is the echolink "text greeting" Page In-Reply-To: References: Message-ID: Not that I care that much to go to the source code and modify that, but I am new to programming etc. and wondering how I would do it. I assume the .c file is C++ or something, so where can i find the source file that I can then recompile and load it back onto my node computer? On Thu, Sep 11, 2014 at 3:23 PM, David McGough wrote: > > Skyler, > > The "Welcome" text, etc., is hard-coded in the chan_echolink.c driver. > Currently, you would need to modify the driver source code and re-compile > to change or add extra text, etc. > > Also, I'm not aware of any direct way to send a audio clip only to > echolink (like immediately after someone connects), currently. > > > 73, David KB4FXC > > > On Thu, 11 Sep 2014, Skyler F wrote: > > > When I connect from an echolink client capable of veiwing the text, it > says > > > > "Welcome to Allstar node *x* > > Echo-link node *y* > > Number *z* > > > > Stations connected" > > > > I really like all of that stuff how it is, I just want to add some text > on > > top of it. Does anybody know where the file is? > > > > On another subject is there a way to transmit a greeting when someone > > connects to the connecting station, but not anywhere else? (be it allstar > > or echolink) > > > > For example, I have 2 nodes connected. When the third one connects, a > > greeting is played to the third node, but not anybody else (not on the > > local repeater or to any of the two nodes already connected) > > > > *73* > > *Skyler KD?WHB* > > > > > > > > -- Skyler Fennell amsatnet.info KD?WHB electricity440 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Fri Sep 12 01:25:02 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Thu, 11 Sep 2014 18:25:02 -0700 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com> <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com> Message-ID: <45B85E05-5E1D-44B0-8849-41CAFC8F659B@mac.com> I?ve been doing this too with one difference, using Asterisk 1.6 rather than the ACID version. Compiles pretty much the same but requires a couple of extra tweaks to the config files as the syntax has a couple of minor differences. Asterisk 1.6 cleans up a few noticeable CLI outputs and (I assume) other bug fixes. -- Tim WD6AWP > On Sep 11, 2014, at 10:15 AM, Doug Crompton wrote: > > Pete, > > I have done this so many times but unfortunately I never documented it. Here is a simple description. > > Get a distro and configure it like you normally would. Get ntpd running, network setup, etc. > > Download the acid code and the latest dahdi - > > I see it is 2.10.0 The last I used was 2.9.x but I suspect it will work the same. If not you could get the 2.9 version. > > http://www.asterisk.org/downloads/dahdi > > Apply the patch - info on how to do that is in the readme > > https://allstarlink.org/fixed-dahdi-patches.tar.gz > > Compile and install dahdi. > > Then compile and install asterisk > > Don't run any offsite updates. Configure it manually - not hard to do - and run. If you already have a configured system you can use those files from /etc.asterisk. BTW the BBB setup procedure and howto's at http://hamvoip.org describe how to do that very easily which would also apply here. The only caveat is the config files would be different to start with so some consideration has to be given to that. > > All that sounds easy but you undoubtedly will have some hiccups and things you will have to do to get it to work. It is impossible to document that as it would be different on the multitude of distros and kernel versions. > > I have compiled it on the latest Debian and Ubuntu. The real problem is OSS support which is required. Debian has it, Ubuntu does not. You have to recompile the kernel and add it back in. For that reason Ubuntu is not recommended as kernel versions can change with frequent updates. > > I guess the big question is do you really need to do this. I forget why you said you can't run a local system. In that case you could just install an acid release on a PC or maybe go with the BBB. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: petem001 at hotmail.com > To: doug at crompton.com > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > Date: Thu, 11 Sep 2014 12:08:04 -0400 > > well can you point me a few pointers on how to do so? > > Never patched some software before. > > > From: Doug Crompton > Sent: Thursday, September 11, 2014 11:03 AM > To: pete M > Cc: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I am not sure what you are saying when you comment.... > > "well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.." > > Did you mean "will" ?? The patches can be applied against the latest dahdi and it will compile on late kernels. The BBB is an example of that. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: petem001 at hotmail.com > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > Date: Thu, 11 Sep 2014 09:42:08 -0400 > > well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.. > > I can run the system on bunch of disto.. > > Here is the list.. > > > CentOS 5 32bit > CentOS 5 64bit > CentOS 6 32bit > CentOS 6 64bit > CentOS 7 64bit > CentOS 7 64bit Minimal > Debian 6 32bit > Debian 6 64bit > Debian 7 32bit > Debian 7 32bit Minimal > Debian 7 64bit > Debian 7 64bit Minimal > Fedora 17 32bit > Fedora 17 64bit > Fedora 19 32bit > Fedora 19 64bit > Starbound-Ubuntu 13.10 32bit > SUSE 12.2 32bit > SUSE 12.2 64bit > Ubuntu 10.04 32bit > Ubuntu 10.04 64bit > Ubuntu 11.10 32bit > Ubuntu 11.10 64bit > Ubuntu 12.10 32bit > Ubuntu 12.10 64bit > Ubuntu 13.10 32bit > Ubuntu 13.10 64bit > Ubuntu 14.04 32bit > Ubuntu 14.04 32bit Minimal > Ubuntu 14.04 64bit > Ubuntu 14.04 64bit Minimal > > So I have lots of choice > > But I was under the feeling that the best distro was centos 5 for acid.. (using the install script from the cd.. > > Unless you can point me in another direction.. > > > From: Doug Crompton > Sent: Wednesday, September 10, 2014 6:16 PM > To: pete M > Cc: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Pete, > > I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: petem001 at hotmail.com > To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org > Date: Wed, 10 Sep 2014 14:12:38 -0400 > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. > > If it would be installed at least up to a point. I would be able to do it.. > > I just dont know how to tell the compiler not to compile that part and go on.. > > > > From: kk6ecm at gmail.com > Date: Wed, 10 Sep 2014 09:15:13 -0700 > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. > > As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} > > Thanks, > Bob > kk6ecm > > Sent from iPad > > > On Sep 10, 2014, at 8:30 AM, pete M > wrote: > > OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? > > If I did I am sorry.. And I gave my apology to every one I could have offended.. > But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M > wrote: > > I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. > > I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. > > > > From: kk6ecm > Sen t: Tuesday, September 09, 2014 1:40 PM > To: APP RPT > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. > > Thanks, > Bob > kk6ecm > > Sent from iPad > > > On Sep 9, 2014, at 8:27 AM, pete M > wrote: > > Ok will try that.. > > thanks! > > > From: Bob > Sent: Tuesday, September 09, 2014 10:55 AM > To: 'APP RPT' > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I?ve done this several times without issue. Here are the steps I used. > > Load CentOS 5.10 downloaded from CentOS website > No features, tools only, no desktop (competes with Asterisk) > Set ssh /etc/ssh/sshd_config > Run "setup" at comand line and disable firewall > vi /etc/rc.d/acidrepo > http://dl.allstarlink.org > Execute portion of ks.cfg, each line at a time > cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig > cat <>/etc/rc.d/rc.local > > cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh > > chmod 755 /etc/rc.d/phase1.sh > > /etc/rc.d/phase1.sh > Auto reboot after phase1.sh executed > phase2.sh runs automatically to completion > > Bob > kk6ecm > > From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org ] On Behalf Of pete M > Sent: Tuesday, September 09, 2014 7:00 AM > To: APP RPT > Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. > > I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. > > here is the out put from the script > > sh phase2.sh > ****** Phase 2 post install ****** > Getting asterisk install script from http://dl.allstarlink.org../ . > Getting files.tar.gz from http://dl.allstarlink.org../ . > ****** Asterisk Installation ****** > /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found > Unpacking files.tar.gz... > Compiling Zaptel... > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking how to run the C preproc esso r... gcc -E > checking for a BSD-compatible install... /usr/bin/install -c > checking whether ln -s works... yes > checking for GNU make... make > checking for grep... /bin/grep > checking for sh... /bin/sh > checking for ln... /bin/ln > checking for wget... /usr/bin/wget > checking for grep that handles long lines and -e... (cached) /bin/grep > checking for egrep... /bin/grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for initscr in -lcurses... no > checking for initscr in -lncurses... no > checking for newtBell in -lnewt... no > checking for usb_init in -lusb... no > configure: creating ./config.status > config.status: creating build_tools/menuselect-deps > config.status: creating makeopts > config.status: creating build_tools/make_firmware_object > configure: *** Zaptel build successfully configured *** > make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking for GNU make... make > checking for asprintf... yes > checking for getloadavg... yes > checking for setenv... yes > checking for strcasestr... yes > checking for strndup... yes > checking for strnlen... yes > checking for strsep... yes > checking for strtoq... yes > checking for unsetenv... yes > checking for vasprintf... yes > checking how to run the C preprocessor... gcc -E > checking for egrep... grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for initscr in -lcurses... no > checking for initscr in -lncurses... no > checking for pkg-config... No > configure: creating ./config.status > config.status: creating makeopts > config.status: creating autoconfig.h > configure: configuring in mxml > configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking for g++... no > checking for c++... no > checking for gpp... no > checking for aCC... no > checking for CC... no > checking for cxx... no > checking for cc++... no > checking for cl... no > checking for FCC... no > checking for KCC... no > checking for RCC... no > checking for xlC_r... no > checking for xlC... no > checking whether we are using the GNU C++ compiler... no > checking whether g++ accepts -g... no > checking for a BSD-compatible install... /usr/bin/install -c > checking for ranlib... ranlib > checking for ar... /usr/bin/ar > checking for cp... /bin/cp > checking for ln... /bin/ln< /font> > checking for mkdir... /bin/mkdir > checking for nroff... /usr/bin/nroff > checking for rm... /bin/rm > checking for strdup... yes > checking for vsnprintf... yes > configure: creating ./config.status > config.status: creating Makefile > config.status: creating mxml.list > config.status: creating mxml.pc > config.status: creating config.h > configure: Menuselect build configuration successfully completed > make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c > gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c > gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c > make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' > gcc -O -Wall -c mxml-attr.c > gcc -O -Wall -c mxml-entity.c > gcc -O -Wall -c mxml-file.c > gcc -O -Wall -c mxml-index.c > gcc -O -Wall -c mxml-node.c > gcc -O -Wall -c mxml-search.c > gcc -O -Wall -c mxml-set.c > gcc -O -Wall -c mxml-private.c > gcc -O -Wall -c mxml-string.c > /bin/rm -f libmxml.a > /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o > a - mxml-attr.o > a - mxml-entity.o > a - mxml-file.o > a - mxml-index.o > a - mxml-node.o > a - mxml-search.o > a - mxml-set.o > a - mxml-private.o > a - mxml-string.o > ranlib libmxml.a > make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' > gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a > make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > Generating input for menuselect ... > > *********************************************************** > The existing menuselect.makeopts file did not specify > that 'zttool' should not be included. However, either some > dependencies for this module were not found or a > conflict exists. > > Either run 'make menuselect' or remove the existing > menuselect.makeopts file to resolve this issue. > *********************************************************** > > make: *** [menuselect.makeopts] Error 255 > Failure: Unable to compile Zaptel 2 > Fatal error: Unable to install Asterisk! > [root at node rc.d]# > > I dont know where to go from there.. > > Anyone care to help a bit? > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at dyb.com Fri Sep 12 01:53:26 2014 From: george at dyb.com (George Csahanin) Date: Thu, 11 Sep 2014 20:53:26 -0500 Subject: [App_rpt-users] What is Dahdi? Message-ID: <4EF59EB0324F4C8F9F8EBCBABE791805@georgecPC> OK, not being a wise-ass, not trying to be stupid, that part?s covered. Just trying to understand. What are the specific functions of: Dahdi Asterisk Libpri Zaptel I know they are all part of the whole package, and that whole package still has me in awe. But being very curious type I wanted to know how this all comes together. In my simple mind I axe: why isn?t Asterisk enough? I know what that one is, but as I use app_rpt daily I wish I knew which of the above are providing what part of the overall system. George J Csahanin W2DB Allstar 2360 Echolink-Free Cedar Park, TX 512-401-2630 home 401-338-0568 cel -------------- next part -------------- An HTML attachment was scrubbed... URL: From petem001 at hotmail.com Fri Sep 12 02:19:19 2014 From: petem001 at hotmail.com (pete M) Date: Thu, 11 Sep 2014 22:19:19 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: , , <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP>, , , , <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com>, , , , , , , , <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com>, , , , , , Message-ID: OK Doug you got me fired up.. just one thing to know what source of asterisk are you using exactly? Got Dahdi got the patch.. will fix what's needed to be fixed about ntpd and all. But what damn source of asterisk are you using? ;-) From: doug at crompton.com To: petem001 at hotmail.com CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 13:15:14 -0400 Pete, I have done this so many times but unfortunately I never documented it. Here is a simple description. Get a distro and configure it like you normally would. Get ntpd running, network setup, etc. Download the acid code and the latest dahdi - I see it is 2.10.0 The last I used was 2.9.x but I suspect it will work the same. If not you could get the 2.9 version. http://www.asterisk.org/downloads/dahdi Apply the patch - info on how to do that is in the readme https://allstarlink.org/fixed-dahdi-patches.tar.gz Compile and install dahdi. Then compile and install asterisk Don't run any offsite updates. Configure it manually - not hard to do - and run. If you already have a configured system you can use those files from /etc.asterisk. BTW the BBB setup procedure and howto's at http://hamvoip.org describe how to do that very easily which would also apply here. The only caveat is the config files would be different to start with so some consideration has to be given to that. All that sounds easy but you undoubtedly will have some hiccups and things you will have to do to get it to work. It is impossible to document that as it would be different on the multitude of distros and kernel versions. I have compiled it on the latest Debian and Ubuntu. The real problem is OSS support which is required. Debian has it, Ubuntu does not. You have to recompile the kernel and add it back in. For that reason Ubuntu is not recommended as kernel versions can change with frequent updates. I guess the big question is do you really need to do this. I forget why you said you can't run a local system. In that case you could just install an acid release on a PC or maybe go with the BBB. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 12:08:04 -0400 well can you point me a few pointers on how to do so? Never patched some software before. From: Doug Crompton Sent: Thursday, September 11, 2014 11:03 AM To: pete M Cc: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I am not sure what you are saying when you comment.... "well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.." Did you mean "will" ?? The patches can be applied against the latest dahdi and it will compile on late kernels. The BBB is an example of that. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 09:42:08 -0400 well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.. I can run the system on bunch of disto.. Here is the list.. CentOS 5 32bit CentOS 5 64bit CentOS 6 32bit CentOS 6 64bit CentOS 7 64bit CentOS 7 64bit Minimal Debian 6 32bit Debian 6 64bit Debian 7 32bit Debian 7 32bit Minimal Debian 7 64bit Debian 7 64bit Minimal Fedora 17 32bit Fedora 17 64bit Fedora 19 32bit Fedora 19 64bit Starbound-Ubuntu 13.10 32bit SUSE 12.2 32bit SUSE 12.2 64bit Ubuntu 10.04 32bit Ubuntu 10.04 64bit Ubuntu 11.10 32bit Ubuntu 11.10 64bit Ubuntu 12.10 32bit Ubuntu 12.10 64bit Ubuntu 13.10 32bit Ubuntu 13.10 64bit Ubuntu 14.04 32bit Ubuntu 14.04 32bit Minimal Ubuntu 14.04 64bit Ubuntu 14.04 64bit Minimal So I have lots of choice But I was under the feeling that the best distro was centos 5 for acid.. (using the install script from the cd.. Unless you can point me in another direction.. From: Doug Crompton Sent: Wednesday, September 10, 2014 6:16 PM To: pete M Cc: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Pete, I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org Date: Wed, 10 Sep 2014 14:12:38 -0400 Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. If it would be installed at least up to a point. I would be able to do it.. I just dont know how to tell the compiler not to compile that part and go on.. From: kk6ecm at gmail.com Date: Wed, 10 Sep 2014 09:15:13 -0700 To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} Thanks, Bob kk6ecm Sent from iPad On Sep 10, 2014, at 8:30 AM, pete M wrote: OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? If I did I am sorry.. And I gave my apology to every one I could have offended.. But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. From: kk6ecm Sen t: Tuesday, September 09, 2014 1:40 PM To: APP RPT Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. Thanks, Bob kk6ecm Sent from iPad On Sep 9, 2014, at 8:27 AM, pete M wrote: Ok will try that.. thanks! From: Bob Sent: Tuesday, September 09, 2014 10:55 AM To: 'APP RPT' Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I?ve done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS website No features, tools only, no desktop (competes with Asterisk) Set ssh /etc/ssh/sshd_config Run "setup" at comand line and disable firewall vi /etc/rc.d/acidrepo http://dl.allstarlink.org Execute portion of ks.cfg, each line at a time cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig cat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.sh Auto reboot after phase1.sh executed phase2.sh runs automatically to completion Bob kk6ecm From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org../. Getting files.tar.gz from http://dl.allstarlink.org../. ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preproc esso r... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln< /font> checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wlEmoticon-winkingsmile[1].png Type: image/png Size: 1135 bytes Desc: not available URL: From doug at crompton.com Fri Sep 12 02:39:52 2014 From: doug at crompton.com (Doug Crompton) Date: Thu, 11 Sep 2014 22:39:52 -0400 Subject: [App_rpt-users] What is Dahdi? In-Reply-To: <4EF59EB0324F4C8F9F8EBCBABE791805@georgecPC> References: <4EF59EB0324F4C8F9F8EBCBABE791805@georgecPC> Message-ID: This will explain it.... http://www.voip-info.org/wiki/view/DAHDI http://blogs.digium.com/2008/05/19/zaptel-project-being-renamed-to-dahdi/ 73 Doug WA3DSP http://www.crompton.com/hamradio From: george at dyb.com To: App_rpt-users at ohnosec.org Date: Thu, 11 Sep 2014 20:53:26 -0500 Subject: [App_rpt-users] What is Dahdi? OK, not being a wise-ass, not trying to be stupid, that part?s covered. Just trying to understand. What are the specific functions of: Dahdi Asterisk Libpri Zaptel I know they are all part of the whole package, and that whole package still has me in awe. But being very curious type I wanted to know how this all comes together. In my simple mind I axe: why isn?t Asterisk enough? I know what that one is, but as I use app_rpt daily I wish I knew which of the above are providing what part of the overall system. George J Csahanin W2DB Allstar 2360 Echolink-Free Cedar Park, TX 512-401-2630 home 401-338-0568 cel _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Fri Sep 12 02:44:16 2014 From: Bryan at bryanfields.net (Bryan Fields) Date: Thu, 11 Sep 2014 22:44:16 -0400 Subject: [App_rpt-users] What is Dahdi? In-Reply-To: References: <4EF59EB0324F4C8F9F8EBCBABE791805@georgecPC> Message-ID: <54125E00.7010700@bryanfields.net> On 9/11/14, 10:39 PM, Doug Crompton wrote: > This will explain it.... > http://blogs.digium.com/2008/05/19/zaptel-project-being-renamed-to-dahdi/ The first comment on that blog post is perfect. -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net From kk6ecm at gmail.com Fri Sep 12 02:51:41 2014 From: kk6ecm at gmail.com (Bob) Date: Thu, 11 Sep 2014 19:51:41 -0700 Subject: [App_rpt-users] What is Dahdi? In-Reply-To: <4EF59EB0324F4C8F9F8EBCBABE791805@georgecPC> References: <4EF59EB0324F4C8F9F8EBCBABE791805@georgecPC> Message-ID: This is what I understand... but looking for an expert view from someone else. Dahdi - Asterisk & hardware device interface Asterisk - telephony switching and PBX service Libpri - protocols used by Asterisk/Dahdi? Zaptel - interface functionally similar to, and predating Dahdi? Bob kk6ecm _____ From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of George Csahanin Sent: Thursday, September 11, 2014 6:53 PM To: App_rpt-users at ohnosec.org Subject: [App_rpt-users] What is Dahdi? OK, not being a wise-ass, not trying to be stupid, that part's covered. Just trying to understand. What are the specific functions of: Dahdi - Asterisk & hardware device interface Asterisk - telephony switching and PBX service Libpri - protocols used by Asterisk/Dahdi? Zaptel - interface functionally similar to, and predating Dahdi? I know they are all part of the whole package, and that whole package still has me in awe. But being very curious type I wanted to know how this all comes together. In my simple mind I axe: why isn't Asterisk enough? I know what that one is, but as I use app_rpt daily I wish I knew which of the above are providing what part of the overall system. George J Csahanin W2DB Allstar 2360 Echolink-Free Cedar Park, TX 512-401-2630 home 401-338-0568 cel -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Fri Sep 12 02:54:13 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Thu, 11 Sep 2014 19:54:13 -0700 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com> <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com> Message-ID: I use this Asterisk source: http://svn.asterisk.org/svn/asterisk/branches/1.6.2/ and pull app_rpt source out of http://x.allstarlink.org/svn-trunk.tar.gz You?ll need libpri and a bunch of other stuff I?ll leave for you to work out on your own. -- Tim :wq On Sep 11, 2014, at 7:19 PM, pete M wrote: > OK Doug you got me fired up.. > > just one thing to know what source of asterisk are you using exactly? > > Got Dahdi got the patch.. will fix what's needed to be fixed about ntpd and all. But what damn source of asterisk are you using? ;-) > > > > > From: doug at crompton.com > To: petem001 at hotmail.com > CC: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > Date: Thu, 11 Sep 2014 13:15:14 -0400 > > Pete, > > I have done this so many times but unfortunately I never documented it. Here is a simple description. > > Get a distro and configure it like you normally would. Get ntpd running, network setup, etc. > > Download the acid code and the latest dahdi - > > I see it is 2.10.0 The last I used was 2.9.x but I suspect it will work the same. If not you could get the 2.9 version. > > http://www.asterisk.org/downloads/dahdi > > Apply the patch - info on how to do that is in the readme > > https://allstarlink.org/fixed-dahdi-patches.tar.gz > > Compile and install dahdi. > > Then compile and install asterisk > > Don't run any offsite updates. Configure it manually - not hard to do - and run. If you already have a configured system you can use those files from /etc.asterisk. BTW the BBB setup procedure and howto's at http://hamvoip.org describe how to do that very easily which would also apply here. The only caveat is the config files would be different to start with so some consideration has to be given to that. > > All that sounds easy but you undoubtedly will have some hiccups and things you will have to do to get it to work. It is impossible to document that as it would be different on the multitude of distros and kernel versions. > > I have compiled it on the latest Debian and Ubuntu. The real problem is OSS support which is required. Debian has it, Ubuntu does not. You have to recompile the kernel and add it back in. For that reason Ubuntu is not recommended as kernel versions can change with frequent updates. > > I guess the big question is do you really need to do this. I forget why you said you can't run a local system. In that case you could just install an acid release on a PC or maybe go with the BBB. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: petem001 at hotmail.com > To: doug at crompton.com > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > Date: Thu, 11 Sep 2014 12:08:04 -0400 > > well can you point me a few pointers on how to do so? > > Never patched some software before. > > > From: Doug Crompton > Sent: Thursday, September 11, 2014 11:03 AM > To: pete M > Cc: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I am not sure what you are saying when you comment.... > > "well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.." > > Did you mean "will" ?? The patches can be applied against the latest dahdi and it will compile on late kernels. The BBB is an example of that. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: petem001 at hotmail.com > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > Date: Thu, 11 Sep 2014 09:42:08 -0400 > > well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.. > > I can run the system on bunch of disto.. > > Here is the list.. > > > CentOS 5 32bit > CentOS 5 64bit > CentOS 6 32bit > CentOS 6 64bit > CentOS 7 64bit > CentOS 7 64bit Minimal > Debian 6 32bit > Debian 6 64bit > Debian 7 32bit > Debian 7 32bit Minimal > Debian 7 64bit > Debian 7 64bit Minimal > Fedora 17 32bit > Fedora 17 64bit > Fedora 19 32bit > Fedora 19 64bit > Starbound-Ubuntu 13.10 32bit > SUSE 12.2 32bit > SUSE 12.2 64bit > Ubuntu 10.04 32bit > Ubuntu 10.04 64bit > Ubuntu 11.10 32bit > Ubuntu 11.10 64bit > Ubuntu 12.10 32bit > Ubuntu 12.10 64bit > Ubuntu 13.10 32bit > Ubuntu 13.10 64bit > Ubuntu 14.04 32bit > Ubuntu 14.04 32bit Minimal > Ubuntu 14.04 64bit > Ubuntu 14.04 64bit Minimal > > So I have lots of choice > > But I was under the feeling that the best distro was centos 5 for acid.. (using the install script from the cd.. > > Unless you can point me in another direction.. > > > From: Doug Crompton > Sent: Wednesday, September 10, 2014 6:16 PM > To: pete M > Cc: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Pete, > > I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: petem001 at hotmail.com > To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org > Date: Wed, 10 Sep 2014 14:12:38 -0400 > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. > > If it would be installed at least up to a point. I would be able to do it.. > > I just dont know how to tell the compiler not to compile that part and go on.. > > > > From: kk6ecm at gmail.com > Date: Wed, 10 Sep 2014 09:15:13 -0700 > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. > > As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} > > Thanks, > Bob > kk6ecm > > Sent from iPad > > > On Sep 10, 2014, at 8:30 AM, pete M wrote: > > OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? If I did I am sorry.. And I gave my apology to every one I could have offended.. But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: > > I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. > > I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. > > > > From: kk6ecm > Sen t: Tuesday, September 09, 2014 1:40 PM > To: APP RPT > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. > > Thanks, > Bob > kk6ecm > > Sent from iPad > > > On Sep 9, 2014, at 8:27 AM, pete M wrote: > > Ok will try that.. > > thanks! > > > From: Bob > Sent: Tuesday, September 09, 2014 10:55 AM > To: 'APP RPT' > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I?ve done this several times without issue. Here are the steps I used. > > Load CentOS 5.10 downloaded from CentOS website > No features, tools only, no desktop (competes with Asterisk) > Set ssh /etc/ssh/sshd_config > Run "setup" at comand line and disable firewall > vi /etc/rc.d/acidrepo > http://dl.allstarlink.org > Execute portion of ks.cfg, each line at a time > cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig > cat <>/etc/rc.d/rc.local > > cd /etc/rc.d; rm -f phase1.sh; wget -qhttp://dl.allstarlink.org/installcd/phase1.sh > > chmod 755 /etc/rc.d/phase1.sh > > /etc/rc.d/phase1.sh > Auto reboot after phase1.sh executed > phase2.sh runs automatically to completion > > Bob > kk6ecm > > From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M > Sent: Tuesday, September 09, 2014 7:00 AM > To: APP RPT > Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. > > I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. > > here is the out put from the script > > sh phase2.sh > ****** Phase 2 post install ****** > Getting asterisk install script from http://dl.allstarlink.org../. > Getting files.tar.gz from http://dl.allstarlink.org../. > ****** Asterisk Installation ****** > /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found > Unpacking files.tar.gz... > Compiling Zaptel... > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking how to run the C preproc esso r... gcc -E > checking for a BSD-compatible install... /usr/bin/install -c > checking whether ln -s works... yes > checking for GNU make... make > checking for grep... /bin/grep > checking for sh... /bin/sh > checking for ln... /bin/ln > checking for wget... /usr/bin/wget > checking for grep that handles long lines and -e... (cached) /bin/grep > checking for egrep... /bin/grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for initscr in -lcurses... no > checking for initscr in -lncurses... no > checking for newtBell in -lnewt... no > checking for usb_init in -lusb... no > configure: creating ./config.status > config.status: creating build_tools/menuselect-deps > config.status: creating makeopts > config.status: creating build_tools/make_firmware_object > configure: *** Zaptel build successfully configured *** > make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking for GNU make... make > checking for asprintf... yes > checking for getloadavg... yes > checking for setenv... yes > checking for strcasestr... yes > checking for strndup... yes > checking for strnlen... yes > checking for strsep... yes > checking for strtoq... yes > checking for unsetenv... yes > checking for vasprintf... yes > checking how to run the C preprocessor... gcc -E > checking for egrep... grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for initscr in -lcurses... no > checking for initscr in -lncurses... no > checking for pkg-config... No > configure: creating ./config.status > config.status: creating makeopts > config.status: creating autoconfig.h > configure: configuring in mxml > configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking for g++... no > checking for c++... no > checking for gpp... no > checking for aCC... no > checking for CC... no > checking for cxx... no > checking for cc++... no > checking for cl... no > checking for FCC... no > checking for KCC... no > checking for RCC... no > checking for xlC_r... no > checking for xlC... no > checking whether we are using the GNU C++ compiler... no > checking whether g++ accepts -g... no > checking for a BSD-compatible install... /usr/bin/install -c > checking for ranlib... ranlib > checking for ar... /usr/bin/ar > checking for cp... /bin/cp > checking for ln... /bin/ln< /font> > checking for mkdir... /bin/mkdir > checking for nroff... /usr/bin/nroff > checking for rm... /bin/rm > checking for strdup... yes > checking for vsnprintf... yes > configure: creating ./config.status > config.status: creating Makefile > config.status: creating mxml.list > config.status: creating mxml.pc > config.status: creating config.h > configure: Menuselect build configuration successfully completed > make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c > gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c > gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c > make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' > gcc -O -Wall -c mxml-attr.c > gcc -O -Wall -c mxml-entity.c > gcc -O -Wall -c mxml-file.c > gcc -O -Wall -c mxml-index.c > gcc -O -Wall -c mxml-node.c > gcc -O -Wall -c mxml-search.c > gcc -O -Wall -c mxml-set.c > gcc -O -Wall -c mxml-private.c > gcc -O -Wall -c mxml-string.c > /bin/rm -f libmxml.a > /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o > a - mxml-attr.o > a - mxml-entity.o > a - mxml-file.o > a - mxml-index.o > a - mxml-node.o > a - mxml-search.o > a - mxml-set.o > a - mxml-private.o > a - mxml-string.o > ranlib libmxml.a > make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' > gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a > make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > Generating input for menuselect ... > > *********************************************************** > The existing menuselect.makeopts file did not specify > that 'zttool' should not be included. However, either some > dependencies for this module were not found or a > conflict exists. > > Either run 'make menuselect' or remove the existing > menuselect.makeopts file to resolve this issue. > *********************************************************** > > make: *** [menuselect.makeopts] Error 255 > Failure: Unable to compile Zaptel 2 > Fatal error: Unable to install Asterisk! > [root at node rc.d]# > > I dont know where to go from there.. > > Anyone care to help a bit? > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Fri Sep 12 03:49:25 2014 From: doug at crompton.com (Doug Crompton) Date: Thu, 11 Sep 2014 23:49:25 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: , , <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP>, , , , <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com>, , , , , , , , <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com>, , , , , , , Message-ID: First of all remind me - what is your end goal here. Are you doing this just for fun or is it for a real need and if so what is the need? The easiest thing to do might be to just download the BBB image at hamvoip.org. Write it to an SD card, mount it on Linux - ubuntu or whatever works. The root partition not the boot partition. Copy from everything from the mount point /usr/src/utils to /usr/src on your linux box. Also copy /etc/asterisk from the mount point to /etc/asterisk for all the config files. The source tree would then be in /usr/src/utils/asterisk - dahdi would also be there along with the patches in /usr/src/utils You can compile and intall both dahdi and asterisk from there. Then following the directions on the BBB page and howto on setting up your node. Another possible choice would be to just bring up a standard centos installation on a PC and copy what you need from there. All the source and files you would need would be there like the scripts in /usr/local/sbin. You would need to make some changes however. As Dave pointed out earlier you are in for some real bumps along the way. There will be packages you will need to download and things you will need to configure. It is not a 123 type of thing. Without some Linux experience it could be daunting. Just remember if you are using dahdi you need to remove any mention of zaptel and use the chan_dahdi.conf as shown in the BBB config. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 22:19:19 -0400 OK Doug you got me fired up.. just one thing to know what source of asterisk are you using exactly? Got Dahdi got the patch.. will fix what's needed to be fixed about ntpd and all. But what damn source of asterisk are you using? ;-) From: doug at crompton.com To: petem001 at hotmail.com CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 13:15:14 -0400 Pete, I have done this so many times but unfortunately I never documented it. Here is a simple description. Get a distro and configure it like you normally would. Get ntpd running, network setup, etc. Download the acid code and the latest dahdi - I see it is 2.10.0 The last I used was 2.9.x but I suspect it will work the same. If not you could get the 2.9 version. http://www.asterisk.org/downloads/dahdi Apply the patch - info on how to do that is in the readme https://allstarlink.org/fixed-dahdi-patches.tar.gz Compile and install dahdi. Then compile and install asterisk Don't run any offsite updates. Configure it manually - not hard to do - and run. If you already have a configured system you can use those files from /etc.asterisk. BTW the BBB setup procedure and howto's at http://hamvoip.org describe how to do that very easily which would also apply here. The only caveat is the config files would be different to start with so some consideration has to be given to that. All that sounds easy but you undoubtedly will have some hiccups and things you will have to do to get it to work. It is impossible to document that as it would be different on the multitude of distros and kernel versions. I have compiled it on the latest Debian and Ubuntu. The real problem is OSS support which is required. Debian has it, Ubuntu does not. You have to recompile the kernel and add it back in. For that reason Ubuntu is not recommended as kernel versions can change with frequent updates. I guess the big question is do you really need to do this. I forget why you said you can't run a local system. In that case you could just install an acid release on a PC or maybe go with the BBB. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 12:08:04 -0400 well can you point me a few pointers on how to do so? Never patched some software before. From: Doug Crompton Sent: Thursday, September 11, 2014 11:03 AM To: pete M Cc: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I am not sure what you are saying when you comment.... "well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.." Did you mean "will" ?? The patches can be applied against the latest dahdi and it will compile on late kernels. The BBB is an example of that. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 09:42:08 -0400 well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.. I can run the system on bunch of disto.. Here is the list.. CentOS 5 32bit CentOS 5 64bit CentOS 6 32bit CentOS 6 64bit CentOS 7 64bit CentOS 7 64bit Minimal Debian 6 32bit Debian 6 64bit Debian 7 32bit Debian 7 32bit Minimal Debian 7 64bit Debian 7 64bit Minimal Fedora 17 32bit Fedora 17 64bit Fedora 19 32bit Fedora 19 64bit Starbound-Ubuntu 13.10 32bit SUSE 12.2 32bit SUSE 12.2 64bit Ubuntu 10.04 32bit Ubuntu 10.04 64bit Ubuntu 11.10 32bit Ubuntu 11.10 64bit Ubuntu 12.10 32bit Ubuntu 12.10 64bit Ubuntu 13.10 32bit Ubuntu 13.10 64bit Ubuntu 14.04 32bit Ubuntu 14.04 32bit Minimal Ubuntu 14.04 64bit Ubuntu 14.04 64bit Minimal So I have lots of choice But I was under the feeling that the best distro was centos 5 for acid.. (using the install script from the cd.. Unless you can point me in another direction.. From: Doug Crompton Sent: Wednesday, September 10, 2014 6:16 PM To: pete M Cc: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Pete, I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org Date: Wed, 10 Sep 2014 14:12:38 -0400 Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. If it would be installed at least up to a point. I would be able to do it.. I just dont know how to tell the compiler not to compile that part and go on.. From: kk6ecm at gmail.com Date: Wed, 10 Sep 2014 09:15:13 -0700 To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} Thanks, Bob kk6ecm Sent from iPad On Sep 10, 2014, at 8:30 AM, pete M wrote: OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? If I did I am sorry.. And I gave my apology to every one I could have offended.. But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. From: kk6ecm Sen t: Tuesday, September 09, 2014 1:40 PM To: APP RPT Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. Thanks, Bob kk6ecm Sent from iPad On Sep 9, 2014, at 8:27 AM, pete M wrote: Ok will try that.. thanks! From: Bob Sent: Tuesday, September 09, 2014 10:55 AM To: 'APP RPT' Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I?ve done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS website No features, tools only, no desktop (competes with Asterisk) Set ssh /etc/ssh/sshd_config Run "setup" at comand line and disable firewall vi /etc/rc.d/acidrepo http://dl.allstarlink.org Execute portion of ks.cfg, each line at a time cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig cat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.sh Auto reboot after phase1.sh executed phase2.sh runs automatically to completion Bob kk6ecm From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org../. Getting files.tar.gz from http://dl.allstarlink.org../. ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preproc esso r... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln< /font> checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOU RC E -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeop ts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wlEmoticon-winkingsmile[1].png Type: image/png Size: 1135 bytes Desc: not available URL: From george at dyb.com Fri Sep 12 06:08:55 2014 From: george at dyb.com (George Csahanin) Date: Fri, 12 Sep 2014 01:08:55 -0500 Subject: [App_rpt-users] What is Dahdi? In-Reply-To: References: <4EF59EB0324F4C8F9F8EBCBABE791805@georgecPC> Message-ID: <1CE9E79FEF7E447EB1B8B65B51A59DC2@georgecPC> OK, thanks for the clarification. It?s fairly close to what I had put together in my mind the last five years. Where I go off center is (and I?m no programmer, I?m sure this has a reason) when/why isn?t the set of drivers just a part of Asterisk. Since it seems that It needs those drivers and the drivers are for Asterisk (or do they also work with other systems?) OK, Doug and all, thanks for some clarification. GeorgeC George J Csahanin W2DB Allstar 2360 Echolink-Free Cedar Park, TX 512-401-2630 home 401-338-0568 cel From: Doug Crompton Sent: Thursday, September 11, 2014 9:39 PM To: George Csahanin Cc: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] What is Dahdi? This will explain it.... http://www.voip-info.org/wiki/view/DAHDI http://blogs.digium.com/2008/05/19/zaptel-project-being-renamed-to-dahdi/ 73 Doug WA3DSP http://www.crompton.com/hamradio -------------------------------------------------------------------------------- From: george at dyb.com To: App_rpt-users at ohnosec.org Date: Thu, 11 Sep 2014 20:53:26 -0500 Subject: [App_rpt-users] What is Dahdi? OK, not being a wise-ass, not trying to be stupid, that part?s covered. Just trying to understand. What are the specific functions of: Dahdi Asterisk Libpri Zaptel I know they are all part of the whole package, and that whole package still has me in awe. But being very curious type I wanted to know how this all comes together. In my simple mind I axe: why isn?t Asterisk enough? I know what that one is, but as I use app_rpt daily I wish I knew which of the above are providing what part of the overall system. George J Csahanin W2DB Allstar 2360 Echolink-Free Cedar Park, TX 512-401-2630 home 401-338-0568 cel _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From N1XBM at amsat.org Fri Sep 12 15:36:47 2014 From: N1XBM at amsat.org (Robert Newberry) Date: Fri, 12 Sep 2014 11:36:47 -0400 Subject: [App_rpt-users] Connection failed Message-ID: So the power was cut to the building my repeater is in. My repeater functions, I'm able to connect via IAX. I'm also able to SSH in and ping the IP of the node I'm trying to connect too (27066) I'm also able to ping google.com. but when I go to the CLI and type rpt fun 27086 *327066 it fails. So what gives? I'm running acid and a DMK URI. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Fri Sep 12 16:19:21 2014 From: doug at crompton.com (Doug Crompton) Date: Fri, 12 Sep 2014 12:19:21 -0400 Subject: [App_rpt-users] Connection failed In-Reply-To: References: Message-ID: The node looks good here - grep 27086 /tmp/rpt_extnodes 27086=radio at 72.224.76.51:4569/27086,72.224.76.51 If you are running Acid on a PC then grep 27086 /var/lib/asterisk/rpt_extnodes 27086=radio at 72.224.76.51:4569/27086,72.224.76.51 Sometimes you have to reboot or restart. Are you registered? CLI>iax2 show registry What is the failure? No response or an actual failure voice message? Also any CLI messages? 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Fri, 12 Sep 2014 11:36:47 -0400 From: N1XBM at amsat.org To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Connection failed So the power was cut to the building my repeater is in. My repeater functions, I'm able to connect via IAX. I'm also able to SSH in and ping the IP of the node I'm trying to connect too (27066) I'm also able to ping google.com. but when I go to the CLI and type rpt fun 27086 *327066 it fails. So what gives? I'm running acid and a DMK URI. _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Fri Sep 12 16:20:58 2014 From: doug at crompton.com (Doug Crompton) Date: Fri, 12 Sep 2014 12:20:58 -0400 Subject: [App_rpt-users] Connection failed In-Reply-To: References: Message-ID: ops... realized I got that node wrong... [root at node40961 sbin]# grep 27066 /tmp/rpt_extnodes 27066=radio at 77.98.187.139:4568/27066,77.98.187.139 Still looks good... 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Fri, 12 Sep 2014 11:36:47 -0400 From: N1XBM at amsat.org To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Connection failed So the power was cut to the building my repeater is in. My repeater functions, I'm able to connect via IAX. I'm also able to SSH in and ping the IP of the node I'm trying to connect too (27066) I'm also able to ping google.com. but when I go to the CLI and type rpt fun 27086 *327066 it fails. So what gives? I'm running acid and a DMK URI. _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vencl at att.net Fri Sep 12 16:32:52 2014 From: vencl at att.net (Lu Vencl) Date: Fri, 12 Sep 2014 12:32:52 -0400 Subject: [App_rpt-users] Connection failed In-Reply-To: References: Message-ID: <84C0BFDF-426F-4198-9EED-EEC8AF9CBDDC@att.net> Sometimes it takes like 30 minutes before all nodes get updated. Or maybe longer? Maybe someone can provide clarification on this and if there is a way to force an update to a node that has not yet received the latest ip? Also going static does help as well on the wan side. Lu Vencl > On Sep 12, 2014, at 11:36 AM, Robert Newberry wrote: > > So the power was cut to the building my repeater is in. My repeater functions, I'm able to connect via IAX. I'm also able to SSH in and ping the IP of the node I'm trying to connect too (27066) I'm also able to ping google.com. but when I go to the CLI and type rpt fun 27086 *327066 it fails. > > So what gives? > > I'm running acid and a DMK URI. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From N1XBM at amsat.org Fri Sep 12 18:01:55 2014 From: N1XBM at amsat.org (Robert Newberry) Date: Fri, 12 Sep 2014 14:01:55 -0400 Subject: [App_rpt-users] Connection failed In-Reply-To: <84C0BFDF-426F-4198-9EED-EEC8AF9CBDDC@att.net> References: <84C0BFDF-426F-4198-9EED-EEC8AF9CBDDC@att.net> Message-ID: It appeared to take a few minutes. I went to get a drink of water and came back and all was well. I suppose after a reboot it must have to reach out and figure out what servers are available. -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Fri Sep 12 20:38:37 2014 From: telesistant at hotmail.com (Jim Duuuude) Date: Fri, 12 Sep 2014 13:38:37 -0700 Subject: [App_rpt-users] What is Dahdi? In-Reply-To: References: <4EF59EB0324F4C8F9F8EBCBABE791805@georgecPC>, Message-ID: DAHDI (previously Zaptel, also/originally Zapata Telephony technology) is/was the hardware/software/systems implementation that allows Asterisk to interface with physical telephony interfaces, provide functionality in software essential to traditional telephony (whereas previous, hardware-implemented designs did this in rather expensive hardware), and, probably most-important to the "radio" type uses of Asterisk, provides synchronization, routing, and combining (conferencing) of audio streams within the system. So, it is essentially an interface between the "physical" "telecom" world, and the "computer" world. Asterisk is the "computer world" part of the system. It provides "call-level" telecom functionality (call switching, call routing, voice interaction, application interface, logging, etc), in addition to audio-stream-level interface and functionality for computer-related voice transport (such as VOIP). Since Asterisk has good application support, it was easy to make it a REALLY good platform on which to implement radio control, since it had nearly all of the characteristics necessary to do so inherently, and was not difficult to add what it lacked. LibPRI is a protocol library for for Primary rate ISDN telecom services. It was included mainly for completeness. I seriously doubt that anyone that initially implemented a radio system has much use for this, but trust me, several people that initially implemented telephone switches using my distro and THEN decided to put a radio interface or two on it, were certainly happy I did it this way. Obviously, LibPRI is not needed for a purely "radio" environment. Zaptel (as mentioned above) was the previous name of DAHDI (don't blame me!! I didnt come up with EITHER of these names!!) Jim WB6NIL "Daddy of DAHDI" -- As I was called by Mark Spencer circa 2008 (while at an Astricon) P.S. I cant tell all of you how tempted I was to answer more like this: DAHDI - Counterpart of the "MAHMI" technology. Once together, DAHDI and MAHMI spawned a number of derivative technologies, such as "SONNI". Sadly, DAHDI and MAHMI don't functionally inter-operate well anymore, and, as you might imagine, SONNI, now requiring two distinct interfaces (one for DAHDI, one for MAHMI), sometimes has interface "issues". :-) :-) :-) From: kk6ecm at gmail.com To: App_rpt-users at ohnosec.org Date: Thu, 11 Sep 2014 19:51:41 -0700 Subject: Re: [App_rpt-users] What is Dahdi? This is what I understand... but looking for an expert view from someone else. Dahdi - Asterisk & hardware device interface Asterisk - telephony switching and PBX service Libpri - protocols used by Asterisk/Dahdi? Zaptel - interface functionally similar to, and predating Dahdi? Bob kk6ecm From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of George Csahanin Sent: Thursday, September 11, 2014 6:53 PM To: App_rpt-users at ohnosec.org Subject: [App_rpt-users] What is Dahdi? OK, not being a wise-ass, not trying to be stupid, that part?s covered. Just trying to understand. What are the specific functions of: Dahdi - Asterisk & hardware device interface Asterisk - telephony switching and PBX service Libpri - protocols used by Asterisk/Dahdi? Zaptel - interface functionally similar to, and predating Dahdi? I know they are all part of the whole package, and that whole package still has me in awe. But being very curious type I wanted to know how this all comes together. In my simple mind I axe: why isn?t Asterisk enough? I know what that one is, but as I use app_rpt daily I wish I knew which of the above are providing what part of the overall system. George J Csahanin W2DB Allstar 2360 Echolink-Free Cedar Park, TX 512-401-2630 home 401-338-0568 cel _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From electricity440 at gmail.com Fri Sep 12 21:40:16 2014 From: electricity440 at gmail.com (Skyler F) Date: Fri, 12 Sep 2014 15:40:16 -0600 Subject: [App_rpt-users] Change DTMF autodial Speed Message-ID: I use cop 48 for automatically dialing DTMF sequences in a shell script. in particular: asterisk -rx "rpt cmd 40764 cop 48 x,y" (x, y are my numbers to dial) They are getting annoying at the default speed though, because it automatically dials it on connect and disconnect. and I would really like to speed them up. Is there any way to do this? So instead of DAAHH its more like dit. ? 73 Skyler KD?WHB -- Skyler Fennell amsatnet.info KD?WHB electricity440 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From kk6ecm at gmail.com Sat Sep 13 00:02:30 2014 From: kk6ecm at gmail.com (Bob) Date: Fri, 12 Sep 2014 17:02:30 -0700 Subject: [App_rpt-users] Multiple requests for registration Message-ID: <1857007D3A0D4789A90DD7BEBDA40C9B@ThePykesHP> My servers are constantly sending registration request and rereqquests. I check two different ones on two different IP addresses at two different locations, although the same ISP. I don't ever remember this happening this much, at this frequency. I'm wondering if there is something I need to fix. Also, is the frequency of these requests adjustable on my end, and is it anything I need to do? The data below is from one server. The other server looks pretty much the same. This one also has Echolink, and I get an Echolink update occasionally interspersed between large groups of the warnings shown below. Thanks, Bob kk6ecm [Sep 12 23:48:34] WARNING[456]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '29009' [Sep 12 23:48:34] WARNING[459]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest [Sep 12 23:48:44] WARNING[452]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '28765' [Sep 12 23:48:45] WARNING[454]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest [Sep 12 23:49:24] WARNING[459]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '29009' [Sep 12 23:49:24] WARNING[458]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest [Sep 12 23:49:35] WARNING[454]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '28765' [Sep 12 23:49:35] WARNING[456]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sat Sep 13 00:35:27 2014 From: doug at crompton.com (Doug Crompton) Date: Fri, 12 Sep 2014 20:35:27 -0400 Subject: [App_rpt-users] Multiple requests for registration In-Reply-To: <1857007D3A0D4789A90DD7BEBDA40C9B@ThePykesHP> References: <1857007D3A0D4789A90DD7BEBDA40C9B@ThePykesHP> Message-ID: The registration interval is 60 seconds hard coded in the source. So what you see is normal. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kk6ecm at gmail.com To: App_rpt-users at ohnosec.org Date: Fri, 12 Sep 2014 17:02:30 -0700 Subject: [App_rpt-users] Multiple requests for registration My servers are constantly sending registration request and rereqquests. I check two different ones on two different IP addresses at two different locations, although the same ISP. I don?t ever remember this happening this much, at this frequency. I?m wondering if there is something I need to fix. Also, is the frequency of these requests adjustable on my end, and is it anything I need to do? The data below is from one server. The other server looks pretty much the same. This one also has Echolink, and I get an Echolink update occasionally interspersed between large groups of the warnings shown below. Thanks, Bob kk6ecm [Sep 12 23:48:34] WARNING[456]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '29009' [Sep 12 23:48:34] WARNING[459]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest [Sep 12 23:48:44] WARNING[452]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '28765' [Sep 12 23:48:45] WARNING[454]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest [Sep 12 23:49:24] WARNING[459]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '29009' [Sep 12 23:49:24] WARNING[458]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest [Sep 12 23:49:35] WARNING[454]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '28765' [Sep 12 23:49:35] WARNING[456]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wadeo at charter.net Sat Sep 13 06:45:42 2014 From: wadeo at charter.net (wade) Date: Sat, 13 Sep 2014 01:45:42 -0500 Subject: [App_rpt-users] Incoming connects Message-ID: <5413E816.7080405@charter.net> Good evening all, I have been dealing with an issue for about a month now of nobody being able to connect to me, either from AllStar or Echolink. I can connect to them by radio or using the CLI and it works perfect. Audio is passed back and forth no drops, nothing. But no one can connect in. About 2 weeks ago I was forced to do a complete system reinstall due to a bad streaming install attempt. I thought maybe that would fix my incoming issue also. It did not. I can ping Google and everything is great, no packets dropped. During the course of this investigation I have gone through my router numerous times and the port forwarding is correct, UDP 4569 for AllStar, UDP 5198-5199 and TCP 5200 for Echolink. This setup has worked flawlessly for months after I set it up in it new location then it just quit. Any ideas that maybe I haven't thought of or maybe something to jar my memory? I also have had this message coming across the CLI constantly. "Warning aprsthread: server noam.aprs2.net cannot be found" That was a short description as I can not copy and paste it to the computer I use to email from. I have tried "rotate.aprs.net" and "rotate.aprs2.net" also with no success. Could the two issues be related at all? I would appreciate any help that can be given. I think it is something so basic I am just over looking it and I hope it is. But I wanted to run it past the experts to see if you guys had any other ideas Thanks Wade KC?MLT Node 28757 --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com From jrorke at cogeco.ca Sat Sep 13 11:43:47 2014 From: jrorke at cogeco.ca (REDBUTTON_CTRL) Date: Sat, 13 Sep 2014 07:43:47 -0400 Subject: [App_rpt-users] Incoming connects In-Reply-To: <5413E816.7080405@charter.net> References: <5413E816.7080405@charter.net> Message-ID: <54142DF3.3050507@cogeco.ca> Is you box on a static IP or DHCP? The default install puts the box on dhcp. After you load the sw then set the box to a static ip. If the bnox is on dhcp you will beable to connect out but inward forwarding doesnt work because the box is not on the ip configured in the router. I see you node is reporting. Can you ssh into the box from another pc? Jon VA3RQ On 9/13/2014 2:45 AM, wade wrote: > Good evening all, > > I have been dealing with an issue for about a month now of nobody > being able to connect to me, either from AllStar or Echolink. I can > connect to them by radio or using the CLI and it works perfect. Audio > is passed back and forth no drops, nothing. But no one can connect in. > About 2 weeks ago I was forced to do a complete system reinstall due > to a bad streaming install attempt. I thought maybe that would fix my > incoming issue also. It did not. I can ping Google and everything is > great, no packets dropped. During the course of this investigation I > have gone through my router numerous times and the port forwarding is > correct, UDP 4569 for AllStar, UDP 5198-5199 and TCP 5200 for > Echolink. This setup has worked flawlessly for months after I set it > up in it new location then it just quit. > > Any ideas that maybe I haven't thought of or maybe something to jar my > memory? > > > > I also have had this message coming across the CLI constantly. > > "Warning aprsthread: server noam.aprs2.net cannot be found" > > That was a short description as I can not copy and paste it to the > computer I use to email from. > > I have tried "rotate.aprs.net" and "rotate.aprs2.net" also with no > success. > Could the two issues be related at all? > > I would appreciate any help that can be given. I think it is something > so basic I am just over looking it and I hope it is. But I wanted to > run it past the experts to see if you guys had any other ideas > > Thanks > Wade > KC?MLT > Node 28757 > > --- > This email is free from viruses and malware because avast! Antivirus > protection is active. > http://www.avast.com > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. From lorentedford at gmail.com Sat Sep 13 13:12:48 2014 From: lorentedford at gmail.com (Loren Tedford) Date: Sat, 13 Sep 2014 08:12:48 -0500 Subject: [App_rpt-users] Incoming connects In-Reply-To: <54142DF3.3050507@cogeco.ca> References: <5413E816.7080405@charter.net> <54142DF3.3050507@cogeco.ca> Message-ID: I was thinking that Maybe the Allstar port has not been forwarded Correctly.. Can you access your node via the Web Trancsiever and Echolink? If its an Echolink issue it would involve crazy port forwarding of 4 ports which.. I already forgot what they were bu you can find it via google.. I think the default port for allstar was like 4569 another helpful hint i have learned from experience is to set the node up using a Static Ip rather than automatic because it it set to Automatic it could change on ya then you would have to report forward the ports to that new ip.. Another thing you could do since most Routersif today allow you to assign Ips via Mac Adress is to set it Static from the Router there is a few good reasons to do this one is that if some thing lets say was to happen and you had to fall back on a backup internet connection our router system your node provided that you have DynDNS setup on the node can relay the new ip info and some times if your lucky might actually be able to get into the node remotely with out having to go out to the repeater sight or node sight.. Not sure on your level of Knowledge with Linux but might go directly out to the node and type in ( ifconfig ) Another thought is internally your node has decided to run IPv6 more and more in the Server situations I have seen IPv6 than ever before never would have dreamed of the day that I would be using both Ipv4 and Ipv6 just a thought.. Loren Tedford (KC9ZHV) Email: lorentedford at gmail.com Phone: 618-553-0806 http://www.lorentedford.com http://kc9zhv.lorentedford.com On Sat, Sep 13, 2014 at 6:43 AM, REDBUTTON_CTRL wrote: > Is you box on a static IP or DHCP? > > The default install puts the box on dhcp. After you load the sw then set > the box to a static ip. If the bnox is on dhcp you will beable to connect > out but inward forwarding doesnt work because the box is not on the ip > configured in the router. > > I see you node is reporting. Can you ssh into the box from another pc? > > Jon VA3RQ > > > On 9/13/2014 2:45 AM, wade wrote: > >> Good evening all, >> >> I have been dealing with an issue for about a month now of nobody >> being able to connect to me, either from AllStar or Echolink. I can connect >> to them by radio or using the CLI and it works perfect. Audio is passed >> back and forth no drops, nothing. But no one can connect in. About 2 weeks >> ago I was forced to do a complete system reinstall due to a bad streaming >> install attempt. I thought maybe that would fix my incoming issue also. It >> did not. I can ping Google and everything is great, no packets dropped. >> During the course of this investigation I have gone through my router >> numerous times and the port forwarding is correct, UDP 4569 for AllStar, >> UDP 5198-5199 and TCP 5200 for Echolink. This setup has worked flawlessly >> for months after I set it up in it new location then it just quit. >> >> Any ideas that maybe I haven't thought of or maybe something to jar my >> memory? >> >> >> >> I also have had this message coming across the CLI constantly. >> >> "Warning aprsthread: server noam.aprs2.net cannot be found" >> >> That was a short description as I can not copy and paste it to the >> computer I use to email from. >> >> I have tried "rotate.aprs.net" and "rotate.aprs2.net" also with no >> success. >> Could the two issues be related at all? >> >> I would appreciate any help that can be given. I think it is something so >> basic I am just over looking it and I hope it is. But I wanted to run it >> past the experts to see if you guys had any other ideas >> >> Thanks >> Wade >> KC?MLT >> Node 28757 >> >> --- >> This email is free from viruses and malware because avast! Antivirus >> protection is active. >> http://www.avast.com >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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 at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From keith at goobie.org Sat Sep 13 13:27:00 2014 From: keith at goobie.org (Keith Goobie) Date: Sat, 13 Sep 2014 09:27:00 -0400 Subject: [App_rpt-users] Incoming connects In-Reply-To: Message-ID: Wade. Two things: 1. Can you send along the contents of the /etc/sysconfig/networking/devices/ifcfg-eth0 and send along the data returned when you execute ?ifconfig ?a? 2. Can you send along the port forwarding rules for your router (not what you copy down, but rather the screen capture or if command line ? cut & paste. Also what is the model number of the router ? some do not properly port forward UDP 4569 ? for example some Linksys models. If you are willing to experiment do the following at a cli ? tcpdump port 4569 and send along a copy of the data capture. Keith VA3YC On 9/13/14 9:12 AM, "Loren Tedford" wrote: > I was thinking that Maybe the Allstar port has not been forwarded Correctly.. > Can you access your node via the Web Trancsiever and Echolink? If its an > Echolink issue it would involve crazy port forwarding of 4 ports which.. I > already forgot what they were bu you can find it via google.. I think the > default port for allstar was like 4569 another helpful hint i have learned > from experience is to set the node up using a Static Ip rather than automatic > because it it set to Automatic it could change on ya then you would have to > report forward the ports to that new ip.. Another thing you could do since > most Routersif today allow you to assign Ips via Mac Adress is to set it > Static from the Router there is a few good reasons to do this one is that if > some thing lets say was to happen and you had to fall back on a backup > internet connection our router system your node provided that you have DynDNS > setup on the node can relay the new ip info and some times if your lucky might > actually be able to get into the node remotely with out having to go out to > the repeater sight or node sight.. > > Not sure on your level of Knowledge with Linux but might go directly out to > the node and type in ( ifconfig )? Another thought is internally your node has > decided to run IPv6 more and more in the Server situations I have seen IPv6 > than ever before never would have dreamed of the day that I would be using > both Ipv4 and Ipv6 just a thought.. > > Loren Tedford (KC9ZHV)? > Email:?lorentedford at gmail.com > Phone: 618-553-0806 > http://www.lorentedford.com > http://kc9zhv.lorentedford.com > > > On Sat, Sep 13, 2014 at 6:43 AM, REDBUTTON_CTRL wrote: >> Is you box on a static IP or DHCP? >> >> The default install puts the box on dhcp. After you load the sw then set the >> box to a static ip. If the bnox is on dhcp you will beable to connect out but >> inward forwarding doesnt work because the box is not on the ip configured in >> the router. >> >> I see you node is reporting. Can you ssh into the box from another pc? >> >> Jon VA3RQ >> >> >> On 9/13/2014 2:45 AM, wade wrote: >>> Good evening all, >>> >>> ? ? I have been dealing with an issue for about a month now of nobody being >>> able to connect to me, either from AllStar or Echolink. I can connect to >>> them by radio or using the CLI and it works perfect. Audio is passed back >>> and forth no drops, nothing. But no one can connect in. About 2 weeks ago I >>> was forced to do a complete system reinstall due to a bad streaming install >>> attempt. I thought maybe that would fix my incoming issue also. It did not. >>> I can ping Google and everything is great, no packets dropped. During the >>> course of this investigation I have gone through my router numerous times >>> and the port forwarding is correct, UDP 4569 for AllStar, UDP 5198-5199 and >>> TCP 5200 for Echolink. This setup has worked flawlessly for months after I >>> set it up in it new location then it just quit. >>> >>> Any ideas that maybe I haven't thought of or maybe something to jar my >>> memory? >>> >>> >>> >>> I also have had this message coming across the CLI constantly. >>> >>> "Warning? aprsthread: server noam.aprs2.net cannot >>> be found" >>> >>> That was a short description as I can not copy and paste it to the computer >>> I use to email from. >>> >>> I have tried "rotate.aprs.net " and >>> "rotate.aprs2.net " also with no success. >>> Could the two issues be related at all? >>> >>> I would appreciate any help that can be given. I think it is something so >>> basic I am just over looking it and I hope it is. But I wanted to run it >>> past the experts to see if you guys had any other ideas >>> >>> Thanks >>> Wade >>> KC?MLT >>> Node 28757 >>> >>> --- >>> This email is free from viruses and malware because avast! Antivirus >>> protection is active. >>> http://www.avast.com >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at 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 at 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 at 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. -- keith at goobie.org Keith Goobie Richmond Hill, ON, CANADA -------------- next part -------------- An HTML attachment was scrubbed... URL: From wadeo at charter.net Sat Sep 13 16:43:34 2014 From: wadeo at charter.net (wade) Date: Sat, 13 Sep 2014 11:43:34 -0500 Subject: [App_rpt-users] Incoming connects In-Reply-To: <3EB2798F-151B-437B-8B54-39525CAB89D4@att.net> References: <5413E816.7080405@charter.net> <3EB2798F-151B-437B-8B54-39525CAB89D4@att.net> Message-ID: <54147436.6090905@charter.net> Sorry for the lack of information here. It was late.. lol Ok, I have a slightly different setup here than most but I'm sure some people do it for remote sites. First off my IP here at home is DCHP. I have a friend just down the street running AllStar with the same ISP and he has no issues. (more on his strange solution later). My setup consist of my main router for the house wired to an HSMM Mesh node in my shack. Another Mesh node is setup and wired to the AllStar Server in the garage. (I'm running this as a test to get ready for a remote site without internet.) So my server has an IP that starts with 10.12.xxx.xx. This setup worked flawlessly for months then this. All the routers, including the main house router are LinkSys. I have checked all these mesh nodes and the main router many times and all have the correct ports open. As for SSH?ng into it. I can if I am wired into my inside mesh node. I can't from anywhere else, I assume because the nodes are in AD-HOC mode??? Not to familiar woth all the networking SSH stuff quite yet. I will try to capture some data from it but I use a different computer to email from so it is difficult. I hope I didn't leave anyone out of information. Wade On 9/13/2014 7:23 AM, Lu Vencl wrote: > I have had the same problem with one of my nodes out in Colorado. The final outcome turned out to be that century link was blocking the port. You may want to try changing your port number to something else like 14569 and give that a shot. Be sure to change your port forwarding accordingly. > If you like, email me directly with your phone number and I will walk you through it. > > Lu Vencl > KA4EPS > >> On Sep 13, 2014, at 2:45 AM, wade wrote: >> >> Good evening all, >> >> I have been dealing with an issue for about a month now of nobody being able to connect to me, either from AllStar or Echolink. I can connect to them by radio or using the CLI and it works perfect. Audio is passed back and forth no drops, nothing. But no one can connect in. About 2 weeks ago I was forced to do a complete system reinstall due to a bad streaming install attempt. I thought maybe that would fix my incoming issue also. It did not. I can ping Google and everything is great, no packets dropped. During the course of this investigation I have gone through my router numerous times and the port forwarding is correct, UDP 4569 for AllStar, UDP 5198-5199 and TCP 5200 for Echolink. This setup has worked flawlessly for months after I set it up in it new location then it just quit. >> >> Any ideas that maybe I haven't thought of or maybe something to jar my memory? >> >> >> >> I also have had this message coming across the CLI constantly. >> >> "Warning aprsthread: server noam.aprs2.net cannot be found" >> >> That was a short description as I can not copy and paste it to the computer I use to email from. >> >> I have tried "rotate.aprs.net" and "rotate.aprs2.net" also with no success. >> Could the two issues be related at all? >> >> I would appreciate any help that can be given. I think it is something so basic I am just over looking it and I hope it is. But I wanted to run it past the experts to see if you guys had any other ideas >> >> Thanks >> Wade >> KC?MLT >> Node 28757 >> >> --- >> This email is free from viruses and malware because avast! Antivirus protection is active. >> http://www.avast.com >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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. --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com From petem001 at hotmail.com Sat Sep 13 23:48:58 2014 From: petem001 at hotmail.com (pete M) Date: Sat, 13 Sep 2014 19:48:58 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: , <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP>, , <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com>, , , , <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com>, , , , , , , , Message-ID: thanks Tim, will look into this.. Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 From: tim.sawyer at mac.com Date: Thu, 11 Sep 2014 19:54:13 -0700 CC: doug at crompton.com; app_rpt-users at ohnosec.org To: petem001 at hotmail.com I use this Asterisk source: http://svn.asterisk.org/svn/asterisk/branches/1.6.2/and pull app_rpt source out of http://x.allstarlink.org/svn-trunk.tar.gz You?ll need libpri and a bunch of other stuff I?ll leave for you to work out on your own. -- Tim :wq On Sep 11, 2014, at 7:19 PM, pete M wrote:OK Doug you got me fired up.. just one thing to know what source of asterisk are you using exactly? Got Dahdi got the patch.. will fix what's needed to be fixed about ntpd and all. But what damn source of asterisk are you using? ;-) From: doug at crompton.com To: petem001 at hotmail.com CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 13:15:14 -0400 Pete, I have done this so many times but unfortunately I never documented it. Here is a simple description. Get a distro and configure it like you normally would. Get ntpd running, network setup, etc. Download the acid code and the latest dahdi - I see it is 2.10.0 The last I used was 2.9.x but I suspect it will work the same. If not you could get the 2.9 version. http://www.asterisk.org/downloads/dahdi Apply the patch - info on how to do that is in the readme https://allstarlink.org/fixed-dahdi-patches.tar.gz Compile and install dahdi. Then compile and install asterisk Don't run any offsite updates. Configure it manually - not hard to do - and run. If you already have a configured system you can use those files from /etc.asterisk. BTW the BBB setup procedure and howto's at http://hamvoip.org describe how to do that very easily which would also apply here. The only caveat is the config files would be different to start with so some consideration has to be given to that. All that sounds easy but you undoubtedly will have some hiccups and things you will have to do to get it to work. It is impossible to document that as it would be different on the multitude of distros and kernel versions. I have compiled it on the latest Debian and Ubuntu. The real problem is OSS support which is required. Debian has it, Ubuntu does not. You have to recompile the kernel and add it back in. For that reason Ubuntu is not recommended as kernel versions can change with frequent updates. I guess the big question is do you really need to do this. I forget why you said you can't run a local system. In that case you could just install an acid release on a PC or maybe go with the BBB. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 12:08:04 -0400 well can you point me a few pointers on how to do so? Never patched some software before. From: Doug CromptonSent: Thursday, September 11, 2014 11:03 AMTo: pete MCc: app_rpt-users at ohnosec.orgSubject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I am not sure what you are saying when you comment.... "well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.." Did you mean "will" ?? The patches can be applied against the latest dahdi and it will compile on late kernels. The BBB is an example of that. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 09:42:08 -0400 well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.. I can run the system on bunch of disto.. Here is the list.. CentOS 5 32bitCentOS 5 64bitCentOS 6 32bitCentOS 6 64bitCentOS 7 64bitCentOS 7 64bit MinimalDebian 6 32bitDebian 6 64bitDebian 7 32bitDebian 7 32bit MinimalDebian 7 64bitDebian 7 64bit MinimalFedora 17 32bitFedora 17 64bitFedora 19 32bitFedora 19 64bitStarbound-Ubuntu 13.10 32bitSUSE 12.2 32bitSUSE 12.2 64bitUbuntu 10.04 32bitUbuntu 10.04 64bitUbuntu 11.10 32bitUbuntu 11.10 64bitUbuntu 12.10 32bitUbuntu 12.10 64bitUbuntu 13.10 32bitUbuntu 13.10 64bitUbuntu 14.04 32bitUbuntu 14.04 32bit MinimalUbuntu 14.04 64bitUbuntu 14.04 64bit Minimal So I have lots of choice But I was under the feeling that the best distro was centos 5 for acid.. (using the install script from the cd.. Unless you can point me in another direction.. From: Doug CromptonSent: Wednesday, September 10, 2014 6:16 PMTo: pete MCc: app_rpt-users at ohnosec.orgSubject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Pete, I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org Date: Wed, 10 Sep 2014 14:12:38 -0400 Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. If it would be installed at least up to a point. I would be able to do it.. I just dont know how to tell the compiler not to compile that part and go on.. From: kk6ecm at gmail.com Date: Wed, 10 Sep 2014 09:15:13 -0700 To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} Thanks,Bobkk6ecm Sent from iPad On Sep 10, 2014, at 8:30 AM, pete M wrote: OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? If I did I am sorry.. And I gave my apology to every one I could have offended.. But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. From: kk6ecmSen t: Tuesday, September 09, 2014 1:40 PMTo: APP RPTSubject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. Thanks,Bobkk6ecm Sent from iPad On Sep 9, 2014, at 8:27 AM, pete M wrote: Ok will try that.. thanks! From: BobSent: Tuesday, September 09, 2014 10:55 AMTo: 'APP RPT'Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I?ve done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS websiteNo features, tools only, no desktop (competes with Asterisk)Set ssh /etc/ssh/sshd_configRun "setup" at comand line and disable firewallvi /etc/rc.d/acidrepo http://dl.allstarlink.orgExecute portion of ks.cfg, each line at a timecp /etc/rc.d/rc.local /etc/rc.d/rc.local.origcat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -qhttp://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.shAuto reboot after phase1.sh executedphase2.sh runs automatically to completion Bobkk6ecm From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh****** Phase 2 post install ******Getting asterisk install script from http://dl.allstarlink.org../.Getting files.tar.gz from http://dl.allstarlink.org../.****** Asterisk Installation ******/etc/rc.d/astinstall.sh: line 11: ntpdate: command not foundUnpacking files.tar.gz...Compiling Zaptel...checking for gcc... gccchecking for C compiler default output file name... a.outchecking whether the C compiler works... yeschecking whether we are cross compiling... nochecking for suffix of executables...checking for suffix of object files... ochecking whether we are using the GNU C compiler... yeschecking whether gcc accepts -g... yeschecking for gcc option to accept ISO C89... none neededchecking how to run the C preproc esso r... gcc -Echecking for a BSD-compatible install... /usr/bin/install -cchecking whether ln -s works... yeschecking for GNU make... makechecking for grep... /bin/grepchecking for sh... /bin/shchecking for ln... /bin/lnchecking for wget... /usr/bin/wgetchecking for grep that handles long lines and -e... (cached) /bin/grepchecking for egrep... /bin/grep -Echecking for ANSI C header files... yeschecking for sys/types.h... yeschecking for sys/stat.h... yeschecking for stdlib.h... yeschecking for string.h... yeschecking for memory.h... yeschecking for strings.h... yeschecking for inttypes.h... yeschecking for stdint.h... yeschecking for unistd.h... yeschecking for initscr in -lcurses... nochecking for initscr in -lncurses... nochecking for newtBell in -lnewt... nochecking for usb_init in -lusb... noconfigure: creating ./config.statusconfig.status: creating build_tools/menuselect-depsconfig.status: creating makeoptsconfig.status: creating build_tools/make_firmware_objectconfigure: *** Zaptel build successfully configured ***make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect'checking build system type... i686-pc-linux-gnuchecking host system type... i686-pc-linux-gnuchecking for gcc... gccchecking for C compiler default output file name... a.outchecking whether the C compiler works... yeschecking whether we are cross compiling... nochecking for suffix of executables...checking for suffix of object files... ochecking whether we are using the GNU C compiler... yeschecking whether gcc accepts -g... yeschecking for gcc option to accept ANSI C... none neededchecking for GNU make... makechecking for asprintf... yeschecking for getloadavg... yeschecking for setenv... yeschecking for strcasestr... yeschecking for strndup... yeschecking for strnlen... yeschecking for strsep... yeschecking for strtoq... yeschecking for unsetenv... yeschecking for vasprintf... yeschecking how to run the C preprocessor... gcc -Echecking for egrep... grep -Echecking for ANSI C header files... yeschecking for sys/types.h... yeschecking for sys/stat.h... yeschecking for stdlib.h... yeschecking for string.h... yeschecking for memory.h... yeschecking for strings.h... yeschecking for inttypes.h... yeschecking for stdint.h... yeschecking for unistd.h... yeschecking for initscr in -lcurses... nochecking for initscr in -lncurses... nochecking for pkg-config... Noconfigure: creating ./config.statusconfig.status: creating makeoptsconfig.status: creating autoconfig.hconfigure: configuring in mxmlconfigure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=.checking for gcc... gccchecking for C compiler default output file name... a.outchecking whether the C compiler works... yeschecking whether we are cross compiling... nochecking for suffix of executables...checking for suffix of object files... ochecking whether we are using the GNU C compiler... yeschecking whether gcc accepts -g... yeschecking for gcc option to accept ANSI C... none neededchecking for g++... nochecking for c++... nochecking for gpp... nochecking for aCC... nochecking for CC... nochecking for cxx... nochecking for cc++... nochecking for cl... nochecking for FCC... nochecking for KCC... nochecking for RCC... nochecking for xlC_r... nochecking for xlC... nochecking whether we are using the GNU C++ compiler... nochecking whether g++ accepts -g... nochecking for a BSD-compatible install... /usr/bin/install -cchecking for ranlib... ranlibchecking for ar... /usr/bin/archecking for cp... /bin/cpchecking for ln... /bin/ln< /font>checking for mkdir... /bin/mkdirchecking for nroff... /usr/bin/nroffchecking for rm... /bin/rmchecking for strdup... yeschecking for vsnprintf... yesconfigure: creating ./config.statusconfig.status: creating Makefileconfig.status: creating mxml.listconfig.status: creating mxml.pcconfig.status: creating config.hconfigure: Menuselect build configuration successfully completedmake[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect'make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect'make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect'gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.cgcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.cgcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.cmake[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml'gcc -O -Wall -c mxml-attr.cgcc -O -Wall -c mxml-entity.cgcc -O -Wall -c mxml-file.cgcc -O -Wall -c mxml-index.cgcc -O -Wall -c mxml-node.cgcc -O -Wall -c mxml-search.cgcc -O -Wall -c mxml-set.cgcc -O -Wall -c mxml-private.cgcc -O -Wall -c mxml-string.c/bin/rm -f libmxml.a/usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.oa - mxml-attr.oa - mxml-entity.oa - mxml-file.oa - mxml-index.oa - mxml-node.oa - mxml-search.oa - mxml-set.oa - mxml-private.oa - mxml-string.oranlib libmxml.amake[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml'gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.amake[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect'make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect'Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue.*********************************************************** make: *** [menuselect.makeopts] Error 255Failure: Unable to compile Zaptel 2Fatal error: Unable to install Asterisk![root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From petem001 at hotmail.com Sat Sep 13 23:56:57 2014 From: petem001 at hotmail.com (pete M) Date: Sat, 13 Sep 2014 19:56:57 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: , , <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP>, , , , <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com>, , , , , , , , <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com>, , , , , , , , Message-ID: OK The GOAL: having a node without a radio on a server to use as a gateway of conference for a few repeaters around the Montreal region. I found a nice site where I can rent a small vps for 5$ a month. nothing fancy. I want to have that computer tu be my conference.. None of the site I have are either stable enough to host a nice conference or where I could have computer in a not arsh place, the bandwith is the issue. So I can load a lot of different distro, BUT they are fixe image to start with. Cnt ask to load the acid iso.. (this would of course fix every thing.) So the goal is not for fun I do need to make this work. Will work from there, will find some answer online for most of the stuff I need, But when it is directly related to app_rpt, here is my only source.. Now I know what version of asterisk to use, where to find it, same for dahdi and app_rpt.. will try to ork on that. will find that I need some library of other stuff enroute and other software.. but I will try.. Not such a noob in linux.. but not a pro.. thanks for you patience.. Pierre VE2PF From: doug at crompton.com To: petem001 at hotmail.com CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 23:49:25 -0400 First of all remind me - what is your end goal here. Are you doing this just for fun or is it for a real need and if so what is the need? The easiest thing to do might be to just download the BBB image at hamvoip.org. Write it to an SD card, mount it on Linux - ubuntu or whatever works. The root partition not the boot partition. Copy from everything from the mount point /usr/src/utils to /usr/src on your linux box. Also copy /etc/asterisk from the mount point to /etc/asterisk for all the config files. The source tree would then be in /usr/src/utils/asterisk - dahdi would also be there along with the patches in /usr/src/utils You can compile and intall both dahdi and asterisk from there. Then following the directions on the BBB page and howto on setting up your node. Another possible choice would be to just bring up a standard centos installation on a PC and copy what you need from there. All the source and files you would need would be there like the scripts in /usr/local/sbin. You would need to make some changes however. As Dave pointed out earlier you are in for some real bumps along the way. There will be packages you will need to download and things you will need to configure. It is not a 123 type of thing. Without some Linux experience it could be daunting. Just remember if you are using dahdi you need to remove any mention of zaptel and use the chan_dahdi.conf as shown in the BBB config. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 22:19:19 -0400 OK Doug you got me fired up.. just one thing to know what source of asterisk are you using exactly? Got Dahdi got the patch.. will fix what's needed to be fixed about ntpd and all. But what damn source of asterisk are you using? ;-) From: doug at crompton.com To: petem001 at hotmail.com CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 13:15:14 -0400 Pete, I have done this so many times but unfortunately I never documented it. Here is a simple description. Get a distro and configure it like you normally would. Get ntpd running, network setup, etc. Download the acid code and the latest dahdi - I see it is 2.10.0 The last I used was 2.9.x but I suspect it will work the same. If not you could get the 2.9 version. http://www.asterisk.org/downloads/dahdi Apply the patch - info on how to do that is in the readme https://allstarlink.org/fixed-dahdi-patches.tar.gz Compile and install dahdi. Then compile and install asterisk Don't run any offsite updates. Configure it manually - not hard to do - and run. If you already have a configured system you can use those files from /etc.asterisk. BTW the BBB setup procedure and howto's at http://hamvoip.org describe how to do that very easily which would also apply here. The only caveat is the config files would be different to start with so some consideration has to be given to that. All that sounds easy but you undoubtedly will have some hiccups and things you will have to do to get it to work. It is impossible to document that as it would be different on the multitude of distros and kernel versions. I have compiled it on the latest Debian and Ubuntu. The real problem is OSS support which is required. Debian has it, Ubuntu does not. You have to recompile the kernel and add it back in. For that reason Ubuntu is not recommended as kernel versions can change with frequent updates. I guess the big question is do you really need to do this. I forget why you said you can't run a local system. In that case you could just install an acid release on a PC or maybe go with the BBB. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 12:08:04 -0400 well can you point me a few pointers on how to do so? Never patched some software before. From: Doug Crompton Sent: Thursday, September 11, 2014 11:03 AM To: pete M Cc: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I am not sure what you are saying when you comment.... "well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.." Did you mean "will" ?? The patches can be applied against the latest dahdi and it will compile on late kernels. The BBB is an example of that. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: doug at crompton.com CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Date: Thu, 11 Sep 2014 09:42:08 -0400 well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.. I can run the system on bunch of disto.. Here is the list.. CentOS 5 32bit CentOS 5 64bit CentOS 6 32bit CentOS 6 64bit CentOS 7 64bit CentOS 7 64bit Minimal Debian 6 32bit Debian 6 64bit Debian 7 32bit Debian 7 32bit Minimal Debian 7 64bit Debian 7 64bit Minimal Fedora 17 32bit Fedora 17 64bit Fedora 19 32bit Fedora 19 64bit Starbound-Ubuntu 13.10 32bit SUSE 12.2 32bit SUSE 12.2 64bit Ubuntu 10.04 32bit Ubuntu 10.04 64bit Ubuntu 11.10 32bit Ubuntu 11.10 64bit Ubuntu 12.10 32bit Ubuntu 12.10 64bit Ubuntu 13.10 32bit Ubuntu 13.10 64bit Ubuntu 14.04 32bit Ubuntu 14.04 32bit Minimal Ubuntu 14.04 64bit Ubuntu 14.04 64bit Minimal So I have lots of choice But I was under the feeling that the best distro was centos 5 for acid.. (using the install script from the cd.. Unless you can point me in another direction.. From: Doug Crompton Sent: Wednesday, September 10, 2014 6:16 PM To: pete M Cc: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Pete, I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. 73 Doug WA3DSP http://www.crompton.com/hamradio From: petem001 at hotmail.com To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org Date: Wed, 10 Sep 2014 14:12:38 -0400 Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. If it would be installed at least up to a point. I would be able to do it.. I just dont know how to tell the compiler not to compile that part and go on.. From: kk6ecm at gmail.com Date: Wed, 10 Sep 2014 09:15:13 -0700 To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} Thanks, Bob kk6ecm Sent from iPad On Sep 10, 2014, at 8:30 AM, pete M wrote: OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? If I did I am sorry.. And I gave my apology to every one I could have offended.. But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. From: kk6ecm Sen t: Tuesday, September 09, 2014 1:40 PM To: APP RPT Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. Thanks, Bob kk6ecm Sent from iPad On Sep 9, 2014, at 8:27 AM, pete M wrote: Ok will try that.. thanks! From: Bob Sent: Tuesday, September 09, 2014 10:55 AM To: 'APP RPT' Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 I?ve done this several times without issue. Here are the steps I used. Load CentOS 5.10 downloaded from CentOS website No features, tools only, no desktop (competes with Asterisk) Set ssh /etc/ssh/sshd_config Run "setup" at comand line and disable firewall vi /etc/rc.d/acidrepo http://dl.allstarlink.org Execute portion of ks.cfg, each line at a time cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig cat <>/etc/rc.d/rc.local cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh chmod 755 /etc/rc.d/phase1.sh /etc/rc.d/phase1.sh Auto reboot after phase1.sh executed phase2.sh runs automatically to completion Bob kk6ecm From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M Sent: Tuesday, September 09, 2014 7:00 AM To: APP RPT Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. here is the out put from the script sh phase2.sh ****** Phase 2 post install ****** Getting asterisk install script from http://dl.allstarlink.org../. Getting files.tar.gz from http://dl.allstarlink.org../. ****** Asterisk Installation ****** /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found Unpacking files.tar.gz... Compiling Zaptel... checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preproc esso r... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/sh checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... no checking for initscr in -lncurses... no checking for pkg-config... No configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln< /font> checking for mkdir... /bin/mkdir checking for nroff... /usr/bin/nroff checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOU RC E -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeop ts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 Failure: Unable to compile Zaptel 2 Fatal error: Unable to install Asterisk! [root at node rc.d]# I dont know where to go from there.. Anyone care to help a bit? _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wlEmoticon-winkingsmile[1].png Type: image/png Size: 1135 bytes Desc: not available URL: From Bryan at bryanfields.net Sun Sep 14 03:13:48 2014 From: Bryan at bryanfields.net (Bryan Fields) Date: Sat, 13 Sep 2014 23:13:48 -0400 Subject: [App_rpt-users] rc.updatenodelist fails. Message-ID: <541507EC.8010306@bryanfields.net> This is not working, looks like all the servers are not responding. Problem retrieving node list from nodes1.allstarlink.org, trying another server Problem retrieving node list from nodes2.allstarlink.org, trying another server Problem retrieving node list from nodes3.allstarlink.org, trying another server Problem retrieving node list from nodes4.allstarlink.org, trying another server Problem retrieving node list from nodes1.allstarlink.org, trying another server Ideas? -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net From tim.sawyer at mac.com Sun Sep 14 03:19:57 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Sat, 13 Sep 2014 20:19:57 -0700 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com> <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com> Message-ID: <2788FE3C-9186-4192-ACC7-7DDF6B940F7B@mac.com> People have jumped on my butt for saying this before but I?ll say it again anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, especially one for $5/mo. I?m not going to tell you not to do it, but if you do manage to jump the hurdles of getting Asterisk installed on a hosted VPS, it may not work as it does on a $50 computer. -- Tim WD6AWP > On Sep 13, 2014, at 4:56 PM, pete M wrote: > > OK > > The GOAL: having a node without a radio on a server to use as a gateway of conference for a few repeaters around the Montreal region. I found a nice site where I can rent a small vps for 5$ a month. nothing fancy. I want to have that computer tu be my conference.. None of the site I have are either stable enough to host a nice conference or where I could have computer in a not arsh place, the bandwith is the issue. > > So I can load a lot of different distro, BUT they are fixe image to start with. Cnt ask to load the acid iso.. (this would of course fix every thing.) > > So the goal is not for fun I do need to make this work. > > Will work from there, will find some answer online for most of the stuff I need, But when it is directly related to app_rpt, here is my only source.. > > Now I know what version of asterisk to use, where to find it, same for dahdi and app_rpt.. will try to ork on that. will find that I need some library of other stuff enroute and other software.. but I will try.. > > Not such a noob in linux.. but not a pro.. thanks for you patience.. > > Pierre VE2PF > > > From: doug at crompton.com > To: petem001 at hotmail.com > CC: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > Date: Thu, 11 Sep 2014 23:49:25 -0400 > > First of all remind me - what is your end goal here. Are you doing this just for fun or is it for a real need and if so what is the need? > > The easiest thing to do might be to just download the BBB image at hamvoip.org. Write it to an SD card, mount it on Linux - ubuntu or whatever works. The root partition not the boot partition. Copy from everything from the mount point /usr/src/utils to /usr/src on your linux box. Also copy /etc/asterisk from the mount point to /etc/asterisk for all the config files. > > The source tree would then be in /usr/src/utils/asterisk - dahdi would also be there along with the patches in /usr/src/utils > > You can compile and intall both dahdi and asterisk from there. Then following the directions on the BBB page and howto on setting up your node. > > Another possible choice would be to just bring up a standard centos installation on a PC and copy what you need from there. All the source and files you would need would be there like the scripts in /usr/local/sbin. You would need to make some changes however. > > As Dave pointed out earlier you are in for some real bumps along the way. There will be packages you will need to download and things you will need to configure. It is not a 123 type of thing. Without some Linux experience it could be daunting. > > Just remember if you are using dahdi you need to remove any mention of zaptel and use the chan_dahdi.conf as shown in the BBB config. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: petem001 at hotmail.com > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > Date: Thu, 11 Sep 2014 22:19:19 -0400 > > OK Doug you got me fired up.. > > just one thing to know what source of asterisk are you using exactly? > > Got Dahdi got the patch.. will fix what's needed to be fixed about ntpd and all. But what damn source of asterisk are you using? ;-) > > > > > From: doug at crompton.com > To: petem001 at hotmail.com > CC: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > Date: Thu, 11 Sep 2014 13:15:14 -0400 > > Pete, > > I have done this so many times but unfortunately I never documented it. Here is a simple description. > > Get a distro and configure it like you normally would. Get ntpd running, network setup, etc. > > Download the acid code and the latest dahdi - > > I see it is 2.10.0 The last I used was 2.9.x but I suspect it will work the same. If not you could get the 2.9 version. > > http://www.asterisk.org/downloads/dahdi > > Apply the patch - info on how to do that is in the readme > > https://allstarlink.org/fixed-dahdi-patches.tar.gz > > Compile and install dahdi. > > Then compile and install asterisk > > Don't run any offsite updates. Configure it manually - not hard to do - and run. If you already have a configured system you can use those files from /etc.asterisk. BTW the BBB setup procedure and howto's at http://hamvoip.org describe how to do that very easily which would also apply here. The only caveat is the config files would be different to start with so some consideration has to be given to that. > > All that sounds easy but you undoubtedly will have some hiccups and things you will have to do to get it to work. It is impossible to document that as it would be different on the multitude of distros and kernel versions. > > I have compiled it on the latest Debian and Ubuntu. The real problem is OSS support which is required. Debian has it, Ubuntu does not. You have to recompile the kernel and add it back in. For that reason Ubuntu is not recommended as kernel versions can change with frequent updates. > > I guess the big question is do you really need to do this. I forget why you said you can't run a local system. In that case you could just install an acid release on a PC or maybe go with the BBB. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: petem001 at hotmail.com > To: doug at crompton.com > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > Date: Thu, 11 Sep 2014 12:08:04 -0400 > > well can you point me a few pointers on how to do so? > > Never patched some software before. > > > From: Doug Crompton > Sent: Thursday, September 11, 2014 11:03 AM > To: pete M > Cc: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I am not sure what you are saying when you comment.... > > "well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.." > > Did you mean "will" ?? The patches can be applied against the latest dahdi and it will compile on late kernels. The BBB is an example of that. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: petem001 at hotmail.com > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > Date: Thu, 11 Sep 2014 09:42:08 -0400 > > well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.. > > I can run the system on bunch of disto.. > > Here is the list.. > > > CentOS 5 32bit > CentOS 5 64bit > CentOS 6 32bit > CentOS 6 64bit > CentOS 7 64bit > CentOS 7 64bit Minimal > Debian 6 32bit > Debian 6 64bit > Debian 7 32bit > Debian 7 32bit Minimal > Debian 7 64bit > Debian 7 64bit Minimal > Fedora 17 32bit > Fedora 17 64bit > Fedora 19 32bit > Fedora 19 64bit > Starbound-Ubuntu 13.10 32bit > SUSE 12.2 32bit > SUSE 12.2 64bit > Ubuntu 10.04 32bit > Ubuntu 10.04 64bit > Ubuntu 11.10 32bit > Ubuntu 11.10 64bit > Ubuntu 12.10 32bit > Ubuntu 12.10 64bit > Ubuntu 13.10 32bit > Ubuntu 13.10 64bit > Ubuntu 14.04 32bit > Ubuntu 14.04 32bit Minimal > Ubuntu 14.04 64bit > Ubuntu 14.04 64bit Minimal > > So I have lots of choice > > But I was under the feeling that the best distro was centos 5 for acid.. (using the install script from the cd.. > > Unless you can point me in another direction.. > > > From: Doug Crompton > Sent: Wednesday, September 10, 2014 6:16 PM > To: pete M > Cc: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Pete, > > I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: petem001 at hotmail.com > To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org > Date: Wed, 10 Sep 2014 14:12:38 -0400 > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. > > If it would be installed at least up to a point. I would be able to do it.. > > I just dont know how to tell the compiler not to compile that part and go on.. > > > > From: kk6ecm at gmail.com > Date: Wed, 10 Sep 2014 09:15:13 -0700 > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. > > As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} > > Thanks, > Bob > kk6ecm > > Sent from iPad > > > On Sep 10, 2014, at 8:30 AM, pete M > wrote: > > OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? > > If I did I am sorry.. And I gave my apology to every one I could have offended.. > But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M > wrote: > > I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. > > I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. > > > > From: kk6ecm > Sen t: Tuesday, September 09, 2014 1:40 PM > To: APP RPT > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. > > Thanks, > Bob > kk6ecm > > Sent from iPad > > > On Sep 9, 2014, at 8:27 AM, pete M > wrote: > > Ok will try that.. > > thanks! > > > From: Bob > Sent: Tuesday, September 09, 2014 10:55 AM > To: 'APP RPT' > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > I?ve done this several times without issue. Here are the steps I used. > > Load CentOS 5.10 downloaded from CentOS website > No features, tools only, no desktop (competes with Asterisk) > Set ssh /etc/ssh/sshd_config > Run "setup" at comand line and disable firewall > vi /etc/rc.d/acidrepo > http://dl.allstarlink.org > Execute portion of ks.cfg, each line at a time > cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig > cat <>/etc/rc.d/rc.local > > cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh > > chmod 755 /etc/rc.d/phase1.sh > > /etc/rc.d/phase1.sh > Auto reboot after phase1.sh executed > phase2.sh runs automatically to completion > > Bob > kk6ecm > > From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org ] On Behalf Of pete M > Sent: Tuesday, September 09, 2014 7:00 AM > To: APP RPT > Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. > > I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. > > here is the out put from the script > > sh phase2.sh > ****** Phase 2 post install ****** > Getting asterisk install script from http://dl.allstarlink.org../ . > Getting files.tar.gz from http://dl.allstarlink.org../ . > ****** Asterisk Installation ****** > /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found > Unpacking files.tar.gz... > Compiling Zaptel... > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking how to run the C preproc esso r... gcc -E > checking for a BSD-compatible install... /usr/bin/install -c > checking whether ln -s works... yes > checking for GNU make... make > checking for grep... /bin/grep > checking for sh... /bin/sh > checking for ln... /bin/ln > checking for wget... /usr/bin/wget > checking for grep that handles long lines and -e... (cached) /bin/grep > checking for egrep... /bin/grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for initscr in -lcurses... no > checking for initscr in -lncurses... no > checking for newtBell in -lnewt... no > checking for usb_init in -lusb... no > configure: creating ./config.status > config.status: creating build_tools/menuselect-deps > config.status: creating makeopts > config.status: creating build_tools/make_firmware_object > configure: *** Zaptel build successfully configured *** > make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking for GNU make... make > checking for asprintf... yes > checking for getloadavg... yes > checking for setenv... yes > checking for strcasestr... yes > checking for strndup... yes > checking for strnlen... yes > checking for strsep... yes > checking for strtoq... yes > checking for unsetenv... yes > checking for vasprintf... yes > checking how to run the C preprocessor... gcc -E > checking for egrep... grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for initscr in -lcurses... no > checking for initscr in -lncurses... no > checking for pkg-config... No > configure: creating ./config.status > config.status: creating makeopts > config.status: creating autoconfig.h > configure: configuring in mxml > configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking for g++... no > checking for c++... no > checking for gpp... no > checking for aCC... no > checking for CC... no > checking for cxx... no > checking for cc++... no > checking for cl... no > checking for FCC... no > checking for KCC... no > checking for RCC... no > checking for xlC_r... no > checking for xlC... no > checking whether we are using the GNU C++ compiler... no > checking whether g++ accepts -g... no > checking for a BSD-compatible install... /usr/bin/install -c > checking for ranlib... ranlib > checking for ar... /usr/bin/ar > checking for cp... /bin/cp > checking for ln... /bin/ln< /font> > checking for mkdir... /bin/mkdir > checking for nroff... /usr/bin/nroff > checking for rm... /bin/rm > checking for strdup... yes > checking for vsnprintf... yes > configure: creating ./config.status > config.status: creating Makefile > config.status: creating mxml.list > config.status: creating mxml.pc > config.status: creating config.h > configure: Menuselect build configuration successfully completed > make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' > gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c > gcc -g -c -D_GNU_SOU RC E -Wall -c -o strcompat.o strcompat.c > gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c > make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' > gcc -O -Wall -c mxml-attr.c > gcc -O -Wall -c mxml-entity.c > gcc -O -Wall -c mxml-file.c > gcc -O -Wall -c mxml-index.c > gcc -O -Wall -c mxml-node.c > gcc -O -Wall -c mxml-search.c > gcc -O -Wall -c mxml-set.c > gcc -O -Wall -c mxml-private.c > gcc -O -Wall -c mxml-string.c > /bin/rm -f libmxml.a > /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o > a - mxml-attr.o > a - mxml-entity.o > a - mxml-file.o > a - mxml-index.o > a - mxml-node.o > a - mxml-search.o > a - mxml-set.o > a - mxml-private.o > a - mxml-string.o > ranlib libmxml.a > make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' > gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a > make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' > Generating input for menuselect ... > > *********************************************************** > The existing menuselect.makeop ts file did not specify > that 'zttool' should not be included. However, either some > dependencies for this module were not found or a > conflict exists. > > Either run 'make menuselect' or remove the existing > menuselect.makeopts file to resolve this issue. > *********************************************************** > > make: *** [menuselect.makeopts] Error 255 > Failure: Unable to compile Zaptel 2 > Fatal error: Unable to install Asterisk! > [root at node rc.d]# > > I dont know where to go from there.. > > Anyone care to help a bit? > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Sun Sep 14 03:23:41 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Sat, 13 Sep 2014 20:23:41 -0700 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: <541507EC.8010306@bryanfields.net> References: <541507EC.8010306@bryanfields.net> Message-ID: <6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com> Works for me? Resolving nodes1.allstarlink.org... 96.36.57.202 Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/plain] Saving to: `/var/lib/asterisk/rpt_extnodes-temp' [ <=> ] 64,417 225K/s in 0.3s 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' saved [64417] Retrieved node list from nodes1.allstarlink.org -- Tim WD6AWP > On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: > > This is not working, looks like all the servers are not responding. > > Problem retrieving node list from nodes1.allstarlink.org, trying another server > Problem retrieving node list from nodes2.allstarlink.org, trying another server > Problem retrieving node list from nodes3.allstarlink.org, trying another server > Problem retrieving node list from nodes4.allstarlink.org, trying another server > Problem retrieving node list from nodes1.allstarlink.org, trying another server > > Ideas? > > -- > Bryan Fields > > 727-409-1194 - Voice > 727-214-2508 - Fax > http://bryanfields.net > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. From Bryan at bryanfields.net Sun Sep 14 03:25:01 2014 From: Bryan at bryanfields.net (Bryan Fields) Date: Sat, 13 Sep 2014 23:25:01 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com> <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com> <2788FE3C-9186-4192-ACC7-7DDF6B940F7B@mac.com> Message-ID: <54150A8D.1000104@bryanfields.net> On 9/13/14, 11:19 PM, Tim Sawyer wrote: > People have jumped on my butt for saying this before but I?ll say it again > anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, > especially one for $5/mo. I?m not going to tell you not to do it, but if > you do manage to jump the hurdles of getting Asterisk installed on a hosted > VPS, it may not work as it does on a $50 computer. I second this. Asterisk is one of those programs that is very timing dependent. A virtual server, especially a $5/month VPS is not going to work well since there are 200 VM's all competing for processor time. This being said, there is no requirement that you run ACID. Grab it and compile from source, I dislike redhat/centos, and run on debian just fine. -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net From Bryan at bryanfields.net Sun Sep 14 03:32:27 2014 From: Bryan at bryanfields.net (Bryan Fields) Date: Sat, 13 Sep 2014 23:32:27 -0400 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: References: <541507EC.8010306@bryanfields.net> <6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com> Message-ID: <54150C4B.3050505@bryanfields.net> Thanks Tim, However, I'm getting 403 errors on each. Perhaps some kinda IP block issue or something? root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl --2014-09-13 23:26:54-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl Resolving nodes1.allstarlink.org... 96.36.57.202 Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. HTTP request sent, awaiting response... 403 2014-09-13 23:26:54 ERROR 403: (no description). root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl --2014-09-13 23:27:00-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl Resolving nodes2.allstarlink.org... 209.159.155.200 Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2014-09-13 23:27:00 ERROR 403: Forbidden. root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl --2014-09-13 23:27:06-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl Resolving nodes3.allstarlink.org... 65.110.110.172 Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. HTTP request sent, awaiting response... 403 2014-09-13 23:27:06 ERROR 403: (no description). root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl --2014-09-13 23:27:11-- http://nodes4.allstarlink.org/cgi-bin/nodes.pl Resolving nodes4.allstarlink.org... 67.214.190.109 Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2014-09-13 23:27:12 ERROR 403: Forbidden. On 9/13/14, 11:23 PM, Tim Sawyer wrote: > Works for me? > > > Resolving nodes1.allstarlink.org... 96.36.57.202 > Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: unspecified [text/plain] > Saving to: `/var/lib/asterisk/rpt_extnodes-temp' > > [ <=> ] 64,417 225K/s in 0.3s > > 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' saved [64417] > > Retrieved node list from nodes1.allstarlink.org > > -- > Tim WD6AWP > >> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: >> >> This is not working, looks like all the servers are not responding. >> >> Problem retrieving node list from nodes1.allstarlink.org, trying another server >> Problem retrieving node list from nodes2.allstarlink.org, trying another server >> Problem retrieving node list from nodes3.allstarlink.org, trying another server >> Problem retrieving node list from nodes4.allstarlink.org, trying another server >> Problem retrieving node list from nodes1.allstarlink.org, trying another server >> >> Ideas? >> >> -- >> Bryan Fields >> >> 727-409-1194 - Voice >> 727-214-2508 - Fax >> http://bryanfields.net >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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. > -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net From kk6ecm at gmail.com Sun Sep 14 03:50:11 2014 From: kk6ecm at gmail.com (Bob) Date: Sat, 13 Sep 2014 20:50:11 -0700 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: <54150C4B.3050505@bryanfields.net> References: <541507EC.8010306@bryanfields.net><6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com> <54150C4B.3050505@bryanfields.net> Message-ID: Works fine here. -----Original Message----- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan Fields Sent: Saturday, September 13, 2014 8:32 PM To: Tim Sawyer; APP RPT Subject: Re: [App_rpt-users] rc.updatenodelist fails. Thanks Tim, However, I'm getting 403 errors on each. Perhaps some kinda IP block issue or something? root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl --2014-09-13 23:26:54-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl Resolving nodes1.allstarlink.org... 96.36.57.202 Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. HTTP request sent, awaiting response... 403 2014-09-13 23:26:54 ERROR 403: (no description). root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl --2014-09-13 23:27:00-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl Resolving nodes2.allstarlink.org... 209.159.155.200 Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2014-09-13 23:27:00 ERROR 403: Forbidden. root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl --2014-09-13 23:27:06-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl Resolving nodes3.allstarlink.org... 65.110.110.172 Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. HTTP request sent, awaiting response... 403 2014-09-13 23:27:06 ERROR 403: (no description). root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl --2014-09-13 23:27:11-- http://nodes4.allstarlink.org/cgi-bin/nodes.pl Resolving nodes4.allstarlink.org... 67.214.190.109 Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2014-09-13 23:27:12 ERROR 403: Forbidden. On 9/13/14, 11:23 PM, Tim Sawyer wrote: > Works for me. > > > Resolving nodes1.allstarlink.org... 96.36.57.202 > Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: unspecified [text/plain] > Saving to: `/var/lib/asterisk/rpt_extnodes-temp' > > [ <=> ] 64,417 225K/s in 0.3s > > 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' saved [64417] > > Retrieved node list from nodes1.allstarlink.org > > -- > Tim WD6AWP > >> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: >> >> This is not working, looks like all the servers are not responding. >> >> Problem retrieving node list from nodes1.allstarlink.org, trying another server >> Problem retrieving node list from nodes2.allstarlink.org, trying another server >> Problem retrieving node list from nodes3.allstarlink.org, trying another server >> Problem retrieving node list from nodes4.allstarlink.org, trying another server >> Problem retrieving node list from nodes1.allstarlink.org, trying another server >> >> Ideas? >> >> -- >> Bryan Fields >> >> 727-409-1194 - Voice >> 727-214-2508 - Fax >> http://bryanfields.net >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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. > -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. From Bryan at bryanfields.net Sun Sep 14 03:58:21 2014 From: Bryan at bryanfields.net (Bryan Fields) Date: Sat, 13 Sep 2014 23:58:21 -0400 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: References: <541507EC.8010306@bryanfields.net><6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com> <54150C4B.3050505@bryanfields.net> Message-ID: <5415125D.3090304@bryanfields.net> I've had three other people on IRC test this and I've tested this from 3 different servers myself. All are giving an error 403 on: http://nodes1.allstarlink.org/cgi-bin/nodes.pl I don't think it's just me :( On 9/13/14, 11:50 PM, Bob wrote: > Works fine here. > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan Fields > Sent: Saturday, September 13, 2014 8:32 PM > To: Tim Sawyer; APP RPT > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > Thanks Tim, > > However, I'm getting 403 errors on each. > > Perhaps some kinda IP block issue or something? > > root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl > --2014-09-13 23:26:54-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl > Resolving nodes1.allstarlink.org... 96.36.57.202 > Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > HTTP request sent, awaiting response... 403 > 2014-09-13 23:26:54 ERROR 403: (no description). > > root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl > --2014-09-13 23:27:00-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl > Resolving nodes2.allstarlink.org... 209.159.155.200 > Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. > HTTP request sent, awaiting response... 403 Forbidden > 2014-09-13 23:27:00 ERROR 403: Forbidden. > > root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl > --2014-09-13 23:27:06-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl > Resolving nodes3.allstarlink.org... 65.110.110.172 > Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. > HTTP request sent, awaiting response... 403 > 2014-09-13 23:27:06 ERROR 403: (no description). > > root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl > --2014-09-13 23:27:11-- http://nodes4.allstarlink.org/cgi-bin/nodes.pl > Resolving nodes4.allstarlink.org... 67.214.190.109 > Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. > HTTP request sent, awaiting response... 403 Forbidden > 2014-09-13 23:27:12 ERROR 403: Forbidden. > > > > > > On 9/13/14, 11:23 PM, Tim Sawyer wrote: >> Works for me. >> >> >> Resolving nodes1.allstarlink.org... 96.36.57.202 >> Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. >> HTTP request sent, awaiting response... 200 OK >> Length: unspecified [text/plain] >> Saving to: `/var/lib/asterisk/rpt_extnodes-temp' >> >> [ <=> > ] 64,417 225K/s in 0.3s >> >> 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' > saved [64417] >> >> Retrieved node list from nodes1.allstarlink.org >> >> -- >> Tim WD6AWP >> >>> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: >>> >>> This is not working, looks like all the servers are not responding. >>> >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > server >>> Problem retrieving node list from nodes2.allstarlink.org, trying another > server >>> Problem retrieving node list from nodes3.allstarlink.org, trying another > server >>> Problem retrieving node list from nodes4.allstarlink.org, trying another > server >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > server >>> >>> Ideas? >>> >>> -- >>> Bryan Fields >>> >>> 727-409-1194 - Voice >>> 727-214-2508 - Fax >>> http://bryanfields.net >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at 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. >> > > -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net From kk6ecm at gmail.com Sun Sep 14 04:12:57 2014 From: kk6ecm at gmail.com (Bob) Date: Sat, 13 Sep 2014 21:12:57 -0700 Subject: [App_rpt-users] Multiple requests for registration In-Reply-To: References: <1857007D3A0D4789A90DD7BEBDA40C9B@ThePykesHP> Message-ID: Why is it sending a "registry rereqquest? "Should I be receiving some sort of confirmation (feedback of success)? Thanks, Bob kk6ecm _____ From: outlook_97fc649978f54bf0 at outlook.com [mailto:outlook_97fc649978f54bf0 at outlook.com] On Behalf Of Doug Crompton Sent: Friday, September 12, 2014 5:35 PM To: Bob Cc: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Multiple requests for registration The registration interval is 60 seconds hard coded in the source. So what you see is normal. 73 Doug WA3DSP http://www.crompton.com/hamradio _____ From: kk6ecm at gmail.com To: App_rpt-users at ohnosec.org Date: Fri, 12 Sep 2014 17:02:30 -0700 Subject: [App_rpt-users] Multiple requests for registration My servers are constantly sending registration request and rereqquests. I check two different ones on two different IP addresses at two different locations, although the same ISP. I don't ever remember this happening this much, at this frequency. I'm wondering if there is something I need to fix. Also, is the frequency of these requests adjustable on my end, and is it anything I need to do? The data below is from one server. The other server looks pretty much the same. This one also has Echolink, and I get an Echolink update occasionally interspersed between large groups of the warnings shown below. Thanks, Bob kk6ecm [Sep 12 23:48:34] WARNING[456]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '29009' [Sep 12 23:48:34] WARNING[459]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest [Sep 12 23:48:44] WARNING[452]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '28765' [Sep 12 23:48:45] WARNING[454]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest [Sep 12 23:49:24] WARNING[459]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '29009' [Sep 12 23:49:24] WARNING[458]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest [Sep 12 23:49:35] WARNING[454]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '28765' [Sep 12 23:49:35] WARNING[456]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Sun Sep 14 04:08:08 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Sat, 13 Sep 2014 21:08:08 -0700 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: <5415125D.3090304@bryanfields.net> References: <541507EC.8010306@bryanfields.net> <6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com> <54150C4B.3050505@bryanfields.net> <5415125D.3090304@bryanfields.net> Message-ID: <686511C0-AB84-401D-9119-B949E53A3730@mac.com> Forwarded to the Duuude. We?ll see what gives. -- Tim :wq On Sep 13, 2014, at 8:58 PM, Bryan Fields wrote: > I've had three other people on IRC test this and I've tested this from 3 > different servers myself. > > All are giving an error 403 on: > > http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > I don't think it's just me :( > > > On 9/13/14, 11:50 PM, Bob wrote: >> Works fine here. >> >> -----Original Message----- >> From: app_rpt-users-bounces at ohnosec.org >> [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan Fields >> Sent: Saturday, September 13, 2014 8:32 PM >> To: Tim Sawyer; APP RPT >> Subject: Re: [App_rpt-users] rc.updatenodelist fails. >> >> Thanks Tim, >> >> However, I'm getting 403 errors on each. >> >> Perhaps some kinda IP block issue or something? >> >> root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl >> --2014-09-13 23:26:54-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl >> Resolving nodes1.allstarlink.org... 96.36.57.202 >> Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. >> HTTP request sent, awaiting response... 403 >> 2014-09-13 23:26:54 ERROR 403: (no description). >> >> root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl >> --2014-09-13 23:27:00-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl >> Resolving nodes2.allstarlink.org... 209.159.155.200 >> Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. >> HTTP request sent, awaiting response... 403 Forbidden >> 2014-09-13 23:27:00 ERROR 403: Forbidden. >> >> root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl >> --2014-09-13 23:27:06-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl >> Resolving nodes3.allstarlink.org... 65.110.110.172 >> Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. >> HTTP request sent, awaiting response... 403 >> 2014-09-13 23:27:06 ERROR 403: (no description). >> >> root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl >> --2014-09-13 23:27:11-- http://nodes4.allstarlink.org/cgi-bin/nodes.pl >> Resolving nodes4.allstarlink.org... 67.214.190.109 >> Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. >> HTTP request sent, awaiting response... 403 Forbidden >> 2014-09-13 23:27:12 ERROR 403: Forbidden. >> >> >> >> >> >> On 9/13/14, 11:23 PM, Tim Sawyer wrote: >>> Works for me. >>> >>> >>> Resolving nodes1.allstarlink.org... 96.36.57.202 >>> Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. >>> HTTP request sent, awaiting response... 200 OK >>> Length: unspecified [text/plain] >>> Saving to: `/var/lib/asterisk/rpt_extnodes-temp' >>> >>> [ <=> >> ] 64,417 225K/s in 0.3s >>> >>> 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' >> saved [64417] >>> >>> Retrieved node list from nodes1.allstarlink.org >>> >>> -- >>> Tim WD6AWP >>> >>>> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: >>>> >>>> This is not working, looks like all the servers are not responding. >>>> >>>> Problem retrieving node list from nodes1.allstarlink.org, trying another >> server >>>> Problem retrieving node list from nodes2.allstarlink.org, trying another >> server >>>> Problem retrieving node list from nodes3.allstarlink.org, trying another >> server >>>> Problem retrieving node list from nodes4.allstarlink.org, trying another >> server >>>> Problem retrieving node list from nodes1.allstarlink.org, trying another >> server >>>> >>>> Ideas? >>>> >>>> -- >>>> Bryan Fields >>>> >>>> 727-409-1194 - Voice >>>> 727-214-2508 - Fax >>>> http://bryanfields.net >>>> >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at 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. >>> >> >> > > > -- > Bryan Fields > > 727-409-1194 - Voice > 727-214-2508 - Fax > http://bryanfields.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Sun Sep 14 04:14:58 2014 From: telesistant at hotmail.com (Jim Duuuude) Date: Sat, 13 Sep 2014 21:14:58 -0700 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: <5415125D.3090304@bryanfields.net> References: <541507EC.8010306@bryanfields.net><6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com>, <54150C4B.3050505@bryanfields.net>, , , <5415125D.3090304@bryanfields.net> Message-ID: It not going to work unless you attempt access from an IP address that has a registered Allstar node. The registration server makes an 'allow list' based upon the IP addresses from which you register your Allstar node. Jim > Date: Sat, 13 Sep 2014 23:58:21 -0400 > From: Bryan at bryanfields.net > To: kk6ecm at gmail.com; tim.sawyer at mac.com; app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > I've had three other people on IRC test this and I've tested this from 3 > different servers myself. > > All are giving an error 403 on: > > http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > I don't think it's just me :( > > > On 9/13/14, 11:50 PM, Bob wrote: > > Works fine here. > > > > -----Original Message----- > > From: app_rpt-users-bounces at ohnosec.org > > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan Fields > > Sent: Saturday, September 13, 2014 8:32 PM > > To: Tim Sawyer; APP RPT > > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > > > Thanks Tim, > > > > However, I'm getting 403 errors on each. > > > > Perhaps some kinda IP block issue or something? > > > > root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:26:54-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes1.allstarlink.org... 96.36.57.202 > > Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > > HTTP request sent, awaiting response... 403 > > 2014-09-13 23:26:54 ERROR 403: (no description). > > > > root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:00-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes2.allstarlink.org... 209.159.155.200 > > Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2014-09-13 23:27:00 ERROR 403: Forbidden. > > > > root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:06-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes3.allstarlink.org... 65.110.110.172 > > Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. > > HTTP request sent, awaiting response... 403 > > 2014-09-13 23:27:06 ERROR 403: (no description). > > > > root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:11-- http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes4.allstarlink.org... 67.214.190.109 > > Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2014-09-13 23:27:12 ERROR 403: Forbidden. > > > > > > > > > > > > On 9/13/14, 11:23 PM, Tim Sawyer wrote: > >> Works for me. > >> > >> > >> Resolving nodes1.allstarlink.org... 96.36.57.202 > >> Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > >> HTTP request sent, awaiting response... 200 OK > >> Length: unspecified [text/plain] > >> Saving to: `/var/lib/asterisk/rpt_extnodes-temp' > >> > >> [ <=> > > ] 64,417 225K/s in 0.3s > >> > >> 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' > > saved [64417] > >> > >> Retrieved node list from nodes1.allstarlink.org > >> > >> -- > >> Tim WD6AWP > >> > >>> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: > >>> > >>> This is not working, looks like all the servers are not responding. > >>> > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes2.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes3.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes4.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > server > >>> > >>> Ideas? > >>> > >>> -- > >>> Bryan Fields > >>> > >>> 727-409-1194 - Voice > >>> 727-214-2508 - Fax > >>> http://bryanfields.net > >>> > >>> _______________________________________________ > >>> App_rpt-users mailing list > >>> App_rpt-users at 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. > >> > > > > > > > -- > Bryan Fields > > 727-409-1194 - Voice > 727-214-2508 - Fax > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Sun Sep 14 04:19:18 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Sat, 13 Sep 2014 21:19:18 -0700 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: References: <541507EC.8010306@bryanfields.net> <6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com> <54150C4B.3050505@bryanfields.net> <5415125D.3090304@bryanfields.net> Message-ID: <6798E2BE-B945-448C-8FD9-9E098F8D6521@mac.com> I guess I should have known that, thanks Jim. -- Tim :wq On Sep 13, 2014, at 9:14 PM, Jim Duuuude wrote: > It not going to work unless you attempt access from an IP address that has > a registered Allstar node. The registration server makes an 'allow list' based upon > the IP addresses from which you register your Allstar node. > > Jim > > > Date: Sat, 13 Sep 2014 23:58:21 -0400 > > From: Bryan at bryanfields.net > > To: kk6ecm at gmail.com; tim.sawyer at mac.com; app_rpt-users at ohnosec.org > > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > > > I've had three other people on IRC test this and I've tested this from 3 > > different servers myself. > > > > All are giving an error 403 on: > > > > http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > > > I don't think it's just me :( > > > > > > On 9/13/14, 11:50 PM, Bob wrote: > > > Works fine here. > > > > > > -----Original Message----- > > > From: app_rpt-users-bounces at ohnosec.org > > > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan Fields > > > Sent: Saturday, September 13, 2014 8:32 PM > > > To: Tim Sawyer; APP RPT > > > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > > > > > Thanks Tim, > > > > > > However, I'm getting 403 errors on each. > > > > > > Perhaps some kinda IP block issue or something? > > > > > > root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > > --2014-09-13 23:26:54-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > > Resolving nodes1.allstarlink.org... 96.36.57.202 > > > Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > > > HTTP request sent, awaiting response... 403 > > > 2014-09-13 23:26:54 ERROR 403: (no description). > > > > > > root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > > --2014-09-13 23:27:00-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > > Resolving nodes2.allstarlink.org... 209.159.155.200 > > > Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. > > > HTTP request sent, awaiting response... 403 Forbidden > > > 2014-09-13 23:27:00 ERROR 403: Forbidden. > > > > > > root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > > --2014-09-13 23:27:06-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > > Resolving nodes3.allstarlink.org... 65.110.110.172 > > > Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. > > > HTTP request sent, awaiting response... 403 > > > 2014-09-13 23:27:06 ERROR 403: (no description). > > > > > > root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > > --2014-09-13 23:27:11-- http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > > Resolving nodes4.allstarlink.org... 67.214.190.109 > > > Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. > > > HTTP request sent, awaiting response... 403 Forbidden > > > 2014-09-13 23:27:12 ERROR 403: Forbidden. > > > > > > > > > > > > > > > > > > On 9/13/14, 11:23 PM, Tim Sawyer wrote: > > >> Works for me. > > >> > > >> > > >> Resolving nodes1.allstarlink.org... 96.36.57.202 > > >> Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > > >> HTTP request sent, awaiting response... 200 OK > > >> Length: unspecified [text/plain] > > >> Saving to: `/var/lib/asterisk/rpt_extnodes-temp' > > >> > > >> [ <=> > > > ] 64,417 225K/s in 0.3s > > >> > > >> 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' > > > saved [64417] > > >> > > >> Retrieved node list from nodes1.allstarlink.org > > >> > > >> -- > > >> Tim WD6AWP > > >> > > >>> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: > > >>> > > >>> This is not working, looks like all the servers are not responding. > > >>> > > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > > server > > >>> Problem retrieving node list from nodes2.allstarlink.org, trying another > > > server > > >>> Problem retrieving node list from nodes3.allstarlink.org, trying another > > > server > > >>> Problem retrieving node list from nodes4.allstarlink.org, trying another > > > server > > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > > server > > >>> > > >>> Ideas? > > >>> > > >>> -- > > >>> Bryan Fields > > >>> > > >>> 727-409-1194 - Voice > > >>> 727-214-2508 - Fax > > >>> http://bryanfields.net > > >>> > > >>> _______________________________________________ > > >>> App_rpt-users mailing list > > >>> App_rpt-users at 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. > > >> > > > > > > > > > > > > -- > > Bryan Fields > > > > 727-409-1194 - Voice > > 727-214-2508 - Fax > > http://bryanfields.net > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Sun Sep 14 04:20:55 2014 From: Bryan at bryanfields.net (Bryan Fields) Date: Sun, 14 Sep 2014 00:20:55 -0400 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: References: <541507EC.8010306@bryanfields.net><6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com>, <54150C4B.3050505@bryanfields.net>, , , <5415125D.3090304@bryanfields.net> Message-ID: <541517A7.1050301@bryanfields.net> Ok, good to know. Maybe we can put that in the docs, as it had me fooled trying to troubleshoot it. I'm running it from asterisk.kb9mci.net, 44.98.254.236 which is registered in the portal for node 40821, and it's still giving an error 403. How often does it update the ACL for the server? I've had to move the server recently. Thanks, On 9/14/14, 12:14 AM, Jim Duuuude wrote: > It not going to work unless you attempt access from an IP address that has > a registered Allstar node. The registration server makes an 'allow list' based upon > the IP addresses from which you register your Allstar node. -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net From doug at crompton.com Sun Sep 14 04:21:46 2014 From: doug at crompton.com (Doug Crompton) Date: Sun, 14 Sep 2014 00:21:46 -0400 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: <5415125D.3090304@bryanfields.net> References: <541507EC.8010306@bryanfields.net><6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com>, <54150C4B.3050505@bryanfields.net>, , , <5415125D.3090304@bryanfields.net> Message-ID: No problem on Comcast in Philadelphia. Did you do a traceroute? 73 Doug WA3DSP http://www.crompton.com/hamradio > Date: Sat, 13 Sep 2014 23:58:21 -0400 > From: Bryan at bryanfields.net > To: kk6ecm at gmail.com; tim.sawyer at mac.com; app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > I've had three other people on IRC test this and I've tested this from 3 > different servers myself. > > All are giving an error 403 on: > > http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > I don't think it's just me :( > > > On 9/13/14, 11:50 PM, Bob wrote: > > Works fine here. > > > > -----Original Message----- > > From: app_rpt-users-bounces at ohnosec.org > > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan Fields > > Sent: Saturday, September 13, 2014 8:32 PM > > To: Tim Sawyer; APP RPT > > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > > > Thanks Tim, > > > > However, I'm getting 403 errors on each. > > > > Perhaps some kinda IP block issue or something? > > > > root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:26:54-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes1.allstarlink.org... 96.36.57.202 > > Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > > HTTP request sent, awaiting response... 403 > > 2014-09-13 23:26:54 ERROR 403: (no description). > > > > root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:00-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes2.allstarlink.org... 209.159.155.200 > > Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2014-09-13 23:27:00 ERROR 403: Forbidden. > > > > root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:06-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes3.allstarlink.org... 65.110.110.172 > > Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. > > HTTP request sent, awaiting response... 403 > > 2014-09-13 23:27:06 ERROR 403: (no description). > > > > root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:11-- http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes4.allstarlink.org... 67.214.190.109 > > Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2014-09-13 23:27:12 ERROR 403: Forbidden. > > > > > > > > > > > > On 9/13/14, 11:23 PM, Tim Sawyer wrote: > >> Works for me. > >> > >> > >> Resolving nodes1.allstarlink.org... 96.36.57.202 > >> Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > >> HTTP request sent, awaiting response... 200 OK > >> Length: unspecified [text/plain] > >> Saving to: `/var/lib/asterisk/rpt_extnodes-temp' > >> > >> [ <=> > > ] 64,417 225K/s in 0.3s > >> > >> 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' > > saved [64417] > >> > >> Retrieved node list from nodes1.allstarlink.org > >> > >> -- > >> Tim WD6AWP > >> > >>> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: > >>> > >>> This is not working, looks like all the servers are not responding. > >>> > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes2.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes3.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes4.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > server > >>> > >>> Ideas? > >>> > >>> -- > >>> Bryan Fields > >>> > >>> 727-409-1194 - Voice > >>> 727-214-2508 - Fax > >>> http://bryanfields.net > >>> > >>> _______________________________________________ > >>> App_rpt-users mailing list > >>> App_rpt-users at 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. > >> > > > > > > > -- > Bryan Fields > > 727-409-1194 - Voice > 727-214-2508 - Fax > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sun Sep 14 04:25:07 2014 From: doug at crompton.com (Doug Crompton) Date: Sun, 14 Sep 2014 00:25:07 -0400 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: <5415125D.3090304@bryanfields.net> References: <541507EC.8010306@bryanfields.net><6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com>, <54150C4B.3050505@bryanfields.net>, , , <5415125D.3090304@bryanfields.net> Message-ID: Can you ping the address? [root at node40961 local]# ping http://nodes1.allstarlink.org/cgi-bin/nodes.pl ping: unknown host http://nodes1.allstarlink.org/cgi-bin/nodes.pl [root at node40961 local]# ping nodes1.allstarlink.org PING nodes1.allstarlink.org (96.36.57.202) 56(84) bytes of data. 64 bytes from 96.36.57.202: icmp_seq=1 ttl=49 time=42.2 ms 64 bytes from 96.36.57.202: icmp_seq=2 ttl=49 time=41.7 ms 64 bytes from 96.36.57.202: icmp_seq=3 ttl=49 time=40.9 ms 73 Doug WA3DSP http://www.crompton.com/hamradio > Date: Sat, 13 Sep 2014 23:58:21 -0400 > From: Bryan at bryanfields.net > To: kk6ecm at gmail.com; tim.sawyer at mac.com; app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > I've had three other people on IRC test this and I've tested this from 3 > different servers myself. > > All are giving an error 403 on: > > http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > I don't think it's just me :( > > > On 9/13/14, 11:50 PM, Bob wrote: > > Works fine here. > > > > -----Original Message----- > > From: app_rpt-users-bounces at ohnosec.org > > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan Fields > > Sent: Saturday, September 13, 2014 8:32 PM > > To: Tim Sawyer; APP RPT > > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > > > Thanks Tim, > > > > However, I'm getting 403 errors on each. > > > > Perhaps some kinda IP block issue or something? > > > > root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:26:54-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes1.allstarlink.org... 96.36.57.202 > > Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > > HTTP request sent, awaiting response... 403 > > 2014-09-13 23:26:54 ERROR 403: (no description). > > > > root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:00-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes2.allstarlink.org... 209.159.155.200 > > Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2014-09-13 23:27:00 ERROR 403: Forbidden. > > > > root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:06-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes3.allstarlink.org... 65.110.110.172 > > Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. > > HTTP request sent, awaiting response... 403 > > 2014-09-13 23:27:06 ERROR 403: (no description). > > > > root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:11-- http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes4.allstarlink.org... 67.214.190.109 > > Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2014-09-13 23:27:12 ERROR 403: Forbidden. > > > > > > > > > > > > On 9/13/14, 11:23 PM, Tim Sawyer wrote: > >> Works for me. > >> > >> > >> Resolving nodes1.allstarlink.org... 96.36.57.202 > >> Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > >> HTTP request sent, awaiting response... 200 OK > >> Length: unspecified [text/plain] > >> Saving to: `/var/lib/asterisk/rpt_extnodes-temp' > >> > >> [ <=> > > ] 64,417 225K/s in 0.3s > >> > >> 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' > > saved [64417] > >> > >> Retrieved node list from nodes1.allstarlink.org > >> > >> -- > >> Tim WD6AWP > >> > >>> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: > >>> > >>> This is not working, looks like all the servers are not responding. > >>> > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes2.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes3.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes4.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > server > >>> > >>> Ideas? > >>> > >>> -- > >>> Bryan Fields > >>> > >>> 727-409-1194 - Voice > >>> 727-214-2508 - Fax > >>> http://bryanfields.net > >>> > >>> _______________________________________________ > >>> App_rpt-users mailing list > >>> App_rpt-users at 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. > >> > > > > > > > -- > Bryan Fields > > 727-409-1194 - Voice > 727-214-2508 - Fax > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at controlservers.net Sun Sep 14 04:35:02 2014 From: robert at controlservers.net (Robert) Date: Sat, 13 Sep 2014 21:35:02 -0700 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: References: <541507EC.8010306@bryanfields.net><6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com>, <54150C4B.3050505@bryanfields.net>, , , <5415125D.3090304@bryanfields.net> Message-ID: <2F78819053524A1EBE2F7B4D2B8B9BAB@desktop> I don't know how I got switched to digest or direct mail but I can reach the URL several ways from one of my dedicated servers and it isn't registered yet for Allstar. It will be as soon as we hook up the new RTCM :-) I hope that this helps some. _____ From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Jim Duuuude Sent: Saturday, September 13, 2014 9:15 PM To: Bryan Fields; Bob; 'Tim Sawyer'; app_rpt mailing list Subject: Re: [App_rpt-users] rc.updatenodelist fails. It not going to work unless you attempt access from an IP address that has a registered Allstar node. The registration server makes an 'allow list' based upon the IP addresses from which you register your Allstar node. Jim > Date: Sat, 13 Sep 2014 23:58:21 -0400 > From: Bryan at bryanfields.net > To: kk6ecm at gmail.com; tim.sawyer at mac.com; app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > I've had three other people on IRC test this and I've tested this from 3 > different servers myself. > > All are giving an error 403 on: > > http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > I don't think it's just me :( > > > On 9/13/14, 11:50 PM, Bob wrote: > > Works fine here. > > > > -----Original Message----- > > From: app_rpt-users-bounces at ohnosec.org > > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan Fields > > Sent: Saturday, September 13, 2014 8:32 PM > > To: Tim Sawyer; APP RPT > > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > > > Thanks Tim, > > > > However, I'm getting 403 errors on each. > > > > Perhaps some kinda IP block issue or something? > > > > root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:26:54-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes1.allstarlink.org... 96.36.57.202 > > Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > > HTTP request sent, awaiting response... 403 > > 2014-09-13 23:26:54 ERROR 403: (no description). > > > > root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:00-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes2.allstarlink.org... 209.159.155.200 > > Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2014-09-13 23:27:00 ERROR 403: Forbidden. > > > > root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:06-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes3.allstarlink.org... 65.110.110.172 > > Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. > > HTTP request sent, awaiting response... 403 > > 2014-09-13 23:27:06 ERROR 403: (no description). > > > > root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:11-- http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes4.allstarlink.org... 67.214.190.109 > > Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2014-09-13 23:27:12 ERROR 403: Forbidden. > > > > > > > > > > > > On 9/13/14, 11:23 PM, Tim Sawyer wrote: > >> Works for me. > >> > >> > >> Resolving nodes1.allstarlink.org... 96.36.57.202 > >> Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > >> HTTP request sent, awaiting response... 200 OK > >> Length: unspecified [text/plain] > >> Saving to: `/var/lib/asterisk/rpt_extnodes-temp' > >> > >> [ <=> > > ] 64,417 225K/s in 0.3s > >> > >> 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' > > saved [64417] > >> > >> Retrieved node list from nodes1.allstarlink.org > >> > >> -- > >> Tim WD6AWP > >> > >>> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: > >>> > >>> This is not working, looks like all the servers are not responding. > >>> > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes2.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes3.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes4.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > server > >>> > >>> Ideas? > >>> > >>> -- > >>> Bryan Fields > >>> > >>> 727-409-1194 - Voice > >>> 727-214-2508 - Fax > >>> http://bryanfields.net > >>> > >>> _______________________________________________ > >>> App_rpt-users mailing list > >>> App_rpt-users at 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. > >> > > > > > > > -- > Bryan Fields > > 727-409-1194 - Voice > 727-214-2508 - Fax > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Sun Sep 14 04:36:13 2014 From: Bryan at bryanfields.net (Bryan Fields) Date: Sun, 14 Sep 2014 00:36:13 -0400 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: References: <541507EC.8010306@bryanfields.net><6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com>, <54150C4B.3050505@bryanfields.net>, , , <5415125D.3090304@bryanfields.net> <541517A7.1050301@bryanfields.net> Message-ID: <54151B3D.1080501@bryanfields.net> It appears to be working now. I didn't do anything, so perhaps it aged out or something. Thanks Duuuuude On 9/14/14, 12:20 AM, Bryan Fields wrote: > Ok, good to know. Maybe we can put that in the docs, as it had me fooled > trying to troubleshoot it. > > I'm running it from asterisk.kb9mci.net, 44.98.254.236 which is registered in > the portal for node 40821, and it's still giving an error 403. > > How often does it update the ACL for the server? I've had to move the server > recently. > > Thanks, > > On 9/14/14, 12:14 AM, Jim Duuuude wrote: >> It not going to work unless you attempt access from an IP address that has >> a registered Allstar node. The registration server makes an 'allow list' based upon >> the IP addresses from which you register your Allstar node. > > -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net From telesistant at hotmail.com Sun Sep 14 04:56:03 2014 From: telesistant at hotmail.com (Jim Duuuude) Date: Sat, 13 Sep 2014 21:56:03 -0700 Subject: [App_rpt-users] Multiple requests for registration In-Reply-To: References: <1857007D3A0D4789A90DD7BEBDA40C9B@ThePykesHP>, , Message-ID: These are normal messages. Dont worry about them. Normally, people run their verbose level lower then whatever you have it set to, and dont see them. What verbose level are you running at? Jim From: kk6ecm at gmail.com To: app_rpt-users at ohnosec.org Date: Sat, 13 Sep 2014 21:12:57 -0700 Subject: Re: [App_rpt-users] Multiple requests for registration Why is it sending a ?registry rereqquest? ?Should I be receiving some sort of confirmation (feedback of success)? Thanks, Bob kk6ecm From: outlook_97fc649978f54bf0 at outlook.com [mailto:outlook_97fc649978f54bf0 at outlook.com] On Behalf Of Doug Crompton Sent: Friday, September 12, 2014 5:35 PM To: Bob Cc: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Multiple requests for registration The registration interval is 60 seconds hard coded in the source. So what you see is normal. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kk6ecm at gmail.com To: App_rpt-users at ohnosec.org Date: Fri, 12 Sep 2014 17:02:30 -0700 Subject: [App_rpt-users] Multiple requests for registration My servers are constantly sending registration request and rereqquests. I check two different ones on two different IP addresses at two different locations, although the same ISP. I don?t ever remember this happening this much, at this frequency. I?m wondering if there is something I need to fix. Also, is the frequency of these requests adjustable on my end, and is it anything I need to do? The data below is from one server. The other server looks pretty much the same. This one also has Echolink, and I get an Echolink update occasionally interspersed between large groups of the warnings shown below. Thanks, Bob kk6ecm [Sep 12 23:48:34] WARNING[456]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '29009' [Sep 12 23:48:34] WARNING[459]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest [Sep 12 23:48:44] WARNING[452]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '28765' [Sep 12 23:48:45] WARNING[454]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest [Sep 12 23:49:24] WARNING[459]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '29009' [Sep 12 23:49:24] WARNING[458]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest [Sep 12 23:49:35] WARNING[454]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '28765' [Sep 12 23:49:35] WARNING[456]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sun Sep 14 05:09:52 2014 From: doug at crompton.com (Doug Crompton) Date: Sun, 14 Sep 2014 01:09:52 -0400 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: <2F78819053524A1EBE2F7B4D2B8B9BAB@desktop> References: <541507EC.8010306@bryanfields.net><6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com>, , <54150C4B.3050505@bryanfields.net>, , , , , , <5415125D.3090304@bryanfields.net>, , <2F78819053524A1EBE2F7B4D2B8B9BAB@desktop> Message-ID: It will work for the registered public IP address. So any computer behind that router would be able to access it. If you have another server registered on a different port it is still the same IP address to the server. 73 Doug WA3DSP http://www.crompton.com/hamradio From: robert at controlservers.net To: telesistant at hotmail.com; bryan at bryanfields.net; kk6ecm at gmail.com; tim.sawyer at mac.com; app_rpt-users at ohnosec.org Date: Sat, 13 Sep 2014 21:35:02 -0700 Subject: Re: [App_rpt-users] rc.updatenodelist fails. I don?t know how I got switched to digest or direct mail but I can reach the URL several ways from one of my dedicated servers and it isn?t registered yet for Allstar. It will be as soon as we hook up the new RTCM J I hope that this helps some. From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Jim Duuuude Sent: Saturday, September 13, 2014 9:15 PM To: Bryan Fields; Bob; 'Tim Sawyer'; app_rpt mailing list Subject: Re: [App_rpt-users] rc.updatenodelist fails. It not going to work unless you attempt access from an IP address that has a registered Allstar node. The registration server makes an 'allow list' based upon the IP addresses from which you register your Allstar node. Jim > Date: Sat, 13 Sep 2014 23:58:21 -0400 > From: Bryan at bryanfields.net > To: kk6ecm at gmail.com; tim.sawyer at mac.com; app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > I've had three other people on IRC test this and I've tested this from 3 > different servers myself. > > All are giving an error 403 on: > > http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > I don't think it's just me :( > > > On 9/13/14, 11:50 PM, Bob wrote: > > Works fine here. > > > > -----Original Message----- > > From: app_rpt-users-bounces at ohnosec.org > > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan Fields > > Sent: Saturday, September 13, 2014 8:32 PM > > To: Tim Sawyer; APP RPT > > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > > > Thanks Tim, > > > > However, I'm getting 403 errors on each. > > > > Perhaps some kinda IP block issue or something? > > > > root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:26:54-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes1.allstarlink.org... 96.36.57.202 > > Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > > HTTP request sent, awaiting response... 403 > > 2014-09-13 23:26:54 ERROR 403: (no description). > > > > root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:00-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes2.allstarlink.org... 209.159.155.200 > > Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2014-09-13 23:27:00 ERROR 403: Forbidden. > > > > root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:06-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes3.allstarlink.org... 65.110.110.172 > > Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. > > HTTP request sent, awaiting response... 403 > > 2014-09-13 23:27:06 ERROR 403: (no description). > > > > root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:11-- http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes4.allstarlink.org... 67.214.190.109 > > Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2014-09-13 23:27:12 ERROR 403: Forbidden. > > > > > > > > > > > > On 9/13/14, 11:23 PM, Tim Sawyer wrote: > >> Works for me. > >> > >> > >> Resolving nodes1.allstarlink.org... 96.36.57.202 > >> Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > >> HTTP request sent, awaiting response... 200 OK > >> Length: unspecified [text/plain] > >> Saving to: `/var/lib/asterisk/rpt_extnodes-temp' > >> > >> [ <=> > > ] 64,417 225K/s in 0.3s > >> > >> 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' > > saved [64417] > >> > >> Retrieved node list from nodes1.allstarlink.org > >> > >> -- > >> Tim WD6AWP > >> > >>> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: > >>> > >>> This is not working, looks like all the servers are not responding. > >>> > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes2.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes3.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes4.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > server > >>> > >>> Ideas? > >>> > >>> -- > >>> Bryan Fields > >>> > >>> 727-409-1194 - Voice > >>> 727-214-2508 - Fax > >>> http://bryanfields.net > >>> > >>> _______________________________________________ > >>> App_rpt-users mailing list > >>> App_rpt-users at 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. > >> > > > > > > > -- > Bryan Fields > > 727-409-1194 - Voice > 727-214-2508 - Fax > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kk6ecm at gmail.com Sun Sep 14 09:42:08 2014 From: kk6ecm at gmail.com (kk6ecm) Date: Sun, 14 Sep 2014 02:42:08 -0700 Subject: [App_rpt-users] Multiple requests for registration In-Reply-To: References: <1857007D3A0D4789A90DD7BEBDA40C9B@ThePykesHP> Message-ID: <6898B660-E479-4CFC-9778-BC773305DEC5@gmail.com> Good point. I had bumped it up to 5 because Asterisk will stop after several days, and I'm trying to capture the reason. The only way I can get it going again is a reboot. I'm running Pickle on a Beagleboard XM. Thanks, Bob kk6ecm Sent from iPad > On Sep 13, 2014, at 9:56 PM, Jim Duuuude wrote: > > These are normal messages. Dont worry about them. Normally, people run their > verbose level lower then whatever you have it set to, and dont see them. What verbose > level are you running at? > > Jim > > From: kk6ecm at gmail.com > To: app_rpt-users at ohnosec.org > Date: Sat, 13 Sep 2014 21:12:57 -0700 > Subject: Re: [App_rpt-users] Multiple requests for registration > > Why is it sending a ?registry rereqquest? ?Should I be receiving some sort of confirmation (feedback of success)? > > > > Thanks, > > Bob > > kk6ecm > > From: outlook_97fc649978f54bf0 at outlook.com [mailto:outlook_97fc649978f54bf0 at outlook.com] On Behalf Of Doug Crompton > Sent: Friday, September 12, 2014 5:35 PM > To: Bob > Cc: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Multiple requests for registration > > > > The registration interval is 60 seconds hard coded in the source. So what you see is normal. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: kk6ecm at gmail.com > To: App_rpt-users at ohnosec.org > Date: Fri, 12 Sep 2014 17:02:30 -0700 > Subject: [App_rpt-users] Multiple requests for registration > > My servers are constantly sending registration request and rereqquests. I check two different ones on two different IP addresses at two different locations, although the same ISP. I don?t ever remember this happening this much, at this frequency. I?m wondering if there is something I need to fix. > > > > Also, is the frequency of these requests adjustable on my end, and is it anything I need to do? > > > > The data below is from one server. The other server looks pretty much the same. This one also has Echolink, and I get an Echolink update occasionally interspersed between large groups of the warnings shown below. > > > > Thanks, > > Bob > > kk6ecm > > > > > > [Sep 12 23:48:34] WARNING[456]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '29009' > > [Sep 12 23:48:34] WARNING[459]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest > > [Sep 12 23:48:44] WARNING[452]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '28765' > > [Sep 12 23:48:45] WARNING[454]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest > > [Sep 12 23:49:24] WARNING[459]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '29009' > > [Sep 12 23:49:24] WARNING[458]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest > > [Sep 12 23:49:35] WARNING[454]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '28765' > > [Sep 12 23:49:35] WARNING[456]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest > > > _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vencl at att.net Sun Sep 14 11:42:08 2014 From: vencl at att.net (Lu Vencl) Date: Sun, 14 Sep 2014 07:42:08 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: <54150A8D.1000104@bryanfields.net> References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com> <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com> <2788FE3C-9186-4192-ACC7-7DDF6B940F7B@mac.com> <54150A8D.1000104@bryanfields.net> Message-ID: <0EBFA15D-28D2-4381-A9B5-D59B12701A40@att.net> Been there and done it. It does not work. Lu Vencl > On Sep 13, 2014, at 11:25 PM, Bryan Fields wrote: > >> On 9/13/14, 11:19 PM, Tim Sawyer wrote: >> People have jumped on my butt for saying this before but I?ll say it again >> anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, >> especially one for $5/mo. I?m not going to tell you not to do it, but if >> you do manage to jump the hurdles of getting Asterisk installed on a hosted >> VPS, it may not work as it does on a $50 computer. > > I second this. Asterisk is one of those programs that is very timing > dependent. A virtual server, especially a $5/month VPS is not going to work > well since there are 200 VM's all competing for processor time. > > This being said, there is no requirement that you run ACID. Grab it and > compile from source, I dislike redhat/centos, and run on debian just fine. > > -- > Bryan Fields > > 727-409-1194 - Voice > 727-214-2508 - Fax > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. From szingman at msgstor.com Sun Sep 14 16:54:20 2014 From: szingman at msgstor.com (Steve Zingman) Date: Sun, 14 Sep 2014 12:54:20 -0400 Subject: [App_rpt-users] Virtual node In-Reply-To: References: Message-ID: <5415C83C.2080404@msgstor.com> Been there, doing that. I've been running Node 2100 as a hub on a VMware VM for years. First as Debian Etch and now Wheezy. Steve N4IRS On 09/14/2014 12:00 PM, app_rpt-users-request at ohnosec.org wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users at ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request at ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner at ohnosec.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. Re: Centos 5 with kernel 2.6.32-042stab093.4 (Lu Vencl) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 14 Sep 2014 07:42:08 -0400 > From: Lu Vencl > To: Bryan Fields > Cc: APP RPT > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > Message-ID: <0EBFA15D-28D2-4381-A9B5-D59B12701A40 at att.net> > Content-Type: text/plain; charset=utf-8 > > Been there and done it. It does not work. > > Lu Vencl > >> On Sep 13, 2014, at 11:25 PM, Bryan Fields wrote: >> >>> On 9/13/14, 11:19 PM, Tim Sawyer wrote: >>> People have jumped on my butt for saying this before but I?ll say it again >>> anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, >>> especially one for $5/mo. I?m not going to tell you not to do it, but if >>> you do manage to jump the hurdles of getting Asterisk installed on a hosted >>> VPS, it may not work as it does on a $50 computer. >> >> I second this. Asterisk is one of those programs that is very timing >> dependent. A virtual server, especially a $5/month VPS is not going to work >> well since there are 200 VM's all competing for processor time. >> >> This being said, there is no requirement that you run ACID. Grab it and >> compile from source, I dislike redhat/centos, and run on debian just fine. >> >> -- >> Bryan Fields >> >> 727-409-1194 - Voice >> 727-214-2508 - Fax >> http://bryanfields.net >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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 at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > End of App_rpt-users Digest, Vol 67, Issue 44 > ********************************************* > From george at dyb.com Sun Sep 14 17:55:43 2014 From: george at dyb.com (George Csahanin) Date: Sun, 14 Sep 2014 12:55:43 -0500 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: <5415125D.3090304@bryanfields.net> References: <541507EC.8010306@bryanfields.net><6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com><54150C4B.3050505@bryanfields.net> <5415125D.3090304@bryanfields.net> Message-ID: I can't see it either, though all seems normal operationally. George J Csahanin W2DB 2360 Cedar Park, TX -----Original Message----- From: Bryan Fields Sent: Saturday, September 13, 2014 10:58 PM To: Bob ; 'Tim Sawyer' ; 'APP RPT' Subject: Re: [App_rpt-users] rc.updatenodelist fails. I've had three other people on IRC test this and I've tested this from 3 different servers myself. All are giving an error 403 on: http://nodes1.allstarlink.org/cgi-bin/nodes.pl I don't think it's just me :( On 9/13/14, 11:50 PM, Bob wrote: > Works fine here. > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan Fields > Sent: Saturday, September 13, 2014 8:32 PM > To: Tim Sawyer; APP RPT > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > Thanks Tim, > > However, I'm getting 403 errors on each. > > Perhaps some kinda IP block issue or something? > > root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl > --2014-09-13 23:26:54-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl > Resolving nodes1.allstarlink.org... 96.36.57.202 > Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > HTTP request sent, awaiting response... 403 > 2014-09-13 23:26:54 ERROR 403: (no description). > > root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl > --2014-09-13 23:27:00-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl > Resolving nodes2.allstarlink.org... 209.159.155.200 > Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. > HTTP request sent, awaiting response... 403 Forbidden > 2014-09-13 23:27:00 ERROR 403: Forbidden. > > root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl > --2014-09-13 23:27:06-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl > Resolving nodes3.allstarlink.org... 65.110.110.172 > Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. > HTTP request sent, awaiting response... 403 > 2014-09-13 23:27:06 ERROR 403: (no description). > > root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl > --2014-09-13 23:27:11-- http://nodes4.allstarlink.org/cgi-bin/nodes.pl > Resolving nodes4.allstarlink.org... 67.214.190.109 > Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. > HTTP request sent, awaiting response... 403 Forbidden > 2014-09-13 23:27:12 ERROR 403: Forbidden. > > > > > > On 9/13/14, 11:23 PM, Tim Sawyer wrote: >> Works for me. >> >> >> Resolving nodes1.allstarlink.org... 96.36.57.202 >> Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. >> HTTP request sent, awaiting response... 200 OK >> Length: unspecified [text/plain] >> Saving to: `/var/lib/asterisk/rpt_extnodes-temp' >> >> [ <=> > ] 64,417 225K/s in 0.3s >> >> 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' > saved [64417] >> >> Retrieved node list from nodes1.allstarlink.org >> >> -- >> Tim WD6AWP >> >>> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: >>> >>> This is not working, looks like all the servers are not responding. >>> >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > server >>> Problem retrieving node list from nodes2.allstarlink.org, trying another > server >>> Problem retrieving node list from nodes3.allstarlink.org, trying another > server >>> Problem retrieving node list from nodes4.allstarlink.org, trying another > server >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > server >>> >>> Ideas? >>> >>> -- >>> Bryan Fields >>> >>> 727-409-1194 - Voice >>> 727-214-2508 - Fax >>> http://bryanfields.net >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at 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. >> > > -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net From george at dyb.com Sun Sep 14 17:56:44 2014 From: george at dyb.com (George Csahanin) Date: Sun, 14 Sep 2014 12:56:44 -0500 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: References: <541507EC.8010306@bryanfields.net><6BB43B12-CAC0-4A70-A0C2-34C450952156@mac.com>, <54150C4B.3050505@bryanfields.net>, , , <5415125D.3090304@bryanfields.net> Message-ID: <309050EA476E41E18BC4F8DE5F929CC5@georgecPC> oops handy to remember TNX George J Csahanin W2DB Cedar Park, TX From: Jim Duuuude Sent: Saturday, September 13, 2014 11:14 PM To: Bryan Fields ; Bob ; 'Tim Sawyer' ; app_rpt mailing list Subject: Re: [App_rpt-users] rc.updatenodelist fails. It not going to work unless you attempt access from an IP address that has a registered Allstar node. The registration server makes an 'allow list' based upon the IP addresses from which you register your Allstar node. Jim > Date: Sat, 13 Sep 2014 23:58:21 -0400 > From: Bryan at bryanfields.net > To: kk6ecm at gmail.com; tim.sawyer at mac.com; app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > I've had three other people on IRC test this and I've tested this from 3 > different servers myself. > > All are giving an error 403 on: > > http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > I don't think it's just me :( > > > On 9/13/14, 11:50 PM, Bob wrote: > > Works fine here. > > > > -----Original Message----- > > From: app_rpt-users-bounces at ohnosec.org > > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan Fields > > Sent: Saturday, September 13, 2014 8:32 PM > > To: Tim Sawyer; APP RPT > > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > > > Thanks Tim, > > > > However, I'm getting 403 errors on each. > > > > Perhaps some kinda IP block issue or something? > > > > root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:26:54-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes1.allstarlink.org... 96.36.57.202 > > Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > > HTTP request sent, awaiting response... 403 > > 2014-09-13 23:26:54 ERROR 403: (no description). > > > > root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:00-- http://nodes2.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes2.allstarlink.org... 209.159.155.200 > > Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2014-09-13 23:27:00 ERROR 403: Forbidden. > > > > root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:06-- http://nodes3.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes3.allstarlink.org... 65.110.110.172 > > Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. > > HTTP request sent, awaiting response... 403 > > 2014-09-13 23:27:06 ERROR 403: (no description). > > > > root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > --2014-09-13 23:27:11-- http://nodes4.allstarlink.org/cgi-bin/nodes.pl > > Resolving nodes4.allstarlink.org... 67.214.190.109 > > Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2014-09-13 23:27:12 ERROR 403: Forbidden. > > > > > > > > > > > > On 9/13/14, 11:23 PM, Tim Sawyer wrote: > >> Works for me. > >> > >> > >> Resolving nodes1.allstarlink.org... 96.36.57.202 > >> Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > >> HTTP request sent, awaiting response... 200 OK > >> Length: unspecified [text/plain] > >> Saving to: `/var/lib/asterisk/rpt_extnodes-temp' > >> > >> [ <=> > > ] 64,417 225K/s in 0.3s > >> > >> 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' > > saved [64417] > >> > >> Retrieved node list from nodes1.allstarlink.org > >> > >> -- > >> Tim WD6AWP > >> > >>> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: > >>> > >>> This is not working, looks like all the servers are not responding. > >>> > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes2.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes3.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes4.allstarlink.org, trying another > > server > >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > > server > >>> > >>> Ideas? > >>> > >>> -- > >>> Bryan Fields > >>> > >>> 727-409-1194 - Voice > >>> 727-214-2508 - Fax > >>> http://bryanfields.net > >>> > >>> _______________________________________________ > >>> App_rpt-users mailing list > >>> App_rpt-users at 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. > >> > > > > > > > -- > Bryan Fields > > 727-409-1194 - Voice > 727-214-2508 - Fax > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From petem001 at hotmail.com Sun Sep 14 20:14:52 2014 From: petem001 at hotmail.com (pete M) Date: Sun, 14 Sep 2014 16:14:52 -0400 Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 In-Reply-To: <2788FE3C-9186-4192-ACC7-7DDF6B940F7B@mac.com> References: <6DFFD48B8A5747D7AB085AC5460BD251@ThePykesHP> <6668D71D-1822-4A33-99AE-D3EAF7FCF289@gmail.com> <95376CDE-D14E-4BC2-9A0B-ECBFC522BF88@gmail.com> <2788FE3C-9186-4192-ACC7-7DDF6B940F7B@mac.com> Message-ID: ok got the memo. will not go on with that project.. but how on hell someone is supposed to run avdamn node in a data center with out cashing thousand of dollard annualy.. Envoy? de mon iPad > Le 2014-09-13 ? 23:20, "Tim Sawyer" a ?crit : > > People have jumped on my butt for saying this before but I?ll say it again anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, especially one for $5/mo. I?m not going to tell you not to do it, but if you do manage to jump the hurdles of getting Asterisk installed on a hosted VPS, it may not work as it does on a $50 computer. > > -- > Tim WD6AWP > >> On Sep 13, 2014, at 4:56 PM, pete M wrote: >> >> OK >> >> The GOAL: having a node without a radio on a server to use as a gateway of conference for a few repeaters around the Montreal region. I found a nice site where I can rent a small vps for 5$ a month. nothing fancy. I want to have that computer tu be my conference.. None of the site I have are either stable enough to host a nice conference or where I could have computer in a not arsh place, the bandwith is the issue. >> >> So I can load a lot of different distro, BUT they are fixe image to start with. Cnt ask to load the acid iso.. (this would of course fix every thing.) >> >> So the goal is not for fun I do need to make this work. >> >> Will work from there, will find some answer online for most of the stuff I need, But when it is directly related to app_rpt, here is my only source.. >> >> Now I know what version of asterisk to use, where to find it, same for dahdi and app_rpt.. will try to ork on that. will find that I need some library of other stuff enroute and other software.. but I will try.. >> >> Not such a noob in linux.. but not a pro.. thanks for you patience.. >> >> Pierre VE2PF >> >> >> From: doug at crompton.com >> To: petem001 at hotmail.com >> CC: app_rpt-users at ohnosec.org >> Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> Date: Thu, 11 Sep 2014 23:49:25 -0400 >> >> First of all remind me - what is your end goal here. Are you doing this just for fun or is it for a real need and if so what is the need? >> >> The easiest thing to do might be to just download the BBB image at hamvoip.org. Write it to an SD card, mount it on Linux - ubuntu or whatever works. The root partition not the boot partition. Copy from everything from the mount point /usr/src/utils to /usr/src on your linux box. Also copy /etc/asterisk from the mount point to /etc/asterisk for all the config files. >> >> The source tree would then be in /usr/src/utils/asterisk - dahdi would also be there along with the patches in /usr/src/utils >> >> You can compile and intall both dahdi and asterisk from there. Then following the directions on the BBB page and howto on setting up your node. >> >> Another possible choice would be to just bring up a standard centos installation on a PC and copy what you need from there. All the source and files you would need would be there like the scripts in /usr/local/sbin. You would need to make some changes however. >> >> As Dave pointed out earlier you are in for some real bumps along the way. There will be packages you will need to download and things you will need to configure. It is not a 123 type of thing. Without some Linux experience it could be daunting. >> >> Just remember if you are using dahdi you need to remove any mention of zaptel and use the chan_dahdi.conf as shown in the BBB config. >> >> 73 Doug >> WA3DSP >> http://www.crompton.com/hamradio >> >> >> From: petem001 at hotmail.com >> To: doug at crompton.com >> CC: app_rpt-users at ohnosec.org >> Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> Date: Thu, 11 Sep 2014 22:19:19 -0400 >> >> OK Doug you got me fired up.. >> >> just one thing to know what source of asterisk are you using exactly? >> >> Got Dahdi got the patch.. will fix what's needed to be fixed about ntpd and all. But what damn source of asterisk are you using? ;-) >> >> >> >> >> From: doug at crompton.com >> To: petem001 at hotmail.com >> CC: app_rpt-users at ohnosec.org >> Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> Date: Thu, 11 Sep 2014 13:15:14 -0400 >> >> Pete, >> >> I have done this so many times but unfortunately I never documented it. Here is a simple description. >> >> Get a distro and configure it like you normally would. Get ntpd running, network setup, etc. >> >> Download the acid code and the latest dahdi - >> >> I see it is 2.10.0 The last I used was 2.9.x but I suspect it will work the same. If not you could get the 2.9 version. >> >> http://www.asterisk.org/downloads/dahdi >> >> Apply the patch - info on how to do that is in the readme >> >> https://allstarlink.org/fixed-dahdi-patches.tar.gz >> >> Compile and install dahdi. >> >> Then compile and install asterisk >> >> Don't run any offsite updates. Configure it manually - not hard to do - and run. If you already have a configured system you can use those files from /etc.asterisk. BTW the BBB setup procedure and howto's at http://hamvoip.org describe how to do that very easily which would also apply here. The only caveat is the config files would be different to start with so some consideration has to be given to that. >> >> All that sounds easy but you undoubtedly will have some hiccups and things you will have to do to get it to work. It is impossible to document that as it would be different on the multitude of distros and kernel versions. >> >> I have compiled it on the latest Debian and Ubuntu. The real problem is OSS support which is required. Debian has it, Ubuntu does not. You have to recompile the kernel and add it back in. For that reason Ubuntu is not recommended as kernel versions can change with frequent updates. >> >> I guess the big question is do you really need to do this. I forget why you said you can't run a local system. In that case you could just install an acid release on a PC or maybe go with the BBB. >> >> 73 Doug >> WA3DSP >> http://www.crompton.com/hamradio >> >> >> From: petem001 at hotmail.com >> To: doug at crompton.com >> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> Date: Thu, 11 Sep 2014 12:08:04 -0400 >> >> well can you point me a few pointers on how to do so? >> >> Never patched some software before. >> >> >> From: Doug Crompton >> Sent: Thursday, September 11, 2014 11:03 AM >> To: pete M >> Cc: app_rpt-users at ohnosec.org >> Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> >> I am not sure what you are saying when you comment.... >> >> "well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.." >> >> Did you mean "will" ?? The patches can be applied against the latest dahdi and it will compile on late kernels. The BBB is an example of that. >> >> 73 Doug >> WA3DSP >> http://www.crompton.com/hamradio >> >> >> From: petem001 at hotmail.com >> To: doug at crompton.com >> CC: app_rpt-users at ohnosec.org >> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> Date: Thu, 11 Sep 2014 09:42:08 -0400 >> >> well I think that Dahdi wont compile correctly on Any distro that have a kernel pass a certain point.. >> >> I can run the system on bunch of disto.. >> >> Here is the list.. >> >> >> CentOS 5 32bit >> CentOS 5 64bit >> CentOS 6 32bit >> CentOS 6 64bit >> CentOS 7 64bit >> CentOS 7 64bit Minimal >> Debian 6 32bit >> Debian 6 64bit >> Debian 7 32bit >> Debian 7 32bit Minimal >> Debian 7 64bit >> Debian 7 64bit Minimal >> Fedora 17 32bit >> Fedora 17 64bit >> Fedora 19 32bit >> Fedora 19 64bit >> Starbound-Ubuntu 13.10 32bit >> SUSE 12.2 32bit >> SUSE 12.2 64bit >> Ubuntu 10.04 32bit >> Ubuntu 10.04 64bit >> Ubuntu 11.10 32bit >> Ubuntu 11.10 64bit >> Ubuntu 12.10 32bit >> Ubuntu 12.10 64bit >> Ubuntu 13.10 32bit >> Ubuntu 13.10 64bit >> Ubuntu 14.04 32bit >> Ubuntu 14.04 32bit Minimal >> Ubuntu 14.04 64bit >> Ubuntu 14.04 64bit Minimal >> >> So I have lots of choice >> >> But I was under the feeling that the best distro was centos 5 for acid.. (using the install script from the cd.. >> >> Unless you can point me in another direction.. >> >> >> From: Doug Crompton >> Sent: Wednesday, September 10, 2014 6:16 PM >> To: pete M >> Cc: app_rpt-users at ohnosec.org >> Subject: RE: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> >> Pete, >> >> I have been somewhat following this. Does it have to be centos? Allstar will run on the latest Debian. You need to install it yourself but depending on your Linux capability it is not a big deal. >> >> 73 Doug >> WA3DSP >> http://www.crompton.com/hamradio >> >> >> From: petem001 at hotmail.com >> To: kk6ecm at gmail.com; app_rpt-users at ohnosec.org >> Date: Wed, 10 Sep 2014 14:12:38 -0400 >> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> >> Thanks Bob. I dont think that it has to do with something impossible to do.. In fact I have been searching the archives about problem like that.. And there was some answer about some patch to dahdi zaptel.. or such.. I am at work, dont remember.. >> >> If it would be installed at least up to a point. I would be able to do it.. >> >> I just dont know how to tell the compiler not to compile that part and go on.. >> >> >> >> From: kk6ecm at gmail.com >> Date: Wed, 10 Sep 2014 09:15:13 -0700 >> To: app_rpt-users at ohnosec.org >> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> >> Couple of thoughts. I've not been able to load using ssh. Last time I attempted this zaptel did not load properly, but it seems I didn't get an error until after the reboot. It seems to me (check the ACID scripts), that ACID disables ssh during the load. When I have loaded CentOS 5.10 (as previously mentioned), I then used some of the ACID scripts to load asterisk, etc, I always had to us a monitor and keyboard on the server to be fully successful. But hey... that could just be my fumbling around. >> >> As for your stated concern. I could be because no one knows the answer. Hard to believe, I know, but it seems to happen occasionally on this list :~} >> >> Thanks, >> Bob >> kk6ecm >> >> Sent from iPad >> >> >> On Sep 10, 2014, at 8:30 AM, pete M wrote: >> >> OK, did I asked a question that CAN?T be answered? Or did I asked the wrong way? >> >> If I did I am sorry.. And I gave my apology to every one I could have offended.. >> But is it possible to at least have a small word from all those guru here if it can be done, and which way should I go? dont need to have someone holding my hand.. Just need to have a small Idea what to do.. Like just point me the pathway.. I will try to do it on my own.. Thanks On Sep 9, 2014, at 11:13 AM, pete M wrote: >> >> I cant use the acid.iso cause the computer is in a remote place ( rented server) and they dont supply special OS installation. I can have fedore ubuntu centos on many flavor (x86 or 64 bit) and many revision... The problem is not the loading od the cd are other things like that.. >> >> I am sure that the kernel is too new and there is a part of zaptel that need a depricated fonction If I am not crazy.. >> >> >> >> From: kk6ecm >> Sen t: Tuesday, September 09, 2014 1:40 PM >> To: APP RPT >> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> >> I use this when ACID will not load, usually due to issues with BIO S and network drivers. I was assuming you were not able to get ACID to load on you computer. If your running phase2.sh was a second attempt after trying to load ACID, you may need to check that all the files are there because the load deletes some files. In short, if this occurred during an attempt to load the ACID download, I'd just try it again. >> >> Thanks, >> Bob >> kk6ecm >> >> Sent from iPad >> >> >> On Sep 9, 2014, at 8:27 AM, pete M wrote: >> >> Ok will try that.. >> >> thanks! >> >> >> From: Bob >> Sent: Tuesday, September 09, 2014 10:55 AM >> To: 'APP RPT' >> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> >> I?ve done this several times without issue. Here are the steps I used. >> >> Load CentOS 5.10 downloaded from CentOS website >> No features, tools only, no desktop (competes with Asterisk) >> Set ssh /etc/ssh/sshd_config >> Run "setup" at comand line and disable firewall >> vi /etc/rc.d/acidrepo >> http://dl.allstarlink.org >> Execute portion of ks.cfg, each line at a time >> cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig >> cat <>/etc/rc.d/rc.local >> >> cd /etc/rc.d; rm -f phase1.sh; wget -q http://dl.allstarlink.org/installcd/phase1.sh >> >> chmod 755 /etc/rc.d/phase1.sh >> >> /etc/rc.d/phase1.sh >> Auto reboot after phase1.sh executed >> phase2.sh runs automatically to completion >> >> Bob >> kk6ecm >> >> From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of pete M >> Sent: Tuesday, September 09, 2014 7:00 AM >> To: APP RPT >> Subject: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> >> Need help to install an allstarlink node that wont have any radio on it in a data center to be my central reflector for my french network of repeater around Quebec Canada.. >> >> I did try to run phase2.sh from /etc/rc.d/ but this fail when compiling. >> >> here is the out put from the script >> >> sh phase2.sh >> ****** Phase 2 post install ****** >> Getting asterisk install script from http://dl.allstarlink.org../. >> Getting files.tar.gz from http://dl.allstarlink.org../. >> ****** Asterisk Installation ****** >> /etc/rc.d/astinstall.sh: line 11: ntpdate: command not found >> Unpacking files.tar.gz... >> Compiling Zaptel... >> checking for gcc... gcc >> checking for C compiler default output file name... a.out >> checking whether the C compiler works... yes >> checking whether we are cross compiling... no >> checking for suffix of executables... >> checking for suffix of object files... o >> checking whether we are using the GNU C compiler... yes >> checking whether gcc accepts -g... yes >> checking for gcc option to accept ISO C89... none needed >> checking how to run the C preproc esso r... gcc -E >> checking for a BSD-compatible install... /usr/bin/install -c >> checking whether ln -s works... yes >> checking for GNU make... make >> checking for grep... /bin/grep >> checking for sh... /bin/sh >> checking for ln... /bin/ln >> checking for wget... /usr/bin/wget >> checking for grep that handles long lines and -e... (cached) /bin/grep >> checking for egrep... /bin/grep -E >> checking for ANSI C header files... yes >> checking for sys/types.h... yes >> checking for sys/stat.h... yes >> checking for stdlib.h... yes >> checking for string.h... yes >> checking for memory.h... yes >> checking for strings.h... yes >> checking for inttypes.h... yes >> checking for stdint.h... yes >> checking for unistd.h... yes >> checking for initscr in -lcurses... no >> checking for initscr in -lncurses... no >> checking for newtBell in -lnewt... no >> checking for usb_init in -lusb... no >> configure: creating ./config.status >> config.status: creating build_tools/menuselect-deps >> config.status: creating makeopts >> config.status: creating build_tools/make_firmware_object >> configure: *** Zaptel build successfully configured *** >> make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' >> checking build system type... i686-pc-linux-gnu >> checking host system type... i686-pc-linux-gnu >> checking for gcc... gcc >> checking for C compiler default output file name... a.out >> checking whether the C compiler works... yes >> checking whether we are cross compiling... no >> checking for suffix of executables... >> checking for suffix of object files... o >> checking whether we are using the GNU C compiler... yes >> checking whether gcc accepts -g... yes >> checking for gcc option to accept ANSI C... none needed >> checking for GNU make... make >> checking for asprintf... yes >> checking for getloadavg... yes >> checking for setenv... yes >> checking for strcasestr... yes >> checking for strndup... yes >> checking for strnlen... yes >> checking for strsep... yes >> checking for strtoq... yes >> checking for unsetenv... yes >> checking for vasprintf... yes >> checking how to run the C preprocessor... gcc -E >> checking for egrep... grep -E >> checking for ANSI C header files... yes >> checking for sys/types.h... yes >> checking for sys/stat.h... yes >> checking for stdlib.h... yes >> checking for string.h... yes >> checking for memory.h... yes >> checking for strings.h... yes >> checking for inttypes.h... yes >> checking for stdint.h... yes >> checking for unistd.h... yes >> checking for initscr in -lcurses... no >> checking for initscr in -lncurses... no >> checking for pkg-config... No >> configure: creating ./config.status >> config.status: creating makeopts >> config.status: creating autoconfig.h >> configure: configuring in mxml >> configure: running /bin/sh './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. >> checking for gcc... gcc >> checking for C compiler default output file name... a.out >> checking whether the C compiler works... yes >> checking whether we are cross compiling... no >> checking for suffix of executables... >> checking for suffix of object files... o >> checking whether we are using the GNU C compiler... yes >> checking whether gcc accepts -g... yes >> checking for gcc option to accept ANSI C... none needed >> checking for g++... no >> checking for c++... no >> checking for gpp... no >> checking for aCC... no >> checking for CC... no >> checking for cxx... no >> checking for cc++... no >> checking for cl... no >> checking for FCC... no >> checking for KCC... no >> checking for RCC... no >> checking for xlC_r... no >> checking for xlC... no >> checking whether we are using the GNU C++ compiler... no >> checking whether g++ accepts -g... no >> checking for a BSD-compatible install... /usr/bin/install -c >> checking for ranlib... ranlib >> checking for ar... /usr/bin/ar >> checking for cp... /bin/cp >> checking for ln... /bin/ln< /font> >> checking for mkdir... /bin/mkdir >> checking for nroff... /usr/bin/nroff >> checking for rm... /bin/rm >> checking for strdup... yes >> checking for vsnprintf... yes >> configure: creating ./config.status >> config.status: creating Makefile >> config.status: creating mxml.list >> config.status: creating mxml.pc >> config.status: creating config.h >> configure: Menuselect build configuration successfully completed >> make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' >> make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' >> make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' >> gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c >> gcc -g -c -D_GNU_SOU RC E -Wall -c -o strcompat.o strcompat.c >> gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c >> make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' >> gcc -O -Wall -c mxml-attr.c >> gcc -O -Wall -c mxml-entity.c >> gcc -O -Wall -c mxml-file.c >> gcc -O -Wall -c mxml-index.c >> gcc -O -Wall -c mxml-node.c >> gcc -O -Wall -c mxml-search.c >> gcc -O -Wall -c mxml-set.c >> gcc -O -Wall -c mxml-private.c >> gcc -O -Wall -c mxml-string.c >> /bin/rm -f libmxml.a >> /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o >> a - mxml-attr.o >> a - mxml-entity.o >> a - mxml-file.o >> a - mxml-index.o >> a - mxml-node.o >> a - mxml-search.o >> a - mxml-set.o >> a - mxml-private.o >> a - mxml-string.o >> ranlib libmxml.a >> make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' >> gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a mxml/libmxml.a >> make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' >> make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' >> Generating input for menuselect ... >> >> *********************************************************** >> The existing menuselect.makeop ts file did not specify >> that 'zttool' should not be included. However, either some >> dependencies for this module were not found or a >> conflict exists. >> >> Either run 'make menuselect' or remove the existing >> menuselect.makeopts file to resolve this issue. >> *********************************************************** >> >> make: *** [menuselect.makeopts] Error 255 >> Failure: Unable to compile Zaptel 2 >> Fatal error: Unable to install Asterisk! >> [root at node rc.d]# >> >> I dont know where to go from there.. >> >> Anyone care to help a bit? >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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 at 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 at 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 at 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 at 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 at 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 at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wayne at anywherehost.net Sun Sep 14 20:25:03 2014 From: wayne at anywherehost.net (Wayne) Date: Sun, 14 Sep 2014 13:25:03 -0700 Subject: [App_rpt-users] Virtual node In-Reply-To: <5415C83C.2080404@msgstor.com> References: <5415C83C.2080404@msgstor.com> Message-ID: <6C84853AD7F948F7B9C6283D5EC389FD@desktop> If it runs on VMWare why not Virtuozzo? As the System Administrator for the hosting company I work we run Virtuozzo 4.7. We generally place two Plesk servers on one hardware node (dual processor Intel XEON/64-bit 2.5GHz,L2 12MB cache, 16GB ECC RAM, and RAID III.) Never do two fully functional servers conflict because we do not allow over-use of resources. If the "dedicated server" VPS resources are small enough to moderate we can run as many as 3-5 containers. With this said I have not yet tried to install ACID into an empty VPS container. By default Virtuozzo creates a Centos 6.x shell with limited files. If adding Plesk it will automatically pull from YUM for a complete distro install. We have several Shoutcast servers configured this way but we had to manually add dependent files. Now then, I want to run ACID on an identical machine and a RTCM but with only ACID on one container regardless of the outstanding horsepower. The main reasons for this are the ability to do a timed back-up to a network resource, restore to a different location if there is a failure, migrate to a different server long enough to change hard drives annually, and a host of other features. The back-up and migration tools are essential. Plus, if the container is rooted a remote command will rebuild the container destructively or non-destructively. The horsepower is so that I can give back to the community by offering the equivalent of a conference channel or otherwise help someone else out. The last reason is to avoid timing issues. Our goal is a hybrid of voted simulcast and non-voted but synced transmit on one node. With all of this said has anyone actually tried to load ACID into a Virtuozzo 4.7 container? I can build a regular server and write a bash script that will TAR and move a back-up file with rsync. But Virtuozzo is a team player and very comfortable for me. I have been running it on almost all of our client servers since 2007. Blessings to all, Namaste -----Original Message----- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Steve Zingman Sent: Sunday, September 14, 2014 9:54 AM To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Virtual node Been there, doing that. I've been running Node 2100 as a hub on a VMware VM for years. First as Debian Etch and now Wheezy. Steve N4IRS On 09/14/2014 12:00 PM, app_rpt-users-request at ohnosec.org wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users at ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request at ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner at ohnosec.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. Re: Centos 5 with kernel 2.6.32-042stab093.4 (Lu Vencl) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 14 Sep 2014 07:42:08 -0400 > From: Lu Vencl > To: Bryan Fields > Cc: APP RPT > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > Message-ID: <0EBFA15D-28D2-4381-A9B5-D59B12701A40 at att.net> > Content-Type: text/plain; charset=utf-8 > > Been there and done it. It does not work. > > Lu Vencl > >> On Sep 13, 2014, at 11:25 PM, Bryan Fields wrote: >> >>> On 9/13/14, 11:19 PM, Tim Sawyer wrote: >>> People have jumped on my butt for saying this before but I?ll say it again >>> anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, >>> especially one for $5/mo. I?m not going to tell you not to do it, but if >>> you do manage to jump the hurdles of getting Asterisk installed on a hosted >>> VPS, it may not work as it does on a $50 computer. >> >> I second this. Asterisk is one of those programs that is very timing >> dependent. A virtual server, especially a $5/month VPS is not going to work >> well since there are 200 VM's all competing for processor time. >> >> This being said, there is no requirement that you run ACID. Grab it and >> compile from source, I dislike redhat/centos, and run on debian just fine. >> >> -- >> Bryan Fields >> >> 727-409-1194 - Voice >> 727-214-2508 - Fax >> http://bryanfields.net >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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 at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > End of App_rpt-users Digest, Vol 67, Issue 44 > ********************************************* > _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. From szingman at msgstor.com Sun Sep 14 20:42:37 2014 From: szingman at msgstor.com (Steve Zingman) Date: Sun, 14 Sep 2014 16:42:37 -0400 Subject: [App_rpt-users] Virtual node In-Reply-To: <6C84853AD7F948F7B9C6283D5EC389FD@desktop> References: <5415C83C.2080404@msgstor.com> <6C84853AD7F948F7B9C6283D5EC389FD@desktop> Message-ID: <5415FDBD.6080600@msgstor.com> One comment I forgot to make, Node 2100 is a HUB not a RF connected node. 73, Steve N4IRS On 09/14/2014 04:25 PM, Wayne wrote: > If it runs on VMWare why not ? > > As the System Administrator for the hosting company I work we run Virtuozzo > 4.7. We generally place two Plesk servers on one hardware node (dual > processor Intel XEON/64-bit 2.5GHz,L2 12MB cache, 16GB ECC RAM, and RAID > III.) Never do two fully functional servers conflict because we do not allow > over-use of resources. If the "dedicated server" VPS resources are small > enough to moderate we can run as many as 3-5 containers. > > With this said I have not yet tried to install ACID into an empty VPS > container. By default Virtuozzo creates a Centos 6.x shell with limited > files. If adding Plesk it will automatically pull from YUM for a complete > distro install. We have several Shoutcast servers configured this way but we > had to manually add dependent files. > > Now then, I want to run ACID on an identical machine and a RTCM but with > only ACID on one container regardless of the outstanding horsepower. The > main reasons for this are the ability to do a timed back-up to a network > resource, restore to a different location if there is a failure, migrate to > a different server long enough to change hard drives annually, and a host of > other features. The back-up and migration tools are essential. Plus, if the > container is rooted a remote command will rebuild the container > destructively or non-destructively. The horsepower is so that I can give > back to the community by offering the equivalent of a conference channel or > otherwise help someone else out. The last reason is to avoid timing issues. > Our goal is a hybrid of voted simulcast and non-voted but synced transmit on > one node. > > With all of this said has anyone actually tried to load ACID into a > Virtuozzo 4.7 container? I can build a regular server and write a bash > script that will TAR and move a back-up file with rsync. But Virtuozzo is a > team player and very comfortable for me. I have been running it on almost > all of our client servers since 2007. > > Blessings to all, > > Namaste > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Steve Zingman > Sent: Sunday, September 14, 2014 9:54 AM > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Virtual node > > Been there, doing that. I've been running Node 2100 as a hub on a VMware > VM for years. First as Debian Etch and now Wheezy. > > Steve N4IRS > > On 09/14/2014 12:00 PM, app_rpt-users-request at ohnosec.org wrote: >> Send App_rpt-users mailing list submissions to >> app_rpt-users at ohnosec.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> or, via email, send a message with subject or body 'help' to >> app_rpt-users-request at ohnosec.org >> >> You can reach the person managing the list at >> app_rpt-users-owner at ohnosec.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of App_rpt-users digest..." >> >> >> Today's Topics: >> >> 1. Re: Centos 5 with kernel 2.6.32-042stab093.4 (Lu Vencl) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sun, 14 Sep 2014 07:42:08 -0400 >> From: Lu Vencl >> To: Bryan Fields >> Cc: APP RPT >> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> Message-ID: <0EBFA15D-28D2-4381-A9B5-D59B12701A40 at att.net> >> Content-Type: text/plain; charset=utf-8 >> >> Been there and done it. It does not work. >> >> Lu Vencl >> >>> On Sep 13, 2014, at 11:25 PM, Bryan Fields wrote: >>> >>>> On 9/13/14, 11:19 PM, Tim Sawyer wrote: >>>> People have jumped on my butt for saying this before but I?ll say it > again >>>> anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, >>>> especially one for $5/mo. I?m not going to tell you not to do it, but if >>>> you do manage to jump the hurdles of getting Asterisk installed on a > hosted >>>> VPS, it may not work as it does on a $50 computer. >>> >>> I second this. Asterisk is one of those programs that is very timing >>> dependent. A virtual server, especially a $5/month VPS is not going to > work >>> well since there are 200 VM's all competing for processor time. >>> >>> This being said, there is no requirement that you run ACID. Grab it and >>> compile from source, I dislike redhat/centos, and run on debian just > fine. >>> >>> -- >>> Bryan Fields >>> >>> 727-409-1194 - Voice >>> 727-214-2508 - Fax >>> http://bryanfields.net >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at 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 at ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> >> End of App_rpt-users Digest, Vol 67, Issue 44 >> ********************************************* >> > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > > From email at jonbyrne.com Sun Sep 14 20:39:26 2014 From: email at jonbyrne.com (Jon Byrne) Date: Sun, 14 Sep 2014 21:39:26 +0100 Subject: [App_rpt-users] Virtual node In-Reply-To: <6C84853AD7F948F7B9C6283D5EC389FD@desktop> References: <5415C83C.2080404@msgstor.com> <6C84853AD7F948F7B9C6283D5EC389FD@desktop> Message-ID: I run my node 40890 on acid running on a KVM Virtual Machine and have had no issues so far, it has been running for around 4 months. I pay ?4.50 a month for it so very happy with the performance. For me the permanent up time is the benifit. I connect my local thelinkbox nodes to it when I am connecting the RF side. Regards Jon 2E0RFU ------------ Jon Byrne email at jonbyrne.com On 14 September 2014 21:25, Wayne wrote: > If it runs on VMWare why not Virtuozzo? > > As the System Administrator for the hosting company I work we run Virtuozzo > 4.7. We generally place two Plesk servers on one hardware node (dual > processor Intel XEON/64-bit 2.5GHz,L2 12MB cache, 16GB ECC RAM, and RAID > III.) Never do two fully functional servers conflict because we do not > allow > over-use of resources. If the "dedicated server" VPS resources are small > enough to moderate we can run as many as 3-5 containers. > > With this said I have not yet tried to install ACID into an empty VPS > container. By default Virtuozzo creates a Centos 6.x shell with limited > files. If adding Plesk it will automatically pull from YUM for a complete > distro install. We have several Shoutcast servers configured this way but > we > had to manually add dependent files. > > Now then, I want to run ACID on an identical machine and a RTCM but with > only ACID on one container regardless of the outstanding horsepower. The > main reasons for this are the ability to do a timed back-up to a network > resource, restore to a different location if there is a failure, migrate to > a different server long enough to change hard drives annually, and a host > of > other features. The back-up and migration tools are essential. Plus, if the > container is rooted a remote command will rebuild the container > destructively or non-destructively. The horsepower is so that I can give > back to the community by offering the equivalent of a conference channel or > otherwise help someone else out. The last reason is to avoid timing issues. > Our goal is a hybrid of voted simulcast and non-voted but synced transmit > on > one node. > > With all of this said has anyone actually tried to load ACID into a > Virtuozzo 4.7 container? I can build a regular server and write a bash > script that will TAR and move a back-up file with rsync. But Virtuozzo is a > team player and very comfortable for me. I have been running it on almost > all of our client servers since 2007. > > Blessings to all, > > Namaste > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Steve Zingman > Sent: Sunday, September 14, 2014 9:54 AM > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Virtual node > > Been there, doing that. I've been running Node 2100 as a hub on a VMware > VM for years. First as Debian Etch and now Wheezy. > > Steve N4IRS > > On 09/14/2014 12:00 PM, app_rpt-users-request at ohnosec.org wrote: > > Send App_rpt-users mailing list submissions to > > app_rpt-users at ohnosec.org > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > or, via email, send a message with subject or body 'help' to > > app_rpt-users-request at ohnosec.org > > > > You can reach the person managing the list at > > app_rpt-users-owner at ohnosec.org > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of App_rpt-users digest..." > > > > > > Today's Topics: > > > > 1. Re: Centos 5 with kernel 2.6.32-042stab093.4 (Lu Vencl) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Sun, 14 Sep 2014 07:42:08 -0400 > > From: Lu Vencl > > To: Bryan Fields > > Cc: APP RPT > > Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 > > Message-ID: <0EBFA15D-28D2-4381-A9B5-D59B12701A40 at att.net> > > Content-Type: text/plain; charset=utf-8 > > > > Been there and done it. It does not work. > > > > Lu Vencl > > > >> On Sep 13, 2014, at 11:25 PM, Bryan Fields > wrote: > >> > >>> On 9/13/14, 11:19 PM, Tim Sawyer wrote: > >>> People have jumped on my butt for saying this before but I?ll say it > again > >>> anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, > >>> especially one for $5/mo. I?m not going to tell you not to do it, but > if > >>> you do manage to jump the hurdles of getting Asterisk installed on a > hosted > >>> VPS, it may not work as it does on a $50 computer. > >> > >> I second this. Asterisk is one of those programs that is very timing > >> dependent. A virtual server, especially a $5/month VPS is not going to > work > >> well since there are 200 VM's all competing for processor time. > >> > >> This being said, there is no requirement that you run ACID. Grab it and > >> compile from source, I dislike redhat/centos, and run on debian just > fine. > >> > >> -- > >> Bryan Fields > >> > >> 727-409-1194 - Voice > >> 727-214-2508 - Fax > >> http://bryanfields.net > >> _______________________________________________ > >> App_rpt-users mailing list > >> App_rpt-users at 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 at ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > > > End of App_rpt-users Digest, Vol 67, Issue 44 > > ********************************************* > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From szingman at msgstor.com Sun Sep 14 20:32:27 2014 From: szingman at msgstor.com (Steve Zingman) Date: Sun, 14 Sep 2014 16:32:27 -0400 Subject: [App_rpt-users] Virtual node In-Reply-To: <6C84853AD7F948F7B9C6283D5EC389FD@desktop> References: <5415C83C.2080404@msgstor.com> <6C84853AD7F948F7B9C6283D5EC389FD@desktop> Message-ID: <5415FB5B.70607@msgstor.com> Wayne, I can speak to Virtuozzo or trying to install Acid on anything. My preference has always been running Debian and "rolling my own" when it comes to Asterisk and AllStar. If you are going to try it on Centos, I would build it from scratch. 73, Steve N4IRS On 09/14/2014 04:25 PM, Wayne wrote: > If it runs on VMWare why not ? > > As the System Administrator for the hosting company I work we run Virtuozzo > 4.7. We generally place two Plesk servers on one hardware node (dual > processor Intel XEON/64-bit 2.5GHz,L2 12MB cache, 16GB ECC RAM, and RAID > III.) Never do two fully functional servers conflict because we do not allow > over-use of resources. If the "dedicated server" VPS resources are small > enough to moderate we can run as many as 3-5 containers. > > With this said I have not yet tried to install ACID into an empty VPS > container. By default Virtuozzo creates a Centos 6.x shell with limited > files. If adding Plesk it will automatically pull from YUM for a complete > distro install. We have several Shoutcast servers configured this way but we > had to manually add dependent files. > > Now then, I want to run ACID on an identical machine and a RTCM but with > only ACID on one container regardless of the outstanding horsepower. The > main reasons for this are the ability to do a timed back-up to a network > resource, restore to a different location if there is a failure, migrate to > a different server long enough to change hard drives annually, and a host of > other features. The back-up and migration tools are essential. Plus, if the > container is rooted a remote command will rebuild the container > destructively or non-destructively. The horsepower is so that I can give > back to the community by offering the equivalent of a conference channel or > otherwise help someone else out. The last reason is to avoid timing issues. > Our goal is a hybrid of voted simulcast and non-voted but synced transmit on > one node. > > With all of this said has anyone actually tried to load ACID into a > Virtuozzo 4.7 container? I can build a regular server and write a bash > script that will TAR and move a back-up file with rsync. But Virtuozzo is a > team player and very comfortable for me. I have been running it on almost > all of our client servers since 2007. > > Blessings to all, > > Namaste > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Steve Zingman > Sent: Sunday, September 14, 2014 9:54 AM > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Virtual node > > Been there, doing that. I've been running Node 2100 as a hub on a VMware > VM for years. First as Debian Etch and now Wheezy. > > Steve N4IRS > > On 09/14/2014 12:00 PM, app_rpt-users-request at ohnosec.org wrote: >> Send App_rpt-users mailing list submissions to >> app_rpt-users at ohnosec.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> or, via email, send a message with subject or body 'help' to >> app_rpt-users-request at ohnosec.org >> >> You can reach the person managing the list at >> app_rpt-users-owner at ohnosec.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of App_rpt-users digest..." >> >> >> Today's Topics: >> >> 1. Re: Centos 5 with kernel 2.6.32-042stab093.4 (Lu Vencl) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sun, 14 Sep 2014 07:42:08 -0400 >> From: Lu Vencl >> To: Bryan Fields >> Cc: APP RPT >> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> Message-ID: <0EBFA15D-28D2-4381-A9B5-D59B12701A40 at att.net> >> Content-Type: text/plain; charset=utf-8 >> >> Been there and done it. It does not work. >> >> Lu Vencl >> >>> On Sep 13, 2014, at 11:25 PM, Bryan Fields wrote: >>> >>>> On 9/13/14, 11:19 PM, Tim Sawyer wrote: >>>> People have jumped on my butt for saying this before but I?ll say it > again >>>> anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, >>>> especially one for $5/mo. I?m not going to tell you not to do it, but if >>>> you do manage to jump the hurdles of getting Asterisk installed on a > hosted >>>> VPS, it may not work as it does on a $50 computer. >>> >>> I second this. Asterisk is one of those programs that is very timing >>> dependent. A virtual server, especially a $5/month VPS is not going to > work >>> well since there are 200 VM's all competing for processor time. >>> >>> This being said, there is no requirement that you run ACID. Grab it and >>> compile from source, I dislike redhat/centos, and run on debian just > fine. >>> >>> -- >>> Bryan Fields >>> >>> 727-409-1194 - Voice >>> 727-214-2508 - Fax >>> http://bryanfields.net >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at 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 at ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> >> End of App_rpt-users Digest, Vol 67, Issue 44 >> ********************************************* >> > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > > From wayne at anywherehost.net Sun Sep 14 20:52:43 2014 From: wayne at anywherehost.net (Wayne) Date: Sun, 14 Sep 2014 13:52:43 -0700 Subject: [App_rpt-users] Virtual node In-Reply-To: <5415FDBD.6080600@msgstor.com> References: <5415C83C.2080404@msgstor.com> <6C84853AD7F948F7B9C6283D5EC389FD@desktop> <5415FDBD.6080600@msgstor.com> Message-ID: <69BE75D6A5C648AEBA6D4353371F0DE1@desktop> I'm the newbie -- how does a hub work? What is its intended use? -----Original Message----- From: Steve Zingman [mailto:szingman at msgstor.com] Sent: Sunday, September 14, 2014 1:43 PM To: wayne at anywherehost.net; app_rpt-users at ohnosec.org Subject: Re: Virtual node One comment I forgot to make, Node 2100 is a HUB not a RF connected node. 73, Steve N4IRS On 09/14/2014 04:25 PM, Wayne wrote: > If it runs on VMWare why not ? > > As the System Administrator for the hosting company I work we run Virtuozzo > 4.7. We generally place two Plesk servers on one hardware node (dual > processor Intel XEON/64-bit 2.5GHz,L2 12MB cache, 16GB ECC RAM, and RAID > III.) Never do two fully functional servers conflict because we do not allow > over-use of resources. If the "dedicated server" VPS resources are small > enough to moderate we can run as many as 3-5 containers. > > With this said I have not yet tried to install ACID into an empty VPS > container. By default Virtuozzo creates a Centos 6.x shell with limited > files. If adding Plesk it will automatically pull from YUM for a complete > distro install. We have several Shoutcast servers configured this way but we > had to manually add dependent files. > > Now then, I want to run ACID on an identical machine and a RTCM but with > only ACID on one container regardless of the outstanding horsepower. The > main reasons for this are the ability to do a timed back-up to a network > resource, restore to a different location if there is a failure, migrate to > a different server long enough to change hard drives annually, and a host of > other features. The back-up and migration tools are essential. Plus, if the > container is rooted a remote command will rebuild the container > destructively or non-destructively. The horsepower is so that I can give > back to the community by offering the equivalent of a conference channel or > otherwise help someone else out. The last reason is to avoid timing issues. > Our goal is a hybrid of voted simulcast and non-voted but synced transmit on > one node. > > With all of this said has anyone actually tried to load ACID into a > Virtuozzo 4.7 container? I can build a regular server and write a bash > script that will TAR and move a back-up file with rsync. But Virtuozzo is a > team player and very comfortable for me. I have been running it on almost > all of our client servers since 2007. > > Blessings to all, > > Namaste > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Steve Zingman > Sent: Sunday, September 14, 2014 9:54 AM > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Virtual node > > Been there, doing that. I've been running Node 2100 as a hub on a VMware > VM for years. First as Debian Etch and now Wheezy. > > Steve N4IRS > > On 09/14/2014 12:00 PM, app_rpt-users-request at ohnosec.org wrote: >> Send App_rpt-users mailing list submissions to >> app_rpt-users at ohnosec.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> or, via email, send a message with subject or body 'help' to >> app_rpt-users-request at ohnosec.org >> >> You can reach the person managing the list at >> app_rpt-users-owner at ohnosec.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of App_rpt-users digest..." >> >> >> Today's Topics: >> >> 1. Re: Centos 5 with kernel 2.6.32-042stab093.4 (Lu Vencl) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sun, 14 Sep 2014 07:42:08 -0400 >> From: Lu Vencl >> To: Bryan Fields >> Cc: APP RPT >> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> Message-ID: <0EBFA15D-28D2-4381-A9B5-D59B12701A40 at att.net> >> Content-Type: text/plain; charset=utf-8 >> >> Been there and done it. It does not work. >> >> Lu Vencl >> >>> On Sep 13, 2014, at 11:25 PM, Bryan Fields wrote: >>> >>>> On 9/13/14, 11:19 PM, Tim Sawyer wrote: >>>> People have jumped on my butt for saying this before but I?ll say it > again >>>> anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, >>>> especially one for $5/mo. I?m not going to tell you not to do it, but if >>>> you do manage to jump the hurdles of getting Asterisk installed on a > hosted >>>> VPS, it may not work as it does on a $50 computer. >>> >>> I second this. Asterisk is one of those programs that is very timing >>> dependent. A virtual server, especially a $5/month VPS is not going to > work >>> well since there are 200 VM's all competing for processor time. >>> >>> This being said, there is no requirement that you run ACID. Grab it and >>> compile from source, I dislike redhat/centos, and run on debian just > fine. >>> >>> -- >>> Bryan Fields >>> >>> 727-409-1194 - Voice >>> 727-214-2508 - Fax >>> http://bryanfields.net >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at 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 at ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> >> End of App_rpt-users Digest, Vol 67, Issue 44 >> ********************************************* >> > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > > From robert at controlservers.net Sun Sep 14 21:19:44 2014 From: robert at controlservers.net (Robert) Date: Sun, 14 Sep 2014 14:19:44 -0700 Subject: [App_rpt-users] Virtual node In-Reply-To: <5415FB5B.70607@msgstor.com> References: <5415C83C.2080404@msgstor.com><6C84853AD7F948F7B9C6283D5EC389FD@desktop> <5415FB5B.70607@msgstor.com> Message-ID: By building it on my own do you mean installing all of CentOS and then getting a list of ACID files to and modify? If so how does one get a list of Allstar files? I can also install Debian. It's just a click away. I'm just more familiar with CentOS. Am I essentially installing a LAMP server? I just like the extra layer onto which an application of importance runs. THANK YOU for the reply. I appreciate you taking the time. -----Original Message----- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Steve Zingman Sent: Sunday, September 14, 2014 1:32 PM To: wayne at anywherehost.net; app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Virtual node Wayne, I can speak to Virtuozzo or trying to install Acid on anything. My preference has always been running Debian and "rolling my own" when it comes to Asterisk and AllStar. If you are going to try it on Centos, I would build it from scratch. 73, Steve N4IRS On 09/14/2014 04:25 PM, Wayne wrote: > If it runs on VMWare why not ? > > As the System Administrator for the hosting company I work we run Virtuozzo > 4.7. We generally place two Plesk servers on one hardware node (dual > processor Intel XEON/64-bit 2.5GHz,L2 12MB cache, 16GB ECC RAM, and RAID > III.) Never do two fully functional servers conflict because we do not allow > over-use of resources. If the "dedicated server" VPS resources are small > enough to moderate we can run as many as 3-5 containers. > > With this said I have not yet tried to install ACID into an empty VPS > container. By default Virtuozzo creates a Centos 6.x shell with limited > files. If adding Plesk it will automatically pull from YUM for a complete > distro install. We have several Shoutcast servers configured this way but we > had to manually add dependent files. > > Now then, I want to run ACID on an identical machine and a RTCM but with > only ACID on one container regardless of the outstanding horsepower. The > main reasons for this are the ability to do a timed back-up to a network > resource, restore to a different location if there is a failure, migrate to > a different server long enough to change hard drives annually, and a host of > other features. The back-up and migration tools are essential. Plus, if the > container is rooted a remote command will rebuild the container > destructively or non-destructively. The horsepower is so that I can give > back to the community by offering the equivalent of a conference channel or > otherwise help someone else out. The last reason is to avoid timing issues. > Our goal is a hybrid of voted simulcast and non-voted but synced transmit on > one node. > > With all of this said has anyone actually tried to load ACID into a > Virtuozzo 4.7 container? I can build a regular server and write a bash > script that will TAR and move a back-up file with rsync. But Virtuozzo is a > team player and very comfortable for me. I have been running it on almost > all of our client servers since 2007. > > Blessings to all, > > Namaste > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Steve Zingman > Sent: Sunday, September 14, 2014 9:54 AM > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Virtual node > > Been there, doing that. I've been running Node 2100 as a hub on a VMware > VM for years. First as Debian Etch and now Wheezy. > > Steve N4IRS > > On 09/14/2014 12:00 PM, app_rpt-users-request at ohnosec.org wrote: >> Send App_rpt-users mailing list submissions to >> app_rpt-users at ohnosec.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> or, via email, send a message with subject or body 'help' to >> app_rpt-users-request at ohnosec.org >> >> You can reach the person managing the list at >> app_rpt-users-owner at ohnosec.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of App_rpt-users digest..." >> >> >> Today's Topics: >> >> 1. Re: Centos 5 with kernel 2.6.32-042stab093.4 (Lu Vencl) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sun, 14 Sep 2014 07:42:08 -0400 >> From: Lu Vencl >> To: Bryan Fields >> Cc: APP RPT >> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >> Message-ID: <0EBFA15D-28D2-4381-A9B5-D59B12701A40 at att.net> >> Content-Type: text/plain; charset=utf-8 >> >> Been there and done it. It does not work. >> >> Lu Vencl >> >>> On Sep 13, 2014, at 11:25 PM, Bryan Fields wrote: >>> >>>> On 9/13/14, 11:19 PM, Tim Sawyer wrote: >>>> People have jumped on my butt for saying this before but I?ll say it > again >>>> anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, >>>> especially one for $5/mo. I?m not going to tell you not to do it, but if >>>> you do manage to jump the hurdles of getting Asterisk installed on a > hosted >>>> VPS, it may not work as it does on a $50 computer. >>> >>> I second this. Asterisk is one of those programs that is very timing >>> dependent. A virtual server, especially a $5/month VPS is not going to > work >>> well since there are 200 VM's all competing for processor time. >>> >>> This being said, there is no requirement that you run ACID. Grab it and >>> compile from source, I dislike redhat/centos, and run on debian just > fine. >>> >>> -- >>> Bryan Fields >>> >>> 727-409-1194 - Voice >>> 727-214-2508 - Fax >>> http://bryanfields.net >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at 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 at ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> >> End of App_rpt-users Digest, Vol 67, Issue 44 >> ********************************************* >> > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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. From szingman at msgstor.com Sun Sep 14 21:31:05 2014 From: szingman at msgstor.com (Steve Zingman) Date: Sun, 14 Sep 2014 17:31:05 -0400 Subject: [App_rpt-users] Virtual node In-Reply-To: References: <5415C83C.2080404@msgstor.com><6C84853AD7F948F7B9C6283D5EC389FD@desktop> <5415FB5B.70607@msgstor.com> Message-ID: <54160919.1020502@msgstor.com> The basics are the same no matter which flavor of Linux you run. Install the base operating system. Install the required libraries for Asterisk. Download the source, compile and install. Setup the configuration file and go. You are building Asterisk the same way Jim builds it to create the Acid image. The nice thing about building a virtual machine is that it's easy to stop take a snapshot and then go on. If you have a problem, revert to the last snapshot and go from there. Steve On 09/14/2014 05:19 PM, Robert wrote: > By building it on my own do you mean installing all of CentOS and then > getting a list of ACID files to and modify? If so how does one get a list of > Allstar files? I can also install Debian. It's just a click away. I'm just > more familiar with CentOS. Am I essentially installing a LAMP server? > > I just like the extra layer onto which an application of importance runs. > > THANK YOU for the reply. I appreciate you taking the time. > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Steve Zingman > Sent: Sunday, September 14, 2014 1:32 PM > To: wayne at anywherehost.net; app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Virtual node > > Wayne, > I can speak to Virtuozzo or trying to install Acid on anything. > My preference has always been running Debian and "rolling my own" when > it comes to Asterisk and AllStar. > > If you are going to try it on Centos, I would build it from scratch. > > 73, Steve N4IRS > > On 09/14/2014 04:25 PM, Wayne wrote: >> If it runs on VMWare why not ? >> >> As the System Administrator for the hosting company I work we run > Virtuozzo >> 4.7. We generally place two Plesk servers on one hardware node (dual >> processor Intel XEON/64-bit 2.5GHz,L2 12MB cache, 16GB ECC RAM, and RAID >> III.) Never do two fully functional servers conflict because we do not > allow >> over-use of resources. If the "dedicated server" VPS resources are small >> enough to moderate we can run as many as 3-5 containers. >> >> With this said I have not yet tried to install ACID into an empty VPS >> container. By default Virtuozzo creates a Centos 6.x shell with limited >> files. If adding Plesk it will automatically pull from YUM for a complete >> distro install. We have several Shoutcast servers configured this way but > we >> had to manually add dependent files. >> >> Now then, I want to run ACID on an identical machine and a RTCM but with >> only ACID on one container regardless of the outstanding horsepower. The >> main reasons for this are the ability to do a timed back-up to a network >> resource, restore to a different location if there is a failure, migrate > to >> a different server long enough to change hard drives annually, and a host > of >> other features. The back-up and migration tools are essential. Plus, if > the >> container is rooted a remote command will rebuild the container >> destructively or non-destructively. The horsepower is so that I can give >> back to the community by offering the equivalent of a conference channel > or >> otherwise help someone else out. The last reason is to avoid timing > issues. >> Our goal is a hybrid of voted simulcast and non-voted but synced transmit > on >> one node. >> >> With all of this said has anyone actually tried to load ACID into a >> Virtuozzo 4.7 container? I can build a regular server and write a bash >> script that will TAR and move a back-up file with rsync. But Virtuozzo is > a >> team player and very comfortable for me. I have been running it on almost >> all of our client servers since 2007. >> >> Blessings to all, >> >> Namaste >> >> -----Original Message----- >> From: app_rpt-users-bounces at ohnosec.org >> [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Steve Zingman >> Sent: Sunday, September 14, 2014 9:54 AM >> To: app_rpt-users at ohnosec.org >> Subject: [App_rpt-users] Virtual node >> >> Been there, doing that. I've been running Node 2100 as a hub on a VMware >> VM for years. First as Debian Etch and now Wheezy. >> >> Steve N4IRS >> >> On 09/14/2014 12:00 PM, app_rpt-users-request at ohnosec.org wrote: >>> Send App_rpt-users mailing list submissions to >>> app_rpt-users at ohnosec.org >>> >>> To subscribe or unsubscribe via the World Wide Web, visit >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >>> or, via email, send a message with subject or body 'help' to >>> app_rpt-users-request at ohnosec.org >>> >>> You can reach the person managing the list at >>> app_rpt-users-owner at ohnosec.org >>> >>> When replying, please edit your Subject line so it is more specific >>> than "Re: Contents of App_rpt-users digest..." >>> >>> >>> Today's Topics: >>> >>> 1. Re: Centos 5 with kernel 2.6.32-042stab093.4 (Lu Vencl) >>> >>> >>> ---------------------------------------------------------------------- >>> >>> Message: 1 >>> Date: Sun, 14 Sep 2014 07:42:08 -0400 >>> From: Lu Vencl >>> To: Bryan Fields >>> Cc: APP RPT >>> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >>> Message-ID: <0EBFA15D-28D2-4381-A9B5-D59B12701A40 at att.net> >>> Content-Type: text/plain; charset=utf-8 >>> >>> Been there and done it. It does not work. >>> >>> Lu Vencl >>> >>>> On Sep 13, 2014, at 11:25 PM, Bryan Fields > wrote: >>>> >>>>> On 9/13/14, 11:19 PM, Tim Sawyer wrote: >>>>> People have jumped on my butt for saying this before but I?ll say it >> again >>>>> anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, >>>>> especially one for $5/mo. I?m not going to tell you not to do it, but > if >>>>> you do manage to jump the hurdles of getting Asterisk installed on a >> hosted >>>>> VPS, it may not work as it does on a $50 computer. >>>> >>>> I second this. Asterisk is one of those programs that is very timing >>>> dependent. A virtual server, especially a $5/month VPS is not going to >> work >>>> well since there are 200 VM's all competing for processor time. >>>> >>>> This being said, there is no requirement that you run ACID. Grab it and >>>> compile from source, I dislike redhat/centos, and run on debian just >> fine. >>>> >>>> -- >>>> Bryan Fields >>>> >>>> 727-409-1194 - Voice >>>> 727-214-2508 - Fax >>>> http://bryanfields.net >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at 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 at ohnosec.org >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> >>> End of App_rpt-users Digest, Vol 67, Issue 44 >>> ********************************************* >>> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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 at 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. > > From szingman at msgstor.com Sun Sep 14 21:38:56 2014 From: szingman at msgstor.com (Steve Zingman) Date: Sun, 14 Sep 2014 17:38:56 -0400 Subject: [App_rpt-users] Virtual node In-Reply-To: <69BE75D6A5C648AEBA6D4353371F0DE1@desktop> References: <5415C83C.2080404@msgstor.com> <6C84853AD7F948F7B9C6283D5EC389FD@desktop> <5415FDBD.6080600@msgstor.com> <69BE75D6A5C648AEBA6D4353371F0DE1@desktop> Message-ID: <54160AF0.7030207@msgstor.com> As the word implies, a hub is a node that other nodes connect to. The idea is that a lot of nodes have enough bandwidth for one or two connections. You can mesh nodes as in: a connects to b connects to c etc. In a hub or star configuration, a b and c all connect to the hub. A Virtual hub does not have any RF gear connected to it and is usually on a high bandwidth Internet connection. 73, Steve N4IRS On 09/14/2014 04:52 PM, Wayne wrote: > I'm the newbie -- how does a hub work? What is its intended use? > > -----Original Message----- > From: Steve Zingman [mailto:szingman at msgstor.com] > Sent: Sunday, September 14, 2014 1:43 PM > To: wayne at anywherehost.net; app_rpt-users at ohnosec.org > Subject: Re: Virtual node > > One comment I forgot to make, Node 2100 is a HUB not a RF connected node. > > 73, Steve N4IRS > > On 09/14/2014 04:25 PM, Wayne wrote: >> If it runs on VMWare why not ? >> >> As the System Administrator for the hosting company I work we run > Virtuozzo >> 4.7. We generally place two Plesk servers on one hardware node (dual >> processor Intel XEON/64-bit 2.5GHz,L2 12MB cache, 16GB ECC RAM, and RAID >> III.) Never do two fully functional servers conflict because we do not > allow >> over-use of resources. If the "dedicated server" VPS resources are small >> enough to moderate we can run as many as 3-5 containers. >> >> With this said I have not yet tried to install ACID into an empty VPS >> container. By default Virtuozzo creates a Centos 6.x shell with limited >> files. If adding Plesk it will automatically pull from YUM for a complete >> distro install. We have several Shoutcast servers configured this way but > we >> had to manually add dependent files. >> >> Now then, I want to run ACID on an identical machine and a RTCM but with >> only ACID on one container regardless of the outstanding horsepower. The >> main reasons for this are the ability to do a timed back-up to a network >> resource, restore to a different location if there is a failure, migrate > to >> a different server long enough to change hard drives annually, and a host > of >> other features. The back-up and migration tools are essential. Plus, if > the >> container is rooted a remote command will rebuild the container >> destructively or non-destructively. The horsepower is so that I can give >> back to the community by offering the equivalent of a conference channel > or >> otherwise help someone else out. The last reason is to avoid timing > issues. >> Our goal is a hybrid of voted simulcast and non-voted but synced transmit > on >> one node. >> >> With all of this said has anyone actually tried to load ACID into a >> Virtuozzo 4.7 container? I can build a regular server and write a bash >> script that will TAR and move a back-up file with rsync. But Virtuozzo is > a >> team player and very comfortable for me. I have been running it on almost >> all of our client servers since 2007. >> >> Blessings to all, >> >> Namaste >> >> -----Original Message----- >> From: app_rpt-users-bounces at ohnosec.org >> [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Steve Zingman >> Sent: Sunday, September 14, 2014 9:54 AM >> To: app_rpt-users at ohnosec.org >> Subject: [App_rpt-users] Virtual node >> >> Been there, doing that. I've been running Node 2100 as a hub on a VMware >> VM for years. First as Debian Etch and now Wheezy. >> >> Steve N4IRS >> >> On 09/14/2014 12:00 PM, app_rpt-users-request at ohnosec.org wrote: >>> Send App_rpt-users mailing list submissions to >>> app_rpt-users at ohnosec.org >>> >>> To subscribe or unsubscribe via the World Wide Web, visit >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >>> or, via email, send a message with subject or body 'help' to >>> app_rpt-users-request at ohnosec.org >>> >>> You can reach the person managing the list at >>> app_rpt-users-owner at ohnosec.org >>> >>> When replying, please edit your Subject line so it is more specific >>> than "Re: Contents of App_rpt-users digest..." >>> >>> >>> Today's Topics: >>> >>> 1. Re: Centos 5 with kernel 2.6.32-042stab093.4 (Lu Vencl) >>> >>> >>> ---------------------------------------------------------------------- >>> >>> Message: 1 >>> Date: Sun, 14 Sep 2014 07:42:08 -0400 >>> From: Lu Vencl >>> To: Bryan Fields >>> Cc: APP RPT >>> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >>> Message-ID: <0EBFA15D-28D2-4381-A9B5-D59B12701A40 at att.net> >>> Content-Type: text/plain; charset=utf-8 >>> >>> Been there and done it. It does not work. >>> >>> Lu Vencl >>> >>>> On Sep 13, 2014, at 11:25 PM, Bryan Fields > wrote: >>>> >>>>> On 9/13/14, 11:19 PM, Tim Sawyer wrote: >>>>> People have jumped on my butt for saying this before but I?ll say it >> again >>>>> anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, >>>>> especially one for $5/mo. I?m not going to tell you not to do it, but > if >>>>> you do manage to jump the hurdles of getting Asterisk installed on a >> hosted >>>>> VPS, it may not work as it does on a $50 computer. >>>> >>>> I second this. Asterisk is one of those programs that is very timing >>>> dependent. A virtual server, especially a $5/month VPS is not going to >> work >>>> well since there are 200 VM's all competing for processor time. >>>> >>>> This being said, there is no requirement that you run ACID. Grab it and >>>> compile from source, I dislike redhat/centos, and run on debian just >> fine. >>>> >>>> -- >>>> Bryan Fields >>>> >>>> 727-409-1194 - Voice >>>> 727-214-2508 - Fax >>>> http://bryanfields.net >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at 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 at ohnosec.org >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> >>> End of App_rpt-users Digest, Vol 67, Issue 44 >>> ********************************************* >>> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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. >> >> > > From wayne at anywherehost.net Sun Sep 14 21:51:28 2014 From: wayne at anywherehost.net (Wayne) Date: Sun, 14 Sep 2014 14:51:28 -0700 Subject: [App_rpt-users] Virtual node In-Reply-To: <54160AF0.7030207@msgstor.com> References: <5415C83C.2080404@msgstor.com> <6C84853AD7F948F7B9C6283D5EC389FD@desktop> <5415FDBD.6080600@msgstor.com> <69BE75D6A5C648AEBA6D4353371F0DE1@desktop> <54160AF0.7030207@msgstor.com> Message-ID: <59CA3960EB454902B9721E86175388E0@desktop> OK. Since our ACID server is going into a high bandwidth data center I am going to need to visualize the topology. It has always been our hope to publicize one node number since if a major emergency occurs (earthquake) Internet will likely be down anyway. -----Original Message----- From: Steve Zingman [mailto:szingman at msgstor.com] Sent: Sunday, September 14, 2014 2:39 PM To: wayne at anywherehost.net; app_rpt-users at ohnosec.org Subject: Re: Virtual node As the word implies, a hub is a node that other nodes connect to. The idea is that a lot of nodes have enough bandwidth for one or two connections. You can mesh nodes as in: a connects to b connects to c etc. In a hub or star configuration, a b and c all connect to the hub. A Virtual hub does not have any RF gear connected to it and is usually on a high bandwidth Internet connection. 73, Steve N4IRS On 09/14/2014 04:52 PM, Wayne wrote: > I'm the newbie -- how does a hub work? What is its intended use? > > -----Original Message----- > From: Steve Zingman [mailto:szingman at msgstor.com] > Sent: Sunday, September 14, 2014 1:43 PM > To: wayne at anywherehost.net; app_rpt-users at ohnosec.org > Subject: Re: Virtual node > > One comment I forgot to make, Node 2100 is a HUB not a RF connected node. > > 73, Steve N4IRS > > On 09/14/2014 04:25 PM, Wayne wrote: >> If it runs on VMWare why not ? >> >> As the System Administrator for the hosting company I work we run > Virtuozzo >> 4.7. We generally place two Plesk servers on one hardware node (dual >> processor Intel XEON/64-bit 2.5GHz,L2 12MB cache, 16GB ECC RAM, and RAID >> III.) Never do two fully functional servers conflict because we do not > allow >> over-use of resources. If the "dedicated server" VPS resources are small >> enough to moderate we can run as many as 3-5 containers. >> >> With this said I have not yet tried to install ACID into an empty VPS >> container. By default Virtuozzo creates a Centos 6.x shell with limited >> files. If adding Plesk it will automatically pull from YUM for a complete >> distro install. We have several Shoutcast servers configured this way but > we >> had to manually add dependent files. >> >> Now then, I want to run ACID on an identical machine and a RTCM but with >> only ACID on one container regardless of the outstanding horsepower. The >> main reasons for this are the ability to do a timed back-up to a network >> resource, restore to a different location if there is a failure, migrate > to >> a different server long enough to change hard drives annually, and a host > of >> other features. The back-up and migration tools are essential. Plus, if > the >> container is rooted a remote command will rebuild the container >> destructively or non-destructively. The horsepower is so that I can give >> back to the community by offering the equivalent of a conference channel > or >> otherwise help someone else out. The last reason is to avoid timing > issues. >> Our goal is a hybrid of voted simulcast and non-voted but synced transmit > on >> one node. >> >> With all of this said has anyone actually tried to load ACID into a >> Virtuozzo 4.7 container? I can build a regular server and write a bash >> script that will TAR and move a back-up file with rsync. But Virtuozzo is > a >> team player and very comfortable for me. I have been running it on almost >> all of our client servers since 2007. >> >> Blessings to all, >> >> Namaste >> >> -----Original Message----- >> From: app_rpt-users-bounces at ohnosec.org >> [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Steve Zingman >> Sent: Sunday, September 14, 2014 9:54 AM >> To: app_rpt-users at ohnosec.org >> Subject: [App_rpt-users] Virtual node >> >> Been there, doing that. I've been running Node 2100 as a hub on a VMware >> VM for years. First as Debian Etch and now Wheezy. >> >> Steve N4IRS >> >> On 09/14/2014 12:00 PM, app_rpt-users-request at ohnosec.org wrote: >>> Send App_rpt-users mailing list submissions to >>> app_rpt-users at ohnosec.org >>> >>> To subscribe or unsubscribe via the World Wide Web, visit >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >>> or, via email, send a message with subject or body 'help' to >>> app_rpt-users-request at ohnosec.org >>> >>> You can reach the person managing the list at >>> app_rpt-users-owner at ohnosec.org >>> >>> When replying, please edit your Subject line so it is more specific >>> than "Re: Contents of App_rpt-users digest..." >>> >>> >>> Today's Topics: >>> >>> 1. Re: Centos 5 with kernel 2.6.32-042stab093.4 (Lu Vencl) >>> >>> >>> ---------------------------------------------------------------------- >>> >>> Message: 1 >>> Date: Sun, 14 Sep 2014 07:42:08 -0400 >>> From: Lu Vencl >>> To: Bryan Fields >>> Cc: APP RPT >>> Subject: Re: [App_rpt-users] Centos 5 with kernel 2.6.32-042stab093.4 >>> Message-ID: <0EBFA15D-28D2-4381-A9B5-D59B12701A40 at att.net> >>> Content-Type: text/plain; charset=utf-8 >>> >>> Been there and done it. It does not work. >>> >>> Lu Vencl >>> >>>> On Sep 13, 2014, at 11:25 PM, Bryan Fields > wrote: >>>> >>>>> On 9/13/14, 11:19 PM, Tim Sawyer wrote: >>>>> People have jumped on my butt for saying this before but I?ll say it >> again >>>>> anyway. It?s very unlikely Asterisk will run worth a damn on a VPS, >>>>> especially one for $5/mo. I?m not going to tell you not to do it, but > if >>>>> you do manage to jump the hurdles of getting Asterisk installed on a >> hosted >>>>> VPS, it may not work as it does on a $50 computer. >>>> >>>> I second this. Asterisk is one of those programs that is very timing >>>> dependent. A virtual server, especially a $5/month VPS is not going to >> work >>>> well since there are 200 VM's all competing for processor time. >>>> >>>> This being said, there is no requirement that you run ACID. Grab it and >>>> compile from source, I dislike redhat/centos, and run on debian just >> fine. >>>> >>>> -- >>>> Bryan Fields >>>> >>>> 727-409-1194 - Voice >>>> 727-214-2508 - Fax >>>> http://bryanfields.net >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at 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 at ohnosec.org >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> >>> End of App_rpt-users Digest, Vol 67, Issue 44 >>> ********************************************* >>> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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. >> >> > > From cypresstower at yahoo.com Mon Sep 15 03:50:11 2014 From: cypresstower at yahoo.com (Johnny Keeker) Date: Sun, 14 Sep 2014 20:50:11 -0700 Subject: [App_rpt-users] rc.updatenodelist fails. In-Reply-To: <5415125D.3090304@bryanfields.net> Message-ID: <1410753011.32456.YahooMailBasic@web163606.mail.gq1.yahoo.com> I've also experienced this occurrence, yet only appears on one of the node servers in service. I Didn't make mention of it because I have no solution on hand. JK -------------------------------------------- On Sat, 9/13/14, Bryan Fields wrote: Subject: Re: [App_rpt-users] rc.updatenodelist fails. To: "Bob" , "'Tim Sawyer'" , "'APP RPT'" Date: Saturday, September 13, 2014, 11:58 PM I've had three other people on IRC test this and I've tested this from 3 different servers myself. All are giving an error 403 on: http://nodes1.allstarlink.org/cgi-bin/nodes.pl I don't think it's just me :( On 9/13/14, 11:50 PM, Bob wrote: > Works fine here. > > -----Original Message----- > From: app_rpt-users-bounces at ohnosec.org > [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Bryan Fields > Sent: Saturday, September 13, 2014 8:32 PM > To: Tim Sawyer; APP RPT > Subject: Re: [App_rpt-users] rc.updatenodelist fails. > > Thanks Tim, > > However, I'm getting 403 errors on each. > > Perhaps some kinda IP block issue or something? > > root at KB9MCI:/etc/rc.d# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl > --2014-09-13 23:26:54--? http://nodes1.allstarlink.org/cgi-bin/nodes.pl > Resolving nodes1.allstarlink.org... 96.36.57.202 > Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. > HTTP request sent, awaiting response... 403 > 2014-09-13 23:26:54 ERROR 403: (no description). > > root at KB9MCI:/etc/rc.d# wget http://nodes2.allstarlink.org/cgi-bin/nodes.pl > --2014-09-13 23:27:00--? http://nodes2.allstarlink.org/cgi-bin/nodes.pl > Resolving nodes2.allstarlink.org... 209.159.155.200 > Connecting to nodes2.allstarlink.org|209.159.155.200|:80... connected. > HTTP request sent, awaiting response... 403 Forbidden > 2014-09-13 23:27:00 ERROR 403: Forbidden. > > root at KB9MCI:/etc/rc.d# wget http://nodes3.allstarlink.org/cgi-bin/nodes.pl > --2014-09-13 23:27:06--? http://nodes3.allstarlink.org/cgi-bin/nodes.pl > Resolving nodes3.allstarlink.org... 65.110.110.172 > Connecting to nodes3.allstarlink.org|65.110.110.172|:80... connected. > HTTP request sent, awaiting response... 403 > 2014-09-13 23:27:06 ERROR 403: (no description). > > root at KB9MCI:/etc/rc.d# wget http://nodes4.allstarlink.org/cgi-bin/nodes.pl > --2014-09-13 23:27:11--? http://nodes4.allstarlink.org/cgi-bin/nodes.pl > Resolving nodes4.allstarlink.org... 67.214.190.109 > Connecting to nodes4.allstarlink.org|67.214.190.109|:80... connected. > HTTP request sent, awaiting response... 403 Forbidden > 2014-09-13 23:27:12 ERROR 403: Forbidden. > > > > > > On 9/13/14, 11:23 PM, Tim Sawyer wrote: >> Works for me. >> >> >> Resolving nodes1.allstarlink.org... 96.36.57.202 >> Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. >> HTTP request sent, awaiting response... 200 OK >> Length: unspecified [text/plain] >> Saving to: `/var/lib/asterisk/rpt_extnodes-temp' >> >>? ???[? <=> > ] 64,417? ? ???225K/s???in 0.3s? ? >> >> 2014-09-13 20:19:36 (225 KB/s) - `/var/lib/asterisk/rpt_extnodes-temp' > saved [64417] >> >> Retrieved node list from nodes1.allstarlink.org >> >> -- >> Tim WD6AWP >> >>> On Sep 13, 2014, at 8:13 PM, Bryan Fields wrote: >>> >>> This is not working, looks like all the servers are not responding. >>> >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > server >>> Problem retrieving node list from nodes2.allstarlink.org, trying another > server >>> Problem retrieving node list from nodes3.allstarlink.org, trying another > server >>> Problem retrieving node list from nodes4.allstarlink.org, trying another > server >>> Problem retrieving node list from nodes1.allstarlink.org, trying another > server >>> >>> Ideas? >>> >>> -- >>> Bryan Fields >>> >>> 727-409-1194 - Voice >>> 727-214-2508 - Fax >>> http://bryanfields.net >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at 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. >> > > -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. From ars.w5omr at gmail.com Mon Sep 15 10:30:47 2014 From: ars.w5omr at gmail.com (Geoff) Date: Mon, 15 Sep 2014 05:30:47 -0500 Subject: [App_rpt-users] Ideas (Mobile App) In-Reply-To: References: Message-ID: <5416BFD7.2070106@gmail.com> On 09/11/2014 02:59 PM, Loren Tedford wrote: > What about a system that is similar to lets say Echolink in the > ability to search and select what repeater you want to add to your > quick list then use this to connect to the repeater through a web > transceiver like setup kinda like an all in one type software.. If i > understood what you were talking about this you would have to setup up > repeater side individually for each user.. Once you get a bit more familiar with the software and read a bit more about it's capabilities, then perhaps you can answer your own questions... but in the meantime, check into 'scheduling', 'iax' and 'macros'. Once a macro is set in rpt.conf you can dial it with a (as few as) 3 digit code, the first two being the standard macro access command. ;-) If there's another allstar node you wish to connect to all the time (to link the nodes together) see 'startup macro'. Lots of information out there, but basically, it's this: Allstar is the radio/repeater control software with the ability to link. It's not 'end-user' stuff, and there are no 'phone apps' to access it from the 'end user' side of things. The "end user" in this type of setup, is the radio/repeater User (and you don't want -them- with access to your castle! That's what the moat and drawbridge are for, right? ;-) ) As the System Operator/Administrator, -you- have the keys to your castle and can do with it as you please. Allstar is fun, very technical, challenging (most times) in finding good documentation and all around does an awesome job in linking two radios/repeaters or combinations thereof together. 73 = Best Regards -Geoff/W5OMR From ars.w5omr at gmail.com Mon Sep 15 10:48:30 2014 From: ars.w5omr at gmail.com (Geoff) Date: Mon, 15 Sep 2014 05:48:30 -0500 Subject: [App_rpt-users] Connection failed In-Reply-To: References: Message-ID: <5416C3FE.10106@gmail.com> On 09/12/2014 10:36 AM, Robert Newberry wrote: > > So the power was cut to the building my repeater is in. My repeater > functions, I'm able to connect via IAX. I'm also able to SSH in and > ping the IP of the node I'm trying to connect too (27066) I'm also > able to ping google.com . but when I go to the CLI > and type rpt fun 27086 *327066 it fails. > > So what gives? > > I'm running acid and a DMK URI. > Do you have access to the firewall on the router? If it were me, I think I'd first find out who/what/where/when I was getting an IP address from (since the building's power was cut, it stands to reason that perhaps the IT guy plugged in the router/switch to a non-emergency line (like your repeater is plugged into) and if you're on wifi, no telling WHERE that thing might be connected. I'm thinking that you're probably connected to another system that doesn't have the port forwarded in the firewall to allow incoming connections. Why it's not allowing -outgoing- connections, well... that's a horse of a different corral. Soooo... Your machine, right? You have control codes, right? Does the repeater respond to radio DTMF controls? how about from the command prompt? Let's first verify this is going to work. Some ssh terminal programs have problems. So, going on the assumption you do not have physical access to that machine, let's first SSH into it: local_system:#~> ssh -p222 root at ip.address.to.node the wait for the password prompt and enter it correctly. Once you're in, let's see who we're connected to, without going through the command line. [root@[your_call] /] asterisk -rx "rpt nodes 27086" and observe the output. then try [root@[your_call] /]# asterisk -rx "rpt fun 27086 *327066" Anything? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ars.w5omr at gmail.com Mon Sep 15 10:53:51 2014 From: ars.w5omr at gmail.com (Geoff) Date: Mon, 15 Sep 2014 05:53:51 -0500 Subject: [App_rpt-users] Virtual node In-Reply-To: <5415FB5B.70607@msgstor.com> References: <5415C83C.2080404@msgstor.com> <6C84853AD7F948F7B9C6283D5EC389FD@desktop> <5415FB5B.70607@msgstor.com> Message-ID: <5416C53F.3080702@gmail.com> On 09/14/2014 03:32 PM, Steve Zingman wrote: > Wayne, > I can speak to Virtuozzo or trying to install Acid on anything. > My preference has always been running Debian and "rolling my own" when > it comes to Asterisk and AllStar. > > If you are going to try it on Centos, I would build it from scratch. > > 73, Steve N4IRS > Uhm... ACID comes (or, did when *I* set my node up) on CentOS 5.x, as default. Why not use that, instead of building from scratch? From szingman at msgstor.com Mon Sep 15 13:33:43 2014 From: szingman at msgstor.com (Steve Zingman) Date: Mon, 15 Sep 2014 09:33:43 -0400 Subject: [App_rpt-users] Virtual node In-Reply-To: <69BE75D6A5C648AEBA6D4353371F0DE1@desktop> References: <5415C83C.2080404@msgstor.com> <6C84853AD7F948F7B9C6283D5EC389FD@desktop> <5415FDBD.6080600@msgstor.com> <69BE75D6A5C648AEBA6D4353371F0DE1@desktop> Message-ID: <5416EAB7.5060901@msgstor.com> > Uhm... ACID comes (or, did when *I* set my node up) on CentOS 5.x, as > default. Why not use that, instead of building from scratch? I was speaking in the context of creating a VM. That being said, I always prefer rolling my own. That way I control what is installed on the machine. 73, Steve N4IRS From ars.w5omr at gmail.com Mon Sep 15 13:41:16 2014 From: ars.w5omr at gmail.com (Geoff) Date: Mon, 15 Sep 2014 08:41:16 -0500 Subject: [App_rpt-users] Virtual node In-Reply-To: <59CA3960EB454902B9721E86175388E0@desktop> References: <5415C83C.2080404@msgstor.com> <6C84853AD7F948F7B9C6283D5EC389FD@desktop> <5415FDBD.6080600@msgstor.com> <69BE75D6A5C648AEBA6D4353371F0DE1@desktop> <54160AF0.7030207@msgstor.com> <59CA3960EB454902B9721E86175388E0@desktop> Message-ID: <5416EC7C.8050107@gmail.com> On 09/14/2014 04:51 PM, Wayne wrote: > OK. Since our ACID server is going into a high bandwidth data center I am > going to need to visualize the topology. It has always been our hope to > publicize one node number since if a major emergency occurs (earthquake) > Internet will likely be down anyway. But, more than likely, your server at the DC will still be up and running, and acting as a Hub (or will there be RF there, as well?) I'm all for the idea that, if possible, connect a Hub at a 'Star' repeater site (one that has awesome height and coverage) with the awesome repeater, and a link repeater on 220MHz or higher (per Eff Cee Cee rules and regumalations). You could use something in the upper UHF range as the local-access repeater and something in the 420MHz range for the link-repeater. Or, 900MHz/1.2GHz, a Gunnplexer at 10GHz, etc...) , if you've got the RF path for it. Any combination of frequencies would work, so long as it falls under the FCC and/or local coordinator action (boy, them guys in Utah are rather anal about their frequency coordination, aren't they? Whoever heard of asking a statewide coordinator if you could put up a Simplex node? But, I digress...) Use allstar at the satellite sites as a repeater controller, only. Two nodes. Site consists of a radio/repeater and a link radio, and each has a node, or private node number. To bring that particular machine on or off the link, just disconnect the link radio from the accessible radio/repeater, then it becomes stand-alone. See, you're not using Allstar to connect the MAIN repeater to the satellite repeater... That connection is made via RF from the satellite sites to the HUB -link- repeater. Allstar at the satellite sites, with a machine controlling the two nodes, and doing the audio/dsp/etc thing. You could either enable or disable it locally with DTMF codes, if there was no internet at the site. What's the upside to all this (what would eventually be) massive equipment build-up? Reliable RF connectivity. IN MY OPINION, Each site could/should be built with an 'off-the-grid' scenario in mind. Battery backup, solar-powered, generator, whatever it takes to keep the site up and running, should the infrastructure fail. And, with small voltage/current devices available (such as a Beagle Bone, just as an example) not much is required at the site, save for the power required to maintain the power output of the radios. Technology has advance to the point where just about anything can be used to keep a small bank of batteries charged up enough to run the radios for a few days. A 5v regulator and some simple circuitry could supply the low-voltage stuff. Each site should be capable of being independent from commercial mains, when they're not available. Let's keep in mind that The NUMBER ONE function of Amateur Radio is that it's available for Emergency Communication. During the 'good times' (non-emergency), linking several sites together brings folks and communities together, be it rag-chewing, or maybe a rainfall net, or what have you, but when disaster strikes, a well planned and maintained link system could be used to provide disaster relief to affected areas. I think that Allstar is the best vehicle to use to facilitate those communication needs. When things are setup properly, the 'First Responders' need to be able to just 'key the mic and talk'. 73 = Best Regards, -Geoff/W5OMR From wayne at anywherehost.net Tue Sep 16 03:49:17 2014 From: wayne at anywherehost.net (Wayne) Date: Mon, 15 Sep 2014 20:49:17 -0700 Subject: [App_rpt-users] Virtual node In-Reply-To: <5416C53F.3080702@gmail.com> References: <5415C83C.2080404@msgstor.com> <6C84853AD7F948F7B9C6283D5EC389FD@desktop><5415FB5B.70607@msgstor.com> <5416C53F.3080702@gmail.com> Message-ID: <728FD65FB39545CBBCC37D82614CB9EB@desktop> CentOS 5.2 is seriously out-dated with well known exploits. CentOS 7 just came out, otherwise you have v6.5. http://wiki.centos.org/Download Does ACID contain its own kernel? I am still waiting for my RTCM to arrive in the mail and haven't installed the OS yet. -----Original Message----- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Geoff Sent: Monday, September 15, 2014 3:54 AM To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Virtual node On 09/14/2014 03:32 PM, Steve Zingman wrote: > Wayne, > I can speak to Virtuozzo or trying to install Acid on anything. > My preference has always been running Debian and "rolling my own" when > it comes to Asterisk and AllStar. > > If you are going to try it on Centos, I would build it from scratch. > > 73, Steve N4IRS > Uhm... ACID comes (or, did when *I* set my node up) on CentOS 5.x, as default. Why not use that, instead of building from scratch? _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. From robert at controlservers.net Tue Sep 16 06:01:09 2014 From: robert at controlservers.net (Robert) Date: Mon, 15 Sep 2014 23:01:09 -0700 Subject: [App_rpt-users] MSF to RTCM Wiring Message-ID: I have seen so many different ways of how to wire a controller / RTCM to a MSF 5000 - is there one sure fired way to do this? Poor eyesight on my part. I hate being the new guy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorentedford at gmail.com Tue Sep 16 14:13:38 2014 From: lorentedford at gmail.com (Loren Tedford) Date: Tue, 16 Sep 2014 09:13:38 -0500 Subject: [App_rpt-users] Trouble shooting Message-ID: Hey its Loren here I am working on our repeater system out here in Olney IL we put in a pico power supply and a few other things including a motherboard we reinstalled from the Acid cd and for some reason we are not passing audio full duplex through the RX side of the repeater suddenly.. Seems strange because the repeater can still capture DTMF makes me wonder if maybe its trying to pick up a ctcss tone or some thing idk did all the trouble shooting I could think of all night last night and still no luck any ideas???? Loren Tedford (KC9ZHV) Email: lorentedford at gmail.com http://www.lorentedford.com http://kc9zhv.lorentedford.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From asylthe at kc9ona.com Tue Sep 16 14:22:51 2014 From: asylthe at kc9ona.com (Andrew Sylthe) Date: Tue, 16 Sep 2014 09:22:51 -0500 Subject: [App_rpt-users] Trouble shooting In-Reply-To: References: Message-ID: Is your duplex set correctly in the config? On Tuesday, September 16, 2014, Loren Tedford wrote: > Hey its Loren here I am working on our repeater system out here in Olney > IL we put in a pico power supply and a few other things including a > motherboard we reinstalled from the Acid cd and for some reason we are not > passing audio full duplex through the RX side of the repeater suddenly.. > Seems strange because the repeater can still capture DTMF makes me wonder > if maybe its trying to pick up a ctcss tone or some thing idk did all the > trouble shooting I could think of all night last night and still no luck > any ideas???? > > > > Loren Tedford (KC9ZHV) > Email: lorentedford at gmail.com > > http://www.lorentedford.com > http://kc9zhv.lorentedford.com > > -- Andrew Sylthe KC9ONA -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike at midnighteng.com Tue Sep 16 14:32:03 2014 From: mike at midnighteng.com (mike at midnighteng.com) Date: Tue, 16 Sep 2014 07:32:03 -0700 Subject: [App_rpt-users] =?utf-8?q?Trouble_shooting?= Message-ID: <20140916073203.71befee5dbd13c5325dd1a521b4e73ee.54e1ccc868.wbe@email06.secureserver.net> An HTML attachment was scrubbed... URL: From lorentedford at gmail.com Tue Sep 16 16:11:01 2014 From: lorentedford at gmail.com (Loren Tedford) Date: Tue, 16 Sep 2014 11:11:01 -0500 Subject: [App_rpt-users] Trouble shooting In-Reply-To: <20140916073203.71befee5dbd13c5325dd1a521b4e73ee.54e1ccc868.wbe@email06.secureserver.net> References: <20140916073203.71befee5dbd13c5325dd1a521b4e73ee.54e1ccc868.wbe@email06.secureserver.net> Message-ID: All I did was go out to repeater site and Swap USB cords and the entire thing just started working both sides VHF and UHF kinda crazy but I guess maybe some how the software and USB config just got mixed some where... Loren Tedford (KC9ZHV) Email: lorentedford at gmail.com http://kc9zhv.lorentedford.com On Tue, Sep 16, 2014 at 9:32 AM, wrote: > > Loren. > > If the software "hears" dtmf then you have a problem tx'ing the rx audio. > > Check usbradio.conf for proper mix settings and > > also check the level settings for a type error (usbradio_tune_XXX) etc. > > ...mike/kb8jnm > > -------- Original Message -------- > Subject: [App_rpt-users] Trouble shooting > From: Loren Tedford > Date: Tue, September 16, 2014 10:13 am > To: app_rpt mailing list > > Hey its Loren here I am working on our repeater system out here in Olney > IL we put in a pico power supply and a few other things including a > motherboard we reinstalled from the Acid cd and for some reason we are not > passing audio full duplex through the RX side of the repeater suddenly.. > Seems strange because the repeater can still capture DTMF makes me wonder > if maybe its trying to pick up a ctcss tone or some thing idk did all the > trouble shooting I could think of all night last night and still no luck > any ideas???? > > > > Loren Tedford (KC9ZHV) > Email: lorentedford at gmail.com > http://www.lorentedford.com > http://kc9zhv.lorentedford.com > > ------------------------------ > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at controlservers.net Tue Sep 16 16:16:55 2014 From: robert at controlservers.net (Robert) Date: Tue, 16 Sep 2014 09:16:55 -0700 Subject: [App_rpt-users] MSF to RTCM Wiring In-Reply-To: References: Message-ID: The repeater will be one of three. Each will communicate with a master server in a commercial data center where our business is located. If I have read correctly this is a hub? At any rate the CLB's will be run with RTCM as non-voted but with synchronized TX. I have the Motorola modules for this. _____ From: KJ6KO [mailto:kj6ko at innercite.com] Sent: Tuesday, September 16, 2014 8:27 AM To: Robert Subject: Re: [App_rpt-users] MSF to RTCM Wiring Hi Robert, It mainly depends on how you are going to use the system. If it is just a stand alone repeater, the RTCM is a bit of overkill, but will work fine. I have done a couple of MSF's. Assuming this is just a standalone CLB repeater (the one with the EPROM), and not a voted system, I like to keep things as simple as possible. Program the repeater to be a "Base Station", NOT a repeater!. Pull RX audio from the DISCRIMINATOR output of the MSF and make sure the RTCM is set to PLFILTER=YES and DEEPPHASIS=YES. The COR/PL Detect on a MSF is a bit trickey. You have to pull it off of a chip and use a transistor to switch it. For TX, just use the PTT and MIC Input. That is the simplest way. You can also feed raw TX audio directly into the modulator from the RTCM and have the RTCM generate the TX PL if you like, but that is a bit more complicated. I have done it, but I don't really see much of an advantage. ALl these connections are Test Points on the MSF, (Except the COR/PL) and that makes connection easy. ALSO, set the squelch on the RTCM a bit high! The RTCM's squelch circuit is a bit touchy. NOW, if you have a CXB (programmable MSF) it is all basically the same except that you can program an output of the MSF for "Valid PL Signal" and use that as the COR/PL input to the RTCM. I don't use the internal controller as the repeater. I have never been real satisfied with the audio quality of the MSF repeated audio. Best to let the RTCM do all the work and digitally filter the DISC audio rather than let the MSF do it! The RTCM will do all the controlling, tail, ID and courtesy tones for you. Also, don't forget to disable the MSF's TX Timer! Unless you are using a voting system, the URI is a MUCH cheaper source and does everything you want for just a standalone repeater, assuming you have a computer to go with it. I use the Beaglebone! The URI as it will also act as the controller, filter the DISC audio and one thing it does that the RTCM won't do is you have REMOTE audio control! That way, after you install the repeater on a hilltop, and you think the audio is a bit high or low, you can remotely bump it up or down to your hearts content! The RTCM is all manual control! Good luck and 73... Greg KJ6KO ----- Original Message ----- From: Robert To: app_rpt-users at ohnosec.org Sent: Monday, September 15, 2014 11:01 PM Subject: [App_rpt-users] MSF to RTCM Wiring I have seen so many different ways of how to wire a controller / RTCM to a MSF 5000 - is there one sure fired way to do this? Poor eyesight on my part. I hate being the new guy. __________ Information from ESET NOD32 Antivirus, version of virus signature database 10426 (20140916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com _____ _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. __________ Information from ESET NOD32 Antivirus, version of virus signature database 10426 (20140916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 10426 (20140916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From kj6qfs at gmail.com Tue Sep 16 21:37:26 2014 From: kj6qfs at gmail.com (Sam Skolfield) Date: Tue, 16 Sep 2014 14:37:26 -0700 Subject: [App_rpt-users] Looking for iMics Message-ID: Hello Group, I am looking for some Griffin iMic audio interfaces for a repeater I'm putting together for my volunteer radio group. There are several on eBay, but they are severely overpriced. If anyone as one laying around, I would really appreciate the opportunity to buy it from you at a reasonable price. Thanks for reading and 73! SS -- KJ6QFS Sam Skolfield -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at dyb.com Wed Sep 17 02:50:31 2014 From: george at dyb.com (George Csahanin) Date: Tue, 16 Sep 2014 21:50:31 -0500 Subject: [App_rpt-users] simplex node and ping-pong-ing Message-ID: <8F6045DF652248B9B7BF8AB38F1A9F24@georgecPC> I have a simplex node and it has started the ping pong thing. Did it once before and don?t remember how I resolved it. I am using simpleusb, and assuming it also accepts rxondelay. I have it set to rxondelay=150 already and it makes no difference. This radio has had no changes in three years (Custom MVP)I do not use carrier sq at all. the CG detect goes to the COS in on the controller. I also have it set to duplex=0, but that was so I can get telemetry tell me if it is linked to something. But none of that changed. The only thing to change was when I renamed echolink.conf to echolink.conf.off to drop that thing. That?s the only change. The reason why I don?t think rxondelay isn?t working is because I can ?kerchunk? for a brief moment and get a response. But according to what I have read, 150 delay should be 3000 ms. George J Csahanin W2DB 2360 Cedar Park, TX -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at dyb.com Wed Sep 17 03:54:13 2014 From: george at dyb.com (George Csahanin) Date: Tue, 16 Sep 2014 22:54:13 -0500 Subject: [App_rpt-users] ping pong-somewhat demystified and a turn for the twilight zone Message-ID: OK, found an old message from Jim that says this was fixed by adding a line to make rxondelay work, and my source is from August 31 2011, which is two years before the fix. I?m going to step into the deep end here and ask a question that may seem like a limey question, but really a cpp question. ./configure output says cpp failed sanity test, look at the log file and I see that it was looking for an include file but cannot find it. The one in question is limits.h, supposedly in linux/limits.h and I looked in /usr/include and it is there. So, please, somebody learn me here. This has been a mystery to me since I started hacking this stuff in the early 90?s and proves why I should maybe stick to broken down TV stations...but...WHERE is it looking for this include file? In limey the source all goes under /usr/src/astsrc/ then under that in /usr/src/astsrc/asterisk is where ./configure, etc is. I tried loading new source, and the August 31, 2011 is what getsrc will download. So added question, assuming I can make this work, can I load the latest source code on the limey box, I have never seen anything different. But curious. George J Csahanin W2DB Cedar Park, TX -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at controlservers.net Wed Sep 17 22:54:55 2014 From: robert at controlservers.net (Robert) Date: Wed, 17 Sep 2014 15:54:55 -0700 Subject: [App_rpt-users] MSF to RTCM Wiring In-Reply-To: <4D00361D8D8E40C7B5A5B9B77876F1AF@KJ6KO> References: <4D00361D8D8E40C7B5A5B9B77876F1AF@KJ6KO> Message-ID: <7401D4C56C4942DB93E6F447A5956402@desktop> The Moto modules ARE the GPS units :-) But I've still never done this. But are you saying that the RTCM has a built-in GPS or that one may be connected? Mark called me today and said my RTCM missed shipping but is leaving today. I looked at the #2 and #3 MSF 5000 and it says that it is a C73 CBX and not CLB's. Hmm. maybe the one on the hill is a CLB. OT: Right now I am desperately looking for someone that has a small space on Strawberry Peak in the San Bernardino Mountains. American Tower is a joke and SubCarrier hasn't replied. I wonder if anyone in the group has a suggestion? Heap's Peak is raining down on Pali Mountain with -1dBm of 99.1 on your FM freakin' dial. If I add the Angle Linear dual cavity back in it reduces it by 99dB (-67dBm). It's a sharp 1MHz window. Strawberry sees the coastal side AND the high desert side. Will $$$. Thank you for the replies. You are all appreciated. _____ From: KJ6KO [mailto:kj6ko at innercite.com] Sent: Tuesday, September 16, 2014 11:12 PM To: robert at controlservers.net Subject: Re: [App_rpt-users] MSF to RTCM Wiring Not sure what "Moto Modules" you are talking about, but the RTCM will do that with a GPS antenna. No need for any special modules. Control, repeat and sync'd TX audio can all be done by the RTCM. Freq can be done by GPS also. Maybe that's the module you are talking about? Sounds like fun! ----- Original Message ----- From: Robert To: 'KJ6KO' ; app_rpt-users at ohnosec.org Sent: Tuesday, September 16, 2014 9:16 AM Subject: RE: [App_rpt-users] MSF to RTCM Wiring The repeater will be one of three. Each will communicate with a master server in a commercial data center where our business is located. If I have read correctly this is a hub? At any rate the CLB's will be run with RTCM as non-voted but with synchronized TX. I have the Motorola modules for this. _____ From: KJ6KO [mailto:kj6ko at innercite.com] Sent: Tuesday, September 16, 2014 8:27 AM To: Robert Subject: Re: [App_rpt-users] MSF to RTCM Wiring Hi Robert, It mainly depends on how you are going to use the system. If it is just a stand alone repeater, the RTCM is a bit of overkill, but will work fine. I have done a couple of MSF's. Assuming this is just a standalone CLB repeater (the one with the EPROM), and not a voted system, I like to keep things as simple as possible. Program the repeater to be a "Base Station", NOT a repeater!. Pull RX audio from the DISCRIMINATOR output of the MSF and make sure the RTCM is set to PLFILTER=YES and DEEPPHASIS=YES. The COR/PL Detect on a MSF is a bit trickey. You have to pull it off of a chip and use a transistor to switch it. For TX, just use the PTT and MIC Input. That is the simplest way. You can also feed raw TX audio directly into the modulator from the RTCM and have the RTCM generate the TX PL if you like, but that is a bit more complicated. I have done it, but I don't really see much of an advantage. ALl these connections are Test Points on the MSF, (Except the COR/PL) and that makes connection easy. ALSO, set the squelch on the RTCM a bit high! The RTCM's squelch circuit is a bit touchy. NOW, if you have a CXB (programmable MSF) it is all basically the same except that you can program an output of the MSF for "Valid PL Signal" and use that as the COR/PL input to the RTCM. I don't use the internal controller as the repeater. I have never been real satisfied with the audio quality of the MSF repeated audio. Best to let the RTCM do all the work and digitally filter the DISC audio rather than let the MSF do it! The RTCM will do all the controlling, tail, ID and courtesy tones for you. Also, don't forget to disable the MSF's TX Timer! Unless you are using a voting system, the URI is a MUCH cheaper source and does everything you want for just a standalone repeater, assuming you have a computer to go with it. I use the Beaglebone! The URI as it will also act as the controller, filter the DISC audio and one thing it does that the RTCM won't do is you have REMOTE audio control! That way, after you install the repeater on a hilltop, and you think the audio is a bit high or low, you can remotely bump it up or down to your hearts content! The RTCM is all manual control! Good luck and 73... Greg KJ6KO ----- Original Message ----- From: Robert To: app_rpt-users at ohnosec.org Sent: Monday, September 15, 2014 11:01 PM Subject: [App_rpt-users] MSF to RTCM Wiring I have seen so many different ways of how to wire a controller / RTCM to a MSF 5000 - is there one sure fired way to do this? Poor eyesight on my part. I hate being the new guy. __________ Information from ESET NOD32 Antivirus, version of virus signature database 10426 (20140916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com _____ _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. __________ Information from ESET NOD32 Antivirus, version of virus signature database 10426 (20140916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 10426 (20140916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 10429 (20140917) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at controlservers.net Thu Sep 18 09:31:58 2014 From: robert at controlservers.net (Robert) Date: Thu, 18 Sep 2014 02:31:58 -0700 Subject: [App_rpt-users] MSF to RTCM Wiring In-Reply-To: <564CC71902DA46AFAFC27CF8A326F832@KJ6KO> References: <4D00361D8D8E40C7B5A5B9B77876F1AF@KJ6KO> <7401D4C56C4942DB93E6F447A5956402@desktop> <564CC71902DA46AFAFC27CF8A326F832@KJ6KO> Message-ID: <90A102532C5546A8AAC3068E9CEEEB4D@desktop> OT :: I absolutely agree that the tower companies should be more ham friendly and it would be great if the ARRL could help. But a large part of the issue is that there are some enterprising hams that have managed to get their own structures and either don?t have the room or they share with just their friends. I am fortunate to pay $50 for one site and only $140 for the second site. But the truly awesome sites controlled by the power houses demand $700 for a ? of a rack. I would love to learn from you the art of syncing the TX audio. I have a natural cutoff where a normally full scale signal begins to drop and what we call site #2 can naturally come in and take over. Site #3 is either going to be on the same pair, or a different pair. I?m not sure yet. Because site #1 straddles both sides of the mountain voting does not seem to be an option. The repeaters sites can see one another. A major part of our mission is as a true ECOMM repeater that can disconnect Allstar nodes if a regional emergency takes place. Because of our 6,400 foot altitude and the ability to talk and listen over the majority of So. California site selection and power level are key. I?ll read and hope to learn how to connect the Motorola GPS units that pop right into the MSF 5000?s. Thank you for sharing your advice with me. _____ From: KJ6KO [mailto:kj6ko at innercite.com] Sent: Wednesday, September 17, 2014 10:32 PM To: Robert Subject: Re: [App_rpt-users] MSF to RTCM Wiring My friend has a GPS connected to every RTCM so the TX audio is time coded and all repeaters TX at exactly the same time in sync. Not sure about how he connects the GPS to the RTCM, but I just helped him put one in a couple weeks ago! Guess I should have asked more about it, but I remember him dialing into the RTCM to see if it was GPS locked! Probably part of the reason they are so much! I was thinking about writing the ARRL to complain about the tower companies (ATC, SBA, Crown Castle etc) not being "Ham Friendly" and see if they could lean on them! Couldn't be worse than doing nothing! ----- Original Message ----- From: Robert To: app_rpt-users at ohnosec.org Sent: Wednesday, September 17, 2014 3:54 PM Subject: Re: [App_rpt-users] MSF to RTCM Wiring The Moto modules ARE the GPS units :-) But I?ve still never done this. But are you saying that the RTCM has a built-in GPS or that one may be connected? Mark called me today and said my RTCM missed shipping but is leaving today. I looked at the #2 and #3 MSF 5000 and it says that it is a C73 CBX and not CLB?s. Hmm maybe the one on the hill is a CLB. OT: Right now I am desperately looking for someone that has a small space on Strawberry Peak in the San Bernardino Mountains. American Tower is a joke and SubCarrier hasn?t replied. I wonder if anyone in the group has a suggestion? Heap?s Peak is raining down on Pali Mountain with -1dBm of 99.1 on your FM freakin? dial. If I add the Angle Linear dual cavity back in it reduces it by 99dB (-67dBm). It?s a sharp 1MHz window. Strawberry sees the coastal side AND the high desert side. Will $$$. Thank you for the replies. You are all appreciated. _____ From: KJ6KO [mailto:kj6ko at innercite.com] Sent: Tuesday, September 16, 2014 11:12 PM To: robert at controlservers.net Subject: Re: [App_rpt-users] MSF to RTCM Wiring Not sure what "Moto Modules" you are talking about, but the RTCM will do that with a GPS antenna. No need for any special modules. Control, repeat and sync'd TX audio can all be done by the RTCM. Freq can be done by GPS also. Maybe that's the module you are talking about? Sounds like fun! ----- Original Message ----- From: Robert To: 'KJ6KO' ; app_rpt-users at ohnosec.org Sent: Tuesday, September 16, 2014 9:16 AM Subject: RE: [App_rpt-users] MSF to RTCM Wiring The repeater will be one of three. Each will communicate with a master server in a commercial data center where our business is located. If I have read correctly this is a hub? At any rate the CLB?s will be run with RTCM as non-voted but with synchronized TX. I have the Motorola modules for this. _____ From: KJ6KO [mailto:kj6ko at innercite.com] Sent: Tuesday, September 16, 2014 8:27 AM To: Robert Subject: Re: [App_rpt-users] MSF to RTCM Wiring Hi Robert, It mainly depends on how you are going to use the system. If it is just a stand alone repeater, the RTCM is a bit of overkill, but will work fine. I have done a couple of MSF's. Assuming this is just a standalone CLB repeater (the one with the EPROM), and not a voted system, I like to keep things as simple as possible. Program the repeater to be a "Base Station", NOT a repeater!. Pull RX audio from the DISCRIMINATOR output of the MSF and make sure the RTCM is set to PLFILTER=YES and DEEPPHASIS=YES. The COR/PL Detect on a MSF is a bit trickey. You have to pull it off of a chip and use a transistor to switch it. For TX, just use the PTT and MIC Input. That is the simplest way. You can also feed raw TX audio directly into the modulator from the RTCM and have the RTCM generate the TX PL if you like, but that is a bit more complicated. I have done it, but I don't really see much of an advantage. ALl these connections are Test Points on the MSF, (Except the COR/PL) and that makes connection easy. ALSO, set the squelch on the RTCM a bit high! The RTCM's squelch circuit is a bit touchy. NOW, if you have a CXB (programmable MSF) it is all basically the same except that you can program an output of the MSF for "Valid PL Signal" and use that as the COR/PL input to the RTCM. I don't use the internal controller as the repeater. I have never been real satisfied with the audio quality of the MSF repeated audio. Best to let the RTCM do all the work and digitally filter the DISC audio rather than let the MSF do it! The RTCM will do all the controlling, tail, ID and courtesy tones for you. Also, don't forget to disable the MSF's TX Timer! Unless you are using a voting system, the URI is a MUCH cheaper source and does everything you want for just a standalone repeater, assuming you have a computer to go with it. I use the Beaglebone! The URI as it will also act as the controller, filter the DISC audio and one thing it does that the RTCM won't do is you have REMOTE audio control! That way, after you install the repeater on a hilltop, and you think the audio is a bit high or low, you can remotely bump it up or down to your hearts content! The RTCM is all manual control! Good luck and 73... Greg KJ6KO ----- Original Message ----- From: Robert To: app_rpt-users at ohnosec.org Sent: Monday, September 15, 2014 11:01 PM Subject: [App_rpt-users] MSF to RTCM Wiring I have seen so many different ways of how to wire a controller / RTCM to a MSF 5000 ? is there one sure fired way to do this? Poor eyesight on my part. I hate being the new guy __________ Information from ESET NOD32 Antivirus, version of virus signature database 10426 (20140916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com _____ _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. __________ Information from ESET NOD32 Antivirus, version of virus signature database 10426 (20140916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 10426 (20140916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 10429 (20140917) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 10434 (20140917) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com _____ _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. __________ Information from ESET NOD32 Antivirus, version of virus signature database 10434 (20140917) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 10435 (20140918) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From wb5nfc at gmail.com Thu Sep 18 21:04:47 2014 From: wb5nfc at gmail.com (John) Date: Thu, 18 Sep 2014 16:04:47 -0500 Subject: [App_rpt-users] Proxy Server and Echolink Message-ID: Node 2186 is set up with a proxy and seems to be working perfectly for incoming and outgoing Allstar calls. However, I'm having trouble with Echolink. The station list appears to be downloading, my node shows up in the Echolink active node list, but I have trouble connecting to other Echolink nodes including the Echo Reflector. Sometimes when I do manage to connect, I will be disconnected within a few minutes. Should Echolink work normally with a proxy server or have I perhaps fat-fingered something in the config files? Troubleshooting suggestions appreciated. John -------------- next part -------------- An HTML attachment was scrubbed... URL: From kp4tr.ramon at gmail.com Fri Sep 19 04:26:24 2014 From: kp4tr.ramon at gmail.com ((KP4TR)Ramon Gonzalez) Date: Fri, 19 Sep 2014 00:26:24 -0400 Subject: [App_rpt-users] URI GPIO manipulation In-Reply-To: <20140907.162049.21786.0@webmail07.dca.untd.com> References: <20140907.162049.21786.0@webmail07.dca.untd.com> Message-ID: <541BB070.10100@gmail.com> I have. And I wrote a page documenting how I did it: http://kp4tr.org/?page_id=412 On 9/7/2014 4:20 PM, zeppelin.1 at netzero.com wrote: > Greetings; a technical question for anyone interested in answering. > Incorporated k0kn txfan script on node 29103 successfully controlling a fan via PP4. > Has anyone attempted controlling a fan via URI gpio4 with success? > > Anton/ kc2rqr > Node 29103 > ____________________________________________________________ > The #1 Worst Carb Ever? > Click to Learn #1 Carb that Kills Your Blood Sugar (Don't Eat This!) > http://thirdpartyoffers.netzero.net/TGL3231/540cbe459554b3e45237bst02duc > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > From mike.lussier at gmail.com Sat Sep 20 00:33:59 2014 From: mike.lussier at gmail.com (Mike Lussier) Date: Fri, 19 Sep 2014 20:33:59 -0400 Subject: [App_rpt-users] Time question Message-ID: I have both of my systems transmitting my call and the time every hour. Its states it in 12 hour fomat. How can I get it to do it in24hour format ? The clock on the Beagle is set for 24 hour format. Thank you Mike AE4ML -- *"We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan* -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike at midnighteng.com Sat Sep 20 01:53:49 2014 From: mike at midnighteng.com (mike at midnighteng.com) Date: Fri, 19 Sep 2014 18:53:49 -0700 Subject: [App_rpt-users] =?utf-8?q?Time_question?= Message-ID: <20140919185349.71befee5dbd13c5325dd1a521b4e73ee.3473c1ec5b.wbe@email06.secureserver.net> An HTML attachment was scrubbed... URL: From doug at crompton.com Sat Sep 20 04:18:00 2014 From: doug at crompton.com (Doug Crompton) Date: Sat, 20 Sep 2014 00:18:00 -0400 Subject: [App_rpt-users] Time question In-Reply-To: References: Message-ID: Mike, The short answer is you can't. The script is setup to say 12 hour format with AM/PM. It could be changed but I have no desire or time to do that right now. If someone else wants to tackle it I would be glad to include it in the distribution. /etc/asterisk/saytime.pl is a Perl script I wrote that says the time outside of app_rpt so you can alter that anyway you like as well as set the volume. I would be glad to assist anyone if they want to modify that code for say a say24time.pl script that could be called. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Fri, 19 Sep 2014 20:33:59 -0400 From: mike.lussier at gmail.com To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Time question I have both of my systems transmitting my call and the time every hour.Its states it in 12 hour fomat. How can I get it to do it in24hour format ? The clock on the Beagle is set for 24 hour format. Thank you Mike AE4ML -- "We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sat Sep 20 04:22:29 2014 From: doug at crompton.com (Doug Crompton) Date: Sat, 20 Sep 2014 00:22:29 -0400 Subject: [App_rpt-users] Time question In-Reply-To: References: Message-ID: /etc/localtime is a symbolic link to the timezone and maybe I am reading you wrong do you want zulu time to read out or do you want to read out the time in 24 hour format. That is two different things. 24 hour format or military style time is 1000, 1100, 1200, 1300 etc. No AM/PM That is what I thought you meant. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Fri, 19 Sep 2014 20:33:59 -0400 From: mike.lussier at gmail.com To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Time question I have both of my systems transmitting my call and the time every hour.Its states it in 12 hour fomat. How can I get it to do it in24hour format ? The clock on the Beagle is set for 24 hour format. Thank you Mike AE4ML -- "We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sat Sep 20 05:30:19 2014 From: doug at crompton.com (Doug Crompton) Date: Sat, 20 Sep 2014 01:30:19 -0400 Subject: [App_rpt-users] Time question In-Reply-To: <7AF54F6CE6B340A68D45B04EA154330C@ThePykesHP> References: , <7AF54F6CE6B340A68D45B04EA154330C@ThePykesHP> Message-ID: yes. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kk6ecm at gmail.com To: doug at crompton.com Subject: RE: [App_rpt-users] Time question Date: Fri, 19 Sep 2014 21:49:13 -0700 forgive me for a correction, but I believe you meant to say /etc/asterisk/local/saytime.pl Thanks, Bob kk6ecm From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Doug Crompton Sent: Friday, September 19, 2014 9:18 PM To: Mike Lussier Cc: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Time question Mike, The short answer is you can't. The script is setup to say 12 hour format with AM/PM. It could be changed but I have no desire or time to do that right now. If someone else wants to tackle it I would be glad to include it in the distribution. /etc/asterisk/saytime.pl is a Perl script I wrote that says the time outside of app_rpt so you can alter that anyway you like as well as set the volume. I would be glad to assist anyone if they want to modify that code for say a say24time.pl script that could be called. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Fri, 19 Sep 2014 20:33:59 -0400 From: mike.lussier at gmail.com To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Time question I have both of my systems transmitting my call and the time every hour. Its states it in 12 hour fomat. How can I get it to do it in24hour format ? The clock on the Beagle is set for 24 hour format. Thank you Mike AE4ML -- "We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike.lussier at gmail.com Sat Sep 20 10:55:52 2014 From: mike.lussier at gmail.com (Michael Lussier) Date: Sat, 20 Sep 2014 06:55:52 -0400 Subject: [App_rpt-users] Time question In-Reply-To: References: Message-ID: <5B114A04-CD28-488B-BCC9-AEB3027641C5@gmail.com> Yes, 24 hour format 1300 1400 1500 Sent from an iPhone 5 > On Sep 20, 2014, at 00:22, Doug Crompton wrote: > > /etc/localtime is a symbolic link to the timezone and maybe I am reading you wrong do you want zulu time to read out or do you want to read out the time in 24 hour format. That is two different things. > > 24 hour format or military style time is 1000, 1100, 1200, 1300 etc. No AM/PM That is what I thought you meant. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > Date: Fri, 19 Sep 2014 20:33:59 -0400 > From: mike.lussier at gmail.com > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Time question > > I have both of my systems transmitting my call and the time every hour. > Its states it in 12 hour fomat. How can I get it to do it in24hour format ? The clock on the Beagle is set for 24 hour format. > > Thank you > > Mike AE4ML > -- > "We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan > > > > _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ars.w5omr at gmail.com Sat Sep 20 14:14:28 2014 From: ars.w5omr at gmail.com (Geoff) Date: Sat, 20 Sep 2014 09:14:28 -0500 Subject: [App_rpt-users] Time question In-Reply-To: <20140919185349.71befee5dbd13c5325dd1a521b4e73ee.3473c1ec5b.wbe@email06.secureserver.net> References: <20140919185349.71befee5dbd13c5325dd1a521b4e73ee.3473c1ec5b.wbe@email06.secureserver.net> Message-ID: <541D8BC4.2000702@gmail.com> On 09/19/2014 08:53 PM, mike at midnighteng.com wrote: > > > Edit /etc/localtime > > You can set all the data on time from there. > You can google linux localtime for more info > > > ...mike/kb8jnm But, that's not what he asked. > I have both of my systems transmitting my call and the time every hour. > Its states it in 12 hour fomat. How can I get it to do it in24hour > format ? > The clock on the Beagle is set for 24 hour format. His problem is not setting the time, or getting it announced. What he wants is for Allison to spit out the time, on the our, in 24-hour format. (ie: 2pm becomes; "Good afternoon. The time is fourteen hundred hours") -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sat Sep 20 15:51:54 2014 From: doug at crompton.com (Doug Crompton) Date: Sat, 20 Sep 2014 11:51:54 -0400 Subject: [App_rpt-users] Time question In-Reply-To: References: Message-ID: OK, It turns out it was easier than I thought. Here is a test script. Let me know if it works right for you. I am sure this may be some tweaks. Once OK I will include it in the next distribution. Just call it with say24time.pl instead of saytime.pl - CHANGE THE NODE in the file!!! 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Fri, 19 Sep 2014 20:33:59 -0400 From: mike.lussier at gmail.com To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Time question I have both of my systems transmitting my call and the time every hour.Its states it in 12 hour fomat. How can I get it to do it in24hour format ? The clock on the Beagle is set for 24 hour format. Thank you Mike AE4ML -- "We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: say24time.pl URL: From mike at midnighteng.com Sat Sep 20 15:54:03 2014 From: mike at midnighteng.com (mike at midnighteng.com) Date: Sat, 20 Sep 2014 08:54:03 -0700 Subject: [App_rpt-users] =?utf-8?q?Time_question?= Message-ID: <20140920085403.71befee5dbd13c5325dd1a521b4e73ee.3b1de45c8f.wbe@email06.secureserver.net> An HTML attachment was scrubbed... URL: From srice3 at cfl.rr.com Sat Sep 20 16:20:59 2014 From: srice3 at cfl.rr.com (The Rices) Date: Sat, 20 Sep 2014 12:20:59 -0400 Subject: [App_rpt-users] File question In-Reply-To: <20140920085403.71befee5dbd13c5325dd1a521b4e73ee.3b1de45c8f.wbe@email06.secureserver.net> References: <20140920085403.71befee5dbd13c5325dd1a521b4e73ee.3b1de45c8f.wbe@email06.secureserver.net> Message-ID: What file is holding my Server node number, server name and node password in Asterisk? I need to edit the information since I did not enter it correctly when I installed the new os. Thanks Steve N4YZA -------------- next part -------------- An HTML attachment was scrubbed... URL: From kj6ko at innercite.com Sat Sep 20 16:56:59 2014 From: kj6ko at innercite.com (KJ6KO) Date: Sat, 20 Sep 2014 09:56:59 -0700 Subject: [App_rpt-users] Node change from DHCP to Static Message-ID: <0315811BFCD44B05968AB2824C7F9986@KJ6KO> I'm sure this is elementary for most of you, but I am an amateur at Linux. I have a node I am moving and it will require a static IP at its new location. I understand the basics of the ip, Netmask, Broadcast,DNS etc, but just unfamiliar with how to change it and what files need to be changed? What files on both the Network device (ETH0) and the Asterisk side of things. System is a standard computer and URI. Thanks...Greg KJ6KO __________ Information from ESET NOD32 Antivirus, version of virus signature database 10444 (20140919) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sat Sep 20 17:03:38 2014 From: doug at crompton.com (Doug Crompton) Date: Sat, 20 Sep 2014 13:03:38 -0400 Subject: [App_rpt-users] Time question In-Reply-To: References: , Message-ID: Slight correction. The 0 minute said oclock instead of hundred - 13 hunderd, 14 hundred etc.. Use this version for tests. 73 Doug WA3DSP http://www.crompton.com/hamradio From: doug at crompton.com To: mike.lussier at gmail.com Date: Sat, 20 Sep 2014 11:51:54 -0400 CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Time question OK, It turns out it was easier than I thought. Here is a test script. Let me know if it works right for you. I am sure this may be some tweaks. Once OK I will include it in the next distribution. Just call it with say24time.pl instead of saytime.pl - CHANGE THE NODE in the file!!! 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Fri, 19 Sep 2014 20:33:59 -0400 From: mike.lussier at gmail.com To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Time question I have both of my systems transmitting my call and the time every hour.Its states it in 12 hour fomat. How can I get it to do it in24hour format ? The clock on the Beagle is set for 24 hour format. Thank you Mike AE4ML -- "We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: say24time.pl URL: From doug at crompton.com Sat Sep 20 17:09:34 2014 From: doug at crompton.com (Doug Crompton) Date: Sat, 20 Sep 2014 13:09:34 -0400 Subject: [App_rpt-users] File question In-Reply-To: References: <20140920085403.71befee5dbd13c5325dd1a521b4e73ee.3b1de45c8f.wbe@email06.secureserver.net>, Message-ID: The node number is in rpt.conf, iax.conf, and extensions.conf - you would have to wholesale change it in all locations. The server name is not used locally but is assigned by you at allstarlink.org - you can change it there it desired. The node password which you get at allstarlink.org under your node information for the server you assigned is used in the registration statement in iax.conf. You specify your node number and password (6 digit number) there. register => xxxxx:yyyyyy at register.allstarlink.org Where xxxxx = node number and yyyyyy=password Do not confuse your linux password, the one you enter when you log into your local system and the node password. They are two different things. 73 Doug WA3DSP http://www.crompton.com/hamradio From: srice3 at cfl.rr.com To: app_rpt-users at ohnosec.org Date: Sat, 20 Sep 2014 12:20:59 -0400 Subject: [App_rpt-users] File question What file is holding my Server node number, server name and node password in Asterisk? I need to edit the information since I did not enter it correctly when I installed the new os. Thanks Steve N4YZA _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From n9udo at yellowthunder.org Sat Sep 20 17:24:15 2014 From: n9udo at yellowthunder.org (Steve Schulze) Date: Sat, 20 Sep 2014 12:24:15 -0500 Subject: [App_rpt-users] URI Problem Message-ID: <541DB83F.5080801@yellowthunder.org> Has anyone run across a URI that goes 'offline' every 3 to 4 days? A simple warm boot command or astres.sh will bring it back on line as well as unplugging the URI and plugging back in. There is no indication that it's not working to the online user. You can connect to the box but no audio (either direction) or PTT passes to the repeater until you reset it. I have installed ferrites on each end of the USB cable and on the control cable on the URI side but no change. Any thoughts? Thanks in advance. -- Amateur Radio - The Original Social Media Steve Schulze - Radio Amateur, General Class - N9UDO Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 Treasurer, Badgerland Amateur Television Society - KB9SFS http://yellowthunder.org/dstar.html From doug at crompton.com Sat Sep 20 17:54:02 2014 From: doug at crompton.com (Doug Crompton) Date: Sat, 20 Sep 2014 13:54:02 -0400 Subject: [App_rpt-users] URI Problem In-Reply-To: <541DB83F.5080801@yellowthunder.org> References: <541DB83F.5080801@yellowthunder.org> Message-ID: Steve, What computer are you using? PC or Beagle Bone Black? etc. Also usbradio or simpleusb? This is a common problem on the URI with external EMI and power spikes. The problem can be fixed. You need to ground everything and eliminate EMI as much as possible. The other issue is the USB not resetting when it has this problem. Most of the PC's will but probably not all. The next version of the BBB code coming out soon will reset fine. If you are using simpleusb there is a bug in the code that precludes a reset upon USB interruption. This fix will also be in the BBB code that is coming soon. If you want to fix a PC simplesusb installation here is the link - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/simpleusb-howto.pdf See how to do the patch at the end of the pdf. You should be able to pull the USB cable from the URI while in use (green light flashing normally) and reinstall the USB and it should start flashing again. If not then your system will not recover from USB EMI hits properly. It is always a good idea to try and fix or reduce the problem because in severe cases it would be resetting all the time. It sounds like you case is less severe. 73 Doug WA3DSP http://www.crompton.com/hamradio > Date: Sat, 20 Sep 2014 12:24:15 -0500 > From: n9udo at yellowthunder.org > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] URI Problem > > Has anyone run across a URI that goes 'offline' every 3 to 4 days? A > simple warm boot command or astres.sh will bring it back on line as well > as unplugging the URI and plugging back in. > > There is no indication that it's not working to the online user. You can > connect to the box but no audio (either direction) or PTT passes to the > repeater until you reset it. > > I have installed ferrites on each end of the USB cable and on the > control cable on the URI side but no change. > > > Any thoughts? > > > Thanks in advance. > > -- > Amateur Radio - The Original Social Media > > Steve Schulze - Radio Amateur, General Class - N9UDO > Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ > Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 > Treasurer, Badgerland Amateur Television Society - KB9SFS > > http://yellowthunder.org/dstar.html > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kk6ecm at gmail.com Sun Sep 21 05:13:23 2014 From: kk6ecm at gmail.com (Bob) Date: Sat, 20 Sep 2014 22:13:23 -0700 Subject: [App_rpt-users] Node change from DHCP to Static In-Reply-To: <0315811BFCD44B05968AB2824C7F9986@KJ6KO> References: <0315811BFCD44B05968AB2824C7F9986@KJ6KO> Message-ID: <647823A57ED543B1A917D16E9D68C24F@ThePykesHP> You may want to use "setup"... enter on the Linux command line. i.e. root at server:/# setup Bob kk6ecm _____ From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of KJ6KO Sent: Saturday, September 20, 2014 9:57 AM To: App_rpt-users at ohnosec.org Subject: [App_rpt-users] Node change from DHCP to Static I'm sure this is elementary for most of you, but I am an amateur at Linux. I have a node I am moving and it will require a static IP at its new location. I understand the basics of the ip, Netmask, Broadcast,DNS etc, but just unfamiliar with how to change it and what files need to be changed? What files on both the Network device (ETH0) and the Asterisk side of things. System is a standard computer and URI. Thanks...Greg KJ6KO __________ Information from ESET NOD32 Antivirus, version of virus signature database 10444 (20140919) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From n9udo at yellowthunder.org Sun Sep 21 11:56:43 2014 From: n9udo at yellowthunder.org (Steve Schulze) Date: Sun, 21 Sep 2014 06:56:43 -0500 Subject: [App_rpt-users] URI Problem In-Reply-To: References: <541DB83F.5080801@yellowthunder.org> Message-ID: <541EBCFB.8010409@yellowthunder.org> Doug. I'm running a PC with usbradio. This is something that just recently showed up. The system has been running fine at it's current location for over a year. The IBM PC that I'm using has a (heavy) metal chassis and I should be able to get a good ground on it back to the building's halo. Unplugging the URI and plugging back in does reset it. When it's not working, the green LED is steady. Thanks! Amateur Radio - The Original Social Media Steve Schulze - Radio Amateur, General Class - N9UDO Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 Treasurer, Badgerland Amateur Television Society - KB9SFS http://yellowthunder.org/dstar.html On 9/20/2014 12:54 PM, Doug Crompton wrote: > Steve, > > What computer are you using? PC or Beagle Bone Black? etc. Also > usbradio or simpleusb? > > This is a common problem on the URI with external EMI and power spikes. > > The problem can be fixed. You need to ground everything and eliminate > EMI as much as possible. > > The other issue is the USB not resetting when it has this problem. > Most of the PC's will but probably not all. The next version of the > BBB code coming out soon will reset fine. > > If you are using simpleusb there is a bug in the code that precludes a > reset upon USB interruption. This fix will also be in the BBB code > that is coming soon. If you want to fix a PC simplesusb installation > here is the link - > > http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/simpleusb-howto.pdf > > See how to do the patch at the end of the pdf. > > You should be able to pull the USB cable from the URI while in use > (green light flashing normally) and reinstall the USB and it should > start flashing again. If not then your system will not recover from > USB EMI hits properly. > > It is always a good idea to try and fix or reduce the problem because > in severe cases it would be resetting all the time. It sounds like you > case is less severe. > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > > Date: Sat, 20 Sep 2014 12:24:15 -0500 > > From: n9udo at yellowthunder.org > > To: app_rpt-users at ohnosec.org > > Subject: [App_rpt-users] URI Problem > > > > Has anyone run across a URI that goes 'offline' every 3 to 4 days? A > > simple warm boot command or astres.sh will bring it back on line as > well > > as unplugging the URI and plugging back in. > > > > There is no indication that it's not working to the online user. You > can > > connect to the box but no audio (either direction) or PTT passes to the > > repeater until you reset it. > > > > I have installed ferrites on each end of the USB cable and on the > > control cable on the URI side but no change. > > > > > > Any thoughts? > > > > > > Thanks in advance. > > > > -- > > Amateur Radio - The Original Social Media > > > > Steve Schulze - Radio Amateur, General Class - N9UDO > > Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ > > Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 > > Treasurer, Badgerland Amateur Television Society - KB9SFS > > > > http://yellowthunder.org/dstar.html > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at 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. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sun Sep 21 13:22:46 2014 From: doug at crompton.com (Doug Crompton) Date: Sun, 21 Sep 2014 09:22:46 -0400 Subject: [App_rpt-users] URI Problem In-Reply-To: <541EBCFB.8010409@yellowthunder.org> References: <541DB83F.5080801@yellowthunder.org> , <541EBCFB.8010409@yellowthunder.org> Message-ID: Steve, It sounds like it might be a SW issue in your PC. From what you say outside influences should reset the URI. Take a good look at your logs on the PC both system and Asterisk and see if you can determine anything. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Sun, 21 Sep 2014 06:56:43 -0500 From: n9udo at yellowthunder.org To: doug at crompton.com CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] URI Problem Doug. I'm running a PC with usbradio. This is something that just recently showed up. The system has been running fine at it's current location for over a year. The IBM PC that I'm using has a (heavy) metal chassis and I should be able to get a good ground on it back to the building's halo. Unplugging the URI and plugging back in does reset it. When it's not working, the green LED is steady. Thanks! Amateur Radio - The Original Social Media Steve Schulze - Radio Amateur, General Class - N9UDO Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 Treasurer, Badgerland Amateur Television Society - KB9SFS http://yellowthunder.org/dstar.html On 9/20/2014 12:54 PM, Doug Crompton wrote: Steve, What computer are you using? PC or Beagle Bone Black? etc. Also usbradio or simpleusb? This is a common problem on the URI with external EMI and power spikes. The problem can be fixed. You need to ground everything and eliminate EMI as much as possible. The other issue is the USB not resetting when it has this problem. Most of the PC's will but probably not all. The next version of the BBB code coming out soon will reset fine. If you are using simpleusb there is a bug in the code that precludes a reset upon USB interruption. This fix will also be in the BBB code that is coming soon. If you want to fix a PC simplesusb installation here is the link - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/simpleusb-howto.pdf See how to do the patch at the end of the pdf. You should be able to pull the USB cable from the URI while in use (green light flashing normally) and reinstall the USB and it should start flashing again. If not then your system will not recover from USB EMI hits properly. It is always a good idea to try and fix or reduce the problem because in severe cases it would be resetting all the time. It sounds like you case is less severe. 73 Doug WA3DSP http://www.crompton.com/hamradio > Date: Sat, 20 Sep 2014 12:24:15 -0500 > From: n9udo at yellowthunder.org > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] URI Problem > > Has anyone run across a URI that goes 'offline' every 3 to 4 days? A > simple warm boot command or astres.sh will bring it back on line as well > as unplugging the URI and plugging back in. > > There is no indication that it's not working to the online user. You can > connect to the box but no audio (either direction) or PTT passes to the > repeater until you reset it. > > I have installed ferrites on each end of the USB cable and on the > control cable on the URI side but no change. > > > Any thoughts? > > > Thanks in advance. > > -- > Amateur Radio - The Original Social Media > > Steve Schulze - Radio Amateur, General Class - N9UDO > Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ > Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 > Treasurer, Badgerland Amateur Television Society - KB9SFS > > http://yellowthunder.org/dstar.html > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sun Sep 21 13:41:41 2014 From: doug at crompton.com (Doug Crompton) Date: Sun, 21 Sep 2014 09:41:41 -0400 Subject: [App_rpt-users] URI Problem In-Reply-To: References: <541DB83F.5080801@yellowthunder.org>, , , <541EBCFB.8010409@yellowthunder.org>, Message-ID: I meant to say SW and/or HW problem. Have you tried a different USB port on the PC. Do you have another URI to try? I doubt it is the URI but you never know. 73 Doug WA3DSP http://www.crompton.com/hamradio From: doug at crompton.com To: n9udo at yellowthunder.org Date: Sun, 21 Sep 2014 09:22:46 -0400 CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] URI Problem Steve, It sounds like it might be a SW issue in your PC. From what you say outside influences should reset the URI. Take a good look at your logs on the PC both system and Asterisk and see if you can determine anything. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Sun, 21 Sep 2014 06:56:43 -0500 From: n9udo at yellowthunder.org To: doug at crompton.com CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] URI Problem Doug. I'm running a PC with usbradio. This is something that just recently showed up. The system has been running fine at it's current location for over a year. The IBM PC that I'm using has a (heavy) metal chassis and I should be able to get a good ground on it back to the building's halo. Unplugging the URI and plugging back in does reset it. When it's not working, the green LED is steady. Thanks! Amateur Radio - The Original Social Media Steve Schulze - Radio Amateur, General Class - N9UDO Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 Treasurer, Badgerland Amateur Television Society - KB9SFS http://yellowthunder.org/dstar.html On 9/20/2014 12:54 PM, Doug Crompton wrote: Steve, What computer are you using? PC or Beagle Bone Black? etc. Also usbradio or simpleusb? This is a common problem on the URI with external EMI and power spikes. The problem can be fixed. You need to ground everything and eliminate EMI as much as possible. The other issue is the USB not resetting when it has this problem. Most of the PC's will but probably not all. The next version of the BBB code coming out soon will reset fine. If you are using simpleusb there is a bug in the code that precludes a reset upon USB interruption. This fix will also be in the BBB code that is coming soon. If you want to fix a PC simplesusb installation here is the link - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/simpleusb-howto.pdf See how to do the patch at the end of the pdf. You should be able to pull the USB cable from the URI while in use (green light flashing normally) and reinstall the USB and it should start flashing again. If not then your system will not recover from USB EMI hits properly. It is always a good idea to try and fix or reduce the problem because in severe cases it would be resetting all the time. It sounds like you case is less severe. 73 Doug WA3DSP http://www.crompton.com/hamradio > Date: Sat, 20 Sep 2014 12:24:15 -0500 > From: n9udo at yellowthunder.org > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] URI Problem > > Has anyone run across a URI that goes 'offline' every 3 to 4 days? A > simple warm boot command or astres.sh will bring it back on line as well > as unplugging the URI and plugging back in. > > There is no indication that it's not working to the online user. You can > connect to the box but no audio (either direction) or PTT passes to the > repeater until you reset it. > > I have installed ferrites on each end of the USB cable and on the > control cable on the URI side but no change. > > > Any thoughts? > > > Thanks in advance. > > -- > Amateur Radio - The Original Social Media > > Steve Schulze - Radio Amateur, General Class - N9UDO > Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ > Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 > Treasurer, Badgerland Amateur Television Society - KB9SFS > > http://yellowthunder.org/dstar.html > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zeppelin.1 at netzero.com Sun Sep 21 16:07:36 2014 From: zeppelin.1 at netzero.com (zeppelin.1 at netzero.com) Date: Sun, 21 Sep 2014 16:07:36 GMT Subject: [App_rpt-users] ReURI Problem Message-ID: <20140921.120736.29488.0@webmail04.dca.untd.com> Hello Steve, Floating ground maybe the culprit; common ground node 29103 and URI rs-232 ground pin. 73 Anton/kc2rqr Node 29103 ---------- Original Message ---------- From: app_rpt-users-request at ohnosec.org To: app_rpt-users at ohnosec.org Subject: App_rpt-users Digest, Vol 67, Issue 59 Date: Sun, 21 Sep 2014 07:56:44 -0400 Send App_rpt-users mailing list submissions to app_rpt-users at ohnosec.org To subscribe or unsubscribe via the World Wide Web, visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users or, via email, send a message with subject or body 'help' to app_rpt-users-request at ohnosec.org You can reach the person managing the list at app_rpt-users-owner at ohnosec.org When replying, please edit your Subject line so it is more specific than "Re: Contents of App_rpt-users digest..." Today's Topics: 1. URI Problem (Steve Schulze) 2. Re: URI Problem (Doug Crompton) 3. Re: Node change from DHCP to Static (Bob) 4. Re: URI Problem (Steve Schulze) ---------------------------------------------------------------------- Message: 1 Date: Sat, 20 Sep 2014 12:24:15 -0500 From: Steve Schulze To: "app_rpt-users at ohnosec.org" Subject: [App_rpt-users] URI Problem Message-ID: <541DB83F.5080801 at yellowthunder.org> Content-Type: text/plain; charset=utf-8; format=flowed Has anyone run across a URI that goes 'offline' every 3 to 4 days? A simple warm boot command or astres.sh will bring it back on line as well as unplugging the URI and plugging back in. There is no indication that it's not working to the online user. You can connect to the box but no audio (either direction) or PTT passes to the repeater until you reset it. I have installed ferrites on each end of the USB cable and on the control cable on the URI side but no change. Any thoughts? Thanks in advance. -- Amateur Radio - The Original Social Media Steve Schulze - Radio Amateur, General Class - N9UDO Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 Treasurer, Badgerland Amateur Television Society - KB9SFS http://yellowthunder.org/dstar.html ------------------------------ Message: 2 Date: Sat, 20 Sep 2014 13:54:02 -0400 From: Doug Crompton To: Steve Schulze Cc: "app_rpt-users at ohnosec.org" Subject: Re: [App_rpt-users] URI Problem Message-ID: Content-Type: text/plain; charset="iso-8859-1" Steve, What computer are you using? PC or Beagle Bone Black? etc. Also usbradio or simpleusb? This is a common problem on the URI with external EMI and power spikes. The problem can be fixed. You need to ground everything and eliminate EMI as much as possible. The other issue is the USB not resetting when it has this problem. Most of the PC's will but probably not all. The next version of the BBB code coming out soon will reset fine. If you are using simpleusb there is a bug in the code that precludes a reset upon USB interruption. This fix will also be in the BBB code that is coming soon. If you want to fix a PC simplesusb installation here is the link - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/simpleusb-howto.pdf See how to do the patch at the end of the pdf. You should be able to pull the USB cable from the URI while in use (green light flashing normally) and reinstall the USB and it should start flashing again. If not then your system will not recover from USB EMI hits properly. It is always a good idea to try and fix or reduce the problem because in severe cases it would be resetting all the time. It sounds like you case is less severe. 73 Doug WA3DSP http://www.crompton.com/hamradio > Date: Sat, 20 Sep 2014 12:24:15 -0500 > From: n9udo at yellowthunder.org > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] URI Problem > > Has anyone run across a URI that goes 'offline' every 3 to 4 days? A > simple warm boot command or astres.sh will bring it back on line as well > as unplugging the URI and plugging back in. > > There is no indication that it's not working to the online user. You can > connect to the box but no audio (either direction) or PTT passes to the > repeater until you reset it. > > I have installed ferrites on each end of the USB cable and on the > control cable on the URI side but no change. > > > Any thoughts? > > > Thanks in advance. > > -- > Amateur Radio - The Original Social Media > > Steve Schulze - Radio Amateur, General Class - N9UDO > Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ > Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 > Treasurer, Badgerland Amateur Television Society - KB9SFS > > http://yellowthunder.org/dstar.html > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Sat, 20 Sep 2014 22:13:23 -0700 From: "Bob" To: "'KJ6KO'" , Subject: Re: [App_rpt-users] Node change from DHCP to Static Message-ID: <647823A57ED543B1A917D16E9D68C24F at ThePykesHP> Content-Type: text/plain; charset="us-ascii" You may want to use "setup"... enter on the Linux command line. i.e. root at server:/# setup Bob kk6ecm _____ From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of KJ6KO Sent: Saturday, September 20, 2014 9:57 AM To: App_rpt-users at ohnosec.org Subject: [App_rpt-users] Node change from DHCP to Static I'm sure this is elementary for most of you, but I am an amateur at Linux. I have a node I am moving and it will require a static IP at its new location. I understand the basics of the ip, Netmask, Broadcast,DNS etc, but just unfamiliar with how to change it and what files need to be changed? What files on both the Network device (ETH0) and the Asterisk side of things. System is a standard computer and URI. Thanks...Greg KJ6KO __________ Information from ESET NOD32 Antivirus, version of virus signature database 10444 (20140919) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 4 Date: Sun, 21 Sep 2014 06:56:43 -0500 From: Steve Schulze To: Doug Crompton Cc: "app_rpt-users at ohnosec.org" Subject: Re: [App_rpt-users] URI Problem Message-ID: <541EBCFB.8010409 at yellowthunder.org> Content-Type: text/plain; charset="windows-1252"; Format="flowed" Doug. I'm running a PC with usbradio. This is something that just recently showed up. The system has been running fine at it's current location for over a year. The IBM PC that I'm using has a (heavy) metal chassis and I should be able to get a good ground on it back to the building's halo. Unplugging the URI and plugging back in does reset it. When it's not working, the green LED is steady. Thanks! Amateur Radio - The Original Social Media Steve Schulze - Radio Amateur, General Class - N9UDO Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 Treasurer, Badgerland Amateur Television Society - KB9SFS http://yellowthunder.org/dstar.html On 9/20/2014 12:54 PM, Doug Crompton wrote: > Steve, > > What computer are you using? PC or Beagle Bone Black? etc. Also > usbradio or simpleusb? > > This is a common problem on the URI with external EMI and power spikes. > > The problem can be fixed. You need to ground everything and eliminate > EMI as much as possible. > > The other issue is the USB not resetting when it has this problem. > Most of the PC's will but probably not all. The next version of the > BBB code coming out soon will reset fine. > > If you are using simpleusb there is a bug in the code that precludes a > reset upon USB interruption. This fix will also be in the BBB code > that is coming soon. If you want to fix a PC simplesusb installation > here is the link - > > http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/simpleusb-howto.pdf > > See how to do the patch at the end of the pdf. > > You should be able to pull the USB cable from the URI while in use > (green light flashing normally) and reinstall the USB and it should > start flashing again. If not then your system will not recover from > USB EMI hits properly. > > It is always a good idea to try and fix or reduce the problem because > in severe cases it would be resetting all the time. It sounds like you > case is less severe. > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > > Date: Sat, 20 Sep 2014 12:24:15 -0500 > > From: n9udo at yellowthunder.org > > To: app_rpt-users at ohnosec.org > > Subject: [App_rpt-users] URI Problem > > > > Has anyone run across a URI that goes 'offline' every 3 to 4 days? A > > simple warm boot command or astres.sh will bring it back on line as > well > > as unplugging the URI and plugging back in. > > > > There is no indication that it's not working to the online user. You > can > > connect to the box but no audio (either direction) or PTT passes to the > > repeater until you reset it. > > > > I have installed ferrites on each end of the USB cable and on the > > control cable on the URI side but no change. > > > > > > Any thoughts? > > > > > > Thanks in advance. > > > > -- > > Amateur Radio - The Original Social Media > > > > Steve Schulze - Radio Amateur, General Class - N9UDO > > Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ > > Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 > > Treasurer, Badgerland Amateur Television Society - KB9SFS > > > > http://yellowthunder.org/dstar.html > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at 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. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ _______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users End of App_rpt-users Digest, Vol 67, Issue 59 ********************************************* From petem001 at hotmail.com Sun Sep 21 16:45:26 2014 From: petem001 at hotmail.com (pete M) Date: Sun, 21 Sep 2014 12:45:26 -0400 Subject: [App_rpt-users] URI GPIO manipulation In-Reply-To: <541BB070.10100@gmail.com> References: <20140907.162049.21786.0@webmail07.dca.untd.com>, <541BB070.10100@gmail.com> Message-ID: That is pretty cool. This is giving me an idea. I could use pin4 of the URI to close or open my repeater from a distance. I can reset my network device by sending a ctcss code to my radio , (using a ctcss decoder) this trigger a small relay and my router/switch/modem are powered down for as long as I hold the ptt, with the exeption of the first 3 second to prevent false trigger. (simple rc time base on the base of the small transitor that trig the relay.. BUT my msf5000 is giving me some problem from time to time. It will unlock in tx and wont receive anything.. Now just a small reset on the controler reset switch will put it back to work, but not always, when that happen, it need a full power down for a few second then it is ok.. the syte can easily be access, but it is a pain to have to go there.. SO. If I can read properly.. I amusing radio usb for that repeater. I need to do those step: in usbradio.conf add: gpio1=out0 in rpt.conf in the fonction stanza I add: 90=cop,62,GPIO1=0 ; Turn off GPIO 191=cop,62,GPIO1=1 ; Turn on GPIO 1 then I will be able to do remotely a shutdown by *90and from the cli of the allstar link computer I will be able to put it back on and off by: asterisk -rx ?rpt fun 1999 *91?to start back the repeater asterisk -rx ?rpt fun 1999 *90?to close it again. Did I got it right? (of course if I do that, it wont be 90 or 91 as the fonction trigger. ) and I will make a small script that will do the closing , wait 10 second then open the repeater again.. Thanks for the answer.. Pierre > Date: Fri, 19 Sep 2014 00:26:24 -0400 > From: kp4tr.ramon at gmail.com > To: zeppelin.1 at netzero.com; app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] URI GPIO manipulation > > I have. And I wrote a page documenting how I did it: > > http://kp4tr.org/?page_id=412 > > On 9/7/2014 4:20 PM, zeppelin.1 at netzero.com wrote: > > Greetings; a technical question for anyone interested in answering. > > Incorporated k0kn txfan script on node 29103 successfully controlling a fan via PP4. > > Has anyone attempted controlling a fan via URI gpio4 with success? > > > > Anton/ kc2rqr > > Node 29103 > > ____________________________________________________________ > > The #1 Worst Carb Ever? > > Click to Learn #1 Carb that Kills Your Blood Sugar (Don't Eat This!) > > http://thirdpartyoffers.netzero.net/TGL3231/540cbe459554b3e45237bst02duc > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From k5ola at usa.com Sun Sep 21 18:34:27 2014 From: k5ola at usa.com (Ed Olague) Date: Sun, 21 Sep 2014 20:34:27 +0200 Subject: [App_rpt-users] New to Allstar Message-ID: An HTML attachment was scrubbed... URL: From kk6ecm at gmail.com Sun Sep 21 18:53:08 2014 From: kk6ecm at gmail.com (kk6ecm) Date: Sun, 21 Sep 2014 11:53:08 -0700 Subject: [App_rpt-users] New to Allstar In-Reply-To: References: Message-ID: <42E96820-E6BE-4B4B-905C-680B38BA543E@gmail.com> How did things go when you tuned your interface? See http://ohnosec.org/drupal/node/48 Thanks, Bob kk6ecm Sent from iPad > On Sep 21, 2014, at 11:34 AM, "Ed Olague" wrote: > > Hello to all: > I just set up a server and seems to working fine according to the Allstarlink site. > Node 41236 > I'm using a URIx with a Alinco DR135 I made the cable and have double checked the pin out. > The URI is blinking (green LED). > Problem is I am unable to get the radio to RX or TX through the URI (no red LED activity) > Looking for help on what i am missing or not doing. > > Ed, K5OLA > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Sun Sep 21 18:57:04 2014 From: Bryan at bryanfields.net (Bryan Fields) Date: Sun, 21 Sep 2014 14:57:04 -0400 Subject: [App_rpt-users] user login prior to control codes? Message-ID: <541F1F80.8050506@bryanfields.net> As we've had some issues with people sending control codes into the system here and linking/unlinking major hubs I'm trying to figure out a better way than just prefixing the functions in rpt.conf with a code prefix (ie *3 becomes *443). Is there a way we can do this on a per user basis? Perhaps setting up a users file with a "PIN" and then requiring a user to "login" with this PIN prior to accepting any control codes? My ideal setup would be have one rpt_users.conf file (which should be changeable with out having to reload asterisk) [users] KB9MCI 12345 KQ4ERT 43567 KB8RET 54321 Then the users would key in #PIN, the system would auth them against the file, and upon authing them, it would respond "CALLSIGN authorized", the courtesy tone would change and the user would have 60 seconds to input the control codes. On the other hand I'd be happy with a way to do this on a per user basis for each command. For Example, *3 for kb9mci would become #12345*3. Anyone have ideas on how to script this sort of a setup? 73's -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net From cypresstower at yahoo.com Sun Sep 21 19:19:48 2014 From: cypresstower at yahoo.com (Johnny Keeker) Date: Sun, 21 Sep 2014 12:19:48 -0700 Subject: [App_rpt-users] BBB node Message-ID: <1411327188.47813.YahooMailBasic@web163606.mail.gq1.yahoo.com> I have an out bound squelch crash on a beaglebone black node using simpleusb. Audio source is gated, I've tried different radio's and squelch settings. I re-configured the node for usbradio using discriminator audio. The crash is gone, but it seems other anomalies have cropped up. Anyone having the same concerns? From kk6ecm at gmail.com Sun Sep 21 20:36:35 2014 From: kk6ecm at gmail.com (Bob) Date: Sun, 21 Sep 2014 13:36:35 -0700 Subject: [App_rpt-users] ACID Firewall Configuration and public IP (static connection w/o router) Message-ID: The only information I've found regarding firewalls use with an Allstarlink.org server is with respect to a router and port forwarding. In the ACID build, the firewall seems to only address TCP for SSH, and not the UDP. Is the assumption here that all Allsterlink.org servers will be behind a firewall such as with a router? What about protection when the server is on a public IP address, statically set, without a router? What protection is afforded here? Is it then necessary to setup the ACID firewall with "Other ports" using "222:TCP 4569:UDP"? I only see "SSH" in the Allow incoming: section, and should eth0 be unchecked? Thanks, r/Bob kk6ecm -------------- next part -------------- An HTML attachment was scrubbed... URL: From telesistant at hotmail.com Sun Sep 21 21:33:23 2014 From: telesistant at hotmail.com (Jim Duuuude) Date: Sun, 21 Sep 2014 14:33:23 -0700 Subject: [App_rpt-users] user login prior to control codes? In-Reply-To: <541F1F80.8050506@bryanfields.net> References: <541F1F80.8050506@bryanfields.net> Message-ID: That sort of a thing was never implemented because of the open-interoperability nature of Allstar. That would prevent any user from going to any Allstar-linked system and be able to use it, which is one of the fundamental premises of Allstar. "Logins" are implemented to remote-base use, but not for general repeater use. Jim WB6NIL > Date: Sun, 21 Sep 2014 14:57:04 -0400 > From: Bryan at bryanfields.net > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] user login prior to control codes? > > As we've had some issues with people sending control codes into the system > here and linking/unlinking major hubs I'm trying to figure out a better way > than just prefixing the functions in rpt.conf with a code prefix (ie *3 > becomes *443). > > Is there a way we can do this on a per user basis? Perhaps setting up a users > file with a "PIN" and then requiring a user to "login" with this PIN prior to > accepting any control codes? > > My ideal setup would be have one rpt_users.conf file (which should be > changeable with out having to reload asterisk) > > [users] > > KB9MCI 12345 > KQ4ERT 43567 > KB8RET 54321 > > Then the users would key in #PIN, the system would auth them against the file, > and upon authing them, it would respond "CALLSIGN authorized", the courtesy > tone would change and the user would have 60 seconds to input the control codes. > > On the other hand I'd be happy with a way to do this on a per user basis for > each command. For Example, *3 for kb9mci would become #12345*3. > > Anyone have ideas on how to script this sort of a setup? > > 73's > -- > Bryan Fields > > 727-409-1194 - Voice > 727-214-2508 - Fax > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Sun Sep 21 22:04:15 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Sun, 21 Sep 2014 15:04:15 -0700 Subject: [App_rpt-users] Call sign changes Message-ID: File this under ?Learn something every day"... Folks who have requested a call sign change have found that even after the Admin changes your call the status pages do not update. Turns out this a feature not a bug, of course :-). The call sign of your account is not the same as the call sign of your node(s). The idea is that you can operate multiple call signs under your one Allstar account, for example a club call, etc. To change your node?s call, go on the portal and bring up your node, then repeater settings. Change the call sign there. -- Tim :wq -------------- next part -------------- An HTML attachment was scrubbed... URL: From srice3 at cfl.rr.com Sun Sep 21 22:16:56 2014 From: srice3 at cfl.rr.com (The Rices) Date: Sun, 21 Sep 2014 18:16:56 -0400 Subject: [App_rpt-users] XIPAR install In-Reply-To: References: <541F1F80.8050506@bryanfields.net> Message-ID: <7F3CBFEBD2A3417CB4569CDDA33F27BD@AdminPC> Got my system working with the XIPAR install from the old Acid install that would hang every so often but had a question. Has anyone figured out a way to use web transceiver with the XIPAR install? I was just curious as it was nice to be able to turn that on at the Allstar site when I wanted to let others access it that way. Thanks Steve N4YZA -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Sun Sep 21 22:37:45 2014 From: Bryan at bryanfields.net (Bryan Fields) Date: Sun, 21 Sep 2014 18:37:45 -0400 Subject: [App_rpt-users] user login prior to control codes? In-Reply-To: References: <541F1F80.8050506@bryanfields.net> Message-ID: <541F5339.2020405@bryanfields.net> On 9/21/14, 5:33 PM, Jim Duuuude wrote: > That sort of a thing was never implemented because of the open-interoperability > nature of Allstar. That would prevent any user from going to any Allstar-linked > system and be able to use it, which is one of the fundamental premises of Allstar. Thanks Duuuuude, I'm not necessarily talking about the Allstar Link, but app_rpt in general. We have a need for this here and I'm generally in favor of open access, but it's become a problem to leave it open with the default Allstar Link access codes. I'm looking for better flexibility in this regard. Would it be easy to take the remote base "login" functionality and apply it to certain sections of rpt.conf? There a quite a few people running app_rpt without interlinking with Allstar at each site (private nodes). Thoughts? -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net From n9udo at yellowthunder.org Sun Sep 21 22:55:54 2014 From: n9udo at yellowthunder.org (Steve Schulze) Date: Sun, 21 Sep 2014 17:55:54 -0500 Subject: [App_rpt-users] URI Problem In-Reply-To: References: <541DB83F.5080801@yellowthunder.org>, , , <541EBCFB.8010409@yellowthunder.org>, Message-ID: <541F577A.6030001@yellowthunder.org> I will try a different port first and I do have another URI I can try as well. Thanks everyone for your input. Amateur Radio - The Original Social Media Steve Schulze - Radio Amateur, General Class - N9UDO Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 Treasurer, Badgerland Amateur Television Society - KB9SFS http://yellowthunder.org/dstar.html On 9/21/2014 8:41 AM, Doug Crompton wrote: > I meant to say SW and/or HW problem. Have you tried a different USB > port on the PC. Do you have another URI to try? I doubt it is the URI > but you never know. > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: doug at crompton.com > To: n9udo at yellowthunder.org > Date: Sun, 21 Sep 2014 09:22:46 -0400 > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] URI Problem > > Steve, > > It sounds like it might be a SW issue in your PC. From what you say > outside influences should reset the URI. Take a good look at your logs > on the PC both system and Asterisk and see if you can determine anything. > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > Date: Sun, 21 Sep 2014 06:56:43 -0500 > From: n9udo at yellowthunder.org > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] URI Problem > > Doug. > > I'm running a PC with usbradio. > > This is something that just recently showed up. The system has been > running fine at it's current location for over a year. The IBM PC that > I'm using has a (heavy) metal chassis and I should be able to get a > good ground on it back to the building's halo. > > Unplugging the URI and plugging back in does reset it. When it's not > working, the green LED is steady. > > > Thanks! > Amateur Radio - The Original Social Media > > Steve Schulze - Radio Amateur, General Class - N9UDO > Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ > Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 > Treasurer, Badgerland Amateur Television Society - KB9SFS > > http://yellowthunder.org/dstar.html > On 9/20/2014 12:54 PM, Doug Crompton wrote: > > Steve, > > What computer are you using? PC or Beagle Bone Black? etc. Also > usbradio or simpleusb? > > This is a common problem on the URI with external EMI and power > spikes. > > The problem can be fixed. You need to ground everything and > eliminate EMI as much as possible. > > The other issue is the USB not resetting when it has this problem. > Most of the PC's will but probably not all. The next version of > the BBB code coming out soon will reset fine. > > If you are using simpleusb there is a bug in the code that > precludes a reset upon USB interruption. This fix will also be in > the BBB code that is coming soon. If you want to fix a PC > simplesusb installation here is the link - > > http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/simpleusb-howto.pdf > > See how to do the patch at the end of the pdf. > > You should be able to pull the USB cable from the URI while in use > (green light flashing normally) and reinstall the USB and it > should start flashing again. If not then your system will not > recover from USB EMI hits properly. > > It is always a good idea to try and fix or reduce the problem > because in severe cases it would be resetting all the time. It > sounds like you case is less severe. > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > > Date: Sat, 20 Sep 2014 12:24:15 -0500 > > From: n9udo at yellowthunder.org > > To: app_rpt-users at ohnosec.org > > Subject: [App_rpt-users] URI Problem > > > > Has anyone run across a URI that goes 'offline' every 3 to 4 > days? A > > simple warm boot command or astres.sh will bring it back on line > as well > > as unplugging the URI and plugging back in. > > > > There is no indication that it's not working to the online user. > You can > > connect to the box but no audio (either direction) or PTT passes > to the > > repeater until you reset it. > > > > I have installed ferrites on each end of the USB cable and on the > > control cable on the URI side but no change. > > > > > > Any thoughts? > > > > > > Thanks in advance. > > > > -- > > Amateur Radio - The Original Social Media > > > > Steve Schulze - Radio Amateur, General Class - N9UDO > > Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ > > Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 > > Treasurer, Badgerland Amateur Television Society - KB9SFS > > > > http://yellowthunder.org/dstar.html > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at dyb.com Mon Sep 22 05:14:37 2014 From: george at dyb.com (George Csahanin) Date: Mon, 22 Sep 2014 00:14:37 -0500 Subject: [App_rpt-users] ping pong-somewhat demystified and a turn for the twilight zone In-Reply-To: References: <67F4591CBE954D7A8338FF74821CA6FE@georgecPC> Message-ID: <0ED3F31114704C9BB187F7167780232D@georgecPC> Back in town... Limey has this script, getsrc, that worked in the past. And yeah, looks at the tgz on the CF card, but that?s old source, so eliminated that file and it did download a source file, but it is August 2011 version, not new source. I can get the source from svn, no problem. The issue is that it suddenly won?t compile. ./configure is needed to run to make a Makefile. But I even tried just adding the line to the old source (chan_simpleusb.c) to add rxondelay. Can?t get configure to run without noting these errors. It claims the said .h file is missing, I just need to know where it needs to be. It exists, just (it seems) not in the right place. And as to the vintage of the source, I recall that the source for asterisk on a limey platform was different and from a different place, but don?t know what/why/when. GeorgeC George J Csahanin W2DB Cedar Park, TX 512-401-2630 home 401-338-0568 cel From: Tim Sawyer Sent: Wednesday, September 17, 2014 9:25 AM To: George Csahanin Subject: Re: [App_rpt-users] ping pong-somewhat demystified and a turn for the twilight zone Actually I don?t think the upgrade runs configure. -- Tim WD6AWP On Sep 16, 2014, at 10:43 PM, George Csahanin wrote: Looks good, thanks. I always used the built in getsrc script. I still need to solve the compiler issue so I can actually do this upgrade. Thanks, Tim. George George J Csahanin W2DB Cedar Park, TX 512-401-2630 home 401-338-0568 cel From: Tim Sawyer Sent: Tuesday, September 16, 2014 11:13 PM To: George Csahanin Subject: Re: [App_rpt-users] ping pong-somewhat demystified and a turn for the twilight zone Is there a reason not to use the normal upgrade procedure? https://allstarlink.org/support.html#astupgrade -- Tim :wq On Sep 16, 2014, at 8:54 PM, George Csahanin wrote: OK, found an old message from Jim that says this was fixed by adding a line to make rxondelay work, and my source is from August 31 2011, which is two years before the fix. I?m going to step into the deep end here and ask a question that may seem like a limey question, but really a cpp question. ./configure output says cpp failed sanity test, look at the log file and I see that it was looking for an include file but cannot find it. The one in question is limits.h, supposedly in linux/limits.h and I looked in /usr/include and it is there. So, please, somebody learn me here. This has been a mystery to me since I started hacking this stuff in the early 90?s and proves why I should maybe stick to broken down TV stations...but...WHERE is it looking for this include file? In limey the source all goes under /usr/src/astsrc/ then under that in /usr/src/astsrc/asterisk is where ./configure, etc is. I tried loading new source, and the August 31, 2011 is what getsrc will download. So added question, assuming I can make this work, can I load the latest source code on the limey box, I have never seen anything different. But curious. George J Csahanin W2DB Cedar Park, TX _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vencl at att.net Mon Sep 22 12:13:01 2014 From: vencl at att.net (Lu Vencl) Date: Mon, 22 Sep 2014 08:13:01 -0400 Subject: [App_rpt-users] RXDELAY in XIPAR Message-ID: <156701cfd65e$8ef08130$acd18390$@att.net> I have a XIPAR node that needs a little support with pulseback removal. Never had to utilize this before, but when looking in URD.conf, I don't see the rxdelay= parameter like I do on ACID builds. I went ahead and inserted the command into the file, but there does not seem to be any action. Can someone confirm the parameter and placement? Here is my example: [usb] hdwtype=0 ; 0=std,1=dev eeprom=0 ; unless you have a cable w/eeprom duplex=0 ; 0=simplex, 1=duplex invertptt=0 ;minsigproc=0 ; minimal signal processing ;sendvoter=0 ; 0=default, no voter rssi, 1=enable voter rssi carrierfrom=usbinvert ; no,usb,usbinvert,dsp,vox ctcssfrom=no ; no,usb,dsp rxondelay=3000 ; Gets rid of the pulseback problem ;rxboost=1 ; rx input boost of 20dB rxboost=0 ; no boost rxdemod=flat ; no,speaker,flat txprelim=0 ; 1 = pre-emphasize and limit txmixa=voice ; no,voice,tone,composite txmixb=tone ; no,voice,tone,composite,auxvoice ;txctcssdefault=77.0 ;rxctcssfreqs=77.0; ;txctcssfreqs=77.0; txtoctype=notone; rxsquelchdelay=900 ; delayline in ms carrier squelch tail eliminator rxnoisefiltype=0 ; 0 for +/-5KHz, 2 for +/-2.5KHz systems Lu, KA4EPS -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Mon Sep 22 13:46:26 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Mon, 22 Sep 2014 06:46:26 -0700 Subject: [App_rpt-users] RXDELAY in XIPAR In-Reply-To: <156701cfd65e$8ef08130$acd18390$@att.net> References: <156701cfd65e$8ef08130$acd18390$@att.net> Message-ID: <6B4EB452-858E-491C-B07A-B912106F9374@mac.com> Really? You need a 3 second delay? -- Tim WD6AWP > On Sep 22, 2014, at 5:13 AM, Lu Vencl wrote: > > I have a XIPAR node that needs a little support with pulseback removal. Never had to utilize this before, but when looking in URD.conf, I don?t see the rxdelay= parameter like I do on ACID builds. I went ahead and inserted the command into the file, but there does not seem to be any action. > Can someone confirm the parameter and placement? > Here is my example: > [usb] > > hdwtype=0 ; 0=std,1=dev > eeprom=0 ; unless you have a cable w/eeprom > duplex=0 ; 0=simplex, 1=duplex > invertptt=0 > ;minsigproc=0 ; minimal signal processing > ;sendvoter=0 ; 0=default, no voter rssi, 1=enable voter rssi > > carrierfrom=usbinvert ; no,usb,usbinvert,dsp,vox > ctcssfrom=no ; no,usb,dsp > rxondelay=3000 ; Gets rid of the pulseback problem > ;rxboost=1 ; rx input boost of 20dB > rxboost=0 ; no boost > rxdemod=flat ; no,speaker,flat > txprelim=0 ; 1 = pre-emphasize and limit > > txmixa=voice ; no,voice,tone,composite > txmixb=tone ; no,voice,tone,composite,auxvoice > > ;txctcssdefault=77.0 > ;rxctcssfreqs=77.0; > ;txctcssfreqs=77.0; > txtoctype=notone; > > rxsquelchdelay=900 ; delayline in ms carrier squelch tail eliminator > rxnoisefiltype=0 ; 0 for +/-5KHz, 2 for +/-2.5KHz systems > > > Lu, > KA4EPS > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vencl at att.net Mon Sep 22 14:07:48 2014 From: vencl at att.net (Lu Vencl) Date: Mon, 22 Sep 2014 10:07:48 -0400 Subject: [App_rpt-users] RXDELAY in XIPAR In-Reply-To: <6B4EB452-858E-491C-B07A-B912106F9374@mac.com> References: <156701cfd65e$8ef08130$acd18390$@att.net> <6B4EB452-858E-491C-B07A-B912106F9374@mac.com> Message-ID: <46719A95-463D-4B06-B7F6-6CDEB348E7FF@att.net> Just made it long to test. But not effective. Probably only need 150 ms. Lu Vencl > On Sep 22, 2014, at 9:46 AM, Tim Sawyer wrote: > > Really? You need a 3 second delay? > -- > Tim WD6AWP > >> On Sep 22, 2014, at 5:13 AM, Lu Vencl wrote: >> >> I have a XIPAR node that needs a little support with pulseback removal. Never had to utilize this before, but when looking in URD.conf, I don?t see the rxdelay= parameter like I do on ACID builds. I went ahead and inserted the command into the file, but there does not seem to be any action. >> Can someone confirm the parameter and placement? >> Here is my example: >> [usb] >> >> hdwtype=0 ; 0=std,1=dev >> eeprom=0 ; unless you have a cable w/eeprom >> duplex=0 ; 0=simplex, 1=duplex >> invertptt=0 >> ;minsigproc=0 ; minimal signal processing >> ;sendvoter=0 ; 0=default, no voter rssi, 1=enable voter rssi >> >> carrierfrom=usbinvert ; no,usb,usbinvert,dsp,vox >> ctcssfrom=no ; no,usb,dsp >> rxondelay=3000 ; Gets rid of the pulseback problem >> ;rxboost=1 ; rx input boost of 20dB >> rxboost=0 ; no boost >> rxdemod=flat ; no,speaker,flat >> txprelim=0 ; 1 = pre-emphasize and limit >> >> txmixa=voice ; no,voice,tone,composite >> txmixb=tone ; no,voice,tone,composite,auxvoice >> >> ;txctcssdefault=77.0 >> ;rxctcssfreqs=77.0; >> ;txctcssfreqs=77.0; >> txtoctype=notone; >> >> rxsquelchdelay=900 ; delayline in ms carrier squelch tail eliminator >> rxnoisefiltype=0 ; 0 for +/-5KHz, 2 for +/-2.5KHz systems >> >> >> Lu, >> KA4EPS >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kb3ors at gmail.com Mon Sep 22 16:23:51 2014 From: kb3ors at gmail.com (Brian Burton) Date: Mon, 22 Sep 2014 12:23:51 -0400 Subject: [App_rpt-users] App_rpt-users Digest, Vol 67, Issue 65 In-Reply-To: References: Message-ID: In xipar its txrxdelay= 20 ms intervals. AB3AA-Brian On Sep 22, 2014 12:00 PM, wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users at ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request at ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner at ohnosec.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. Re: RXDELAY in XIPAR (Lu Vencl) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 22 Sep 2014 10:07:48 -0400 > From: Lu Vencl > To: Tim Sawyer > Cc: "app_rpt-users at ohnosec.org" , > "webmaster at n4yza.com" > Subject: Re: [App_rpt-users] RXDELAY in XIPAR > Message-ID: <46719A95-463D-4B06-B7F6-6CDEB348E7FF at att.net> > Content-Type: text/plain; charset="utf-8" > > Just made it long to test. But not effective. Probably only need 150 ms. > > Lu Vencl > > > On Sep 22, 2014, at 9:46 AM, Tim Sawyer wrote: > > > > Really? You need a 3 second delay? > > -- > > Tim WD6AWP > > > >> On Sep 22, 2014, at 5:13 AM, Lu Vencl wrote: > >> > >> I have a XIPAR node that needs a little support with pulseback removal. > Never had to utilize this before, but when looking in URD.conf, I don?t see > the rxdelay= parameter like I do on ACID builds. I went ahead and inserted > the command into the file, but there does not seem to be any action. > >> Can someone confirm the parameter and placement? > >> Here is my example: > >> [usb] > >> > >> hdwtype=0 ; 0=std,1=dev > >> eeprom=0 ; unless you have a cable w/eeprom > >> duplex=0 ; 0=simplex, 1=duplex > >> invertptt=0 > >> ;minsigproc=0 ; minimal signal processing > >> ;sendvoter=0 ; 0=default, no voter rssi, 1=enable voter rssi > >> > >> carrierfrom=usbinvert ; no,usb,usbinvert,dsp,vox > >> ctcssfrom=no ; no,usb,dsp > >> rxondelay=3000 ; Gets rid of the pulseback problem > >> ;rxboost=1 ; rx input boost of 20dB > >> rxboost=0 ; no boost > >> rxdemod=flat ; no,speaker,flat > >> txprelim=0 ; 1 = pre-emphasize and limit > >> > >> txmixa=voice ; no,voice,tone,composite > >> txmixb=tone ; no,voice,tone,composite,auxvoice > >> > >> ;txctcssdefault=77.0 > >> ;rxctcssfreqs=77.0; > >> ;txctcssfreqs=77.0; > >> txtoctype=notone; > >> > >> rxsquelchdelay=900 ; delayline in ms carrier squelch tail eliminator > >> rxnoisefiltype=0 ; 0 for +/-5KHz, 2 for +/-2.5KHz systems > >> > >> > >> Lu, > >> KA4EPS > >> _______________________________________________ > >> App_rpt-users mailing list > >> App_rpt-users at 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. > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://ohnosec.org/pipermail/app_rpt-users/attachments/20140922/20917ad4/attachment-0001.html > > > > ------------------------------ > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > End of App_rpt-users Digest, Vol 67, Issue 65 > ********************************************* > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kuggie at kuggie.com Mon Sep 22 18:38:53 2014 From: kuggie at kuggie.com (Kevin Custer) Date: Mon, 22 Sep 2014 14:38:53 -0400 Subject: [App_rpt-users] RXDELAY in XIPAR In-Reply-To: <46719A95-463D-4B06-B7F6-6CDEB348E7FF@att.net> References: <156701cfd65e$8ef08130$acd18390$@att.net> <6B4EB452-858E-491C-B07A-B912106F9374@mac.com> <46719A95-463D-4B06-B7F6-6CDEB348E7FF@att.net> Message-ID: <54206CBD.5080306@kuggie.com> I'd have to dig a bit, but I believe this setting does not work as intended in XIPAR. Please stand by..... I'm sorry to have kept you waiting. In XIPAR it's txrxdelay= 20 ms intervals. Kevin On 9/22/2014 10:07 AM, Lu Vencl wrote: > Just made it long to test. But not effective. Probably only need 150 ms. > > Lu Vencl > > On Sep 22, 2014, at 9:46 AM, Tim Sawyer > wrote: > >> Really? You need a 3 second delay? >> -- >> Tim WD6AWP >> >>> On Sep 22, 2014, at 5:13 AM, Lu Vencl >> > wrote: >>> >>> I have a XIPAR node that needs a little support with pulseback >>> removal. Never had to utilize this before, but when looking in >>> URD.conf, I don't see the rxdelay= parameter like I do on ACID >>> builds. I went ahead and inserted the command into the file, but >>> there does not seem to be any action. >>> Can someone confirm the parameter and placement? >>> Here is my example: >>> [usb] >>> hdwtype=0 ; 0=std,1=dev >>> eeprom=0 ; unless you have a cable w/eeprom >>> duplex=0 ; 0=simplex, 1=duplex >>> invertptt=0 >>> ;minsigproc=0 ; minimal signal processing >>> ;sendvoter=0 ; 0=default, no voter rssi, 1=enable voter rssi >>> carrierfrom=usbinvert ; no,usb,usbinvert,dsp,vox >>> ctcssfrom=no ; no,usb,dsp >>> rxondelay=3000 ; Gets rid of the pulseback problem >>> ;rxboost=1 ; rx input boost of 20dB >>> rxboost=0 ; no boost >>> rxdemod=flat ; no,speaker,flat >>> txprelim=0 ; 1 = pre-emphasize and limit >>> txmixa=voice ; no,voice,tone,composite >>> txmixb=tone ; no,voice,tone,composite,auxvoice >>> ;txctcssdefault=77.0 >>> ;rxctcssfreqs=77.0; >>> ;txctcssfreqs=77.0; >>> txtoctype=notone; >>> rxsquelchdelay=900 ; delayline in ms carrier squelch tail eliminator >>> rxnoisefiltype=0 ; 0 for +/-5KHz, 2 for +/-2.5KHz systems >>> Lu, >>> KA4EPS >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at ohnosec.org >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please >>> visithttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-usersand >>> 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 at 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. > > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2014.0.4765 / Virus Database: 4025/8255 - Release Date: 09/22/14 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at controlservers.net Mon Sep 22 18:49:07 2014 From: robert at controlservers.net (Robert) Date: Mon, 22 Sep 2014 11:49:07 -0700 Subject: [App_rpt-users] RTCM Arrived Message-ID: <2C7332360943426CA115A64BD702F595@desktop> My first RTCM arrived and it is my intention to use one on each of my MSF 5000's. So far I haven't read of a solid way of interfacing to either CLB or CBX models. Any help would be appreciated except that I plan to place a RC-210 in front of the RTCM. We won't be voting. At best we will attempt to sync the TX and audio on three repeaters. Or not. I have no idea what the controller can do as far as external links or operating as a full repeater controller. I have a weather RX to add, a semi-duplex link, etc. I have thought of using a 2m radio (or 440; the site has 440 for control) with a RC-210 connected to it and using IT to link to the repeater. Any thoughts? I appreciate all of you! Robert -------------- next part -------------- An HTML attachment was scrubbed... URL: From gene at wb9coy.com Tue Sep 23 22:34:22 2014 From: gene at wb9coy.com (gene at wb9coy.com) Date: Tue, 23 Sep 2014 15:34:22 -0700 Subject: [App_rpt-users] Not able to receive incoming connections Message-ID: <20140923153422.6bda0fc0b2fcdc09c2716b2cba60b34f.b59f50f291.wbe@email12.secureserver.net> My node is 41303 W6QAR I have verified that I NAT on port 4569. It was mentioned that a check can be done on my node to see if it had to be forced. From doug at crompton.com Tue Sep 23 23:38:57 2014 From: doug at crompton.com (Doug Crompton) Date: Tue, 23 Sep 2014 19:38:57 -0400 Subject: [App_rpt-users] Not able to receive incoming connections In-Reply-To: <20140923153422.6bda0fc0b2fcdc09c2716b2cba60b34f.b59f50f291.wbe@email12.secureserver.net> References: <20140923153422.6bda0fc0b2fcdc09c2716b2cba60b34f.b59f50f291.wbe@email12.secureserver.net> Message-ID: Gene, Not sure what you mean by forced but you need to port foward port 4569 upd to the IP address of your Allstar computer. The Allstar computer should be set as a static IP address on your local network so that the local address does not change. In addition if you want to access your system remotely or have someone else do it for maintenance you need to port forward port 222 tcp to the IP address of your Allstar computer. 73 Doug WA3DSP http://www.crompton.com/hamradio > From: gene at wb9coy.com > To: app_rpt-users at ohnosec.org > Date: Tue, 23 Sep 2014 15:34:22 -0700 > Subject: [App_rpt-users] Not able to receive incoming connections > > My node is 41303 W6QAR > > I have verified that I NAT on port 4569. It was mentioned that a check > can be done on my node to see if it had to be forced. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gene at wb9coy.com Wed Sep 24 05:37:21 2014 From: gene at wb9coy.com (gene at wb9coy.com) Date: Tue, 23 Sep 2014 22:37:21 -0700 Subject: [App_rpt-users] =?utf-8?q?Not_able_to_receive_incoming_connection?= =?utf-8?q?s?= Message-ID: <20140923223721.6bda0fc0b2fcdc09c2716b2cba60b34f.7324a418f0.wbe@email12.secureserver.net> An HTML attachment was scrubbed... URL: From gene at wb9coy.com Wed Sep 24 06:09:09 2014 From: gene at wb9coy.com (gene at wb9coy.com) Date: Tue, 23 Sep 2014 23:09:09 -0700 Subject: [App_rpt-users] =?utf-8?q?Not_able_to_receive_incoming_connection?= =?utf-8?q?s?= Message-ID: <20140923230909.6bda0fc0b2fcdc09c2716b2cba60b34f.57f5307248.wbe@email12.secureserver.net> An HTML attachment was scrubbed... URL: From doug at crompton.com Wed Sep 24 06:36:53 2014 From: doug at crompton.com (Doug Crompton) Date: Wed, 24 Sep 2014 02:36:53 -0400 Subject: [App_rpt-users] Not able to receive incoming connections In-Reply-To: <20140923223721.6bda0fc0b2fcdc09c2716b2cba60b34f.7324a418f0.wbe@email12.secureserver.net> References: <20140923223721.6bda0fc0b2fcdc09c2716b2cba60b34f.7324a418f0.wbe@email12.secureserver.net> Message-ID: Gene, There is no way to "force" something through a router that is miss-configured or not working correctly. In the router you should be able to port forward and you need the following ports forwarded 4569 udp 222 tcp It is important that you specify udp and tcp. In some case you can say 'both' Both ports should be forwarded to your Allstar box IP address. Without 4569 no one will be able to connect to you. Without 222 no one will be able to administratively connect to your allstar. There is no way around this you need the forwards to work. In a pinch you could setup DMZ in the router to the allstar box and see if it works. If it doesn't you have other problems but if it does then you know you port forwarding is incorrect. I don't know your router but there is probably someone else on here that could help. I know with the Verizon FIOS routers you need specify the from port and IP as any and the to port and Ip as the ones you want it to go to. Specifying the from port as a specific number even if it is the right number does not work. 73 Doug WA3DSP http://www.crompton.com/hamradio From: gene at wb9coy.com To: doug at crompton.com CC: app_rpt-users at ohnosec.org Subject: RE: [App_rpt-users] Not able to receive incoming connections Date: Tue, 23 Sep 2014 22:37:21 -0700 Hi Doug, thanks for the response. My router is an ATT U-Verse I have NAT to port 4569 and 222. For some reason I can not connect to it. It shows up on the Web Xcvr. I am able to have QSOs on node 2003. I think it is an in-bound issue. I read on the AllStar pages that a sys admin might have to force port 4569 on the AllStar side. I am writting to this mail list because I am stuck on why I can not conntec to my node which is 41303 -------- Original Message -------- Subject: RE: [App_rpt-users] Not able to receive incoming connections From: Doug Crompton Date: Tue, September 23, 2014 4:38 pm To: "gene at wb9coy.com" Cc: "app_rpt-users at ohnosec.org" Gene, Not sure what you mean by forced but you need to port foward port 4569 upd to the IP address of your Allstar computer. The Allstar computer should be set as a static IP address on your local network so that the local address does not change. In addition if you want to access your system remotely or have someone else do it for maintenance you need to port forward port 222 tcp to the IP address of your Allstar computer. 73 Doug WA3DSP http://www.crompton.com/hamradio > From: gene at wb9coy.com > To: app_rpt-users at ohnosec.org > Date: Tue, 23 Sep 2014 15:34:22 -0700 > Subject: [App_rpt-users] Not able to receive incoming connections > > My node is 41303 W6QAR > > I have verified that I NAT on port 4569. It was mentioned that a check > can be done on my node to see if it had to be forced. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jrorke at cogeco.ca Wed Sep 24 14:05:28 2014 From: jrorke at cogeco.ca (Jon Rorke) Date: Wed, 24 Sep 2014 10:05:28 -0400 Subject: [App_rpt-users] Not able to receive incoming connections In-Reply-To: References: <20140923223721.6bda0fc0b2fcdc09c2716b2cba60b34f.7324a418f0.wbe@email12.secureserver.net> Message-ID: <5422CFA8.3030604@cogeco.ca> You node is not reporting to the allstar server. First make sure you have these lines uncommented in your node: statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null ; Get the system list for this server statpost_url=http://stats.allstarlink.org/uhandler.php And then make sure you /etc/resolv.conf file has a valid namserver in it if your box is on a static IP. nameserver 8.8.8.8 Then if you node statrs to report to the Allstar site then after 15 min or so nodes should be able to connect. This assumes you do have all the ports properly forwarded in your router. Jon On 9/24/2014 2:36 AM, Doug Crompton wrote: > Gene, > > There is no way to "force" something through a router that is > miss-configured or not working correctly. > > In the router you should be able to port forward and you need the > following ports forwarded > > 4569 udp > 222 tcp > > It is important that you specify udp and tcp. In some case you can say > 'both' > > Both ports should be forwarded to your Allstar box IP address. Without > 4569 no one will be able to connect to you. Without 222 no one will be > able to administratively connect to your allstar. > > There is no way around this you need the forwards to work. In a pinch > you could setup DMZ in the router to the allstar box and see if it > works. If it doesn't you have other problems but if it does then you > know you port forwarding is incorrect. > > I don't know your router but there is probably someone else on here > that could help. I know with the Verizon FIOS routers you need specify > the from port and IP as any and the to port and Ip as the ones you > want it to go to. Specifying the from port as a specific number even > if it is the right number does not work. > > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: gene at wb9coy.com > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > Subject: RE: [App_rpt-users] Not able to receive incoming connections > Date: Tue, 23 Sep 2014 22:37:21 -0700 > > Hi Doug, thanks for the response. My router is an ATT U-Verse > I have NAT to port 4569 and 222. For some reason I can not connect to > it. It shows up on the Web Xcvr. I am able to have QSOs on node > 2003. I think it is an in-bound issue. I read on the AllStar pages > that a sys admin might have to force port 4569 on the AllStar side. > I am writting to this mail list because I am stuck on why I can not > conntec to my node which is 41303 > > -------- Original Message -------- > Subject: RE: [App_rpt-users] Not able to receive incoming connections > From: Doug Crompton > > Date: Tue, September 23, 2014 4:38 pm > To: "gene at wb9coy.com " > > Cc: "app_rpt-users at ohnosec.org " > > > > Gene, > > Not sure what you mean by forced but you need to port foward port > 4569 upd to the IP address of your Allstar computer. The Allstar > computer should be set as a static IP address on your local > network so that the local address does not change. > > In addition if you want to access your system remotely or have > someone else do it for maintenance you need to port forward port > 222 tcp to the IP address of your Allstar computer. > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > > From:gene at wb9coy.com > > To: app_rpt-users at ohnosec.org > > Date: Tue, 23 Sep 2014 15:34:22 -0700 > > Subject: [App_rpt-users] Not able to receive incoming connections > > > > My node is 41303 W6QAR > > > > I have verified that I NAT on port 4569. It was mentioned that a > check > > can be done on my node to see if it had to be forced. > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorentedford at gmail.com Thu Sep 25 01:52:22 2014 From: lorentedford at gmail.com (Loren Tedford) Date: Wed, 24 Sep 2014 20:52:22 -0500 Subject: [App_rpt-users] Security Issues Message-ID: Hey its Loren here again... Was curious what everyone found was the most substantial security risk with a Acid installation connected too two repeaters.. The sip.conf was deleted from the asterisks folder.. Noticed a strange node connection that didn?t match all stars normal node numbers 3101702 also found some thing with x.allstarlink.org in it anybody know what this is?? Anyway my linode server has been under constant attack from China they keep wanting to ssh into the server we had to drastically beef up things on the server such as changing the whole root user issue and moving to another port number etc.. Any thoughts ideas did i just become victum of a Sip attack too besides 19 ddos attacks this week already and over a million failed ssh attempts into my person linode server... Loren Tedford (KC9ZHV) Email: lorentedford at gmail.com http://www.lorentedford.com http://www.Ltcraft.net http://www.richlandcountycomputers.com http://kc9zhv.lorentedford.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Thu Sep 25 02:43:16 2014 From: doug at crompton.com (Doug Crompton) Date: Wed, 24 Sep 2014 22:43:16 -0400 Subject: [App_rpt-users] Security Issues In-Reply-To: References: Message-ID: I assume you have the linux box behind a router? If so why would you have sip even routed to your linux box if you are not using it? Routers make good firewalls. The only thing you should have routed is 4569 (udp) and 222 (tcp) neither have to be routed. 4569 would only need to be routed if you wanted to accept incoming connections. Outgoing would work fine without it. 222 would only be needed for administration. >From what you are saying you obviously must not have a front-end (router firewall etc.) on your system . It sounds like you are just hanging on the raw Internet!! Some people go the easy route and put thhings in the DMZ of their routers which does open them up to the world. I went into an Allstar system this week to help with setup and I immediately knew it was on the DMZ. In the Asterisk client I was getting sip messages left and right. I unloaded the sip module and they went away. Not the right way to do it though as it should not be on dmz to begin with. Simply not having a sip.conf file does not prevent sip traffic!!! Assuming you have a router there should be no need to disable sip as it is never going to get to your box unless you port forward it there. It would be a good idea thought to not load the code for it if you are not using it. A noload=chan_sip.so in modules.conf would take care of that. Most good routers also allow you to specify specific or blocks of IP addresses to disallow. If there is a specific foreign block, say in China you can identify you could probably block it. So the bottom line is you could make your linux system tottally unavailable to the outside world by just not forwarding any ports. The downside is no one could connect to you (sometimes desirable) and you could not remotely administer your system. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Wed, 24 Sep 2014 20:52:22 -0500 From: lorentedford at gmail.com To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Security Issues Hey its Loren here again... Was curious what everyone found was the most substantial security risk with a Acid installation connected too two repeaters.. The sip.conf was deleted from the asterisks folder.. Noticed a strange node connection that didn?t match all stars normal node numbers 3101702 also found some thing with x.allstarlink.org in it anybody know what this is?? Anyway my linode server has been under constant attack from China they keep wanting to ssh into the server we had to drastically beef up things on the server such as changing the whole root user issue and moving to another port number etc.. Any thoughts ideas did i just become victum of a Sip attack too besides 19 ddos attacks this week already and over a million failed ssh attempts into my person linode server... Loren Tedford (KC9ZHV) Email: lorentedford at gmail.com http://www.lorentedford.com http://www.Ltcraft.nethttp://www.richlandcountycomputers.comhttp://kc9zhv.lorentedford.com _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken at kc2idb.net Thu Sep 25 07:43:28 2014 From: ken at kc2idb.net (Ken Boyle) Date: Thu, 25 Sep 2014 03:43:28 -0400 Subject: [App_rpt-users] Security Issues Message-ID: You could also install fail2ban. By default it allows three failed password attempts. Than temporarily bans the IP address. On Sep 24, 2014 10:43 PM, Doug Crompton wrote: > > I assume you have the linux box behind a router? If so why would you have sip even routed to your linux box if you are not using it? Routers make good firewalls. The only thing you should have routed is 4569 (udp) and 222 (tcp) ? neither have to be routed.? 4569 would only need to be routed if you wanted to accept incoming connections. Outgoing would work fine without it. 222 would only be needed for administration. > > From what you are saying you obviously must not have a front-end (router firewall etc.) on your system . It sounds like you are just hanging on the raw Internet!! Some people go the easy route and put thhings in the DMZ of their routers which does open them up to the world. I went into an Allstar system this week to help with setup and I immediately knew it was on the DMZ. In the Asterisk client I was getting sip messages left and right. I unloaded the sip module and they went away. Not the right way to do it though as it should not be on dmz to begin with. Simply not having a sip.conf file does not prevent sip traffic!!! > > Assuming you have a router there should be no need to disable sip as it is never going to get to your box unless you port forward it there. It would be a good idea thought to not load the code for it if you are not using it. A noload=chan_sip.so ? in modules.conf would take care of that. > > Most good routers also allow you to specify specific or blocks of IP addresses to disallow. If there is a specific foreign block, say in China you can identify you could probably block it. > > So the bottom line is you could make your linux system tottally unavailable to the outside world by just not forwarding any ports. The downside is no one could connect to you (sometimes desirable) and you could not remotely administer your system. ? > > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > ________________________________ > Date: Wed, 24 Sep 2014 20:52:22 -0500 > From: lorentedford at gmail.com > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Security Issues > > Hey its Loren here again... > > Was curious what everyone found was the most substantial security risk with a Acid installation connected too two repeaters.. The sip.conf was deleted from the asterisks folder..? Noticed a strange node connection that didn?t match all stars normal node numbers 3101702 also found some thing with x.allstarlink.org in it anybody know what this is?? Anyway my linode server has been under constant attack from China they keep wanting to ssh into the server we had to drastically beef up things on the server such as changing the whole root user issue and moving to another port number etc.. Any thoughts ideas did i just become victum of a Sip attack too besides 19 ddos attacks this week already and over a million failed ssh attempts into my person linode server... > > > Loren Tedford (KC9ZHV)? > Email:?lorentedford at gmail.com > > http://www.lorentedford.com > http://www.Ltcraft.net > http://www.richlandcountycomputers.com > http://kc9zhv.lorentedford.com > > > _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. From mike.lussier at gmail.com Thu Sep 25 12:38:49 2014 From: mike.lussier at gmail.com (Mike Lussier) Date: Thu, 25 Sep 2014 08:38:49 -0400 Subject: [App_rpt-users] Changing the time on the BBB Message-ID: Greeting all, I have been testing a time announcement script and in order to see how it worked around the time of midnight I have needed to change the time on the BBB. I play the file through the radio and it works. I used this command # date -s "23 SEP 2014 23:55:00" Then I type date and verify the proper day and time. I run the same time script again and it doesn't work. I boot the BBB and the time is back to current and the script works. Any thoughts ?? -- *"We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan* -------------- next part -------------- An HTML attachment was scrubbed... URL: From email at jonbyrne.com Thu Sep 25 14:06:17 2014 From: email at jonbyrne.com (Jon Byrne) Date: Thu, 25 Sep 2014 15:06:17 +0100 Subject: [App_rpt-users] Security Issues In-Reply-To: <20140925074343.526E5E3C0039@ohnosec.org> References: <20140925074343.526E5E3C0039@ohnosec.org> Message-ID: Hi Loren, I guess you are running your Allstar node on a Virtual server, I do the same and have found bouts of activity from Chinese IP Addresses and other countries. Mostly SIP attempts, but also SSH. If you do not use SIP then unload it and set your IPTABLES to block that port. As for the SSH, this is will probably not be a targeted attack more that they are targeting the block of IP Addresses yours is in. If you have specific IP Addresses you connect to then you can lock connections to those IP's, plus install the fail2ban as mentioned and ensure there is a secure password and you should be ok. You could also enable PORTKNOCKING http://en.wikipedia.org/wiki/Port_knocking As for the 3101702 connection, is that no an Echolink node? http://ns2.s13avahost.net/repeaters/echolink/node_status.php?node=CX4BBH#sthash.n00kxN55.32DNtjrl.dpbs Hope that helps. Jon 2E0RFU ------------ Jon Byrne email at jonbyrne.com On 25 September 2014 08:43, Ken Boyle wrote: > You could also install fail2ban. By default it allows three failed > password attempts. Than temporarily bans the IP address. > > On Sep 24, 2014 10:43 PM, Doug Crompton wrote: > > > > I assume you have the linux box behind a router? If so why would you > have sip even routed to your linux box if you are not using it? Routers > make good firewalls. The only thing you should have routed is 4569 (udp) > and 222 (tcp) neither have to be routed. 4569 would only need to be > routed if you wanted to accept incoming connections. Outgoing would work > fine without it. 222 would only be needed for administration. > > > > From what you are saying you obviously must not have a front-end (router > firewall etc.) on your system . It sounds like you are just hanging on the > raw Internet!! Some people go the easy route and put thhings in the DMZ of > their routers which does open them up to the world. I went into an Allstar > system this week to help with setup and I immediately knew it was on the > DMZ. In the Asterisk client I was getting sip messages left and right. I > unloaded the sip module and they went away. Not the right way to do it > though as it should not be on dmz to begin with. Simply not having a > sip.conf file does not prevent sip traffic!!! > > > > Assuming you have a router there should be no need to disable sip as it > is never going to get to your box unless you port forward it there. It > would be a good idea thought to not load the code for it if you are not > using it. A noload=chan_sip.so in modules.conf would take care of that. > > > > Most good routers also allow you to specify specific or blocks of IP > addresses to disallow. If there is a specific foreign block, say in China > you can identify you could probably block it. > > > > So the bottom line is you could make your linux system tottally > unavailable to the outside world by just not forwarding any ports. The > downside is no one could connect to you (sometimes desirable) and you could > not remotely administer your system. > > > > > > 73 Doug > > WA3DSP > > http://www.crompton.com/hamradio > > > > > > ________________________________ > > Date: Wed, 24 Sep 2014 20:52:22 -0500 > > From: lorentedford at gmail.com > > To: app_rpt-users at ohnosec.org > > Subject: [App_rpt-users] Security Issues > > > > Hey its Loren here again... > > > > Was curious what everyone found was the most substantial security risk > with a Acid installation connected too two repeaters.. The sip.conf was > deleted from the asterisks folder.. Noticed a strange node connection that > didn?t match all stars normal node numbers 3101702 also found some thing > with x.allstarlink.org in it anybody know what this is?? Anyway my linode > server has been under constant attack from China they keep wanting to ssh > into the server we had to drastically beef up things on the server such as > changing the whole root user issue and moving to another port number etc.. > Any thoughts ideas did i just become victum of a Sip attack too besides 19 > ddos attacks this week already and over a million failed ssh attempts into > my person linode server... > > > > > > Loren Tedford (KC9ZHV) > > Email: lorentedford at gmail.com > > > > http://www.lorentedford.com > > http://www.Ltcraft.net > > http://www.richlandcountycomputers.com > > http://kc9zhv.lorentedford.com > > > > > > _______________________________________________ App_rpt-users mailing > list App_rpt-users at 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 at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From k5tra at austin.rr.com Thu Sep 25 14:35:14 2014 From: k5tra at austin.rr.com (k5tra) Date: Thu, 25 Sep 2014 09:35:14 -0500 Subject: [App_rpt-users] Changing the time on the BBB Message-ID: <007e01cfd8cd$ebaf4020$c30dc060$@rr.com> Mike, use the time/date control function: timedatectl type: timedatectl (for time and date info) type: timedatectl set-time "2012-10-30 18:17:16" ( to set date and time) TIMEZONE setting: timedatectl set-timezone yourzone/subzone Example: timedatectl set-timezone America/Chicago Tom / K5TRA -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike at midnighteng.com Thu Sep 25 15:06:13 2014 From: mike at midnighteng.com (mike at midnighteng.com) Date: Thu, 25 Sep 2014 08:06:13 -0700 Subject: [App_rpt-users] =?utf-8?q?NEW__Security_Issues?= Message-ID: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net> An HTML attachment was scrubbed... URL: From aprs at ka3nam.com Thu Sep 25 15:16:12 2014 From: aprs at ka3nam.com (Joe Bennett) Date: Thu, 25 Sep 2014 10:16:12 -0500 Subject: [App_rpt-users] Security Issues In-Reply-To: References: <20140925074343.526E5E3C0039@ohnosec.org> Message-ID: <542431BC.6010708@ka3nam.com> I guess I'm worried about some of the 'security' comments being shared here... First of all, if there is a service that is not used, it should be disabled. Firewall or no firewall... It's somewhat like locking the doors of your car, but leaving the convertible top down... Second, while fail2ban would stop the potential 'hacker' from potentially reaching the service or application itself, the incoming packet/ frame still has to be processed to find out if it should be banned, dropped or allowed... So a DoS or DDos attack is not squelched... A couple of things to recommend is that you use some sort of two-factor authentication on your SSH users. Google auth is free and works well... Find yourself a password generator and make strong passwords (like 32 characters)... Disable any service that is not critical for the operation of the intended use... I recommend all of these, and best of all, ALL of this can be done for FREE! Installation and setup can readily be found online... -Joe KA3NAM On 9/25/2014 9:06 AM, Jon Byrne wrote: > Hi Loren, > > I guess you are running your Allstar node on a Virtual server, I do > the same and have found bouts of activity from Chinese IP Addresses > and other countries. Mostly SIP attempts, but also SSH. > > If you do not use SIP then unload it and set your IPTABLES to block > that port. > > As for the SSH, this is will probably not be a targeted attack more > that they are targeting the block of IP Addresses yours is in. If you > have specific IP Addresses you connect to then you can lock > connections to those IP's, plus install the fail2ban as mentioned and > ensure there is a secure password and you should be ok. You could also > enable PORTKNOCKING http://en.wikipedia.org/wiki/Port_knocking > > As for the 3101702 connection, is that no an Echolink node? > > http://ns2.s13avahost.net/repeaters/echolink/node_status.php?node=CX4BBH#sthash.n00kxN55.32DNtjrl.dpbs > > Hope that helps. > > Jon > 2E0RFU > > > > ------------ > Jon Byrne > email at jonbyrne.com > > On 25 September 2014 08:43, Ken Boyle > wrote: > > You could also install fail2ban. By default it allows three failed > password attempts. Than temporarily bans the IP address. > > On Sep 24, 2014 10:43 PM, Doug Crompton > wrote: > > > > I assume you have the linux box behind a router? If so why would > you have sip even routed to your linux box if you are not using > it? Routers make good firewalls. The only thing you should have > routed is 4569 (udp) and 222 (tcp) neither have to be routed. > 4569 would only need to be routed if you wanted to accept incoming > connections. Outgoing would work fine without it. 222 would only > be needed for administration. > > > > From what you are saying you obviously must not have a front-end > (router firewall etc.) on your system . It sounds like you are > just hanging on the raw Internet!! Some people go the easy route > and put thhings in the DMZ of their routers which does open them > up to the world. I went into an Allstar system this week to help > with setup and I immediately knew it was on the DMZ. In the > Asterisk client I was getting sip messages left and right. I > unloaded the sip module and they went away. Not the right way to > do it though as it should not be on dmz to begin with. Simply not > having a sip.conf file does not prevent sip traffic!!! > > > > Assuming you have a router there should be no need to disable > sip as it is never going to get to your box unless you port > forward it there. It would be a good idea thought to not load the > code for it if you are not using it. A noload=chan_sip.so in > modules.conf would take care of that. > > > > Most good routers also allow you to specify specific or blocks > of IP addresses to disallow. If there is a specific foreign block, > say in China you can identify you could probably block it. > > > > So the bottom line is you could make your linux system tottally > unavailable to the outside world by just not forwarding any ports. > The downside is no one could connect to you (sometimes desirable) > and you could not remotely administer your system. > > > > > > 73 Doug > > WA3DSP > > http://www.crompton.com/hamradio > > > > > > ________________________________ > > Date: Wed, 24 Sep 2014 20:52:22 -0500 > > From: lorentedford at gmail.com > > To: app_rpt-users at ohnosec.org > > Subject: [App_rpt-users] Security Issues > > > > Hey its Loren here again... > > > > Was curious what everyone found was the most substantial > security risk with a Acid installation connected too two > repeaters.. The sip.conf was deleted from the asterisks folder.. > Noticed a strange node connection that didn?t match all stars > normal node numbers 3101702 also found some thing with > x.allstarlink.org in it anybody know > what this is?? Anyway my linode server has been under constant > attack from China they keep wanting to ssh into the server we had > to drastically beef up things on the server such as changing the > whole root user issue and moving to another port number etc.. Any > thoughts ideas did i just become victum of a Sip attack too > besides 19 ddos attacks this week already and over a million > failed ssh attempts into my person linode server... > > > > > > Loren Tedford (KC9ZHV) > > Email: lorentedford at gmail.com > > > > http://www.lorentedford.com > > http://www.Ltcraft.net > > http://www.richlandcountycomputers.com > > http://kc9zhv.lorentedford.com > > > > > > _______________________________________________ App_rpt-users > mailing list App_rpt-users at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kk6ecm at gmail.com Thu Sep 25 16:01:46 2014 From: kk6ecm at gmail.com (Bob) Date: Thu, 25 Sep 2014 09:01:46 -0700 Subject: [App_rpt-users] NEW Security Issues In-Reply-To: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net> References: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net> Message-ID: I'm running the latest ACID build, and ran the tests recommended by http://www.theregister.co.uk/2014/09/24/bash_shell_vuln/ to see if it is vulnerable. The ACID build passed both tests... the bug was not detected. See also, https://securityblog.redhat.com/2014/09/24/bash-specially-crafted-environmen t-variables-code-injection-attack/ This does not mean my routers are safe... still an open question for me. Bob kk6ecm _____ From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of mike at midnighteng.com Sent: Thursday, September 25, 2014 8:06 AM To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] NEW Security Issues The increase in recent hack attempts are the result of the resent knowlage of a fundamental bug in bash. It was not a big deal till someone published the flaw before some patches could be issued. Some folks set-ups are vulnerable. If you run HTTP, you certainly are. Just a FYI... SHELLSHOCK - this is bigger and older than heartbleed. It is a very big deal for "all" linux systems running http. http://seclists.org/oss-sec/2014/q3/650 to check your version of bash, type cd /bin bash --version our acid installs should be at 3.2 Remote ssh devices are possibly at risk. Current patches may not be entirely effective. Much more to be known about this. google shellshock for more info. ...mike/kb8jnm -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Thu Sep 25 16:04:00 2014 From: doug at crompton.com (Doug Crompton) Date: Thu, 25 Sep 2014 12:04:00 -0400 Subject: [App_rpt-users] Security Issues In-Reply-To: References: , , Message-ID: Loren, You did not explain why the allstar server has to be on DMZ? If there are other ports you need forwarded echolink, irlp, etc. to that computer you can do that. It would be much better to take the time and get the proper ports working then to have it open to the world. DMZ is OK for testing but not continuous use. You can certainly add protection to the linux box in the form of firewall, PW protection etc. but the best place to do it is at the source in the router. Why make it complicated!! The BeagleBone Black Allstar does have a pre-configured firewall that can be implemented easily in a situation where you might need it. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Thu, 25 Sep 2014 08:58:58 -0500 Subject: Re: [App_rpt-users] Security Issues From: lorentedford at gmail.com To: doug at crompton.com Doug We are using a ARRIS/Motorola SBG6580 SURFboard DOCSIS 3.0 Cable Modem and WiFi-N Router. This unit is DMZ to our Allstar box for a few purposes one being that the node is also being utilized for more that just repeater functions.. 2nd we have changed our port for ssh for security purposes first off just in the event we get attacked with a bunch of ssh hackers like my Linode server was under the past 3 weeks... We keep getting Chinese Ips trying to hack access to our public servers... Anyway back to the point.. We didnt realize that the server over all is open so.. If this is the case isnt there a firewall built into the acid distro? if not would it be easier for us to throw like Debian like what i have on my other servers that I use and still be capable of running allstar setup with both repeaters.. Lots of questions here i know.. But if the software cant handle its own firewall functions I need to look at a more long term solutions. I at least figured it had Iptables in it unless i looked in the wrong place.. also in the Moduels.conf ; ; Asterisk configuration file ; ; Module Loader configuration file ; [modules] autoload=yes noload=chan_oss.so noload=chan_alsa.so noload=chan_phone.so noload=chan_sip.so [global] I really like remoting the system do it all the time from work using ssh via my phone when making adjustments to my stuff.. Thanks so much for getting back to me so quickly and let me know if there is anything i did wrong or any other suggestions based on this.. I am also using the Echolink.conf file for now it will one day be moved to the 2 meter repeater once we get our duplexer problem fixed been a rough couple of weeks from everything to unauthorized access attempts to damaged product during shipping gotta love UPS thanks again 73's Loren~ Loren Tedford (KC9ZHV) Email: lorentedford at gmail.com Email: lorentedford at live.comEmail: lorentedford at aol.comEmail: LorenCS at Ltcraft.netEmail: lorentedford at yahoo.comEmail: loren at lorentedford.com Email: loren at richlandcountycomputers.comPhone: 618-553-0806http://www.lorentedford.com http://www.Ltcraft.nethttp://www.richlandcountycomputers.comhttp://kc9zhv.lorentedford.com On Wed, Sep 24, 2014 at 9:43 PM, Doug Crompton wrote: I assume you have the linux box behind a router? If so why would you have sip even routed to your linux box if you are not using it? Routers make good firewalls. The only thing you should have routed is 4569 (udp) and 222 (tcp) neither have to be routed. 4569 would only need to be routed if you wanted to accept incoming connections. Outgoing would work fine without it. 222 would only be needed for administration. >From what you are saying you obviously must not have a front-end (router firewall etc.) on your system . It sounds like you are just hanging on the raw Internet!! Some people go the easy route and put thhings in the DMZ of their routers which does open them up to the world. I went into an Allstar system this week to help with setup and I immediately knew it was on the DMZ. In the Asterisk client I was getting sip messages left and right. I unloaded the sip module and they went away. Not the right way to do it though as it should not be on dmz to begin with. Simply not having a sip.conf file does not prevent sip traffic!!! Assuming you have a router there should be no need to disable sip as it is never going to get to your box unless you port forward it there. It would be a good idea thought to not load the code for it if you are not using it. A noload=chan_sip.so in modules.conf would take care of that. Most good routers also allow you to specify specific or blocks of IP addresses to disallow. If there is a specific foreign block, say in China you can identify you could probably block it. So the bottom line is you could make your linux system tottally unavailable to the outside world by just not forwarding any ports. The downside is no one could connect to you (sometimes desirable) and you could not remotely administer your system. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Wed, 24 Sep 2014 20:52:22 -0500 From: lorentedford at gmail.com To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Security Issues Hey its Loren here again... Was curious what everyone found was the most substantial security risk with a Acid installation connected too two repeaters.. The sip.conf was deleted from the asterisks folder.. Noticed a strange node connection that didn?t match all stars normal node numbers 3101702 also found some thing with x.allstarlink.org in it anybody know what this is?? Anyway my linode server has been under constant attack from China they keep wanting to ssh into the server we had to drastically beef up things on the server such as changing the whole root user issue and moving to another port number etc.. Any thoughts ideas did i just become victum of a Sip attack too besides 19 ddos attacks this week already and over a million failed ssh attempts into my person linode server... Loren Tedford (KC9ZHV) Email: lorentedford at gmail.com http://www.lorentedford.com http://www.Ltcraft.nethttp://www.richlandcountycomputers.comhttp://kc9zhv.lorentedford.com _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wb3awj at comcast.net Thu Sep 25 16:23:41 2014 From: wb3awj at comcast.net (Robert A. Poff WB3AWJ) Date: Thu, 25 Sep 2014 16:23:41 +0000 (UTC) Subject: [App_rpt-users] Security Issues In-Reply-To: <542431BC.6010708@ka3nam.com> References: <20140925074343.526E5E3C0039@ohnosec.org> <542431BC.6010708@ka3nam.com> Message-ID: <1467891142.30154437.1411662221962.JavaMail.root@comcast.net> And of course, simple things like: Don't allow the root user to login via ssh. Hey, doing the su/sudo thing from a different login account doesn't take all the much time. Change the ssh port to something oddball. I've even stopped using 222 as it's somewhat common. When setting a password, if it tells you it's in the dictionary, use something else. No matter how "cool" or "easy" it is. At the very least, close off ALL the normal SIP ports. If you MUST use SIP for some god forsaken reason, move it to oddball ports. Consider moving your IAX port to something non-standard. Even with a router with appropriate security, I've considered putting up an RPi as a site SSH gateway. So that the Asterisk boxes are only exposed to the outside world on the IAX port. Forward whatever port I'm using for SSH to the RPi, log into it, and from there to the other machines at the site. Might even be a convenient place to run AllMon.... Why do I say all this..... I violated all of those suggestions due to over confidence, and laziness. It took them several years, but they got in. At first "all" they did was disable cron, and later remove it. Further on, they changed the root password. Still not sure what they were up to. They did nothing to Asterisk. When building the new machine, I took better precautions. In the long view... it's kind of like what a cop told us when he came to investigate a break in at our club site years ago. "You can't keep them out. So do all you can to slow them down.... Robert A. Poff Loganville, PA. 1983 Hunter 34 Havre de Grace, MD "Lieutenant, target the offending power boat and launch photon torpedoes" -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Thu Sep 25 16:27:42 2014 From: doug at crompton.com (Doug Crompton) Date: Thu, 25 Sep 2014 12:27:42 -0400 Subject: [App_rpt-users] NEW Security Issues In-Reply-To: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net> References: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net> Message-ID: Information on Centos Bash update - http://centosnow.blogspot.com/2014/09/critical-bash-updates-for-centos-5.html 73 Doug WA3DSP http://www.crompton.com/hamradio From: mike at midnighteng.com To: app_rpt-users at ohnosec.org Date: Thu, 25 Sep 2014 08:06:13 -0700 Subject: [App_rpt-users] NEW Security Issues The increase in recent hack attempts are the result of the resent knowlage of a fundamental bug in bash.It was not a big deal till someone published the flaw before some patches could be issued. Some folks set-ups are vulnerable. If you run HTTP, you certainly are. Just a FYI... SHELLSHOCK - this is bigger and older than heartbleed. It is a very big deal for "all" linux systems running http. http://seclists.org/oss-sec/2014/q3/650 to check your version of bash, type cd /binbash --version our acid installs should be at 3.2 Remote ssh devices are possibly at risk.Current patches may not be entirely effective.Much more to be known about this. google shellshock for more info. ...mike/kb8jnm _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike.lussier at gmail.com Thu Sep 25 16:55:30 2014 From: mike.lussier at gmail.com (Mike Lussier) Date: Thu, 25 Sep 2014 12:55:30 -0400 Subject: [App_rpt-users] Subject: Changing the time on the BBB Message-ID: Thank you Tom, I will try that this evening -- *"We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan* -------------- next part -------------- An HTML attachment was scrubbed... URL: From srice3 at cfl.rr.com Thu Sep 25 16:57:25 2014 From: srice3 at cfl.rr.com (The Rices) Date: Thu, 25 Sep 2014 12:57:25 -0400 Subject: [App_rpt-users] NEW Security Issues In-Reply-To: References: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net> Message-ID: <8AD4C7060BDF4BB1AD56D1964E4BBA2F@AdminPC> Thanks, Did the update as I am sure others will as well. Steve N4YZA From: Doug Crompton Sent: Thursday, September 25, 2014 12:27 PM To: mike at midnighteng.com Cc: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] NEW Security Issues Information on Centos Bash update - http://centosnow.blogspot.com/2014/09/critical-bash-updates-for-centos-5.html 73 Doug WA3DSP http://www.crompton.com/hamradio -------------------------------------------------------------------------------- From: mike at midnighteng.com To: app_rpt-users at ohnosec.org Date: Thu, 25 Sep 2014 08:06:13 -0700 Subject: [App_rpt-users] NEW Security Issues The increase in recent hack attempts are the result of the resent knowlage of a fundamental bug in bash. It was not a big deal till someone published the flaw before some patches could be issued. Some folks set-ups are vulnerable. If you run HTTP, you certainly are. Just a FYI... SHELLSHOCK - this is bigger and older than heartbleed. It is a very big deal for "all" linux systems running http. http://seclists.org/oss-sec/2014/q3/650 to check your version of bash, type cd /bin bash --version our acid installs should be at 3.2 Remote ssh devices are possibly at risk. Current patches may not be entirely effective. Much more to be known about this. google shellshock for more info. ...mike/kb8jnm _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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. -------------------------------------------------------------------------------- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4765 / Virus Database: 4025/8270 - Release Date: 09/25/14 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vencl at att.net Thu Sep 25 17:05:51 2014 From: vencl at att.net (Lu Vencl) Date: Thu, 25 Sep 2014 13:05:51 -0400 Subject: [App_rpt-users] RXDELAY in XIPAR In-Reply-To: <54206CBD.5080306@kuggie.com> References: <156701cfd65e$8ef08130$acd18390$@att.net> <6B4EB452-858E-491C-B07A-B912106F9374@mac.com> <46719A95-463D-4B06-B7F6-6CDEB348E7FF@att.net> <54206CBD.5080306@kuggie.com> Message-ID: <03AFA1E5-FEBC-41C0-9FD7-0ABB3D4AEBF7@att.net> Tried this but there was no effect. I placed it in URD.conf I assume that is correct? Lu Vencl > On Sep 22, 2014, at 2:38 PM, Kevin Custer wrote: > > I'd have to dig a bit, but I believe this setting does not work as intended in XIPAR. Please stand by..... > > I'm sorry to have kept you waiting. > > In XIPAR it's txrxdelay= 20 ms intervals. > > Kevin > > > >> On 9/22/2014 10:07 AM, Lu Vencl wrote: >> Just made it long to test. But not effective. Probably only need 150 ms. >> >> Lu Vencl >> >> On Sep 22, 2014, at 9:46 AM, Tim Sawyer wrote: >> >>> Really? You need a 3 second delay? >>> -- >>> Tim WD6AWP >>> >>>> On Sep 22, 2014, at 5:13 AM, Lu Vencl wrote: >>>> >>>> I have a XIPAR node that needs a little support with pulseback removal. Never had to utilize this before, but when looking in URD.conf, I don?t see the rxdelay= parameter like I do on ACID builds. I went ahead and inserted the command into the file, but there does not seem to be any action. >>>> Can someone confirm the parameter and placement? >>>> Here is my example: >>>> [usb] >>>> >>>> hdwtype=0 ; 0=std,1=dev >>>> eeprom=0 ; unless you have a cable w/eeprom >>>> duplex=0 ; 0=simplex, 1=duplex >>>> invertptt=0 >>>> ;minsigproc=0 ; minimal signal processing >>>> ;sendvoter=0 ; 0=default, no voter rssi, 1=enable voter rssi >>>> >>>> carrierfrom=usbinvert ; no,usb,usbinvert,dsp,vox >>>> ctcssfrom=no ; no,usb,dsp >>>> rxondelay=3000 ; Gets rid of the pulseback problem >>>> ;rxboost=1 ; rx input boost of 20dB >>>> rxboost=0 ; no boost >>>> rxdemod=flat ; no,speaker,flat >>>> txprelim=0 ; 1 = pre-emphasize and limit >>>> >>>> txmixa=voice ; no,voice,tone,composite >>>> txmixb=tone ; no,voice,tone,composite,auxvoice >>>> >>>> ;txctcssdefault=77.0 >>>> ;rxctcssfreqs=77.0; >>>> ;txctcssfreqs=77.0; >>>> txtoctype=notone; >>>> >>>> rxsquelchdelay=900 ; delayline in ms carrier squelch tail eliminator >>>> rxnoisefiltype=0 ; 0 for +/-5KHz, 2 for +/-2.5KHz systems >>>> >>>> >>>> Lu, >>>> KA4EPS >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at 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 at 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. >> >> >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2014.0.4765 / Virus Database: 4025/8255 - Release Date: 09/22/14 >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Thu Sep 25 18:38:10 2014 From: doug at crompton.com (Doug Crompton) Date: Thu, 25 Sep 2014 14:38:10 -0400 Subject: [App_rpt-users] NEW Security Issues In-Reply-To: References: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net>, Message-ID: Sorry I did not qualify that. The way to update centos is yum update bash The current update is: Updated: bash.i386 0:3.2-33.el5.1 This should not require any recompiles. If you have any current bash jobs running you would have to stop and restart them to use the new code or just reboot. 73 Doug WA3DSP http://www.crompton.com/hamradio From: doug at crompton.com To: mike at midnighteng.com Date: Thu, 25 Sep 2014 12:27:42 -0400 CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] NEW Security Issues Information on Centos Bash update - http://centosnow.blogspot.com/2014/09/critical-bash-updates-for-centos-5.html 73 Doug WA3DSP http://www.crompton.com/hamradio From: mike at midnighteng.com To: app_rpt-users at ohnosec.org Date: Thu, 25 Sep 2014 08:06:13 -0700 Subject: [App_rpt-users] NEW Security Issues The increase in recent hack attempts are the result of the resent knowlage of a fundamental bug in bash.It was not a big deal till someone published the flaw before some patches could be issued. Some folks set-ups are vulnerable. If you run HTTP, you certainly are. Just a FYI... SHELLSHOCK - this is bigger and older than heartbleed. It is a very big deal for "all" linux systems running http. http://seclists.org/oss-sec/2014/q3/650 to check your version of bash, type cd /binbash --version our acid installs should be at 3.2 Remote ssh devices are possibly at risk.Current patches may not be entirely effective.Much more to be known about this. google shellshock for more info. ...mike/kb8jnm _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kk6ecm at gmail.com Thu Sep 25 20:02:48 2014 From: kk6ecm at gmail.com (Bob) Date: Thu, 25 Sep 2014 13:02:48 -0700 Subject: [App_rpt-users] NEW Security Issues In-Reply-To: References: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net>, Message-ID: I performed the yum update... killed asterisk... lots of errors, repeater down. looks like I should have just updated bash (sigh!) need to rebuild ACID unless there is a way to "undo" the yum update. (sigh!) _____ From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Doug Crompton Sent: Thursday, September 25, 2014 11:38 AM To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] NEW Security Issues Sorry I did not qualify that. The way to update centos is yum update bash The current update is: Updated: bash.i386 0:3.2-33.el5.1 This should not require any recompiles. If you have any current bash jobs running you would have to stop and restart them to use the new code or just reboot. 73 Doug WA3DSP http://www.crompton.com/hamradio _____ From: doug at crompton.com To: mike at midnighteng.com Date: Thu, 25 Sep 2014 12:27:42 -0400 CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] NEW Security Issues Information on Centos Bash update - http://centosnow.blogspot.com/2014/09/critical-bash-updates-for-centos-5.htm l 73 Doug WA3DSP http://www.crompton.com/hamradio _____ From: mike at midnighteng.com To: app_rpt-users at ohnosec.org Date: Thu, 25 Sep 2014 08:06:13 -0700 Subject: [App_rpt-users] NEW Security Issues The increase in recent hack attempts are the result of the resent knowlage of a fundamental bug in bash. It was not a big deal till someone published the flaw before some patches could be issued. Some folks set-ups are vulnerable. If you run HTTP, you certainly are. Just a FYI... SHELLSHOCK - this is bigger and older than heartbleed. It is a very big deal for "all" linux systems running http. http://seclists.org/oss-sec/2014/q3/650 to check your version of bash, type cd /bin bash --version our acid installs should be at 3.2 Remote ssh devices are possibly at risk. Current patches may not be entirely effective. Much more to be known about this. google shellshock for more info. ...mike/kb8jnm _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kb4fxc at inttek.net Thu Sep 25 20:29:30 2014 From: kb4fxc at inttek.net (David McGough) Date: Thu, 25 Sep 2014 16:29:30 -0400 (EDT) Subject: [App_rpt-users] =?utf-8?q?NEW__Security_Issues?= In-Reply-To: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net> Message-ID: Hi Everyone, I'm going to try to slow the panic here! WHY is this such a huge security concern for AllStar users???? The only remote attack vector that might be of concern is via the apache webserver. And, this is only a concern if you've got bash shell scripts in a publicly accessible cgi-bin directory. So, if you do have a vulnerable cgi-bin, just temporarily do a "chmod 700" on this directory and the problem is mitigated....Or, just stop the apache service entirely. This vulnerability isn't like HeartBleed from several months ago. Nor does it provide a means for privilege escalation. Am I missing something??? (I hope not! I've got over 100 servers with this vulnerability currently). So, slow down and -plan- this fix. Don't break your system due to an unneeded panic! 73, David KB4FXC On Thu, 25 Sep 2014 mike at midnighteng.com wrote: > > The increase in recent hack attempts are the result of the resent knowlage of a fundamental bug in bash. > It was not a big deal till someone published the flaw before some patches could be issued. > > Some folks set-ups are vulnerable. If you run HTTP, you certainly are. > > Just a FYI... > > SHELLSHOCK? - this is bigger and older than heartbleed. > > It is a very big deal for "all" linux systems running http. > > http://seclists.org/oss-sec/2014/q3/650??????? > > to check your version of bash, type > > cd /bin > bash --version > > our acid installs should be at 3.2 > Remote ssh devices are possibly at risk. > Current patches may not be entirely effective. > Much more to be known about this. > > google shellshock for more info. > > ...mike/kb8jnm > > > > From tim.sawyer at mac.com Thu Sep 25 20:41:35 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Thu, 25 Sep 2014 13:41:35 -0700 Subject: [App_rpt-users] NEW Security Issues In-Reply-To: References: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net> Message-ID: <947462C5-75A6-49BD-A5BE-92D584B6B3C5@mac.com> This should fix your update? http://docs.allstarlink.org/drupal/node/111 -- Tim :wq On Sep 25, 2014, at 1:02 PM, Bob wrote: > I performed the yum update... killed asterisk... lots of errors, repeater down. looks like I should have just updated bash (sigh!) need to rebuild ACID unless there is a way to ?undo? the yum update. (sigh!) > > From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Doug Crompton > Sent: Thursday, September 25, 2014 11:38 AM > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] NEW Security Issues > > Sorry I did not qualify that. The way to update centos is > > yum update bash > > The current update is: > > Updated: > bash.i386 0:3.2-33.el5.1 > > This should not require any recompiles. If you have any current bash jobs running you would have to stop and restart them to use the new code or just reboot. > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: doug at crompton.com > To: mike at midnighteng.com > Date: Thu, 25 Sep 2014 12:27:42 -0400 > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] NEW Security Issues > > Information on Centos Bash update - > > http://centosnow.blogspot.com/2014/09/critical-bash-updates-for-centos-5.html > > 73 Doug > WA3DSP > http://www.crompton.com/hamradio > > > From: mike at midnighteng.com > To: app_rpt-users at ohnosec.org > Date: Thu, 25 Sep 2014 08:06:13 -0700 > Subject: [App_rpt-users] NEW Security Issues > > > The increase in recent hack attempts are the result of the resent knowlage of a fundamental bug in bash. > It was not a big deal till someone published the flaw before some patches could be issued. > > Some folks set-ups are vulnerable. If you run HTTP, you certainly are. > > Just a FYI... > > SHELLSHOCK - this is bigger and older than heartbleed. > > It is a very big deal for "all" linux systems running http. > > http://seclists.org/oss-sec/2014/q3/650 > > to check your version of bash, type > > cd /bin > bash --version > > our acid installs should be at 3.2 > Remote ssh devices are possibly at risk. > Current patches may not be entirely effective. > Much more to be known about this. > > google shellshock for more info. > > ...mike/kb8jnm > > > > _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kuggie at kuggie.com Thu Sep 25 20:58:07 2014 From: kuggie at kuggie.com (Kevin Custer) Date: Thu, 25 Sep 2014 16:58:07 -0400 Subject: [App_rpt-users] TXRXDELAY in XIPAR In-Reply-To: <03AFA1E5-FEBC-41C0-9FD7-0ABB3D4AEBF7@att.net> References: <156701cfd65e$8ef08130$acd18390$@att.net> <6B4EB452-858E-491C-B07A-B912106F9374@mac.com> <46719A95-463D-4B06-B7F6-6CDEB348E7FF@att.net> <54206CBD.5080306@kuggie.com> <03AFA1E5-FEBC-41C0-9FD7-0ABB3D4AEBF7@att.net> Message-ID: <542481DF.3050106@kuggie.com> On 9/25/2014 1:05 PM, Lu Vencl wrote: > Tried this but there was no effect. I placed it in URD.conf I assume > that is correct? Correct. You did a kill and a start? -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Thu Sep 25 21:15:47 2014 From: doug at crompton.com (Doug Crompton) Date: Thu, 25 Sep 2014 17:15:47 -0400 Subject: [App_rpt-users] NEW Security Issues In-Reply-To: References: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net>, Message-ID: I totally agree. All this security talk you might think we were running national security servers. Human nature is sometimes so bizarre. People can be scared so easily and the media loves scaring people. But then sometimes it takes scare tactics to get someone to take action. Has anyone ever had an Allstar system compromised that was properly setup? The fix is easy. If you are running centos just do yum update bash The upcoming Beaglebone Black 1.2 release will have the fix. Ubuntu auto updated today. Other releases should have similar update paths. Run this script at the Linux prompt to test - env X="() { :;} ; echo busted" `which bash` -c "echo completed" If it returns busted then you have the problem. One caveat - the current fixes are preliminary and have not gone through extensive testing to you might want to check for updates again in a fews day or weeks. 73 Doug WA3DSP http://www.crompton.com/hamradio > Date: Thu, 25 Sep 2014 16:29:30 -0400 > From: kb4fxc at inttek.net > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] NEW Security Issues > > > Hi Everyone, > > I'm going to try to slow the panic here! WHY is this such a huge security > concern for AllStar users???? > > The only remote attack vector that might be of concern is via the apache > webserver. And, this is only a concern if you've got bash shell scripts in > a publicly accessible cgi-bin directory. So, if you do have a vulnerable > cgi-bin, just temporarily do a "chmod 700" on this directory and the > problem is mitigated....Or, just stop the apache service entirely. > > This vulnerability isn't like HeartBleed from several months ago. Nor does > it provide a means for privilege escalation. > > Am I missing something??? (I hope not! I've got over 100 servers with > this vulnerability currently). > > So, slow down and -plan- this fix. Don't break your system due to an > unneeded panic! > > > 73, David KB4FXC > > > > > > On Thu, 25 Sep 2014 mike at midnighteng.com wrote: > > > > > The increase in recent hack attempts are the result of the resent knowlage of a fundamental bug in bash. > > It was not a big deal till someone published the flaw before some patches could be issued. > > > > Some folks set-ups are vulnerable. If you run HTTP, you certainly are. > > > > Just a FYI... > > > > SHELLSHOCK - this is bigger and older than heartbleed. > > > > It is a very big deal for "all" linux systems running http. > > > > http://seclists.org/oss-sec/2014/q3/650 > > > > to check your version of bash, type > > > > cd /bin > > bash --version > > > > our acid installs should be at 3.2 > > Remote ssh devices are possibly at risk. > > Current patches may not be entirely effective. > > Much more to be known about this. > > > > google shellshock for more info. > > > > ...mike/kb8jnm > > > > > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From N1XBM at amsat.org Thu Sep 25 21:16:17 2014 From: N1XBM at amsat.org (Robert Newberry) Date: Thu, 25 Sep 2014 17:16:17 -0400 Subject: [App_rpt-users] NEW Security Issues In-Reply-To: References: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net> Message-ID: That's strange I followed the instructions here. http://centosnow.blogspot.com/2014/09/critical-bash-updates-for-centos-5.html?m=1 Updated no problem. Then Doug pointed out yum update bash. Just to be double sure I did that and it saw something like no update necessary. I just just got done taking on my repeater we had Zello, zoiper, and RF going it was a beautiful thing. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wb3awj at comcast.net Thu Sep 25 21:26:42 2014 From: wb3awj at comcast.net (Robert A. Poff WB3AWJ) Date: Thu, 25 Sep 2014 21:26:42 +0000 (UTC) Subject: [App_rpt-users] NEW Security Issues In-Reply-To: References: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net> Message-ID: <69151674.30425460.1411680402259.JavaMail.root@comcast.net> When I had SIP enabled and standard ports forwarded, many days I saw almost continuous attempts to register several thousand extensions at a time. As I said in my previous post,.... I cleaned my house and slapped myself on the wrists, after having completely lost access to the repeater. Login for root was enabled, and after a couple years, they brute forced their way in guessing the password. While the password wasn't "1234", it was in the dictionary. In many cases it doesn't mean going crazy, just examining your set up and correcting dumb stuff. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kenh at tsg-us.com Thu Sep 25 21:38:00 2014 From: kenh at tsg-us.com (Ken W4NOC) Date: Thu, 25 Sep 2014 17:38:00 -0400 Subject: [App_rpt-users] SSH Security Issues References: Message-ID: DMZ will invite SSH attacks and about every other known hack. Within a few days or a week they will zero in on your pubic IP. I know someone that inadvertently left their machine behind a DMZ and the SSH attack traffic was incredible. Pick an odd port for your SSH. I won't mention the ports we use on this reflector. That is what we did on several nodes and that stopped the SSH attacks. All of the hacks know to go after port 22 and they have long wised up to 222. So, you may wish to avoid 222 as your SSH port. As already mentioned, pick a really good password. Ken W4NOC > > Message: 3 > Date: Thu, 25 Sep 2014 10:16:12 -0500 > From: Joe Bennett > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Security Issues > Message-ID: <542431BC.6010708 at ka3nam.com> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > I guess I'm worried about some of the 'security' comments being shared > here... First of all, if there is a service that is not used, it should > be disabled. Firewall or no firewall... It's somewhat like locking the > doors of your car, but leaving the convertible top down... Second, while > fail2ban would stop the potential 'hacker' from potentially reaching the > service or application itself, the incoming packet/ frame still has to > be processed to find out if it should be banned, dropped or allowed... > So a DoS or DDos attack is not squelched... > > A couple of things to recommend is that you use some sort of two-factor > authentication on your SSH users. Google auth is free and works well... > Find yourself a password generator and make strong passwords (like 32 > characters)... Disable any service that is not critical for the > operation of the intended use... I recommend all of these, and best of > all, ALL of this can be done for FREE! Installation and setup can > readily be found online... > > > -Joe > KA3NAM > > > On 9/25/2014 9:06 AM, Jon Byrne wrote: >> Hi Loren, >> >> I guess you are running your Allstar node on a Virtual server, I do >> the same and have found bouts of activity from Chinese IP Addresses >> and other countries. Mostly SIP attempts, but also SSH. >> >> If you do not use SIP then unload it and set your IPTABLES to block >> that port. >> >> As for the SSH, this is will probably not be a targeted attack more >> that they are targeting the block of IP Addresses yours is in. If you >> have specific IP Addresses you connect to then you can lock >> connections to those IP's, plus install the fail2ban as mentioned and >> ensure there is a secure password and you should be ok. You could also >> enable PORTKNOCKING http://en.wikipedia.org/wiki/Port_knocking >> >> As for the 3101702 connection, is that no an Echolink node? >> >> http://ns2.s13avahost.net/repeaters/echolink/node_status.php?node=CX4BBH#sthash.n00kxN55.32DNtjrl.dpbs >> >> Hope that helps. >> >> Jon >> 2E0RFU >> >> >> >> ------------ >> Jon Byrne >> email at jonbyrne.com >> >> On 25 September 2014 08:43, Ken Boyle > > wrote: >> >> You could also install fail2ban. By default it allows three failed >> password attempts. Than temporarily bans the IP address. >> >> On Sep 24, 2014 10:43 PM, Doug Crompton > > wrote: >> > >> > I assume you have the linux box behind a router? If so why would >> you have sip even routed to your linux box if you are not using >> it? Routers make good firewalls. The only thing you should have >> routed is 4569 (udp) and 222 (tcp) neither have to be routed. >> 4569 would only need to be routed if you wanted to accept incoming >> connections. Outgoing would work fine without it. 222 would only >> be needed for administration. >> > >> > From what you are saying you obviously must not have a front-end >> (router firewall etc.) on your system . It sounds like you are >> just hanging on the raw Internet!! Some people go the easy route >> and put thhings in the DMZ of their routers which does open them >> up to the world. I went into an Allstar system this week to help >> with setup and I immediately knew it was on the DMZ. In the >> Asterisk client I was getting sip messages left and right. I >> unloaded the sip module and they went away. Not the right way to >> do it though as it should not be on dmz to begin with. Simply not >> having a sip.conf file does not prevent sip traffic!!! >> > >> > Assuming you have a router there should be no need to disable >> sip as it is never going to get to your box unless you port >> forward it there. It would be a good idea thought to not load the >> code for it if you are not using it. A noload=chan_sip.so in >> modules.conf would take care of that. >> > >> > Most good routers also allow you to specify specific or blocks >> of IP addresses to disallow. If there is a specific foreign block, >> say in China you can identify you could probably block it. >> > >> > So the bottom line is you could make your linux system tottally >> unavailable to the outside world by just not forwarding any ports. >> The downside is no one could connect to you (sometimes desirable) >> and you could not remotely administer your system. >> > >> > >> > 73 Doug >> > WA3DSP >> > http://www.crompton.com/hamradio >> > >> > >> > ________________________________ >> > Date: Wed, 24 Sep 2014 20:52:22 -0500 >> > From: lorentedford at gmail.com >> > To: app_rpt-users at ohnosec.org >> > Subject: [App_rpt-users] Security Issues >> > >> > Hey its Loren here again... >> > >> > Was curious what everyone found was the most substantial >> security risk with a Acid installation connected too two >> repeaters.. The sip.conf was deleted from the asterisks folder.. >> Noticed a strange node connection that didn?t match all stars >> normal node numbers 3101702 also found some thing with >> x.allstarlink.org in it anybody know >> what this is?? Anyway my linode server has been under constant >> attack from China they keep wanting to ssh into the server we had >> to drastically beef up things on the server such as changing the >> whole root user issue and moving to another port number etc.. Any >> thoughts ideas did i just become victum of a Sip attack too >> besides 19 ddos attacks this week already and over a million >> failed ssh attempts into my person linode server... >> > >> > >> > Loren Tedford (KC9ZHV) >> > Email: lorentedford at gmail.com >> > >> > http://www.lorentedford.com >> > http://www.Ltcraft.net >> > http://www.richlandcountycomputers.com >> > http://kc9zhv.lorentedford.com >> > >> > >> > _______________________________________________ App_rpt-users >> mailing list App_rpt-users at 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 at 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 at 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. > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > ------------------------------ > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > End of App_rpt-users Digest, Vol 67, Issue 71 > ********************************************* From kk6ecm at gmail.com Thu Sep 25 22:10:46 2014 From: kk6ecm at gmail.com (kk6ecm) Date: Thu, 25 Sep 2014 15:10:46 -0700 Subject: [App_rpt-users] NEW Security Issues In-Reply-To: <947462C5-75A6-49BD-A5BE-92D584B6B3C5@mac.com> References: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net> <947462C5-75A6-49BD-A5BE-92D584B6B3C5@mac.com> Message-ID: <171415F2-0289-46D6-A57E-1265B4DCA7A3@gmail.com> Cool. I'll give it a go before a reload. Whenever I do a server build, I take copious notes so I can duplicate all the steps,.. just time. Thanks much! Bob kk6ecm Sent from iPad > On Sep 25, 2014, at 1:41 PM, Tim Sawyer wrote: > > This should fix your update? > http://docs.allstarlink.org/drupal/node/111 > -- > Tim > :wq > >> On Sep 25, 2014, at 1:02 PM, Bob wrote: >> >> I performed the yum update... killed asterisk... lots of errors, repeater down. looks like I should have just updated bash (sigh!) need to rebuild ACID unless there is a way to ?undo? the yum update. (sigh!) >> >> From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Doug Crompton >> Sent: Thursday, September 25, 2014 11:38 AM >> To: app_rpt-users at ohnosec.org >> Subject: Re: [App_rpt-users] NEW Security Issues >> >> Sorry I did not qualify that. The way to update centos is >> >> yum update bash >> >> The current update is: >> >> Updated: >> bash.i386 0:3.2-33.el5.1 >> >> This should not require any recompiles. If you have any current bash jobs running you would have to stop and restart them to use the new code or just reboot. >> >> 73 Doug >> WA3DSP >> http://www.crompton.com/hamradio >> >> >> From: doug at crompton.com >> To: mike at midnighteng.com >> Date: Thu, 25 Sep 2014 12:27:42 -0400 >> CC: app_rpt-users at ohnosec.org >> Subject: Re: [App_rpt-users] NEW Security Issues >> >> Information on Centos Bash update - >> >> http://centosnow.blogspot.com/2014/09/critical-bash-updates-for-centos-5.html >> >> 73 Doug >> WA3DSP >> http://www.crompton.com/hamradio >> >> >> From: mike at midnighteng.com >> To: app_rpt-users at ohnosec.org >> Date: Thu, 25 Sep 2014 08:06:13 -0700 >> Subject: [App_rpt-users] NEW Security Issues >> >> >> The increase in recent hack attempts are the result of the resent knowlage of a fundamental bug in bash. >> It was not a big deal till someone published the flaw before some patches could be issued. >> >> Some folks set-ups are vulnerable. If you run HTTP, you certainly are. >> >> Just a FYI... >> >> SHELLSHOCK - this is bigger and older than heartbleed. >> >> It is a very big deal for "all" linux systems running http. >> >> http://seclists.org/oss-sec/2014/q3/650 >> >> to check your version of bash, type >> >> cd /bin >> bash --version >> >> our acid installs should be at 3.2 >> Remote ssh devices are possibly at risk. >> Current patches may not be entirely effective. >> Much more to be known about this. >> >> google shellshock for more info. >> >> ...mike/kb8jnm >> >> >> >> _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vencl at att.net Thu Sep 25 23:40:40 2014 From: vencl at att.net (Lu Vencl) Date: Thu, 25 Sep 2014 19:40:40 -0400 Subject: [App_rpt-users] TXRXDELAY in XIPAR In-Reply-To: <542481DF.3050106@kuggie.com> References: <156701cfd65e$8ef08130$acd18390$@att.net> <6B4EB452-858E-491C-B07A-B912106F9374@mac.com> <46719A95-463D-4B06-B7F6-6CDEB348E7FF@att.net> <54206CBD.5080306@kuggie.com> <03AFA1E5-FEBC-41C0-9FD7-0ABB3D4AEBF7@att.net> <542481DF.3050106@kuggie.com> Message-ID: <4C1089C6-1848-402E-AA0F-BAA7D71CE44D@att.net> I actually did a complete reboot. Lu Vencl > On Sep 25, 2014, at 4:58 PM, Kevin Custer wrote: > >> On 9/25/2014 1:05 PM, Lu Vencl wrote: >> Tried this but there was no effect. I placed it in URD.conf I assume that is correct? > > Correct. You did a kill and a start? > From kuggie at kuggie.com Fri Sep 26 01:35:06 2014 From: kuggie at kuggie.com (Kevin Custer) Date: Thu, 25 Sep 2014 21:35:06 -0400 Subject: [App_rpt-users] TXRXDELAY in XIPAR In-Reply-To: <4C1089C6-1848-402E-AA0F-BAA7D71CE44D@att.net> References: <156701cfd65e$8ef08130$acd18390$@att.net> <6B4EB452-858E-491C-B07A-B912106F9374@mac.com> <46719A95-463D-4B06-B7F6-6CDEB348E7FF@att.net> <54206CBD.5080306@kuggie.com> <03AFA1E5-FEBC-41C0-9FD7-0ABB3D4AEBF7@att.net> <542481DF.3050106@kuggie.com> <4C1089C6-1848-402E-AA0F-BAA7D71CE44D@att.net> Message-ID: <5424C2CA.60401@kuggie.com> On 9/25/2014 7:40 PM, Lu Vencl wrote: > I actually did a complete reboot. Not sure then... We have a few simplex nodes that were giving us problems and when Brian implemented this parameter it totally fixed the problem. Maybe Brian can comment? Kevin From tim.sawyer at mac.com Fri Sep 26 02:40:23 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Thu, 25 Sep 2014 19:40:23 -0700 Subject: [App_rpt-users] NEW Security Issues In-Reply-To: <1AF63C812EC545A9A4DA7FD4BD97BFB1@ThePykesHP> References: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net> <947462C5-75A6-49BD-A5BE-92D584B6B3C5@mac.com> <1AF63C812EC545A9A4DA7FD4BD97BFB1@ThePykesHP> Message-ID: <14AF1114-8DFC-4F9E-AEE4-DB2731C55450@mac.com> Agreed! And glad you are back on the air. -- Tim :wq On Sep 25, 2014, at 6:47 PM, Bob wrote: > Thanks again... worked as advertised. I?m still amazed at the genius behind this system. > > From: Tim Sawyer [mailto:tim.sawyer at mac.com] > Sent: Thursday, September 25, 2014 1:42 PM > To: Bob > Cc: Doug Crompton; app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] NEW Security Issues > > This should fix your update? > http://docs.allstarlink.org/drupal/node/111 > -- > Tim > :wq > > On Sep 25, 2014, at 1:02 PM, Bob wrote: > > > I performed the yum update... killed asterisk... lots of errors, repeater down. looks like I should have just updated bash (sigh!) need to rebuild ACID unless there is a way to ?undo? the yum update. (sigh!) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wayne at anywherehost.net Fri Sep 26 15:40:04 2014 From: wayne at anywherehost.net (Wayne) Date: Fri, 26 Sep 2014 08:40:04 -0700 Subject: [App_rpt-users] SSH Security Issues In-Reply-To: References: Message-ID: <3F3692C7C0BD489494A521FD177E6E74@desktop> I am a little late to this thread. As I've mentioned in the past I work for a web hosting business and we are all too familiar with SSH attacks. Years ago we allowed SSH to our customers and we were regularly rebuilding servers OS and attempting to restore customer data. It was maddening. We shut off all SSH except from specific IP's. That is easier than choosing a different port. Many/most hackers will do a port scan before a hack to see what's open. We use hardware firewalls and intelligent switches. As a general rule one should ALWAYS use a "stateful" firewall. This means that everything is off by default and one builds policies for each service including SSH. During this process one makes an exception allowance for a specific IP(s) or subnets. Keep the subnet small if you can. If you are trying to access from a dynamic IP consider using a discreet DNS provider. But never run DMZ. Always checks your logs and if you see IP's attempting access on any port that are not you or a twisted servant then blacklist the IP! You may also deploy a "honey pot" server whose job it is to be discovered before the real server. Ipconfig rules will let them in like the Roach Motel but not come out. More importantly is logs their IP that you are duty-bound that blacklist. -----Original Message----- From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Ken W4NOC Sent: Thursday, September 25, 2014 2:38 PM To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] SSH Security Issues DMZ will invite SSH attacks and about every other known hack. Within a few days or a week they will zero in on your pubic IP. I know someone that inadvertently left their machine behind a DMZ and the SSH attack traffic was incredible. Pick an odd port for your SSH. I won't mention the ports we use on this reflector. That is what we did on several nodes and that stopped the SSH attacks. All of the hacks know to go after port 22 and they have long wised up to 222. So, you may wish to avoid 222 as your SSH port. As already mentioned, pick a really good password. Ken W4NOC > > Message: 3 > Date: Thu, 25 Sep 2014 10:16:12 -0500 > From: Joe Bennett > To: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Security Issues > Message-ID: <542431BC.6010708 at ka3nam.com> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > I guess I'm worried about some of the 'security' comments being shared > here... First of all, if there is a service that is not used, it should > be disabled. Firewall or no firewall... It's somewhat like locking the > doors of your car, but leaving the convertible top down... Second, while > fail2ban would stop the potential 'hacker' from potentially reaching the > service or application itself, the incoming packet/ frame still has to > be processed to find out if it should be banned, dropped or allowed... > So a DoS or DDos attack is not squelched... > > A couple of things to recommend is that you use some sort of two-factor > authentication on your SSH users. Google auth is free and works well... > Find yourself a password generator and make strong passwords (like 32 > characters)... Disable any service that is not critical for the > operation of the intended use... I recommend all of these, and best of > all, ALL of this can be done for FREE! Installation and setup can > readily be found online... > > > -Joe > KA3NAM > > > On 9/25/2014 9:06 AM, Jon Byrne wrote: >> Hi Loren, >> >> I guess you are running your Allstar node on a Virtual server, I do >> the same and have found bouts of activity from Chinese IP Addresses >> and other countries. Mostly SIP attempts, but also SSH. >> >> If you do not use SIP then unload it and set your IPTABLES to block >> that port. >> >> As for the SSH, this is will probably not be a targeted attack more >> that they are targeting the block of IP Addresses yours is in. If you >> have specific IP Addresses you connect to then you can lock >> connections to those IP's, plus install the fail2ban as mentioned and >> ensure there is a secure password and you should be ok. You could also >> enable PORTKNOCKING http://en.wikipedia.org/wiki/Port_knocking >> >> As for the 3101702 connection, is that no an Echolink node? >> >> http://ns2.s13avahost.net/repeaters/echolink/node_status.php?node=CX4BBH#sth ash.n00kxN55.32DNtjrl.dpbs >> >> Hope that helps. >> >> Jon >> 2E0RFU >> >> >> >> ------------ >> Jon Byrne >> email at jonbyrne.com >> >> On 25 September 2014 08:43, Ken Boyle > > wrote: >> >> You could also install fail2ban. By default it allows three failed >> password attempts. Than temporarily bans the IP address. >> >> On Sep 24, 2014 10:43 PM, Doug Crompton > > wrote: >> > >> > I assume you have the linux box behind a router? If so why would >> you have sip even routed to your linux box if you are not using >> it? Routers make good firewalls. The only thing you should have >> routed is 4569 (udp) and 222 (tcp) neither have to be routed. >> 4569 would only need to be routed if you wanted to accept incoming >> connections. Outgoing would work fine without it. 222 would only >> be needed for administration. >> > >> > From what you are saying you obviously must not have a front-end >> (router firewall etc.) on your system . It sounds like you are >> just hanging on the raw Internet!! Some people go the easy route >> and put thhings in the DMZ of their routers which does open them >> up to the world. I went into an Allstar system this week to help >> with setup and I immediately knew it was on the DMZ. In the >> Asterisk client I was getting sip messages left and right. I >> unloaded the sip module and they went away. Not the right way to >> do it though as it should not be on dmz to begin with. Simply not >> having a sip.conf file does not prevent sip traffic!!! >> > >> > Assuming you have a router there should be no need to disable >> sip as it is never going to get to your box unless you port >> forward it there. It would be a good idea thought to not load the >> code for it if you are not using it. A noload=chan_sip.so in >> modules.conf would take care of that. >> > >> > Most good routers also allow you to specify specific or blocks >> of IP addresses to disallow. If there is a specific foreign block, >> say in China you can identify you could probably block it. >> > >> > So the bottom line is you could make your linux system tottally >> unavailable to the outside world by just not forwarding any ports. >> The downside is no one could connect to you (sometimes desirable) >> and you could not remotely administer your system. >> > >> > >> > 73 Doug >> > WA3DSP >> > http://www.crompton.com/hamradio >> > >> > >> > ________________________________ >> > Date: Wed, 24 Sep 2014 20:52:22 -0500 >> > From: lorentedford at gmail.com >> > To: app_rpt-users at ohnosec.org >> > Subject: [App_rpt-users] Security Issues >> > >> > Hey its Loren here again... >> > >> > Was curious what everyone found was the most substantial >> security risk with a Acid installation connected too two >> repeaters.. The sip.conf was deleted from the asterisks folder.. >> Noticed a strange node connection that didn?t match all stars >> normal node numbers 3101702 also found some thing with >> x.allstarlink.org in it anybody know >> what this is?? Anyway my linode server has been under constant >> attack from China they keep wanting to ssh into the server we had >> to drastically beef up things on the server such as changing the >> whole root user issue and moving to another port number etc.. Any >> thoughts ideas did i just become victum of a Sip attack too >> besides 19 ddos attacks this week already and over a million >> failed ssh attempts into my person linode server... >> > >> > >> > Loren Tedford (KC9ZHV) >> > Email: lorentedford at gmail.com >> > >> > http://www.lorentedford.com >> > http://www.Ltcraft.net >> > http://www.richlandcountycomputers.com >> > http://kc9zhv.lorentedford.com >> > >> > >> > _______________________________________________ App_rpt-users >> mailing list App_rpt-users at 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 at 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 at 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. > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > ------------------------------ > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > End of App_rpt-users Digest, Vol 67, Issue 71 > ********************************************* _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. From wayne at anywherehost.net Fri Sep 26 15:47:39 2014 From: wayne at anywherehost.net (Wayne) Date: Fri, 26 Sep 2014 08:47:39 -0700 Subject: [App_rpt-users] NEW Security Issues In-Reply-To: <171415F2-0289-46D6-A57E-1265B4DCA7A3@gmail.com> References: <20140925080613.71befee5dbd13c5325dd1a521b4e73ee.43a5124674.wbe@email06.secureserver.net><947462C5-75A6-49BD-A5BE-92D584B6B3C5@mac.com> <171415F2-0289-46D6-A57E-1265B4DCA7A3@gmail.com> Message-ID: Here is how you should check to see if you are vulnerable and odds are you ARE. ~# env x='() { :;}; echo vulnerable' bash -c "echo this is a test" If the system is vulnerable, the output is: vulnerable this is a test It is far easier to upgrade bash and all OS distros now have a patch. Wayne http://hamradiohost.net _____ From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of kk6ecm Sent: Thursday, September 25, 2014 3:11 PM To: Tim Sawyer Cc: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] NEW Security Issues Cool. I'll give it a go before a reload. Whenever I do a server build, I take copious notes so I can duplicate all the steps,.. just time. Thanks much! Bob kk6ecm Sent from iPad On Sep 25, 2014, at 1:41 PM, Tim Sawyer wrote: This should fix your update. http://docs.allstarlink.org/drupal/node/111 -- Tim :wq On Sep 25, 2014, at 1:02 PM, Bob wrote: I performed the yum update... killed asterisk... lots of errors, repeater down. looks like I should have just updated bash (sigh!) need to rebuild ACID unless there is a way to "undo" the yum update. (sigh!) _____ From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Doug Crompton Sent: Thursday, September 25, 2014 11:38 AM To: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] NEW Security Issues Sorry I did not qualify that. The way to update centos is yum update bash The current update is: Updated: bash.i386 0:3.2-33.el5.1 This should not require any recompiles. If you have any current bash jobs running you would have to stop and restart them to use the new code or just reboot. 73 Doug WA3DSP http://www.crompton.com/hamradio _____ From: doug at crompton.com To: mike at midnighteng.com Date: Thu, 25 Sep 2014 12:27:42 -0400 CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] NEW Security Issues Information on Centos Bash update - http://centosnow.blogspot.com/2014/09/critical-bash-updates-for-centos-5.htm l 73 Doug WA3DSP http://www.crompton.com/hamradio _____ From: mike at midnighteng.com To: app_rpt-users at ohnosec.org Date: Thu, 25 Sep 2014 08:06:13 -0700 Subject: [App_rpt-users] NEW Security Issues The increase in recent hack attempts are the result of the resent knowlage of a fundamental bug in bash. It was not a big deal till someone published the flaw before some patches could be issued. Some folks set-ups are vulnerable. If you run HTTP, you certainly are. Just a FYI... SHELLSHOCK - this is bigger and older than heartbleed. It is a very big deal for "all" linux systems running http. http://seclists.org/oss-sec/2014/q3/650 to check your version of bash, type cd /bin bash --version our acid installs should be at 3.2 Remote ssh devices are possibly at risk. Current patches may not be entirely effective. Much more to be known about this. google shellshock for more info. ...mike/kb8jnm _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kf7mbk at w7ara.net Fri Sep 26 15:50:51 2014 From: kf7mbk at w7ara.net (Mike M) Date: Fri, 26 Sep 2014 08:50:51 -0700 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: Message-ID: Resending since my initial post has been pending moderation for 2 days now and got no reply from the list owner email. I have modified an HT to bring out the receive LED signal and use it as the COR input to a DMK URI. It is a digital signal as viewed on a scope (i.e. very short slope in the transitions) This seems like it would work well and it does on strong signals. But on marginal signals where the LED may blink on and off quickly (like during picket fencing), it seems to confuse the URI (or the software) were it will start off good, but then a quick dropout of the COR signal will cause the software to no longer detect carrier, even though the signal on the COR input has been restored. Even if the input is solid high (or low in my case, I'm using usbinvert) it will not detect a carrier until there is another dropout of adequate time to "reset" it. I've tried putting a simple RC on the input but it didn't really help much. Seems the URI (or software) needs a significant minimum time between transitions to properly detect them, long enough that it would delay the carrier detection too much without a circuit more complex than an RC (i.e. something that would allow instant keyup, but delay the key down.) Linked is a scope image. https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg Carrier was detected until this signal dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is the signal out of the radio. Carrier was not detected after the 5th dropout even though the signal remained low. Anyone ever experience this and/or have ideas on how to fix it? Thanks. Mike KF7MBK -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Fri Sep 26 16:49:37 2014 From: doug at crompton.com (Doug Crompton) Date: Fri, 26 Sep 2014 12:49:37 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: , Message-ID: From: doug at crompton.com To: kf7mbk at w7ara.net Subject: RE: [App_rpt-users] Fwd: COR signal getting confused Date: Fri, 26 Sep 2014 12:46:14 -0400 That is very strange. Have you changed any of the default timing values? Are you using simplex/duplex? Courtesy tone? Timing values could effect that. I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes and I have never seen that problem. I have one user who has a signal like you describe. He walks in a park with a handheld and he is often in and out. Also I assume you are not using any rxdelay? 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 08:50:51 -0700 To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Fwd: COR signal getting confused Resending since my initial post has been pending moderation for 2 days now and got no reply from the list owner email. I have modified an HT to bring out the receive LED signal and use it as the COR input to a DMK URI. It is a digital signal as viewed on a scope (i.e. very short slope in the transitions) This seems like it would work well and it does on strong signals. But on marginal signals where the LED may blink on and off quickly (like during picket fencing), it seems to confuse the URI (or the software) were it will start off good, but then a quick dropout of the COR signal will cause the software to no longer detect carrier, even though the signal on the COR input has been restored. Even if the input is solid high (or low in my case, I'm using usbinvert) it will not detect a carrier until there is another dropout of adequate time to "reset" it. I've tried putting a simple RC on the input but it didn't really help much. Seems the URI (or software) needs a significant minimum time between transitions to properly detect them, long enough that it would delay the carrier detection too much without a circuit more complex than an RC (i.e. something that would allow instant keyup, but delay the key down.) Linked is a scope image. https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg Carrier was detected until this signal dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is the signal out of the radio. Carrier was not detected after the 5th dropout even though the signal remained low. Anyone ever experience this and/or have ideas on how to fix it? Thanks. Mike KF7MBK _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jrorke at cogeco.ca Fri Sep 26 16:53:37 2014 From: jrorke at cogeco.ca (Jon Rorke) Date: Fri, 26 Sep 2014 12:53:37 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: Message-ID: <54259A11.7060404@cogeco.ca> The URI wants to see a signal that goes hi to low or open collector to ground. It also has a diode on the input to block incoming voltage. So if your COR line sources a voltage then removes it but doesn't go all the way to ground when it goes low, then the URI will not see a transition. So perhaps you can put a resistor to the base of a NPN transistor and connect the collector to the URI I/P. Change the carrier from to "USB" in usbradio.conf and you should be good to go. On 9/26/2014 11:50 AM, Mike M wrote: > Resending since my initial post has been pending moderation for 2 days > now and got no reply from the list owner email. > > I have modified an HT to bring out the receive LED signal and use it > as the COR input to a DMK URI. It is a digital signal as viewed on a > scope (i.e. very short slope in the transitions) This seems like it > would work well and it does on strong signals. But on marginal signals > where the LED may blink on and off quickly (like during picket > fencing), it seems to confuse the URI (or the software) were it will > start off good, but then a quick dropout of the COR signal will cause > the software to no longer detect carrier, even though the signal on > the COR input has been restored. Even if the input is solid high (or > low in my case, I'm using usbinvert) it will not detect a carrier > until there is another dropout of adequate time to "reset" it. > > I've tried putting a simple RC on the input but it didn't really help > much. Seems the URI (or software) needs a significant minimum time > between transitions to properly detect them, long enough that it would > delay the carrier detection too much without a circuit more complex > than an RC (i.e. something that would allow instant keyup, but delay > the key down.) > > Linked is a scope image. > > https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg > > Carrier was detected until this signal > dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is > the signal out of the radio. Carrier was not detected after the 5th > dropout even though the signal remained low. > > Anyone ever experience this and/or have ideas on how to fix it? > > Thanks. > > Mike > KF7MBK > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kf7mbk at w7ara.net Fri Sep 26 16:56:21 2014 From: kf7mbk at w7ara.net (Mike M) Date: Fri, 26 Sep 2014 09:56:21 -0700 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: Message-ID: Doug, First: thanks for the excellent writeup on getting allstar running on the BBB. I used it to get up and running very quickly and is the setup I am having this issue with. I am running duplex =1 as well. I have not changed any timing values, (I'm essentially running the as-installed setup from the install image on your site) but I will take a look at them and see if I can make some changes for the better. Thanks! -Mike On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: > ------------------------------ > From: doug at crompton.com > To: kf7mbk at w7ara.net > Subject: RE: [App_rpt-users] Fwd: COR signal getting confused > Date: Fri, 26 Sep 2014 12:46:14 -0400 > > That is very strange. Have you changed any of the default timing values? > Are you using simplex/duplex? Courtesy tone? Timing values could effect > that. > > I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes > and I have never seen that problem. I have one user who has a signal like > you describe. He walks in a park with a handheld and he is often in and out. > > Also I assume you are not using any rxdelay? > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 08:50:51 -0700 > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Fwd: COR signal getting confused > > > Resending since my initial post has been pending moderation for 2 days now > and got no reply from the list owner email. > > I have modified an HT to bring out the receive LED signal and use it > as the COR input to a DMK URI. It is a digital signal as viewed on a > scope (i.e. very short slope in the transitions) This seems like it > would work well and it does on strong signals. But on marginal signals > where the LED may blink on and off quickly (like during picket > fencing), it seems to confuse the URI (or the software) were it will > start off good, but then a quick dropout of the COR signal will cause > the software to no longer detect carrier, even though the signal on > the COR input has been restored. Even if the input is solid high (or > low in my case, I'm using usbinvert) it will not detect a carrier > until there is another dropout of adequate time to "reset" it. > > I've tried putting a simple RC on the input but it didn't really help > much. Seems the URI (or software) needs a significant minimum time > between transitions to properly detect them, long enough that it would > delay the carrier detection too much without a circuit more complex > than an RC (i.e. something that would allow instant keyup, but delay > the key down.) > > Linked is a scope image. > > > https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg > > Carrier was detected until this signal > dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is > the signal out of the radio. Carrier was not detected after the 5th > dropout even though the signal remained low. > > Anyone ever experience this and/or have ideas on how to fix it? > > Thanks. > > Mike > KF7MBK > > > _______________________________________________ App_rpt-users mailing list > App_rpt-users at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Fri Sep 26 17:07:27 2014 From: doug at crompton.com (Doug Crompton) Date: Fri, 26 Sep 2014 13:07:27 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: , , Message-ID: Mike, Before you change any timing make sure as Jon pointed out that your COS signal is going hard high and low on signal and non-signal. You might need a pullup. The URI is kind of weak in that regard. It should be TTL levels <.5 volt low and >2.5 volt high and preferably rail to rail. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 09:56:21 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org Doug, First: thanks for the excellent writeup on getting allstar running on the BBB. I used it to get up and running very quickly and is the setup I am having this issue with. I am running duplex =1 as well. I have not changed any timing values, (I'm essentially running the as-installed setup from the install image on your site) but I will take a look at them and see if I can make some changes for the better. Thanks!-Mike On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: From: doug at crompton.com To: kf7mbk at w7ara.net Subject: RE: [App_rpt-users] Fwd: COR signal getting confused Date: Fri, 26 Sep 2014 12:46:14 -0400 That is very strange. Have you changed any of the default timing values? Are you using simplex/duplex? Courtesy tone? Timing values could effect that. I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes and I have never seen that problem. I have one user who has a signal like you describe. He walks in a park with a handheld and he is often in and out. Also I assume you are not using any rxdelay? 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 08:50:51 -0700 To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Fwd: COR signal getting confused Resending since my initial post has been pending moderation for 2 days now and got no reply from the list owner email. I have modified an HT to bring out the receive LED signal and use it as the COR input to a DMK URI. It is a digital signal as viewed on a scope (i.e. very short slope in the transitions) This seems like it would work well and it does on strong signals. But on marginal signals where the LED may blink on and off quickly (like during picket fencing), it seems to confuse the URI (or the software) were it will start off good, but then a quick dropout of the COR signal will cause the software to no longer detect carrier, even though the signal on the COR input has been restored. Even if the input is solid high (or low in my case, I'm using usbinvert) it will not detect a carrier until there is another dropout of adequate time to "reset" it. I've tried putting a simple RC on the input but it didn't really help much. Seems the URI (or software) needs a significant minimum time between transitions to properly detect them, long enough that it would delay the carrier detection too much without a circuit more complex than an RC (i.e. something that would allow instant keyup, but delay the key down.) Linked is a scope image. https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg Carrier was detected until this signal dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is the signal out of the radio. Carrier was not detected after the 5th dropout even though the signal remained low. Anyone ever experience this and/or have ideas on how to fix it? Thanks. Mike KF7MBK _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kf7mbk at w7ara.net Fri Sep 26 17:18:19 2014 From: kf7mbk at w7ara.net (Mike M) Date: Fri, 26 Sep 2014 10:18:19 -0700 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: Message-ID: The scope image in the OP shows there doesn't appear to be a problem with pulling hi or low, The transitions (without the RC) are very clean and go all the way to ground.. It seems like the URI is doing edge detection instead of level detection, and it's just missing fast edges. Wasn't sure if this was something that could be tweaked in software or if I'll have to put some external debounce logic on the line. On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: > Mike, > > Before you change any timing make sure as Jon pointed out that your COS > signal is going hard high and low on signal and non-signal. You might need > a pullup. The URI is kind of weak in that regard. It should be TTL levels > <.5 volt low and >2.5 volt high and preferably rail to rail. > > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 09:56:21 -0700 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > > Doug, > > First: thanks for the excellent writeup on getting allstar running on the > BBB. I used it to get up and running very quickly and is the setup I am > having this issue with. > > I am running duplex =1 as well. I have not changed any timing values, > (I'm essentially running the as-installed setup from the install image on > your site) but I will take a look at them and see if I can make some > changes for the better. > > Thanks! > -Mike > > > > > > On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: > > ------------------------------ > From: doug at crompton.com > To: kf7mbk at w7ara.net > Subject: RE: [App_rpt-users] Fwd: COR signal getting confused > Date: Fri, 26 Sep 2014 12:46:14 -0400 > > That is very strange. Have you changed any of the default timing values? > Are you using simplex/duplex? Courtesy tone? Timing values could effect > that. > > I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes > and I have never seen that problem. I have one user who has a signal like > you describe. He walks in a park with a handheld and he is often in and out. > > Also I assume you are not using any rxdelay? > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 08:50:51 -0700 > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Fwd: COR signal getting confused > > > Resending since my initial post has been pending moderation for 2 days now > and got no reply from the list owner email. > > I have modified an HT to bring out the receive LED signal and use it > as the COR input to a DMK URI. It is a digital signal as viewed on a > scope (i.e. very short slope in the transitions) This seems like it > would work well and it does on strong signals. But on marginal signals > where the LED may blink on and off quickly (like during picket > fencing), it seems to confuse the URI (or the software) were it will > start off good, but then a quick dropout of the COR signal will cause > the software to no longer detect carrier, even though the signal on > the COR input has been restored. Even if the input is solid high (or > low in my case, I'm using usbinvert) it will not detect a carrier > until there is another dropout of adequate time to "reset" it. > > I've tried putting a simple RC on the input but it didn't really help > much. Seems the URI (or software) needs a significant minimum time > between transitions to properly detect them, long enough that it would > delay the carrier detection too much without a circuit more complex > than an RC (i.e. something that would allow instant keyup, but delay > the key down.) > > Linked is a scope image. > > > https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg > > Carrier was detected until this signal > dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is > the signal out of the radio. Carrier was not detected after the 5th > dropout even though the signal remained low. > > Anyone ever experience this and/or have ideas on how to fix it? > > Thanks. > > Mike > KF7MBK > > > _______________________________________________ App_rpt-users mailing list > App_rpt-users at 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. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Fri Sep 26 22:05:03 2014 From: doug at crompton.com (Doug Crompton) Date: Fri, 26 Sep 2014 18:05:03 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: , , , , Message-ID: Mike, Are you using PL or noise squelch or both? Like I said I have not seen this problem and I am using basically stock timing. Every time the PL or squelch goes untrue for a certain (short) duration you should hear a courtesy tone. Perhpas you should try duplex=0 just to see if there is an issue with TX recovery. Do you have another radio you can try? 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 10:18:19 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org The scope image in the OP shows there doesn't appear to be a problem with pulling hi or low, The transitions (without the RC) are very clean and go all the way to ground.. It seems like the URI is doing edge detection instead of level detection, and it's just missing fast edges. Wasn't sure if this was something that could be tweaked in software or if I'll have to put some external debounce logic on the line. On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: Mike, Before you change any timing make sure as Jon pointed out that your COS signal is going hard high and low on signal and non-signal. You might need a pullup. The URI is kind of weak in that regard. It should be TTL levels <.5 volt low and >2.5 volt high and preferably rail to rail. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 09:56:21 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org Doug, First: thanks for the excellent writeup on getting allstar running on the BBB. I used it to get up and running very quickly and is the setup I am having this issue with. I am running duplex =1 as well. I have not changed any timing values, (I'm essentially running the as-installed setup from the install image on your site) but I will take a look at them and see if I can make some changes for the better. Thanks!-Mike On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: From: doug at crompton.com To: kf7mbk at w7ara.net Subject: RE: [App_rpt-users] Fwd: COR signal getting confused Date: Fri, 26 Sep 2014 12:46:14 -0400 That is very strange. Have you changed any of the default timing values? Are you using simplex/duplex? Courtesy tone? Timing values could effect that. I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes and I have never seen that problem. I have one user who has a signal like you describe. He walks in a park with a handheld and he is often in and out. Also I assume you are not using any rxdelay? 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 08:50:51 -0700 To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Fwd: COR signal getting confused Resending since my initial post has been pending moderation for 2 days now and got no reply from the list owner email. I have modified an HT to bring out the receive LED signal and use it as the COR input to a DMK URI. It is a digital signal as viewed on a scope (i.e. very short slope in the transitions) This seems like it would work well and it does on strong signals. But on marginal signals where the LED may blink on and off quickly (like during picket fencing), it seems to confuse the URI (or the software) were it will start off good, but then a quick dropout of the COR signal will cause the software to no longer detect carrier, even though the signal on the COR input has been restored. Even if the input is solid high (or low in my case, I'm using usbinvert) it will not detect a carrier until there is another dropout of adequate time to "reset" it. I've tried putting a simple RC on the input but it didn't really help much. Seems the URI (or software) needs a significant minimum time between transitions to properly detect them, long enough that it would delay the carrier detection too much without a circuit more complex than an RC (i.e. something that would allow instant keyup, but delay the key down.) Linked is a scope image. https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg Carrier was detected until this signal dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is the signal out of the radio. Carrier was not detected after the 5th dropout even though the signal remained low. Anyone ever experience this and/or have ideas on how to fix it? Thanks. Mike KF7MBK _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kf7mbk at w7ara.net Sat Sep 27 01:59:26 2014 From: kf7mbk at w7ara.net (Mike M) Date: Fri, 26 Sep 2014 18:59:26 -0700 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: Message-ID: OK, so I did some more testing. I have routed the signal out of the radio to an NPN and switched from usbinvert to usb as suggested. This made little difference, but in this configuration I could make the RC work a little better bridging the dropouts. But still would end up not detecting carrier after a quick dropout even though the COR signal into the dongle was high. Duplex = 0 seems to eliminate the problem. Is there a setting to tell it how long to wait after COR dropped to start transmitting the courtesy tone? (though I suppose that would defeat the purpose of the duplex=1 setting) Note that I have the PTT disconnected for testing, so all I see is the red LED come on as soon as the COR out of the radio drops. Actually as I'm typing this and playing with it, I just noticed it appears if the COR is restored ANY time the PTT is active for the courtesy tone, it will ignore the COR line until it's dropped and brought back up AFTER the PTT is done. This behavior seems VERY repeatable, even with a cleanly restored COR signal, So it may have nothing to do with quick dropouts and everything to do with the courtesy tone.. Are there any settings that control this? The LED on the radio (and hence my COR input) is controlled by noise squelch opening. On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton wrote: > Mike, > > Are you using PL or noise squelch or both? Like I said I have not seen > this problem and I am using basically stock timing. Every time the PL or > squelch goes untrue for a certain (short) duration you should hear a > courtesy tone. Perhpas you should try duplex=0 just to see if there is an > issue with TX recovery. Do you have another radio you can try? > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 10:18:19 -0700 > > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > The scope image in the OP shows there doesn't appear to be a problem with > pulling hi or low, The transitions (without the RC) are very clean and go > all the way to ground.. It seems like the URI is doing edge detection > instead of level detection, and it's just missing fast edges. Wasn't sure > if this was something that could be tweaked in software or if I'll have to > put some external debounce logic on the line. > > > On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: > > Mike, > > Before you change any timing make sure as Jon pointed out that your COS > signal is going hard high and low on signal and non-signal. You might need > a pullup. The URI is kind of weak in that regard. It should be TTL levels > <.5 volt low and >2.5 volt high and preferably rail to rail. > > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 09:56:21 -0700 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > > Doug, > > First: thanks for the excellent writeup on getting allstar running on the > BBB. I used it to get up and running very quickly and is the setup I am > having this issue with. > > I am running duplex =1 as well. I have not changed any timing values, > (I'm essentially running the as-installed setup from the install image on > your site) but I will take a look at them and see if I can make some > changes for the better. > > Thanks! > -Mike > > > > > > On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: > > ------------------------------ > From: doug at crompton.com > To: kf7mbk at w7ara.net > Subject: RE: [App_rpt-users] Fwd: COR signal getting confused > Date: Fri, 26 Sep 2014 12:46:14 -0400 > > That is very strange. Have you changed any of the default timing values? > Are you using simplex/duplex? Courtesy tone? Timing values could effect > that. > > I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes > and I have never seen that problem. I have one user who has a signal like > you describe. He walks in a park with a handheld and he is often in and out. > > Also I assume you are not using any rxdelay? > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 08:50:51 -0700 > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Fwd: COR signal getting confused > > > Resending since my initial post has been pending moderation for 2 days now > and got no reply from the list owner email. > > I have modified an HT to bring out the receive LED signal and use it > as the COR input to a DMK URI. It is a digital signal as viewed on a > scope (i.e. very short slope in the transitions) This seems like it > would work well and it does on strong signals. But on marginal signals > where the LED may blink on and off quickly (like during picket > fencing), it seems to confuse the URI (or the software) were it will > start off good, but then a quick dropout of the COR signal will cause > the software to no longer detect carrier, even though the signal on > the COR input has been restored. Even if the input is solid high (or > low in my case, I'm using usbinvert) it will not detect a carrier > until there is another dropout of adequate time to "reset" it. > > I've tried putting a simple RC on the input but it didn't really help > much. Seems the URI (or software) needs a significant minimum time > between transitions to properly detect them, long enough that it would > delay the carrier detection too much without a circuit more complex > than an RC (i.e. something that would allow instant keyup, but delay > the key down.) > > Linked is a scope image. > > > https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg > > Carrier was detected until this signal > dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is > the signal out of the radio. Carrier was not detected after the 5th > dropout even though the signal remained low. > > Anyone ever experience this and/or have ideas on how to fix it? > > Thanks. > > Mike > KF7MBK > > > _______________________________________________ App_rpt-users mailing list > App_rpt-users at 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. > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sat Sep 27 03:37:34 2014 From: doug at crompton.com (Doug Crompton) Date: Fri, 26 Sep 2014 23:37:34 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: , , , , , Message-ID: Mike, You can try the changing the courtesy time wait then set back to duplex=1 The wait-times section This section allows the wait times for voice responses and other audio telemetry events to be adjusted. All wait times are in milliseconds. telemwait sets the time before sending the general audio telemetry responses used in the application which are not specifically defined below idwait sets the time to wait before sending ID audio telemetry unkeywait sets the amount of time to wait before sending the courtesy tone. This can be used to ensure breaking stations can get their turn calltermwait sets the amount of time between an autopatch disconnect and the audio telemetry message indicating the call has been terminated The unkeywait is the one to mess with. It is 400ms on the BBB by default. Make it longer like 1000 so it spans the dropout period you are seeing. Experiment with times. If that doesn't work I really think you should try a different radio. My thoughts are that it is some kind of recovery issue with TX. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 18:59:26 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org OK, so I did some more testing. I have routed the signal out of the radio to an NPN and switched from usbinvert to usb as suggested. This made little difference, but in this configuration I could make the RC work a little better bridging the dropouts. But still would end up not detecting carrier after a quick dropout even though the COR signal into the dongle was high. Duplex = 0 seems to eliminate the problem. Is there a setting to tell it how long to wait after COR dropped to start transmitting the courtesy tone? (though I suppose that would defeat the purpose of the duplex=1 setting) Note that I have the PTT disconnected for testing, so all I see is the red LED come on as soon as the COR out of the radio drops. Actually as I'm typing this and playing with it, I just noticed it appears if the COR is restored ANY time the PTT is active for the courtesy tone, it will ignore the COR line until it's dropped and brought back up AFTER the PTT is done. This behavior seems VERY repeatable, even with a cleanly restored COR signal, So it may have nothing to do with quick dropouts and everything to do with the courtesy tone.. Are there any settings that control this? The LED on the radio (and hence my COR input) is controlled by noise squelch opening. On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton wrote: Mike, Are you using PL or noise squelch or both? Like I said I have not seen this problem and I am using basically stock timing. Every time the PL or squelch goes untrue for a certain (short) duration you should hear a courtesy tone. Perhpas you should try duplex=0 just to see if there is an issue with TX recovery. Do you have another radio you can try? 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 10:18:19 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org The scope image in the OP shows there doesn't appear to be a problem with pulling hi or low, The transitions (without the RC) are very clean and go all the way to ground.. It seems like the URI is doing edge detection instead of level detection, and it's just missing fast edges. Wasn't sure if this was something that could be tweaked in software or if I'll have to put some external debounce logic on the line. On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: Mike, Before you change any timing make sure as Jon pointed out that your COS signal is going hard high and low on signal and non-signal. You might need a pullup. The URI is kind of weak in that regard. It should be TTL levels <.5 volt low and >2.5 volt high and preferably rail to rail. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 09:56:21 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org Doug, First: thanks for the excellent writeup on getting allstar running on the BBB. I used it to get up and running very quickly and is the setup I am having this issue with. I am running duplex =1 as well. I have not changed any timing values, (I'm essentially running the as-installed setup from the install image on your site) but I will take a look at them and see if I can make some changes for the better. Thanks!-Mike On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: From: doug at crompton.com To: kf7mbk at w7ara.net Subject: RE: [App_rpt-users] Fwd: COR signal getting confused Date: Fri, 26 Sep 2014 12:46:14 -0400 That is very strange. Have you changed any of the default timing values? Are you using simplex/duplex? Courtesy tone? Timing values could effect that. I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes and I have never seen that problem. I have one user who has a signal like you describe. He walks in a park with a handheld and he is often in and out. Also I assume you are not using any rxdelay? 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 08:50:51 -0700 To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Fwd: COR signal getting confused Resending since my initial post has been pending moderation for 2 days now and got no reply from the list owner email. I have modified an HT to bring out the receive LED signal and use it as the COR input to a DMK URI. It is a digital signal as viewed on a scope (i.e. very short slope in the transitions) This seems like it would work well and it does on strong signals. But on marginal signals where the LED may blink on and off quickly (like during picket fencing), it seems to confuse the URI (or the software) were it will start off good, but then a quick dropout of the COR signal will cause the software to no longer detect carrier, even though the signal on the COR input has been restored. Even if the input is solid high (or low in my case, I'm using usbinvert) it will not detect a carrier until there is another dropout of adequate time to "reset" it. I've tried putting a simple RC on the input but it didn't really help much. Seems the URI (or software) needs a significant minimum time between transitions to properly detect them, long enough that it would delay the carrier detection too much without a circuit more complex than an RC (i.e. something that would allow instant keyup, but delay the key down.) Linked is a scope image. https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg Carrier was detected until this signal dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is the signal out of the radio. Carrier was not detected after the 5th dropout even though the signal remained low. Anyone ever experience this and/or have ideas on how to fix it? Thanks. Mike KF7MBK _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kp4tr.ramon at gmail.com Sat Sep 27 04:27:50 2014 From: kp4tr.ramon at gmail.com ((KP4TR)Ramon Gonzalez) Date: Sat, 27 Sep 2014 00:27:50 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: , , , , , Message-ID: <54263CC6.9050507@gmail.com> What HT brand/model are you using, just out of curiosity? On 9/26/2014 11:37 PM, Doug Crompton wrote: > Mike, > > You can try the changing the courtesy time wait then set back to duplex=1 > > The wait-times section > This section allows the wait times for voice responses and other audio > telemetry events to be adjusted. All wait times are in milliseconds. > > */telemwait/* sets the time before sending the general audio telemetry > responses used in the application which are not specifically defined below > */idwait/* sets the time to wait before sending ID audio telemetry > */unkeywait/* sets the amount of time to wait before sending the > courtesy tone. This can be used to ensure breaking stations can get > their turn > */calltermwait/* sets the amount of time between an autopatch > disconnect and the audio telemetry message indicating the call has > been terminated > > The unkeywait is the one to mess with. It is 400ms on the BBB by > default. Make it longer like 1000 so it spans the dropout period you > are seeing. Experiment with times. > > If that doesn't work I really think you should try a different radio. > My thoughts are that it is some kind of recovery issue with TX. > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 18:59:26 -0700 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > OK, so I did some more testing. > > I have routed the signal out of the radio to an NPN and switched from > usbinvert to usb as suggested. This made little difference, but in > this configuration I could make the RC work a little better bridging > the dropouts. But still would end up not detecting carrier after a > quick dropout even though the COR signal into the dongle was high. > > Duplex = 0 seems to eliminate the problem. Is there a setting to tell > it how long to wait after COR dropped to start transmitting the > courtesy tone? (though I suppose that would defeat the purpose of the > duplex=1 setting) Note that I have the PTT disconnected for testing, > so all I see is the red LED come on as soon as the COR out of the > radio drops. > > Actually as I'm typing this and playing with it, I just noticed it > appears if the COR is restored ANY time the PTT is active for the > courtesy tone, it will ignore the COR line until it's dropped and > brought back up AFTER the PTT is done. This behavior seems VERY > repeatable, even with a cleanly restored COR signal, So it may have > nothing to do with quick dropouts and everything to do with the > courtesy tone.. > > Are there any settings that control this? > > The LED on the radio (and hence my COR input) is controlled by noise > squelch opening. > > > > > > > On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton > wrote: > > Mike, > > Are you using PL or noise squelch or both? Like I said I have not > seen this problem and I am using basically stock timing. Every > time the PL or squelch goes untrue for a certain (short) duration > you should hear a courtesy tone. Perhpas you should try duplex=0 > just to see if there is an issue with TX recovery. Do you have > another radio you can try? > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 10:18:19 -0700 > > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > The scope image in the OP shows there doesn't appear to be a > problem with pulling hi or low, The transitions (without the RC) > are very clean and go all the way to ground.. It seems like the > URI is doing edge detection instead of level detection, and it's > just missing fast edges. Wasn't sure if this was something that > could be tweaked in software or if I'll have to put some external > debounce logic on the line. > > > On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton > wrote: > > Mike, > > Before you change any timing make sure as Jon pointed out > that your COS signal is going hard high and low on signal and > non-signal. You might need a pullup. The URI is kind of weak > in that regard. It should be TTL levels <.5 volt low and > >2.5 volt high and preferably rail to rail. > > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 09:56:21 -0700 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > > Doug, > > First: thanks for the excellent writeup on getting allstar > running on the BBB. I used it to get up and running very > quickly and is the setup I am having this issue with. > > I am running duplex =1 as well. I have not changed any timing > values, (I'm essentially running the as-installed setup from > the install image on your site) but I will take a look at them > and see if I can make some changes for the better. > > Thanks! > -Mike > > > > > > On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton > > wrote: > > ------------------------------------------------------------------------ > From: doug at crompton.com > To: kf7mbk at w7ara.net > Subject: RE: [App_rpt-users] Fwd: COR signal getting confused > Date: Fri, 26 Sep 2014 12:46:14 -0400 > > That is very strange. Have you changed any of the default > timing values? Are you using simplex/duplex? Courtesy > tone? Timing values could effect that. > > I use simplex with courtesy tone (duplex=1 in rpt.conf) > on several nodes and I have never seen that problem. I > have one user who has a signal like you describe. He walks > in a park with a handheld and he is often in and out. > > Also I assume you are not using any rxdelay? > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 08:50:51 -0700 > To: app_rpt-users at ohnosec.org > > Subject: [App_rpt-users] Fwd: COR signal getting confused > > > Resending since my initial post has been pending > moderation for 2 days now and got no reply from the list > owner email. > > I have modified an HT to bring out the receive LED signal > and use it > as the COR input to a DMK URI. It is a digital signal as > viewed on a > scope (i.e. very short slope in the transitions) This > seems like it > would work well and it does on strong signals. But on > marginal signals > where the LED may blink on and off quickly (like during picket > fencing), it seems to confuse the URI (or the software) > were it will > start off good, but then a quick dropout of the COR signal > will cause > the software to no longer detect carrier, even though the > signal on > the COR input has been restored. Even if the input is > solid high (or > low in my case, I'm using usbinvert) it will not detect a > carrier > until there is another dropout of adequate time to "reset" it. > > I've tried putting a simple RC on the input but it didn't > really help > much. Seems the URI (or software) needs a significant > minimum time > between transitions to properly detect them, long enough > that it would > delay the carrier detection too much without a circuit > more complex > than an RC (i.e. something that would allow instant keyup, > but delay > the key down.) > > Linked is a scope image. > > https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg > > Carrier was detected until this signal > dropout event. Ch A is my RC filtered signal sent to the > URI, Ch B is > the signal out of the radio. Carrier was not detected > after the 5th > dropout even though the signal remained low. > > Anyone ever experience this and/or have ideas on how to > fix it? > > Thanks. > > Mike > KF7MBK > > > _______________________________________________ > App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kf7mbk at w7ara.net Sat Sep 27 04:29:46 2014 From: kf7mbk at w7ara.net (Mike M) Date: Fri, 26 Sep 2014 21:29:46 -0700 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: <54263CC6.9050507@gmail.com> References: <54263CC6.9050507@gmail.com> Message-ID: Puxing 777 On Fri, Sep 26, 2014 at 9:27 PM, (KP4TR)Ramon Gonzalez < kp4tr.ramon at gmail.com> wrote: > What HT brand/model are you using, just out of curiosity? > > > > On 9/26/2014 11:37 PM, Doug Crompton wrote: > > Mike, > > You can try the changing the courtesy time wait then set back to duplex=1 > > The wait-times section > This section allows the wait times for voice responses and other audio > telemetry events to be adjusted. All wait times are in milliseconds. > > *telemwait* sets the time before sending the general audio telemetry > responses used in the application which are not specifically defined below > *idwait* sets the time to wait before sending ID audio telemetry > *unkeywait* sets the amount of time to wait before sending the courtesy > tone. This can be used to ensure breaking stations can get their turn > *calltermwait* sets the amount of time between an autopatch disconnect > and the audio telemetry message indicating the call has been terminated > > The unkeywait is the one to mess with. It is 400ms on the BBB by default. > Make it longer like 1000 so it spans the dropout period you are seeing. > Experiment with times. > > If that doesn't work I really think you should try a different radio. My > thoughts are that it is some kind of recovery issue with TX. > > > > *73 Doug WA3DSP http://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 18:59:26 -0700 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > OK, so I did some more testing. > > I have routed the signal out of the radio to an NPN and switched from > usbinvert to usb as suggested. This made little difference, but in this > configuration I could make the RC work a little better bridging the > dropouts. But still would end up not detecting carrier after a quick > dropout even though the COR signal into the dongle was high. > > Duplex = 0 seems to eliminate the problem. Is there a setting to tell it > how long to wait after COR dropped to start transmitting the courtesy tone? > (though I suppose that would defeat the purpose of the duplex=1 setting) > Note that I have the PTT disconnected for testing, so all I see is the red > LED come on as soon as the COR out of the radio drops. > > Actually as I'm typing this and playing with it, I just noticed it > appears if the COR is restored ANY time the PTT is active for the courtesy > tone, it will ignore the COR line until it's dropped and brought back up > AFTER the PTT is done. This behavior seems VERY repeatable, even with a > cleanly restored COR signal, So it may have nothing to do with quick > dropouts and everything to do with the courtesy tone.. > > Are there any settings that control this? > > The LED on the radio (and hence my COR input) is controlled by noise > squelch opening. > > > > > > > On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton wrote: > > Mike, > > Are you using PL or noise squelch or both? Like I said I have not seen > this problem and I am using basically stock timing. Every time the PL or > squelch goes untrue for a certain (short) duration you should hear a > courtesy tone. Perhpas you should try duplex=0 just to see if there is an > issue with TX recovery. Do you have another radio you can try? > > > > *73 Doug WA3DSP http://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 10:18:19 -0700 > > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > The scope image in the OP shows there doesn't appear to be a problem with > pulling hi or low, The transitions (without the RC) are very clean and go > all the way to ground.. It seems like the URI is doing edge detection > instead of level detection, and it's just missing fast edges. Wasn't sure > if this was something that could be tweaked in software or if I'll have to > put some external debounce logic on the line. > > > On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: > > Mike, > > Before you change any timing make sure as Jon pointed out that your COS > signal is going hard high and low on signal and non-signal. You might need > a pullup. The URI is kind of weak in that regard. It should be TTL levels > <.5 volt low and >2.5 volt high and preferably rail to rail. > > > > > *73 Doug WA3DSP http://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 09:56:21 -0700 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > > Doug, > > First: thanks for the excellent writeup on getting allstar running on > the BBB. I used it to get up and running very quickly and is the setup I > am having this issue with. > > I am running duplex =1 as well. I have not changed any timing values, > (I'm essentially running the as-installed setup from the install image on > your site) but I will take a look at them and see if I can make some > changes for the better. > > Thanks! > -Mike > > > > > > On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: > > ------------------------------ > From: doug at crompton.com > To: kf7mbk at w7ara.net > Subject: RE: [App_rpt-users] Fwd: COR signal getting confused > Date: Fri, 26 Sep 2014 12:46:14 -0400 > > That is very strange. Have you changed any of the default timing values? > Are you using simplex/duplex? Courtesy tone? Timing values could effect > that. > > I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes > and I have never seen that problem. I have one user who has a signal like > you describe. He walks in a park with a handheld and he is often in and out. > > Also I assume you are not using any rxdelay? > > > > *73 Doug WA3DSP http://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 08:50:51 -0700 > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Fwd: COR signal getting confused > > > Resending since my initial post has been pending moderation for 2 days > now and got no reply from the list owner email. > > I have modified an HT to bring out the receive LED signal and use it > as the COR input to a DMK URI. It is a digital signal as viewed on a > scope (i.e. very short slope in the transitions) This seems like it > would work well and it does on strong signals. But on marginal signals > where the LED may blink on and off quickly (like during picket > fencing), it seems to confuse the URI (or the software) were it will > start off good, but then a quick dropout of the COR signal will cause > the software to no longer detect carrier, even though the signal on > the COR input has been restored. Even if the input is solid high (or > low in my case, I'm using usbinvert) it will not detect a carrier > until there is another dropout of adequate time to "reset" it. > > I've tried putting a simple RC on the input but it didn't really help > much. Seems the URI (or software) needs a significant minimum time > between transitions to properly detect them, long enough that it would > delay the carrier detection too much without a circuit more complex > than an RC (i.e. something that would allow instant keyup, but delay > the key down.) > > Linked is a scope image. > > > https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg > > Carrier was detected until this signal > dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is > the signal out of the radio. Carrier was not detected after the 5th > dropout even though the signal remained low. > > Anyone ever experience this and/or have ideas on how to fix it? > > Thanks. > > Mike > KF7MBK > > > _______________________________________________ App_rpt-users mailing > list App_rpt-users at 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 listApp_rpt-users at ohnosec.orghttp://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. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kp4tr.ramon at gmail.com Sat Sep 27 04:32:19 2014 From: kp4tr.ramon at gmail.com ((KP4TR)Ramon Gonzalez) Date: Sat, 27 Sep 2014 00:32:19 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: , , , , , Message-ID: <54263DD3.8030600@gmail.com> Try this in usbradio.conf (this is not recognized in simpleusb): rxondelay=25 ; This will instruct the usbradio driver to ignore the COR line ; for a specified number of 20mSec intervals following the release of PTT. On 9/26/2014 11:37 PM, Doug Crompton wrote: > Mike, > > You can try the changing the courtesy time wait then set back to duplex=1 > > The wait-times section > This section allows the wait times for voice responses and other audio > telemetry events to be adjusted. All wait times are in milliseconds. > > */telemwait/* sets the time before sending the general audio telemetry > responses used in the application which are not specifically defined below > */idwait/* sets the time to wait before sending ID audio telemetry > */unkeywait/* sets the amount of time to wait before sending the > courtesy tone. This can be used to ensure breaking stations can get > their turn > */calltermwait/* sets the amount of time between an autopatch > disconnect and the audio telemetry message indicating the call has > been terminated > > The unkeywait is the one to mess with. It is 400ms on the BBB by > default. Make it longer like 1000 so it spans the dropout period you > are seeing. Experiment with times. > > If that doesn't work I really think you should try a different radio. > My thoughts are that it is some kind of recovery issue with TX. > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 18:59:26 -0700 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > OK, so I did some more testing. > > I have routed the signal out of the radio to an NPN and switched from > usbinvert to usb as suggested. This made little difference, but in > this configuration I could make the RC work a little better bridging > the dropouts. But still would end up not detecting carrier after a > quick dropout even though the COR signal into the dongle was high. > > Duplex = 0 seems to eliminate the problem. Is there a setting to tell > it how long to wait after COR dropped to start transmitting the > courtesy tone? (though I suppose that would defeat the purpose of the > duplex=1 setting) Note that I have the PTT disconnected for testing, > so all I see is the red LED come on as soon as the COR out of the > radio drops. > > Actually as I'm typing this and playing with it, I just noticed it > appears if the COR is restored ANY time the PTT is active for the > courtesy tone, it will ignore the COR line until it's dropped and > brought back up AFTER the PTT is done. This behavior seems VERY > repeatable, even with a cleanly restored COR signal, So it may have > nothing to do with quick dropouts and everything to do with the > courtesy tone.. > > Are there any settings that control this? > > The LED on the radio (and hence my COR input) is controlled by noise > squelch opening. > > > > > > > On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton > wrote: > > Mike, > > Are you using PL or noise squelch or both? Like I said I have not > seen this problem and I am using basically stock timing. Every > time the PL or squelch goes untrue for a certain (short) duration > you should hear a courtesy tone. Perhpas you should try duplex=0 > just to see if there is an issue with TX recovery. Do you have > another radio you can try? > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 10:18:19 -0700 > > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > The scope image in the OP shows there doesn't appear to be a > problem with pulling hi or low, The transitions (without the RC) > are very clean and go all the way to ground.. It seems like the > URI is doing edge detection instead of level detection, and it's > just missing fast edges. Wasn't sure if this was something that > could be tweaked in software or if I'll have to put some external > debounce logic on the line. > > > On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton > wrote: > > Mike, > > Before you change any timing make sure as Jon pointed out > that your COS signal is going hard high and low on signal and > non-signal. You might need a pullup. The URI is kind of weak > in that regard. It should be TTL levels <.5 volt low and > >2.5 volt high and preferably rail to rail. > > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 09:56:21 -0700 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > > Doug, > > First: thanks for the excellent writeup on getting allstar > running on the BBB. I used it to get up and running very > quickly and is the setup I am having this issue with. > > I am running duplex =1 as well. I have not changed any timing > values, (I'm essentially running the as-installed setup from > the install image on your site) but I will take a look at them > and see if I can make some changes for the better. > > Thanks! > -Mike > > > > > > On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton > > wrote: > > ------------------------------------------------------------------------ > From: doug at crompton.com > To: kf7mbk at w7ara.net > Subject: RE: [App_rpt-users] Fwd: COR signal getting confused > Date: Fri, 26 Sep 2014 12:46:14 -0400 > > That is very strange. Have you changed any of the default > timing values? Are you using simplex/duplex? Courtesy > tone? Timing values could effect that. > > I use simplex with courtesy tone (duplex=1 in rpt.conf) > on several nodes and I have never seen that problem. I > have one user who has a signal like you describe. He walks > in a park with a handheld and he is often in and out. > > Also I assume you are not using any rxdelay? > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 08:50:51 -0700 > To: app_rpt-users at ohnosec.org > > Subject: [App_rpt-users] Fwd: COR signal getting confused > > > Resending since my initial post has been pending > moderation for 2 days now and got no reply from the list > owner email. > > I have modified an HT to bring out the receive LED signal > and use it > as the COR input to a DMK URI. It is a digital signal as > viewed on a > scope (i.e. very short slope in the transitions) This > seems like it > would work well and it does on strong signals. But on > marginal signals > where the LED may blink on and off quickly (like during picket > fencing), it seems to confuse the URI (or the software) > were it will > start off good, but then a quick dropout of the COR signal > will cause > the software to no longer detect carrier, even though the > signal on > the COR input has been restored. Even if the input is > solid high (or > low in my case, I'm using usbinvert) it will not detect a > carrier > until there is another dropout of adequate time to "reset" it. > > I've tried putting a simple RC on the input but it didn't > really help > much. Seems the URI (or software) needs a significant > minimum time > between transitions to properly detect them, long enough > that it would > delay the carrier detection too much without a circuit > more complex > than an RC (i.e. something that would allow instant keyup, > but delay > the key down.) > > Linked is a scope image. > > https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg > > Carrier was detected until this signal > dropout event. Ch A is my RC filtered signal sent to the > URI, Ch B is > the signal out of the radio. Carrier was not detected > after the 5th > dropout even though the signal remained low. > > Anyone ever experience this and/or have ideas on how to > fix it? > > Thanks. > > Mike > KF7MBK > > > _______________________________________________ > App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kf7mbk at w7ara.net Sat Sep 27 04:15:03 2014 From: kf7mbk at w7ara.net (Mike M) Date: Fri, 26 Sep 2014 21:15:03 -0700 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: Message-ID: Doug, this behavior happens even if I manually toggle the COR independent of the radio and audio so unless I'm not understanding, I can't see this being the radio. I tried changing unkeywait to 1000 but made no difference other than extending the time the PTT is active for the courtesy tone, and thus extending the window in which the COR line going high will be ignored. Seems that anything that extends the time that the PTT is active for the courtesy tone also extends the time that the COR is ignored. Just to make sure I'm not doing anything stupid or have an unconventional setuo,. my test setup is: HT -> DMK URI -> BBB (node 1998) -> ethernet -> Allstar on a VM (node 1620) -> IAX -> Zioper soft phone on laptop HT has audio in/out connected to the URI. PTT from the URI is not connected to the HT while testing. Signal from receive LED on the HT goes to COR URI input. I have the HT tuned to the weather frequency and I'm making/breaking the antenna connection to simulate picket fencing and I'm monitoring the audio received by the URI/BBB on the softphone. Bottom line is if the COR line drops, the courtesy pause and tone is instantly triggered, triggering the URI PTT. This works. But, if while the PTT is active, the COR line goes high again, the audio through the URI is not routed through until the COR line goes low* and high again after the PTT/courtesy tone is done transmitting. * when going low after getting ignored going high, no courtesy tone is triggered. Would it be useful/appropriate change carrierfrom to "no" and instead set ctcssfrom = usb and switch the radio output to the ctcss input on the URI and see if the problem still exists? Thanks for all the help! -Mike On Fri, Sep 26, 2014 at 8:37 PM, Doug Crompton wrote: > Mike, > > You can try the changing the courtesy time wait then set back to duplex=1 > > The wait-times section > This section allows the wait times for voice responses and other audio > telemetry events to be adjusted. All wait times are in milliseconds. > > *telemwait* sets the time before sending the general audio telemetry > responses used in the application which are not specifically defined below > *idwait* sets the time to wait before sending ID audio telemetry > *unkeywait* sets the amount of time to wait before sending the courtesy > tone. This can be used to ensure breaking stations can get their turn > *calltermwait* sets the amount of time between an autopatch disconnect > and the audio telemetry message indicating the call has been terminated > > The unkeywait is the one to mess with. It is 400ms on the BBB by default. > Make it longer like 1000 so it spans the dropout period you are seeing. > Experiment with times. > > If that doesn't work I really think you should try a different radio. My > thoughts are that it is some kind of recovery issue with TX. > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 18:59:26 -0700 > > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > OK, so I did some more testing. > > I have routed the signal out of the radio to an NPN and switched from > usbinvert to usb as suggested. This made little difference, but in this > configuration I could make the RC work a little better bridging the > dropouts. But still would end up not detecting carrier after a quick > dropout even though the COR signal into the dongle was high. > > Duplex = 0 seems to eliminate the problem. Is there a setting to tell it > how long to wait after COR dropped to start transmitting the courtesy tone? > (though I suppose that would defeat the purpose of the duplex=1 setting) > Note that I have the PTT disconnected for testing, so all I see is the red > LED come on as soon as the COR out of the radio drops. > > Actually as I'm typing this and playing with it, I just noticed it appears > if the COR is restored ANY time the PTT is active for the courtesy tone, it > will ignore the COR line until it's dropped and brought back up AFTER the > PTT is done. This behavior seems VERY repeatable, even with a cleanly > restored COR signal, So it may have nothing to do with quick dropouts and > everything to do with the courtesy tone.. > > Are there any settings that control this? > > The LED on the radio (and hence my COR input) is controlled by noise > squelch opening. > > > > > > > On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton wrote: > > Mike, > > Are you using PL or noise squelch or both? Like I said I have not seen > this problem and I am using basically stock timing. Every time the PL or > squelch goes untrue for a certain (short) duration you should hear a > courtesy tone. Perhpas you should try duplex=0 just to see if there is an > issue with TX recovery. Do you have another radio you can try? > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 10:18:19 -0700 > > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > The scope image in the OP shows there doesn't appear to be a problem with > pulling hi or low, The transitions (without the RC) are very clean and go > all the way to ground.. It seems like the URI is doing edge detection > instead of level detection, and it's just missing fast edges. Wasn't sure > if this was something that could be tweaked in software or if I'll have to > put some external debounce logic on the line. > > > On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: > > Mike, > > Before you change any timing make sure as Jon pointed out that your COS > signal is going hard high and low on signal and non-signal. You might need > a pullup. The URI is kind of weak in that regard. It should be TTL levels > <.5 volt low and >2.5 volt high and preferably rail to rail. > > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 09:56:21 -0700 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > > Doug, > > First: thanks for the excellent writeup on getting allstar running on the > BBB. I used it to get up and running very quickly and is the setup I am > having this issue with. > > I am running duplex =1 as well. I have not changed any timing values, > (I'm essentially running the as-installed setup from the install image on > your site) but I will take a look at them and see if I can make some > changes for the better. > > Thanks! > -Mike > > > > > > On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: > > ------------------------------ > From: doug at crompton.com > To: kf7mbk at w7ara.net > Subject: RE: [App_rpt-users] Fwd: COR signal getting confused > Date: Fri, 26 Sep 2014 12:46:14 -0400 > > That is very strange. Have you changed any of the default timing values? > Are you using simplex/duplex? Courtesy tone? Timing values could effect > that. > > I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes > and I have never seen that problem. I have one user who has a signal like > you describe. He walks in a park with a handheld and he is often in and out. > > Also I assume you are not using any rxdelay? > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 08:50:51 -0700 > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Fwd: COR signal getting confused > > > Resending since my initial post has been pending moderation for 2 days now > and got no reply from the list owner email. > > I have modified an HT to bring out the receive LED signal and use it > as the COR input to a DMK URI. It is a digital signal as viewed on a > scope (i.e. very short slope in the transitions) This seems like it > would work well and it does on strong signals. But on marginal signals > where the LED may blink on and off quickly (like during picket > fencing), it seems to confuse the URI (or the software) were it will > start off good, but then a quick dropout of the COR signal will cause > the software to no longer detect carrier, even though the signal on > the COR input has been restored. Even if the input is solid high (or > low in my case, I'm using usbinvert) it will not detect a carrier > until there is another dropout of adequate time to "reset" it. > > I've tried putting a simple RC on the input but it didn't really help > much. Seems the URI (or software) needs a significant minimum time > between transitions to properly detect them, long enough that it would > delay the carrier detection too much without a circuit more complex > than an RC (i.e. something that would allow instant keyup, but delay > the key down.) > > Linked is a scope image. > > > https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg > > Carrier was detected until this signal > dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is > the signal out of the radio. Carrier was not detected after the 5th > dropout even though the signal remained low. > > Anyone ever experience this and/or have ideas on how to fix it? > > Thanks. > > Mike > KF7MBK > > > _______________________________________________ App_rpt-users mailing list > App_rpt-users at 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. > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sat Sep 27 04:47:12 2014 From: doug at crompton.com (Doug Crompton) Date: Sat, 27 Sep 2014 00:47:12 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: , , , , , , Message-ID: The ctcss and carrier from are just bits so technically you could use either one and it would work the same. You do need to set the one you are not using to none. We always use carrierfrom even though it is ctcss that is driving it. I tried what you are doing here. I listened to myself iaxrpt from a distant node. Then I key the local PTT on my handheld into my local node. I immediately unkey and then keyed again before I heard the courtesy tone and it worked fine. Tried it several times. Why don't you eliminate the 1620 node in the test and iaxrpt directly to 1998 to see what happens there. This is acting like what you would see with an rxdelay setting but it should be 0 by default unless you somehow got that into your config. Specifically say rxdelay=0 in the 1998 rpt.conf context to be sure. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 21:15:03 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org Doug, this behavior happens even if I manually toggle the COR independent of the radio and audio so unless I'm not understanding, I can't see this being the radio. I tried changing unkeywait to 1000 but made no difference other than extending the time the PTT is active for the courtesy tone, and thus extending the window in which the COR line going high will be ignored. Seems that anything that extends the time that the PTT is active for the courtesy tone also extends the time that the COR is ignored. Just to make sure I'm not doing anything stupid or have an unconventional setuo,. my test setup is: HT -> DMK URI -> BBB (node 1998) -> ethernet -> Allstar on a VM (node 1620) -> IAX -> Zioper soft phone on laptop HT has audio in/out connected to the URI. PTT from the URI is not connected to the HT while testing. Signal from receive LED on the HT goes to COR URI input. I have the HT tuned to the weather frequency and I'm making/breaking the antenna connection to simulate picket fencing and I'm monitoring the audio received by the URI/BBB on the softphone. Bottom line is if the COR line drops, the courtesy pause and tone is instantly triggered, triggering the URI PTT. This works. But, if while the PTT is active, the COR line goes high again, the audio through the URI is not routed through until the COR line goes low* and high again after the PTT/courtesy tone is done transmitting. * when going low after getting ignored going high, no courtesy tone is triggered. Would it be useful/appropriate change carrierfrom to "no" and instead set ctcssfrom = usb and switch the radio output to the ctcss input on the URI and see if the problem still exists? Thanks for all the help!-Mike On Fri, Sep 26, 2014 at 8:37 PM, Doug Crompton wrote: Mike, You can try the changing the courtesy time wait then set back to duplex=1 The wait-times section This section allows the wait times for voice responses and other audio telemetry events to be adjusted. All wait times are in milliseconds. telemwait sets the time before sending the general audio telemetry responses used in the application which are not specifically defined below idwait sets the time to wait before sending ID audio telemetry unkeywait sets the amount of time to wait before sending the courtesy tone. This can be used to ensure breaking stations can get their turn calltermwait sets the amount of time between an autopatch disconnect and the audio telemetry message indicating the call has been terminated The unkeywait is the one to mess with. It is 400ms on the BBB by default. Make it longer like 1000 so it spans the dropout period you are seeing. Experiment with times. If that doesn't work I really think you should try a different radio. My thoughts are that it is some kind of recovery issue with TX. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 18:59:26 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org OK, so I did some more testing. I have routed the signal out of the radio to an NPN and switched from usbinvert to usb as suggested. This made little difference, but in this configuration I could make the RC work a little better bridging the dropouts. But still would end up not detecting carrier after a quick dropout even though the COR signal into the dongle was high. Duplex = 0 seems to eliminate the problem. Is there a setting to tell it how long to wait after COR dropped to start transmitting the courtesy tone? (though I suppose that would defeat the purpose of the duplex=1 setting) Note that I have the PTT disconnected for testing, so all I see is the red LED come on as soon as the COR out of the radio drops. Actually as I'm typing this and playing with it, I just noticed it appears if the COR is restored ANY time the PTT is active for the courtesy tone, it will ignore the COR line until it's dropped and brought back up AFTER the PTT is done. This behavior seems VERY repeatable, even with a cleanly restored COR signal, So it may have nothing to do with quick dropouts and everything to do with the courtesy tone.. Are there any settings that control this? The LED on the radio (and hence my COR input) is controlled by noise squelch opening. On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton wrote: Mike, Are you using PL or noise squelch or both? Like I said I have not seen this problem and I am using basically stock timing. Every time the PL or squelch goes untrue for a certain (short) duration you should hear a courtesy tone. Perhpas you should try duplex=0 just to see if there is an issue with TX recovery. Do you have another radio you can try? 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 10:18:19 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org The scope image in the OP shows there doesn't appear to be a problem with pulling hi or low, The transitions (without the RC) are very clean and go all the way to ground.. It seems like the URI is doing edge detection instead of level detection, and it's just missing fast edges. Wasn't sure if this was something that could be tweaked in software or if I'll have to put some external debounce logic on the line. On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: Mike, Before you change any timing make sure as Jon pointed out that your COS signal is going hard high and low on signal and non-signal. You might need a pullup. The URI is kind of weak in that regard. It should be TTL levels <.5 volt low and >2.5 volt high and preferably rail to rail. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 09:56:21 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org Doug, First: thanks for the excellent writeup on getting allstar running on the BBB. I used it to get up and running very quickly and is the setup I am having this issue with. I am running duplex =1 as well. I have not changed any timing values, (I'm essentially running the as-installed setup from the install image on your site) but I will take a look at them and see if I can make some changes for the better. Thanks!-Mike On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: From: doug at crompton.com To: kf7mbk at w7ara.net Subject: RE: [App_rpt-users] Fwd: COR signal getting confused Date: Fri, 26 Sep 2014 12:46:14 -0400 That is very strange. Have you changed any of the default timing values? Are you using simplex/duplex? Courtesy tone? Timing values could effect that. I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes and I have never seen that problem. I have one user who has a signal like you describe. He walks in a park with a handheld and he is often in and out. Also I assume you are not using any rxdelay? 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 08:50:51 -0700 To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Fwd: COR signal getting confused Resending since my initial post has been pending moderation for 2 days now and got no reply from the list owner email. I have modified an HT to bring out the receive LED signal and use it as the COR input to a DMK URI. It is a digital signal as viewed on a scope (i.e. very short slope in the transitions) This seems like it would work well and it does on strong signals. But on marginal signals where the LED may blink on and off quickly (like during picket fencing), it seems to confuse the URI (or the software) were it will start off good, but then a quick dropout of the COR signal will cause the software to no longer detect carrier, even though the signal on the COR input has been restored. Even if the input is solid high (or low in my case, I'm using usbinvert) it will not detect a carrier until there is another dropout of adequate time to "reset" it. I've tried putting a simple RC on the input but it didn't really help much. Seems the URI (or software) needs a significant minimum time between transitions to properly detect them, long enough that it would delay the carrier detection too much without a circuit more complex than an RC (i.e. something that would allow instant keyup, but delay the key down.) Linked is a scope image. https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg Carrier was detected until this signal dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is the signal out of the radio. Carrier was not detected after the 5th dropout even though the signal remained low. Anyone ever experience this and/or have ideas on how to fix it? Thanks. Mike KF7MBK _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sat Sep 27 04:49:15 2014 From: doug at crompton.com (Doug Crompton) Date: Sat, 27 Sep 2014 00:49:15 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: <54263DD3.8030600@gmail.com> References: , , , , , , <54263DD3.8030600@gmail.com> Message-ID: That command does work in simpleusb also but I think it is the opposite that is the problem. It is not responding. Worth a try I suppose. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Sat, 27 Sep 2014 00:32:19 -0400 From: kp4tr.ramon at gmail.com To: doug at crompton.com; kf7mbk at w7ara.net CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Fwd: COR signal getting confused Try this in usbradio.conf (this is not recognized in simpleusb): rxondelay=25 ; This will instruct the usbradio driver to ignore the COR line ; for a specified number of 20mSec intervals following the release of PTT. On 9/26/2014 11:37 PM, Doug Crompton wrote: Mike, You can try the changing the courtesy time wait then set back to duplex=1 The wait-times section This section allows the wait times for voice responses and other audio telemetry events to be adjusted. All wait times are in milliseconds. telemwait sets the time before sending the general audio telemetry responses used in the application which are not specifically defined below idwait sets the time to wait before sending ID audio telemetry unkeywait sets the amount of time to wait before sending the courtesy tone. This can be used to ensure breaking stations can get their turn calltermwait sets the amount of time between an autopatch disconnect and the audio telemetry message indicating the call has been terminated The unkeywait is the one to mess with. It is 400ms on the BBB by default. Make it longer like 1000 so it spans the dropout period you are seeing. Experiment with times. If that doesn't work I really think you should try a different radio. My thoughts are that it is some kind of recovery issue with TX. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 18:59:26 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org OK, so I did some more testing. I have routed the signal out of the radio to an NPN and switched from usbinvert to usb as suggested. This made little difference, but in this configuration I could make the RC work a little better bridging the dropouts. But still would end up not detecting carrier after a quick dropout even though the COR signal into the dongle was high. Duplex = 0 seems to eliminate the problem. Is there a setting to tell it how long to wait after COR dropped to start transmitting the courtesy tone? (though I suppose that would defeat the purpose of the duplex=1 setting) Note that I have the PTT disconnected for testing, so all I see is the red LED come on as soon as the COR out of the radio drops. Actually as I'm typing this and playing with it, I just noticed it appears if the COR is restored ANY time the PTT is active for the courtesy tone, it will ignore the COR line until it's dropped and brought back up AFTER the PTT is done. This behavior seems VERY repeatable, even with a cleanly restored COR signal, So it may have nothing to do with quick dropouts and everything to do with the courtesy tone.. Are there any settings that control this? The LED on the radio (and hence my COR input) is controlled by noise squelch opening. On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton wrote: Mike, Are you using PL or noise squelch or both? Like I said I have not seen this problem and I am using basically stock timing. Every time the PL or squelch goes untrue for a certain (short) duration you should hear a courtesy tone. Perhpas you should try duplex=0 just to see if there is an issue with TX recovery. Do you have another radio you can try? 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 10:18:19 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org The scope image in the OP shows there doesn't appear to be a problem with pulling hi or low, The transitions (without the RC) are very clean and go all the way to ground.. It seems like the URI is doing edge detection instead of level detection, and it's just missing fast edges. Wasn't sure if this was something that could be tweaked in software or if I'll have to put some external debounce logic on the line. On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: Mike, Before you change any timing make sure as Jon pointed out that your COS signal is going hard high and low on signal and non-signal. You might need a pullup. The URI is kind of weak in that regard. It should be TTL levels <.5 volt low and >2.5 volt high and preferably rail to rail. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 09:56:21 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org Doug, First: thanks for the excellent writeup on getting allstar running on the BBB. I used it to get up and running very quickly and is the setup I am having this issue with. I am running duplex =1 as well. I have not changed any timing values, (I'm essentially running the as-installed setup from the install image on your site) but I will take a look at them and see if I can make some changes for the better. Thanks! -Mike On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: From: doug at crompton.com To: kf7mbk at w7ara.net Subject: RE: [App_rpt-users] Fwd: COR signal getting confused Date: Fri, 26 Sep 2014 12:46:14 -0400 That is very strange. Have you changed any of the default timing values? Are you using simplex/duplex? Courtesy tone? Timing values could effect that. I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes and I have never seen that problem. I have one user who has a signal like you describe. He walks in a park with a handheld and he is often in and out. Also I assume you are not using any rxdelay? 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 08:50:51 -0700 To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Fwd: COR signal getting confused Resending since my initial post has been pending moderation for 2 days now and got no reply from the list owner email. I have modified an HT to bring out the receive LED signal and use it as the COR input to a DMK URI. It is a digital signal as viewed on a scope (i.e. very short slope in the transitions) This seems like it would work well and it does on strong signals. But on marginal signals where the LED may blink on and off quickly (like during picket fencing), it seems to confuse the URI (or the software) were it will start off good, but then a quick dropout of the COR signal will cause the software to no longer detect carrier, even though the signal on the COR input has been restored. Even if the input is solid high (or low in my case, I'm using usbinvert) it will not detect a carrier until there is another dropout of adequate time to "reset" it. I've tried putting a simple RC on the input but it didn't really help much. Seems the URI (or software) needs a significant minimum time between transitions to properly detect them, long enough that it would delay the carrier detection too much without a circuit more complex than an RC (i.e. something that would allow instant keyup, but delay the key down.) Linked is a scope image. https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg Carrier was detected until this signal dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is the signal out of the radio. Carrier was not detected after the 5th dropout even though the signal remained low. Anyone ever experience this and/or have ideas on how to fix it? Thanks. Mike KF7MBK _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sat Sep 27 05:44:40 2014 From: doug at crompton.com (Doug Crompton) Date: Sat, 27 Sep 2014 01:44:40 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: , , , , , , , , , , , , , , , <54263DD3.8030600@gmail.com>, Message-ID: rxdelay delays qualifying the COS signal until the number of milliseconds after PTT release. This would be true for the courtesy tone also because any TX could cause a false COS trigger if you had that problem. Maybe you just need to disable the courtesy tone. 73 Doug WA3DSP http://www.crompton.com/hamradio From: doug at crompton.com To: app_rpt-users at ohnosec.org Date: Sat, 27 Sep 2014 00:49:15 -0400 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused That command does work in simpleusb also but I think it is the opposite that is the problem. It is not responding. Worth a try I suppose. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Sat, 27 Sep 2014 00:32:19 -0400 From: kp4tr.ramon at gmail.com To: doug at crompton.com; kf7mbk at w7ara.net CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Fwd: COR signal getting confused Try this in usbradio.conf (this is not recognized in simpleusb): rxondelay=25 ; This will instruct the usbradio driver to ignore the COR line ; for a specified number of 20mSec intervals following the release of PTT. On 9/26/2014 11:37 PM, Doug Crompton wrote: Mike, You can try the changing the courtesy time wait then set back to duplex=1 The wait-times section This section allows the wait times for voice responses and other audio telemetry events to be adjusted. All wait times are in milliseconds. telemwait sets the time before sending the general audio telemetry responses used in the application which are not specifically defined below idwait sets the time to wait before sending ID audio telemetry unkeywait sets the amount of time to wait before sending the courtesy tone. This can be used to ensure breaking stations can get their turn calltermwait sets the amount of time between an autopatch disconnect and the audio telemetry message indicating the call has been terminated The unkeywait is the one to mess with. It is 400ms on the BBB by default. Make it longer like 1000 so it spans the dropout period you are seeing. Experiment with times. If that doesn't work I really think you should try a different radio. My thoughts are that it is some kind of recovery issue with TX. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 18:59:26 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org OK, so I did some more testing. I have routed the signal out of the radio to an NPN and switched from usbinvert to usb as suggested. This made little difference, but in this configuration I could make the RC work a little better bridging the dropouts. But still would end up not detecting carrier after a quick dropout even though the COR signal into the dongle was high. Duplex = 0 seems to eliminate the problem. Is there a setting to tell it how long to wait after COR dropped to start transmitting the courtesy tone? (though I suppose that would defeat the purpose of the duplex=1 setting) Note that I have the PTT disconnected for testing, so all I see is the red LED come on as soon as the COR out of the radio drops. Actually as I'm typing this and playing with it, I just noticed it appears if the COR is restored ANY time the PTT is active for the courtesy tone, it will ignore the COR line until it's dropped and brought back up AFTER the PTT is done. This behavior seems VERY repeatable, even with a cleanly restored COR signal, So it may have nothing to do with quick dropouts and everything to do with the courtesy tone.. Are there any settings that control this? The LED on the radio (and hence my COR input) is controlled by noise squelch opening. On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton wrote: Mike, Are you using PL or noise squelch or both? Like I said I have not seen this problem and I am using basically stock timing. Every time the PL or squelch goes untrue for a certain (short) duration you should hear a courtesy tone. Perhpas you should try duplex=0 just to see if there is an issue with TX recovery. Do you have another radio you can try? 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 10:18:19 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org The scope image in the OP shows there doesn't appear to be a problem with pulling hi or low, The transitions (without the RC) are very clean and go all the way to ground.. It seems like the URI is doing edge detection instead of level detection, and it's just missing fast edges. Wasn't sure if this was something that could be tweaked in software or if I'll have to put some external debounce logic on the line. On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: Mike, Before you change any timing make sure as Jon pointed out that your COS signal is going hard high and low on signal and non-signal. You might need a pullup. The URI is kind of weak in that regard. It should be TTL levels <.5 volt low and >2.5 volt high and preferably rail to rail. 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 09:56:21 -0700 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused To: doug at crompton.com CC: app_rpt-users at ohnosec.org Doug, First: thanks for the excellent writeup on getting allstar running on the BBB. I used it to get up and running very quickly and is the setup I am having this issue with. I am running duplex =1 as well. I have not changed any timing values, (I'm essentially running the as-installed setup from the install image on your site) but I will take a look at them and see if I can make some changes for the better. Thanks! -Mike On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: From: doug at crompton.com To: kf7mbk at w7ara.net Subject: RE: [App_rpt-users] Fwd: COR signal getting confused Date: Fri, 26 Sep 2014 12:46:14 -0400 That is very strange. Have you changed any of the default timing values? Are you using simplex/duplex? Courtesy tone? Timing values could effect that. I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes and I have never seen that problem. I have one user who has a signal like you describe. He walks in a park with a handheld and he is often in and out. Also I assume you are not using any rxdelay? 73 Doug WA3DSP http://www.crompton.com/hamradio From: kf7mbk at w7ara.net Date: Fri, 26 Sep 2014 08:50:51 -0700 To: app_rpt-users at ohnosec.org Subject: [App_rpt-users] Fwd: COR signal getting confused Resending since my initial post has been pending moderation for 2 days now and got no reply from the list owner email. I have modified an HT to bring out the receive LED signal and use it as the COR input to a DMK URI. It is a digital signal as viewed on a scope (i.e. very short slope in the transitions) This seems like it would work well and it does on strong signals. But on marginal signals where the LED may blink on and off quickly (like during picket fencing), it seems to confuse the URI (or the software) were it will start off good, but then a quick dropout of the COR signal will cause the software to no longer detect carrier, even though the signal on the COR input has been restored. Even if the input is solid high (or low in my case, I'm using usbinvert) it will not detect a carrier until there is another dropout of adequate time to "reset" it. I've tried putting a simple RC on the input but it didn't really help much. Seems the URI (or software) needs a significant minimum time between transitions to properly detect them, long enough that it would delay the carrier detection too much without a circuit more complex than an RC (i.e. something that would allow instant keyup, but delay the key down.) Linked is a scope image. https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg Carrier was detected until this signal dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is the signal out of the radio. Carrier was not detected after the 5th dropout even though the signal remained low. Anyone ever experience this and/or have ideas on how to fix it? Thanks. Mike KF7MBK _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. < /div > _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike at midnighteng.com Sat Sep 27 08:30:17 2014 From: mike at midnighteng.com (mike at midnighteng.com) Date: Sat, 27 Sep 2014 01:30:17 -0700 Subject: [App_rpt-users] =?utf-8?q?Fwd=3A_COR_signal_getting_confused?= Message-ID: <20140927013017.71befee5dbd13c5325dd1a521b4e73ee.1dcfc02a18.wbe@email06.secureserver.net> An HTML attachment was scrubbed... URL: From jrorke at cogeco.ca Sat Sep 27 12:23:18 2014 From: jrorke at cogeco.ca (REDBUTTON_CTRL) Date: Sat, 27 Sep 2014 08:23:18 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused - couple of questions. In-Reply-To: <20140927013017.71befee5dbd13c5325dd1a521b4e73ee.1dcfc02a18.wbe@email06.secureserver.net> References: <20140927013017.71befee5dbd13c5325dd1a521b4e73ee.1dcfc02a18.wbe@email06.secureserver.net> Message-ID: <5426AC36.8070107@cogeco.ca> Just a quick question here. So you have duplex =1 in rpt.conf and in usbradio duplex=0 right? You need to make sure the duplex setting in both the rpt and usberadio.conf files are set to a half duplex mode. How fast is the green light blinking on the URI? What hardware is the node on? Jon On 9/27/2014 4:30 AM, mike at midnighteng.com wrote: > > Mike, > > May I ask the specific radio involved here ? > > ...mike/kb8jnm > > -------- Original Message -------- > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > From: Doug Crompton > > Date: Sat, September 27, 2014 1:44 am > To: "app_rpt-users at ohnosec.org " > > > > rxdelay delays qualifying the COS signal until the number of > milliseconds after PTT release. This would be true for the > courtesy tone also because any TX could cause a false COS trigger > if you had that problem. > > Maybe you just need to disable the courtesy tone. > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: doug at crompton.com > To: app_rpt-users at ohnosec.org > Date: Sat, 27 Sep 2014 00:49:15 -0400 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > > That command does work in simpleusb also but I think it is the > opposite that is the problem. It is not responding. Worth a try I > suppose. > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > Date: Sat, 27 Sep 2014 00:32:19 -0400 > From: kp4tr.ramon at gmail.com > To: doug at crompton.com ; kf7mbk at w7ara.net > > CC: app_rpt-users at ohnosec.org > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > > Try this in usbradio.conf (this is not recognized in simpleusb): > > rxondelay=25 ; This will instruct the usbradio driver > to ignore the COR line > ; for a specified number of 20mSec > intervals following the release of PTT. > > > On 9/26/2014 11:37 PM, Doug Crompton wrote: > > Mike, > > You can try the changing the courtesy time wait then set back > to duplex=1 > > The wait-times section > This section allows the wait times for voice responses and > other audio telemetry events to be adjusted. All wait times > are in milliseconds. > > */telemwait/* sets the time before sending the general audio > telemetry responses used in the application which are not > specifically defined below > */idwait/* sets the time to wait before sending ID audio telemetry > */unkeywait/* sets the amount of time to wait before sending > the courtesy tone. This can be used to ensure breaking > stations can get their turn > */calltermwait/* sets the amount of time between an autopatch > disconnect and the audio telemetry message indicating the call > has been terminated > > The unkeywait is the one to mess with. It is 400ms on the BBB > by default. Make it longer like 1000 so it spans the dropout > period you are seeing. Experiment with times. > > If that doesn't work I really think you should try a different > radio. My thoughts are that it is some kind of recovery issue > with TX. > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 18:59:26 -0700 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > OK, so I did some more testing. > > I have routed the signal out of the radio to an NPN and > switched from usbinvert to usb as suggested. This made little > difference, but in this configuration I could make the RC work > a little better bridging the dropouts. But still would end up > not detecting carrier after a quick dropout even though the > COR signal into the dongle was high. > > Duplex = 0 seems to eliminate the problem. Is there a setting > to tell it how long to wait after COR dropped to start > transmitting the courtesy tone? (though I suppose that would > defeat the purpose of the duplex=1 setting) Note that I have > the PTT disconnected for testing, so all I see is the red LED > come on as soon as the COR out of the radio drops. > > Actually as I'm typing this and playing with it, I just > noticed it appears if the COR is restored ANY time the PTT is > active for the courtesy tone, it will ignore the COR line > until it's dropped and brought back up AFTER the PTT is done. > This behavior seems VERY repeatable, even with a cleanly > restored COR signal, So it may have nothing to do with quick > dropouts and everything to do with the courtesy tone.. > > Are there any settings that control this? > > The LED on the radio (and hence my COR input) is controlled > by noise squelch opening. > > > > > > > On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton > > wrote: > > Mike, > > Are you using PL or noise squelch or both? Like I said I > have not seen this problem and I am using basically stock > timing. Every time the PL or squelch goes untrue for a > certain (short) duration you should hear a courtesy tone. > Perhpas you should try duplex=0 just to see if there is an > issue with TX recovery. Do you have another radio you can > try? > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 10:18:19 -0700 > > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > > The scope image in the OP shows there doesn't appear to be > a problem with pulling hi or low, The transitions > (without the RC) are very clean and go all the way to > ground.. It seems like the URI is doing edge detection > instead of level detection, and it's just missing fast > edges. Wasn't sure if this was something that could be > tweaked in software or if I'll have to put some external > debounce logic on the line. > > > On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton > > wrote: > > Mike, > > Before you change any timing make sure as Jon pointed > out that your COS signal is going hard high and low on > signal and non-signal. You might need a pullup. The > URI is kind of weak in that regard. It should be TTL > levels <.5 volt low and >2.5 volt high and preferably > rail to rail. > > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 09:56:21 -0700 > Subject: Re: [App_rpt-users] Fwd: COR signal getting > confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > > > Doug, > > First: thanks for the excellent writeup on getting > allstar running on the BBB. I used it to get up and > running very quickly and is the setup I am having this > issue with. > > I am running duplex =1 as well. I have not changed > any timing values, (I'm essentially running the > as-installed setup from the install image on your > site) but I will take a look at them and see if I can > make some changes for the better. > > Thanks! > -Mike > > > > > > On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton > > wrote: > > ------------------------------------------------------------------------ > From: doug at crompton.com > To: kf7mbk at w7ara.net > Subject: RE: [App_rpt-users] Fwd: COR signal > getting confused > Date: Fri, 26 Sep 2014 12:46:14 -0400 > > That is very strange. Have you changed any of the > default timing values? Are you using > simplex/duplex? Courtesy tone? Timing values could > effect that. > > I use simplex with courtesy tone (duplex=1 in > rpt.conf) on several nodes and I have never seen > that problem. I have one user who has a signal > like you describe. He walks in a park with a > handheld and he is often in and out. > > Also I assume you are not using any rxdelay? > > *73 Doug > WA3DSP > http://www.crompton.com/hamradio* > > > ------------------------------------------------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 08:50:51 -0700 > To: app_rpt-users at ohnosec.org > > Subject: [App_rpt-users] Fwd: COR signal getting > confused > > > Resending since my initial post has been pending > moderation for 2 days now and got no reply from > the list owner email. > > I have modified an HT to bring out the receive LED > signal and use it > as the COR input to a DMK URI. It is a digital > signal as viewed on a > scope (i.e. very short slope in the transitions) > This seems like it > would work well and it does on strong signals. But > on marginal signals > where the LED may blink on and off quickly (like > during picket > fencing), it seems to confuse the URI (or the > software) were it will > start off good, but then a quick dropout of the > COR signal will cause > the software to no longer detect carrier, even > though the signal on > the COR input has been restored. Even if the > input is solid high (or > low in my case, I'm using usbinvert) it will not > detect a carrier > until there is another dropout of adequate time to > "reset" it. > > I've tried putting a simple RC on the input but it > didn't really help > much. Seems the URI (or software) needs a > significant minimum time > between transitions to properly detect them, long > enough that it would > delay the carrier detection too much without a > circuit more complex > than an RC (i.e. something that would allow > instant keyup, but delay > the key down.) > > Linked is a scope image. > > https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg > > Carrier was detected until this signal > dropout event. Ch A is my RC filtered signal sent > to the URI, Ch B is > the signal out of the radio. Carrier was not > detected after the 5th > dropout even though the signal remained low. > > Anyone ever experience this and/or have ideas on > how to fix it? > > Thanks. > > Mike > KF7MBK > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. > > > < /div > > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visithttp://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 at 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 at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kk6ecm at gmail.com Sat Sep 27 15:15:38 2014 From: kk6ecm at gmail.com (Bob) Date: Sat, 27 Sep 2014 08:15:38 -0700 Subject: [App_rpt-users] FW: Node numbers Message-ID: <581DE9072B0648158FB14E176FCAFD9D@ThePykesHP> I thought I heard "node 26070 connected to node 28765" this morning about 0630, then again when disconnected a few moments later (the latter node being mine, and I had gotten out of CLI> last night, not recording the connection). When I attempted to look up node 26070 I found no nodes between the 2xxx series and 27000. Don't think I was dreaming... but what happened to the nodes in between? Where could this contact have originated? Thanks, Bob kk6ecm -------------- next part -------------- An HTML attachment was scrubbed... URL: From kf7mbk at w7ara.net Sat Sep 27 15:47:11 2014 From: kf7mbk at w7ara.net (Mike M) Date: Sat, 27 Sep 2014 08:47:11 -0700 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: Message-ID: I'm starting to think its the URI. First, I got rid of all the components (transistor and RC) because they made little difference and don't want the added complexity. I went back to usbinvert. I brought the radio and URI to the 1620 node on the VM (basically a stock install of ACID) and connected Zoiper directly to the node. This left the BBB and its configuration completely out of the loop and I still got the same behavior. Next I reconnected the URI and radio to the BBB and connected directly to it via Zioper (I didn't do this before because I was having trouble connecting Zoiper to the BBB, but I got that figured out) and it's still the same behavior. And just to eliminate the radio, I disconnected it completely, connected the COR input to a pullup, and grounded it by hand. When I ground the COR line (usbinvert), I can hear slight background noise through Zoiper and when I unground it, the courtesy tone is triggered (URI PTT active as well) and then the background noise goes away when the CT is done. But if I ground the COR line while the courtesy tone is playing, it ignores the COR and does not pass audio to zioper until I cycle the COR line again. And finally I tried using the CTCSS input, same exact behavior. I know there is a URI test program from DMK, but I didn't really see a way to simply read out the status of the inputs, just automated tests requiring a loopback. -Mike On Fri, Sep 26, 2014 at 9:47 PM, Doug Crompton wrote: > The ctcss and carrier from are just bits so technically you could use > either one and it would work the same. You do need to set the one you are > not using to none. We always use carrierfrom even though it is ctcss that > is driving it. > > I tried what you are doing here. I listened to myself iaxrpt from a > distant node. Then I key the local PTT on my handheld into my local node. I > immediately unkey and then keyed again before I heard the courtesy tone and > it worked fine. Tried it several times. > > Why don't you eliminate the 1620 node in the test and iaxrpt directly to > 1998 to see what happens there. > > This is acting like what you would see with an rxdelay setting but it > should be 0 by default unless you somehow got that into your config. > Specifically say rxdelay=0 in the 1998 rpt.conf context to be sure. > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 21:15:03 -0700 > > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > Doug, this behavior happens even if I manually toggle the COR independent > of the radio and audio so unless I'm not understanding, I can't see this > being the radio. > > I tried changing unkeywait to 1000 but made no difference other than > extending the time the PTT is active for the courtesy tone, and thus > extending the window in which the COR line going high will be ignored. > Seems that anything that extends the time that the PTT is active for the > courtesy tone also extends the time that the COR is ignored. > > Just to make sure I'm not doing anything stupid or have an unconventional > setuo,. my test setup is: > > HT -> DMK URI -> BBB (node 1998) -> ethernet -> Allstar on a VM (node > 1620) -> IAX -> Zioper soft phone on laptop > > HT has audio in/out connected to the URI. PTT from the URI is not > connected to the HT while testing. Signal from receive LED on the HT goes > to COR URI input. > > I have the HT tuned to the weather frequency and I'm making/breaking the > antenna connection to simulate picket fencing and I'm monitoring the audio > received by the URI/BBB on the softphone. > > Bottom line is if the COR line drops, the courtesy pause and tone is > instantly triggered, triggering the URI PTT. This works. But, if while the > PTT is active, the COR line goes high again, the audio through the URI is > not routed through until the COR line goes low* and high again after the > PTT/courtesy tone is done transmitting. > > * when going low after getting ignored going high, no courtesy tone is > triggered. > > > Would it be useful/appropriate change carrierfrom to "no" and instead set > ctcssfrom = usb and switch the radio output to the ctcss input on the URI > and see if the problem still exists? > > Thanks for all the help! > -Mike > > > > On Fri, Sep 26, 2014 at 8:37 PM, Doug Crompton wrote: > > Mike, > > You can try the changing the courtesy time wait then set back to duplex=1 > > The wait-times section > This section allows the wait times for voice responses and other audio > telemetry events to be adjusted. All wait times are in milliseconds. > > *telemwait* sets the time before sending the general audio telemetry > responses used in the application which are not specifically defined below > *idwait* sets the time to wait before sending ID audio telemetry > *unkeywait* sets the amount of time to wait before sending the courtesy > tone. This can be used to ensure breaking stations can get their turn > *calltermwait* sets the amount of time between an autopatch disconnect > and the audio telemetry message indicating the call has been terminated > > The unkeywait is the one to mess with. It is 400ms on the BBB by default. > Make it longer like 1000 so it spans the dropout period you are seeing. > Experiment with times. > > If that doesn't work I really think you should try a different radio. My > thoughts are that it is some kind of recovery issue with TX. > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 18:59:26 -0700 > > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > OK, so I did some more testing. > > I have routed the signal out of the radio to an NPN and switched from > usbinvert to usb as suggested. This made little difference, but in this > configuration I could make the RC work a little better bridging the > dropouts. But still would end up not detecting carrier after a quick > dropout even though the COR signal into the dongle was high. > > Duplex = 0 seems to eliminate the problem. Is there a setting to tell it > how long to wait after COR dropped to start transmitting the courtesy tone? > (though I suppose that would defeat the purpose of the duplex=1 setting) > Note that I have the PTT disconnected for testing, so all I see is the red > LED come on as soon as the COR out of the radio drops. > > Actually as I'm typing this and playing with it, I just noticed it appears > if the COR is restored ANY time the PTT is active for the courtesy tone, it > will ignore the COR line until it's dropped and brought back up AFTER the > PTT is done. This behavior seems VERY repeatable, even with a cleanly > restored COR signal, So it may have nothing to do with quick dropouts and > everything to do with the courtesy tone.. > > Are there any settings that control this? > > The LED on the radio (and hence my COR input) is controlled by noise > squelch opening. > > > > > > > On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton wrote: > > Mike, > > Are you using PL or noise squelch or both? Like I said I have not seen > this problem and I am using basically stock timing. Every time the PL or > squelch goes untrue for a certain (short) duration you should hear a > courtesy tone. Perhpas you should try duplex=0 just to see if there is an > issue with TX recovery. Do you have another radio you can try? > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 10:18:19 -0700 > > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > The scope image in the OP shows there doesn't appear to be a problem with > pulling hi or low, The transitions (without the RC) are very clean and go > all the way to ground.. It seems like the URI is doing edge detection > instead of level detection, and it's just missing fast edges. Wasn't sure > if this was something that could be tweaked in software or if I'll have to > put some external debounce logic on the line. > > > On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: > > Mike, > > Before you change any timing make sure as Jon pointed out that your COS > signal is going hard high and low on signal and non-signal. You might need > a pullup. The URI is kind of weak in that regard. It should be TTL levels > <.5 volt low and >2.5 volt high and preferably rail to rail. > > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 09:56:21 -0700 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > To: doug at crompton.com > CC: app_rpt-users at ohnosec.org > > > Doug, > > First: thanks for the excellent writeup on getting allstar running on the > BBB. I used it to get up and running very quickly and is the setup I am > having this issue with. > > I am running duplex =1 as well. I have not changed any timing values, > (I'm essentially running the as-installed setup from the install image on > your site) but I will take a look at them and see if I can make some > changes for the better. > > Thanks! > -Mike > > > > > > On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: > > ------------------------------ > From: doug at crompton.com > To: kf7mbk at w7ara.net > Subject: RE: [App_rpt-users] Fwd: COR signal getting confused > Date: Fri, 26 Sep 2014 12:46:14 -0400 > > That is very strange. Have you changed any of the default timing values? > Are you using simplex/duplex? Courtesy tone? Timing values could effect > that. > > I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes > and I have never seen that problem. I have one user who has a signal like > you describe. He walks in a park with a handheld and he is often in and out. > > Also I assume you are not using any rxdelay? > > > > *73 DougWA3DSPhttp://www.crompton.com/hamradio > * > > > ------------------------------ > From: kf7mbk at w7ara.net > Date: Fri, 26 Sep 2014 08:50:51 -0700 > To: app_rpt-users at ohnosec.org > Subject: [App_rpt-users] Fwd: COR signal getting confused > > > Resending since my initial post has been pending moderation for 2 days now > and got no reply from the list owner email. > > I have modified an HT to bring out the receive LED signal and use it > as the COR input to a DMK URI. It is a digital signal as viewed on a > scope (i.e. very short slope in the transitions) This seems like it > would work well and it does on strong signals. But on marginal signals > where the LED may blink on and off quickly (like during picket > fencing), it seems to confuse the URI (or the software) were it will > start off good, but then a quick dropout of the COR signal will cause > the software to no longer detect carrier, even though the signal on > the COR input has been restored. Even if the input is solid high (or > low in my case, I'm using usbinvert) it will not detect a carrier > until there is another dropout of adequate time to "reset" it. > > I've tried putting a simple RC on the input but it didn't really help > much. Seems the URI (or software) needs a significant minimum time > between transitions to properly detect them, long enough that it would > delay the carrier detection too much without a circuit more complex > than an RC (i.e. something that would allow instant keyup, but delay > the key down.) > > Linked is a scope image. > > > https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg > > Carrier was detected until this signal > dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is > the signal out of the radio. Carrier was not detected after the 5th > dropout even though the signal remained low. > > Anyone ever experience this and/or have ideas on how to fix it? > > Thanks. > > Mike > KF7MBK > > > _______________________________________________ App_rpt-users mailing list > App_rpt-users at 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. > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jrorke at cogeco.ca Sat Sep 27 16:11:19 2014 From: jrorke at cogeco.ca (REDBUTTON_CTRL) Date: Sat, 27 Sep 2014 12:11:19 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: Message-ID: <5426E1A7.8040804@cogeco.ca> Ok In a bid to understand what it is you think is wrong let me clarify from what you are saying below. Your node is set up for duplex=1 (half duplex with courtesy beep and tail) right? And the problem you are seeing is the node will not receive a signal when it is transmitting the courtesy beep or tail - right? If the above is correct, then this configuration cannot receive a signal while it is transmitting. This is normal for this configuration. If your radio is portable or mobile radio, then your radio can only receive or transmit but not both simultaneously. So in duplex =1 mode the URI assumes your receiver is active if the node isnt transmitting. So the node ignores all receiver activity while its transmitting. Once the tail is gone then it will listen to thereceiver cor line. For some reason from you explanation below you are expecting the node to receive in full duplex. Unless the radio you have connected is capable of full duplex, this wont work. If the radio connected to the URI is a pair of radios or a duplexed base station and if you set the duplex setting to duplex=2 in rpt conf and duplex =1 in usbradio then it will receive while its transmitting. Hope I understand this right and this helps. Jon VA3RQ On 9/27/2014 11:47 AM, Mike M wrote: > I'm starting to think its the URI. > > First, I got rid of all the components (transistor and RC) because > they made little difference and don't want the added complexity. I > went back to usbinvert. > I brought the radio and URI to the 1620 node on the VM (basically a > stock install of ACID) and connected Zoiper directly to the node. > This left the BBB and its configuration completely out of the loop and > I still got the same behavior. > > Next I reconnected the URI and radio to the BBB and connected directly > to it via Zioper (I didn't do this before because I was having trouble > connecting Zoiper to the BBB, but I got that figured out) and it's > still the same behavior. > > And just to eliminate the radio, I disconnected it completely, > connected the COR input to a pullup, and grounded it by hand. When I > ground the COR line (usbinvert), I can hear slight background noise > through Zoiper and when I unground it, the courtesy tone is triggered > (URI PTT active as well) and then the background noise goes away when > the CT is done. But if I ground the COR line while the courtesy tone > is playing, it ignores the COR and does not pass audio to zioper until > I cycle the COR line again. > > And finally I tried using the CTCSS input, same exact behavior. > > I know there is a URI test program from DMK, but I didn't really see a > way to simply read out the status of the inputs, just automated tests > requiring a loopback. > > -Mike > > sage to the list detailing the problem. From jrorke at cogeco.ca Sat Sep 27 16:25:20 2014 From: jrorke at cogeco.ca (REDBUTTON_CTRL) Date: Sat, 27 Sep 2014 12:25:20 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: <5426E1A7.8040804@cogeco.ca> References: <5426E1A7.8040804@cogeco.ca> Message-ID: <5426E4F0.4090500@cogeco.ca> I should further clarify the "duplex=1 mode" settings. This is the mode when in rpt.conf has duplex set to 1 and usbradio has duplex=0. This config is a half duplex mode but gives a courtesy beep and tail after RX activity. The duplex=1 mode in rpt.conf tells the node it is in half duplex mode but sends a courtesy beep and a tail after it receives a signal from the node receiver. The duplex=0 in usbradio tells the URI hardware that your radio is only half duplex and cannot transmit while receiving. The setup for half duplex nodes is kinda nice as it tells the user that they are making the sinplex node. A setting of duplex =0 in rpt conf and duplex =0 in usbradio is the same as above with no courtesy tone and no tail. It works just as well as above but there is no local feedback to let you know if you are hitting the simplex node or not. Jon VA3RQ On 9/27/2014 12:11 PM, REDBUTTON_CTRL wrote: > Ok In a bid to understand what it is you think is wrong let me clarify > from what you are saying below. > Your node is set up for duplex=1 (half duplex with courtesy beep and > tail) right? > And the problem you are seeing is the node will not receive a signal > when it is transmitting the courtesy beep or tail - right? > > If the above is correct, then this configuration cannot receive a > signal while it is transmitting. This is normal for this configuration. > If your radio is portable or mobile radio, then your radio can only > receive or transmit but not both simultaneously. So in duplex =1 > mode the URI assumes your receiver is active if the node isnt > transmitting. So the node ignores all receiver activity while its > transmitting. Once the tail is gone then it will listen to thereceiver > cor line. > > For some reason from you explanation below you are expecting the node > to receive in full duplex. Unless the radio you have connected is > capable of full duplex, this wont work. If the radio connected to the > URI is a pair of radios or a duplexed base station and if you set the > duplex setting to duplex=2 in rpt conf and duplex =1 in usbradio then > it will receive while its transmitting. > > Hope I understand this right and this helps. > > Jon VA3RQ > > On 9/27/2014 11:47 AM, Mike M wrote: >> I'm starting to think its the URI. >> >> First, I got rid of all the components (transistor and RC) because >> they made little difference and don't want the added complexity. I >> went back to usbinvert. >> I brought the radio and URI to the 1620 node on the VM (basically a >> stock install of ACID) and connected Zoiper directly to the node. >> This left the BBB and its configuration completely out of the loop >> and I still got the same behavior. >> >> Next I reconnected the URI and radio to the BBB and connected >> directly to it via Zioper (I didn't do this before because I was >> having trouble connecting Zoiper to the BBB, but I got that figured >> out) and it's still the same behavior. >> >> And just to eliminate the radio, I disconnected it completely, >> connected the COR input to a pullup, and grounded it by hand. When I >> ground the COR line (usbinvert), I can hear slight background noise >> through Zoiper and when I unground it, the courtesy tone is triggered >> (URI PTT active as well) and then the background noise goes away when >> the CT is done. But if I ground the COR line while the courtesy tone >> is playing, it ignores the COR and does not pass audio to zioper >> until I cycle the COR line again. >> >> And finally I tried using the CTCSS input, same exact behavior. >> >> I know there is a URI test program from DMK, but I didn't really see >> a way to simply read out the status of the inputs, just automated >> tests requiring a loopback. >> >> -Mike >> >> sage to the list detailing the problem. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. From kf7mbk at w7ara.net Sun Sep 28 16:52:05 2014 From: kf7mbk at w7ara.net (Mike M) Date: Sun, 28 Sep 2014 09:52:05 -0700 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: Message-ID: > Your node is set up for duplex=1 (half duplex with courtesy beep and tail) right? Correct, in both conf files. > And the problem you are seeing is the node will not receive a signal when it is transmitting the courtesy beep or tail - right? While true, this isn't the actual problem. I drew a diagram which will hopefully be worth 1000 words. https://lh3.googleusercontent.com/-q3CmjOEBsMA/VCg72OZCNbI/AAAAAAAAPSc/wCZoJYknoLU/s822/COR%2520problem.png Though I just realized, I may have the order of the silence and the tone backwards. Regardless, it is not the important issue. -Mike From: REDBUTTON_CTRL To: app_rpt-users at ohnosec.org Cc: Date: Sat, 27 Sep 2014 12:11:19 -0400 Subject: Re: [App_rpt-users] Fwd: COR signal getting confused Ok In a bid to understand what it is you think is wrong let me clarify from what you are saying below. Your node is set up for duplex=1 (half duplex with courtesy beep and tail) right? And the problem you are seeing is the node will not receive a signal when it is transmitting the courtesy beep or tail - right? If the above is correct, then this configuration cannot receive a signal while it is transmitting. This is normal for this configuration. If your radio is portable or mobile radio, then your radio can only receive or transmit but not both simultaneously. So in duplex =1 mode the URI assumes your receiver is active if the node isnt transmitting. So the node ignores all receiver activity while its transmitting. Once the tail is gone then it will listen to thereceiver cor line. For some reason from you explanation below you are expecting the node to receive in full duplex. Unless the radio you have connected is capable of full duplex, this wont work. If the radio connected to the URI is a pair of radios or a duplexed base station and if you set the duplex setting to duplex=2 in rpt conf and duplex =1 in usbradio then it will receive while its transmitting. Hope I understand this right and this helps. Jon VA3RQ On Sat, Sep 27, 2014 at 8:47 AM, Mike M wrote: > I'm starting to think its the URI. > > First, I got rid of all the components (transistor and RC) because they made > little difference and don't want the added complexity. I went back to > usbinvert. > I brought the radio and URI to the 1620 node on the VM (basically a stock > install of ACID) and connected Zoiper directly to the node. This left the > BBB and its configuration completely out of the loop and I still got the > same behavior. > > Next I reconnected the URI and radio to the BBB and connected directly to it > via Zioper (I didn't do this before because I was having trouble connecting > Zoiper to the BBB, but I got that figured out) and it's still the same > behavior. > > And just to eliminate the radio, I disconnected it completely, connected the > COR input to a pullup, and grounded it by hand. When I ground the COR line > (usbinvert), I can hear slight background noise through Zoiper and when I > unground it, the courtesy tone is triggered (URI PTT active as well) and > then the background noise goes away when the CT is done. But if I ground > the COR line while the courtesy tone is playing, it ignores the COR and does > not pass audio to zioper until I cycle the COR line again. > > And finally I tried using the CTCSS input, same exact behavior. > > I know there is a URI test program from DMK, but I didn't really see a way > to simply read out the status of the inputs, just automated tests requiring > a loopback. > > -Mike > > > > On Fri, Sep 26, 2014 at 9:47 PM, Doug Crompton wrote: >> >> The ctcss and carrier from are just bits so technically you could use >> either one and it would work the same. You do need to set the one you are >> not using to none. We always use carrierfrom even though it is ctcss that is >> driving it. >> >> I tried what you are doing here. I listened to myself iaxrpt from a >> distant node. Then I key the local PTT on my handheld into my local node. I >> immediately unkey and then keyed again before I heard the courtesy tone and >> it worked fine. Tried it several times. >> >> Why don't you eliminate the 1620 node in the test and iaxrpt directly to >> 1998 to see what happens there. >> >> This is acting like what you would see with an rxdelay setting but it >> should be 0 by default unless you somehow got that into your config. >> Specifically say rxdelay=0 in the 1998 rpt.conf context to be sure. >> >> 73 Doug >> WA3DSP >> http://www.crompton.com/hamradio >> >> >> ________________________________ >> From: kf7mbk at w7ara.net >> Date: Fri, 26 Sep 2014 21:15:03 -0700 >> >> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >> To: doug at crompton.com >> CC: app_rpt-users at ohnosec.org >> >> Doug, this behavior happens even if I manually toggle the COR independent >> of the radio and audio so unless I'm not understanding, I can't see this >> being the radio. >> >> I tried changing unkeywait to 1000 but made no difference other than >> extending the time the PTT is active for the courtesy tone, and thus >> extending the window in which the COR line going high will be ignored. >> Seems that anything that extends the time that the PTT is active for the >> courtesy tone also extends the time that the COR is ignored. >> >> Just to make sure I'm not doing anything stupid or have an unconventional >> setuo,. my test setup is: >> >> HT -> DMK URI -> BBB (node 1998) -> ethernet -> Allstar on a VM (node >> 1620) -> IAX -> Zioper soft phone on laptop >> >> HT has audio in/out connected to the URI. PTT from the URI is not >> connected to the HT while testing. Signal from receive LED on the HT goes >> to COR URI input. >> >> I have the HT tuned to the weather frequency and I'm making/breaking the >> antenna connection to simulate picket fencing and I'm monitoring the audio >> received by the URI/BBB on the softphone. >> >> Bottom line is if the COR line drops, the courtesy pause and tone is >> instantly triggered, triggering the URI PTT. This works. But, if while the >> PTT is active, the COR line goes high again, the audio through the URI is >> not routed through until the COR line goes low* and high again after the >> PTT/courtesy tone is done transmitting. >> >> * when going low after getting ignored going high, no courtesy tone is >> triggered. >> >> >> Would it be useful/appropriate change carrierfrom to "no" and instead set >> ctcssfrom = usb and switch the radio output to the ctcss input on the URI >> and see if the problem still exists? >> >> Thanks for all the help! >> -Mike >> >> >> >> On Fri, Sep 26, 2014 at 8:37 PM, Doug Crompton wrote: >> >> Mike, >> >> You can try the changing the courtesy time wait then set back to duplex=1 >> >> The wait-times section >> This section allows the wait times for voice responses and other audio >> telemetry events to be adjusted. All wait times are in milliseconds. >> >> telemwait sets the time before sending the general audio telemetry >> responses used in the application which are not specifically defined below >> idwait sets the time to wait before sending ID audio telemetry >> unkeywait sets the amount of time to wait before sending the courtesy >> tone. This can be used to ensure breaking stations can get their turn >> calltermwait sets the amount of time between an autopatch disconnect and >> the audio telemetry message indicating the call has been terminated >> >> The unkeywait is the one to mess with. It is 400ms on the BBB by default. >> Make it longer like 1000 so it spans the dropout period you are seeing. >> Experiment with times. >> >> If that doesn't work I really think you should try a different radio. My >> thoughts are that it is some kind of recovery issue with TX. >> >> 73 Doug >> WA3DSP >> http://www.crompton.com/hamradio >> >> >> ________________________________ >> From: kf7mbk at w7ara.net >> Date: Fri, 26 Sep 2014 18:59:26 -0700 >> >> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >> To: doug at crompton.com >> CC: app_rpt-users at ohnosec.org >> >> OK, so I did some more testing. >> >> I have routed the signal out of the radio to an NPN and switched from >> usbinvert to usb as suggested. This made little difference, but in this >> configuration I could make the RC work a little better bridging the >> dropouts. But still would end up not detecting carrier after a quick >> dropout even though the COR signal into the dongle was high. >> >> Duplex = 0 seems to eliminate the problem. Is there a setting to tell it >> how long to wait after COR dropped to start transmitting the courtesy tone? >> (though I suppose that would defeat the purpose of the duplex=1 setting) >> Note that I have the PTT disconnected for testing, so all I see is the red >> LED come on as soon as the COR out of the radio drops. >> >> Actually as I'm typing this and playing with it, I just noticed it appears >> if the COR is restored ANY time the PTT is active for the courtesy tone, it >> will ignore the COR line until it's dropped and brought back up AFTER the >> PTT is done. This behavior seems VERY repeatable, even with a cleanly >> restored COR signal, So it may have nothing to do with quick dropouts and >> everything to do with the courtesy tone.. >> >> Are there any settings that control this? >> >> The LED on the radio (and hence my COR input) is controlled by noise >> squelch opening. >> >> >> >> >> >> >> On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton wrote: >> >> Mike, >> >> Are you using PL or noise squelch or both? Like I said I have not seen >> this problem and I am using basically stock timing. Every time the PL or >> squelch goes untrue for a certain (short) duration you should hear a >> courtesy tone. Perhpas you should try duplex=0 just to see if there is an >> issue with TX recovery. Do you have another radio you can try? >> >> 73 Doug >> WA3DSP >> http://www.crompton.com/hamradio >> >> >> ________________________________ >> From: kf7mbk at w7ara.net >> Date: Fri, 26 Sep 2014 10:18:19 -0700 >> >> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >> To: doug at crompton.com >> CC: app_rpt-users at ohnosec.org >> >> The scope image in the OP shows there doesn't appear to be a problem with >> pulling hi or low, The transitions (without the RC) are very clean and go >> all the way to ground.. It seems like the URI is doing edge detection >> instead of level detection, and it's just missing fast edges. Wasn't sure >> if this was something that could be tweaked in software or if I'll have to >> put some external debounce logic on the line. >> >> >> On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: >> >> Mike, >> >> Before you change any timing make sure as Jon pointed out that your COS >> signal is going hard high and low on signal and non-signal. You might need a >> pullup. The URI is kind of weak in that regard. It should be TTL levels >> <.5 volt low and >2.5 volt high and preferably rail to rail. >> >> >> 73 Doug >> WA3DSP >> http://www.crompton.com/hamradio >> >> >> ________________________________ >> From: kf7mbk at w7ara.net >> Date: Fri, 26 Sep 2014 09:56:21 -0700 >> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >> To: doug at crompton.com >> CC: app_rpt-users at ohnosec.org >> >> >> Doug, >> >> First: thanks for the excellent writeup on getting allstar running on the >> BBB. I used it to get up and running very quickly and is the setup I am >> having this issue with. >> >> I am running duplex =1 as well. I have not changed any timing values, >> (I'm essentially running the as-installed setup from the install image on >> your site) but I will take a look at them and see if I can make some changes >> for the better. >> >> Thanks! >> -Mike >> >> >> >> >> >> On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: >> >> ________________________________ >> From: doug at crompton.com >> To: kf7mbk at w7ara.net >> Subject: RE: [App_rpt-users] Fwd: COR signal getting confused >> Date: Fri, 26 Sep 2014 12:46:14 -0400 >> >> That is very strange. Have you changed any of the default timing values? >> Are you using simplex/duplex? Courtesy tone? Timing values could effect >> that. >> >> I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes >> and I have never seen that problem. I have one user who has a signal like >> you describe. He walks in a park with a handheld and he is often in and out. >> >> Also I assume you are not using any rxdelay? >> >> 73 Doug >> WA3DSP >> http://www.crompton.com/hamradio >> >> >> ________________________________ >> From: kf7mbk at w7ara.net >> Date: Fri, 26 Sep 2014 08:50:51 -0700 >> To: app_rpt-users at ohnosec.org >> Subject: [App_rpt-users] Fwd: COR signal getting confused >> >> >> Resending since my initial post has been pending moderation for 2 days now >> and got no reply from the list owner email. >> >> I have modified an HT to bring out the receive LED signal and use it >> as the COR input to a DMK URI. It is a digital signal as viewed on a >> scope (i.e. very short slope in the transitions) This seems like it >> would work well and it does on strong signals. But on marginal signals >> where the LED may blink on and off quickly (like during picket >> fencing), it seems to confuse the URI (or the software) were it will >> start off good, but then a quick dropout of the COR signal will cause >> the software to no longer detect carrier, even though the signal on >> the COR input has been restored. Even if the input is solid high (or >> low in my case, I'm using usbinvert) it will not detect a carrier >> until there is another dropout of adequate time to "reset" it. >> >> I've tried putting a simple RC on the input but it didn't really help >> much. Seems the URI (or software) needs a significant minimum time >> between transitions to properly detect them, long enough that it would >> delay the carrier detection too much without a circuit more complex >> than an RC (i.e. something that would allow instant keyup, but delay >> the key down.) >> >> Linked is a scope image. >> >> >> https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg >> >> Carrier was detected until this signal >> dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is >> the signal out of the radio. Carrier was not detected after the 5th >> dropout even though the signal remained low. >> >> Anyone ever experience this and/or have ideas on how to fix it? >> >> Thanks. >> >> Mike >> KF7MBK >> >> >> _______________________________________________ App_rpt-users mailing list >> App_rpt-users at 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. >> >> >> >> >> > From kf7mbk at w7ara.net Sun Sep 28 17:01:06 2014 From: kf7mbk at w7ara.net (Mike M) Date: Sun, 28 Sep 2014 10:01:06 -0700 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: Message-ID: Oh, hmm, I think I see what you are saying. I knew it was going to be something stupid. The problem here isn't the URI, software, or the radio. It's that I disconnected PTT to the radio for testing. I failed to realize, which you just pointed out, that if the PTT is asserted, and actually connected to the radio, the radio's COR line will drop and will not return until the PTT is released. Basically all this time I've been testing a scenario that will never happen (COR asserted from radio while PTT is asserted from URI). Man I feel dumb. Very sorry for taking up peoples time and the list bandwidth and a very big thank you to all that helped. -Mike On Sun, Sep 28, 2014 at 9:52 AM, Mike M wrote: >> Your node is set up for duplex=1 (half duplex with courtesy beep and tail) right? > > Correct, in both conf files. > >> And the problem you are seeing is the node will not receive a signal when it is transmitting the courtesy beep or tail - right? > > While true, this isn't the actual problem. > > I drew a diagram which will hopefully be worth 1000 words. > https://lh3.googleusercontent.com/-q3CmjOEBsMA/VCg72OZCNbI/AAAAAAAAPSc/wCZoJYknoLU/s822/COR%2520problem.png > > Though I just realized, I may have the order of the silence and the > tone backwards. Regardless, it is not the important issue. > > -Mike > > > > > > From: REDBUTTON_CTRL > To: app_rpt-users at ohnosec.org > Cc: > Date: Sat, 27 Sep 2014 12:11:19 -0400 > Subject: Re: [App_rpt-users] Fwd: COR signal getting confused > Ok In a bid to understand what it is you think is wrong let me clarify > from what you are saying below. > Your node is set up for duplex=1 (half duplex with courtesy beep and > tail) right? > And the problem you are seeing is the node will not receive a signal > when it is transmitting the courtesy beep or tail - right? > > If the above is correct, then this configuration cannot receive a > signal while it is transmitting. This is normal for this > configuration. > If your radio is portable or mobile radio, then your radio can only > receive or transmit but not both simultaneously. So in duplex =1 > mode the URI assumes your receiver is active if the node isnt > transmitting. So the node ignores all receiver activity while its > transmitting. Once the tail is gone then it will listen to thereceiver > cor line. > > For some reason from you explanation below you are expecting the node > to receive in full duplex. Unless the radio you have connected is > capable of full duplex, this wont work. If the radio connected to the > URI is a pair of radios or a duplexed base station and if you set the > duplex setting to duplex=2 in rpt conf and duplex =1 in usbradio then > it will receive while its transmitting. > > Hope I understand this right and this helps. > > Jon VA3RQ > > On Sat, Sep 27, 2014 at 8:47 AM, Mike M wrote: >> I'm starting to think its the URI. >> >> First, I got rid of all the components (transistor and RC) because they made >> little difference and don't want the added complexity. I went back to >> usbinvert. >> I brought the radio and URI to the 1620 node on the VM (basically a stock >> install of ACID) and connected Zoiper directly to the node. This left the >> BBB and its configuration completely out of the loop and I still got the >> same behavior. >> >> Next I reconnected the URI and radio to the BBB and connected directly to it >> via Zioper (I didn't do this before because I was having trouble connecting >> Zoiper to the BBB, but I got that figured out) and it's still the same >> behavior. >> >> And just to eliminate the radio, I disconnected it completely, connected the >> COR input to a pullup, and grounded it by hand. When I ground the COR line >> (usbinvert), I can hear slight background noise through Zoiper and when I >> unground it, the courtesy tone is triggered (URI PTT active as well) and >> then the background noise goes away when the CT is done. But if I ground >> the COR line while the courtesy tone is playing, it ignores the COR and does >> not pass audio to zioper until I cycle the COR line again. >> >> And finally I tried using the CTCSS input, same exact behavior. >> >> I know there is a URI test program from DMK, but I didn't really see a way >> to simply read out the status of the inputs, just automated tests requiring >> a loopback. >> >> -Mike >> >> >> >> On Fri, Sep 26, 2014 at 9:47 PM, Doug Crompton wrote: >>> >>> The ctcss and carrier from are just bits so technically you could use >>> either one and it would work the same. You do need to set the one you are >>> not using to none. We always use carrierfrom even though it is ctcss that is >>> driving it. >>> >>> I tried what you are doing here. I listened to myself iaxrpt from a >>> distant node. Then I key the local PTT on my handheld into my local node. I >>> immediately unkey and then keyed again before I heard the courtesy tone and >>> it worked fine. Tried it several times. >>> >>> Why don't you eliminate the 1620 node in the test and iaxrpt directly to >>> 1998 to see what happens there. >>> >>> This is acting like what you would see with an rxdelay setting but it >>> should be 0 by default unless you somehow got that into your config. >>> Specifically say rxdelay=0 in the 1998 rpt.conf context to be sure. >>> >>> 73 Doug >>> WA3DSP >>> http://www.crompton.com/hamradio >>> >>> >>> ________________________________ >>> From: kf7mbk at w7ara.net >>> Date: Fri, 26 Sep 2014 21:15:03 -0700 >>> >>> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >>> To: doug at crompton.com >>> CC: app_rpt-users at ohnosec.org >>> >>> Doug, this behavior happens even if I manually toggle the COR independent >>> of the radio and audio so unless I'm not understanding, I can't see this >>> being the radio. >>> >>> I tried changing unkeywait to 1000 but made no difference other than >>> extending the time the PTT is active for the courtesy tone, and thus >>> extending the window in which the COR line going high will be ignored. >>> Seems that anything that extends the time that the PTT is active for the >>> courtesy tone also extends the time that the COR is ignored. >>> >>> Just to make sure I'm not doing anything stupid or have an unconventional >>> setuo,. my test setup is: >>> >>> HT -> DMK URI -> BBB (node 1998) -> ethernet -> Allstar on a VM (node >>> 1620) -> IAX -> Zioper soft phone on laptop >>> >>> HT has audio in/out connected to the URI. PTT from the URI is not >>> connected to the HT while testing. Signal from receive LED on the HT goes >>> to COR URI input. >>> >>> I have the HT tuned to the weather frequency and I'm making/breaking the >>> antenna connection to simulate picket fencing and I'm monitoring the audio >>> received by the URI/BBB on the softphone. >>> >>> Bottom line is if the COR line drops, the courtesy pause and tone is >>> instantly triggered, triggering the URI PTT. This works. But, if while the >>> PTT is active, the COR line goes high again, the audio through the URI is >>> not routed through until the COR line goes low* and high again after the >>> PTT/courtesy tone is done transmitting. >>> >>> * when going low after getting ignored going high, no courtesy tone is >>> triggered. >>> >>> >>> Would it be useful/appropriate change carrierfrom to "no" and instead set >>> ctcssfrom = usb and switch the radio output to the ctcss input on the URI >>> and see if the problem still exists? >>> >>> Thanks for all the help! >>> -Mike >>> >>> >>> >>> On Fri, Sep 26, 2014 at 8:37 PM, Doug Crompton wrote: >>> >>> Mike, >>> >>> You can try the changing the courtesy time wait then set back to duplex=1 >>> >>> The wait-times section >>> This section allows the wait times for voice responses and other audio >>> telemetry events to be adjusted. All wait times are in milliseconds. >>> >>> telemwait sets the time before sending the general audio telemetry >>> responses used in the application which are not specifically defined below >>> idwait sets the time to wait before sending ID audio telemetry >>> unkeywait sets the amount of time to wait before sending the courtesy >>> tone. This can be used to ensure breaking stations can get their turn >>> calltermwait sets the amount of time between an autopatch disconnect and >>> the audio telemetry message indicating the call has been terminated >>> >>> The unkeywait is the one to mess with. It is 400ms on the BBB by default. >>> Make it longer like 1000 so it spans the dropout period you are seeing. >>> Experiment with times. >>> >>> If that doesn't work I really think you should try a different radio. My >>> thoughts are that it is some kind of recovery issue with TX. >>> >>> 73 Doug >>> WA3DSP >>> http://www.crompton.com/hamradio >>> >>> >>> ________________________________ >>> From: kf7mbk at w7ara.net >>> Date: Fri, 26 Sep 2014 18:59:26 -0700 >>> >>> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >>> To: doug at crompton.com >>> CC: app_rpt-users at ohnosec.org >>> >>> OK, so I did some more testing. >>> >>> I have routed the signal out of the radio to an NPN and switched from >>> usbinvert to usb as suggested. This made little difference, but in this >>> configuration I could make the RC work a little better bridging the >>> dropouts. But still would end up not detecting carrier after a quick >>> dropout even though the COR signal into the dongle was high. >>> >>> Duplex = 0 seems to eliminate the problem. Is there a setting to tell it >>> how long to wait after COR dropped to start transmitting the courtesy tone? >>> (though I suppose that would defeat the purpose of the duplex=1 setting) >>> Note that I have the PTT disconnected for testing, so all I see is the red >>> LED come on as soon as the COR out of the radio drops. >>> >>> Actually as I'm typing this and playing with it, I just noticed it appears >>> if the COR is restored ANY time the PTT is active for the courtesy tone, it >>> will ignore the COR line until it's dropped and brought back up AFTER the >>> PTT is done. This behavior seems VERY repeatable, even with a cleanly >>> restored COR signal, So it may have nothing to do with quick dropouts and >>> everything to do with the courtesy tone.. >>> >>> Are there any settings that control this? >>> >>> The LED on the radio (and hence my COR input) is controlled by noise >>> squelch opening. >>> >>> >>> >>> >>> >>> >>> On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton wrote: >>> >>> Mike, >>> >>> Are you using PL or noise squelch or both? Like I said I have not seen >>> this problem and I am using basically stock timing. Every time the PL or >>> squelch goes untrue for a certain (short) duration you should hear a >>> courtesy tone. Perhpas you should try duplex=0 just to see if there is an >>> issue with TX recovery. Do you have another radio you can try? >>> >>> 73 Doug >>> WA3DSP >>> http://www.crompton.com/hamradio >>> >>> >>> ________________________________ >>> From: kf7mbk at w7ara.net >>> Date: Fri, 26 Sep 2014 10:18:19 -0700 >>> >>> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >>> To: doug at crompton.com >>> CC: app_rpt-users at ohnosec.org >>> >>> The scope image in the OP shows there doesn't appear to be a problem with >>> pulling hi or low, The transitions (without the RC) are very clean and go >>> all the way to ground.. It seems like the URI is doing edge detection >>> instead of level detection, and it's just missing fast edges. Wasn't sure >>> if this was something that could be tweaked in software or if I'll have to >>> put some external debounce logic on the line. >>> >>> >>> On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: >>> >>> Mike, >>> >>> Before you change any timing make sure as Jon pointed out that your COS >>> signal is going hard high and low on signal and non-signal. You might need a >>> pullup. The URI is kind of weak in that regard. It should be TTL levels >>> <.5 volt low and >2.5 volt high and preferably rail to rail. >>> >>> >>> 73 Doug >>> WA3DSP >>> http://www.crompton.com/hamradio >>> >>> >>> ________________________________ >>> From: kf7mbk at w7ara.net >>> Date: Fri, 26 Sep 2014 09:56:21 -0700 >>> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >>> To: doug at crompton.com >>> CC: app_rpt-users at ohnosec.org >>> >>> >>> Doug, >>> >>> First: thanks for the excellent writeup on getting allstar running on the >>> BBB. I used it to get up and running very quickly and is the setup I am >>> having this issue with. >>> >>> I am running duplex =1 as well. I have not changed any timing values, >>> (I'm essentially running the as-installed setup from the install image on >>> your site) but I will take a look at them and see if I can make some changes >>> for the better. >>> >>> Thanks! >>> -Mike >>> >>> >>> >>> >>> >>> On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: >>> >>> ________________________________ >>> From: doug at crompton.com >>> To: kf7mbk at w7ara.net >>> Subject: RE: [App_rpt-users] Fwd: COR signal getting confused >>> Date: Fri, 26 Sep 2014 12:46:14 -0400 >>> >>> That is very strange. Have you changed any of the default timing values? >>> Are you using simplex/duplex? Courtesy tone? Timing values could effect >>> that. >>> >>> I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes >>> and I have never seen that problem. I have one user who has a signal like >>> you describe. He walks in a park with a handheld and he is often in and out. >>> >>> Also I assume you are not using any rxdelay? >>> >>> 73 Doug >>> WA3DSP >>> http://www.crompton.com/hamradio >>> >>> >>> ________________________________ >>> From: kf7mbk at w7ara.net >>> Date: Fri, 26 Sep 2014 08:50:51 -0700 >>> To: app_rpt-users at ohnosec.org >>> Subject: [App_rpt-users] Fwd: COR signal getting confused >>> >>> >>> Resending since my initial post has been pending moderation for 2 days now >>> and got no reply from the list owner email. >>> >>> I have modified an HT to bring out the receive LED signal and use it >>> as the COR input to a DMK URI. It is a digital signal as viewed on a >>> scope (i.e. very short slope in the transitions) This seems like it >>> would work well and it does on strong signals. But on marginal signals >>> where the LED may blink on and off quickly (like during picket >>> fencing), it seems to confuse the URI (or the software) were it will >>> start off good, but then a quick dropout of the COR signal will cause >>> the software to no longer detect carrier, even though the signal on >>> the COR input has been restored. Even if the input is solid high (or >>> low in my case, I'm using usbinvert) it will not detect a carrier >>> until there is another dropout of adequate time to "reset" it. >>> >>> I've tried putting a simple RC on the input but it didn't really help >>> much. Seems the URI (or software) needs a significant minimum time >>> between transitions to properly detect them, long enough that it would >>> delay the carrier detection too much without a circuit more complex >>> than an RC (i.e. something that would allow instant keyup, but delay >>> the key down.) >>> >>> Linked is a scope image. >>> >>> >>> https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg >>> >>> Carrier was detected until this signal >>> dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is >>> the signal out of the radio. Carrier was not detected after the 5th >>> dropout even though the signal remained low. >>> >>> Anyone ever experience this and/or have ideas on how to fix it? >>> >>> Thanks. >>> >>> Mike >>> KF7MBK >>> >>> >>> _______________________________________________ App_rpt-users mailing list >>> App_rpt-users at 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. >>> >>> >>> >>> >>> >> From jrorke at cogeco.ca Sun Sep 28 18:13:55 2014 From: jrorke at cogeco.ca (REDBUTTON_CTRL) Date: Sun, 28 Sep 2014 14:13:55 -0400 Subject: [App_rpt-users] Fwd: COR signal getting confused In-Reply-To: References: Message-ID: <54284FE3.1070207@cogeco.ca> Ok I hope it works fine now. Not a problem on asking these questions. Sometimes its hard to see the forest for the trees. Been there many times! And all this info will hopefully help someone else down the road. Cheers! Jon VA3RQ On 9/28/2014 1:01 PM, Mike M wrote: > Oh, hmm, I think I see what you are saying. I knew it was going to be > something stupid. > > The problem here isn't the URI, software, or the radio. It's that I > disconnected PTT to the radio for testing. I failed to realize, which > you just pointed out, that if the PTT is asserted, and actually > connected to the radio, the radio's COR line will drop and will not > return until the PTT is released. Basically all this time I've been > testing a scenario that will never happen (COR asserted from radio > while PTT is asserted from URI). > > Man I feel dumb. Very sorry for taking up peoples time and the list > bandwidth and a very big thank you to all that helped. > > -Mike > > > > > On Sun, Sep 28, 2014 at 9:52 AM, Mike M wrote: >>> Your node is set up for duplex=1 (half duplex with courtesy beep and tail) right? >> Correct, in both conf files. >> >>> And the problem you are seeing is the node will not receive a signal when it is transmitting the courtesy beep or tail - right? >> While true, this isn't the actual problem. >> >> I drew a diagram which will hopefully be worth 1000 words. >> https://lh3.googleusercontent.com/-q3CmjOEBsMA/VCg72OZCNbI/AAAAAAAAPSc/wCZoJYknoLU/s822/COR%2520problem.png >> >> Though I just realized, I may have the order of the silence and the >> tone backwards. Regardless, it is not the important issue. >> >> -Mike >> >> >> >> >> >> From: REDBUTTON_CTRL >> To: app_rpt-users at ohnosec.org >> Cc: >> Date: Sat, 27 Sep 2014 12:11:19 -0400 >> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >> Ok In a bid to understand what it is you think is wrong let me clarify >> from what you are saying below. >> Your node is set up for duplex=1 (half duplex with courtesy beep and >> tail) right? >> And the problem you are seeing is the node will not receive a signal >> when it is transmitting the courtesy beep or tail - right? >> >> If the above is correct, then this configuration cannot receive a >> signal while it is transmitting. This is normal for this >> configuration. >> If your radio is portable or mobile radio, then your radio can only >> receive or transmit but not both simultaneously. So in duplex =1 >> mode the URI assumes your receiver is active if the node isnt >> transmitting. So the node ignores all receiver activity while its >> transmitting. Once the tail is gone then it will listen to thereceiver >> cor line. >> >> For some reason from you explanation below you are expecting the node >> to receive in full duplex. Unless the radio you have connected is >> capable of full duplex, this wont work. If the radio connected to the >> URI is a pair of radios or a duplexed base station and if you set the >> duplex setting to duplex=2 in rpt conf and duplex =1 in usbradio then >> it will receive while its transmitting. >> >> Hope I understand this right and this helps. >> >> Jon VA3RQ >> >> On Sat, Sep 27, 2014 at 8:47 AM, Mike M wrote: >>> I'm starting to think its the URI. >>> >>> First, I got rid of all the components (transistor and RC) because they made >>> little difference and don't want the added complexity. I went back to >>> usbinvert. >>> I brought the radio and URI to the 1620 node on the VM (basically a stock >>> install of ACID) and connected Zoiper directly to the node. This left the >>> BBB and its configuration completely out of the loop and I still got the >>> same behavior. >>> >>> Next I reconnected the URI and radio to the BBB and connected directly to it >>> via Zioper (I didn't do this before because I was having trouble connecting >>> Zoiper to the BBB, but I got that figured out) and it's still the same >>> behavior. >>> >>> And just to eliminate the radio, I disconnected it completely, connected the >>> COR input to a pullup, and grounded it by hand. When I ground the COR line >>> (usbinvert), I can hear slight background noise through Zoiper and when I >>> unground it, the courtesy tone is triggered (URI PTT active as well) and >>> then the background noise goes away when the CT is done. But if I ground >>> the COR line while the courtesy tone is playing, it ignores the COR and does >>> not pass audio to zioper until I cycle the COR line again. >>> >>> And finally I tried using the CTCSS input, same exact behavior. >>> >>> I know there is a URI test program from DMK, but I didn't really see a way >>> to simply read out the status of the inputs, just automated tests requiring >>> a loopback. >>> >>> -Mike >>> >>> >>> >>> On Fri, Sep 26, 2014 at 9:47 PM, Doug Crompton wrote: >>>> The ctcss and carrier from are just bits so technically you could use >>>> either one and it would work the same. You do need to set the one you are >>>> not using to none. We always use carrierfrom even though it is ctcss that is >>>> driving it. >>>> >>>> I tried what you are doing here. I listened to myself iaxrpt from a >>>> distant node. Then I key the local PTT on my handheld into my local node. I >>>> immediately unkey and then keyed again before I heard the courtesy tone and >>>> it worked fine. Tried it several times. >>>> >>>> Why don't you eliminate the 1620 node in the test and iaxrpt directly to >>>> 1998 to see what happens there. >>>> >>>> This is acting like what you would see with an rxdelay setting but it >>>> should be 0 by default unless you somehow got that into your config. >>>> Specifically say rxdelay=0 in the 1998 rpt.conf context to be sure. >>>> >>>> 73 Doug >>>> WA3DSP >>>> http://www.crompton.com/hamradio >>>> >>>> >>>> ________________________________ >>>> From: kf7mbk at w7ara.net >>>> Date: Fri, 26 Sep 2014 21:15:03 -0700 >>>> >>>> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >>>> To: doug at crompton.com >>>> CC: app_rpt-users at ohnosec.org >>>> >>>> Doug, this behavior happens even if I manually toggle the COR independent >>>> of the radio and audio so unless I'm not understanding, I can't see this >>>> being the radio. >>>> >>>> I tried changing unkeywait to 1000 but made no difference other than >>>> extending the time the PTT is active for the courtesy tone, and thus >>>> extending the window in which the COR line going high will be ignored. >>>> Seems that anything that extends the time that the PTT is active for the >>>> courtesy tone also extends the time that the COR is ignored. >>>> >>>> Just to make sure I'm not doing anything stupid or have an unconventional >>>> setuo,. my test setup is: >>>> >>>> HT -> DMK URI -> BBB (node 1998) -> ethernet -> Allstar on a VM (node >>>> 1620) -> IAX -> Zioper soft phone on laptop >>>> >>>> HT has audio in/out connected to the URI. PTT from the URI is not >>>> connected to the HT while testing. Signal from receive LED on the HT goes >>>> to COR URI input. >>>> >>>> I have the HT tuned to the weather frequency and I'm making/breaking the >>>> antenna connection to simulate picket fencing and I'm monitoring the audio >>>> received by the URI/BBB on the softphone. >>>> >>>> Bottom line is if the COR line drops, the courtesy pause and tone is >>>> instantly triggered, triggering the URI PTT. This works. But, if while the >>>> PTT is active, the COR line goes high again, the audio through the URI is >>>> not routed through until the COR line goes low* and high again after the >>>> PTT/courtesy tone is done transmitting. >>>> >>>> * when going low after getting ignored going high, no courtesy tone is >>>> triggered. >>>> >>>> >>>> Would it be useful/appropriate change carrierfrom to "no" and instead set >>>> ctcssfrom = usb and switch the radio output to the ctcss input on the URI >>>> and see if the problem still exists? >>>> >>>> Thanks for all the help! >>>> -Mike >>>> >>>> >>>> >>>> On Fri, Sep 26, 2014 at 8:37 PM, Doug Crompton wrote: >>>> >>>> Mike, >>>> >>>> You can try the changing the courtesy time wait then set back to duplex=1 >>>> >>>> The wait-times section >>>> This section allows the wait times for voice responses and other audio >>>> telemetry events to be adjusted. All wait times are in milliseconds. >>>> >>>> telemwait sets the time before sending the general audio telemetry >>>> responses used in the application which are not specifically defined below >>>> idwait sets the time to wait before sending ID audio telemetry >>>> unkeywait sets the amount of time to wait before sending the courtesy >>>> tone. This can be used to ensure breaking stations can get their turn >>>> calltermwait sets the amount of time between an autopatch disconnect and >>>> the audio telemetry message indicating the call has been terminated >>>> >>>> The unkeywait is the one to mess with. It is 400ms on the BBB by default. >>>> Make it longer like 1000 so it spans the dropout period you are seeing. >>>> Experiment with times. >>>> >>>> If that doesn't work I really think you should try a different radio. My >>>> thoughts are that it is some kind of recovery issue with TX. >>>> >>>> 73 Doug >>>> WA3DSP >>>> http://www.crompton.com/hamradio >>>> >>>> >>>> ________________________________ >>>> From: kf7mbk at w7ara.net >>>> Date: Fri, 26 Sep 2014 18:59:26 -0700 >>>> >>>> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >>>> To: doug at crompton.com >>>> CC: app_rpt-users at ohnosec.org >>>> >>>> OK, so I did some more testing. >>>> >>>> I have routed the signal out of the radio to an NPN and switched from >>>> usbinvert to usb as suggested. This made little difference, but in this >>>> configuration I could make the RC work a little better bridging the >>>> dropouts. But still would end up not detecting carrier after a quick >>>> dropout even though the COR signal into the dongle was high. >>>> >>>> Duplex = 0 seems to eliminate the problem. Is there a setting to tell it >>>> how long to wait after COR dropped to start transmitting the courtesy tone? >>>> (though I suppose that would defeat the purpose of the duplex=1 setting) >>>> Note that I have the PTT disconnected for testing, so all I see is the red >>>> LED come on as soon as the COR out of the radio drops. >>>> >>>> Actually as I'm typing this and playing with it, I just noticed it appears >>>> if the COR is restored ANY time the PTT is active for the courtesy tone, it >>>> will ignore the COR line until it's dropped and brought back up AFTER the >>>> PTT is done. This behavior seems VERY repeatable, even with a cleanly >>>> restored COR signal, So it may have nothing to do with quick dropouts and >>>> everything to do with the courtesy tone.. >>>> >>>> Are there any settings that control this? >>>> >>>> The LED on the radio (and hence my COR input) is controlled by noise >>>> squelch opening. >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Fri, Sep 26, 2014 at 3:05 PM, Doug Crompton wrote: >>>> >>>> Mike, >>>> >>>> Are you using PL or noise squelch or both? Like I said I have not seen >>>> this problem and I am using basically stock timing. Every time the PL or >>>> squelch goes untrue for a certain (short) duration you should hear a >>>> courtesy tone. Perhpas you should try duplex=0 just to see if there is an >>>> issue with TX recovery. Do you have another radio you can try? >>>> >>>> 73 Doug >>>> WA3DSP >>>> http://www.crompton.com/hamradio >>>> >>>> >>>> ________________________________ >>>> From: kf7mbk at w7ara.net >>>> Date: Fri, 26 Sep 2014 10:18:19 -0700 >>>> >>>> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >>>> To: doug at crompton.com >>>> CC: app_rpt-users at ohnosec.org >>>> >>>> The scope image in the OP shows there doesn't appear to be a problem with >>>> pulling hi or low, The transitions (without the RC) are very clean and go >>>> all the way to ground.. It seems like the URI is doing edge detection >>>> instead of level detection, and it's just missing fast edges. Wasn't sure >>>> if this was something that could be tweaked in software or if I'll have to >>>> put some external debounce logic on the line. >>>> >>>> >>>> On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton wrote: >>>> >>>> Mike, >>>> >>>> Before you change any timing make sure as Jon pointed out that your COS >>>> signal is going hard high and low on signal and non-signal. You might need a >>>> pullup. The URI is kind of weak in that regard. It should be TTL levels >>>> <.5 volt low and>2.5 volt high and preferably rail to rail. >>>> >>>> >>>> 73 Doug >>>> WA3DSP >>>> http://www.crompton.com/hamradio >>>> >>>> >>>> ________________________________ >>>> From: kf7mbk at w7ara.net >>>> Date: Fri, 26 Sep 2014 09:56:21 -0700 >>>> Subject: Re: [App_rpt-users] Fwd: COR signal getting confused >>>> To: doug at crompton.com >>>> CC: app_rpt-users at ohnosec.org >>>> >>>> >>>> Doug, >>>> >>>> First: thanks for the excellent writeup on getting allstar running on the >>>> BBB. I used it to get up and running very quickly and is the setup I am >>>> having this issue with. >>>> >>>> I am running duplex =1 as well. I have not changed any timing values, >>>> (I'm essentially running the as-installed setup from the install image on >>>> your site) but I will take a look at them and see if I can make some changes >>>> for the better. >>>> >>>> Thanks! >>>> -Mike >>>> >>>> >>>> >>>> >>>> >>>> On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton wrote: >>>> >>>> ________________________________ >>>> From: doug at crompton.com >>>> To: kf7mbk at w7ara.net >>>> Subject: RE: [App_rpt-users] Fwd: COR signal getting confused >>>> Date: Fri, 26 Sep 2014 12:46:14 -0400 >>>> >>>> That is very strange. Have you changed any of the default timing values? >>>> Are you using simplex/duplex? Courtesy tone? Timing values could effect >>>> that. >>>> >>>> I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes >>>> and I have never seen that problem. I have one user who has a signal like >>>> you describe. He walks in a park with a handheld and he is often in and out. >>>> >>>> Also I assume you are not using any rxdelay? >>>> >>>> 73 Doug >>>> WA3DSP >>>> http://www.crompton.com/hamradio >>>> >>>> >>>> ________________________________ >>>> From: kf7mbk at w7ara.net >>>> Date: Fri, 26 Sep 2014 08:50:51 -0700 >>>> To: app_rpt-users at ohnosec.org >>>> Subject: [App_rpt-users] Fwd: COR signal getting confused >>>> >>>> >>>> Resending since my initial post has been pending moderation for 2 days now >>>> and got no reply from the list owner email. >>>> >>>> I have modified an HT to bring out the receive LED signal and use it >>>> as the COR input to a DMK URI. It is a digital signal as viewed on a >>>> scope (i.e. very short slope in the transitions) This seems like it >>>> would work well and it does on strong signals. But on marginal signals >>>> where the LED may blink on and off quickly (like during picket >>>> fencing), it seems to confuse the URI (or the software) were it will >>>> start off good, but then a quick dropout of the COR signal will cause >>>> the software to no longer detect carrier, even though the signal on >>>> the COR input has been restored. Even if the input is solid high (or >>>> low in my case, I'm using usbinvert) it will not detect a carrier >>>> until there is another dropout of adequate time to "reset" it. >>>> >>>> I've tried putting a simple RC on the input but it didn't really help >>>> much. Seems the URI (or software) needs a significant minimum time >>>> between transitions to properly detect them, long enough that it would >>>> delay the carrier detection too much without a circuit more complex >>>> than an RC (i.e. something that would allow instant keyup, but delay >>>> the key down.) >>>> >>>> Linked is a scope image. >>>> >>>> >>>> https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg >>>> >>>> Carrier was detected until this signal >>>> dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is >>>> the signal out of the radio. Carrier was not detected after the 5th >>>> dropout even though the signal remained low. >>>> >>>> Anyone ever experience this and/or have ideas on how to fix it? >>>> >>>> Thanks. >>>> >>>> Mike >>>> KF7MBK >>>> >>>> >>>> _______________________________________________ App_rpt-users mailing list >>>> App_rpt-users at 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. >>>> >>>> >>>> >>>> >>>> From N1XBM at amsat.org Sun Sep 28 19:28:53 2014 From: N1XBM at amsat.org (Robert Newberry) Date: Sun, 28 Sep 2014 15:28:53 -0400 Subject: [App_rpt-users] Multiple nodes Message-ID: So as it stands I have a one node system. I have another URI on the way and will have BBB soon. The eventual plan is to have a few repeaters and some simplex nodes at people's houses for RF hot spot access. What is the best way to tie these together? I understand you can set permanent links that will reestablish connection if lost. Is there other ways of accomplishing this? I only ask because I have my one node setup with email, autopatch and all other kinds of bells and whistles. I'd like to be able to do all of this from other RF locations and I wonder if I need to just set each node up accordingly or can one node be the workhorse and the other nodes just be dumb connections. Did I make any sense with that question? -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Sun Sep 28 21:00:00 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Sun, 28 Sep 2014 14:00:00 -0700 Subject: [App_rpt-users] Multiple nodes In-Reply-To: References: Message-ID: There are a few ways to do what you want ? that is permanently tie multiple repeaters together ? if I understand your question. First, permanent connections are not as permanent as you might expect. If the computer that initiated the permanent connections goes down the connection will not reestablish. However you can have a startup macro make the connection as Asterisk starts. Also, there seems to be some intermittent bug, which I?ve never pinned down, where permanent connections won?t reestablish with out forcing a disconnect first. Second way is with RTCMs. They are a whole lot easier to deploy and way more reliable than a bunch of USB type nodes, with the trade off in expense. Although by the time you buy a BBB and a URI you?re getting close to the expense of an RTCM. Of course you can go with a cheep sound dongle and an eBay used thin client PC. It?s the ?ol time/money/reliability trade off. I strongly recommend the RTCM approach. And a third option is called app_radbridge. If you don?t want to buy RTCMs this is probably the way to go. I?ve never tried to use it. The only documentation I am aware of is in the source which is reproduced here. /* This application is intended to provide a generic "bridging" functionality for radio-oriented Asterisk channels. The idea here is that certain radio applications lend themselves to needing a "generic" (passes audio and tx/rx keying completely transparently) to and from two or more endpoints. An example of such an appication might be replacing (or providing equivlent new functionaliy of) one or more full-duplex UHF control links with an IP-based one(s). app_radbridge allows multiple instances of radio-oriented channels transparently "bridged" together. The config file (radbridge.conf) allows specification of each "bridging" instance and what radio-oriented Asterisk channels are to be associated with it. There is no need for any other specificaiton of configuration. The file format for radbridge.conf departs somewhat from the standard usage (at least for radio stuff) of the Asterisk config file architecture. In most other radio-oriented cases, an instance of whatever it is gets defined as a "Stanza" in the config file. In this case, because of limitations in the way that Asterisk parses config files, that was not possible. Instead, all config information goes into the [general] stanza, and each line of config info defines a different instance of radio bridging. For example: [general] instance1 = Voter/1234,Radio/5678 instance2 = Voter/1235,Radio/5679 This example would define two radio bridging instances "instance1" and "instance2", each with 2 channels associated with them. The supported channel types are "Voter" (chan_voter), "Radio" (chan_usbradio), "SimpleUsb" (chan_simpleusb), and "Zap" ("Dahdi") (chan_dahdi, for the couple of devices that use this channel driver, such as the PCIRadio card, and separate analog channels using an ARIB board or such). Rather then "adding" (which would actually be a lot of *removing* optionally) this functionality in app_rpt, it made more sense to create a separate application specifically for this purpose. In addition, this allows for a system that is merely provided for doing this bridging application and nothing else radio-oriented, to not have to run app_rpt at all. */ -- Tim :wq On Sep 28, 2014, at 12:28 PM, Robert Newberry wrote: > So as it stands I have a one node system. I have another URI on the way and will have BBB soon. The eventual plan is to have a few repeaters and some simplex nodes at people's houses for RF hot spot access. > > What is the best way to tie these together? I understand you can set permanent links that will reestablish connection if lost. > > Is there other ways of accomplishing this? I only ask because I have my one node setup with email, autopatch and all other kinds of bells and whistles. I'd like to be able to do all of this from other RF locations and I wonder if I need to just set each node up accordingly or can one node be the workhorse and the other nodes just be dumb connections. > > Did I make any sense with that question? > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From k0xm at byrg.net Sun Sep 28 21:17:27 2014 From: k0xm at byrg.net (Chuck Kraly) Date: Sun, 28 Sep 2014 14:17:27 -0700 Subject: [App_rpt-users] Multiple nodes In-Reply-To: References: Message-ID: Tim, Not to debate some of your statements, but I am from Kansas and maybe our math is different. My BBB cost 55 bucks, and the URI was 70. The RTCM is 269 bucks.... What am I missing? Chuck K0XM Allstar 41153 Portable BBB repeater 927.2375 in San Diego (until the end of 2014) On Sun, Sep 28, 2014 at 2:00 PM, Tim Sawyer wrote: > There are a few ways to do what you want ? that is permanently tie > multiple repeaters together ? if I understand your question. > > First, permanent connections are not as permanent as you might expect. If > the computer that initiated the permanent connections goes down the > connection will not reestablish. However you can have a startup macro make > the connection as Asterisk starts. Also, there seems to be some > intermittent bug, which I?ve never pinned down, where permanent connections > won?t reestablish with out forcing a disconnect first. > > Second way is with RTCMs. They are a whole lot easier to deploy and way > more reliable than a bunch of USB type nodes, with the trade off in > expense. Although by the time you buy a BBB and a URI you?re getting close > to the expense of an RTCM. Of course you can go with a cheep sound dongle > and an eBay used thin client PC. It?s the ?ol time/money/reliability trade > off. I strongly recommend the RTCM approach. > > And a third option is called app_radbridge. If you don?t want to buy RTCMs > this is probably the way to go. I?ve never tried to use it. The only > documentation I am aware of is in the source which is reproduced here. > > /* This application is intended to provide a generic "bridging" > functionality for radio-oriented Asterisk channels. > > The idea here is that certain radio applications lend themselves > to needing a "generic" (passes audio and tx/rx keying completely > transparently) to and from two or more endpoints. > > An example of such an appication might be replacing (or providing > equivlent new functionaliy of) one or more full-duplex UHF control > links with an IP-based one(s). > > app_radbridge allows multiple instances of radio-oriented channels > transparently "bridged" together. > > The config file (radbridge.conf) allows specification of each > "bridging" instance and what radio-oriented Asterisk channels > are to be associated with it. There is no need for any other > specificaiton of configuration. > > The file format for radbridge.conf departs somewhat from the standard > usage (at least for radio stuff) of the Asterisk config file > architecture. > > In most other radio-oriented cases, an instance of whatever it is > gets defined as a "Stanza" in the config file. In this case, because > of limitations in the way that Asterisk parses config files, that > was not possible. Instead, all config information goes into the > [general] stanza, and each line of config info defines a different > instance of radio bridging. For example: > > [general] > > instance1 = Voter/1234,Radio/5678 > instance2 = Voter/1235,Radio/5679 > > This example would define two radio bridging instances "instance1" > and "instance2", each with 2 channels associated with them. > > The supported channel types are "Voter" (chan_voter), "Radio" > (chan_usbradio), "SimpleUsb" (chan_simpleusb), and "Zap" ("Dahdi") > (chan_dahdi, for the couple of devices that use this channel > driver, such as the PCIRadio card, and separate analog channels > using an ARIB board or such). > > Rather then "adding" (which would actually be a lot of *removing* > optionally) this functionality in app_rpt, it made more sense to > create a separate application specifically for this purpose. In > addition, this allows for a system that is merely provided for > doing this bridging application and nothing else radio-oriented, > to not have to run app_rpt at all. > */ > > -- > Tim > :wq > > On Sep 28, 2014, at 12:28 PM, Robert Newberry wrote: > > So as it stands I have a one node system. I have another URI on the way > and will have BBB soon. The eventual plan is to have a few repeaters and > some simplex nodes at people's houses for RF hot spot access. > > What is the best way to tie these together? I understand you can set > permanent links that will reestablish connection if lost. > > Is there other ways of accomplishing this? I only ask because I have my > one node setup with email, autopatch and all other kinds of bells and > whistles. I'd like to be able to do all of this from other RF locations and > I wonder if I need to just set each node up accordingly or can one node be > the workhorse and the other nodes just be dumb connections. > > Did I make any sense with that question? > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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. > -- Chuck K0XM Backyard Repeater Group k0xm at byrg.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Sun Sep 28 22:07:38 2014 From: doug at crompton.com (Doug Crompton) Date: Sun, 28 Sep 2014 18:07:38 -0400 Subject: [App_rpt-users] Multiple nodes In-Reply-To: References: , Message-ID: Well of course I am prejudiced towards the BBB but the cost difference is a lot more than you are stating. RTCM,s are $280 and you could put together a BBB system for around $150 or alot less if you want to mod a USB FOB. Of course this is minus radio in both cases. I have no experience with an RTCM. I think it has many nice features but many that the average person would never use. The upside to the RTCM is you would have one server that you could configure to do what you want rather than handling each individual BBB server. The end product would be the same but the administration would be different. You could administer remote BBB nodes via SSH/SCP very nicely. The downside of the one server multi RTCM is that if that server or its connection goes down the whole system is hosed. The RTCM's while maintaining local control would not be connected to anywhere. The BBB approach would be a stand alone server capable of anything an Allstar system could do. It is also very reliable and the new code that is coming out in a few days will be rock solid and suitable for remote locations. We have a basically BBB network here in PA/NJ with a central PC hub that they all connect to with mostly permanent connections. If the hub or internet connections to the hub goes down it will reconnect. The hub uses a startup macro to establish certain key connections. I find it is best to have the various nodes connected to the hub use permanent connections to the hub with a startup macro. If anything goes down it will come back up and reconnect will take place. 73 Doug WA3DSP http://www.crompton.com/hamradio From: tim.sawyer at mac.com Date: Sun, 28 Sep 2014 14:00:00 -0700 To: N1XBM at amsat.org CC: app_rpt-users at ohnosec.org Subject: Re: [App_rpt-users] Multiple nodes There are a few ways to do what you want ? that is permanently tie multiple repeaters together ? if I understand your question. First, permanent connections are not as permanent as you might expect. If the computer that initiated the permanent connections goes down the connection will not reestablish. However you can have a startup macro make the connection as Asterisk starts. Also, there seems to be some intermittent bug, which I?ve never pinned down, where permanent connections won?t reestablish with out forcing a disconnect first. Second way is with RTCMs. They are a whole lot easier to deploy and way more reliable than a bunch of USB type nodes, with the trade off in expense. Although by the time you buy a BBB and a URI you?re getting close to the expense of an RTCM. Of course you can go with a cheep sound dongle and an eBay used thin client PC. It?s the ?ol time/money/reliability trade off. I strongly recommend the RTCM approach. And a third option is called app_radbridge. If you don?t want to buy RTCMs this is probably the way to go. I?ve never tried to use it. The only documentation I am aware of is in the source which is reproduced here. /* This application is intended to provide a generic "bridging" functionality for radio-oriented Asterisk channels. The idea here is that certain radio applications lend themselves to needing a "generic" (passes audio and tx/rx keying completely transparently) to and from two or more endpoints. An example of such an appication might be replacing (or providing equivlent new functionaliy of) one or more full-duplex UHF control links with an IP-based one(s). app_radbridge allows multiple instances of radio-oriented channels transparently "bridged" together. The config file (radbridge.conf) allows specification of each "bridging" instance and what radio-oriented Asterisk channels are to be associated with it. There is no need for any other specificaiton of configuration. The file format for radbridge.conf departs somewhat from the standard usage (at least for radio stuff) of the Asterisk config file architecture. In most other radio-oriented cases, an instance of whatever it is gets defined as a "Stanza" in the config file. In this case, because of limitations in the way that Asterisk parses config files, that was not possible. Instead, all config information goes into the [general] stanza, and each line of config info defines a different instance of radio bridging. For example: [general] instance1 = Voter/1234,Radio/5678instance2 = Voter/1235,Radio/5679 This example would define two radio bridging instances "instance1" and "instance2", each with 2 channels associated with them. The supported channel types are "Voter" (chan_voter), "Radio" (chan_usbradio), "SimpleUsb" (chan_simpleusb), and "Zap" ("Dahdi") (chan_dahdi, for the couple of devices that use this channel driver, such as the PCIRadio card, and separate analog channels using an ARIB board or such). Rather then "adding" (which would actually be a lot of *removing* optionally) this functionality in app_rpt, it made more sense to create a separate application specifically for this purpose. In addition, this allows for a system that is merely provided for doing this bridging application and nothing else radio-oriented, to not have to run app_rpt at all. */ -- Tim :wq On Sep 28, 2014, at 12:28 PM, Robert Newberry wrote:So as it stands I have a one node system. I have another URI on the way and will have BBB soon. The eventual plan is to have a few repeaters and some simplex nodes at people's houses for RF hot spot access. What is the best way to tie these together? I understand you can set permanent links that will reestablish connection if lost.Is there other ways of accomplishing this? I only ask because I have my one node setup with email, autopatch and all other kinds of bells and whistles. I'd like to be able to do all of this from other RF locations and I wonder if I need to just set each node up accordingly or can one node be the workhorse and the other nodes just be dumb connections. Did I make any sense with that question? _______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From k5tra at austin.rr.com Mon Sep 29 01:21:24 2014 From: k5tra at austin.rr.com (k5tra) Date: Sun, 28 Sep 2014 20:21:24 -0500 Subject: [App_rpt-users] Multiple nodes Message-ID: <004401cfdb83$af690d90$0e3b28b0$@rr.com> Chuck, Actually, BBB for $55, uSD 16GB for $8 and USB FOB (modified) for $12 is well under $100 for a very good node. Tom / K5TRA -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Mon Sep 29 04:01:43 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Sun, 28 Sep 2014 21:01:43 -0700 Subject: [App_rpt-users] Multiple nodes In-Reply-To: <004401cfdb83$af690d90$0e3b28b0$@rr.com> References: <004401cfdb83$af690d90$0e3b28b0$@rr.com> Message-ID: I didn't mean to mis-repsrent the cost of a BBB or dis it in any way. I have a BBB and it?s a fine node. Here?s why I recommend RTCMs over any type of USB node in general and specifically in response to Robert?s question: Permanent connections are no where near as reliable as RTCMs in mixminus mode. Startup macros are very annoying when restarting and troubleshooting a node. Repeater ID, hangtime, courtesy tones, touch tone commands, cron jobs, tail messages etc, etc, are all set just once. Less is better: RTCMs are absolutely the least amount of hardware you can deploy. Entire solution comes from a single source. Easy to install by non Linux knowledgeable radio techs. No CF or SD to burn or CD to load. Just a few settings including audio. RX levels set with LED indicators. Lots of TX audio drive. Proven to work in harsh environments. No problematic and unpredictable USB issues. Have the capability to fail over to a backup server. Have ZERO repeat audio delay in duplex mode 3. If you might ever want to set up a voter or simulcast system you can. Squelch is the best there is, as good as or better than MICOR squelch. Firmware remotely upgradeable. Runs over a wide input voltage. On board RC pre and deemphasis filters. In all fairness there are a couple of drawbacks: Repeater duplex mode 3 has no TT muting. Other full duplex modes do not have this issue. This is somewhat subjective but my sense is the network needs to have lower loss and latency than with IAX. Yes, there are cheaper solutions but for my money, time and effort the RTCM is the best trade off. -- Tim :wq On Sep 28, 2014, at 6:21 PM, k5tra wrote: > Chuck, > Actually, BBB for $55, uSD 16GB for $8 and USB FOB (modified) for $12 is well under $100 for a very good node. > Tom / K5TRA > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.sawyer at mac.com Mon Sep 29 04:40:42 2014 From: tim.sawyer at mac.com (Tim Sawyer) Date: Sun, 28 Sep 2014 21:40:42 -0700 Subject: [App_rpt-users] Multiple nodes In-Reply-To: References: <004401cfdb83$af690d90$0e3b28b0$@rr.com> Message-ID: <2FC66AEE-B08C-4EBE-8F74-F690AC5A6146@mac.com> Doug, I just want to add to this that I think what you guys are doing with the BBB is absolutely fantastic. You, David and possibly others are doing a ton of work behind the scenes to make not only the BBB better but also AllStar. People don?t know the amount of work the BBB team has contributed. While I?m not going to recommend the BBB for every application it?s certainly a fine solution in many cases and it's only getting better. I look forward to your future efforts and the next release and the one after that, and the one after? How about an audio cape so we can ditch USB all together? -- Tim :wq On Sep 28, 2014, at 9:01 PM, Tim Sawyer wrote: > I didn't mean to mis-repsrent the cost of a BBB or dis it in any way. I have a BBB and it?s a fine node. Here?s why I recommend RTCMs over any type of USB node in general and specifically in response to Robert?s question: > > Permanent connections are no where near as reliable as RTCMs in mixminus mode. > Startup macros are very annoying when restarting and troubleshooting a node. > Repeater ID, hangtime, courtesy tones, touch tone commands, cron jobs, tail messages etc, etc, are all set just once. > Less is better: RTCMs are absolutely the least amount of hardware you can deploy. > Entire solution comes from a single source. > Easy to install by non Linux knowledgeable radio techs. > No CF or SD to burn or CD to load. > Just a few settings including audio. RX levels set with LED indicators. > Lots of TX audio drive. > Proven to work in harsh environments. > No problematic and unpredictable USB issues. > Have the capability to fail over to a backup server. > Have ZERO repeat audio delay in duplex mode 3. > If you might ever want to set up a voter or simulcast system you can. > Squelch is the best there is, as good as or better than MICOR squelch. > Firmware remotely upgradeable. > Runs over a wide input voltage. > On board RC pre and deemphasis filters. > > In all fairness there are a couple of drawbacks: > > Repeater duplex mode 3 has no TT muting. Other full duplex modes do not have this issue. > This is somewhat subjective but my sense is the network needs to have lower loss and latency than with IAX. > > Yes, there are cheaper solutions but for my money, time and effort the RTCM is the best trade off. > -- > Tim > :wq > > On Sep 28, 2014, at 6:21 PM, k5tra wrote: > >> Chuck, >> Actually, BBB for $55, uSD 16GB for $8 and USB FOB (modified) for $12 is well under $100 for a very good node. >> Tom / K5TRA >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Mon Sep 29 06:02:26 2014 From: doug at crompton.com (Doug Crompton) Date: Mon, 29 Sep 2014 02:02:26 -0400 Subject: [App_rpt-users] Multiple nodes In-Reply-To: <2FC66AEE-B08C-4EBE-8F74-F690AC5A6146@mac.com> References: <004401cfdb83$af690d90$0e3b28b0$@rr.com>, , <2FC66AEE-B08C-4EBE-8F74-F690AC5A6146@mac.com> Message-ID: Thanks Tim for your comments. It is a labor of love. We do it not to make any money but rather to improve the Allstar system both for us and everyone involved. As you mentioned the upcoming 1.2 release due out later this week has some rather substantial changes the biggest one being a tremendous increase in USB (and simpleusb) reliability. Hubs work well and so does WIFI and USB sticks for backup. There are also many other enhancements like backup and restore scripts that will be documented on the web page and in the announcement. As for the audio cape that is something we thought about but with the tremendous increase in USB reliability it is being put on the back burner for now. As a tease of future releases a complete rewrite of the USB channel driver is in the works getting away from the obsolete OSS model and using ALSA. That is only a part of the story though as the current code is really rather inefficient. This is maybe acceptable on a fast PC but on a slower processor it can be a real problem. Unfortunately the GPIO code will have to wait also as it is an integral part of the channel driver. Hopefully we will be able to begin testing on this in a month or two. USB has gotten a bad rap and in many cases it is not the HW's fault. The latest kernel has fixed many of the Linux/BBB USB problems and thanks to Dave, KB4FXC some bugs in both the simpleusb and usbradio code have been found that also caused severe USB issues. USB sound hardware is out there in abundance and once the code is optimized and GPIO added the unmodified cheap sound FOBS will work just fine. A user will be able to put together a complete system minus the radio for far less than $100. Judging from the number of downloads of the code there are many hundreds of new BBB systems out there already. 73 Doug WA3DSP http://www.crompton.com/hamradio Subject: Re: [App_rpt-users] Multiple nodes From: tim.sawyer at mac.com Date: Sun, 28 Sep 2014 21:40:42 -0700 CC: app_rpt-users at ohnosec.org To: doug at crompton.com Doug, I just want to add to this that I think what you guys are doing with the BBB is absolutely fantastic. You, David and possibly others are doing a ton of work behind the scenes to make not only the BBB better but also AllStar. People don?t know the amount of work the BBB team has contributed. While I?m not going to recommend the BBB for every application it?s certainly a fine solution in many cases and it's only getting better. I look forward to your future efforts and the next release and the one after that, and the one after? How about an audio cape so we can ditch USB all together? -- Tim :wq On Sep 28, 2014, at 9:01 PM, Tim Sawyer wrote:I didn't mean to mis-repsrent the cost of a BBB or dis it in any way. I have a BBB and it?s a fine node. Here?s why I recommend RTCMs over any type of USB node in general and specifically in response to Robert?s question: Permanent connections are no where near as reliable as RTCMs in mixminus mode. Startup macros are very annoying when restarting and troubleshooting a node. Repeater ID, hangtime, courtesy tones, touch tone commands, cron jobs, tail messages etc, etc, are all set just once. Less is better: RTCMs are absolutely the least amount of hardware you can deploy.Entire solution comes from a single source.Easy to install by non Linux knowledgeable radio techs.No CF or SD to burn or CD to load. Just a few settings including audio. RX levels set with LED indicators.Lots of TX audio drive.Proven to work in harsh environments.No problematic and unpredictable USB issues.Have the capability to fail over to a backup server.Have ZERO repeat audio delay in duplex mode 3.If you might ever want to set up a voter or simulcast system you can.Squelch is the best there is, as good as or better than MICOR squelch. Firmware remotely upgradeable.Runs over a wide input voltage. On board RC pre and deemphasis filters. In all fairness there are a couple of drawbacks: Repeater duplex mode 3 has no TT muting. Other full duplex modes do not have this issue.This is somewhat subjective but my sense is the network needs to have lower loss and latency than with IAX. Yes, there are cheaper solutions but for my money, time and effort the RTCM is the best trade off. -- Tim :wq On Sep 28, 2014, at 6:21 PM, k5tra wrote:Chuck,Actually, BBB for $55, uSD 16GB for $8 and USB FOB (modified) for $12 is well under $100 for a very good node.Tom / K5TRA_______________________________________________ App_rpt-users mailing list App_rpt-users at 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 at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From N1XBM at amsat.org Mon Sep 29 12:55:13 2014 From: N1XBM at amsat.org (Robert Newberry) Date: Mon, 29 Sep 2014 08:55:13 -0400 Subject: [App_rpt-users] Email asterisk Message-ID: I use K0kn email scripts with Gmail. Things will chug along fine for a few days and then google locks me out and I have to log in via a Web browser and type in the goofy letters to get things happy. Anyone else have this problem? Anyone know how to fix it? Or better yet what I'm doing wrong. -------------- next part -------------- An HTML attachment was scrubbed... URL: From N1XBM at amsat.org Mon Sep 29 12:57:25 2014 From: N1XBM at amsat.org (Robert Newberry) Date: Mon, 29 Sep 2014 08:57:25 -0400 Subject: [App_rpt-users] Multiple nodes In-Reply-To: References: <004401cfdb83$af690d90$0e3b28b0$@rr.com> <2FC66AEE-B08C-4EBE-8F74-F690AC5A6146@mac.com> Message-ID: I appreciate all of the feedback. I almost feel like there are situations that a RTCM will be perfect and others I'd rather use a BBB -------------- next part -------------- An HTML attachment was scrubbed... URL: From cypresstower at yahoo.com Mon Sep 29 15:11:15 2014 From: cypresstower at yahoo.com (Johnny Keeker) Date: Mon, 29 Sep 2014 08:11:15 -0700 Subject: [App_rpt-users] Multiple nodes In-Reply-To: <004401cfdb83$af690d90$0e3b28b0$@rr.com> Message-ID: <1412003475.19447.YahooMailBasic@web163601.mail.gq1.yahoo.com> BBB has one problem, I get complaints about a squelch crash I'm about to install an audio delay board... JK -------------------------------------------- On Sun, 9/28/14, k5tra wrote: Subject: Re: [App_rpt-users] Multiple nodes To: app_rpt-users at ohnosec.org Date: Sunday, September 28, 2014, 9:21 PM Chuck, Actually, BBB for $55, uSD 16GB for $8 and? USB FOB (modified) for $12 is well under $100 for a very good node. Tom / K5TRA -----Inline Attachment Follows----- _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. From k5tra at austin.rr.com Mon Sep 29 15:25:41 2014 From: k5tra at austin.rr.com (k5tra) Date: Mon, 29 Sep 2014 10:25:41 -0500 Subject: [App_rpt-users] Multiple nodes Message-ID: <002a01cfdbf9$a18855c0$e4990140$@rr.com> We haven't had squelch burst problem (on BBB) using SimpleUSB and COS line from RX (w/ reverse burst). TRA -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at crompton.com Mon Sep 29 16:52:17 2014 From: doug at crompton.com (Doug Crompton) Date: Mon, 29 Sep 2014 12:52:17 -0400 Subject: [App_rpt-users] Multiple nodes In-Reply-To: <1412003475.19447.YahooMailBasic@web163601.mail.gq1.yahoo.com> References: <004401cfdb83$af690d90$0e3b28b0$@rr.com>, <1412003475.19447.YahooMailBasic@web163601.mail.gq1.yahoo.com> Message-ID: Johnny, Well this is not a BBB problem but rather the fact that when using simpleusb you don't have the SW capability to eliminate it. I would say that someone is just too picky but if the tail is longer than normal then it can be a problem. The squelch tail source is the fault of the RX at the particular node it is coming from. Sometimes even with PL you need to adjust the squelch up because of PL shutdown delays and also local noise problems. It is more of a problem with some radios than others. We use the Alincos quites a bit and with them the squelch setting norm is anywhere from 4 to 7 and not the default 2. 73 Doug WA3DSP http://www.crompton.com/hamradio > Date: Mon, 29 Sep 2014 08:11:15 -0700 > From: cypresstower at yahoo.com > To: app_rpt-users at ohnosec.org; k5tra at austin.rr.com > Subject: Re: [App_rpt-users] Multiple nodes > > BBB has one problem, I get complaints about a squelch crash > I'm about to install an audio delay board... > JK > -------------------------------------------- > On Sun, 9/28/14, k5tra wrote: > > Subject: Re: [App_rpt-users] Multiple nodes > To: app_rpt-users at ohnosec.org > Date: Sunday, September 28, 2014, 9:21 PM > > > > > > > > > > > > > > > > > Chuck, > > Actually, BBB for $55, uSD > 16GB for $8 and USB FOB > (modified) for $12 is well under $100 for a very good > node. > > Tom / K5TRA > > > > > > > -----Inline Attachment Follows----- > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at 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 at 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cypresstower at yahoo.com Mon Sep 29 20:11:42 2014 From: cypresstower at yahoo.com (Johnny Keeker) Date: Mon, 29 Sep 2014 13:11:42 -0700 Subject: [App_rpt-users] Multiple nodes In-Reply-To: <002a01cfdbf9$a18855c0$e4990140$@rr.com> Message-ID: <1412021502.66285.YahooMailBasic@web163602.mail.gq1.yahoo.com> I'm now using a motorola GM300. On the radio side it's clean but on the internet side, I still have a squelch burst. Also used an alinco dr135, it's worse. In both instances I'm using simpleusb and cor. I've also tried usbradio, it eliminates the burst but there are other artifacts it produces, like a ripple in the audio peaks. Oh Well JK -------------------------------------------- On Mon, 9/29/14, k5tra wrote: Subject: [App_rpt-users] Multiple nodes To: app_rpt-users at ohnosec.org Date: Monday, September 29, 2014, 11:25 AM We haven?t had squelch burst problem (on BBB) using SimpleUSB and COS line from RX (w/ reverse burst). TRA -----Inline Attachment Follows----- _______________________________________________ App_rpt-users mailing list App_rpt-users at 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. From tom.caspar at cpcomms.com Tue Sep 30 03:06:30 2014 From: tom.caspar at cpcomms.com (Tom Caspar) Date: Tue, 30 Sep 2014 03:06:30 +0000 Subject: [App_rpt-users] (no subject) Message-ID: <85B3C088F7834740B0EB04F281E7CD5B084CCDDB@CPNYMAIL2.cpcomm.int> I have a private node with 6 voted receivers usng RTCMs. I'd like to add a 7th RTCM to this node that is always mixed in rather than voted. I'm able to make this rtcm work as a 7th voted rceive with no problem. Everything Ive read seems to indicate that if I change Gps pps polarity to "none" this will achieve my desired results, however I am unable to get audio out of my transmit rtcm from thiis 7th site. It does change color to cyan in Allmon indicating it is non voted input but I do not get any indication or audio when that units COR goes active. Is there something I'm missing? Thanks, Tom From cypresstower at yahoo.com Tue Sep 30 03:19:06 2014 From: cypresstower at yahoo.com (Johnny Keeker) Date: Mon, 29 Sep 2014 20:19:06 -0700 Subject: [App_rpt-users] Multiple nodes Message-ID: <1412047146.92683.YahooMailBasic@web163604.mail.gq1.yahoo.com> Good thought, although I am using rxondelay. I discovered the burst is just inherent of a simplex node. Just a note, I configured the BBB for usbradio and enabled the rxsquelchdelay with success, however the audio produced a pulsing attribute. A tradeoff, so I'm back to simpleusb. Next I plan to try an audio delay board. Over kill but it's all in the spirit of ham radio... Thanks to those responsible for the BBB JK -------------------------------------------- On Mon, 9/29/14, k5tra wrote: Subject: RE: [App_rpt-users] Multiple nodes To: "'Johnny Keeker'" Date: Monday, September 29, 2014, 5:29 PM Hi Johnny, I've been using TK-941 radios in full duplex repeater mode. I am using a COS interface/buffer circuit in the RX radio and a DMK URI. Is your GM300 running as a simplex link radio? If so, 'wonder if rxondelay parameter would help? Tom / K5TRA -----Original Message----- From: Johnny Keeker [mailto:cypresstower at yahoo.com] Sent: Monday, September 29, 2014 3:12 PM To: app_rpt-users at ohnosec.org; k5tra Subject: Re: [App_rpt-users] Multiple nodes I'm now using a motorola GM300. On the radio side it's clean but on the internet side, I still have a squelch burst. Also used an alinco dr135, it's worse. In both instances I'm using simpleusb and cor. I've also tried usbradio, it eliminates the burst but there are other artifacts it produces, like a ripple in the audio peaks. Oh Well JK -------------------------------------------- On Mon, 9/29/14, k5tra wrote: ? Subject: [App_rpt-users] Multiple nodes ? To: app_rpt-users at ohnosec.org ? Date: Monday, September 29, 2014, 11:25 AM ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? We haven?t had ? squelch burst problem (on BBB) using ? SimpleUSB and COS line from RX (w/ reverse burst). ? ? TRA ? ? ? ? ? ? ? -----Inline Attachment Follows----- ? _______________________________________________ ? App_rpt-users mailing list ? App_rpt-users at 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. ? From mike at midnighteng.com Tue Sep 30 05:29:26 2014 From: mike at midnighteng.com (mike at midnighteng.com) Date: Mon, 29 Sep 2014 22:29:26 -0700 Subject: [App_rpt-users] NEW Bash Security Update #3 Message-ID: <20140929222926.71befee5dbd13c5325dd1a521b4e73ee.436efed40f.wbe@email06.secureserver.net> An HTML attachment was scrubbed... URL: