Date: Tue, 2 Mar 2010 12:58:47 +0000 (UTC) From: Anton Yuzhaninov <citrin@citrin.ru> To: freebsd-net@freebsd.org Subject: Re: net/mpd5: proxy arp don't work on FreeBSD 8 Message-ID: <hmj227$pak$1@dough.gmane.org> References: <hmgmol$alh$1@dough.gmane.org> <hmirsc$3ul$1@dough.gmane.org> <083F4753-5883-4322-8324-BB6A540BAB69@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 >> options=3<RXCSUM,TXCSUM> >> 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<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> 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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> 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 <full-duplex>) 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<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?hmj227$pak$1>