From owner-freebsd-mobile@FreeBSD.ORG Sat Oct 11 11:42:23 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0ECBA16A4B3 for ; Sat, 11 Oct 2003 11:42:23 -0700 (PDT) Received: from www.kukulies.org (www.kukulies.org [213.146.112.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EFFF43FBF for ; Sat, 11 Oct 2003 11:42:21 -0700 (PDT) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (localhost [127.0.0.1]) by www.kukulies.org (8.12.10/8.12.6) with ESMTP id h9BIgJgv077389 for ; Sat, 11 Oct 2003 20:42:19 +0200 (CEST) (envelope-from kuku@www.kukulies.org) Received: (from kuku@localhost) by www.kukulies.org (8.12.10/8.12.6/Submit) id h9BIgIf6077388 for freebsd-mobile@freebsd.org; Sat, 11 Oct 2003 20:42:18 +0200 (CEST) Date: Sat, 11 Oct 2003 20:42:18 +0200 (CEST) From: "C. Kukulies" Message-Id: <200310111842.h9BIgIf6077388@www.kukulies.org> To: freebsd-mobile@freebsd.org Subject: wi0, cannot ping but wlan is up X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Oct 2003 18:42:23 -0000 ifconfig wi0 on my Dell 8000 (two days old cvsup) shows that the WLAN is up on the right SSID, adhoc mode, 2Mbit. But the interface didn|t get the address from dhclient. I stopped dhclient and set the address manually. Set default route manually. When I ping the peer point, my gateway machine, I get sendto: host is down. At the same time I see reachtion via tcpdump on the peer (gateway) side: # tcpdump: listening on wi0 20:25:01.474063 arp who-has 192.168.254.1 tell kukubook2k 20:25:01.474194 arp reply 192.168.254.1 is-at 0:2:2d:49:91:ce 20:25:02.480821 arp who-has 192.168.254.1 tell kukubook2k 20:25:02.480899 arp reply 192.168.254.1 is-at 0:2:2d:49:91:ce 20:25:03.490909 arp who-has 192.168.254.1 tell kukubook2k 20:25:03.490971 arp reply 192.168.254.1 is-at 0:2:2d:49:91:ce 20:25:04.500925 arp who-has 192.168.254.1 tell kukubook2k 20:25:04.500991 arp reply 192.168.254.1 is-at 0:2:2d:49:91:ce 20:25:05.511001 arp who-has 192.168.254.1 tell kukubook2k 20:25:05.511068 arp reply 192.168.254.1 is-at 0:2:2d:49:91:ce 20:27:12.614890 192.168.254.1 > kukubook2k: icmp: echo request 20:27:13.617743 192.168.254.1 > kukubook2k: icmp: echo request 20:27:14.627750 192.168.254.1 > kukubook2k: icmp: echo request 20:27:15.706424 192.168.254.1 > kukubook2k: icmp: echo request 20:27:16.707795 192.168.254.1 > kukubook2k: icmp: echo request 20:27:17.717808 192.168.254.1 > kukubook2k: icmp: echo request 20:27:18.727827 192.168.254.1 > kukubook2k: icmp: echo request 20:27:19.737851 192.168.254.1 > kukubook2k: icmp: echo request 20:32:01.697642 arp who-has 192.168.254.1 tell kukubook2k 20:32:01.697730 arp reply 192.168.254.1 is-at 0:2:2d:49:91:ce 20:32:02.706892 arp who-has 192.168.254.1 tell kukubook2k 20:32:02.706975 arp reply 192.168.254.1 is-at 0:2:2d:49:91:ce The arp requests are the consequence of the ping from my notbook to the peer, while the icmp: echo request is the ping from my notebook. Could it be a firewall issue? I have not changed anything and have firewall_enable=NO in rc.conf. Any ideas? -- Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de