R P Herrold

perhaps this is an RFE then ... The host in question which is the NCiDD server has lots of interfaces. In looking, it appears that you are listening on ALL interfaces [root@router ~]# netstat -pant | grep "3333" tcp 0 0 0.0.0.0:3333 0.0.0.0:* LISTEN 1824/ncidd [root@router ~]# ip a | grep "inet " inet 127.0.0.1/8 scope host lo inet 99.26.230.105/29 brd 99.26.230.111 scope global noprefixroute dynamic enp0s25 inet 10.16.0.1/21 brd 10.16.7.255 scope global br1 inet 192.168.150.1 peer 192.168.150.2/32...

On Wed, 13 Nov 2019, Ed Attfield wrote: Optionally binding to a particular interface would be easy to add -- the hardest part is in updating the documentation :) I'll try it ... I'll take a swing at it too I cloned the HG repository ... I do not see a makefile target to roll a tarball. May I buy a hint? thanks -- Russ herrold

perhaps this is an RFE then ... The host in question which is the NCiDD server has lots of interfaces. In looking, it appears that you are listening on ALL interfaces [root@router ~]# netstat -pant | grep "3333" tcp 0 0 0.0.0.0:3333 0.0.0.0:* LISTEN 1824/ncidd [root@router ~]# ip a | grep "inet " inet 127.0.0.1/8 scope host lo inet 99.26.230.105/29 brd 99.26.230.111 scope global noprefixroute dynamic enp0s25 inet 10.16.0.1/21 brd 10.16.7.255 scope global br1 inet 192.168.150.1 peer 192.168.150.2/32...

NCIDD -V does not report the corect listening IP. net of the HOST ssetting

So theminimal fix xeems to be to strlen each entry in the alises file, and when not commented, and not over-long, to accept it. When overlong, to emit a WARN and discard it

I commented out the offending line, and ... it starts 9 alias NAME * = "cold call amacon alexa network" if "16144260646" # Fri Oct alias NAME * = "forged CID Name - B of A -- HU after I proceed in call" if "148 alias NAME * = "spam health call" if "15052970343" # Wed Oct 30 16:29:06 201 No modified files, so no updates needed. [root@router ncid]# ncidd -D Started: 11/13/2019 10:09:27 Server: ncidd (NCID) 1.10.1 API: 1.8 Feature Set 1 2 3 4 5 Sysname: Linux Nodename: router.owlriver.net Machine: x86_64...

Found it -- it was an over-long entry in the Aliasses file, which the progrem had accepted a few days ago: ] [root@router ncid]# ncidd -D Started: 11/13/2019 10:08:48 Server: ncidd (NCID) 1.10.1 API: 1.8 Feature Set 1 2 3 4 5 Sysname: Linux Nodename: router.owlriver.net Machine: x86_64 Release: 3.10.0-1062.4.1.el7.x86_64 Version: #1 SMP Fri Oct 18 17:15:30 UTC 2019 Command line: ncidd -D Logfile: /var/log/ncidd.log Processed config file: /etc/ncid/ncidd.conf Verbose level: 1 cidinput = 0 Configured...

[root@router ~]# ncidd -V ncidd [router.owlriver.net:3333] (NCID) 1.10.1 API: 1.8 Feature Set 1 2 3 4 5 [root@router ~]#