[1485] in linux-net channel archive
SETARP and also utmp
daemon@ATHENA.MIT.EDU (Jason Duerstock)
Tue Dec 5 01:56:46 1995
Date: Mon, 4 Dec 1995 13:28:53 -0500
From: Jason Duerstock <jduersto@kendall.mdcc.edu>
To: linux-kernel@vger.rutgers.edu
cc: linux-net@vger.rutgers.edu
I'm trying to set up bootpd on a machine running 1.2.13 with a HP PC LAN+
card and I get the following message when the machine receives a bootp
request.
Nov 13 16:18:35 mars bootpd[13968]: version 2.4.3
Nov 13 16:19:08 mars kernel: ARP: SETARP: requested PA is 0.0.0.0 !
Nov 13 16:19:25 mars last message repeated 5 times
I get this message when requesting from a Macintosh and also from a PC
running Novell's LAN Workplace for DOS TCPIP.EXE.
Any idea how to go about making this work?
I've also discovered a bug somewhere regarding the utmp file.
According to my /usr/include/utmp.h:
struct utmp {
short ut_type; /* type of login */
pid_t ut_pid; /* pid of login-process */
char ut_line[UT_LINESIZE]; /* devicename of tty - null-term */
char ut_id[2]; /* abbrev. ttyname, as 01, s1 etc. */
time_t ut_time; /* logintime */
char ut_user[UT_NAMESIZE]; /* username, not null-term */
char ut_host[UT_HOSTSIZE]; /* hostname for remote login... */
long ut_addr; /* IP addr of remote host */
};
However, because ut_id is defined as only two characters, utmp breaks
when someone dials in on my Bocaboard because the devices are /dev/ttyS16,
/dev/ttyS17, /dev/ttyS18, etc.
What is the best way to remedy this? Do we want to change /dev/ttyS?? to
/dev/ttySa, /dev/ttySb, etc., or do we need to modify libc to support a 3
character ut_id so that the getutent() function works? Or is there a
third solution I haven't come up with?
Jason Duerstock
jduersto@kendall.mdcc.edu
