Re: bin/44671: syslogd sends udp dgrams from port 65534

[Takahiro Kambe <taca%back-street.net@localhost>]

The following reply was made to PR bin/44671; it has been noted by GNATS.

From: Takahiro Kambe <taca%back-street.net@localhost>
To: gabor%berczi.be@localhost
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: bin/44671: syslogd sends udp dgrams from port 65534
Date: Thu, 03 Mar 2011 18:39:48 +0900 (JST)

 In message <70C515E7-2D18-42E7-9B50-99A555E29C1B%berczi.be@localhost>
        on Thu, 3 Mar 2011 10:05:08 +0100,
        Berczi Gabor <gabor%berczi.be@localhost> wrote:
 >> Your expectation isn't correct.
 > 
 > Actually it is.
 Then, what is the basis?  You should show clearly.
 
 >> It is RECOMMENDED that the source port also be 514 to indicate that
 >> the message is from the syslog process of the sender
 > 
 > I have no idea (yet) who and why decided that port 65534 is so
 > sweet,
 It is simply free anonymous port range when syslogd(8) was invoked.
 In <netinet/in.h>, you could find:
 
 #define IPPORT_RESERVED         1024
 #define IPPORT_ANONMIN          49152
 #define IPPORT_ANONMAX          65535
 #define IPPORT_RESERVEDMIN      600
 #define IPPORT_RESERVEDMAX      (IPPORT_RESERVED-1)
 
 > but it sure does remind me of the case of Rui Paolo
 I don't read the thread and it isn't related here at all.  Anyway,
 
 > Additionally, NetBSD syslogd is only bugged with the -s option. Do
 > note that for example FreeBSD's syslogd -s works as expected.
 Various *BSD system has slightly diffrent command options, including
 syslogd(8).  Meaning of "-s" options of syslogd(8) isn't the same
 between FreeBSD and NetBSD has a little meaning.
 
 -- 
 Takahiro Kambe <taca%back-street.net@localhost>