IP id is set to 0 on unconnected sockets when the DF bit is set (path mtu discovery is enabled). Try issuing a connect() in your application and see if the ids are increasing again.
ID of zero again? I thought that went away years ago? Anyway, given the number of "helpful" devices out there willing to clear the DF bit, fragment and forward, perhaps always setting the IP ID to 0, even if DF is set, isn't such a good idea?
rick jones - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
