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.
27 lines
753 B
C++
27 lines
753 B
C++
#ifndef DCC_PASSTHROUGH_HPP_GSDFESAE
|
|
#define DCC_PASSTHROUGH_HPP_GSDFESAE
|
|
|
|
#include "time_trigger.hpp"
|
|
#include <vanetza/access/interface.hpp>
|
|
#include <vanetza/dcc/data_request.hpp>
|
|
#include <vanetza/dcc/interface.hpp>
|
|
#include <vanetza/net/cohesive_packet.hpp>
|
|
|
|
class DccPassthrough : public vanetza::dcc::RequestInterface
|
|
{
|
|
public:
|
|
DccPassthrough(vanetza::access::Interface&, TimeTrigger& trigger);
|
|
|
|
void request(const vanetza::dcc::DataRequest& request, std::unique_ptr<vanetza::ChunkPacket> packet) override;
|
|
|
|
void allow_packet_flow(bool allow);
|
|
bool allow_packet_flow();
|
|
|
|
private:
|
|
vanetza::access::Interface& access_;
|
|
TimeTrigger& trigger_;
|
|
bool allow_packet_flow_ = true;
|
|
};
|
|
|
|
#endif /* DCC_PASSTHROUGH_HPP_GSDFESAE */
|