From owner-freebsd-stable Fri Sep 7 11:43:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 63CD437B403 for ; Fri, 7 Sep 2001 11:43:51 -0700 (PDT) Received: from simoeon.sentex.net (pyroxene.sentex.ca [199.212.134.18]) by smtp1.sentex.ca (8.11.6/8.11.6) with ESMTP id f87Ihbo99492; Fri, 7 Sep 2001 14:43:37 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20010907143601.04c6de00@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 07 Sep 2001 14:38:09 -0400 To: Mike Hogsett , freebsd-stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: VLAN Broken ? ( 4.3-RELEASE-p17 ) In-Reply-To: <200109071827.f87IRgS22146@glob.csl.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 11:27 AM 9/7/01 -0700, Mike Hogsett wrote: >I am having great difficulty with VLANs on 4.3-RELEASE-p17. This looks to be prior to the merging of jlemon's fxp changes and integration of the VLAN code. In the past, did you not apply the patches manually to your kernel ? 4.4 STABLE works very well for me BTW with the fxp nic and jumbo frames. bdr-3-hesp# ifconfig -a | grep ^vlan vlan0: flags=8843 mtu 1500 vlan1: flags=8843 mtu 1500 vlan2: flags=8843 mtu 1500 vlan3: flags=8843 mtu 1500 vlan4: flags=8843 mtu 1500 vlan5: flags=8843 mtu 1500 vlan6: flags=0<> mtu 1500 >uname -a : FreeBSD buzby 4.3-RELEASE-p17 FreeBSD 4.3-RELEASE-p17 #2: >Wed Sep 5 15:26:11 PDT 2001 root@buzby:/usr/src/sys/compile/PRI-NIS >i386 > >ifconfig -a : > >fxp0: flags=8843 mtu 1500 > ether 00:30:48:41:04:7b > media: autoselect (100baseTX ) status: active > supported media: autoselect 100baseTX 100baseTX > 10baseT/UTP 10baseT/UTP >lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 >vlan0: flags=8843 mtu 1500 > inet 192.168.1.250 netmask 0xffffff00 broadcast 192.168.1.255 > ether 00:30:48:41:04:7b > vlan: 1 parent interface: fxp0 >vlan1: flags=8843 mtu 1500 > inet 192.168.4.250 netmask 0xffffff00 broadcast 192.168.4.255 > ether 00:30:48:41:04:7b > vlan: 504 parent interface: fxp0 >vlan2: flags=8843 mtu 1500 > inet 192.168.5.250 netmask 0xffffff00 broadcast 192.168.5.255 > ether 00:30:48:41:04:7b > vlan: 505 parent interface: fxp0 >vlan3: flags=8843 mtu 1500 > inet 192.168.15.250 netmask 0xffffff00 broadcast 192.168.15.255 > ether 00:30:48:41:04:7b > vlan: 515 parent interface: fxp0 >vlan4: flags=8843 mtu 1500 > inet 192.168.16.250 netmask 0xffffff00 broadcast 192.168.16.255 > ether 00:30:48:41:04:7b > vlan: 516 parent interface: fxp0 >vlan5: flags=8843 mtu 1500 > inet 192.168.19.250 netmask 0xffffff00 broadcast 192.168.19.255 > ether 00:30:48:41:04:7b > vlan: 519 parent interface: fxp0 > > > > >From a remote host : > >; ping -s 1468 buzby >PING buzby.somedomain.com (192.168.19.250) from 192.168.15.161 : >1468(1496) bytes of data. >Warning: time of day goes back, taking countermeasures. >1476 bytes from buzby.somedomain.com (192.168.19.250): icmp_seq=0 ttl=255 >time=1.011 msec >1476 bytes from buzby.somedomain.com (192.168.19.250): icmp_seq=1 ttl=255 >time=678 usec >1476 bytes from buzby.somedomain.com (192.168.19.250): icmp_seq=2 ttl=255 >time=671 usec >1476 bytes from buzby.somedomain.com (192.168.19.250): icmp_seq=3 ttl=255 >time=678 usec > >--- buzby.somedomain.com ping statistics --- >4 packets transmitted, 4 packets received, 0% packet loss >round-trip min/avg/max/mdev = 0.671/0.759/1.011/0.147 ms > >; ping -s 1469 buzby >PING buzby.somedomain.com (192.168.19.250) from 192.168.15.161 : >1469(1497) bytes of data. > >--- buzby.somedomain.com ping statistics --- >4 packets transmitted, 0 packets received, 100% packet loss > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message