Hello, Bird supports with ospf type broadcast. Looks that it actually means hat you execpt from "type mcast". On several networks multicast is broken. Yes it is broken and we cannot do nothing for that because they are metro ethernet and odsl (operator dsl) networks and they are leased from local operators. One solution is make mtmp configuration but if you have 100 router it is nightmare. So I humbly asking new feature. It is real broadcast type. Because of compatibility reasons it is unpossible use type bcast for that and rename multicast for type mcast I suggest that new type is rbcast. It is extension over rfc but it is really usefull one. On real broadcast packets send to 255.255.255.255 so they does not get meshed up with multicast specific rules. I have hear many times "but multicast is broadcast on l2 networks". Pleas dont use that argument. Truck is car, pickup is car but it does not mean that truck is pickup. Some times you have roads where you can drive with pickups but not with trucks. First time when I face this problem I was thiking that "ok this is corner case and solution is ptmp". When we start get these cases on several networks with several operators and several vendors, I start thinking that maybe there is improvement need on ospf. ps How many elese had suffer problems with metro ethernet or dsl network that devices delivery unicast traffic and bcast traffic to ff:ff:ff:ff:ff:ff but does not delivery traffic to 01:00:5e:00:00:05 -- F-Solutions Oy Tapio Haapala PL 7, 90571 Oulu GSM 040-0998371 Skype burner- IRC Burner@ircnet