Raw sockets and ports

[Housatonic]

I was considering giving raw sockets a go (through ASM) but it mentions forwarding the ports, as well as the port +1. I run two servers in a cluster, so I conveniently used ports 27015 and 27016 for them. Does this mean they would cause conflicts if I enabled raw sockets?

[twitch.tv/TehEmoGurl]

Raw sockets do not bind to specific ports. Ports are specifically across TCP and UDP where as sockets are IP. These are completely different protocols.

However, if you are forward a port to a raw socket that is already being used by a none raw socket i would ASSUME the port would onlly be used by the first one that is started. Once the port is open and used by one application it will be closed to all other applications.

I have not tried it myself however so yoou can always give it a shot and let us know, But in theory you should not be able to run both at the same time on the same port.

RAW or LPT is actually a protocol meant specifically for printing, it is very low profile and would not yield a good bandwidth even if it did work.

Simple solution: Open and set custom ports for different uses or set a port range for both to use so the second started will chose a unused port within that range. U can do this with port range forwarding or "triggering" in most if not all modern routers.

Note: It is technically possible to run as many applications as you want off a single port with advanced networking using multiple network LAN switches. However, this will cause congestion onthe port and high chance of data errors and is never reccomended (And i've never actually heard of anyone doign it other than simply to see if it works/is possible).

Hope this helped.

[Gran]

Originally posted by Housatonic:

I was considering giving raw sockets a go (through ASM) but it mentions forwarding the ports, as well as the port +1. I run two servers in a cluster, so I conveniently used ports 27015 and 27016 for them. Does this mean they would cause conflicts if I enabled raw sockets?

Yes it would conflict. When switched to Raw Socket Mode Server 1 would use Port 27015+27016
and Server 2 would use 27016 + 27017, guess you see the Problem ;-)

Put Server 2 to 27017 and your good to go.

[Housatonic]

Alrighty, thank you both!

I was afraid of that answer, reason I wanted to try raw sockets was because I've been getting a number of people dripping into my server lately, and I think I was detecting the first hints of lag, wanted to see if there were improvements to be made. Would hate for the server to be playing hide and seek with them though.

(In case anybody happens to know, would it actually be worth using for that, or is it just a personal preference thing?)

[twitch.tv/TehEmoGurl]

Originally posted by Housatonic:

Alrighty, thank you both!

I was afraid of that answer, reason I wanted to try raw sockets was because I've been getting a number of people dripping into my server lately, and I think I was detecting the first hints of lag, wanted to see if there were improvements to be made. Would hate for the server to be playing hide and seek with them though.

(In case anybody happens to know, would it actually be worth using for that, or is it just a personal preference thing?)

RAW is meant for print servers specifically. Only other used application is for security protocols. They are not meant for heavy bandwidth loads like games and such so i would expect it to perform much worse for this application.

[Housatonic]

Ohh, I see, alrighty, no loss then. That clears it all up, thanks again!

[Gran]

Originally posted by beam.pro/TehEmoGurl:

Originally posted by Housatonic:

Alrighty, thank you both!

I was afraid of that answer, reason I wanted to try raw sockets was because I've been getting a number of people dripping into my server lately, and I think I was detecting the first hints of lag, wanted to see if there were improvements to be made. Would hate for the server to be playing hide and seek with them though.

(In case anybody happens to know, would it actually be worth using for that, or is it just a personal preference thing?)

RAW is meant for print servers specifically. Only other used application is for security protocols. They are not meant for heavy bandwidth loads like games and such so i would expect it to perform much worse for this application.

Uhm you're talking Raw Protocol, network printing protocol using TCP/IP and for that you're right.
Housatronic is talking Raw Sockets, UDP traffic with just a header and no transport layer encapsulation.

@Housatronic the introducing of Raw Sockets by the Devs was a Desaster in Sep/15 lots of timeouts and connection losses while using it. Tried it around then, switched it off after 2 Hours and never used it again. So i'm not able to tell you if they ever fixed the problems, sorry.

[Housatonic]

I did read somewhat mixed things, from what little I found with a quick Google search. Some seemed to have better luck without, while some had been doing fine for months without issue. If it's no significant gain though, convenience probably wins out.