Date: Wed, 16 Jun 1999 20:36:19 -0400 (EDT) From: Thomas David Rivers <rivers@dignus.com> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/12251: slattach followed by ifconfig sl0 doesn't work. Message-ID: <199906170036.UAA08247@lakes.dignus.com>
next in thread | raw e-mail | index | archive | help
>Number: 12251 >Category: kern >Synopsis: slattach followed by ifconfig sl0 doesn't work. >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jun 16 17:40:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Thomas David Rivers >Release: FreeBSD 3.1-RELEASE i386 >Organization: Dignus, LLC >Environment: FreeBSD 3.1-R and FreeBSD 3.2-R (maybe others) >Description: If you do an slattach followed by an ifconfig - the ifconfig will report ifconfig: ioctl(SIOCAIFADDR): File exists because it attempts to add the same route to the routing table twice. The reason for this is that in_ifinit() (in /sys/netinet/in.c) calls the interface-specific ioctl routine to give it a "chance" to do things. In the SL/IP case, if the slip unit sc_ttyp field is set (which it will be because slattach has associated the tty) - then if_up() will be called, which eventually adds the route to the route table. Later in in_ifinit(), rtinit() gets called again to add the exact same route. The second call to rtinit() results in an EEXISTS return code because the route is already there. >How-To-Repeat: slattach -c -s 9600 /dev/cuaa0 ifconfig sl0 n.n.n.n m.m.m.m >Fix: Don't do slattach first - if the device isn't opened, this problem doesn't exist. [Unfortunately, sysintall does do the slattach first, which means SL/IP installs no longer work.] >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906170036.UAA08247>