- Joined
- May 23, 2008
- Messages
- 1,071
- Reaction score
- 574
Guys. This is a fair warning to all of you. Something is up with the broadcast IPV4 needed in the configs. I am not 100% sure yet what needs to go in there, but it's not your WAN IP ending in .255.
I had my stuff configured supposedly correctly... WAN IP's in the correct spots, broadcast send IPs set to my WAN IP, but the last 3 digits changed to 255.
[ex. if my WAN ip was 123.45.67.89, then my broadcast send IP would be 123.45.67.255, like tutorials and such say to set it as]
But... I just got a DDOS report from my dedicated server host.
My machine was DDOSing the IP set as my broadcast IP (ending in .255, the rest same as my original IP)...
I shut down my Iris server and changed the broadcast's but now I am not sure exactly what is needed to be in there for it to work correctly. I have tried 255.255.255.255, 0.0.0.0, and another IP on my system. None seem to let the login server load up fully. Does anyone have any ideas?
I had my stuff configured supposedly correctly... WAN IP's in the correct spots, broadcast send IPs set to my WAN IP, but the last 3 digits changed to 255.
[ex. if my WAN ip was 123.45.67.89, then my broadcast send IP would be 123.45.67.255, like tutorials and such say to set it as]
But... I just got a DDOS report from my dedicated server host.
My machine was DDOSing the IP set as my broadcast IP (ending in .255, the rest same as my original IP)...
I shut down my Iris server and changed the broadcast's but now I am not sure exactly what is needed to be in there for it to work correctly. I have tried 255.255.255.255, 0.0.0.0, and another IP on my system. None seem to let the login server load up fully. Does anyone have any ideas?