Menu ▾ ▴

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

v1.0_(example)
closed
None
1
2020-04-29
2019-11-13
R P Herrold
No

see: SUBJECT ... it should

[root@router ncid]# ncidd -V
ncidd [router.owlriver.net:3333] (NCID) 1.10.1
API: 1.8 Feature Set 1 2 3 4 5
[root@router ncid]# grep -v "^#" ncid.conf | grep -v "^$"
set Host 10.16.0.1
set Port 3333
set PIDfile ""
set ModDir "/usr/share/ncid/modules"
set ModName ""
set PopupTime 5
set Delay 15
set HostnameFlag 0
set DialPrefix ""
set Verbose 0
set NoGUI 0
set WrapLines "word"
set Country "US"
set NoOne 0
set nameWidth 30
set NoExit 0
set WakeUp 1
set AltDate 0
set DateSepar "/"
set TivoFlag 0
[root@router ncid]#

Discussion

  • Ed Attfield

    Ed Attfield - 2019-11-13

    I'm somewhat confused by the question.

    ncidd -V uses gethostname() to obtain the hostname for the system you're running it on.

    ncid.conf is the config file for the ncid client, and can specify an ncidd server on a different Host.

     
  • R P Herrold

    R P Herrold - 2019-11-13

    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 scope global tun0
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0

    I had set up firewalld rules to block inquiries from 'outside', but a 'belt and suspenders' approach of limiting listening to only enumerated HOSTS in the config file [or a new ncidd.conf file]

    [root@secure ~]# nmap -p 3333 99.26.230.105
    Interesting ports on 99.26.230.105:
    PORT STATE SERVICE
    3333/tcp filtered dec-notes

     

    Last edit: R P Herrold 2020-04-28
  • Ed Attfield

    Ed Attfield - 2019-11-13

    Optionally binding to a particular interface would be easy to add -- the hardest part is in updating the documentation :)
    I'll try it ...

     
    • R P Herrold

      R P Herrold - 2019-11-13

      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

       
  • Ed Attfield

    Ed Attfield - 2019-11-15

    I've added it as a set ifaddr option coming in ncidd 1.11.

     
  • John L. Chmielewski

    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,4 +1,3 @@
    -
     see: SUBJECT ... it should
    
     [root@router ncid]# ncidd  -V
    
    • assigned_to: Ed Attfield
     
  • Ed Attfield

    Ed Attfield - 2020-04-29
    • status: open --> closed
     
  • Ed Attfield

    Ed Attfield - 2020-04-29

    As noted int the prototype ncidd.conf file for 1.11

    # The default TCP/IP port accepts client connections from everywhere
    # restrict it to the local host:
    # set ifaddr = 127.0.0.1
    # restrict it to a single interface card:
    # set ifaddr = 192.168.0.15
    
     

Anonymous
Anonymous

Add attachments
Cancel