From owner-freebsd-net@FreeBSD.ORG Thu May 8 04:17:57 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ECFE5FCE for ; Thu, 8 May 2014 04:17:57 +0000 (UTC) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [67.212.89.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B38AC79F for ; Thu, 8 May 2014 04:17:57 +0000 (UTC) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) by mail.bsdinfo.com.br (Postfix) with ESMTP id E2F50139E5 for ; Thu, 8 May 2014 01:18:00 -0300 (BRT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bsdinfo.com.br; h=content-type:content-type:in-reply-to:references:subject :subject:to:mime-version:user-agent:from:from:date:date :message-id; s=dkim; t=1399522677; x=1400386678; bh=4iyQIAeHvYhT GiRs0kAL4BlRaCLKVIVJe8Gioq//snY=; b=jtg+1UjI5fm8HWUGO+4NNdzoAKYg Blm0h2KO6CzVUXedkYR45Lyhx3N+phb9Ga4HZyGawwbsWcKrpHsZJE4a0pEhQbml q5sIU0U7FxtFMp+JPyBNwpzrf9p1L1KNllCNRp2exCyGdQknDJHJbUyPHdNkPzor Y55niW70/OBdcQU= X-Virus-Scanned: amavisd-new at mail.bsdinfo.com.br Received: from mail.bsdinfo.com.br ([127.0.0.1]) by mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YOaaek7qb0T for ; Thu, 8 May 2014 01:17:57 -0300 (BRT) Received: from MacBook-de-Gondim-2.local (unknown [186.193.54.69]) by mail.bsdinfo.com.br (Postfix) with ESMTPSA id 2A2CF139C3; Thu, 8 May 2014 01:17:55 -0300 (BRT) Message-ID: <536B056B.1080009@bsdinfo.com.br> Date: Thu, 08 May 2014 01:17:47 -0300 From: Marcelo Gondim User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Alan Somers Subject: Re: Problem with removing mac address from arptable on 10-stable References: <536A5580.6020502@bsdinfo.com.br> <536A822A.7040404@bsdinfo.com.br> <536AC505.80107@bsdinfo.com.br> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2014 04:17:58 -0000 Em 07/05/14 23:05, Alan Somers escreveu: > On Wed, May 7, 2014 at 5:43 PM, Marcelo Gondim wrote: >> Em 07/05/14 15:57, Marcelo Gondim escreveu: >> >>> Em 07/05/14 15:18, Alan Somers escreveu: >>>> On Wed, May 7, 2014 at 9:47 AM, Marcelo Gondim >>>> wrote: >>>>> Hi all, >>>>> >>>>> I'm having this problemon my FreeBSD 10-STABLE: >>>>> >>>>> (root@rt01)[~]# arp -an|grep 187.xxx.216.252 >>>>> ? (187.xxx.216.252) at 5c:e0:f6:00:11:29 on vlan4 permanent [vlan] >>>>> >>>>> (root@rt01)[~]# arp -d 187.xxx.216.252 >>>>> delete: cannot locate 187.xxx.216.252 >>>>> >>>>> FreeBSD rt01.xxxxxx.com.br 10.0-STABLE FreeBSD 10.0-STABLE #8 r265409: >>>>> Tue >>>>> May 6 01:14:05 BRT 2014 >>>>> root@rt01.xxxxxx.com.br:/usr/obj/usr/src/sys/GONDIM >>>>> amd64 >>>>> >>>>> This is a real problem or am I missing something? >>>> Are you using multiple FIBs? There are been bugs relating to FIBs and >>>> the ARP table. If you're unsure, check "sysctl net.fibs" >>> Hi Alan, >>> >>> Thanks for your reply. >>> >>> # sysctl net.fibs >>> net.fibs: 2 >>> >>> I'll change it to 1 and see if the problem will happen. > net.fibs defaults to 1. Why was it set to 2? It must've been > deliberately set to 2 on your system, and changing it to 1 will > probably break something. I had defined in the kernel but never used. Right now is with value 1. > >>> Thanks! >> Hi Alan, >> >> did not work :( >> >> It also happens the errors below when I try to add a host in the arp table: >> >> # arp -an|grep 187.xxx >> ? (187.xxx.219.28) at 00:1e:67:77:de:62 on vlan4 permanent [vlan] >> >> # arp -s 187.xxx.223.254 5c:e0:f6:00:12:8e >> cannot intuit interface index and type for 187.xxx.223.254 >> # arp -s 187.xxx.216.253 5c:e0:f6:00:11:2c >> cannot intuit interface index and type for 187.xxx.216.253 >> # arp -s 187.xxx.223.253 5c:e0:f6:00:12:8b >> cannot intuit interface index and type for 187.xxx.223.253 >> # arp -s 187.xxx.216.254 5c:e0:f6:00:11:2f >> cannot intuit interface index and type for 187.xxx.216.254 >> >> # sysctl net.fibs >> net.fibs: 1 >> >> dmesg: >> >> arpresolve: can't allocate llinfo for 187.xxx.216.254 >> arpresolve: can't allocate llinfo for 187.xxx.216.254 >> arpresolve: can't allocate llinfo for 187.xxx.216.254 >> arpresolve: can't allocate llinfo for 187.xxx.216.254 >> arpresolve: can't allocate llinfo for 187.xxx.216.254 >> arpresolve: can't allocate llinfo for 187.xxx.216.254 >> arpresolve: can't allocate llinfo for 187.xxx.216.254 >> arpresolve: can't allocate llinfo for 187.xxx.216.254 > Please show me your network settings from /etc/rc.conf. It also might > be helpful to see the output of "netstat -rn" and "setfib 1 netstat > -rn". One guess as to your problem would be that your subnet mask is > configured wrong, or that other hosts on your vlan are configured with > a different subnet mask or even an entirely different network prefix. Thanks again for your help. :) Instead of using rc.conf I use the /etc/start_if.xxx. /etc/start_if.em0: /sbin/ifconfig disc0 create /sbin/ifconfig em0 159.XXX.51.98/30 /sbin/ifconfig em0 inet6 2804:XXXX:FFFF:FFD8::2/64 /sbin/ifconfig disc0 127.0.0.254 /etc/start_if.em1: /sbin/ifconfig em1 64.XXX.195.70/30 /sbin/ifconfig em1 inet6 2001:XXXX:2001:1001::96/126 /etc/start_if.em2: /sbin/ifconfig lagg1 create /sbin/ifconfig em2 up /sbin/ifconfig em5 up /sbin/ifconfig lagg1 laggproto lacp laggport em2 laggport em5 /sbin/ifconfig lagg1 up /sbin/ifconfig vlan0 create /sbin/ifconfig vlan1 create /sbin/ifconfig vlan2 create /sbin/ifconfig vlan3 create /sbin/ifconfig vlan0 186.XXX.48.1/27 vlan 3081 vlandev lagg1 /sbin/ifconfig vlan0 inet6 2804:XXXX:DEAD::1/64 /sbin/ifconfig vlan1 177.XXX.240.254/27 vlan 3082 vlandev lagg1 /sbin/ifconfig vlan1 inet6 2804:XXXX:CAFE::1/64 /sbin/ifconfig vlan2 186.XXX.54.1/27 vlan 2126 vlandev lagg1 /sbin/ifconfig vlan2 inet6 2804:XXXX:CADE::1/64 /sbin/ifconfig vlan3 186.XXX.61.1/27 vlan 3088 vlandev lagg1 /sbin/ifconfig vlan3 inet6 2804:XXXX:BAD::1/64 /etc/start_if.em3: /sbin/ifconfig em3 186.YYY.1.150/30 /etc/start_if.em6: /sbin/ifconfig em6 177.XXX.255.1/29 /etc/start_if.em7: /sbin/ifconfig em7 up /sbin/ifconfig vlan4 create /sbin/ifconfig vlan5 create /sbin/ifconfig vlan4 187.XXX.219.28/21 vlan 1441 vlandev em7 /sbin/ifconfig vlan5 inet6 2001:XXXX::219:28/64 vlan 1442 vlandev em7 There are over 487,000 routes on this server. The list would be too big to put here in this email. Is a BGP router. My /etc/rc.conf: hostname="rt01.xxxxxx.com.br" keymap="br275.iso.acc" ipv6_activate_all_interfaces="YES" sshd_enable="YES" syslogd_flags="-s -s" ntpdate_enable="YES" ntpdate_hosts="0.freebsd.pool.ntp.org" firewall_enable="YES" firewall_script="/etc/beastiefrw/beastiefrw" snmpd_enable="YES" snmpd_flags="-a" snmpd_conffile="/usr/local/share/snmp/snmpd.conf" fsck_y_enable="YES"