tech-net archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: MACSEC and if_msk.c
So far I get the following:
# ifconfig -m msk0
msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 18:a9:05:dd:f6:07
media: Ethernet autoselect (1000baseT full-duplex)
status: active
supported Ethernet media:
media none
media 10baseT
media 10baseT mediaopt full-duplex
media 100baseTX
media 100baseTX mediaopt full-duplex
media 1000baseT
media 1000baseT mediaopt full-duplex
media autoselect
inet 192.168.0.15 netmask 0xffffff00 broadcast 192.168.0.255
inet6 fe80::1aa9:5ff:fedd:f607%msk0 prefixlen 64 scopeid 0x1
an extract from dmesg shows (http://www.netbsd.org/~richard/dmesg.txt):
~/src/netbsd$ grep msk dmesg.txt
mskc0 at pci2 dev 0 function 0, Yukon-2 Extreme rev. B0 (0x2): ioapic0
pin 16
msk0 at mskc0 port A: Ethernet address 18:a9:05:dd:f6:07
msk_jumbo_buf = 0xffff800043ff3000
makphy0 at msk0 phy 0: Marvell 88E1149 Gigabit PHY, rev. 1
msk0: link state DOWN (was UNKNOWN)
msk0: link state UP (was DOWN)
Unfortunately, still no external access (ping et al) so far ...
I haven't tinkered with the chksum bits yet nor, for what the Yukon-II
Extreme family is concerned, the V2 DESC bits...
Seems some useful info found perusing the linux sky2 driver, though.
I noticed somebody else using amd64 had some issues (35711), I'm curious
if I should first get i386 going before testing amd64.
concerning MACSEC, I noticed this in a freebsd commit
(from http://www.squish.net/pipermail/owc/2009-April/001292.html):
~ if_msk.c
> Remove holdover XMAC II writes/reads inherited from sk as
> they aren't required and cause problems like the 88E8072
> hard locking a system when enabling macsec bypass.
> Tested on 8053/8072 by me and 8021 by kettenis.
> ok kettenis@ (jsg@)
~ if_skreg.h ~ if_msk.c
> Bypass macsec on extreme/supreme based chips.
> Makes my 88E8072 work.
> ok kettenis@ (jsg@)
Home |
Main Index |
Thread Index |
Old Index