I'm working on a Raspberry Pi hub and it appeared to install everything fine and I went through the ASL quick setup wizard. The node is reporting it's online and such but when I try connecting to it from another node it tells me the connection failed or timed out. It seems like I had a similar issue with our club node and it's possibly a dahdi problem but I don't know how to fix it? Any suggestions? 73, Russell Thomas, KV4S
sorry the new node number is 49308 <http://stats.allstarlink.org/nodeinfo.cgi?node=49308>. On Wed, Nov 7, 2018 at 2:26 PM Russell Thomas <russell@kv4s.com> wrote:
I'm working on a Raspberry Pi hub and it appeared to install everything fine and I went through the ASL quick setup wizard.
The node is reporting it's online and such but when I try connecting to it from another node it tells me the connection failed or timed out.
It seems like I had a similar issue with our club node and it's possibly a dahdi problem but I don't know how to fix it?
Any suggestions?
73, Russell Thomas, KV4S
I just had the same problem with my clubs ASL node and I am trying to remember how I fixed it....something to do with the Bind address in IAX.conf.....I had to set it to like 0.0.0.0 to bind on all IP's I think? Also check to make sure you have the right ports forwarded to the PI. On Wed, Nov 7, 2018 at 3:28 PM Russell Thomas <russell@kv4s.com> wrote:
sorry the new node number is 49308 <http://stats.allstarlink.org/nodeinfo.cgi?node=49308>.
On Wed, Nov 7, 2018 at 2:26 PM Russell Thomas <russell@kv4s.com> wrote:
I'm working on a Raspberry Pi hub and it appeared to install everything fine and I went through the ASL quick setup wizard.
The node is reporting it's online and such but when I try connecting to it from another node it tells me the connection failed or timed out.
It seems like I had a similar issue with our club node and it's possibly a dahdi problem but I don't know how to fix it?
Any suggestions?
73, Russell Thomas, KV4S
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
-- Jeff Lehman, KC8QCH E-mail: kc8qch@gmail.com http://kc8qch.dx.am Hamshack Hotline: 4218 Webmaster Hamilton County ARPSC http://www.hamcoarpsc.org E-mail: hamcoarpsc@gmail.com Phone: 513-452-6480 Allstar 47374 Administrator Project Manager, HHUL World Wide Amateur Radio Guild http://www.theguildglobal.org E-Mail: kc8qch@theguildglobal.net
I had the same problem setting up my node. It turned out to be the port setting in the router. After I set it the node started working. Walt wb4lds From: Russell Thomas Sent: Wednesday, November 07, 2018 1:27 PM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] Connection issues with new ASL hub sorry the new node number is 49308. On Wed, Nov 7, 2018 at 2:26 PM Russell Thomas <russell@kv4s.com> wrote: I'm working on a Raspberry Pi hub and it appeared to install everything fine and I went through the ASL quick setup wizard. The node is reporting it's online and such but when I try connecting to it from another node it tells me the connection failed or timed out. It seems like I had a similar issue with our club node and it's possibly a dahdi problem but I don't know how to fix it? Any suggestions? 73, Russell Thomas, KV4S -------------------------------------------------------------------------------- _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
On 11/7/18 3:27 PM, Russell Thomas wrote:
sorry the new node number is 49308 <http://stats.allstarlink.org/nodeinfo.cgi?node=49308>.
Based on what I'm seeing: I see IAX respond on 4569 on 174.85.220.36 I see your node in the extnodes list 49308=radio@174.85.220.36:4569/49308,174.85.220.36 I am unable to connect to it. This implies you node is not downloading the extnodes file. check how new /var/lib/asterisk/rpt_extnodes is, and if it has anything in it. For two AllStar Nodes to connected, they must have reciprocal entries in their respective extnodes files. If one isn't updating, it's not going to allow the other to connect. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
I have a new ASL node on a Pi3. I can us iaxrpt to connect to other nodes, but it does not accept an external connection. Both the external and my new node are reporting external node list. I have not figured it out. It works when connected to another node. Oh, one more thing. The other node is on DIAL... not sure that should make a difference. Thanks, Bob K6ECM 73
On Nov 7, 2018, at 12:41 PM, Bryan Fields <Bryan@bryanfields.net> wrote:
On 11/7/18 3:27 PM, Russell Thomas wrote: sorry the new node number is 49308 <http://stats.allstarlink.org/nodeinfo.cgi?node=49308>.
Based on what I'm seeing:
I see IAX respond on 4569 on 174.85.220.36
I see your node in the extnodes list 49308=radio@174.85.220.36:4569/49308,174.85.220.36
I am unable to connect to it.
This implies you node is not downloading the extnodes file. check how new /var/lib/asterisk/rpt_extnodes is, and if it has anything in it.
For two AllStar Nodes to connected, they must have reciprocal entries in their respective extnodes files. If one isn't updating, it's not going to allow the other to connect.
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
On 11/7/18 3:52 PM, Bob Pyke wrote:
I have a new ASL node on a Pi3. I can us iaxrpt to connect to other nodes, but it does not accept an external connection. Both the external and my new node are reporting external node list. I have not figured it out. It works when connected to another node.
Ok, how is your node connected? Is there a NAT device in the way between your node and 174.85.220.36? You will need for forward UDP 4569 from 174.85.220.36 to what ever the NAT'd IP is if that's the case. But I really think the issue is your nodes list, I've checked and I do see 174.85.220.36 pulling the extnodes file every 3 or 4 minutes.
Oh, one more thing. The other node is on DIAL... not sure that should make a difference.
It shouldn't. There is little difference between the underlying protocols of AllStar, There are still Limey Linux based nodes on the network from 2004 working. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
Bryan, There are two folks with the same issue. I’m the second (node 27287) Thanks, Bob K6ECM 73
On Nov 7, 2018, at 1:09 PM, Bryan Fields <Bryan@bryanfields.net> wrote:
On 11/7/18 3:52 PM, Bob Pyke wrote: I have a new ASL node on a Pi3. I can us iaxrpt to connect to other nodes, but it does not accept an external connection. Both the external and my new node are reporting external node list. I have not figured it out. It works when connected to another node.
Ok, how is your node connected? Is there a NAT device in the way between your node and 174.85.220.36?
You will need for forward UDP 4569 from 174.85.220.36 to what ever the NAT'd IP is if that's the case.
But I really think the issue is your nodes list, I've checked and I do see 174.85.220.36 pulling the extnodes file every 3 or 4 minutes.
Oh, one more thing. The other node is on DIAL... not sure that should make a difference.
It shouldn't. There is little difference between the underlying protocols of AllStar, There are still Limey Linux based nodes on the network from 2004 working.
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
On 11/7/18 4:09 PM, Bryan Fields wrote:
Ok, how is your node connected? Is there a NAT device in the way between your node and 174.85.220.36?
eureka! NAT bs is present :( root@Itchy:~# grep 174.85.220.36 /var/lib/asterisk/rpt_extnodes 47923=radio@174.85.220.36:4569/47923,174.85.220.36 49308=radio@174.85.220.36:4569/49308,174.85.220.36 They a passing from different ports for IAX on the registration servers as well. You have two nodes behind the same IP, and they are identifying on the same port, so the NAT device at 174.85.220.36 won't be able to direct them to the proper internal address if they are not on different ports. What I would do is configure a nat rule to forward udp 174.85.220.36:4570 to <Internal-IP-49308>:4569 and configure the port for the server 49308 is on to 4570 in the portal. This way when people connect to 47923, it goes to 174.85.220.36:4569 and 49308 will go to 174.85.220.36:4570. If you want 47923 and 49308 you'll need to configure them in rpt.conf, since they will be behind your NAT device, and using direct connections. [nodes] 49308 = radio@<Internal-IP-49308>:4569/49308,NONE Give this a try and report back. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
Check out of document https://docs.google.com/document/d/1Dz0zD12RJKeFkmfuDM9fhQj88C84JeygfLygR8Vn... -- Thanks, David "Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one." Thomas Jefferson On Wed, Nov 7, 2018 at 1:24 PM Bryan Fields <Bryan@bryanfields.net> wrote:
On 11/7/18 4:09 PM, Bryan Fields wrote:
Ok, how is your node connected? Is there a NAT device in the way between your node and 174.85.220.36?
eureka! NAT bs is present :(
root@Itchy:~# grep 174.85.220.36 /var/lib/asterisk/rpt_extnodes 47923=radio@174.85.220.36:4569/47923,174.85.220.36 49308=radio@174.85.220.36:4569/49308,174.85.220.36
They a passing from different ports for IAX on the registration servers as well.
You have two nodes behind the same IP, and they are identifying on the same port, so the NAT device at 174.85.220.36 won't be able to direct them to the proper internal address if they are not on different ports.
What I would do is configure a nat rule to forward udp 174.85.220.36:4570 to <Internal-IP-49308>:4569 and configure the port for the server 49308 is on to 4570 in the portal.
This way when people connect to 47923, it goes to 174.85.220.36:4569 and 49308 will go to 174.85.220.36:4570.
If you want 47923 and 49308 you'll need to configure them in rpt.conf, since they will be behind your NAT device, and using direct connections.
[nodes] 49308 = radio@<Internal-IP-49308>:4569/49308,NONE
Give this a try and report back.
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Thanks all! I think NAT is the problem as well. I'll work on it next time I'm by the computer! Many thanks! On Wed, Nov 7, 2018, 5:17 PM David Shaw <shawpbx@gmail.com wrote:
Check out of document
https://docs.google.com/document/d/1Dz0zD12RJKeFkmfuDM9fhQj88C84JeygfLygR8Vn...
-- Thanks, David
"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one." Thomas Jefferson
On Wed, Nov 7, 2018 at 1:24 PM Bryan Fields <Bryan@bryanfields.net> wrote:
On 11/7/18 4:09 PM, Bryan Fields wrote:
Ok, how is your node connected? Is there a NAT device in the way between your node and 174.85.220.36?
eureka! NAT bs is present :(
root@Itchy:~# grep 174.85.220.36 /var/lib/asterisk/rpt_extnodes 47923=radio@174.85.220.36:4569/47923,174.85.220.36 49308=radio@174.85.220.36:4569/49308,174.85.220.36
They a passing from different ports for IAX on the registration servers as well.
You have two nodes behind the same IP, and they are identifying on the same port, so the NAT device at 174.85.220.36 won't be able to direct them to the proper internal address if they are not on different ports.
What I would do is configure a nat rule to forward udp 174.85.220.36:4570 to <Internal-IP-49308>:4569 and configure the port for the server 49308 is on to 4570 in the portal.
This way when people connect to 47923, it goes to 174.85.220.36:4569 and 49308 will go to 174.85.220.36:4570.
If you want 47923 and 49308 you'll need to configure them in rpt.conf, since they will be behind your NAT device, and using direct connections.
[nodes] 49308 = radio@<Internal-IP-49308>:4569/49308,NONE
Give this a try and report back.
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password 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@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
per the instructions, I did not create this node on a separate server on Allstar Link. can it be moved or have it deleted and start over? On Wed, Nov 7, 2018 at 6:45 PM Russell Thomas <russell@kv4s.com> wrote:
Thanks all! I think NAT is the problem as well. I'll work on it next time I'm by the computer!
Many thanks!
On Wed, Nov 7, 2018, 5:17 PM David Shaw <shawpbx@gmail.com wrote:
Check out of document
https://docs.google.com/document/d/1Dz0zD12RJKeFkmfuDM9fhQj88C84JeygfLygR8Vn...
-- Thanks, David
"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one." Thomas Jefferson
On Wed, Nov 7, 2018 at 1:24 PM Bryan Fields <Bryan@bryanfields.net> wrote:
On 11/7/18 4:09 PM, Bryan Fields wrote:
Ok, how is your node connected? Is there a NAT device in the way between your node and 174.85.220.36?
eureka! NAT bs is present :(
root@Itchy:~# grep 174.85.220.36 /var/lib/asterisk/rpt_extnodes 47923=radio@174.85.220.36:4569/47923,174.85.220.36 49308=radio@174.85.220.36:4569/49308,174.85.220.36
They a passing from different ports for IAX on the registration servers as well.
You have two nodes behind the same IP, and they are identifying on the same port, so the NAT device at 174.85.220.36 won't be able to direct them to the proper internal address if they are not on different ports.
What I would do is configure a nat rule to forward udp 174.85.220.36:4570 to <Internal-IP-49308>:4569 and configure the port for the server 49308 is on to 4570 in the portal.
This way when people connect to 47923, it goes to 174.85.220.36:4569 and 49308 will go to 174.85.220.36:4570.
If you want 47923 and 49308 you'll need to configure them in rpt.conf, since they will be behind your NAT device, and using direct connections.
[nodes] 49308 = radio@<Internal-IP-49308>:4569/49308,NONE
Give this a try and report back.
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password 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@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Yes Thanks, Bob K6ECM 73
On Nov 8, 2018, at 6:21 PM, Russell Thomas <russell@kv4s.com> wrote:
per the instructions, I did not create this node on a separate server on Allstar Link. can it be moved or have it deleted and start over?
On Wed, Nov 7, 2018 at 6:45 PM Russell Thomas <russell@kv4s.com> wrote: Thanks all! I think NAT is the problem as well. I'll work on it next time I'm by the computer!
Many thanks!
On Wed, Nov 7, 2018, 5:17 PM David Shaw <shawpbx@gmail.com wrote: Check out of document
https://docs.google.com/document/d/1Dz0zD12RJKeFkmfuDM9fhQj88C84JeygfLygR8Vn...
-- Thanks, David
"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one." Thomas Jefferson
On Wed, Nov 7, 2018 at 1:24 PM Bryan Fields <Bryan@bryanfields.net> wrote: On 11/7/18 4:09 PM, Bryan Fields wrote:
Ok, how is your node connected? Is there a NAT device in the way between your node and 174.85.220.36?
eureka! NAT bs is present :(
root@Itchy:~# grep 174.85.220.36 /var/lib/asterisk/rpt_extnodes 47923=radio@174.85.220.36:4569/47923,174.85.220.36 49308=radio@174.85.220.36:4569/49308,174.85.220.36
They a passing from different ports for IAX on the registration servers as well.
You have two nodes behind the same IP, and they are identifying on the same port, so the NAT device at 174.85.220.36 won't be able to direct them to the proper internal address if they are not on different ports.
What I would do is configure a nat rule to forward udp 174.85.220.36:4570 to <Internal-IP-49308>:4569 and configure the port for the server 49308 is on to 4570 in the portal.
This way when people connect to 47923, it goes to 174.85.220.36:4569 and 49308 will go to 174.85.220.36:4570.
If you want 47923 and 49308 you'll need to configure them in rpt.conf, since they will be behind your NAT device, and using direct connections.
[nodes] 49308 = radio@<Internal-IP-49308>:4569/49308,NONE
Give this a try and report back.
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password 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@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password 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@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Got it!! Thanks everyone!! On Thu, Nov 8, 2018 at 8:31 PM Bob Pyke <k6ecm1@gmail.com> wrote:
Yes
Thanks, Bob K6ECM 73
On Nov 8, 2018, at 6:21 PM, Russell Thomas <russell@kv4s.com> wrote:
per the instructions, I did not create this node on a separate server on Allstar Link. can it be moved or have it deleted and start over?
On Wed, Nov 7, 2018 at 6:45 PM Russell Thomas <russell@kv4s.com> wrote:
Thanks all! I think NAT is the problem as well. I'll work on it next time I'm by the computer!
Many thanks!
On Wed, Nov 7, 2018, 5:17 PM David Shaw <shawpbx@gmail.com wrote:
Check out of document
https://docs.google.com/document/d/1Dz0zD12RJKeFkmfuDM9fhQj88C84JeygfLygR8Vn...
-- Thanks, David
"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one." Thomas Jefferson
On Wed, Nov 7, 2018 at 1:24 PM Bryan Fields <Bryan@bryanfields.net> wrote:
On 11/7/18 4:09 PM, Bryan Fields wrote:
Ok, how is your node connected? Is there a NAT device in the way between your node and 174.85.220.36?
eureka! NAT bs is present :(
root@Itchy:~# grep 174.85.220.36 /var/lib/asterisk/rpt_extnodes 47923=radio@174.85.220.36:4569/47923,174.85.220.36 49308=radio@174.85.220.36:4569/49308,174.85.220.36
They a passing from different ports for IAX on the registration servers as well.
You have two nodes behind the same IP, and they are identifying on the same port, so the NAT device at 174.85.220.36 won't be able to direct them to the proper internal address if they are not on different ports.
What I would do is configure a nat rule to forward udp 174.85.220.36:4570 to <Internal-IP-49308>:4569 and configure the port for the server 49308 is on to 4570 in the portal.
This way when people connect to 47923, it goes to 174.85.220.36:4569 and 49308 will go to 174.85.220.36:4570.
If you want 47923 and 49308 you'll need to configure them in rpt.conf, since they will be behind your NAT device, and using direct connections.
[nodes] 49308 = radio@<Internal-IP-49308>:4569/49308,NONE
Give this a try and report back.
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password 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@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password 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@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password 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@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
participants (6)
-
Bob Pyke -
Bryan Fields -
David Shaw -
Jeff Lehman -
Russell Thomas -
walter