From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 05:44:45 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B82A21065676; Sun, 4 Jan 2009 05:44:45 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 9A9158FC0C; Sun, 4 Jan 2009 05:44:45 +0000 (UTC) (envelope-from randy@psg.com) Received: from 50.216.138.210.bn.2iij.net ([210.138.216.50] helo=rmac.psg.com) by ran.psg.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LJLn1-000NaT-Fs; Sun, 04 Jan 2009 05:44:44 +0000 Message-ID: <49604CCA.7050301@psg.com> Date: Sun, 04 Jan 2009 14:44:42 +0900 From: Randy Bush User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20081204 Thunderbird/3.0b1 MIME-Version: 1.0 To: Sam Leffler References: <495F0B2D.7060701@psg.com> <49604720.4070703@freebsd.org> In-Reply-To: <49604720.4070703@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: hosts on bridged wlan can not reliably see each other X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2009 05:44:46 -0000 On 09.01.04 14:20, Sam Leffler wrote: > Randy Bush wrote: >> soekris 5501 of nov 28, pre new arp >> >> problem description >> o all hosts on the wireless can get outside, no problem >> o they can also get to wired devices on vr[1-3] >> o they can reliably not see/ping/... each other on the wireless >> o the soekris can ping them all >> o higher layers are worse >> o the messages on this list worry me about upgrading this week, >> as this is my home gate to the world and somewhat complex >> (bridge, tunnel, pppoe, ...), whereas the mass of servers are >> all pretty straightforward. >> >> .----------------. >> | | >> | b ---ath0| 192.168.0.0/24 >> | r | >> ext iij | i --- vr1| LAN hosts, >> PPP/NAT ---|vr0--- d | >> WAN | g --- vr2| DHCP Clients >> | e | >> | 0 --- vr3| pptp 200-209 >> | | >> `----------------' >> >> ath0: mem 0xa0010000-0xa001ffff irq 15 at device 17.0 on >> pci0 >> ath0: [ITHREAD] >> ath0: WARNING: using obsoleted if_watchdog interface >> ath0: mac 5.9 phy 4.3 radio 3.6 >> >> # uname -a >> FreeBSD soek0.psg.com 8.0-CURRENT FreeBSD 8.0-CURRENT #2: Fri Nov 28 >> 19:16:10 UTC 2008 root@soek0.psg.com:/usr/obj/usr/src/sys/SOEK0 i386 >> >> wlans_ath0="wlan0 wlan1" >> create_args_wlan0="wlanmode hostap channel 11 ssid rgnet-aden wep wepkey >> arbitrarykeys weptxkey 1 media autoselect mode 11g up" >> cloned_interfaces=bridge0 >> ifconfig_bridge0="192.168.0.1 addm vr1 addm vr2 addm vr3 addm wlan0 addm >> wlan1 up" >> ifconfig_vr1=up >> ifconfig_vr2=up >> ifconfig_vr3=up >> gateway_enable=YES >> >> the soekris can see them all >> >> # arp -an >> ? (192.168.0.10) at 00:15:c5:4a:6f:c5 on bridge0 [bridge] >> ? (192.168.0.12) at 00:1e:52:70:b6:36 on bridge0 [bridge] >> ? (192.168.0.13) at 00:15:00:10:ed:09 on bridge0 [bridge] >> ? (192.168.0.17) at 00:0d:65:27:bd:f2 on bridge0 [bridge] >> ? (192.168.0.128) at 00:23:12:fc:39:b9 on bridge0 [bridge] >> ? (192.168.0.129) at 00:23:df:6a:dc:9b on bridge0 [bridge] >> >> and gets log entries of >> >> Jan 2 00:01:09 soek kernel: rtfree: 0xc2e803c0 has 1 refs >> Jan 2 00:01:16 soek kernel: rtfree: 0xc2e80078 has 1 refs >> Jan 2 00:01:16 soek kernel: rtfree: 0xc2e80078 has 1 refs >> Jan 2 00:01:16 soek kernel: arp_proxy: ignoring request from >> 192.168.0.10 via vr2, expecting bridge0 >> >> what more should i do to debug? > > Use tcpdump to track where the packets are visible. If this is a > wireless issue you will have stats to identify drops as well as the > usual debug facilities. sorry, this is why i was arp conscious soekris# ping 192.168.0.129 PING 192.168.0.129 (192.168.0.129): 56 data bytes 64 bytes from 192.168.0.129: icmp_seq=0 ttl=64 time=113.103 ms 64 bytes from 192.168.0.129: icmp_seq=1 ttl=64 time=349.680 ms 64 bytes from 192.168.0.129: icmp_seq=2 ttl=64 time=366.531 ms ^C --- 192.168.0.129 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 113.103/276.438/366.531/115.700 ms then, when pinging (unsuccessfully) from another host on the wireless soekris# tcpdump -i bridge0 host 192.168.0.129 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bridge0, link-type EN10MB (Ethernet), capture size 96 bytes 05:40:28.486793 arp who-has 192.168.0.129 tell 192.168.0.12 05:40:29.486335 arp who-has 192.168.0.129 tell 192.168.0.12 05:40:30.486776 arp who-has 192.168.0.129 tell 192.168.0.12 05:40:31.487058 arp who-has 192.168.0.129 tell 192.168.0.12 05:40:32.487227 arp who-has 192.168.0.129 tell 192.168.0.12 ^C 5 packets captured 2192 packets received by filter 0 packets dropped by kernel ath ierrors are an old fact of life here, see a thread from almost a year ago soekris# netstat -ni Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll vr0 1500 00:00:24:c8:b3:28 139171779 0 102370058 0 0 vr1 1500 00:00:24:c8:b3:29 0 0 0 0 0 vr2 1500 00:00:24:c8:b3:2a 11034998 0 54497266 0 0 vr3 1500 00:00:24:c8:b3:2b 246912 0 321750 0 0 ath0 2290 00:0b:6b:83:59:25 192042747 20665363 77278643 27 0 lo0 16384 111523 0 111523 0 0 lo0 16384 fe80:6::1/64 fe80:6::1 0 - 0 - - lo0 16384 ::1/128 ::1 0 - 0 - - lo0 16384 127.0.0.0/8 127.0.0.1 111523 - 111523 - - bridg 1500 d6:9b:35:b7:7c:bd 92627892 0 131886570 0 0 bridg 1500 192.168.0.0/2 192.168.0.1 231764 - 146544 - - wlan0 1500 00:0b:6b:83:59:25 81345984 0 77084603 192714 0 wlan1 1500 00:0b:6b:83:59:25 0 0 0 0 0 tun0 1454 138915852 0 102337216 0 0 tun0 1454 210.138.216.5 210.138.216.50 7709196 - 10317194 - - randy