From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 12:59:04 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF8F8106566B for ; Tue, 2 Mar 2010 12:59:04 +0000 (UTC) (envelope-from freebsd-net@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 3D48A8FC13 for ; Tue, 2 Mar 2010 12:59:04 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1NmRgk-0001rU-Jz for freebsd-net@freebsd.org; Tue, 02 Mar 2010 13:59:02 +0100 Received: from gw2.masterhost.ru ([87.242.97.5]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Mar 2010 13:59:02 +0100 Received: from citrin by gw2.masterhost.ru with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Mar 2010 13:59:02 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-net@freebsd.org From: Anton Yuzhaninov Date: Tue, 2 Mar 2010 12:58:47 +0000 (UTC) Organization: Vega Lines: 52 Sender: Message-ID: References: <083F4753-5883-4322-8324-BB6A540BAB69@gmail.com> X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: gw2.masterhost.ru X-Comment-To: Luiz Otavio O Souza User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (Linux/2.6.31-gentoo-r6 (i686)) Subject: Re: net/mpd5: proxy arp don't work on FreeBSD 8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2010 12:59:04 -0000 On Tue, 2 Mar 2010 09:44:04 -0300, Luiz Otavio O Souza wrote: >> This problem can be repeated without mpd: >> >> # ifconfig vlan408 >> vlan408: flags=8844 metric 0 mtu 1500 >> options=3 >> ether 00:04:23:ba:2a:7a >> inet 10.25.1.244 netmask 0xffffff00 broadcast 10.25.1.255 >> ... >> # kldload ng_iface >> # ngctl mkpeer . iface foobar inet >> # ifconfig ng0 192.168.100.100/32 10.25.1.245 >> # ifconfig ng0 >> ng0: flags=88d1 metric 0 mtu 1500 >> inet 192.168.100.100 --> 10.25.1.245 netmask 0xffffffff >> # arp -s 10.25.1.245 00:04:23:ba:2a:7a pub >> cannot intuit interface index and type for 10.25.1.245 LOOS> LOOS> But what about the 192.168.100.100 ? You are using IPs from this network somewhere else ? 1. No. Why it should be used somewhere else? 2. It works in RELENG7 Other example: vlan408: 10.25.1.244/24 ng0: 10.25.1.245/32 -> 10.25.1.246 same error: cannot intuit interface index and type for 10.25.1.246 LOOS> vlan100: flags=8843 metric 0 mtu 1500 LOOS> ether 00:08:54:0e:55:77 LOOS> inet 192.168.10.1 netmask 0xffffff00 broadcast 192.168.10.255 LOOS> media: Ethernet autoselect (100baseTX ) LOOS> status: active ... LOOS> Then i just replace the bogus IP to some other valid IP (using the IP from vlan100): LOOS> LOOS> # ifconfig ng0 192.168.10.1/32 192.168.10.2 LOOS> # ifconfig ng0 LOOS> ng0: flags=88d1 metric 0 mtu 1500 LOOS> inet 192.168.10.1 --> 192.168.10.2 netmask 0xffffffff LOOS> # arp -S 192.168.10.2 1:2:3:4:5:6 pub; echo $? LOOS> arp: writing to routing socket: Invalid argument LOOS> 0 LOOS> # arp -an | grep 192.168.10.2 LOOS> ? (192.168.10.2) at 01:02:03:04:05:06 on vlan100 permanent published [vlan] Why same ip - 192.168.10.1 should be configuren on two different interfaces: vlan100 and ng0. It looks like ugly hack. -- WBR, Anton Yuzhaninov