Network card Intel and 802.1P tag
Hi! I have two network interfaces - fxp and em When i send on both interface packet with 802.1P tag, i see this tag on fxp and don't see on em. em: 10:41:14.849139 00:18:ba:8a:c8:c1 (oui Unknown) 00:15:b7:62:de:ec (oui Unknown), ethertype 802.1Q (0x8100), length 118: vlan 20, p 0 fxp: 10:40:56.259886 00:18:ba:8a:c8:c1 (oui Unknown) 00:02:b3:61:d5:5a (oui Unknown), ethertype 802.1Q (0x8100), length 118: vlan 20, p 4 FreeBSD 7.2-RELEASE em0: Intel(R) PRO/1000 Network Connection 6.9.6 port 0xbfe0-0xbfff mem 0xffae-0xffaf irq 16 at device 0.0 on pci1 fxp0: Intel 82550 Pro/100 Ethernet port 0xa000-0xa03f mem 0xe402-0xe4020fff,0xe400-0xe401 irq 19 at device 1.0 on pci2 miibus0: MII bus on fxp0 Any idea how I can see 802.1P tag on em? -- __ ***AOS224-RIPE*** tel/fax: +380-56-3728171 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Network card Intel and 802.1P tag
У Ср, 2009-08-05 у 10:54 -0500, Gary Gatten пише: Not ALL chipsets / drivers support 802.1Q / p , maybe this is one of them? I have this problem on some ethernet cards, such as: e...@pci0:14:0:0:class=0x02 card=0x109a15d9 chip=0x109a8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82573L Intel PRO/1000 PL Network Adaptor' class = network subclass = ethernet e...@pci0:6:0:0: class=0x02 card=0x108c15d9 chip=0x108c8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82573E Intel Corporation 82573E Gigabit Ethernet Controller (Copper)' class = network subclass = ethernet Andrey O.Sokolov wrote: Any idea how I can see 802.1P tag on em? You should, I guess, with no extra steps. Perhaps the em driver has some hardware capability, which set the priority tag to zero? Is the vlan hardware processing enabled? How I can enable this processing? Could you post the output of ifconfig em0? Output of ifconfig both: em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:15:b7:62:de:ec media: Ethernet 100baseTX full-duplex status: active vlan20: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=3RXCSUM,TXCSUM ether 00:15:b7:62:de:ec inet media: Ethernet 100baseTX full-duplex status: active vlan: 20 parent interface: em0 == fxp0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC ether 00:02:b3:61:d5:5a media: Ethernet 100baseTX full-duplex status: active vlan20: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=3RXCSUM,TXCSUM ether 00:02:b3:61:d5:5a inet media: Ethernet 100baseTX full-duplex status: active vlan: 20 parent interface: fxp0 -- ***AOS224-RIPE*** mailto:arc...@alkar.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [?? Probable Spam] Re: Network card Intel and 802.1P tag
У Ср, 2009-08-05 у 20:41 +0300, Nikos Vassiliadis пише: Is the vlan hardware processing enabled? How I can enable this processing? ifconfig em0 vlanhwtag enables vlan processing in hw ifconfig em0 -vlanhwtag disables vlan processing in hw Maybe one these will work correctly without the zeroing effect. I tried both variant on both NIC - fxp and em The result doesn't change ;( Perhaps off topic, but why are you interested in priority tags, since FreeBSD will silently ignore them? I developing QoS-model for big network. I have casualy found out this problem, when I analyzed the traffic with different COS-value from various devices. -- ***AOS224-RIPE*** mailto:arc...@alkar.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading from 6.2 to 7.0
On Sat, Mar 08, 2008 at 07:48:40PM +, Adam J Richardson wrote:
Jay Deiman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a couple of 6.2 machines that I would like to upgrade to the 7.0
release. Is there an official set of instructions for this process?
1.cvsup new source (src port)
2.cd /usr/src
3.make buildworld
4.change you KERNCONF
5.make KERNCONF=yourKERN
6.shutdown -r now (reboot in single mode)
7.mergemaster -p
8.make delete-old
9.make installworld
10.mergemaster
11.reboot
12.cd /usr/port/ports-mgmt/portmanager
13.make deinstall make install clean (if portmanager was install)
14. portmanager -u -f
15. cd /usr/src
16. make delete-old-libs
17.shutdown -r now
Thanks,
Jay Deiman
Hi Jay,
This isn't a recommendation or anything, but I did manage to upgrade one
of my boxes from 6.3-SOMETHING to 7.0-BETA4 using the standard make
{build{world,kernel},install{kernel,world}} process. I didn't have any
problems with it, but it's not a supported method, so only do this if
you're a crazy like me with no regard for his data. Actually you're
probably best off backing up all your data and doing a clean install.
Since I'm a crazy with no regard for his data, I'm doing it again
tonight, this time to 7.0-RELEASE with a GENERIC kernel. I'll let you
know how it goes.
YMMV
#include disclaimer.h
etc.
Regards,
Adam J Richardson
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
___
С уважением,
Андрей Соколов
***AOS224-RIPE*** mailto:[EMAIL PROTECTED]
Phone +38(056)3728047
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
