Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 19 Mar 2006 08:03:32 -0500
From:      Chuck Swiger <cswiger@mac.com>
To:        Harlan Stenn <harlan@everett.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: arp_rtrequest: bad gateway (!AF_LINK)
Message-ID:  <441D56A4.3050400@mac.com>
In-Reply-To: <20060319122649.CBFEC54827@minnie.everett.org>
References:  <20060319122649.CBFEC54827@minnie.everett.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Harlan Stenn wrote:
> Here's an example of some stuff in /etc/rc.conf:
> 
>  ifconfig_fxp0="inet 66.220.13.226/28 media 100baseTX mediaopt full-duplex"
>  ifconfig_fxp0_alias0="inet 192.168.64.10/32"
>  ifconfig_fxp0_alias1="inet 66.220.13.227/32"
>  ifconfig_fxp0_alias2="inet 66.220.13.230/32"
>  ifconfig_fxp1="inet 192.168.64.11/32"
>  ifconfig_lo0_alias0="inet 192.168.64.9/32"
>  ifconfig_lo0_alias1="inet 192.168.65.3/32"
>  ifconfig_lo0_alias2="inet 192.168.65.5/32"
> 
> The problem is that I'm seeing the following lines repeated in my syslog:
> 
>  arp_rtrequest: bad gateway 192.168.64.10 (!AF_LINK)
>  arp_rtrequest: bad gateway 66.220.13.227 (!AF_LINK)

I infer you are trying to set up other machines (or a local jail?) on something
like 192.168.64.8 or .4 which are trying to ARP for their router.  It doesn't
make sense to do ARP over the loopback, and anyway, a real NIC and the loopback
use different framing types.  What happens if you change:

>  ifconfig_lo0_alias0="inet 192.168.64.9/32"

...and so forth to:

>  ifconfig_fxp1_alias0="inet 192.168.64.9/32"

...?

Oh, yes, and this does not make sense, either:

>  ifconfig_fxp0_alias0="inet 192.168.64.10/32"

...and people put their internal 192.168 subnet as a /24:

>  ifconfig_fxp1="inet 192.168.64.11/32"

Most unusual.  People normally only need to use IP aliases when your renumber an
existing system and some other machine which can't be changed easily still needs
to talk to that host using the old IP, or if you need to host multiple instances
of something like an SSL-based webserver which demand a separate IP for each
site due to the protocol limitations.

If you have two NICs, they should be on separate subnets, in separate collision
domains, unless you are doing channel bonding/CARP/FEC, in which case they must
be specially configured for that purpose (and therefore would be on the same
subnet only).

-- 
-Chuck



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?441D56A4.3050400>