[OZAPRS] VK4TTT

[Damien Gardner Jnr]

If you know what you're doing, you don't need to 'hide' the online status of your boxes..  

And if you had to deal with tech support at various ISP's very much, you'd know that blocking ICMP is an absolute nightmare when the ISP's customers have issues connecting to you.. - first thing tech support at the remote ISP does is try to ping.  No ping? They go "sorry its the remote site, talk to them".  Doesn't matter if it's actually that they're trying to send an email that breaches the sending domain's SPF, or if their source IP is in a blacklist, if they can't ping your server, they decide it's your problem and don't look any further..

Easier not to break the RFC's..

--DG


On 05/01/2011, at 1:12 PM, Ian Bennett wrote:

> Keeps out tyre kickers too.
> If a host doesn't respond to pings, "they" assume it is not there and so look
> elsewhere.
> Provided you know your network (and know what you are doing), you don't need
> ping for fault finding.
> 
> On Wed, Jan 5th, 2011 at 11:21 AM, Kim Hawtin <kim at hawtin.net.au> wrote:
> 
>> Andrew Rich wrote:
>>> DG I thought you were more of a geek than that
>>> 
>>> http://vk4ttt.aprs.id.au:14501/    APRS SERVER STATUS
>>> 
>>> telnet vk4ttt.aprs.id.au 14580 User defined port
>>> telnet vk4ttt.aprs.id.au 10152 full stream (just heart beats at the
>> moment)
>> 
>> not responding to ICMP makes debugging and testing a joy.
>> 
>> Kim VK5FNET
>> _______________________________________________
>> OZAPRS mailing list
>> OZAPRS at aprs.net.au
>> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>> 
>> 
>> 
> 
> 
> 
> _______________________________________________
> OZAPRS mailing list
> OZAPRS at aprs.net.au
> http://lists.aprs.net.au/mailman/listinfo/ozaprs