|
There are several reason why you may have problems with your connection to T2FRANCE. As a first step you should verify that the server is on line by looking at the status page: http://france.aprs2.net:14501. The status of all Tier 2 servers is shown on the T2 HomePage.
If you can't connect to any of the APRS-IS servers, you may have a problem with a firewall. In this case start your telnet client and connect to "rotate.aprs2.net" (w/o quotes), port 14580. If you don't see the keep-alive packet of a server, your APRS client will not be able to connect to any APRS-IS server. You have to fix the firewall problem first.
- Connection Instabilities
The most frequent reason for connection instabilities is the fact that you receive more data from the server than you can process in due time. If the server sees that you can't keep pace with the stream rate, it disconnects you.
Try to connect to port 14580 and use a filter to limit the data rate you receive from the server (see below).
A second frequent reason is the connection via WiFi or other wire-less links. Many have the unpleasant behaviour to 'fall asleep' or simply disappear without terminating the TCP/IP connection. My router log is full with residues of these loose ends. If you can use a wire connection to the APRS-IS, please do so.
- Full Feed Connections (Port 10152)
Not available on this server. It is generally not supported by the T2 servers. Connect to port 14580 and define your filter (See below). If available, full-feed connections would not accept any filter and always send the full bandwidth.
- Connections on Port 14580
This port allows you to customize your feed, i.e. define the filter for the data you receive from the server. If you do not define a filter, the server can't know what you want to receive and will consequently not send any data but the keep-alive packet for the connection. It will, however, read and process the data you send upstream.
A custom filter allows you to get whatever data you want from the APRS-IS. The filter guide is here.
If your server list in UI-View is not up-to-date, read here how to download the actual version, or here how to modify the loaded server list.
- Log on Required
T2FRANCE requires log on, i.e. you have to put a callsign or an ID in your program and at least -1 in the field for the validation number, if you do not have a validation number for your callsign.
If you do not enter a validation number your connection will not be verified and shown as such on the status page. In this case several restriction for the use of the APRS-IS apply. You can, for example, not send any messages via the Internet if your callsign is not validated, i.e. you are not recognized as a HAM. Look here for details.
If you are a licensed radio amateur and do not yet have a validation number, please drop me a line.
- Using AFilter
If you use AFilter you may have problems to log on to the server. Read this.
- Badly configured clients
Badly configured clients may generate useless looped packets and duplicates. This is typically the case of poorly configured aprsD servers which maintain multiple connects to more than one APRS-IS server. This approach is a useless waste of APRS-IS resources because it wasts bandwidth, causes loops and duplicates in the system. Even in case of '-RO' connections they seem to send ID packet to everyone and cause loops.
Nobody needs more than one upstream connection at the same time. All the CORE - Tier 2 server network works reliably without this. Be unique !.
- Blocked IPs
I hold a list of excluded IPs in my firewall. Most of these IPs had in the past tried to send me NIMDA attacks or other unfriendly stuff. If you happen to have a dynamic IP and feel to be excluded with no reason, please send me a mail.
If you encounter a problem, do not hesitate to send me a mail.
|