May 2012 - App_rpt-users - lists.keekles.org

Re: [App_rpt-users] EchoLink
by Alan Adamson 23 May '12

23 May '12

BTW, from that box I can issue a telnet server1.echolink.org 5200 and get a connection, so that part isn't port forwarding related….At this point it seems it has to do with the build…. hmm… betting it's a library enhancement that hasn't been addressed…. Still debugging… The connect is failing most of the time… Wonder if putting those IP to names in the hosts file would help it… gonna try that now. Alan From: Matt Roberts [mailto:n9gmr@me.com] Sent: Wednesday, May 23, 2012 4:04 PM To: Alan Adamson Subject: Re: [App_rpt-users] EchoLink Did you forward port 5200? I think that uses TCP. Matt Roberts Sent from my iPad On May 23, 2012, at 3:59 PM, Alan Adamson <adamson_alan(a)hotmail.com> wrote: if you are talking about the UDP ports (5198 and 5199), then yes, but this would be a TCP issue as I'm sure there is some connection that is made (outbound from me to a registration server) and that I would assume would be on a TCP connection… Outbound connections are not blocked by my router and I have the UDP ports forwarded as noted above and still the same error responses. From: Matt Roberts [mailto:n9gmr@me.com] Sent: Wednesday, May 23, 2012 3:15 PM To: Alan Adamson Subject: Re: [App_rpt-users] EchoLink Did you forward the required ports in your router? Matt Roberts n9gmr(a)me.com Sent from my iPhone On May 23, 2012, at 2:22 PM, Alan Adamson <adamson_alan(a)hotmail.com> wrote: Doesn't get much easier than this… straight from the samples config file with the information changed as required. [el0] confmode=no call=W7QO-R ; Change this! pwd=<changed to my password> ; Change this! name=Test ; Change this to your real name! qth=Atlanta,GA ; Change this to your actual QTH! email=adamson_alan(a)hotmail.com ; Change this! maxstns=20 rtcptimeout=10 node=710254 ; Change this! recfile=/tmp/recorded.gsm astnode=28578 ; Change this to your active Allstar node number! context=radio-secure server1=server1.echolink.org server2=server2.echolink.org server3=server3.echolink.org With that setup I get these errors which have been discussed before… and it doesn't matter if I change the server names to naeast.echolink.org, etc. [May 23 14:19:52] ERROR[2033] chan_echolink.c: Error in parsing header on server1.echolink.org [May 23 14:20:22] ERROR[2031] chan_echolink.c: connect() failed to connect to the Echolink server server2.echolink.org [May 23 14:20:22] ERROR[2033] chan_echolink.c: connect() failed to connect to the Echolink server server2.echolink.org [May 23 14:20:43] ERROR[2033] chan_echolink.c: Unable to connect to directory server server2.echolink.org [May 23 14:20:43] ERROR[2033] chan_echolink.c: Error in parsing header on server3.echolink.org [May 23 14:21:03] ERROR[2033] chan_echolink.c: Error in parsing header on server1.echolink.org I'll go look to see if there have been changes to the chan_echolink.c file that I'm not running but I just built everything with the distribution makefile yesterday. This was talked about on this forum last year, but I never found a resolution other than it worked for some and not for others…??? Alan From: Ken [mailto:ke2n@cs.com] Sent: Wednesday, May 23, 2012 1:23 PM To: adamson_alan(a)hotmail.com Subject: Re: [App_rpt-users] EchoLink It is not unusual for one of the echolink servers to be down; as long as you can talk to *one* of them, it should work. I think that, after you come on line, it may be some time before you can actually USE the echolink feature, while you wait for their system to updpate. Incorrect header information is another story - if you post your configuration (minus the password) maybe someone will see a problem - or not - in which case there was some compile issue ... Ken -----Original Message----- From: Alan Adamson <adamson_alan(a)hotmail.com> To: App_rpt-users <App_rpt-users(a)ohnosec.org> Sent: Wed, May 23, 2012 8:34 am Subject: [App_rpt-users] EchoLink So, learning to run before I can walk :)… With my newfound enthusiasm and a debian install. I wanted to test out functionality figured an easy way was to see about getting EchoLink working as well. So I added the echolink.conf file, made the changes for my specific EchoLink node and restarted. However I get all these errors about not being able to connect to their servers, header information not being correct, etc. I did some scanning and found that others have experiences the same thing. Anyone have this working on a recent install? Second, is there some type of *echo* conference bridge or *reflector* (Sorry for the use of the term, but it's appropriate)… I need some way to test audio without being live on the air, etc? Alan _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

New node build problems
by Matt Beasant 23 May '12

23 May '12

I Have just built a new test node out of a HP thin client. 1GHz processor and 512Mb RAM. It seems to work OK but seems to take an age to start up the Asterisk application. Not boot up as such but once the Asterisk application starts ( i.e. I can log into the CLI with the asterisk -r command ) it seems to be some time until the LED starts to flash on the USB fob. The node seems to be loading beagle board channel drivers and Voter channel drivers, none of which I am using - how could I stop it loading these channel drivers to speed up my startup? Also, I have this node set to connect to a hub via the permalink cmd I put in the startup macro - this doesnt seem to be running for some reason? Maybe its related to the slow startup? Any help greatly appreciated, Many thanks, Matt G4RKY

1 0

Re: [App_rpt-users] EchoLink
by Alan Adamson 23 May '12

23 May '12

Doesn't get much easier than this… straight from the samples config file with the information changed as required. [el0] confmode=no call=W7QO-R ; Change this! pwd=<changed to my password> ; Change this! name=Test ; Change this to your real name! qth=Atlanta,GA ; Change this to your actual QTH! email=adamson_alan(a)hotmail.com ; Change this! maxstns=20 rtcptimeout=10 node=710254 ; Change this! recfile=/tmp/recorded.gsm astnode=28578 ; Change this to your active Allstar node number! context=radio-secure server1=server1.echolink.org server2=server2.echolink.org server3=server3.echolink.org With that setup I get these errors which have been discussed before… and it doesn't matter if I change the server names to naeast.echolink.org, etc. [May 23 14:19:52] ERROR[2033] chan_echolink.c: Error in parsing header on server1.echolink.org [May 23 14:20:22] ERROR[2031] chan_echolink.c: connect() failed to connect to the Echolink server server2.echolink.org [May 23 14:20:22] ERROR[2033] chan_echolink.c: connect() failed to connect to the Echolink server server2.echolink.org [May 23 14:20:43] ERROR[2033] chan_echolink.c: Unable to connect to directory server server2.echolink.org [May 23 14:20:43] ERROR[2033] chan_echolink.c: Error in parsing header on server3.echolink.org [May 23 14:21:03] ERROR[2033] chan_echolink.c: Error in parsing header on server1.echolink.org I'll go look to see if there have been changes to the chan_echolink.c file that I'm not running but I just built everything with the distribution makefile yesterday. This was talked about on this forum last year, but I never found a resolution other than it worked for some and not for others…??? Alan From: Ken [mailto:ke2n@cs.com] Sent: Wednesday, May 23, 2012 1:23 PM To: adamson_alan(a)hotmail.com Subject: Re: [App_rpt-users] EchoLink It is not unusual for one of the echolink servers to be down; as long as you can talk to *one* of them, it should work. I think that, after you come on line, it may be some time before you can actually USE the echolink feature, while you wait for their system to updpate. Incorrect header information is another story - if you post your configuration (minus the password) maybe someone will see a problem - or not - in which case there was some compile issue ... Ken -----Original Message----- From: Alan Adamson <adamson_alan(a)hotmail.com> To: App_rpt-users <App_rpt-users(a)ohnosec.org> Sent: Wed, May 23, 2012 8:34 am Subject: [App_rpt-users] EchoLink So, learning to run before I can walk :)… With my newfound enthusiasm and a debian install. I wanted to test out functionality figured an easy way was to see about getting EchoLink working as well. So I added the echolink.conf file, made the changes for my specific EchoLink node and restarted. However I get all these errors about not being able to connect to their servers, header information not being correct, etc. I did some scanning and found that others have experiences the same thing. Anyone have this working on a recent install? Second, is there some type of *echo* conference bridge or *reflector* (Sorry for the use of the term, but it's appropriate)… I need some way to test audio without being live on the air, etc? Alan _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

2 1

Re: [App_rpt-users] EchoLink
by Alan Adamson 23 May '12

23 May '12

I didn't, but it's an outgoing requested port so I shouldn't need to forward it… I will, but because the allstar box, connects to it, and via TCP, it shouldn't need to be forwarded… Alan From: Matt Roberts [mailto:n9gmr@me.com] Sent: Wednesday, May 23, 2012 4:04 PM To: Alan Adamson Subject: Re: [App_rpt-users] EchoLink Did you forward port 5200? I think that uses TCP. Matt Roberts Sent from my iPad On May 23, 2012, at 3:59 PM, Alan Adamson <adamson_alan(a)hotmail.com> wrote: if you are talking about the UDP ports (5198 and 5199), then yes, but this would be a TCP issue as I'm sure there is some connection that is made (outbound from me to a registration server) and that I would assume would be on a TCP connection… Outbound connections are not blocked by my router and I have the UDP ports forwarded as noted above and still the same error responses. From: Matt Roberts [mailto:n9gmr@me.com] Sent: Wednesday, May 23, 2012 3:15 PM To: Alan Adamson Subject: Re: [App_rpt-users] EchoLink Did you forward the required ports in your router? Matt Roberts n9gmr(a)me.com Sent from my iPhone On May 23, 2012, at 2:22 PM, Alan Adamson <adamson_alan(a)hotmail.com> wrote: Doesn't get much easier than this… straight from the samples config file with the information changed as required. [el0] confmode=no call=W7QO-R ; Change this! pwd=<changed to my password> ; Change this! name=Test ; Change this to your real name! qth=Atlanta,GA ; Change this to your actual QTH! email=adamson_alan(a)hotmail.com ; Change this! maxstns=20 rtcptimeout=10 node=710254 ; Change this! recfile=/tmp/recorded.gsm astnode=28578 ; Change this to your active Allstar node number! context=radio-secure server1=server1.echolink.org server2=server2.echolink.org server3=server3.echolink.org With that setup I get these errors which have been discussed before… and it doesn't matter if I change the server names to naeast.echolink.org, etc. [May 23 14:19:52] ERROR[2033] chan_echolink.c: Error in parsing header on server1.echolink.org [May 23 14:20:22] ERROR[2031] chan_echolink.c: connect() failed to connect to the Echolink server server2.echolink.org [May 23 14:20:22] ERROR[2033] chan_echolink.c: connect() failed to connect to the Echolink server server2.echolink.org [May 23 14:20:43] ERROR[2033] chan_echolink.c: Unable to connect to directory server server2.echolink.org [May 23 14:20:43] ERROR[2033] chan_echolink.c: Error in parsing header on server3.echolink.org [May 23 14:21:03] ERROR[2033] chan_echolink.c: Error in parsing header on server1.echolink.org I'll go look to see if there have been changes to the chan_echolink.c file that I'm not running but I just built everything with the distribution makefile yesterday. This was talked about on this forum last year, but I never found a resolution other than it worked for some and not for others…??? Alan From: Ken [mailto:ke2n@cs.com] Sent: Wednesday, May 23, 2012 1:23 PM To: adamson_alan(a)hotmail.com Subject: Re: [App_rpt-users] EchoLink It is not unusual for one of the echolink servers to be down; as long as you can talk to *one* of them, it should work. I think that, after you come on line, it may be some time before you can actually USE the echolink feature, while you wait for their system to updpate. Incorrect header information is another story - if you post your configuration (minus the password) maybe someone will see a problem - or not - in which case there was some compile issue ... Ken -----Original Message----- From: Alan Adamson <adamson_alan(a)hotmail.com> To: App_rpt-users <App_rpt-users(a)ohnosec.org> Sent: Wed, May 23, 2012 8:34 am Subject: [App_rpt-users] EchoLink So, learning to run before I can walk :)… With my newfound enthusiasm and a debian install. I wanted to test out functionality figured an easy way was to see about getting EchoLink working as well. So I added the echolink.conf file, made the changes for my specific EchoLink node and restarted. However I get all these errors about not being able to connect to their servers, header information not being correct, etc. I did some scanning and found that others have experiences the same thing. Anyone have this working on a recent install? Second, is there some type of *echo* conference bridge or *reflector* (Sorry for the use of the term, but it's appropriate)… I need some way to test audio without being live on the air, etc? Alan _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

