Malformed AS_PATH workaround

[Alexander Shikoff]

Hello,

one of participants of our IXP trying to build BGP session with Route-server
running bird v. 1.2.4. The problem is that customer uses BGP on 
Alcatel-Lucent OS-6850. It seems that this switch requires first-as
matching peer-as and no way to change its behavior.

We're using next configuration for peers:
protocol bgp PEER {
        passive;
        local as MyASN;
        neighbor x.x.x.x as PeerASN;
        rs client;
        import where bgp_in([
		...
        ]);
        export where bgp_out(PeerASN);
}

Is there a way to keep "rs client" functionality, but add MyASN
to as-path? If I create separate export filter with prepends, will it work?

Thanks in advance!

-- 
MINO-RIPE