Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Program received signal SIGSEGV, Segmentation fault.This segmentation fault occurs at line 26.
0x6fc61225 in ?? () from c:\users\name\desktop\libstdc++-6.dll
(gdb) continue
Continuing.
[Inferior 1 (process 2652) exited with code 030000000005]
(gdb)
g++ c:/users/name/desktop/test3.cpp -o c:/users/name/desktop/test3 -lsfml-system -lsfml-network -std=c++11
Getting such code right, efficient and then maintain it all is a lot of work that I don't see our team is having.
Then you need to start thinking of what to support. MySQL, PostgreSQL, SQLite, etc...
Honestly there are a ton of very good, well maintained and iften quite modern libraries out there, that do a way better job than we ever could.
If you're afraid of using libraries, then C++ is not really the place to be...
You made your life harder by using the same port to send and receive. If you use 2 different ports, you could port forward like zsbzsb said, but because you have to get into the hole that your outgoing data came out of, it is all down to guesswork if you use the same port. This is a feature (a good intended one) of stateful firewalls. It is meant to, among other things, protect you and your internal network. Instead of trying to circumvent it, you might want to consider alternate solutions if possible.
+--------+ +---------------------------+
| | ---- src = 55001 ----> | ---- randomize port ----> | --- src = 65432 ----+
| PC | | Gateway | |
| | <----- ??? | not mapped : drop <---- | <-- dst = 55001 ----+
+--------+ +---------------------------+
Auch, indeed... You're right.
Will this work then, if I do port-forwarding?
Generally ISPs offer a more expensive 'business' plan that includes a static public IP address which would then allow you to handling incoming connections (port forwarding) and host your own server.
Is this the way to do it then?
<code>
Well according to binary1248 a UDP socket can receive from itself and as you already said it works so no need for the second socket. But when it comes to sending stuff to your public IP and hoping it gets through that is an entirely different issue. You are most likely behind a NAT from your ISP so there is no way for you to allow incoming connections.
See: http://www.sfml-dev.org/faq.php#network-internet-network
#include <iostream>You didn't bind the socket to a port, so obviously the operating system didn't know where to receive the data from. Using the above code I can receive the test string as expected.
#include <string>
#include <cstring>
#include <SFML/System.hpp>
#include <SFML/Network.hpp>
using namespace std;
int main() {
sf::UdpSocket socket;
sf::IpAddress ip = "127.0.0.1";
unsigned short port = 54000;
size_t x = 100;
sf::Socket::Status status;
socket.bind(54000);
char data[50] = "Test";
//Send part
status = socket.send(data, x, ip, port);
if (status == sf::Socket::Done) {
cout << "[Announcement] Packed sended successfull." <<endl;
} else {
cout << "[Error] Failed. Error code returned: " << status << " (Send)." <<endl;
}
//Receive part
char receivedPacket[50];
memset(receivedPacket, 0, 50);
size_t z;
status = socket.receive(receivedPacket, x, z, ip , port);
if (status == sf::Socket::Done) {
cout << "[Announcement] Packet received succesfull." <<endl;
} else {
cout << "[Error] Failed. Error code returned: " << status << " (Receive)." <<endl;
}
cout << receivedPacket << endl;
cin.ignore().get();
}
Dumb statement: but I wasn't aware that the same socket could receive its own data that it just sent (TCP or UDP for that matter). What if you actually open a second socket for receiving and only bind the receiving socket? Oh, and your revised code never binds to a port.
