Hmm, when I disable SuSEfirewall2, this does not happen. So it seems like some race between interfaces bring-up and firewall setup. I was unable to reproduce by starting SuSEfirewall2 after system boots.