From owner-freebsd-current Tue Feb 2 22:49:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07743 for freebsd-current-outgoing; Tue, 2 Feb 1999 22:49:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from genius.cirx.org (r00t.m1.ntu.edu.tw [140.112.240.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07673 for ; Tue, 2 Feb 1999 22:49:03 -0800 (PST) (envelope-from clkao@CirX.ORG) Received: (from clkao@localhost) by genius.cirx.org (8.9.2/8.9.1) id OAA01948; Wed, 3 Feb 1999 14:47:45 +0800 (CST) (envelope-from clkao@CirX.ORG) Date: Wed, 3 Feb 1999 14:47:45 +0800 (CST) Message-Id: <199902030647.OAA01948@genius.cirx.org> X-Authentication-Warning: genius.cirx.org: clkao set sender to clkao@CirX.ORG using -f From: Chia-liang Kao To: wpaul@skynet.ctr.columbia.edu CC: current@FreeBSD.ORG In-reply-to: <199902030524.AAA06011@skynet.ctr.columbia.edu> (message from Bill Paul on Wed, 3 Feb 1999 00:24:27 -0500 (EST)) Subject: Re: problem with vr0 References: <199902030524.AAA06011@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Bill Paul * Date: Wed, 3 Feb 1999 00:24:27 -0500 (EST) * * > I did a `ping 192.168.100.1', and there is no response and no messages * > at all. I think the most interesting part of this is that I can see * > both of the lights on the hub blinking when I ping 192.168.100.1; * > while only the light of the other side blinks when he pings me. * * What kind of hub is this? It's a nonaccredited 5-port 10Bast-T hub which we used to connect outside world via another interface (my de0 and his ed0). And when we're trying to use this hub for internal connection only via both of our newly bought dfe530s, we're in trouble. * Are you using any unusual networking tricks, like network address * translation or firewalling or IP aliasing? People tend to forget to * mention things like that. There are some things I'm curious about: No, that's why I typed a `ipfw list' in the very first mail which indicates I have no firewall configuration in my kernel at all. * - What does netstat -in show? Are there any input errors? Are there * any input packets? (If the input packet counter keeps incrementing * then it has to be receiving something.) * There are some Ipkts but very few as you can see in the following. # netstat -in Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll de0 1500 00.80.c8.46.1e.d4 313987 34111 18717 185 2651 de0 1500 140.112.240/2 140.112.240.59 313987 34111 18717 185 2651 vr0 1500 00.80.c8.ef.82.09 16 0 15804 0 0 vr0 1500 192.168.100 192.168.100.2 16 0 15804 0 0 * - Do you see any suspicious messages when you do a dmesg to look at the * kernel message buffer? The vr driver should report receive errors if * it encounters any. Not at all, only `vr0: promiscuous mode enabled' when starting tcpdump. * - If you run tcpdump on the vr0 interface (tcpdump -n -e -i vr0) can * you see the traffic from the other host? Try the following: * * # arp -d 192.168.100.1 * # tcpdump -n -e -i vr0 & * # ping -c 5 192.168.100.1 * * Show us the output. PING 192.168.100.1 (192.168.100.1): 56 data bytes 14:32:35.481753 0:80:c8:ef:82:9 ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.1 tell 192.168.100.2 14:32:36.486348 0:80:c8:ef:82:9 ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.1 tell 192.168.100.2 14:32:36.486561 0:80:c8:ef:3c:3f 0:80:c8:ef:82:9 0806 60: arp reply 192.168.100.1 is-at 0:80:c8:ef:3c:3f 14:32:36.486625 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 > 192.168.100.1: icmp: echo request 14:32:37.496739 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 > 192.168.100.1: icmp: echo request 14:32:38.506383 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 > 192.168.100.1: icmp: echo request 14:32:39.516717 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 > 192.168.100.1: icmp: echo request --- 192.168.100.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss and here is the result of the same test done on 192.168.100.1 (with the target changed to 192.168.100.2): ping -c 5 192.168.100.2 PING 192.168.100.2 (192.168.100.2): 56 data bytes 14:36:01.999162 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:03.008614 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:04.018622 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:05.028656 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:06.038664 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.2 tell 192.168.100.1 14:36:14.106056 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0800 142: 192.168.100.1.1090> 192.168.100.255.111: udp 100 14:36:14.106075 0:80:c8:ef:3c:3f ff:ff:ff:ff:ff:ff 0800 142: 192.168.100.1.1090> 192.168.100.255.111: udp 100 --- 192.168.100.2 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message