Date: Tue, 17 Oct 95 19:51 WET DST From: aj@Ieunet.ie (Alan Judge) To: FreeBSD-gnats-submit@freebsd.org Cc: tech@Ieunet.ie Subject: kern/785: 2.0.5-950622-SNAP Various ifconfig alias problems Message-ID: <m0t5H6d-000IFbC@pop.Ieunet.ie> Resent-Message-ID: <199510171900.MAA03712@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 785 >Category: kern >Synopsis: Various ifconfig alias problems >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Oct 17 12:00:01 PDT 1995 >Last-Modified: >Originator: Alan Judge >Organization: Ieunet Ltd >Release: FreeBSD 2.0-BUILT-19950612 i386 >Environment: 2.0.5-950622-SNAP running busy web server. 10 virtual interfaces running using ifconfig alias. >Description: Several, possibly related problems: - ifconfig ed0 xxx.yyy.zzz.123 alias returns error: ifconfig: ioctl (SIOCAIFADDR): File exists If run a second time, there is no error and everything seems to be OK. - In order for the new address to be reachable from the host itself, you need to do ifconfig lo0 xxx.yyy.zzz.123 alias as well. I don't know if this is intentional, but it's certainly necessary. This usually results in a kernel error message like: arp_rtrequest: bad gateway value rtinit: wrong ifa (0xf06b2600) was (0xf0746d80) And again sometimes must be redone. - Some of this may be related to the fact that the presence of an arp entry for the host being aliased (even an incomplete one) seems to break everything. So I've been doing arp -d first. >How-To-Repeat: >Fix: Unknown. Current workaround is to do: $i=xxx.yyy.zzz.aaa arp -d $i > /dev/null 2>&1 ifconfig ed0 $i alias > /dev/null 2>&1 ifconfig ed0 $i alias ifconfig lo0 $i alias > /dev/null 2>&1 ifconfig lo0 $i alias >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0t5H6d-000IFbC>