[Bridge] [PROBLEM] mac address learned on wrong port

[Seweryn Niemiec <ser@man.szczecin.pl>]

Hi,

On one of my servers, the most basic thing doesn't work and after 2 days of 
unsuccessful digging in my severs and the Internet, I'm desperate enough to 
write to this list :)

Ubuntu server with kernel 3.19.0-33-generic #38~14.04.1-Ubuntu has p2p1.17 
physical interface attached to bri17 bridge. When I start some LXC container, it 
creates for ex. vethPQORXD interface and adds it to bri17 bridge. It looks like 
this:

# brctl show bri17
bridge name     bridge id               STP enabled     interfaces
bri17           8000.00163eaaaa30       no              p2p1.17
                                                         vethPQORXD

LXC container's eth0 interface (linked to vethPQORXD) has mac 00:16:3e:aa:aa:66. 
When I add IP do this eth0 and ping something to generate eth frame, that mac is 
learned on p2p1.17 port instead of vethPQORXD:

# brctl showmacs bri17
port no mac addr                is local?       ageing timer
   1     00:16:3e:aa:aa:66       no               112.50
[... some other macs ...]
   1     3c:fd:fe:01:ee:e0       yes                0.00
   1     3c:fd:fe:01:ee:e0       yes                0.00
   2     fe:56:74:59:a4:9e       yes                0.00
   2     fe:56:74:59:a4:9e       yes                0.00

Of course it makes communication of outside world with that container impossible 
(host<->container works).

Any ideas why this happens?

-- 
Best regards,
Seweryn Niemiec