I tested this on other hardware: It has nothing to do with i354.
It’s a bug in the vlan driver which has already been reported here
        http://marc.info/?l=openbsd-misc&m=139903544321689&w=2

Axel

Am 02.09.2014 um 15:45 schrieb Axel Rau <axel....@chaos1.de>:

> Am 30.08.2014 um 13:46 schrieb Axel Rau <axel....@chaos1.de>:
> 
>> Am 29.08.2014 um 08:11 schrieb Jonathan Gray <j...@jsg.id.au>:
>> 
>>> Initial support for the i347 phy was added back in March but that wasn't
>>> part of 5.5.  I suspect you want something along the lines of the
>>> following patch:
>> Yes, this patch worked (does at least initialization of em2-em5,
>> more testing to follow).
> Next problem shows up with sppp over vlan from MAC 00:60:e0:5a:75:45:
> - - - -
> 13:49:38.170666 00:60:e0:5a:75:39 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q 
> (0x8100)
>                , length 60: vlan 7, p 3, ethertype PPPoE D, PPPoE PADI
>                [Service-Name] [Host-Uniq 0x95F818D3]
> 13:49:38.313082 00:30:88:1f:18:9a > 00:60:e0:5a:75:39, ethertype 802.1Q 
> (0x8100)
>                , length 87: vlan 7, p 6, ethertype PPPoE D, PPPoE PADO
>                [Host-Uniq 0x95F818D3] [AC-Name "FFMR71-se800-B2224180702381"]
>                [AC-Cookie "..lvg}..Bv.>.;8."] [Service-Name]
> 13:49:38.313093 00:60:e0:5a:75:39 > 00:30:75:39:00:30, ethertype 802.1Q 
> (0x8100)
>                , length 60: vlan 7, p 3, ethertype PPPoE D, PPPoE PADR
>                [Service-Name] [AC-Cookie "..lvg}..Bv.>.;8."]
>                [Host-Uniq 0x95F818D3]
> 13:49:43.310779 00:60:e0:5a:75:39 > 00:30:75:39:00:30, ethertype 802.1Q 
> (0x8100)
>                , length 60: vlan 7, p 3, ethertype PPPoE D, PPPoE PADR
>                [Service-Name] [AC-Cookie "..lvg}..Bv.>.;8."] 
>                [Host-Uniq 0x95F818D3]
> 13:49:53.311256 00:60:e0:5a:75:39 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q 
> (0x8100)
>                , length 60: vlan 7, p 3, ethertype PPPoE D, PPPoE PADI
>                [Service-Name] [Host-Uniq 0x95F818D3]
> 13:49:53.339482 00:30:88:1f:18:9a > 00:60:e0:5a:75:39, ethertype 802.1Q 
> (0x8100)
>                , length 87: vlan 7, p 6, ethertype PPPoE D, PPPoE PADO 
>                [Host-Uniq 0x95F818D3] [AC-Name "FFMR71-se800-B2224180702381"]
>                [AC-Cookie "..lvg}..Bv.>.;8."] [Service-Name]
> 13:49:53.339492 00:60:e0:5a:75:39 > 00:30:75:39:00:30, ethertype 802.1Q 
> (0x8100)
>                , length 60: vlan 7, p 3, ethertype PPPoE D, PPPoE PADR
>                [Service-Name] [AC-Cookie "..lvg}..Bv.>.;8."]
>                [Host-Uniq 0x95F818D3]
> 13:50:01.214264 00:60:e0:5a:75:39 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q 
> (0x8100)
>                , length 60: vlan 7, p 3, ethertype PPPoE D, PPPoE PADI
>                [Service-Name] [Host-Uniq 0x95F818D3]
> - - -
> The i347 device (em5) has a hardware-MAC of 00:60:e0:5a:75:45, but shows up
> above as 00:60:e0:5a:75:39.
> The answer to the pppoe server with MAC address 00:30:88:1f:18:9a is being
> sent to MAC 00:30:75:39:00:30 instead.
> 
> Do I need more patches (perhaps VLAN related) for the i347 ?
> 
> Any help welcome,
> Axel
> ---
> PGP-Key:29E99DD6  ☀ +49 151 2300 9283  ☀ computing @ chaos claudius
> 

---
PGP-Key:29E99DD6  ☀ +49 151 2300 9283  ☀ computing @ chaos claudius

Reply via email to