[aprssig] Recommended IGate Connection

[Eric Goforth]

Hi Joel;

If all you want to do is message traffic, i would connect to the Message only port of the server.  If you are also wanting to do position reports then you have to consider how much traffic your network connection (or how much you willing to give up) can handle.  Port 23 is the entire network, world-wide.  That's a lot.  If you think your users would apprecieate getting msg traffic from Africa (for example), then you kind of have to do that.  However, I have my iGate only connecting to North America traffic only and it serves my community very well.

Just my opinion and I'm sure your going to get a lot of them here..  ;-)

73's
Eric J. Goforth, N6GOF



-----Original Message-----
From: aprssig-bounces at lists.tapr.org on behalf of Joel Maslak
Sent: Sun 9/10/2006 9:08 PM
To: TAPR APRS Mailing List
Subject: [aprssig] Recommended IGate Connection
 
I'm running an IGate for a relatively small geographic area (transmit  
path of WIDE2-1, considering shortening even more to one specific  
named WIDE).

Right now, I use aprsd (2.2.5 I think).  I'm using the following to  
connect to the internet stream in the aprsd.conf:

Server rotate.aprs.net 23 hub-sr

I'm not sure I'm using the prefered port (or other options for that  
matter).

What's the current recommendations for systems like mine?  I want to  
support message traffic to my local RF users, but less bandwidth for  
the upstream server would be a good thing if it doesn't impact my  
local users.


_______________________________________________
aprssig mailing list
aprssig at lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 3343 bytes
Desc: not available
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20060910/11da0950/attachment.dat>