The code:
struct PacketData
{
ClientData clientData;
uint8_t header[1];
sf::Packet packet;
sf::Socket::Status status;
time_point recieveTime;
};
...
while (!m_shutdown)
{
if (!m_selector.wait(sf::seconds(1.0f)))
{
continue;
}
{
size_t recieved;
std::lock_guard<std::mutex> lock(m_socketMutex);
packetData.status = m_socket.receive(packetData.header, 1, recieved, packetData.clientData.address, packetData.clientData.port);
}
const auto& isOnIgnoreList = std::find_if(m_ignoreList.begin(), m_ignoreList.end(), [&packetData](const ClientData& clientData) {return packetData.clientData == clientData; }) != m_ignoreList.end();
if (isOnIgnoreList)
{
// HERE! How to ignore the packet without recieving it?
continue;
}
...
}
I'm trying to implement a "IP ban", and my question is: does SFML allow to somehow ignore the packet without actually receiving it? Because if I just ignore the packet, the selector.wait will return true all the time as there's data to read.
Also just noticed, the first .recieve returns an error and reads 0 bytes... why? There's only one socket in selector.
The code:
struct PacketData
{
ClientData clientData;
uint8_t header[1];
sf::Packet packet;
sf::Socket::Status status;
time_point recieveTime;
};
...
while (!m_shutdown)
{
if (!m_selector.wait(sf::seconds(1.0f)))
{
continue;
}
{
size_t recieved;
std::lock_guard<std::mutex> lock(m_socketMutex);
packetData.status = m_socket.receive(packetData.header, 1, recieved, packetData.clientData.address, packetData.clientData.port);
}
const auto& isOnIgnoreList = std::find_if(m_ignoreList.begin(), m_ignoreList.end(), [&packetData](const ClientData& clientData) {return packetData.clientData == clientData; }) != m_ignoreList.end();
if (isOnIgnoreList)
{
// HERE! How to ignore the packet without recieving it?
continue;
}
...
}
I'm trying to implement a "IP ban", and my question is: does SFML allow to somehow ignore the packet without actually receiving it? Because if I just ignore the packet, the selector.wait will return true all the time as there's data to read.
Also just noticed, the first .recieve returns an error and reads 0 bytes... why? There's only one socket in selector.
The documentation doesn't say anything about blocking. U can do one of these 2 things:
- check the ip manually (not recommended due speed; it could been the way SFML would do that anyway if this was a core feature)
- modify one of the active firewalls (the closer to the global infrastructure the better; example: block on the router rather than ur pc if the router is dedicated for the server, so the packet won't reach the pc)