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 13.11.2014 um 16:01 schrieb Axel Rau <[email protected]>:

> Hi,
> 
> This is a pppoe-client on Atom C2000 based Axiomtek NA361 Hardware.
> pppoe is running via VLAN on device em5, which is I354 based:
> 
> em5: flags=28843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6> mtu 1500
>        lladdr 00:60:e0:5a:75:39
>        priority: 0
>        media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause)
>        status: active
> # ifconfig vlan7  
> vlan7: flags=28843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6> mtu 1500
>        lladdr 00:60:e0:5a:75:39
>        priority: 0
>        vlan: 7 parent interface: em5
>        groups: vlan
>        status: active
> # ifconfig pppoe0
> pppoe0: flags=28810<POINTOPOINT,SIMPLEX,MULTICAST,NOINET6> mtu 1492
>        priority: 0
>        dev: vlan7 state: initial
>        sid: 0x0 PADI retries: 0 PADR retries: 0
>        groups: pppoe egress
>        status: no carrier
>        inet 0.0.0.0 --> 0.0.0.1 netmask 0xffffffff
> 
> The pppoe server side has a MAC of 00:30:88:1f:18:9a and the client em5 is 
> 00:60:e0:5a:75:39
> 
> Here, the client asks for the server via broadcast:
> 20:59:34.771668 00:60:e0:5a:75:39 (oui Unknown) > Broadcast, ethertype 802.1Q 
> (0x8100),\
>       length 60: vlan 7, p 3, ethertype PPPoE D, PPPoE PADI [Service-Name] \
>       [Host-Uniq 0x3DCA3906]
> The server responds:
> 20:59:34.800113 00:30:88:1f:18:9a (oui Unknown) > 00:60:e0:5a:75:39 (oui 
> Unknown),\
>       ethertype 802.1Q (0x8100), length 87: vlan 7, p 6, ethertype PPPoE D,\
>       PPPoE PADO [Host-Uniq 0x3DCA3906] [AC-Name 
> „FFMR71-se800-B2224180702381“]\
>       [AC-Cookie „..lvg}..Bv.>.;8."] [Service-Name]
> The client’s answer is going to 00:30:75:39:00:30 instead of 
> 00:30:88:1f:18:9a:
> 20:59:34.800121 00:60:e0:5a:75:39 (oui Unknown) > 00:30:75:39:00:30 (oui 
> Unknown),\
>       ethertype 802.1Q (0x8100), length 60: vlan 7, p 3, ethertype PPPoE D, \
>       PPPoE PADR [Service-Name] [AC-Cookie „..lvg}..Bv.>.;8."] [Host-Uniq 
> 0x3DCA3906]
> This is the bug.
> 
> An example of a working negotiation (another obsd client, with other hardware,
> 00:80:c8:c9:7f:e0, same server):
> 
> 20:56:06.361036 00:80:c8:c9:7f:e0 (oui Unknown) > Broadcast, ethertype 802.1Q 
> (0x8100),\
>       length 60: vlan 7, p 3, ethertype PPPoE D, PPPoE PADI [Service-Name] \
>       [Host-Uniq 0x0B998AFC]
> 20:56:06.438095 00:30:88:1f:18:9a (oui Unknown) > 00:80:c8:c9:7f:e0 (oui 
> Unknown),\
>       ethertype 802.1Q (0x8100), length 87: vlan 7, p 6, ethertype PPPoE D,\
>       PPPoE PADO [Host-Uniq 0x0B998AFC] [AC-Name 
> „FFMR71-se800-B2224180702381“]\
>       [AC-Cookie „..G..#z Cd0=.9{."] [Service-Name]
> 20:56:06.438105 00:80:c8:c9:7f:e0 (oui Unknown) > 00:30:88:1f:18:9a (oui 
> Unknown),\
>       ethertype 802.1Q (0x8100), length 60: vlan 7, p 3, ethertype PPPoE D,\
>       PPPoE PADR [Service-Name] [AC-Cookie „..G..#z Cd0=.9{."] [Host-Uniq 
> 0x0B998AFC]
> 20:56:06.590633 00:30:88:1f:18:9a (oui Unknown) > 00:80:c8:c9:7f:e0 (oui 
> Unknown),\
>       ethertype 802.1Q (0x8100), length 67: vlan 7, p 6, ethertype PPPoE D,\
>       PPPoE PADS [ses 0x256d] [Service-Name] [Host-Uniq 0x0B998AFC]\
>       AC-Name „FFMR71-se800-B2224180702381“]
> 20:56:06.590643 00:80:c8:c9:7f:e0 (oui Unknown) > 00:30:88:1f:18:9a (oui 
> Unknown),\
>       ethertype 802.1Q (0x8100), length 60: vlan 7, p 3, ethertype PPPoE S,\
>       PPPoE  [ses 0x256d] LCP (0xc021), length 16: LCP, Conf-Request (0x01), 
> id 1, length 16
>       encoded length 14 (=Option(s) length 10)
>         Magic-Num Option (0x05), length 6: 0x1f15ce89
>         MRU Option (0x01), length 4: 1492
> 
> Axel
> PS: dmesg attached: 
> <dmesg_ifconfig.txt>
> —
> PGP-Key:29E99DD6  ☀ +49 151 2300 9283  ☀ computing @ chaos claudius
> 

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


Reply via email to