
As mentioned in my previous reply, ns-3 lacks a complete implementation of the DSRC stack. The code you may encounter labeled as 'ns-2-dsrc' typically only mimics primitive functions through an 802.11p.tcl script and basic application-layer logic.
If you are conducting serious research on VANET/DSRC, results obtained through these primitive ns-2 extensions will not accurately reflect real-world scenarios. This is because they fail to incorporate essential multi-channel scheduling and routing capabilities inherent to a standard DSRC stack.
Therefore, if this is for scholarly research and you are in the early stages, I strongly recommend avoiding ns-2 for VANET/DSRC simulations to ensure the validity of your findings.
--
You received this message because you are subscribed to the Google Groups "Network Simulator 2 (NS2)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-users+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ns-users/fdb38f29-ac47-41ca-968f-67cf988d9c27n%40googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ns-users/CAHXeiM8z2WW%3D%2Bfxn98r5J55LXrgfMwg2mf0_6%2Bv2tYQGWeFQgQ%40mail.gmail.com.
If you are conducting research on VANETs using the DSRC protocol stack, it is vital to first develop a deep understanding of what DSRC actually entails. (A good starting point is my previous post: 'Confusions in doing VANET simulations using DSRC/WAVE under ns-3 or ns-2').

(Even though you can not find a complete implementation of it in any simulator,) Try to understand each and every component of an ideal DSRC protocol stack.
The reason is that DSRC is uniquely and brilliantly designed specifically for VANET communication scenarios. However, it is not yet fully implemented in most simulators. Furthermore, the original scope of DSRC found in older white papers is evolving rapidly due to the practical integration of 4G/5G technology.
Currently, Veins (for OMNeT++) is the framework closest to the original DSRC drafts. However, you should also explore the 'ms-van3t' extension for ns-3. As a Multi-Stack VANET Framework, it goes beyond the original DSRC stack by attempting to utilize modern mobile communication technologies for V2V and V2X communication.
But I prefer using ns-3 (ms-van3t') and developing your protocols from scratch, under this framework.
To view this discussion visit https://groups.google.com/d/msgid/ns-users/CAE%2BbC6oSFxhjjFmcE9SJxbtORuZNpTeSe8o8--0H8BO2icTFLA%40mail.gmail.com.
To view this discussion visit https://groups.google.com/d/msgid/ns-users/CAHXeiM_D%2BhKz9Af6TMN3DhRN8waTz_w%2BGBa-ASmUBG5T5gy5kQ%40mail.gmail.com.