From: Chuck B. <cb...@vi...> - 2002-04-11 14:28:26
|
On Tuesday 09 April 2002 10:17 pm, Dennis Hudson, N2LBT wrote: <<snip, snip>> : What ever happened to the information campaign that was started a few w= eeks : ago. I followed a few links this evening, and there is still quite a fe= w : aprsd users cross connecting using verified connections on 1313. Is the= new : jav code at third doing something different with 1313 connections? I se= e : most of the potential loop connects are all on first now. Is there a wa= y to : add force users to not connect, especially verified on port 1313 with : aprsd? : : Dennis, N2LBT I'll not beat the perverbial dead horse about the proper use of port 1313= ; but=20 in the past I spent considerable amount of time and energy contacting sys= =20 admins with misconfigured servers. I had left port 1313 open to public u= se=20 to help better track these users down. There are a few that just either=20 refuse or ignore my requests. Anyway, effective today port 1313 is close= d to=20 public access on first.aprs.net. Public ports on First: 23 -- full-feed without history 1314 -- message traffic 10151 -- full-feed with history (15min) 14501 -- server status (http) 14502 -- feed with IP source Chuck Byam, KG4IJB |