Re: [App_rpt-users] EchoLink
by Alan Adamson 23 May '12

23 May '12

if you are talking about the UDP ports (5198 and 5199), then yes, but this would be a TCP issue as I'm sure there is some connection that is made (outbound from me to a registration server) and that I would assume would be on a TCP connection… Outbound connections are not blocked by my router and I have the UDP ports forwarded as noted above and still the same error responses. From: Matt Roberts [mailto:n9gmr@me.com] Sent: Wednesday, May 23, 2012 3:15 PM To: Alan Adamson Subject: Re: [App_rpt-users] EchoLink Did you forward the required ports in your router? Matt Roberts n9gmr(a)me.com Sent from my iPhone On May 23, 2012, at 2:22 PM, Alan Adamson <adamson_alan(a)hotmail.com> wrote: Doesn't get much easier than this… straight from the samples config file with the information changed as required. [el0] confmode=no call=W7QO-R ; Change this! pwd=<changed to my password> ; Change this! name=Test ; Change this to your real name! qth=Atlanta,GA ; Change this to your actual QTH! email=adamson_alan(a)hotmail.com ; Change this! maxstns=20 rtcptimeout=10 node=710254 ; Change this! recfile=/tmp/recorded.gsm astnode=28578 ; Change this to your active Allstar node number! context=radio-secure server1=server1.echolink.org server2=server2.echolink.org server3=server3.echolink.org With that setup I get these errors which have been discussed before… and it doesn't matter if I change the server names to naeast.echolink.org, etc. [May 23 14:19:52] ERROR[2033] chan_echolink.c: Error in parsing header on server1.echolink.org [May 23 14:20:22] ERROR[2031] chan_echolink.c: connect() failed to connect to the Echolink server server2.echolink.org [May 23 14:20:22] ERROR[2033] chan_echolink.c: connect() failed to connect to the Echolink server server2.echolink.org [May 23 14:20:43] ERROR[2033] chan_echolink.c: Unable to connect to directory server server2.echolink.org [May 23 14:20:43] ERROR[2033] chan_echolink.c: Error in parsing header on server3.echolink.org [May 23 14:21:03] ERROR[2033] chan_echolink.c: Error in parsing header on server1.echolink.org I'll go look to see if there have been changes to the chan_echolink.c file that I'm not running but I just built everything with the distribution makefile yesterday. This was talked about on this forum last year, but I never found a resolution other than it worked for some and not for others…??? Alan From: Ken [mailto:ke2n@cs.com] Sent: Wednesday, May 23, 2012 1:23 PM To: adamson_alan(a)hotmail.com Subject: Re: [App_rpt-users] EchoLink It is not unusual for one of the echolink servers to be down; as long as you can talk to *one* of them, it should work. I think that, after you come on line, it may be some time before you can actually USE the echolink feature, while you wait for their system to updpate. Incorrect header information is another story - if you post your configuration (minus the password) maybe someone will see a problem - or not - in which case there was some compile issue ... Ken -----Original Message----- From: Alan Adamson <adamson_alan(a)hotmail.com> To: App_rpt-users <App_rpt-users(a)ohnosec.org> Sent: Wed, May 23, 2012 8:34 am Subject: [App_rpt-users] EchoLink So, learning to run before I can walk :)… With my newfound enthusiasm and a debian install. I wanted to test out functionality figured an easy way was to see about getting EchoLink working as well. So I added the echolink.conf file, made the changes for my specific EchoLink node and restarted. However I get all these errors about not being able to connect to their servers, header information not being correct, etc. I did some scanning and found that others have experiences the same thing. Anyone have this working on a recent install? Second, is there some type of *echo* conference bridge or *reflector* (Sorry for the use of the term, but it's appropriate)… I need some way to test audio without being live on the air, etc? Alan _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

