From owner-freebsd-net@FreeBSD.ORG Mon Feb 13 14:48:01 2006
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: freebsd-net@freebsd.org
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 9339916A420
for <freebsd-net@freebsd.org>; Mon, 13 Feb 2006 14:48:01 +0000 (GMT)
(envelope-from mt@smtp.top.net.ua)
Received: from smtp.top.net.ua (smtp.top.net.ua [88.81.254.198])
by mx1.FreeBSD.org (Postfix) with ESMTP id D4D3843D5A
for <freebsd-net@freebsd.org>; Mon, 13 Feb 2006 14:48:00 +0000 (GMT)
(envelope-from mt@smtp.top.net.ua)
Received: from smtp.top.net.ua (localhost [127.0.0.1])
by smtp.top.net.ua (Postfix) with ESMTP id DFA2C608B55
for <freebsd-net@freebsd.org>; Mon, 13 Feb 2006 16:38:15 +0200 (EET)
Received: by smtp.top.net.ua (Postfix, from userid 1012)
id 8CC44608B6B; Mon, 13 Feb 2006 16:38:15 +0200 (EET)
Date: Mon, 13 Feb 2006 16:38:15 +0200
From: Maxim Tuliuk <mt@primats.org.ua>
To: freebsd-net@freebsd.org
Message-ID: <20060213143815.GA22437@top.net.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: weirdness with vlans & sk on 5.4-RELEASE
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2006 14:48:01 -0000
Hello!
I'm having some troubles with "sk" netcard in 5.4-RELEASE:
config info:
> part of dmesg boot:
FreeBSD 5.4-RELEASE-p2 #1: Tue Jun 28 16:10:16 EEST 2005
skc0: <3Com 3C940 Gigabit Ethernet> port 0xd400-0xd4ff mem 0xfeae8000-0xfeaebfff irq 22 at device 5.0 on pci2
skc0: 3Com Gigabit LOM (3C940) rev. (0x1)
sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
sk0: Ethernet address: 00:0c:6e:52:2e:5b
miibus0: <MII bus> on sk0
e1000phy0: <Marvell 88E1000 Gigabit PHY> on miibus0
e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto
> ifconfig vlan0
vlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1496
inet 10.49.3.13 netmask 0xffffff00 broadcast 10.49.3.255
ether 00:0c:6e:52:2e:5b
media: Ethernet autoselect (100baseTX <half-duplex>)
status: active
vlan: 9 parent interface: sk0
> ifconfig sk0
sk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 10.49.0.7 netmask 0xffffff00 broadcast 10.49.0.255
ether 00:0c:6e:52:2e:5b
media: Ethernet autoselect (100baseTX <half-duplex>)
status: active
addional info:
10.49.3.13 - the host with "broken" sk
10.49.3.10 - the nfs server host
tcpdump output:
> tcpdump -n -i vlan0 host 10.49.3.10
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vlan0, link-type EN10MB (Ethernet), capture size 96 bytes
16:31:17.890049 IP 10.49.3.13.557961704 > 10.49.3.10.2049: 156 readdir [|nfs]
16:31:17.891576 IP 10.49.3.10 > 10.49.3.13: udp
16:31:19.919736 IP 10.49.3.13.557961704 > 10.49.3.10.2049: 156 readdir [|nfs]
16:31:19.921189 IP 10.49.3.10 > 10.49.3.13: udp
16:31:23.969108 IP 10.49.3.13.557961704 > 10.49.3.10.2049: 156 readdir [|nfs]
16:31:23.970438 IP 10.49.3.10 > 10.49.3.13: udp
> tcpdump -n -i sk0 vlan 9
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on sk0, link-type EN10MB (Ethernet), capture size 96 bytes
16:32:53.875178 IP 10.49.3.13.557961704 > 10.49.3.10.2049: 156 readdir [|nfs]
16:32:53.876145 IP 10.49.3.10.2049 > 10.49.3.13.557961704: reply ok 1472 readdir16:32:53.876578 IP 10.49.3.10 > 10.49.3.13: udp
16:32:55.904865 IP 10.49.3.13.557961704 > 10.49.3.10.2049: 156 readdir [|nfs]
16:32:55.905811 IP 10.49.3.10.2049 > 10.49.3.13.557961704: reply ok 1472 readdir16:32:55.906246 IP 10.49.3.10 > 10.49.3.13: udp
16:32:59.954278 IP 10.49.3.13.557961704 > 10.49.3.10.2049: 156 readdir [|nfs]
16:32:59.955651 IP 10.49.3.10.2049 > 10.49.3.13.557961704: reply ok 1472 readdir16:32:59.956078 IP 10.49.3.10 > 10.49.3.13: udp
as you can see above, sk0 interface receives udp packet but vlan0 doesn't...
Any suggestions?
--
Maxim Tuliuk
WWW: http://primats.org.ua/~mt/
ICQ: 21134222
Bike is the freedom of moving