Network-I Frequently Asked Questions
Something odd is happening and ...
Whatever the problem, the first step is always to check
to look for any likely-sounding error reports or warnings -
/tmp/GREY.LOG will only be used if $HOME/GREY.LOG couldn't be opened, for whatever reason.
Note that since the niftraff inetd service runs as the root user, its $HOME/GREY.log will resolve to root's home directory.
When I press Start on the nifwin GUI, it reports that it can't contact the specified interface.
The Network-I service referred to by nifwin is actually niftap running in a special mode, under the control of the inetd daemon, so use
'lsof -i :19681'
or 'netstat -an | fgrep 19681'
on the server machine to check if the niftraff port is active.
This problem normally means it's not listening, so if that is the case, you'll have to check your inetd or xinetd config, to make sure that 'niftap -R' is configured to run on that TCP port.
For Linux, the Network-I installation procedure assumes that service specs are stored under /etc/xinetd.d, and it should have created the file niftraff in there.
If for whatever reason, your Linux system is not set up like that, then configure your inetd accordingly, to achieve the required effect.
For Solaris, look at /etc/inetd.conf to verify that the installation successfully added the niftraff entry to it.
If so, sending SIGHUP to the inetd process (which Network-I does during the install) should be enough to activate it.
For Solaris 10 systems with SMF, Network-I should have run the inetconv utility at install time to create
and that should be enough.
Running 'svcs -a | fgrep niftraff' will show what state the service is in, and if it's in maintenance mode for whatever reason, running
'svcadm clear svc:/network/niftraff/tcp:default'
should fix it.