Re: [App_rpt-users] App_rpt-users Digest, Vol 39, Issue 35
by Bradley Haney 23 May '12

23 May '12

Is the Port Fwd set up on the router? On Wed, May 23, 2012 at 1:22 PM, <app_rpt-users-request(a)ohnosec.org> wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users(a)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(a)ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner(a)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: EchoLink (Alan Adamson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 23 May 2012 14:22:00 -0400 > From: Alan Adamson <adamson_alan(a)hotmail.com> > To: <App_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] EchoLink > Message-ID: <SNT108-DS24FA88593B3FF16DB7AE80E9030(a)phx.gbl> > Content-Type: text/plain; charset="utf-8" > > Doesn't get much easier than this? straight from the samples config file with the information changed as required. > > [el0] > confmode=no > call=W7QO-R ; Change this! > pwd=<changed to my password> ; Change this! > name=Test ; Change this to your real name! > qth=Atlanta,GA ; Change this to your actual QTH! > email=adamson_alan(a)hotmail.com ; Change this! > maxstns=20 > rtcptimeout=10 > node=710254 ; Change this! > recfile=/tmp/recorded.gsm > astnode=28578 ; Change this to your active Allstar node number! > context=radio-secure > server1=server1.echolink.org > server2=server2.echolink.org > server3=server3.echolink.org > > With that setup I get these errors which have been discussed before? and it doesn't matter if I change the server names to naeast.echolink.org, etc. > > [May 23 14:19:52] ERROR[2033] chan_echolink.c: Error in parsing header on server1.echolink.org > [May 23 14:20:22] ERROR[2031] chan_echolink.c: connect() failed to connect to the Echolink server server2.echolink.org > [May 23 14:20:22] ERROR[2033] chan_echolink.c: connect() failed to connect to the Echolink server server2.echolink.org > [May 23 14:20:43] ERROR[2033] chan_echolink.c: Unable to connect to directory server server2.echolink.org > [May 23 14:20:43] ERROR[2033] chan_echolink.c: Error in parsing header on server3.echolink.org > [May 23 14:21:03] ERROR[2033] chan_echolink.c: Error in parsing header on server1.echolink.org > > I'll go look to see if there have been changes to the chan_echolink.c file that I'm not running but I just built everything with the distribution makefile yesterday. This was talked about on this forum last year, but I never found a resolution other than it worked for some and not for others???? > > Alan > > From: Ken [mailto:ke2n@cs.com] > Sent: Wednesday, May 23, 2012 1:23 PM > To: adamson_alan(a)hotmail.com > Subject: Re: [App_rpt-users] EchoLink > > It is not unusual for one of the echolink servers to be down; as long as you can talk to *one* of them, it should work. > I think that, after you come on line, it may be some time before you can actually USE the echolink feature, while you wait for their system to updpate. > Incorrect header information is another story - if you post your configuration (minus the password) maybe someone will see a problem - or not - in which case there was some compile issue ... > > Ken > -----Original Message----- > From: Alan Adamson <adamson_alan(a)hotmail.com> > To: App_rpt-users <App_rpt-users(a)ohnosec.org> > Sent: Wed, May 23, 2012 8:34 am > Subject: [App_rpt-users] EchoLink > So, learning to run before I can walk :)? With my newfound enthusiasm and a debian install. I wanted to test out functionality figured an easy way was to see about getting EchoLink working as well. > So I added the echolink.conf file, made the changes for my specific EchoLink node and restarted. However I get all these errors about not being able to connect to their servers, header information not being correct, etc. > I did some scanning and found that others have experiences the same thing. Anyone have this working on a recent install? > Second, is there some type of *echo* conference bridge or *reflector* (Sorry for the use of the term, but it's appropriate)? I need some way to test audio without being live on the air, etc? > Alan > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >

1 0

EchoLink
by Alan Adamson 23 May '12

23 May '12

So, learning to run before I can walk :). With my newfound enthusiasm and a debian install. I wanted to test out functionality figured an easy way was to see about getting EchoLink working as well. So I added the echolink.conf file, made the changes for my specific EchoLink node and restarted. However I get all these errors about not being able to connect to their servers, header information not being correct, etc. I did some scanning and found that others have experiences the same thing. Anyone have this working on a recent install? Second, is there some type of *echo* conference bridge or *reflector* (Sorry for the use of the term, but it's appropriate). I need some way to test audio without being live on the air, etc? Alan

2 1

OMG - I think it works!
by Alan Adamson 23 May '12

23 May '12

So I hope you all will appreciate a little yelling and screaming!!! Here is what I did today.. I took a brand new DN2800MT Atom MB. Added 2G of ram, and 60G SSD drive and put that in an M350 case. I then took the Debian *64bit* net install, the latest - 6.0.5 and I used a tool to put it on a USB stick. From there, I booted from the usb stick and I installed Debian. I had been to this point prior so I knew how to get here. Next I knew I needed to get new drivers for the ALSA support. So I went to Realtek and downloaded their linux kernel modules.. Built and installed them - this meant I also had to put a development environment on the debian install through apt-get. Ok, so far so good. I had seen this as my motivation to get this working on Debian. http://kriskirkland.com/?p=143 I took this install script and modified it a little. Also because I can't get to the dl.allstarlink.org site directly (DNS issues), I got the files I needed through my cell connection and used them locally. During the install, you build the entire source for everything. This was my first challenge, there were errors in the source that I had to fix. As it turns out, it was just include files that needed to be added due to the recent kernel that I'm running. I also had to fix the udev rules for zaptel, they were basically wrong for the version of udev that is running, nothing dramatic, just some "="'s that needed to be "==" due to a change in the udev syntax. Next I added the ixaRPT setup and rebooted. Wow, a clean reboot. Nothing wrong and everything seems to be working. I was using the allstarlink node list to determine if I was up or not and I've since found out that I've got one little issue to work through. On a reboot, the system is functional, but I don't show as registered in the list. If I manually stop and start asterisk, I show up correctly. So. Bottom line, I seem to be functional and on the allstar link network with node 28578 - now before you all start connecting to me. There are no radios attached just yet. :). I'm waiting on my URI's and I've got an RTCM setting here that I need to look at in the coming days. But thanks to everyone that helped with suggestions and ideas. And thanks to Bryan Boyle for connecting to me and letting me know that audio was working both way, at least from my windows machine via the iaxRpt client. I also have the X-Lite client configured to connect to the sip.allstarlink site, but I don't know how to make PTT work with it :). I'll figure that out next. Bottom line, a pristine Debian install, with a Debianish ACID like install, on a very late model Atom MB.. Most would say 3 strikes, but man does it feel good when it works! Ok, one quick question. The *only * notice I get on bootup is something about a zap(tel) timer and using ztdummy instead.. Is that normal? Alan

3 2

Any RTCM Voter Installations Out There?
by Frederick Bray 23 May '12

23 May '12

I very recently purchased my RTCM module and will be ordering a second one soon. It will be a while before I have time to get it all running, but I thought I'd see whether there are any "average" users out there who might relate their experiences for the purpose of helping to educate me. (Jim Dixon has very kindly offered assistance, but because of work commitments it will be a while before I can meet with him.) I gather that chan_voter isn't included in the current ACID CENTOS distribution and will need to be compiled on my system. I can do this as I have a little bit of UNIX/Linux experience, but I don't want re-invent the wheel unnecessarily. Is there any documentation that I should be reading in addition to that on the voter project site? Thanks. 73, Fred Bray W6WAW

5 4

Debian - Allstar install - from scratch - Phase 1
by Alan Adamson 23 May '12

23 May '12

In an effort to document what I did, I'm going to do it in phases. Here is the basic Debian install process. a) I downloaded the netinst files from this link - http://www.debian.org/distrib/, I used the 32bit one for an N270 install that I put IRLP on, and the 64bit one for an N2800 install that I did the Allstar install on. b) I then used the bootable usb creator from pendrivelinux.com - get it here for windows http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/ c) you select a distribution, browse to the ISO you just downloaded above, select the usb drive and either format or not and select create. .what you'll have is a bootable usb drive with the distribution you selected above on it to boot from. d) setup the right boot order in the bios on your mother board, and poof, you should be able to install debian from that process. You'll need the box connected to the network so that it can go get all the right modules. I pretty much created a vanilla install, only thing I did install was ssh and sql, and the last selection which I can't remember right now but was core related. When it was ready to reboot, I had a Debian install done. Ok, phase 2 will be around what you need to do before you install anything further. Alan

1 0