Subject: bin/4383: ipnat error messages could be clearer
To: None <>
From: Martin Husemann <>
List: netbsd-bugs
Date: 10/29/1997 11:08:31
>Number:         4383
>Category:       bin
>Synopsis:       ipnat fails to mention file name on file open errors
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 29 02:35:02 1997
>Originator:     Martin Husemann
UP-Vision Computergraphik GmbH, Bad Arolsen
>Release:        Oct 27
System: NetBSD 1.3_ALPHA NetBSD 1.3_ALPHA (RUMOLT) #0: Tue Oct 28 20:12:27 MET 1997 i386


When failing to open /dev/ipnat (or friends) ipnat (and ipfstats) don't
give usefull error messages.


On a machine running ipnat for a while with a realy old version of -current
and no /dev/ipnat yet (or temporarily remove /dev/ipnat from a test machine), 
try this:

[/etc] root@rumolt > ls -l ipnat.conf 
-rw-r--r--  1 root  wheel  94 Apr 27  1997 ipnat.conf
[/etc] root@rumolt > ipnat -f ipnat.conf 
open: No such file or directory

Always display filename with errormessage, this should be clue enough.
Maybe even give a hint to /dev/MAKEDEV or a man page describing the
nat setup.