Files
Ashin Walpola d107534eb2 Keep vanetza-idf in obu-firmware, so a plain clone builds the firmware
obu-firmware builds against the vanetza-idf C-ITS library, which until now
came from the colleague's microbu-esp32c5 tree beside the repository and was
not tracked here, so a clone of this repository could not build the firmware
it ships. The library alone is now part of obu-firmware, as
obu-firmware/external/vanetza-idf: their external/vanetza-idf at commit
cf4b99f, unchanged (9775 files; see its PROVENANCE.md). CMake takes it from
there by default; -DVANETZA_IDF_DIR still points the build elsewhere.

The rest of the colleague's tree (their own VAM firmware, PKI tooling,
station-link Python tools, the V2X2MAP bridge) stays out of this repository
and gitignored; nothing is pushed to their repository. NOTES.md, docs/06,
TODO.md and the pcap verifier's usage line point at the new location.
2026-09-24 10:56:05 +02:00

31 lines
794 B
C++

#ifndef VANETZA_ROUTER_FUZZING_CONTEXT_HPP
#define VANETZA_ROUTER_FUZZING_CONTEXT_HPP
#include <vanetza/common/manual_runtime.hpp>
#include <vanetza/dcc/interface.hpp>
#include <vanetza/geonet/router.hpp>
#include <vanetza/geonet/transport_interface.hpp>
#include <vanetza/geonet/tests/security_context.hpp>
namespace vanetza
{
class RouterFuzzingContext {
public:
RouterFuzzingContext();
void initialize();
void indicate(ByteBuffer&& buffer);
private:
ManualRuntime runtime;
SecurityContext security;
geonet::ManagementInformationBase mib;
std::unique_ptr<geonet::Router> router;
std::unique_ptr<dcc::RequestInterface> req_ifc;
std::unique_ptr<geonet::TransportInterface> ind_ifc;
};
} // namespace vanetza
#endif //VANETZA_ROUTER_FUZZING_CONTEXT_HPP