From nobody@FreeBSD.org  Sun Sep 15 07:36:31 2002
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6A7A237B400
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 15 Sep 2002 07:36:31 -0700 (PDT)
Received: from www.freebsd.org (www.FreeBSD.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0B04043E3B
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 15 Sep 2002 07:36:31 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.4/8.12.4) with ESMTP id g8FEaUOT086778
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 15 Sep 2002 07:36:30 -0700 (PDT)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.4/8.12.4/Submit) id g8FEaUQm086777;
	Sun, 15 Sep 2002 07:36:30 -0700 (PDT)
Message-Id: <200209151436.g8FEaUQm086777@www.freebsd.org>
Date: Sun, 15 Sep 2002 07:36:30 -0700 (PDT)
From: Andrew Stesin <stesin@tormoz.net>
To: freebsd-gnats-submit@FreeBSD.org
Subject: VLANs do not work with fxp + catalyst as they supposed to
X-Send-Pr-Version: www-1.0

>Number:         42806
>Category:       i386
>Synopsis:       VLANs do not work with fxp + catalyst as they supposed to
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Sep 15 07:40:01 PDT 2002
>Closed-Date:    Sat Jul 10 15:57:21 GMT 2004
>Last-Modified:  Sat Jul 10 15:57:21 GMT 2004
>Originator:     Andrew Stesin
>Release:        4.7-PRERELEASE
>Organization:
TormozNet
>Environment:
FreeBSD chour.hostmaster.net.ua 4.7-PRERELEASE FreeBSD 4.7-PRERELEASE #3: Sun Sep 15 14:47:25 EEST 2002     root@chour
.hostmaster.net.ua:/home/.src/sys/compile/CHOUR  i386
>Description:
After long fiddling, now it works. FreeBSD 4.7-PRERELEASE, Cat 2940XL

Working rc.conf fragment *now* looks this way:

--- 8< ---

network_interfaces="lo0 fxp0 fxp1 vlan0 vlan1 vlan2 vlan3 vlan4 vlan5"
ifconfig_lo0="inet 127.0.0.1 netmask 255.0.0.0"

# fxp0 - "internal" trunk

ifconfig_fxp0="media 100baseTX mediaopt full-duplex link0 up"
ifconfig_vlan0="inet 10.99.25.1 netmask 255.255.255.0 vlan 25 vlandev fxp0 mtu 1500 up arp"
ifconfig_vlan1="inet 10.99.23.1 netmask 255.255.255.0 vlan 23 vlandev fxp0 mtu 1500 up arp"
ifconfig_vlan2="inet 10.100.2.1 netmask 255.255.255.0 vlan 2 vlandev fxp0 mtu 1500 up arp"

# fxp1 - "external" trunk

ifconfig_fxp1="media 100baseTX mediaopt full-duplex link0 up"
ifconfig_vlan3="inet 17.33.33.61 netmask 255.255.255.252 vlan 3 vlandev fxp1 mtu 1500 up arp"
ifconfig_vlan4="inet 12.44.44.30 netmask 255.255.255.252 vlan 4 vlandev fxp1 mtu 1500 up arp"
ifconfig_vlan5="inet 95.55.55.22 netmask 255.255.255.248 vlan 5 vlandev fxp1 mtu 1500 up arp"

--- 8< ---

The problem is: as soon as I say "link0" in ifconfigs for vlanXX
interfaces, is just plain doesn't work. Catalyst doesn't see even a
mac-addresses for vlanXX interfaces.

Another problem is: as soon as I remove "link0" from ifconfigs for
"carrier" interfaces fxp0 and fxp1 - again it doesn't work.

Also I can't "see" Catalyst "own" IP (seen at `sh in vlan1') after
I do:
ifconfig vlan6 inet 10.100.200.1 netmask 255.255.255.0 vlan 1 vlandev fxp0 mtu 1500 up arp

ping 10.100.200.2  (to catalyst) never returns, but! what a surprise! as soon as I do
ping 10.100.200.255 - I get responces from 10.100.200.2 ! The address 10.100.200.2 doesn't then appear in ARP table anyway.
>How-To-Repeat:
      Supposedly if you take a box with two fxp interfaces and plug them into Catalyst 2900 XL - you will(?) get the same problem?

The box is SuperMicro 1U server with ServerWorks chipset and 2 onboard fxp's:

fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xd000-0xd03f mem 0xfe800000-0xfe8fffff,0xfeafc000-0xfeafcfff irq 5 at
device 4.0 on pci0
fxp0: Ethernet address 00:30:48:11:0f:85
inphy0: <i82555 10/100 media interface> on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: <Intel Pro 10/100B/100+ Ethernet> port 0xd400-0xd43f mem 0xfe900000-0xfe9fffff,0xfeafd000-0xfeafdfff irq 9 at
device 6.0 on pci0
fxp1: Ethernet address 00:30:48:11:0f:84
inphy1: <i82555 10/100 media interface> on miibus1
inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

pcib0: <ServerWorks NB6635 3.0LE host to PCI bridge> on motherboard
pcib1: <ServerWorks NB6635 3.0LE host to PCI bridge> on motherboard

>Fix:
      Remove link0 from ifconfig's for vlanXX interfaces. Add "link0 up" to ifconfigs for "carrier" fxp interfaces. Pray.
>Release-Note:
>Audit-Trail:

From: Yar Tikhiy <yar@FreeBSD.org>
To: freebsd-gnats-submit@FreeBSD.org, stesin@tormoz.net
Cc:  
Subject: Re: i386/42806: VLANs do not work with fxp + catalyst as they supposed to
Date: Thu, 30 Jan 2003 19:29:09 +0300

 Andrew,
 
 First of all, the link0 flag should not be set on a vlan interface
 unless its parent device (specified with "vlandev") supports VLANs
 in both its hardware and driver.  The list of such devices may be
 seen on the vlan(4) manpage; fxp isn't in the list.
 
 Second, what fxp cards did you use?  As fxp(4) states, the link0
 flag means to the fxp driver that accelerating microcode must be
 loaded to the card.  Perhaps your cards just couldn't function
 without such microcode?
 
 Would you mind telling the current state of the problem you met?
 
 -- 
 Yar
State-Changed-From-To: open->suspended 
State-Changed-By: bms 
State-Changed-When: Sun Jul 4 16:05:17 GMT 2004 
State-Changed-Why:  
Timeout on feedback 

http://www.freebsd.org/cgi/query-pr.cgi?pr=42806 
State-Changed-From-To: suspended->closed 
State-Changed-By: linimon 
State-Changed-When: Sat Jul 10 15:56:44 GMT 2004 
State-Changed-Why:  
Submitter notes that he no longer experiences this problem. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=42806 
>Unformatted:
